EverestAPI/Everest

Issues with the Debug Console

Open

#314 opened on Jun 8, 2021

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

Repository metrics

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

Description

  • Using the q command (added by Everest) while in-game to close the console will open the pause menu, since it seems that the Enter input is not consumed and Enter is now bound to pause by default in 1.4.0.0
    • This can also be seen by rebinding Enter to any other action and then using the q command when that action could otherwise be used.
  • The ` character, when typed on a non-US keyboard layout, opens and closes the debug console as expected, however pressing the key in the location of the ` key on the US layout will close the console but not open it
  • Opening the console with the . key, as added by Everest seems to put the console into a state of being "extra-open", and processes key inputs differently than when opening it with `, such that on a non-US layout, the key corresponding to the position of the US ` key no longer closes the console, and instead types it's corresponding character. When the ` character is typed, it causes the console to return to "normal" behaviour without closing it, allowing either the ` character or corresponding ` key to close it.

Contributor guide

Research direction
Examine the input handling in Commands.cs, particularly the `q` command and key bindings. Trace the event flow to understand why Enter isn't consumed and why `.` key causes different behavior.
Tech stack
csharp
Domain
backend
Issue type
Bug
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
3
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
1-3 hours
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.
Clear
Prerequisites
C#
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
60