[Trigger] Does this make sense?

[Veldris]

So i was wondering if i could Destroy special effect like this.

• SpecialEffect Destroyer
  • Events
    • Time - Every 60.00 seconds of game time
  • Conditions
  • Actions
    • For each (Integer A) from 1 to 25, do (Actions)
      • Loop - Actions
        • Special Effect - Destroy (Last created special effect)

to remove all Special effects from the Map coz my map use alot of Special effect and i can't seem to find a solution for that.

 

[Jampion]

no, everytime a new special effect is created (Last created special effect) gets overwritten.

Your trigger would try to destroy the same special effect 25 times.

You need to store your special effects in variables or hashtables and destroy them later. A lot of special effects can be destroyed instantly, if you only need their death animation.

 

[Tasyen]

A lot of special effects can be destroyed instantly, if you only need their death animation.

Also valid if the used model has only 1 animation. Examples: Thunderclap, blizzard...

 

[Veldris]

no, everytime a new special effect is created (Last created special effect) gets overwritten.

Your trigger would try to destroy the same special effect 25 times.

You need to store your special effects in variables or hashtables and destroy them later. A lot of special effects can be destroyed instantly, if you only need their death animation.

How do you want me to store them as Variables there's alot of SpecialEffects

 

[Lizreu]

How do you want me to store them as Variables there's alot of SpecialEffects

Unfortunately, that's on you to figure it out. You can store them in an array. Arrays can handle 32768 elements in version 1.29+, and 8192 in prior versions.

Alternatively, like Jampion said, you can store them in hashtables. Unfortunately, there's not really a way around this if you want to destroy them.

 

[Veldris]

Unfortunately, that's on you to figure it out. You can store them in an array. Arrays can handle 32768 elements in version 1.29+, and 8192 in prior versions.

Alternatively, like Jampion said, you can store them in hashtables. Unfortunately, there's not really a way around this if you want to destroy them.

Thanks for telling me that noted for Future.