Thanks a lot for sharing! Very interesting experiment.
That said, please please, no "WASD". This is very uncomfortable on non-QWERTY keyboard layouts.
There are two solutions to this.
# Best solution
Game programmer always mean "the group of physically-positioned keys that happen to be labelled WASD on the programmer's keyboard", not "whatever keys that are actually labelled WASD on the player's keyboard".
So, wherever possible, use an API that refers to key position, not key symbol. This is possible in most programming environments, e.g. in Javascript using https://developer.mozilla.org/en-US/docs/Web/API/KeyboardEve...
# Alternative solution
Alternatively, use keys that are stable across most common Latin keyboards layout, which means no AMQWYZ.
ESDF is fine, as are RDFG, TFGH, or the traditional IJKL (see https://en.wikipedia.org/wiki/Arrow_keys for more).
If you want to be kind to Dvorak, Bepo, Colemak and other users, prefer the first solution!
https://en.wikipedia.org/wiki/Keyboard_layout#QWERTY-based_L...
That said, please please, no "WASD". This is very uncomfortable on non-QWERTY keyboard layouts.
There are two solutions to this.
# Best solution
Game programmer always mean "the group of physically-positioned keys that happen to be labelled WASD on the programmer's keyboard", not "whatever keys that are actually labelled WASD on the player's keyboard".
So, wherever possible, use an API that refers to key position, not key symbol. This is possible in most programming environments, e.g. in Javascript using https://developer.mozilla.org/en-US/docs/Web/API/KeyboardEve...
# Alternative solution
Alternatively, use keys that are stable across most common Latin keyboards layout, which means no AMQWYZ.
ESDF is fine, as are RDFG, TFGH, or the traditional IJKL (see https://en.wikipedia.org/wiki/Arrow_keys for more).
If you want to be kind to Dvorak, Bepo, Colemak and other users, prefer the first solution!
https://en.wikipedia.org/wiki/Keyboard_layout#QWERTY-based_L...