19:57, 12th Oct 2012
Magtheridon96: Approved.

Tips:
-
- You can cache the picked unit into a variable inside the group enumeration loop instead of repeating the call more than once.

This could use a configuration trigger...

One last suggestion, maybe... Look at the approved spells to see what configuration triggers are...

Sorry I didn't post the configuration

• ...

then post it... XD

hahaha. >.<

since the boulder grows, I think it's just fair that the AOE should be configurable too and can increase per level... the speed can also be better if it can be changed per level... the boulder growth should be configurable too...

I don't want the speed to be Increased... I'll just put the AoE and the BoulderSize to Configuration Trigger

But what if the user wants to? It's not that much of a big deal to add...

Not now Adiktuz, I have so many things to do. Btw Thanks

There is an error in the loop trigger you posted I guess...

iChaos said:

There is an error in the loop trigger you posted I guess...

Click to expand...

How About know??

You should turn off collision for the boulder.
The animation is not smooth..
The rate of the size getting bigger is too fast.
It grows too fast. Pretty laggy though..

No need to turn off. Because, it's already turned off. Lol. hahaha. Do you mean turn on the collision of the Boulder.

The loop isnt smooth,maybe 0.05 or 0.04 is enough or you might want to add a loop in a loop

I'd suggest using Co-ordinates for moving the boulder - it generates a lot less lag (try casting a tonne of this spell at one time, or assume there are other spells in the map using the same function), is more efficient and could make things a lot smoother,as for "growth rate" being too fast as far as other people are saying, prehaps, use divide it by 2 or something? though 0.03 seconds loop would make it more smooth, in theory.

In eithercase here's the functions for using Co-ordinates if you want them:

• Custom script: call SetUnitX()
• Custom script: call SetUnitY()

You can either use the GetLocationX() and Y for your new location or calculate the new location mathematically i.e.

• Custom script: call SetUnitX(Unit, GetUnitX(Unit) + Distance * Cos(Angle * bj_DEGTORAD))
• Custom script: call SetUnitY(Unit, GetUnitY(Unit) + Distance * Sin(Angle * bj_DEGTORAD))

Note the Sine and Cosine for that

Hope this helps

Yeah,tank is right

I'm pretty sure the description should be 0.03 seconds instead of milliseconds.

This one is epic! Exxelent idea and creation!
5/5