Featured work
Games & gameplay systems
The projects I'd want a studio to look at first: networked multiplayer, combat systems, and the architecture decisions behind them.
Wizard Derby
A networked multiplayer racing/derby game where two wizards crew a single vehicle, where one drives, one casts spells, and they swap roles mid-race. Teams share a health pool and draw spells to sabotage opponents.
I'm one of three project managers: I run meetings, track each contributor's progress, and helped
stand up the binary-safe Unreal pipeline (GitHub + Git LFS with file locking
on .uasset/.umap) plus Steam multiplayer. I also wrote the
C++ graph class behind the spell system — it stores each spell's rune
combination and checks what players draw against them.
Simplicity VTT
A desktop virtual tabletop for D&D-style games: synchronized dual screens (a full-control DM view and a restricted player view), a grid map with drag-and-drop tokens, and a turn-based combat engine resolving attacks against armor class.
I designed the three-tier layered architecture and a Dispatcher pattern with role-specific interfaces to enforce DM-vs-player permissions, and I authored the package, class, and sequence diagrams. Built test-first with JUnit and PR code reviews.
Roguelike Deck-Builder
A 2D deck-builder inspired by Slay the Spire, with working turn-based combat: a playable hero, a card/mana/hand system, targeting modes, status effects (burn/DoT), and a conditional perk system.
Built around an event-driven Action System. A central dispatcher runs each action through pre, perform, and post phases, so combat systems react to events without referencing each other. Content (cards, enemies, perks) is data-driven via ScriptableObjects, authored as assets rather than code.
Multiplayer Volleyball
A networked multiplayer volleyball game with bumping, setting, and spiking. The ball, players, and score stay synchronized across connected instances, with auto team assignment and serve rotation.
