Differences

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

--- tools_overview [2026/05/04 00:39] – created frank_lee_smith
+++ tools_overview [2026/05/04 02:08] (current) – frank_lee_smith
@@ Line 2: / Line 2: @@
 The mapping tools are small components that you add to objects in a map scene. Each component does one job: a button sends a signal, a mover moves, a trigger reacts to players, a spawner creates pickups, and so on. Build larger map features by combining these pieces.
+//Click "Add Component" on the GameObject...//
+{{::addcomponent.png?400|}}
+------------------
+//... Then navigate to the mapping tools or search for them directly//
+{{:tttmappingtools.png?400|}}
+------------------
 ===== Component categories =====
 ^ Editor category ^ Components ^ Typical use ^
-| ''TTT Mapping Tools/Interaction/Buttons'' | ''TTT Button'', ''TTT Role Button'' | World buttons, hold buttons, toggles, traitor/detective buttons. |
+| ''Interaction/Buttons'' | ''TTT Button'', ''TTT Role Button'' | World buttons, hold buttons, toggles, traitor/detective buttons. |
-| ''TTT Mapping Tools/Interaction/State'' | ''TTT Enable Target'' | Turn lights, sounds, particles, components, or object groups on/off. |
+| ''Interaction/State'' | ''TTT Enable Target'' | Turn lights, sounds, particles, components, or object groups on/off. |
-| ''TTT Mapping Tools/Movement/Binary'' | ''TTT Linear Mover'', ''TTT Rotating Door'' | Sliding doors, lifts, panels, hinged doors, rotating traps. |
+| ''Movement/Binary'' | ''TTT Linear Mover'', ''TTT Rotating Door'' | Sliding doors, lifts, panels, hinged doors, rotating traps. |
-| ''TTT Mapping Tools/Movement/Path'' | ''TTT Path Mover'', ''TTT Path Track'', ''TTT Path Point'' | Elevators, trains, multi-stop platforms, path-based movement. |
+| ''Movement/Path'' | ''TTT Path Mover'', ''TTT Path Track'', ''TTT Path Point'' | Elevators, trains, multi-stop platforms, path-based movement. |
-| ''TTT Mapping Tools/Triggers'' | ''TTT Trigger Box'', ''TTT Trigger Hurt'', ''TTT Trigger Push'', ''TTT Trigger Teleport'', ''TTT Trigger Role Tester'' | Room sensors, damage traps, fans, launch pads, teleporters, traitor testers. |
+| ''Spawners'' | Weapon, ammo, grenade, and random spawn markers | Round-resetting pickups. |
-| ''TTT Mapping Tools/Spawners'' | Weapon, ammo, grenade, and random spawn markers | Round-resetting pickups. |
+| ''Triggers'' | ''TTT Trigger Box'', ''TTT Trigger Hurt'', ''TTT Trigger Push'', ''TTT Trigger Teleport'', ''TTT Trigger Role Tester'' | Room sensors, damage traps, fans, launch pads, teleporters, traitor testers. |
 ===== Core ideas =====
@@ Line 19: / Line 30: @@
 Clients can press usable objects, but the host decides whether the action is allowed and applies the result. This matters for traps, doors, role checks, teleports, damage, pickup spawning, and round reset state. If you are able to, always test map logic with at least one host and one client, not only in editor-host mode. Feel free to ask us on Discord and we can give your map a test run on the development branch.
-==== Map IO signals ====
+==== Map I/O signals ====
 Most authored logic uses the same signal model:
-  - A sender fires an output.
+. A sender fires an output.
-  - The output has one or more map links (Other map tools).
-  - Each map link finds a receiver by direct reference, object name, or tag.
+. The output has one or more map links (Other map tools).
-  - The receiver gets an input such as ''Activate'', ''Open'', ''Start'', ''Stop'', ''Toggle'', ''Lock'', or ''Unlock''.
+{{::signaloutputs.png?800|}}
+. Each map link finds a receiver by direct reference, object name, or tag.
+{{::button.png?1200|}}
+. The receiver gets an input such as ''Activate'', ''Open'', ''Start'', ''Stop'', ''Toggle'', ''Lock'', or ''Unlock''.
 This is similar to Source-style target/input authoring, while still supporting direct component references for scene-authored maps (It's a pain in the ass to use the dropper tool in Hammer, so text is supported as well).