Ah right. So I didn't even need to convert everything to timers then
Lua allows a user implementation of Wait using coroutines, times and lambas (as TriggerHappy has mentioned). This has the huge advantage that your program flow can remain exactly the same just with your TriggerSleepAction waits replaced with the coroutine based waits. This avoids all the complexities of tracking state that JASS has when using timers. Lua also does this quite efficiently, possibly more so than JASS due to the exclusive use of built-in language features to manage the state rather than hashtables, indexers or other such systems.
function xxx()
<part 1>
local t = CreateTimer()
TimerStart(t, 10, false, function()
<part 2>
TimerStart(t, 10, false, function()
<part 3>
end)end)
endYes you start a timer and in its callback function you get the coroutine to resume. The callback function is a lambda which retains a copy of some of the local state allowing it to know which coroutine to resume. The creation of the timer, callback, starting and resuming could all be turned into a single function call usable inside any coroutine which fulfils the style of traditional TriggerSleepAction wait.
function wait(howMuch: number) {
const timer = new Timer();
const co = coroutine.running();
timer.start(howMuch, false, () => {
coroutine.resume(co[0]);
});
coroutine.yield();
timer.destroy();
}
const co = coroutine.create(() => {
print("hello");
wait(1);
print("world");
})
coroutine.resume(co);
For timer based systems the recommended approach is to use a mapping data structure such as hashtable. You can then map data to the handle id of the timer so that you can retrieve that data again when the timer expires by getting the expired timer's handle ID. This principle was used all the way back with the handlevars system, although hashtables are now much more efficient at it.
Ok, all of not create a lot of variables.
Special Effect - Create a special effect
Set Effect = (Last created special effect)
Trigger - Run Remove Effect <gen> (Ignoring conditions)
Remove Effect
Events
Conditions
Actions
Custom script: local effect tempEffect
Custom script: set tempEffect = udg_Effect
Wait 2.00 seconds
Custom script: set udg_Effect = tempEffect
Special Effect - Destroy Effect
I've never once experienced an issue with using something like that. Sure, it's not as precise as using timers, but it's hardly noticeable.But what can I do in case I use the trick of remove a effect after a time because for that you must do
Because I can't use local timers in this case.
Actions
Special Effect - Create a special effect attached to the chest of (Triggering unit) using Abilities\Spells\Human\DivineShield\DivineShieldTarget.mdl
Set Variable SFX_Duration = 1.00
Trigger - Run SFX Destroy <gen> (ignoring conditions)
Actions
Custom script: local effect sfx = GetLastCreatedEffectBJ()
Wait SFX_Duration seconds
Custom script: call DestroyEffect(sfx)
Custom script: set sfx = null
In the first trigger, if there's nothing after creating the effect what is the point of creation another one to destroy the effect? Can do it all in one trigger for fully optimization. The duration variable seems questionable. Also can use the shadowing global variable trick.I've never once experienced an issue with using something like that. Sure, it's not as precise as using timers, but it's hardly noticeable.
Also, you can optimize it and add more control:
That's just an example on how to use it.
Actions
Set Variable SFX_Duration = 2.00
Unit Group - Pick every unit in (Units in (Playable map area)) and do (Actions)
Loop - Actions
Special Effect - Create a special effect attached to the overhead of (Triggering unit) using Abilities\Spells\Undead\AbsorbMana\AbsorbManaBirthMissile.mdl
Trigger - Run SFX Destroy <gen> (ignoring conditions)
) works perfectly.
It can be, thanks.
