18th Apr 2016

Review:

Very simple in concept and coding. The code is leakless and MUI.

The knockback is done poor and eventually bugs in corners or in reach of unpathable terrain tiles.
I can strongly recommend Bribe's GUI Knockback 2.5D.

Troubleshooting:

• The dummy death event trigger is not required. Can't raise, Does not decay is all you need.

Review changelog:

1. -

here is the Video

hey, this is just a quick look
- put the dummy trigger in different category
- use Map Initialization for constant ryugan
- give explanation to each variable in the constant ryugan
- use real for timer variable so that you can decrease it by 0.03
- you leaked temp point002, put the RemoveLocation inside the pick action
- store picked unit into a variable
- store main ability into a variable
- give instruction how to import your spell

will add more soon

hey, more additions: (don't take this seriously )
- you dont need to turn on the loopn on each cast
- store last created unit into a variable
- there is my mistake above, just delete the dummy trigger (unecessary)
- create the sfx using trigger so that user could configure it
- actualy there still more but just fix those above first

thx for the advice..
but if i don't put the dummy trigger it will have death sound that is very noisy

- store picked unit into a variable <-how to do this?
i mean is it possible just to like
set unit xx = picked unit
cause is unit group isn't it?
- store main ability into a variable
just wondering what does this do?

- create the sfx using trigger so that user could configure it
not sure understand


i'm still beginner in spell making so
thank you for helping me
just updated (haven't put instruction because i have no time) (just a quick fix)

i don't want to update the whole post yet cause is not done yet (not even test if it works after the fix)

and is this MUI?
please if can check it for me

Also, for the love of Christ, remove the imports from the map. They add nothing to the spell but kilobytes.

I disagree with that this time Magtheridon96, it Is pretty much 50% of the spell. Blademaster wouldn't fit this, though illidan has a slight chance too.

It's not about fitting in or not. It's a needless addition that increases file size.
I often recommend an alternative to this: Link to the model in the description so map size is reduced.

For spell effects, it's fine, but for the test hero?

So, if the spell effects were not hero animations, you would allow imports?..

Yes. Because those are actually part of the spell.
The test hero used in the map that users are only going to use to try out the spell a few times is not part of the spell.

Spell submission rules:

No overloading the testmap with bulky, unneeded custom models and icons. If you really do need to use a lot of imported content, link to it in your description.

Click to expand...

Spell is more contest like, than some general type.
It fit this model perfectly fine and I like it.
Maybe you could make exception here, as long as it passes all other scripting rules.

epix review from maghter o0

It's not a rule we enforce anyway.
It's just one of those "by the way" things.