EverestAPI/Everest

Improve Asset Reloading

Open

#321 opened on Jun 16, 2021

View on GitHub
 (0 comments) (0 reactions) (0 assignees)C# (104 forks)auto 404
discussionhelp wantedrewrite

Repository metrics

Stars
 (503 stars)
PR merge metrics
 (PR metrics pending)

Description

  • Unloading assemblies needs to be redone so that it actually works properly (it should be noted that fully unloading assemblies will never be possible using .NET Framework and due to how the game is built)
  • Hot-swapping assemblies needs to be done in a way that accounts for dependencies
  • Hot-swapping maps and content can cause concurrency issues, and not all assets can be hotswapped reliably

Contributor guide

Research direction
Investigate the current assembly unloading mechanism in .NET Framework and design a new approach that properly unloads assemblies while accounting for dependencies and concurrency issues during hot swapping of maps and content.
Tech stack
csharp
Domain
backend
Issue type
Refactor
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
4
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
3-5 days
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
Fresh
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
Mostly clear
Prerequisites
C#.NET
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
30