You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In the settings menu, the keybinds for switching tabs are tied to the keybinds for "Cycle Form" and "Cycle Shiny". This means that if the user somehow deletes those keybinds, the user will no longer be able to switch tabs in the settings, which prevents the user from accessing the keyboard settings to undo this mistake later on. This effectively bricks the keyboard settings (unless the user deletes settings from local storage, etc.).
Reproduction
(See description)
Expected behavior
There should be some sort of safeguard preventing the user from deleting these important keybinds.
Screenshots / Videos
20250114.Bricking.Keyboard.Settings.mp4
Session export file
No response
User data export file
No response
Additional context
No response
The text was updated successfully, but these errors were encountered:
PigeonBar
added
Triage
The issue needs triage
P1 Bug
Major bug. Used for when a specific move/ability/interaction causes the game to softlock or crash.
UI/UX
User interface/-experience related
and removed
Triage
The issue needs triage
labels
Jan 14, 2025
Describe the bug
In the settings menu, the keybinds for switching tabs are tied to the keybinds for "Cycle Form" and "Cycle Shiny". This means that if the user somehow deletes those keybinds, the user will no longer be able to switch tabs in the settings, which prevents the user from accessing the keyboard settings to undo this mistake later on. This effectively bricks the keyboard settings (unless the user deletes settings from local storage, etc.).
Reproduction
(See description)
Expected behavior
There should be some sort of safeguard preventing the user from deleting these important keybinds.
Screenshots / Videos
20250114.Bricking.Keyboard.Settings.mp4
Session export file
No response
User data export file
No response
Additional context
No response
The text was updated successfully, but these errors were encountered: