Survivor Roguelite Maker Adds a Data-Driven Unity Game Template

Unity developers exploring arena-survival games have another template to evaluate. Survivor Roguelite Maker, released on the Asset Store on November 10 by FlyCat, is described as a C# framework for building 2D survivor roguelites. It covers authoring data, combat loops, enemy waves, item progression and test utilities, rather than offering a finished commercial game.

The publisher outlines two progression structures. In an arena flow, players can reach a shop between waves; in a field flow, level-up choices can appear during combat. Combat options include ranged and melee attacks, auras, orbiting weapons and homing projectiles. Encounter data can describe elites, multi-phase bosses, horde events and status effects. The system is intended to accept custom presentation and assets through several layers of authoring tools.

A notable part of the product is its emphasis on balancing before release. The listed editor tools include a Wave Editor, Balance Simulator, Run Pacing view, Build Lab, Weapon Lab and Horde Preview. The publisher says developers can compare builds and replay or inspect recorded wave conditions. These are meaningful workflow ideas, although the supplied store text does not independently establish the statistical accuracy of the simulations or the quality of combat balancing.

The technical notes mention Unity 6000.0-based support, compatibility with Built-in and URP for its 2D sample, and dependencies on Unity UI and Input System packages. The listing also contains an unusually explicit AI disclosure: the publisher says coding assistants contributed to its code, tools and documentation, and Stable Audio 3 generated music and sound effects locally. These statements refer to how the package was made; they are not claims that the runtime contains a generative AI system.

An evaluation should use a fresh sample project, run a default wave and then alter one parameter at a time: enemy count, damage, upgrade frequency and shop prices. Compare the editor's predicted pacing with actual playtests, documenting where expectations diverge. Inspect extension points before replacing the demo visuals or importing the system into an existing codebase.

Templates can shorten prototyping, but maintainability depends on the underlying structure and clarity of the source. For small teams, the stronger question is whether this framework supports the kind of game they want to evolve, not how quickly its demonstration can be launched.