Thanks to the iOS version this should be easy to add: ADOM kept a lot of "global" variables and structures so that loading/creating a new character was impossible because the old values would modify the new character. Since ADOM on iOS has no "quit" option, there now is a routine that resets ADOM to the initial state.

Irrespective of what default behavior would be present if this feature is implemented, I'd like to be able to customize this on adom.cfg. For example, I'd like to keep the current behavior on save (exit) but the new one on quit (go to main menu) and also have one or the other option available in the case of dying.

Added two configuration parameters: Quit_After_Death and Quit_After_Save

The default value for both is "false"; if you set them both to "true" you get the current/old ADOM behavior back.

Is it possible to implement a third parameter for deaths by 'Q'uitting as opposed to deaths by other means?

Sure... how about "Quit_After_Leaving"?

Sounds good to me, though "quit_after_quitting" would be a little more intuitive, if not very elegant sounding. But it doesn't necessarily need to have an intuitive name as long as its effects are explained in appendix B of the manual.

You are right, "quitting" is more fitting.

Implementing this was a little more complicate than expected. A simple "loop" around around the main menu was not enough since some of the global data is modified during the game (e.g. item rarity). We have to store a backup of this data and restore it before the player starts/loads a new game. Additionally a lot of global variables needed to be reset to their original value.

To avoid the strange "Quit after quitting" name, I would call them:

Exit_After_Death
Exit_After_Save
Exit_After_Quitting

Good idea, done.

tl;dr: expect possible strange behaviors after returning to the main menu and starting a new character?

We just found another side effect during testing, but I hope we find all problems before the next Prerelease. :)