Game Stages Mod FAQ

Create a stage with the stage creation command, then assign it to yourself or a player using the add-stage command. Once a stage exists, you can attach locks to it via the config files or the in-game lock commands.

A stage is a named flag a player either has or doesn't have, while a lock is a rule that checks for a stage before allowing something like using an item or crafting a recipe. You create stages first, then attach locks that reference those stage names.

Use the stage check command targeting the player, which lists every stage they currently hold. You can also check a single stage to get a simple yes/no result.

The most common cause is a typo or case mismatch between the stage name in the lock and the stage name you created. Reloading the config or restarting the world after editing lock files also fixes most cases where changes don't apply.

Yes, stages are stored per-player and persist through death, respawn, and dimension travel. They are tied to the player's data, not their inventory or location.

Yes, recipe locks and item locks are separate. You can gate a crafting recipe so it can't be made until a stage is granted, while still letting players use the item if they obtain it another way.

Game Stages itself only stores and checks stages; automatic granting is done by other mods or by command blocks and functions that run the add-stage command. Pair it with a questing or advancement mod to trigger stage grants on events.

Yes, stages are tracked per player, so each player progresses independently. Server operators manage stages through the same commands, and locks apply globally based on each player's own stage list.

Stage checks are lightweight and run only when relevant actions happen, so typical packs with hundreds of locks see no noticeable impact. Extremely large lock lists can add minor overhead during recipe and inventory checks, but it's rarely significant.

Yes, the remove-stage command takes a stage away from a player, and any locks tied to that stage immediately apply again. This is useful for testing or for resetting progression on a server.

It is a progression framework that locks items, blocks, mobs, and recipes behind configurable stages, unlocking content as players advance. It provides an API for modpacks and other mods to build stage-based progression systems.

The main way to interact with it is through the commands it adds. The gamestage command adds or removes a stage from a player, and the stageinfo command lists all stages you have unlocked in chat.

It adds gamestage, which takes a player name (or @p), add or remove, and a stage name, and stageinfo, which lists your unlocked stages in chat. It also adds /gamestage reloadfakes.

Use the gamestage command with the player name, then add or remove, then the stage name. Trying to add a stage with a name that does not exist will create the stage.

Use the stageinfo command. It has no parameters and lists all the stages you have unlocked in chat.

The mod file lists Minecraft 1.20.1 with Forge. The Modrinth page lists 1.19.2, 1.19.4, 1.20, 1.20.1, 1.20.2, and 1.20.3, and the 9Minecraft article lists versions from 1.12.2 up to 1.20.4.

No. Stages are non-linear, and players can gain or lose stages at any time. They can be used for linear quest progression, branching quests, RPG classes, pack modes, and more.

Yes. It provides a stage API that lets other mods hook into stages, and it handles the player save data and packets required for stages.

It provides the foundation for stage-based progression systems, where content is made available depending on which stages a player has unlocked. Pack creators decide how to organize their stages, such as for quest progression, RPG classes, or expert, hardcore, and easy pack modes.