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.
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.
Source Engine's Entity I/O moves gameplay logic into map data via a string-based async event bus. Covers C++ declaration model, Hammer authoring, runtime dispatch, and debugging tools for typos, coercion bugs, and circular loops.
Players rubber-band but ping looks fine? Learn to read net_graph choke, loss, sv, and var on a Source engine server to isolate whether the cause is client rates, server tick instability, or the network path.
Fix Source Engine map leaks with the pointfile, then cut VVIS compile time using func_detail, areaportals and hint brushes.
Explore how the Source Engine uses client-side prediction and server reconciliation to eliminate input lag while maintaining an authoritative server state.
sourceengine