Selected Work - Games

Streetvers - a roguelike on four platforms

A single-player street-culture roguelike on the MoreMountains TopDownEngine: wave combat, a 33-type buff-card economy drafted between waves, a capturable territory base layer, raids, and a sigil meta-progression tree-one Unity 6 project building to iOS, Android, Windows and Mac.

Role

Solo Developer

Engine

Unity 6 · C# · MoreMountains TopDownEngine

Platforms

iOS · Android · Windows · Mac

01The game

Streetvers is a single-player roguelike where you clear waves, draft buff cards between them, capture and defend territory, run raids, and grow a sigil meta-progression tree across runs. It is built on the MoreMountains TopDownEngine so the design budget goes to the systems that make it feel good, the buff economy, the base layer, and the meta-progression, instead of re-inventing combat. The prototype is at version 0.4 across 190 C# scripts and 9 scenes, building from one Unity 6 project to all four platforms.

02What I built

  • Wave / combat loop - the moment-to-moment core, tuned on a battle-tested top-down combat substrate.

  • Buff-card economy - 33 buff types drafted between waves-the roguelike decision layer that makes each run different.

  • Territory base layer - 10+ capturable zones with hired guards/dealers and passive income-a meta layer over the runs.

  • Sigil meta-progression - a skill tree that carries power and identity across runs, plus a raid simulator and store UI.

Streetvers x Reality Metaverse - official trailer

03Development challenges

One project, four platforms

Problem
Mobile and desktop have different input handling and performance budgets, but I did not want to maintain two separate forks of the game.
Approach
I kept a single Unity 6 project with iOS, Android, Windows, and Mac configured side by side and one shared input model. Mobile autoaim and distance-based AI culling are scoped as the next pass.
Result
All four targets build from one codebase, and the platform-specific tuning is scoped work rather than a structural blocker.

Character data drives every surface

Problem
Each character is a playable unit, a collectible card, a social drop, and a stake-gated NFT drop through the Reality Metaverse partnership, and these cannot drift apart.
Approach
I drove the roster and the card from one record and one render path authored in the admin panel, and the backend reads Reality Metaverse's $RMV economy over its API instead of reimplementing it.
Result
A change to a character updates every surface at once, and the partner's drops stay in sync without a second copy of the data.

Buff draft that stays a decision

Problem
The 33 buffs drafted between waves are the roguelike's main decision layer, but stacking pushes runs toward one dominant build or makes the offer feel random.
Approach
I tuned what each draft offers and capped stacking so picks trade off against each other, and I composed effects on the TopDownEngine's stat hooks so combinations resolve the same way without per-buff special cases.
Result
Each draft is a real choice, builds vary between runs, and adding a buff is a data change rather than a new balancing edge case.

Built on the engine's seams

Problem
The MoreMountains TopDownEngine handles combat, but the buff economy, territory layer, and sigil progression are not in it, and editing the engine directly turns every upgrade into a merge conflict.
Approach
I built the meta systems as layers on top of the engine's stat and ability hooks instead of forking its internals, keeping my code and the engine's code on separate seams.
Result
Most of the design time went into the systems unique to the game, and engine updates stay drop-in.

04Engine & tooling

Built on a combat substrate so the work goes into game feel and systems design.

Unity 6C#MoreMountains TopDownEngineUGUIBuilt-in RP

05Outcomes

StatusSingle-player prototype at pre-release 0.4
PlatformsiOS · Android · Windows · Mac from one project
190 / 9Unity C# scripts / scenes
33buff card types in the roguelike loop
10+capturable territory zones in the base layer
Card surfaceOne render path · three audiences