EverestAPI / EverestAPI/Everest

"retry level" from crash handler doesn't reload the level

Open
#1,145 0 comments 0 reactions 0 assignees View on GitHub
bug
Dominant language
C#
Stars
516
Forks
106
Avg merge
4d 9h
Merged PRs (30d)
5

Description

### My mods and Everest install are up to date

Yes

### I have recreated the bug with only Everest OR a minimum number of mods enabled

Yes

### Describe the bug

upon tripping the everest crash handler, selecting "retry level" does not reload the level, even if it has been modified. this means even if you fix whatever's crashing the game, you won't be able to retry level and will instead have to save and quit and load the map from the overworld

### Steps to reproduce

1. open a room in a map that will trip the crash handler immediately upon loading into it, but **not** in loadlevel
2. after the crash handler is triggered, modify the map such that the crash no longer happens
3. select "retry level" from the crash handler
4. the crash handler trips again, as the level has not been reloaded

### Expected behavior

the hot reload should either occur as normal on save while the crash handler is active (on the surface, seems likely infeasible to me as there is explicit behavior within AssetReloadHelper to prevent this from occuring, which surely isn't there for no reason), or the level should be reloaded when "retry level" is selected

### Operating System

to my knowledge, any

### Everest Version

6397

### Mods required to reproduce

_No response_

### Additional context

_No response_

Contributor guide

Open the contributing guide

Research direction

Start by tracing the crash handler's "Retry Level" action and AssetReloadHelper, then compare that path with normal level loading. Reproduce with a room that crashes on entry, modify it to stop crashing, and verify that Retry Level loads the modified level without invoking the crash handler again.

Written by the indexing model from the issue text.

Assessment

Tech stack
csharp
Domain
game-dev
Issue type
Bug
Difficulty
3/5
Estimated time
1-2 days
Activity status
Quiet
Clarity
Mostly clear
Newbie friendliness
58/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.