Scenario-Based First Aid Training Game with Branching Emergencies and Scoring

The problem: people freeze in emergencies

Most people have never practised what to do when someone chokes, collapses or bleeds heavily. Classroom first aid courses are good but short, expensive per head for employers, and the knowledge fades within months if it is never used. Factories, schools, security companies and ride-hailing fleets are often required or strongly encouraged to have trained staff, yet a certificate says little about whether a person would make the right first three decisions under pressure.

A game is a good fit here because the thing being trained is decision-making under time pressure, not memorising a leaflet.

What already exists and the gap

• Lifesaver by Resuscitation Council UK and UNIT9 is an interactive film that teaches CPR through live-action branching scenarios; there is also a workplace e-learning version.
• British Red Cross First Aid app gives clear step-by-step guidance and quizzes, but it is a reference, not a practice space.
• St John Ambulance and similar bodies offer e-learning modules, mostly slide-and-quiz style.

The gap is a lightweight, offline-capable game that is data-driven (so a trainer can localise emergency numbers, language and scenarios), measures decisions and timing rather than quiz answers, and gives an employer or school a view of where their people go wrong. Live-action film is expensive to localise; a data-driven game with simple 2D or low-poly art is not.

What you build

Learners play five scenarios on an Android phone. Each scenario opens with a scene, a casualty state and a clock. Choices appear as actions (check danger, call for help, back blows, apply pressure, cool the burn). Wrong or slow actions change the casualty state: the bleeding worsens, the choking casualty becomes unresponsive. Every run ends in a debrief that replays the timeline and explains each decision against the guideline.

Instructors create a group, share a join code, and see scores, completion and a ranked list of the most common mistakes across the group. Content authors (your team for now) write scenarios in a JSON format with states, transitions, timers and feedback text in two languages.

The technically interesting part

The scenario engine is the heart of the project. Model each scenario as a timed state machine where the casualty state evolves on its own while the learner acts, so doing nothing is also a choice with consequences. Validate every scenario file at load time: no unreachable states, no dead ends without a debrief, every choice has feedback in every language. Build the debrief from an event log so it can show "you started compressions 40 seconds after collapse" from real data.

The CPR tap mini-game is a small signal-processing problem: compute rate and variability from tap timestamps, ignore double taps, and give feedback that is stable rather than flickering.

How to evaluate it

• Learning: a pre-test, one play session, and a post-test with at least 20 participants; report the mean score change and which topics moved least. If you can, repeat the post-test two weeks later to measure retention.
• Content correctness: have one qualified first aid trainer review every scenario and record their corrections.
• Engine quality: automated tests that load every scenario and walk every branch to an ending.
• Usability: completion rate and time per scenario, plus a short questionnaire on confidence to act.

Suggested plan

1. Weeks 1 to 3: pick the guideline source you will follow, write the five scenarios on paper, get them reviewed.
2. Weeks 4 to 8: scenario data format, validator and the state machine engine with placeholder art.
3. Weeks 9 to 14: first two scenarios playable end to end with debrief; pilot with 5 people.
4. Semester 2, weeks 1 to 6: remaining scenarios, CPR mini-game, Urdu text and audio.
5. Weeks 7 to 10: instructor view, groups and sync.
6. Weeks 11 to 14: learning study, trainer review, report and demo.

Path to a product

The first customer is a company that already pays for annual first aid training, such as a factory, a school chain or a security firm, using the game as refresher training between classroom sessions. Price per learner per year, with instructor dashboards included. A second channel is licensing the engine to first aid training providers who want a branded version in their own language. The scenario format is the asset: it lets you add languages and new emergencies cheaply.

Scope warning

Do not write your own medical content from scratch without a qualified reviewer, and do not claim the game certifies anyone. Skip 3D characters with facial animation, VR and multiplayer. Five well-reviewed scenarios with a solid engine and a real learning study are a complete project.

Learn what you need on Sefism

• Godot Engine Documentation : scenes, signals and exporting to Android.
• Game Programming Patterns : the state pattern and event queues your scenario engine needs.
• Mobile roadmap : shipping, testing and updating an Android app properly.
• Firebase Documentation : authentication and sync for groups and scores.
• Programming cheat sheet : clean data structures for states and transitions.

Get help with this idea

The hard calls here are which guideline to follow and how to test learning honestly. Bring your proposal and we can agree the scope, pick a stack your team can finish with, and design an evaluation your panel will respect. You build it; we help you make the calls.

• Discuss this idea with a mentor
• Send a query to Tauseef
• Book a 1:1 session

New here? Create a free account first.