Ages 15–18 · Grades 9–12 · Computer Science

PackForge

Most game content isn’t code — it’s data that has to fit a schema: the right fields, the allowed values, the sane ranges. That contract is what lets thousands of mods load safely. Here you fix broken content packs — an unknown rarity, an impossible stack, clashing ids — until the validator gives you a clean pass. It’s the real discipline behind data-driven modding.

Loading the packs…

A case · you decide

Tomas's mod that crashed the server

Tomas, 16 — writing a content pack of new items for his friends' game server

The idea in play: mods are data: a pack has to fit the schema (types, ranges, unique ids) before the game ever loads it.

Tomas adds a legendary sword with a stack size of 0, a potion that shares an id with an existing potion, and a rarity spelled 'legandary'. The server will not start.

None of these are code bugs. They are data that breaks the rules the game expects.

A schema says what is allowed: stack size between 1 and 64, rarity from a fixed list, every id unique.

What is the most reliable way to find all the problems?

The potion id clashes with an existing one. What is the right fix?

Fix a pack →

What next? Pick a door

Chosen from what this app is about. What you open is remembered on this device only.