EverestAPI / EverestAPI/Olympus

[Feature Request] Adding verbose prompt to exit out of debugging

Open
#153 0 comments 0 reactions 0 assignees View on GitHub
Dominant language
Lua
Stars
179
Forks
41
Avg merge
2d 16h
Merged PRs (30d)
8

Description

### Environment
Debian 13 (trixie) 6.12.73-1
Everest 25.12.05.01-azure-5355-2959f ([latest](https://dev.azure.com/EverestAPI/Olympus/_apis/build/builds/5355/artifacts?artifactName=linux.main&api-version=5.0&%24format=zip))

### Reproducing

Pressing `F3` or `Fn + F3` key in a running Everest instance causes debug profiler to run, which spawns an error screen that you cannot exit out of unless you use the relevant key again and spawn a new instance. I have uploaded the relevant error output [here](https://github.com/user-attachments/files/25819907/debug-error-spawned.txt) for the sake of good practice although I know better than to try and dip into testing code.

The `F3` key is likely intended for testing (`debugLabel`) Love Engine but on the user end, accidentally pressing it will cause the error to persist with no verbose prompt to exit out of the mode. You would have to look at the relevant source code to identify what went wrong.

Furthermore, debugging will persist because the state is saved outside the Everest install (thank you Love Engine), it would be crucial to make users aware of how to exit out of it.

### Proposed solution

Print out a verbose prompt to cleanly exit out of the mode for users who did not intent to startup debugging.

Contributor guide

No contributing guide indexed for this repository

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.