Six short RPG Maker games I built to open project-based units for students who were already playing games in class, and who often weren’t there on launch day.
- Project Type: Custom educational game design for project-based learning
- Audience or Client: Students in English 10A and 10B at Rapid City High School, then the alternative program for Rapid City Area Schools
- Role: Designer, developer, and classroom teacher
- Format or Deliverables: Six RPG Maker games, one to open each of three units in English 10A and 10B, each playable offline in about 30 minutes; roughly 80 hours of development in total
The Situation
My students at Rapid City High School, then the district’s alternative program, faced a lot of barriers to starting a new unit together. Attendance was inconsistent, so a launch-day activity would miss part of the class. Permission slips were hard to collect, which ruled out most field trips. Motivation varied widely from student to student. Meanwhile, plenty of them were already trying to play video games during class. I wanted an opening for each project-based unit that students would actually start, and that a student who missed the first day could still pick up later.
The Approach in Brief
I looked at presentations and virtual field trips, and then decided to build the hooks as games. The way I put it to other teachers is that if students are going to be trying to play video games in the classroom, I may as well make them video games that are for the classroom. Each unit opened with a short RPG Maker game that set up the unit’s central problem. The games were party-based, so getting through them took a mix of characters with different strengths, which gave us a way into the group work that each project would ask for. Every game ran offline, downloaded easily, and took about half an hour, so a student could play it whenever they were there.
What Came Out of It
I built six games over roughly 80 hours, one to open each of the three units in English 10A and 10B, and students played them in class as the start of each unit. The most practical result was the one I’d designed for. A student who missed the launch day could play the game when they came back and start the unit from the same place as everyone else, instead of getting a summary from me. I didn’t collect data on engagement or learning, so I can’t say more than that with confidence.
Key Takeaway
A unit hook that lives in a file instead of a single class period is more forgiving of irregular attendance. Building it as a game meant meeting students in something they were already doing.
Deeper Context
Attendance was the constraint that shaped everything else. In a regular classroom, a hook is an event: a demonstration, a discussion, a trip. In an alternative program where any given day might be missing a third of the class, an event-based hook leaves the people who most need a way in without one. A game that each student plays on their own time works more like a reading than a lesson, and it can wait for them.
The technical limits mattered too. The school’s computers varied, and internet access couldn’t be counted on, so the games had to run offline, stay small enough to download, and use controls students would figure out without instruction. RPG Maker fit those limits. Its menus and movement were familiar to anyone who had played a classic role-playing game, and it let me keep one consistent game world across all six games so students could recognize where they were. I wrote the events, story, and educational content myself and used the art that ships with RPG Maker, which let me spend my time on the design rather than on drawing.
The Journey
Each game had three jobs. The first was setting up the unit’s problem in a way students could explore instead of being told about it. The second was refreshing the skills the unit would need, which I built into the environment as things to find and read along the way. The third was rehearsing group work. Players controlled a party, and the characters had different strengths, so the paths through each game depended on how a student used the whole team. That gave us something concrete to come back to in later reflections on how their actual project groups were working.
The game that opened the first unit of English 10A focused on ethics and law. Players ran into a fantasy version of the classic dilemma about stealing medicine to save someone’s life, recast as the theft of a healing herb. To decide what should happen, they could track down “historical” scrolls in the game world that worked as precedents, consider the different characters’ perspectives, and make and defend a decision. That decision became the starting point for the unit’s project work.
The fantasy setting helped with topics that might otherwise feel too close or too preachy. Students could argue about the herb thief more freely than they might about a real person, and then carry that argument into the real-world material in the unit. The games were also designed to be replayed, with more than one way through, so a student who came back to one could try a different approach.
The Work Itself
Both walkthroughs in this case show the English 10A Unit 1 game. The one below gives a fuller look at it, and the original game files for all six games are linked after it.
Original game files (Google Drive)
What I’d Change
The main thing I’d change is how the games connected to the projects that followed. The educational content sometimes sat on top of the game instead of growing out of it, and the link from a game’s problem to the project students then worked on could have been much clearer. I’d design each game backward from its project, so that what students decided in the game was the first real piece of their project work.
I’d also build in more support for reflection. The games gave us a shared experience to talk about, especially around group dynamics, but I relied on weekly reflections to do that work without much structure around them. Short reflection prompts tied to specific moments in each game would have helped.
The technical setup could have been simpler, too. Getting the files onto school computers took more effort than it should have for a half-hour experience. And if I did this again, I’d keep better notes on what students said and how they reacted as they played. The games were an invitation more than an assignment, so I wouldn’t track them like one, but notes on student impressions would have given me something clearer to share than my own memory of how they went.
Connections
For the course these games opened, see Personalized ELA 10: A Flex-Blended, Mastery-Based English Course. For the classroom tool I built with code around the same period, see Reflections on “Why All Teachers Should Code,” Part 0 of the vibe-coding series. For a recent game I designed and wrote but where AI wrote most of the code, the opposite of this project, see Meridian: Narrative Video Game. For how I think about games versus gamification, see The Difference Between a Game and a Badge.
If you’ve built games for your own classroom, I’d like to hear about it. You can reach me at licht.education@gmail.com, and there are more tools, articles, and resources at bradylicht.com.

