Divine Storm

[Moderator]

19:31, 5th Jul 2015
Maker:

The spell does not support more than one caster
casting the spell at the same time
Look for tutorials how to make it MUI or ask for help
in Triggers & Scripts subforum

 

[btdonald]

Make it MUI ^^!~

http://www.hiveworkshop.com/forums/...orials-279/visualize-dynamic-indexing-241896/

 

[PAZBoy]

Make it MUI ^^!~

http://www.hiveworkshop.com/forums/...orials-279/visualize-dynamic-indexing-241896/

I don't know MUI

 

[btdonald]

The link I give you teach you how to make it MUI ^^!~

 

[Andser]

- Don't use waits, only if you are doing something that really needs them (like cinematics).
- Instead of

• Set Life - Life of Picked Unit -100

use

• Unit - Cause (Caster) to damage (Target), dealing (Damage) damage of attack type (Spell or whatever) and damage type Normal

No one will get credits for killing a unit with Set Life, thats why.
- Also, you can add the casting unit to a group (lets say DStorm_Casters) and then in the periodic trigger

• Unit Group - Pick every unit in DStorm_Casters and do (Actions)
  • Loop - Actions
    • Periodic Actions here

(^ but replace Caster with Picked Unit)

• Do nothing

^ this does exactly what it says, if you ever coded in any other language (C, Pascal, Python, Java etc...) you would know it isn't needed to tell the program to do nothing, because he will do nothing if there's nothing
I checked your profile, you've got many other rejected/unacceptable resources, there are many guide on Hive for triggering, but as btdonald said, try to make it MUI.
(I know, the conditions on Hive are tough, I also got many unaccepted/awaiting update resources ^^, but if you are really into triggering I can help you a bit)

 

[Squiggy]

To make this easily mui, you could do:
Unit - Add Expiration timer
to your hammer dummy so it kills itself without leaving a leak

Add a custom value to your dummy unit (like 56) and check for the value in your conditions, like Pick every unit in 700,700 from POINT whereas POINT is a variable, set to pick the position of every unit with the custom value (of 56 here) so your variables don't get overwritten.

As for the TurnOn-Off part; check for the amount of units on your map having such a custom value and if the amount is 0 (zero/none), turn off the trigger- respectively turn it on when the spell is being cast.

Also, leave out the Do Nothing, do
Custom script: call udg_RemoveLocation() and others, as explained here to get rid of leaks.

Ah, the joy of spellmaking until you notice coding them in GUI is tedious...

 

[SayazEmil]

well done

 

[IcemanBo]

Hello.

Please read the http://www.hiveworkshop.com/forums/rules-information-710/spell-submission-rules-230362/.

Spells must be useful. Extremely simple, cinematic, or other spells which have no place in a game will not be accepted.

The spell/system must be leakless.

Spells must be MUI and MPI

Users have to be able to configure your spell to their liking.

Spells and systems must have decent importing instructions

This concept is by far too simple. I don't see this being able to be approved.

Rejected for now. Ask in forum if you have question about triggering.