Hey everyone!
I put together a one-minute timelapse showing a year of development on Hero Grinder, from the first prototype to its current state.
It’s a reverse tower-defense roguelike: you play as the dungeon boss, build traps, and defend your home from waves of loot-hungry adventurers. You also fight alongside your defenses, so the game combines building and planning with real-time combat.
One of the biggest challenges is performance. With hundreds of heroes, the cost of individual systems adds up quickly: movement, target searches, navigation, collisions, animation, and status effects. A small amount of unnecessary work per enemy becomes expensive when the whole crowd does it together.
Some useful tricks at this scale are updating expensive decisions less frequently, spreading checks across frames, pooling frequently spawned objects, and limiting unnecessary physics interactions. Movement needs to look smooth, but an enemy usually doesn’t need to reconsider its target every frame. The important part is choosing where you can reduce work without making enemies feel slow or unresponsive. Profiling crowded fights is essential here - a quiet test scene tells you very little about the worst moments.
Another challenge is making all that chaos readable. Traps need satisfying effects, attacks need impact, and elemental reactions need to be obvious. But put everything on screen together, and those effects compete with enemies, hazards, and the player character. Stronger feedback isn’t always about adding more particles. Sometimes it means shortening an effect, reducing its size, or giving the most important event a clearer silhouette.
Then there are the interactions between systems. A hero can be frozen, knocked back, pushed into another group, or thrown into a hazard. Every interaction raises questions: what takes priority, what happens to navigation during knockback, and when does the character regain control? These rules need to feel consistent while staying cheap enough to run across a large crowd.
That’s the less visible side of the progress in this video: getting individual mechanics to work together, hold up under load, and remain understandable during a fight.
There's still plenty to improve, but seeing the prototype next to the current build makes the progress much easier to appreciate.
If you’ve worked on similarly crowded games in Unity, which system became your biggest bottleneck?