Differences

This shows you the differences between two versions of the page.

--- advanced_entities_explanation [2023/05/24 14:42] – frank_lee_smith
+++ advanced_entities_explanation [2026/04/06 23:28] (current) – frank_lee_smith
@@ Line 1: / Line 1: @@
-==============Advanced Entities Explanation==============
+================Doors and Elevators================
-This page is for all the optional entities that will enhance your TTT map and make it more interesting. It is HIGHLY recommended that you use these sparingly. The best maps use things like traitor traps and testing tastefully and in a balanced way. **It's better to not use these entities than just plopping them in for the sake of it**
+This page will go over rotating doors, sliding doors, and elevators for your TTT map.
-=====Traitor Tester (ttt_tester)======
+======Rotating Doors======
+A door that will need to rotate on a pivot to open.
-**ttt_tester** is the entity used to create a **Traitor Tester.** This functions as a way to test whether someone is an Innocent or a Traitor. Typically, it is implemented with some catch or has a way for traitors to counter it as to not make it too easy to get everyone proven.
-To implement, use a trigger or button to activate ttt_tester with the //Activate// output. Once activated **ttt_tester** will check the role of who triggered the button/trigger and do either a //OnPass// or on //OnFail// output for innocent and traitor respectively.
+{{:f9x8q37.png?nolink&400|}}
-For more in-depth instructions check below.
-. Create a confined space for a player to get tested in, include an ent_door or ent_platform to enclose while testing.
-. Create the ttt_role_check entity, place it near the tester (doesn't matter where), and give it a name.
+To implement, create a new empty in the outliner and add the **Rotating Door** component. The model for your door will also need to be added to this gameobject via the Model Renderer component.
-.  Create a **trigger_multiple** in the confined space and uncheck the //Enabled// object property.
+**Note: The Pivot for the door model you use must have the pivot set to the side the door will rotate on**
-{{::trigger_1.png?600|}}
+{{:v0sqw0h.png?nolink&400|}}
-. Add an output on the trigger to remove itself.
+By default, the door will be set to a straight 90 degree pivot. This can be modified in the object properties or dragging the pivot gizmo.
-{{::trigger_2.png?600|}}
+======Sliding Doors======
+A door that will open and close by moving back and forth in one direction.
-. Add an **Activate** output to send to the **ttt_tester** entity
+{{:w9kktdz.png?nolink&400|}}
-{{::trigger_3.png?600|}}
+To implement, create a new empty in the outliner and add the Linear Mover component. The model for your door will also need to be added to this gameobject via the Model Renderer component. The pivot does not matter for this type of door.
+The **Move Delta** variable determines how far the door moves when activated
-. Set OnPass and OnFail outputs to something the play can see like red and green dynamic lights turning on.
-{{::trigger_4.png?600|}}
+{{:9jqr4sp.png?nolink&400|}}
+======Elevator======
-. Hook up a button to close the door for 6 - 10 seconds, then open it.
+An elevator needs multiple gameobjects to function.
-. Add an output to the same button to the **trigger_multiple** to enable after the tester door closes.
+Currently, support is in for two stop elevators only.
-. Clean up the system and play with the timing until it works and feels right
+====Path Track====
-Congrats, you just made your first tester!
+The first thing you will need is a **Path Track**. Create an empty gameobject and add the **Path Track** component. This can be placed anywhere, but you need to give it a unique name.
-**Tips**
+{{::vr353h3.png?nolink&400|}}
-  - Give the tester time for it the "test" the player. Instant testers are no fun and are not balanced
-  - Testers are implemented best with Traitor Rooms being close by to invite some counterplay
-  - Many testers will allow players to "break" them by destroying something in the room, should have a lot of HP
-  - Some maps will force players to find something to activate the tester or find fuel around the map to power for a test
-======ttt_role_button======
+====Path Mover====
-**ttt_role_button** is what is typically called the "Traitor Button." It is an entity that allows a set role to press a button they see in their vision if within it's range by pressing E. When pressed it will be able to send outputs similar to ent_button.
+This will be the elevator itself. Create an empty gameobject and add a **Path Mover** component. Give the gameobject itself a unique name.
-{{:role_button.png?400|}}
+{{::tfs9034.png?nolink&400|}}
-There are a few important Object Properties:
+Add a **Model Renderer** for the elevator model on this object. Make sure your elevator model has collisions.
-**Role** - will determine which role can see it, can be used for expanded roles by typing their name
+The **Track Name** property MUST be filled with the same unique name the **Path Track** was given.
-**Description** - Tells the player what it does, will show up next to the button when they look at it.
+{{::5hfqqwp.png?nolink&400|}}
-**Delay** - How long until the button can be used again. Will have no delay at 0.
+====Path Point====
-**Remove on use** - Will delete the button after being used once. Useful for one time traps like explosions
+You will need to create two separate gameobjects and add a **Path Point** to each.
-**Tips**
+{{::xw2qvf1.png?nolink&400|}}
-  * Use sparingly, trap heavy maps can be annoying and unbalanced. The best maps have only a few traps at most.
+Name them Point 1 and Point 2 in the **Point name** variable in the object properties.
-  * You can use this entity to make Detective Rooms by making a Detective button on a door
-  * Innocent buttons should be avoided unless you have a really good reason to use it
-======ttt_text_popup======
+{{::1nnth0r.png?nolink&400|}}
-**ttt_text_popup** allows for a message to pop up on the player's screen when receiving an input.
+Point 1 will need to have the same position/transform as the path mover. Point 2 will be where the elevator moves to when activated.
-{{::ttt_text.png?600|}}
+====Buttons====
-There are a few important Object Properties:
+Your elevator will need a button for each position of the elevator. Start by creating each of your buttons by creating a new empty gameobject and adding a **TTT Button Component**
-**Target Players** -  Allows for the entity to send the message to the activator, everyone, or a specific team
+{{::70hjqvn.png?nolink&400|}}
-**Popup Text** - Will determine what the main message contains
+Add a **Model Renderer** with the model your button will be using. Make sure your model has collisions.
-**Popup Title** - Will determine the title above the main message. Useful to clarify a cooldown or if single use
+To hook your buttons into the elevator find the **Objects** section in the object properties and add an //Targets On Activated// item.
-======ttt_credit_adjust======
+{{::00tj6p2.png?nolink&400|}}
-**ttt_credit_adjust** will remove or give credits to the user. This is useful for something like a role button that costs a credit to activate.
+In the popup, you need to set the name to the unique name of the gameobject you made for the elevator itself.
-To implement simply have the button/trigger send an //Adjust// output upon activation to the **ttt_credit_adjust**. The amount can be set in the Object Properties by changing the Adjust Amount. To remove one credit make the amount -1.
+Set the input to "CallOrDepart"
-======ttt_force_win======
+The Payload will need to be set to the point that the elevator goes to when pressed while the elevator is at the button's stop. So the button at Point 1 will need the payload to be Point 2 and vice versa. Buttons can still recall the elevator to its stop, though.
+{{::54x40qs.png?nolink&400|}}
+If all of this is set up properly your elevator will be functional with two buttons and two back and forth stops.