I run, though I did not write the supporting scripts for, a public ADOM SSH-accessible server. I have been investigating inserting 1.2.0xx into the current ecosystem.

The server wrapper allows players to choose between ADOM 1.0.0 and 1.1.1. It keeps the profile data of different versions separate by making ~/.adom.data a symlink to a version-specific directory based on which version of ADOM the user has selected. I guess ADOM_HOME does this on Windows, but that doesn't work on Linux and I don't see an equivalent.

The normal way to share a HISCORE file with other users on the system is to create a file named /etc/adom_ds that just contains the desired folder for the .HISCORE file to live in. On the server, the high score files for different versions are kept separate by - as far as I can tell - a binary patch to the ADOM executables that cause each version to look for a different /etc/adom_ds* file.

I do not have the technical ability (yet?) to replicate the binary patching, so I'm looking at being able to enable 1.2.0 on the server by just using the default /etc/adom_ds file and replicating the symlinking for the new version, but if (when?) 1.3.0 comes out I will have trouble with the HISCORE file and may have to choose between 1.2.x and 1.3.0.

So my RFE is twofold:

(1) Add a command-line switch to the ADOM executable that allows users to specify their desired .HISCORE file location, or a way to tell ADOM to look at a specific adom_ds file

(2) Add a command-line switch to the ADOM executable that allows users to specify their desired profile folder.