EverestAPI / EverestAPI/Everest
Improve level error handling
- Dominant language
- C#
- Stars
- 516
- Forks
- 106
- Avg merge
- 4d 9h
- Merged PRs (30d)
- 5
Description
### I am planning on implementing this myself
Yes
### Describe your request
Currently maps hard crash if you encounter an exception within them, _except_ when entering from `LevelEnter`, e.g. loading a map from a new savefile. In that case, it opens a postcard informing you that an exception has occurred and returns you to map. I want to look into:
1. Moving this "soft-crash" functionality so it gets called in more situations. Looking first into exceptions that occur during level load, ideally others as well.
2. Improving logs in places that hard-crash with non-descriptive exceptions and stack traces, e.g. autotiler-related crashes.
3. Potentially manually invoking the soft-crash features with specific messages for common crashes.
### Additional context
_No response_
Contributor guide
Assessment
This issue has not been assessed yet.