Read-only archive of the Armageddon Games Forums Archive (2000–2026) · About this archive

777: Singular Flag bug.

5 replies · 1,589 views · Started 28 April 2008

It might have to do with script integration or inherent singular flags. But anyway:

You can bypass a screen with singular triggers on it by triggering one trigger, leaving the screen, and re-entering; even when the screen is set it to "All Triggers->16-31." To my knowledge, this didn't happen before. My setup is integrated with the spin checker script using inherent singular flags.

No, this is when you DIDN'T activate every trigger; you leave the screen, come back and then all the triggers are triggered, despite the fact that I have "All Triggers->16-31" set

I just clarified the ZCWiki. But this is the bug:
It appears that you can cheat the system by leaving the screen with one trigger activated, probably because it sets the permanent screen state even with singular flags on. This probably isn't known immediately because the temporary screen state isn't set per se. I could probably counter this with the script I'm using, though.

beefster09 wrote:I just clarified the ZCWiki. But this is the bug:
It appears that you can cheat the system by leaving the screen with one trigger activated, probably because it sets the permanent screen state even with singular flags on.

So, here's what's happening:
i) The Triggering Combo changes.
ii) The other Trigger Flags do not change (because they are flagged with "Singular"😉.
iv) The "Secrets" screen state is set.

And, when you re-enter the screen:
i) If the "Secrets" screen state is set, then all of the flags are changed.

If you consult the wiki, you'll see that the way to prevent the "Secrets" state from being set that easily is to use the "All Triggers->Perm Scrt" screen flag. "All Triggers->16-31" is concerned only with preventing "Secret Tile" flags from being triggered.

Result: not a bug!

'Not A Bug' thread moved from quarantined to exterminated. Dark Nation (or other developer), how am I doing? Reply only in one of the threads I moved.