dMZX Forums: Label caching compat fix only applies on first test -> MegaZeux Bugs -> Tracker

In MegaZeux versions 2.80 through 2.83, whenever a label was immediately followed by a SEND "ALL" to the same label, that send jumped to a different line than intended in the Robot that initiated the send due to a quirk in label caching (one past the command after the label, but only when the two lines are immediately adjacent). 2.84 changed this to the less buggy pre-2.80 behavior (the initiating Robot jumps to the label when unlocked even in this case) as a result of changing label caching and applied a compatibility fix. However, this fix seems to only apply on the first editor test, failing on subsequent tests. This resets when a new world is loaded, even if it's the same world.

This fix was applied because Thanatos Insignia (DoZ ver) relied on it during level transition, but there's thankfully an easier test case. Secret Demo relies on the old behavior when talking to uncleben on the #ascorp_mzx board.

Behavior dates back to 2.84.

Updating status to: Confirmed

When __TEST.MZX is reloaded, the robot labels are immediately cached in 2.84+ form (as __TEST.MZX is a 2.93 world file), then the world version is reverted to 2.83. This doesn't affect the labels.

This could be fixed by either recaching every robot's labels or by moving the compatibility hack into the send implementation (rather than the cache). It will probably also be fixed automatically by moving label caching to compilation in 3.00.