Learning Game Engine
A game engine I built for one-hour learning games, where each game is a pack of content dropped onto the same board.
- Modules in the first game
- 5
- Interactive beats to play
- 40
- To pass the final check
- 9 of 10
React, TypeScript, three.js, Zustand, SCORM 1.2, xAPI
The first simulation training game I made was about industrial bearings, and I made it from scratch. It shipped, subject-matter experts reviewed it, and it runs inside a learning management system (LMS). Getting there meant solving a list of problems that have nothing to do with bearings: scoring, saving progress, resuming where the learner stopped, and packaging the game so that an LMS can launch it and record a result. I did not want to solve them a second time. I finished the flagship first and then took the engine out of what was actually there.
What I built
There is one engine, and each game is a pack that sits on it.
- The engine never learns the topic
- It moves the learner through modules and beats, keeps a ledger of their decisions, scores them against a weighted rubric, opens the next module only on a pass and runs the final assessment. It also packages the game in SCORM, the standard format an LMS uses to launch a course and record the score.
- A content pack is the game
- The pack holds the beats, the rules, the questions and every word the learner reads.
- A brand pack is the look
- Colours, fonts and logos live in their own folder, and re-branding a game for another client means adding a new folder.
How a game teaches
- Beats
- A game has beats where a course has slides. A beat is one screen with one job: brief, teach, decide or judge.
- Teach before test
- Every assessed beat opens by teaching, and a learner is never asked about something the game has not taught. That was the number one issue in the first version of the flagship.
- One rule for each module
- If I cannot name a module’s one rule, the module is not designed yet.
- A wrong call costs, and the learner keeps moving
- The engine logs a wrong decision with a damage weight and plain feedback. At the verdict the game plays the learner’s own setup back to them, and a failure goes through a post-mortem before a retry.
- Critical decisions fail the module on their own
- That includes a critical decision the learner skipped.
What it delivers
Two games run on the engine. The first is a deliberately thin one about setting up a ladder, and its job is to exercise every mechanism once. The second is a full one-hour game with five modules, 40 beats and a ten-question final check where nine are needed to pass.
