• Listen to a special audio message from Bill Roper to the Hive Workshop community (Bill is a former Vice President of Blizzard Entertainment, Producer, Designer, Musician, Voice Actor) 🔗Click here to hear his message!
  • Read Evilhog's interview with Gregory Alper, the original composer of the music for WarCraft: Orcs & Humans 🔗Click here to read the full interview.
  • The Hive's 22nd Icon Contest: Creep Abilities is now concluded, time to vote for your favourite set of icons! Click here to vote!
  • ✅ The POLL for Hive's Texturing Contest #34 is OPEN! Vote for the TOP 3 SKINS! 🔗Click here to cast your vote!
  • ✅ The POLL for Hive's Techtree Contest #20 is OPEN! Vote for the TOP 3 FACTIONS! 🔗Click here to cast your vote!

call TriggerSleepAction(0.1)

Status
Not open for further replies.
well, it is not exactly dangerous but not very good to use either.
I believe it has inaccuracy. It approximately waits 0.27 more than given value.
It also doesn't stop when the game is paused, so if someone lags it continues to count down.
There might be more downsides to it than I remember. People will usually recommend timers instead of TSA.

Using it during map initialization should be safe in most cases. It boils down to how you use the function.
It should be fine to use if you don't mind it being somewhat inaccurate.
But I don't really see the need to use it for your reason as they should initialize in order. Unless you have a special case.
You also have the option to use Elapsed Time instead of Map Initialization.
 
Last edited:
Status
Not open for further replies.
Back
Top