-
Listen to a special audio message from Bill Roper to the Hive Workshop community (Bill is a former Vice President of Blizzard Entertainment, Producer, Designer, Musician, Voice Actor) 🔗Click here to hear his message!
-
Read Evilhog's interview with Gregory Alper, the original composer of the music for WarCraft: Orcs & Humans 🔗Click here to read the full interview.
-
The Hive's 22nd Icon Contest: Creep Abilities is now concluded, time to vote for your favourite set of icons! Click here to vote!
-
✅ The POLL for Hive's Texturing Contest #34 is OPEN! Vote for the TOP 3 SKINS! 🔗Click here to cast your vote!
-
✅ The POLL for Hive's Techtree Contest #20 is OPEN! Vote for the TOP 3 FACTIONS! 🔗Click here to cast your vote!
HerrDave's Gate System
- Author(s)
- HerrDave
- Tags
- GUI / Triggers, Open Source, No Target, System
- Size
- 127.06 KB
- Rating
- Downloads
- 99
- Created
- Sep 22, 2025
- Updated
- Sep 23, 2025
- Resources
- 1
- State
Pending
This bundle is marked as pending. It has not been reviewed by a staff member yet.
Finally we have a system for capturable gates which can be opened and closed, and update the Pathing AI when opened/closed!
How do these gates work?
Installation Guide:
(Inside HerrDave's GateSystem map)
All done, you now have gates!
How do these gates work?
- Each gate has 3 versions, Open, Closed and Ruins
- The moment a gate starts opening, it becomes pathable for units (You don't need to wait for the doors to be all the way open before you can move)
[*]The gate only becomes solidly "closed" once the doors are fully closed (Like in Battle for Middle-earth) - If a unit is running towards a closing gate and doesn't make it in time, it will automatically seek out another path instead of thinking it is still open and rubbing it's face on the doors
- Units caught inside a closing gate automatically get "pushed out" and will resume normal pathing
- If a Gate dies, it will turn into Ruins and change ownership to the Attacker
- These gates will never "snap" to another location when changing variants (this was an issue with older Gate Systems in Warcraft 3 based on Bear Form)
[*]Gate Ruins can be "upgraded" into Open Gates again
Installation Guide:
(Inside HerrDave's GateSystem map)
- Go to the Object Editor and copy the [Open Gate] and [Close Gate] abilities, and paste them in your map
- Go to the Object Editor and copy all 3 variations of each Gate Angle you need [Gate Closed, Gate Open, Gate Ruins] and paste them in your map
- Go to the Trigger Editor and copy the [Gate System] folder and paste it in your map
- Check your Open Gates and make sure they have the [Close Gate (Q Tranquility)] ability
- Check your Closed Gates and make sure they have the [Open Gate (Q Tranquility)] ability
All done, you now have gates!
Contents
![A]mun](https://cdn.hiveworkshop.com/data/avatars/m/140/140771.jpg?1674379729){kind=avatar}
So this actually updates the pathing, but why?
Unit - Create 1 Gate Ruins (Ruins Horizontal) for (Owner of (Killing unit)) at (GateLocation offset by (0.00, 0.00)) facing Default building facing degrees
^ should be owner of triggering unit (no change of ownership)
ah nevermind you want the gates to be captured
Unit - Create 1 Gate Ruins (Ruins Diagonal Left) for (Owner of (Killing unit)) at (GateLocation offset by (0.00, 0.00)) facing Default building facing degrees
^ doesn't offset leak a second location? (unless 0,0 does not)
ah nevermind you want the gates to be captured
Unit - Create 1 Gate Ruins (Ruins Diagonal Left) for (Owner of (Killing unit)) at (GateLocation offset by (0.00, 0.00)) facing Default building facing degrees
^ doesn't offset leak a second location? (unless 0,0 does not)
- Joined
- Dec 23, 2013
- Messages
- 1,452
It actually may,
I'll stick in a Location variable that cleans itself up
Updated the Gate Ruins section to:
Unit - Create 1 Gate Ruins (Ruins Horizontal) for (Owner of (Killing unit)) at GateLocation facing Default building facing degrees
*Edit
There we go, updated
Thanks for catching that!
Updated the Gate Ruins section to:
Unit - Create 1 Gate Ruins (Ruins Horizontal) for (Owner of (Killing unit)) at GateLocation facing Default building facing degrees
*Edit
There we go, updated
Thanks for catching that!
Last edited:
Antares
Spell Reviewer
- Joined
- Dec 13, 2009
- Messages
- 1,106
Very nice.
I don't think this should be categorized as a system. I think template is a better fit.
Can you merge the four different triggers of each type into one? You can remove the unit type check in the conditions, then do a branch in the actions for each type.
I don't think this should be categorized as a system. I think template is a better fit.
Can you merge the four different triggers of each type into one? You can remove the unit type check in the conditions, then do a branch in the actions for each type.
