Castle Paradox

[Bagne]

I have a "swap party" script that is triggered by keypress.

It's strange: if you lean on the designated key (c), "swap" gets triggered multiple times (before the first finishes execution) even though the "permit multiple script triggers" bit is set to OFF.

I've tried implementing a makeshift "suspend keypress" by only allowing scripts to run when a certain TAG (51) is turned on.
This doesn't seem to work - I can't imagine why.

My keypress script looks sort of like this:

[TMC]

When a script is triggered, such as an on-keypress, the interpreter checks whether the current script (which, because script are only triggered outside of the interpreter, will always be in the middle of either a wait or one of those very rare commands that cause an invisible wait) is the same as the one that wants to be triggered. If so, "permit multiple script triggers" dictates what will happen. In your case, the current script is swap, and the triggered script is your on-keypress, so the interpreter doesn't see the problem and they pile up.

What you are doing is basically the correct way to prevent double triggering of scripts. However, you should move set tag (51,on) inside the if, otherwise any other keypress will reset the tag! I'm guessing this is your problem, because everything else is right.

You know... you can write key:c instead of 46. I know, I'll remove the table of scancodes from the plotdictionary.
_________________
"It is so great it is insanely great."

[Nepenthe]

EDIT: TMC beat me to it (and provided a better answer!)

I think you want to check that tag by itself before you do any keyispressed stuff. This is roughly what my keypress script looks like:

[Bagne]

Yes, moving the "resume swap" worked - thanks!

One last question: neither typing "key:c" or "c" works for me.
_________________
Working on rain and cloud formation

[Pepsi Ranger]

[Bagne]

Bingo!
_________________
Working on rain and cloud formation