Reply to Re: Code in hit proc
If you don't have an account, just leave the password field blank.
It should be. Taken from DinkC Reference:
"...So any wait(), even a wait(1), makes a script "yield the floor" to other active scripts to allow them time to finish or at least get to their own wait() points before this script is resumed."
So wait(); isn't just a delay, it pauses the script and lets other scripts run their stuff. Wait(1); usually solves quite a few problems with script execution, for example, in cutscenes with screenchanges and screen base scripts.
I can't figure out why wait(30); works in this case, and wait(1); doesn't. Basically, is wait(4); the same as four consecutive wait(1)s or not?
"...So any wait(), even a wait(1), makes a script "yield the floor" to other active scripts to allow them time to finish or at least get to their own wait() points before this script is resumed."
So wait(); isn't just a delay, it pauses the script and lets other scripts run their stuff. Wait(1); usually solves quite a few problems with script execution, for example, in cutscenes with screenchanges and screen base scripts.
I can't figure out why wait(30); works in this case, and wait(1); doesn't. Basically, is wait(4); the same as four consecutive wait(1)s or not?
