Massing Units

[Sgt. Johnson]

So I tried to make a massing system for Zone Control so that players could control all their marines that spawn without having to micro them at every single bunker they own, I came across 2 problems however.

1) The Unit I use to control the massing steps on the beacon then teleports back to the center of the mass area, for some reason he continues to run to the beacon and you have to manually tell him to stop. Using a trigger to order him to stop will not work, the only way I could get him to stop is after teleporting off the beacon I had a trigger order him to move to the center of the massing area. This would stop him from moving back on the beacon over and over.

2) Leaking! For some reason using the mass continually would cause "something" to leak, the fps would drop a bit and I would get delay, same as what happens in WC3 typically when you have a leak.

Below is a screenshot of the trigger if it helps anyone to figure this out.
(The 3 closed IF actions are the same as the open one except for the other 3 teams)

 

[Element of Water]

For the stop order, I don't know. Maybe try hold position?

For the leaking, I guess pick every unit in... leaks just like it does it wc2. *sighs".

 

[Sgt. Johnson]

For the stop order, I don't know. Maybe try hold position?

For the leaking, I guess pick every unit in... leaks just like it does it wc2. *sighs".

Hopefully the leaking is just a bug.

And I'll try hold position after I finish my lunch and see what happens.

Edit: Hold position does work with stopping the unit after moving it via a trigger, kinda annoying yet useful though that unit's keep moving even after moving them instantly via a trigger.

Edit 2: Ok oddly enough the leaking has suddenly stopped =/ also I think the reason the massing unit was not stopping probably would have something to with the fact I accidently removed the stop button/ability for it xD

 

[Dr Super Good]

SC2 will not leak as much as WC3, however there is no reason to be stupid. Do not be afraid to manually deallocate something, as it will save the garbage collector doing so.

 

[Mr.Cheese]

The question of leaks is very important, and we ought to investigate it. All the typical 'leaks' that occurred in Warcraft 3, how do they fare in Starcraft 2 without the War 3 leak fixes?

In one example, I had units continually spawn from 'center of Region X'. In Warcraft 3, I would make a temporary point at center of Region X, make the unit, and delete the temporary point. However, I'm not doing any of that in Starcraft 2 but have gone wild (does feel like 'going wild' after the restraints of Warcraft 3) and haven't noticed any effect. But that doesn't mean it is leaking or not. Dr. Super Feel Good, I think now is precisely the time to 'act stupid' so we can discover what this engine can do. Since I am very good at being stupid, I am finding some fun things with this engine.

One amusing thing is that Starcraft 2 will turn off triggers for you if it doesn't like them. For example, I made a loop where a trigger would run itself and keep making units. Units kept spawning and spawning and spawning until Starcraft 2 had enough of my funny busines and turned off the trigger! Even gave a message that it turned it off! In Warcraft 3, the game would have crashed.

I'll give this to Starcraft 2: it's engine is far more fun than Warcraft 3's was.

 

[Sgt. Johnson]

The leaking completely stopped and I haven't been able to get it to go again lol, idk why o.o

 

[Dr Super Good]

Its far better built and higher quality than WC3's.

Still do keep in mind that the base engine is quite demanding so do remember to program your map for people with slower computers (still aim for the best but your map should be playable with someone running the game at medium or your map will not be popular for 3 years).

The leaking was probably a false positive (no leak but something else) or else was a brief period during which the garbage collector fell asleep and was not working.