Difference between revisions of "0001"
Jump to navigation
Jump to search
m |
|||
Line 3: | Line 3: | ||
| description = Stops the execution of a [[thread]] | | description = Stops the execution of a [[thread]] | ||
| p1 = Time to wait (in milliseconds) | | p1 = Time to wait (in milliseconds) | ||
− | | game = | + | | game = [[GTA 3]], [[Vice City]], [[San Andreas]] |
+ | | native = [[WAIT]] | ||
}} | }} | ||
This opcode stops an execution of the thread for specified amount of time in ms. In both the [[Mission Builder]] and [[Sanny Builder]], you can type '''wait''' instead. A parameter value of 0 (wait 0 ms) means that the thread will regain focus as soon as possible, whereas values greater than 0 denote the minimum time span that has to go by before the thread is revisited. A wait is required for almost all [[Create a thread#Loops|loops]]. | This opcode stops an execution of the thread for specified amount of time in ms. In both the [[Mission Builder]] and [[Sanny Builder]], you can type '''wait''' instead. A parameter value of 0 (wait 0 ms) means that the thread will regain focus as soon as possible, whereas values greater than 0 denote the minimum time span that has to go by before the thread is revisited. A wait is required for almost all [[Create a thread#Loops|loops]]. |
Revision as of 07:56, 14 January 2010
{{{games}}}
This opcode stops an execution of the thread for specified amount of time in ms. In both the Mission Builder and Sanny Builder, you can type wait instead. A parameter value of 0 (wait 0 ms) means that the thread will regain focus as soon as possible, whereas values greater than 0 denote the minimum time span that has to go by before the thread is revisited. A wait is required for almost all loops.
Keywords
wait, thread