Zombie Spawners 🧟, Unity 2D NavMesh🧭
🧭 Smarter Systems & Backends
How Dying Light Uses Data Validation to Tame 25,000 Zombie Spawners
Techland reveals how it uses aggressive, context-aware data validation to ship huge open-world zombie games without drowning in content bugs. From validating thousands of zombie spawners against level geometry to scanning story graphs for quest conflicts in 4-player co-op, validators catch problems without ever running the game. The runtime stays simple; all the “ugly” edge-case logic lives in tool-only code driven by data.
Static Allocation and TigerBeetle: How to Build Uncrashable Game Backends
Joran Dirk Greef, creator of TigerBeetle, explains how a specialized transactional database can hit hundreds of thousands to a million transactions per second by embracing Amdahl’s law, batching, and a numbers-only schema. He introduces “Tiger Style,” a set of NASA-inspired habits: static allocation, strict limits, heavy assertions, and deterministic simulation testing that lets you fast‑forward years of rare bugs into a day. The conversation argues that safety is an architectural problem, not a language feature, and shows how these ideas produce ultra-reliable, physics‑aware infrastructure—ideal for things like game economies, counters, and rate limiting.
🎮 Engines, Worlds & Optimization
How to Add 2D Pathfinding in Unity with NavMeshPlus
Unity’s built-in NavMesh is aimed at 3D, but this tutorial shows how to turn it into a powerful 2D pathfinding system. Using NavMeshPlus, you’ll set up a navigation surface, bake a 2D navmesh from sprites or colliders, and configure a NavMeshAgent-driven character. The creator demonstrates using PolygonCollider2D to trace complex walls and tuning agent radius and height for 2D scale. The result: click-to-move units that naturally route around obstacles in a 2D scene.
From 120GB to 6GB: Extreme Unreal World Optimization for Nintendo Switch
A tiny team set out to build “Euro Truck, but with trains” across a compressed Europe in Unreal, then had to squeeze the entire 5,000km² world onto an 8GB Switch cartridge. Using Houdini, OpenStreetMap data, and an “excitement analysis” to contract boring stretches, they automated most of the world and reserved handcrafting for stations and cities. When performance tanked, they deleted landscapes, baked terrain into static meshes, killed shadows and fog, and leaned on AO to claw back visual quality—ultimately shipping a surprisingly solid Switch port that became the game’s second-best platform.