LevelKit-Text Ready for Year 8 Rotations
TL;DR
Shipped the first classroom-ready version of LevelKit-Text on January 16, 2026 so it was ready for the start of the Year 8 rotations.
Benjamin Hyde
Education Leader & AI Builder
LevelKit-Text reached its first classroom-ready version on January 16, 2026, timed for the start of our Year 8 rotations. The goal was to build something that gave students the fun of creating a text adventure game without the usual setup friction or the overhead of building an engine from scratch.
Text adventures are a strong entry point for younger students because they combine story, logic, and programming in a way that feels immediately creative. The problem is that if students have to build every system themselves, too much time disappears into scaffolding. LevelKit-Text was my attempt to solve that by providing the engine and letting students focus on the game content.
What shipped
The first version shipped with the core pieces needed for classroom use: room navigation, branching options, turn-based combat, inventory, XP levelling, save and load, and a structured way for students to create content without touching the underlying engine.
The other major goal was keeping it zero-dependency. Everything runs on Python's standard library, which matters in a school environment where install friction can kill momentum before a lesson even starts.
Why it mattered
The real value of the project is the separation between engine code and student-editable content. Students can work on rooms, battles, items, and story flow while the heavier systems stay stable underneath. That makes the project much more achievable for a Year 8 rotation.
It also gave me a reusable framework instead of rebuilding a fresh game project every time the rotation came around. Once the structure was in place, the class could spend more time designing games and less time fighting boilerplate.
Build Notes
Approach
Build a classroom-ready text adventure framework that gave Year 8 students a working engine while keeping their authoring work focused on content rather than systems code.
Tools Used
Python, Tkinter, dataclasses, JSON, importlib
What Worked
The engine-content split made the project far more teachable, and the zero-dependency approach made it realistic for school deployment.
What Failed
Balancing flexibility with simplicity was still the hard part. Every extra feature risked making the content layer harder for younger students to understand.
What's Next
Refine the classroom materials, improve the validator tooling, and keep tightening the path from Year 8 LevelKit-Text into the later LevelKit Platform work.