Chat
Discord
you're all wrong, wait 0 isn't half a frame, 'nor is it 1 frame and wait 1 like 2 frames... wait 0 is abit more tricky
when you use a wait 0, in that frame the game runs through it normally, calculating all the bdys and itrs and stuff, but after that, it already sets the frame to the 'next' value in the exact same cycle, which actually causes the game to NOT show f.e. the pic you used for the wait-zero-frame because at the end of the calculating cycle it's already set to the next frame... the game basically kind of skips the wait: 0 frame...
though, if you use two wait 0's after eachother, in the first cycle, the first one gets calculated, then changes to the second one, but due to the game only doing one cycle per char, the second one is not instantly skipped, so you can actually see the pic of the second wait 0 frame... the same thing happens if the first frame of a special attack or something is a wait 0, because the player input is calculated After all the frame stuff, it would have only calculated the previous frame, the one which had the hit_something in it, but not actually the first one of the special attack (this is also the reason why opoint doesn't work in the first frame of a move)
hope you could understand that, I'm not good at explaining such stuff, but that's how it works
tl;dr -> use wait 0 as first frame of an action or after another wait: 0 and it'd show as 1 frame, use it between other frames and it'll not show atall and be skipped instantly (bdys and itrs and stuff would still work though)
when you use a wait 0, in that frame the game runs through it normally, calculating all the bdys and itrs and stuff, but after that, it already sets the frame to the 'next' value in the exact same cycle, which actually causes the game to NOT show f.e. the pic you used for the wait-zero-frame because at the end of the calculating cycle it's already set to the next frame... the game basically kind of skips the wait: 0 frame...
though, if you use two wait 0's after eachother, in the first cycle, the first one gets calculated, then changes to the second one, but due to the game only doing one cycle per char, the second one is not instantly skipped, so you can actually see the pic of the second wait 0 frame... the same thing happens if the first frame of a special attack or something is a wait 0, because the player input is calculated After all the frame stuff, it would have only calculated the previous frame, the one which had the hit_something in it, but not actually the first one of the special attack (this is also the reason why opoint doesn't work in the first frame of a move)
hope you could understand that, I'm not good at explaining such stuff, but that's how it works
tl;dr -> use wait 0 as first frame of an action or after another wait: 0 and it'd show as 1 frame, use it between other frames and it'll not show atall and be skipped instantly (bdys and itrs and stuff would still work though)