Gameplay Systems
Gameplay Systems Loop Lab
You instrument small loops—movement, encounters, economy-adjacent pacing—and learn to read qualitative signals from playtests. Sessions stay grounded in PC input fidelity and desk ergonomics, not mobile assumptions.
KRW 580,000 · informational only on this static site
Request syllabus by email
Features
- Loop teardown worksheets
- Feel-first tuning heuristics for PC input
- Debug overlay habits that do not tank performance
- Playtest script patterns for tiny cohorts
- Telemetry-light observation grids
- Branching experiment backlog format
- Cross-build regression checklist
Outcomes
- Two tightened loops with documented iteration history
- A repeatable playtest ritual for the team
- Shared criteria for when a loop is “ship-candidate”
Mentor of record
Jonas Meyer
Lead game design mentor focused on tactile PC combat and puzzle pacing.
FAQ
Which engines are supported?
Concepts transfer broadly; mentor feedback assumes Unreal or Unity workflows for examples.
Can solo devs join?
Yes, though pair exercises expect you to borrow a friend for one session or use provided sample roles.
Limitations?
We do not cover networked competitive balance at production scale; scope stays local or small-session multiplayer.
Experience notes
-
“The loop teardown worksheet caught a pacing blind spot we had ignored for months.”
-
“Debug overlay habits alone were worth the time; fewer mystery hitches during reviews.”