// the find
ieatyoursushi/Zombtoy
Unity Isometric/FPS shooter survival game I originally built in sophomore year of high school. Currently being refactored for feature-scalability, advanced multiplayer systems along a modernized principal-codebase.
A high school zombie survival game in Unity being actively refactored by its original author to support event-driven architecture and multiplayer. It combines isometric and FPS perspectives and pairs with a minimal .NET 8 backend for score tracking. This is a student learning project, not a production-ready game engine or framework.
The move to a GameEvents system (decoupled pub/sub over direct component references) is the right call for Unity at this scale — it makes the codebase much easier to extend without cascading changes. Object pooling for projectiles and effects shows the author has already hit the performance walls that teach this lesson. The .NET Minimal API backend is appropriately scoped — no Swagger bloat, no ORM ceremony, just endpoints that do one thing. Including a REFACTOR_PLAN.md and architecture diagrams in DevTools suggests the author is thinking structurally, not just hacking features in.
3 stars and 0 forks after years of work means this has no community and likely hasn't been run by anyone but the author — expect rough edges when cloning cold. The multiplayer ambitions (CO-OP, anticheat, user profiles) are all listed as future work with zero implementation; the backend today is a score list over HTTP with no auth. The README mentions third-party Unity Store assets (WarFX, Cartoon FX, Sci-Fi Pack) without clarifying their licenses — you can't redistribute or fork the full project legally without sorting that out. Multiple scenes representing 'differing versions' of the same level is a red flag for accumulated technical debt that the refactor hasn't cleaned up yet.