Thanks, I'll have to try something like that. That would be a good solution.
I'm also not sure if the issue with the auto-jumping on 'nothing' is because of a faulty reading of its main mechanism -- Basically, it's reading 1 , but should say 0.
It's happening right at the new-cycle frame, I think. But yes that solution should work block a faulty reading if it's just happening for that frame. (I was seeing the cycle-reading be 0 correctly, then the new-cycle frame appeared to read 1, allowing air-jumps)
It was also inconsistent -- Most times it would not lock into that glitch, just sometimes. Would like to confirm it's not from the rough-draft logic, causing that false-reading somehow, too.
Appreciate your insight.