wait () command in Titan Two...

[antithesis]

Titan One's wait command peaks at 4000 ms. They can be stacked, but at the expense of bytecode.

What will be the limit on wait (or the equivalent command) on Titan Two?

[bonefisher]

Seen the info around here somewhere but can't find it. I believe there is no limit what was said. Take a look it is in here somewhere!

[Vendetta]

He states it here; http://www.consoletuner.com/forum/viewtopic.php?f=23&t=3417&p=27135&hilit=4000ms#p27135

"Titan Two is not limited to the 4000ms maximum for time measures

[J2Kbr]

correct, the wait statement, on the new scripting language, can go from 1ms to 32767ms. A wide range that can cover any requirements.

[antithesis]

correct, the wait statement, on the new scripting language, can go from 1ms to 32767ms. A wide range that can cover any requirements.

Thanks for the confirmation, I can definitely use 30 secs of that

Does it also apply to get_ptime () ?

Here's the reason I'm curious - viewtopic.php?f=6&t=4422&p=33034#p33034

To get this snippet to work, get_ptime (15000) would need to be possible. The follow-up event_press (CROUCH) could happen anywhere from 5 seconds to 15 seconds later, depending on manual or automatic respawn (Destiny sometimes checks for an available respawn location).

[pablosscripts]

I was actually just about to ask this question. 32767ms is heaps!

[J2Kbr]

Does it also apply to get_ptime () ?

Not exactly. the equivalent to get_ptime on Titan Two is time_actived(), it returns a 32-bit unsigned int, which can measure the "activated time" from 0 to 4294967295ms, or 49 days.

Also, we have - for Titan Two - a new function called time_resting(), which measures for how long a button is in the resting position - here it can track up to 49 days too.

[The_Rabid_Taco]

49 days! Holy poop on a stick! Now that is tracking! Oh, I can already see the new scripts, left to run for days on end, except my playstation is never left alone for that long. LOL

[antithesis]

Does it also apply to get_ptime () ?

Not exactly. the equivalent to get_ptime on Titan Two is time_actived(), it returns a 32-bit unsigned int, which can measure the "activated time" from 0 to 4294967295ms, or 49 days.

Also, we have - for Titan Two - a new function called time_resting(), which measures for how long a button is in the resting position - here it can track up to 49 days too.

I think 49 days should cover it...just

[bonefisher]

Man I really needed 50 days out of this.....lol!