-
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!
Timer Elapsed event
- Status
- Joined
- Oct 24, 2012
- Messages
- 6,545
i think they are handled differently. i dont believe u can destroy a triggerregistertimer.
also y use event single ?
if its just a single event u can start a timer in the init trigger and then do ur actions when timer runs out. this way u can destroy it and u may not need the trigger.
also y use event single ?
if its just a single event u can start a timer in the init trigger and then do ur actions when timer runs out. this way u can destroy it and u may not need the trigger.
- Joined
- Nov 11, 2006
- Messages
- 7,777
It uses an internal timer similar in accuracy/behavior as CreateTimer(), but you do not have access to it. Simple test:
It will show "null", therefore calling
JASS:
function X takes nothing returns nothing
if GetExpiredTimer() == null then
call BJDebugMsg("null")
else
call BJDebugMsg("not null")
endif
endfunction
function Init takes nothing returns nothing
local trigger t = CreateTrigger()
call TriggerRegisterTimerEvent(t, 3, false)
call TriggerAddAction(t, function X)
endfunctionDestroyTimer(GetExpiredTimer()) will have no effect (confirmed by a test I just ran).- Status
Similar threads
- Locked
