Sequencing Map Events with logic_relay in Source Engine Hammer
Wire one player action to multiple delayed events in Hammer using logic_relay, then verify the chain on a dedicated server.
ReadMeFeed / Community knowledge
Real questions. Useful conversations. Find the people who know your stack.
Wire one player action to multiple delayed events in Hammer using logic_relay, then verify the chain on a dedicated server.
Wire Source 1 map entities with named outputs and inputs, then test live with ent_fire.
Source Engine hides latency by running identical movement code on client and server. Learn how lag compensation rewinds hitboxes for hitscan and how the 100ms default lerp creates a fixed peeker's advantage for map design.
Wire Source Engine entities in Hammer so a button opens a door and plays a sound, without server code.
Source Engine NPCs get stuck because legacy nodes don’t cover continuous walkable space. A built-in NavMesh of convex polygons stored in a .nav file gives reliable A* pathfinding, but it must be generated and kept in sync with map geometry.
In Source SDK 2013, entity replication is driven by Send/Recv tables and the engine's PVS check. Learn when to trust the default and when to force FL_EDICT_ALWAYS.
Learn how the Source Engine uses BSP and PVS to manage visibility and collision, and why 'leaks' in your brush geometry can break your map compilation.
Learn how to slash VVIS compile times and reduce runtime overdraw in the Source Engine by strategically converting decorative world brushes to func_detail.
Learn how to set up and verify model level‑of‑detail (LOD) in the Source Engine, understand its impact on frame rates, and avoid visual popping. A step‑by‑step guide with a QC example, trade‑offs, and practical checks for the game developer.