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
Is your feature request related to a problem? Please describe.
I don't use QWERTY, and even if I did, I'd be using esdf for movement anyway. Overall it just doesn't make sense why wasd is used to describe button presses instead of ↑←↓→ considering it's much more terse and universal and doesn't make assumptions on the client's external influences.
On top of that the other button presses are marked by the first letter of their action (i.e. jump is J, crouch is C, etc.) and based on the default bindings of the games. Seems inconsistent.
Describe the solution you'd like
Modify these values from AWSDCJLR to ←↑↓→_^↺↻ with - used to represent not pressed.
Describe alternatives you've considered
An alternative that might be a headache to implement would be to allow clients to set preferred glyphs to represent those keys, I'm not a fan of this approach however since that's one more thing for someone to setup.
The text was updated successfully, but these errors were encountered:
I started formatting this but couldn't get it perfect. This is a pretty easy edit to make. The file is /surftimer/misc.sp and the function is -> public void CenterHudDead - see below:
Is your feature request related to a problem? Please describe.
I don't use QWERTY, and even if I did, I'd be using esdf for movement anyway. Overall it just doesn't make sense why wasd is used to describe button presses instead of
↑
←
↓
→
considering it's much more terse and universal and doesn't make assumptions on the client's external influences.On top of that the other button presses are marked by the first letter of their action (i.e. jump is J, crouch is C, etc.) and based on the default bindings of the games. Seems inconsistent.
Describe the solution you'd like
Modify these values from
AWSDCJLR
to←↑↓→_^↺↻
with-
used to represent not pressed.Describe alternatives you've considered
An alternative that might be a headache to implement would be to allow clients to set preferred glyphs to represent those keys, I'm not a fan of this approach however since that's one more thing for someone to setup.
The text was updated successfully, but these errors were encountered: