I need help... (again)
- Thread starter Smitty #1
- Start date
- Mar 23, 2017
- 1,338
- 996
image machine broke
If you have the Ultimate mapping resource pack from A boojam snark press 
then on the right under Catagories, choose the doors prefab and select a setupgate door. Change the Select option on the top right to "objects" and disable props in the visgroups tab, then rename each of the doors (example Onewaydoor_top for the top door and Onewaydoor_bottom for the bottom door) and go into the outputs for each door and delete the "On fully open, Kill" output. Then using use the trigger texture as you would a regular door and make it a Trigger_multiple entity, then put in the regular outputs for a door, just instead of listing each door's name, list it as "Onewaydoor_*" the * at the end targets all entities with that name. then just move the trigger to one side to allow only that side to open the door. I can provide images if you do not understand what I am saying.
then on the right under Catagories, choose the doors prefab and select a setupgate door. Change the Select option on the top right to "objects" and disable props in the visgroups tab, then rename each of the doors (example Onewaydoor_top for the top door and Onewaydoor_bottom for the bottom door) and go into the outputs for each door and delete the "On fully open, Kill" output. Then using use the trigger texture as you would a regular door and make it a Trigger_multiple entity, then put in the regular outputs for a door, just instead of listing each door's name, list it as "Onewaydoor_*" the * at the end targets all entities with that name. then just move the trigger to one side to allow only that side to open the door. I can provide images if you do not understand what I am saying.
Box Of Paper
L3: Member
- Jul 15, 2019
- 138
- 159
I created a map with an example of one-way door.
You basically need to parent the prop_dynamics to func_doors (with "Render mode" set to "Dont Render"),
and create two trigger_multiple:
- One that opens the gates, which mustn't extend beyond them [OnStartTouchAll PropDoor Open]
- And one that closes the gates which extends a little bit beyond them [OnEndTouchAll PropDoor Close]
It isn't necessary to separate the outputs, but this way prevents the player from getting stuck.
You basically need to parent the prop_dynamics to func_doors (with "Render mode" set to "Dont Render"),
and create two trigger_multiple:
- One that opens the gates, which mustn't extend beyond them [OnStartTouchAll PropDoor Open]
- And one that closes the gates which extends a little bit beyond them [OnEndTouchAll PropDoor Close]
It isn't necessary to separate the outputs, but this way prevents the player from getting stuck.
Box Of Paper
L3: Member
- Jul 15, 2019
- 138
- 159
You're welcome
I'm not sure of what's breaking the second door, I'd suggest checking the trigger_multiple's outputs and the func_doors' properties for wrongly setup targetnames;
also check if the prop_dynamics are parented with the right door.
If you have used * in the outputs like I did, make sure that the prefixes are diffrent for each gate, alternativly setup the trigger_multiples to open and close the doors you want to (using their full name).
I'm not sure of what's breaking the second door, I'd suggest checking the trigger_multiple's outputs and the func_doors' properties for wrongly setup targetnames;
also check if the prop_dynamics are parented with the right door.
If you have used * in the outputs like I did, make sure that the prefixes are diffrent for each gate, alternativly setup the trigger_multiples to open and close the doors you want to (using their full name).
Are the names for the doors different?
RevolutionTeam
L4: Comfortable Member
- May 19, 2019
- 173
- 45
Ok, here's the best way to do the one way door.
ONE WAY DOORS:
STEP ONE - Create a brush (preferably translucent texture)
STEP TWO - Make the brush a func_door
STEP THREE - Make the func_door's speed 300, set the move direction to up, and name it "onewaydoor_top" (Remember the lip!)
STEP FOUR - Clone the door to the bottom, rename it "onewaydoor_bottom", and change the move direction to down.
STEP FIVE - Add a trigger that only triggers from the back, and do the "OnStartTouchAll" and "OnEndTouchAll" stuff.
STEP SIX - Add two prop_dynamics, sharing the names of the doors with "_prop" at the end, and parent them to their respective doors.
Congrats! You just made a one way door on a KotH map! Why did you even need it?
ONE WAY DOORS:
STEP ONE - Create a brush (preferably translucent texture)
STEP TWO - Make the brush a func_door
STEP THREE - Make the func_door's speed 300, set the move direction to up, and name it "onewaydoor_top" (Remember the lip!)
STEP FOUR - Clone the door to the bottom, rename it "onewaydoor_bottom", and change the move direction to down.
STEP FIVE - Add a trigger that only triggers from the back, and do the "OnStartTouchAll" and "OnEndTouchAll" stuff.
STEP SIX - Add two prop_dynamics, sharing the names of the doors with "_prop" at the end, and parent them to their respective doors.
Congrats! You just made a one way door on a KotH map! Why did you even need it?
RevolutionTeam
L4: Comfortable Member
- May 19, 2019
- 173
- 45
Set the move direction to Left (relative to your "Top (X,Y)"), and vice-versa.
Keep in mind one-way doors are pretty undesirable in gameplay.
RevolutionTeam
L4: Comfortable Member
- May 19, 2019
- 173
- 45
Unless you're trying to do something like Dustbowl, then one-way doors aren't desirable.
Doors in general (outside of spawn doors obviously) are undesirable - they create really awkward gameplay around them. Running up to a door and getting a faceful of sentry rockets at point blank after the door reveals theres a lv3 behind it is not fun.
RevolutionTeam
L4: Comfortable Member
- May 19, 2019
- 173
- 45
That's why you use setup doors, so that you can see what the hell is next.