How could a scenario check on its multiplayer id?

[nickanc]

Hello! Probably the question has an easy solution that for some reasons I can't see.

I am currently working on Orocia Random Mod in an attempt to macro the functioning of the map so that adding new maps for that game is easier.
And I am puzzled by the fact that picking the add-on as it is, changing the name of the id under the [multiplayer] tag in the scenario, for instance change

Code: Select all

[multiplayer]
	id=Orocia_Random_Ageless_Mod

to

Code: Select all

[multiplayer]
	id=Orocia_Random_Ageless_default_Mod

the game goes nuts, it seems not even the options of the scenario are followed. I was not able to understand why, but probably I lack a full background.

So my question is: in general, how could a scenario check on the value of its multiplayer id? Isn't it relevant just to distinguish a scenario from another or is it used elsewhere?

[Ravana]

Spoiler:

Lua can read current scenario id. However, orocia does not use that.

So, scenario id should be safe to change still.

However, I could replicate your situation. Looking.


Debugging revealed that difficulty setting is not saved.


I see that [options] id has to be unique across all scenarios that have ever been used, enforced by preferences file
this means that scenario may never be assigned new id

Known 1.12 bug, possible with 1.13.7.

[nickanc]

Spoiler:

Lua can read current scenario id. However, orocia does not use that.

So, scenario id should be safe to change still.

However, I could replicate your situation. Looking.


Debugging revealed that difficulty setting is not saved.


I see that [options] id has to be unique across all scenarios that have ever been used, enforced by preferences file
this means that scenario may never be assigned new id

Known 1.12 bug, possible with 1.13.7.

I suspected there were something with the ids of the options but I was unsure. I'll try with 1.13.7, thank you.