Soul Split

[Moderator]

12th Dec 2015
IcemanBo: Too long as NeedsFix. Rejected.

22:57, 7th Aug 2012
Magtheridon96: Instead of using custom values, you should use some other form of data storage.
Try dynamic indexing, unit indexing, or maybe simple hashtables.

edit
Nevermind, I noticed you're doing it for dummies only, that's totally fine, but I'd recommend using Bribe's UnitIndexer as an optional requirement so you can disable the system, create the unit, then enable it.

Just tell the user to do so, don't actually include the system

Also, your method of indexing is not good enough.
Dynamic indexing would be best. Hanky outlines the method with examples perfectly, so check out that template.

 

[zv27]

...missing tooltip

 

[Tank-Commander]

Like with your other one, it's using custom values, which collide with eachother, put both of your spells that you've uploaded into the same map, try using them both. The result will be equal to a mess

Also I thought I should point out while your screenshots are ingame, they're not really what they mean by ingame screenshot, since neither of them actually display the -spell- they just display a hero which casts them, which actually tells us all nothing about it, can't see what it does, and yes they both lack tooltips as zv27 rightfully said

Edit: Must say though, minus all the comment scripts, this spell is actually really simple and short

 

[Magtheridon96]

Actually, now that I think about it, this resource /can/ use custom values and it would be fine.

This is because he's only editing the custom value for a dummy unit.

Of course, you need to add warnings here.
Tell users they need to disable their unit indexers before you create the unit and enable after.

 

[daRk_sParroW]

thanks for the tips.