T-Kill/Unit patrol

You can submit your maps here. Both finished and unfinished submissions are welcome.
Forum rules
Finished maps:
• Submitting your own map(s):
One map per topic please! (Or we will have a hard time finding out which comment is for which map)
You can leave your Username@Realm so people can contact you in game. (eg.: 3ICE@USEast, 3ICE@Northrend)
Write a description and don't forget to post some screenshots. (Images and videos are worth a thousand words)
• Submitting a map not made by you:
Do not claim it as yours. We'll find it out (sooner or later) anyway.
Ask the maker to submit it himself is possible.
Or at least let the maker know that his map has a topic here, so he can benefit from your comments and bug reports. (Or request the thread be deleted for whatever reason*.)

Unfinished maps:
You are welcome to post your unfinished maps here and ask for help.
We will look at the map and tell you whats wrong with it or how to continue editing it.

Projects:
Important/cool maps and big projects will have their own forum category inside. (Like the 3ICE's Maze Designer category)
DarkJustice12
Posts: 50
Joined: Fri Jan 20, 2012 3:35 pm
Realm: US East
Account: DarkJustice
Clan: ATR

T-Kill/Unit patrol

Unread post by DarkJustice12 »

this is for anyone who wants it but mostly i want 3ice to check it for leaks
Attachments
Simple Terrain Killing and Unit Patrol System.w3x
(14.74 KiB) Downloaded 615 times

User avatar
3ICE
Admin
Posts: 2629
Joined: Sat Mar 01, 2008 11:34 pm
Realm: Europe
Account: 3ICE
Clan: 3ICE
Location: Hungary
Contact:

Re: T-Kill/Unit patrol

Unread post by 3ICE »

That's a bad way to do it. Good idea and nice effort, but you generate much more lag than the currently accepted standard does. (Which is 11 kill triggers, one for each player.) Unit comes within range of unit is much faster than Pick every unit in (Units within PickingRange of UnitLoc) on a tight 0.03 timer.

I'm ignoring all leaks in setup because they only leak once.

PatrolUnits would imply a unit group because it is plural. Rename it to (Current/Picked)PatrolUnit.

Actually, Set PatrolUnits = (Picked unit) is probably unnecessary. Referring to Picked unit is faster. Warcraft 3 correctly handles nested unit groups, so you won't have conflicts just because there are two picked units at the same time. The inner block will use the second picked unit and the outer block will use the first.

Unit Group - Pick every unit in (Units within PickingRange of UnitLoc) leaks a group (Units within PickingRange of UnitLoc) every 0.03 seconds and is generally much slower than the standard kill triggers as noted above.

Change ((Picked unit) belongs to an enemy of (Owner of PatrolUnits)) Equal to True to (Picked unit) belongs to an enemy of Player 12 (Brown) or the even simpler (Owner of (Picked unit)) Not equal to Player 12 (Brown).

I created a similar system and then deleted it after realizing it was slower than the hated (but still the best) 11 kill triggers standard.

If you have 100 patrolling units, your system will temporarily create 100 empty groups every 0.03 seconds and often store actual units in them before discarding them. The accepted standard keeps it at 11, no matter how many patrols you have.
ImageImageImageImageImage
Image
ImageImage

Post Reply

Who is online

Users browsing this forum: No registered users and 142 guests