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

6 Dec 2011
Bribe: The line where you say the user should add some conditions for the gate ("Insert a condition here. Like if you want it to only open for 1 player or something.") should be where you have the conditions for "Picked unit is flying == false" and "Picked unit is dead == false". This will make your system easier to edit and it will also run more quickly especially if there are large numbers of units on the map.

Instead of creating a point for the region and removing the point as well, per every unit on the map throughout the entire game, do this from the looping trigger in place of the region/point stuff:

• Custom script: call MoveRectTo(udg_GateRect, GetUnitX(GetEnumUnit()), GetUnitY(GetEnumUnit()))

. Then you don't need locations at all, save some lines of code, some RAM processing time and generally makes your system better overall.

I discovered something funny while making this...
If you add a tree to the gate opening... The tree flips out and makes death sounds n stuff. And you can walk through it lol.
So.. Don't put trees as a gate. xD

hehe, nice work man, this is very useful 5/5

You know, the best Gate system I can think of is one that lets the user define a condition for a gate to be open

That's all that a Gate system should be.

Bribe you don't find creating and destroying a rect 10 times a second is something? Rects as locations can be moved and you know it. And what mag ssaid above ofc.

Hope that's enough for today >=D time to go back to diablo.

This is a gate opener for destructables only, right?

Yeah gates are destructables

Yeah I thought it was a unit gate system for a moment but then I checked triggers.