Removing Destructables

[prismpirate]

Is there a way to make a destructable have a timed life, similar to units?

 

[Rainther]

By adding timer that will eventually remove it, yes.

 

[Jesus4Lyf]

Trigger sleep action, then remove?

"Execute" a function that does this.

IE:

func doyourremove takes some destructible and a real returns nothing
call TriggerSleepAction(yourreal)
call RemoveThingie(dest)
endfunction

//Use:
call doyourremove.execute(dest,real)

 

[prismpirate]

If I created multiple destructables using a loop, then TriggerSleepAction(sometime) will cause the loop to take a long time to run. Is there such thing as a destructable group?

 

[Rainther]

I believe their are systems out there for it. I assume you wish to destroy all at the same time?

 

[prismpirate]

I'll post my trigger here:

scope sprout initializer Init
    globals
    private constant integer spellid = 'A01U'
    endglobals
    private function sproutaction takes nothing returns nothing
        local real x
        local real y
        local real theta = 0
        local destructable lastcreateddestructable
        loop
            exitwhen theta > 315
            set x = (Cos(Deg2Rad(theta))*200)+GetUnitX(GetSpellTargetUnit())
            set y = (Sin(Deg2Rad(theta))*200) +GetUnitY(GetSpellTargetUnit())
            set lastcreateddestructable = CreateDestructable(treetype,x,y,0,1,1)
            set theta = theta + 45
        endloop
    endfunction
    private function sproutcondition takes nothing returns boolean
        return GetSpellAbilityId() == spellid
    endfunction
    private function Init takes nothing returns nothing
    local trigger t = CreateTrigger()    
    local integer index = 0
    loop
        call TriggerRegisterPlayerUnitEvent(t, Player(index), EVENT_PLAYER_UNIT_SPELL_EFFECT, null)
        set index = index + 1
        exitwhen index == 11
    endloop
    call TriggerAddCondition(t, Condition(function sproutcondition))
    call TriggerAddAction(t, function sproutaction)
    endfunction
endscope

Basically its Dota's Furion's Sprout. I've managed to create the trees, now I need to remove them x seconds after they are created

 

[Tom Jones]

Do as Jesus4life said, it's by far the easiest.

 

[Jesus4Lyf]

If I created multiple destructables using a loop, then TriggerSleepAction(sometime) will cause the loop to take a long time to run.

Read my code more carefully. Calling with .execute(... starts a new thread. Meaning your code will execute immediately and stuff. (But the stuff after the wait will wait in its own thread to fire.)

 

[prismpirate]

Thanks a lot. I didn't know about .execute. vJass tutorials never talked about them. Will try to +rep you sometime later, I've maxed mine out at the moment.

 

[TriggerHappy]

You could try this;

http://www.wc3c.net/showthread.php?t=105456

 

[Jesus4Lyf]

No need for his map to break on patch 1.24 just to remove a tree.

The solution he has now is suitable.

 

[TriggerHappy]

No need for his map to break on patch 1.24 just to remove a tree.

The solution he has now is suitable.

How will it break on patch 1.24?

 

[Flare]

How will it break on patch 1.24?

The return bug is being 'fixed', isn't it?
I haven't been keeping up-to-date with the new patch details, but I think that was mentioned somewhere

 

[TriggerHappy]

My script doesn't contain the return bug.

 

[Jesus4Lyf]

It requires TimerUtils which has it.

Therefore, his map must break on patch if it uses your script.

Stupid argument, completely off topic anyway as my suggestion was much more suited to what was asked.

 

[TriggerHappy]

Just to make things clear, im pretty sure vex made a hashtable version for TimerUtils which will work for the new patches.

 

[Jesus4Lyf]

>Therefore, his map must break on patch if it uses your script.
In other words, when the patch is released. In other words, when WC3 moves from 1.23 to 1.24. TU releases can only work on either, not both. I'm really surprised I needed to clarify this.