Thank you, i gave a try to the key debugger and noticed that when i press :
azerty "<" the result is the game detecting the keypress is "<"
but if i press azerty "." (that should result into "<"), it results into ":" ?
Now if i press azerty ">" the game detect it as "<" ? or if i press the azerty ":" the result is ":" ?
now if i press SHIFT+A , SHIFT+Q and SHIFT+W (so the game does not detect the lower case version, because it would only trigger the actual game action instead of showing the debugging message), it leads into the detected results being a , q and w in that order , something odd, because azerty -> qwerty should lead into the result order being q, a and z
It's as if the game is able to detect azerty keys there ?
For the "wait for a turn", if i press "Numpad . " the game detect nothing at all and the azerty "." is assumed by the game as ":" as said previously (something odd as what should result from the azerty to qwerty is "<" ) but if i press the ":" key , that should translate into "." in the azerty->qwerty, the game detect it as ":" ?
And for the azerty M key, that in azerty->qwerty lead into ";" , in the game it leads into M ?
From those tests, it looks like there was some azerty support done in the code, but it was made complete, as some azerty keypress lead into qwerty result in the game, while other azerty keypresses lead into azerty results in the game too.
edit as i was writing :
Looking back on the old
Incursion changelogs i found that at version 0.5.9B :
* Fixes to accomodate AZERTY keyboard -- users can now
set a keyboard layout by changing Incursion.cfg; see
comments in that file for more info.
So i think the dev started to made some azerty support but it wasn't complete, explaining why some azerty keypresses seems to result into azerty results, while other result into qwerty ones.