A one-person studio building games across action, horror, and serious play
JugPanda Studios started in educational game research, but the current identity is broader: a flagship action game, browser-native multiplayer experimentation, and focused prototypes that prove whether a mechanic deserves to grow.
The studio story
The first big question was whether games could teach well without becoming dry, manipulative, or overly abstract. That work became Coco Crunchers — a multi-year educational platformer that was both research and a real shipped release.
That foundation still matters, but the modern studio picture is more varied: a flagship action game, a browser-native horror direction, and interactive training experiments that are described publicly at a higher level than before.
In practice, JugPanda Studios behaves like a compact game R&D lab: some projects aim at larger-scale commercial identity, some validate mechanics quickly, and some turn specialized expertise into something playable.
What defines the work
Flagship ambition: bigger-scope action that feels market-facing instead of archival.
Prototype discipline: smaller experiments earn their keep by proving a mechanic, loop, or training pattern.
Selective visibility: the site stays honest about what is active without publishing every useful in-development detail.
Current slate
The clearest public windows into what the studio is building right now
Current flagship
VEILBREAK
A larger-scale sci-fi action project that currently leads the studio's public slate.
Browser horror prototype
WHISPER
A browser-native horror experiment focused on atmosphere, tension, and cooperative play.
Training sim experiment
Checkride
A serious-game prototype exploring interactive training and replayable decision-making.
Core values
Principles that carry across every game, prototype, and experiment
Research-Informed
Testing, learning outcomes, and player behavior still shape decisions — even when the work shifts toward more commercial game feel.
Player-First
The goal is playable, readable, pressure-tested work, not design theory that only sounds good in a pitch paragraph.
Experimental
Small prototypes answer hard questions quickly, then the strongest mechanics survive into larger builds.
Intentional
Each project needs a clear reason to exist: sharpen a genre hook, prove a system, or solve a specific training problem.
Technical range
The engines, languages, and systems currently showing up across the studio’s work