Pre 2023.09 Scenario issues

[TehAwol]

When using certain old React scenarios (from before ~2023.09) several issues occur:

• Certain triggers are corrupt which can lead to a broken initial state (E.g. MSG mailbox phase 1 empty)
  • This can be fixed by resaving each trigger variable and restarting the scenario. This does provoke changes on export in the variables order and ids
• Trying to instantiate these scenarios as trainer does nothing and leads to an "Error: 413 Message too big"

[xgo-work]

Tried with a very simple case with one variable incremented by a single trigger at game start.

• ORIGINAL => works fine. Real game instance as well
• COPY (in lobby without any reset) => scenario has to be reset once for trigger to work. But instanciated game works fine
• PATCHED from export => scenario has to be reset once for trigger to work. But instanciated game works fine
• LOADED from wgz export => scenario has to be reset once for trigger to work. But instanciated game works fine

[xgo-work]

When patching to a copy of the original scenario, the following diff happens

GameModel
Trigger Serialization TEST (3)
items
trigger1 - trigger1
dependencies
TransitionDependency:1017811:Afa53c
variableName
n
scope
SELF

TransitionDependency:1016671:WprkHk
variableName
n
scope
SELF

=> The TransitionDependency is adapted to the new variable, that seems correct, although a bit surprising. In the sense that the abstract dependency of a trigger to a variable should not vary from 2 identical copies of a scenario.

[TehAwol]

Closing issue.

Duplication error provoked by developer error