Adding new menus to MENUDEFS without overwriting

[Kyle873]

Simply, when one loads two different mods that modify the OptionsMenu node, the mod loaded last will take over and overwrite the previous menu's definition. Therefore, it's impossible to load two mods with MENUDEFS modifying the said OptionsMenu node without blocking access to one of the menus. At least, not without frankenstitching the MENUDEFS together or some such.

What I'm asking for is a simple keyword or method to simple tell the MENUDEF to add a new menu to the already existing OptionsMenu node (or any other if necessary/needed) so that these types of conflicts would no longer occur.

In this example case, I'm referring to Doom RPG and Droplets, both of which use menus for settings adjustment, but only that which is loaded last will take precedence over the menu modification.

[Nash]

Yes x 0x7FFFFFFF

(TBH I feel it should have been designed additively in the first place :S)

[Ed the Bat]

I wholeheartedly support this suggestion.

[Lord Misfit]

Agree with this too. While I've not run afoul of the issue yet, I'm sure I eventually will, and knowing I wouldn't need to worry about this at all would be great.

[Enjay]

It would certainly have to be optioned with a keyword or something. Otherwise, how could a mod alter existing menus to remove or move items? (This, of course, isn't usually desirable but it can be for stand alone mods/games.)

[Graf Zahl]

added

[Nash]

Here's how to use this, in case anyone is wondering.

In your MENUDEF, simply add this

Code: Select all

AddOptionMenu "OptionsMenu"
{
    // Your custom menu and widgets go here
    // It will be appended after the built-in OptionsMenu
    StaticText "My Custom Options"
    Slider "My Custom Slider", "cl_custom_cvar", 0, 20, 1
}