Moderator
M
Moderator
22:32, 16th Jun 2010
Hanky:
Very simple. But well, useful enough.
Hanky:
Very simple. But well, useful enough.
(3 ratings)
Great, alot of leaks. No need to use arrayed variables as they are infact instant cast. Make a loop please to reduce the amount of code and fix the point leaks.
fix the point leaks as baassee said
use loops instead of copy&pasting the same stupid part of code 20 times
why do you pause/unpause the caster/target?
terrain deformation lags hard on big maps with lots of doodads in multilayer
don't use unnecessary imports and give credits for ALL things you imported
Attached Thumbnails
edit:
omg....use a variable then lol
(for loop integer i from 0 to 6 do actions
set angle = convert integer to real(integer i) * 60.00
or something like that)
Remove the arrays on the variables. It is not needed.
Is too simple, I vote for rejection
Posted by War Golum
Some tips and suggestions for improvement:Judgment has the same flaws as Chrone Impulse, therefore i won´t bother to repeat myself. Further i´m missing proper documentation for this spell and as stated above the custom imports are more than just redundant, you may remove the fast before this gets rejected.
- The spell is MPI (Multi Player Instanceable), which won´t be accepted. Only fully MUI (Multi Unit Instanceable) spells are allowed.
- In case you want to stick to MPI then please save (Player number of (Owner of (Casting unit))) to an integer. That would make your code more readable.
- Your script runs instantly therefore pausing the caster and the target is obsolete. You should remove those actions.
- Use your own integer instead of Integer-A as stated above.
- You have point leaks in your loop. You need to remove CI_Point2 ad the end of the loop.
Please do not double post (you obviously know where the Edit-Button is) and don´t spam those smileys, its just awful.
~TNT
So remove the arrays as you say, it is MUI then you dont need the arrays. (It is instant)
the spells are instant, so it is MUI not MPI(yes it is MPI if it HAS wait action!)
One leak :
JM_POINT offset by 350 towards .. ...
Set JM_Point2 = (JM_Point offset by 350.00 towards (120.00 x (Real((Integer A)))) degrees)
What, does not leak? He sets a new point. If it would leak it would have looked like "position of (something) offset by ..."
No need to null player variables?