Moderator
M
Moderator
15:41, 6th Oct 2009
TriggerHappy187:
Sorry but this spell is far to simple to be approved at hive.
First of all the actual coding is only like 5 lines long. Aside from that it leaks.
You also statically create the unit for player 1 (red) all of the time, even if the caster is another player.
As for the leak, your currently storing the location but never removing it. At the end of your trigger add;
Custom script: call RemoveLocation(udg_pointx[GetPlayerId(GetTriggerPlayer())+1])
You did half of the work by storing the location.
You also use TriggerSleepAction (waits) which are bad because they are inaccurate and also still run while a player is lagging.
TriggerHappy187:
Sorry but this spell is far to simple to be approved at hive.
First of all the actual coding is only like 5 lines long. Aside from that it leaks.
You also statically create the unit for player 1 (red) all of the time, even if the caster is another player.
As for the leak, your currently storing the location but never removing it. At the end of your trigger add;
Custom script: call RemoveLocation(udg_pointx[GetPlayerId(GetTriggerPlayer())+1])
You did half of the work by storing the location.
You also use TriggerSleepAction (waits) which are bad because they are inaccurate and also still run while a player is lagging.