Yep, it's a compromise. The newer bindings no longer respect your personalized bindings as there were many problems with that (e.g. pressing : missed a key, you could define invalid bindings by omitting certain commands, etc.).

It might not be optimal but I'm not sure if there's a better solution in the foreseeable future :-/

Given the recent push to make the game more friendly for newbies, wouldn't this be an extreme priority? This bug pretty much destroys any ability to have custom key binds...

Newbies don't use custom key bindings. No tester I ever played with so far even came close to feeling the desire to rebind keys. And then they probably wouldn't think about editing a text file. You have a wrong perception of newbie problems, believe me :-)

I'll have to disagree here. Pretty much anybody that I know that plays PC games (myself included) will immediately look in a new game's option menu to remap keys, especially keys we realize we don't like as we're playing through the game initially. In the current state of PC game dev it's almost unheard of to not have remappable keybinds in-game, but given that's a lot of effort to implement in ADOM at this point, being able to remap keys in a file is a decent workaround. That said, if the remappings in that file aren't actually taken into account in the game, there's not much point to using it.

I find it interesting that none of the testers have asked about remapping keys, given that's the first thing I do on any new game (let alone roguelike) I play. I wonder what they would think about the mind-crafting key (ctrl-i), should any of them happen to try mindcrafter =P.

(P.S. Hope I'm not coming off poorly, I love this game and your dev work, but I think some type of remappable key system that works is important to the reception of this game.)

Maybe the combination is the point: Currently there is no UI remapping available and thus people stop caring about it. That's at least what I observe in our UI/UX lab: They just don't care and learn the ADOM keybindings. Unless that changes I'll keep the priority very low. Data trumps opinion ;-)

And yes, I do agree in that a UI-based remapping would be awesome and useful to have - but it's too much effort right now. Maybe in a couple of months...

(and hopefully I do not appear rude... I'm just trying to distribute our limited resources to the best of my ability ;-) )

A small suggestion that ought to fix this issue as a minor work-around for now, at least for vi-keys users: to my knowledge, hjklyubn is completely unmapped in "ask for a position" prompts. Would it be possible to simply map them as alternative keys in addition to 123456789? That should at least allow vi-keys users to still be able to play properly.

I don't understand this argument. Position prompts asks for a position -- you are saying that a new player would first accidentally press a button to move the cursor, then *also* press the "confirm" key? How is this different from fatfingering a number?
Keep in mind that I am referring to *position* prompts here, not *direction* prompts. Those already respect your remapped directional keys as input (unless this was changed in a later release ruining direction remapping further?).

I misread and thought that this applied to directional prompts as well. Rereading the OP it's just picking positions, so there's no danger in having undocumented behavior, and I withdraw my objection.

Not sure if this is related but if I am using the noteye version with VI keybindings, am I affected by this bug? I am a newbie *but* I'd very much like with a cherry on top to use VI keybindings *and* to also have a key binding for look, farlook, and any other command that might be superseded by the VI movement keys. Thank you

Are you saying there is a new in-game option for VI keybindings? If so, I have no idea what they bind those commands to, but surely they do bind them?

Otherwise, you can look at the keymap I created for vi-keys on an older version where getpos prompts still worked fine (link in OP). They're NetHack-inspired since I'm a NetHack player, but you can change them if you wish -- but either way, it gives an exhaustive list of the keybinds in comments on top. Nothing important is left out -- I've ascended games using it.

You still have access to the commands look, target / throw, etc. when using vi keybindings with ADOM because you remap those keys. This bug is that ADOM does not respect those keybindings in certain commands and requires you to use num-keys (which you can of course do using the number row, it's just really annoying). You can see a list of which commands work or don't work @ https://www.adom.de/forums/project.php?issueid=6543

In addition to FIQ's excellent work above, I have a vi-keys setup based more on DCSS - https://pastebin.com/raw/DQL5DxWY

Oh, I see, thanks for the explanation and config files