|
| 22 Oct 2012 03:42 PM |
I know wait() is the slowest you can make a script wait, but how long is it?
Like if I wanted to something to wait 10 seconds but had something for looks happened before it it waits to long (Like this, as a example
script.Parent.Name = "Lol" wait() script.Parent.Name = "Lul" wait() script.Parent.Name = "Troll" wait() script.Parent.Name = "Lua" wait() script.Parent.Name = "DIE" wait() script.Parent.Name = "JkJkJk" wait(10) workspace.Name.Health = 0
)
(Please note I know that is a random stupid script, Its just a example its not part of something I made xD) |
|
|
| Report Abuse |
|
|
|
| 22 Oct 2012 03:44 PM |
wait() is not the slowest wait possible, it results in a wait about .03 seconds long. The shortest possible wait depends on the speed of the game engine, but if you say something like wait(.001) that will work.
Also, wait() in a local script is solely determined by the LocalPlayer and their changing of Roblox Studio's settings. I suggest always putting a number (This does NOT include 0) inside those parenthesis. |
|
|
| Report Abuse |
|
|
XhymbbQd6
|
  |
| Joined: 22 Jul 2011 |
| Total Posts: 1468 |
|
|
| 22 Oct 2012 03:45 PM |
| wait() I believe is around 0.5 seconds... what your script would do, would change the name so fast nothing would be able to nice besides JKJKJK, and then it waits 10 more seconds and kills them. |
|
|
| Report Abuse |
|
|
|
| 22 Oct 2012 03:46 PM |
That waits 0.15 of a second before the wait(10).
0.03 * 5 = 0.15 |
|
|
| Report Abuse |
|
|
|
| 22 Oct 2012 03:47 PM |
@Source Its just a example. |
|
|
| Report Abuse |
|
|
|
| 22 Oct 2012 03:47 PM |
@Wood
Waiting any shorter a time than 0.03 seconds is impossible because it would lead to the script continuing faster than the game can tell it to.
0.03 is as low as you can go unless you do not wait at all. |
|
|
| Report Abuse |
|
|
|
| 22 Oct 2012 03:50 PM |
http://wiki.roblox.com/index.php/User:JulienDethurens/Essays/Wait_function
NoThx |
|
|
| Report Abuse |
|
|
|
| 22 Oct 2012 03:54 PM |
I read there that it uses the DefaultWaitTime setting. Mine is by default set at 0.029999999999999999
aka, 0.03 |
|
|
| Report Abuse |
|
|
|
| 22 Oct 2012 03:55 PM |
But not everyone's is.
¤ ¤ † K M X D † ¤ ¤ |
|
|
| Report Abuse |
|
|
|
| 22 Oct 2012 03:57 PM |
The game can sometimes run at slightly faster than .03 seconds between game ticks. And your settings only apply to LocalScripts.
But even if your settings are set to .029, some other jokester might come along with it set to 50. If that were in a local script, he could easily exploit the flaws of the game. |
|
|
| Report Abuse |
|
|
|
| 22 Oct 2012 03:57 PM |
But that only applies in LocalScripts.
I do not see why you linked me to that page. It doesn't make sense that wait(0) waits at all because 0 is absolutely nothing. You can't actually wait 0 seconds, unless you didn't actually wait. |
|
|
| Report Abuse |
|
|
|
| 22 Oct 2012 03:58 PM |
| It does not matter. If you call the wait function, you will surely wait no matter what! |
|
|
| Report Abuse |
|
|
|
| 22 Oct 2012 04:01 PM |
No, if you read that essay which you YOURSELF linked me to you would see that it only checks if the time has passed each tick before continuing the script.
Therefore, telling it to wait 0 seconds means it checks and then instantly carries on on the next tick.
But like I said, this is pointless because it does not wait. |
|
|
| Report Abuse |
|
|
|
| 22 Oct 2012 04:05 PM |
Unfortunately, Julien was incorrect in that one bit of information.
Why you getting so angry? qq
Go into Roblox Studio and type this in
n=0 while wait(0)do n=n+1 print(n)end
Do you think that's not waiting? You call the wait function, you wait. |
|
|
| Report Abuse |
|
|
|
| 22 Oct 2012 04:06 PM |
Err, type that in to the Command Bar I mean.
Then compare the speed at which it counts to using wait without any arguments.
|
|
|
| Report Abuse |
|
|
|
| 22 Oct 2012 04:08 PM |
Well that's a predicament.
Something has evidently changed, but that still doesn't make sense. I tested it and it looks like wait(0) and wait() are the same, but that doesn't make sense, does it?
Surely waiting 0 is not waiting at all. |
|
|
| Report Abuse |
|
|
|
| 22 Oct 2012 04:09 PM |
| Do I win cookies yet!?!?!??!!??!!?!??! qq |
|
|
| Report Abuse |
|
|
|
| 22 Oct 2012 04:11 PM |
| If I look back at it, not really. You proved me wrong on a secondary point, but still: wait() aka wait(0.03) is as low as you can go. |
|
|
| Report Abuse |
|
|
|
| 22 Oct 2012 04:14 PM |
A game tick can occur with smaller than a .03 second interval under good game engine conditionssssssssssssssssssssssssssssss
Still, people should get in the habbit of using a number besides 0 while using the wait function, if for nothing else when a local script is used.
k fein no cookies i sad now |
|
|
| Report Abuse |
|
|
|
| 22 Oct 2012 04:16 PM |
But the game has a throttle of 30fps, meaning you cannot go faster than this. UNLESS:
There is or was a setting which allowed you to speedhack as fast as your computer could go. |
|
|
| Report Abuse |
|
|
|
| 22 Oct 2012 04:31 PM |
o well that I didn't know >.>
|
|
|
| Report Abuse |
|
|
| |
|
|
| 22 Oct 2012 04:46 PM |
| Thank you Chop... Wait, didn't I just see you on SFOTHIV? |
|
|
| Report Abuse |
|
|
|
| 22 Oct 2012 05:16 PM |
print(wait(0)) 0.036859219858741 279.89907026768
print(wait()) 0.038513533788262 291.58182579403 |
|
|
| Report Abuse |
|
|
|
| 22 Oct 2012 05:25 PM |
> wait() is not the slowest wait possible, it results in a wait about .03 seconds long. The shortest possible wait depends on the speed of the game engine, but if you say something like wait(.001) that will work.
False, Wait() will wait until the next frame, which is essentially the fastest you can go unless you don't wait at all. |
|
|
| Report Abuse |
|
|