48: you're much better off doing a state machine. See flags below, only set the current state in a number, add the number as a condition to the events that can only happen in the current state. Change said state within the event.
Well, that's exactly what I'm doing, I just tried to simplify the whole thing to make my point about timers clear. That it'd be really cool if we could create a timer and access and reset that specific timer after it's been created and run.
The timer is necessary for a couple of things, mainly setting back gvs that then trigger actions again. I just wanna be able to extend the timers time after it's been created.
[quote:29yhjtap]49: use flags. 1 to enable, 0 to disable.
+On control "left"
+global('movementEnabled) equals 1
Ah, that's clever, yeah. Still, it'd be nice being able to have actions where we could deactivate keys until they're being activated again. Your solution will work, but it'll also mean that the 'movementEnabled' condition will have to be queued for every single control event.
And if I only want to deactivate a specific button at a specific moment, I'll have to create a gv just for this one action, which is sorta inefficient.