Game Stages Mod — Configuration
Commands
Game Stages provides a robust set of commands for administrators (Op Level 2) and players (Op Level 0) to manage progression data.
| Command | Op Level | Description |
|---|---|---|
/gamestage add <player> <stage> (silent) |
2 | Grants a stage to the specified player. If 'silent' is used, the player receives no chat notification. |
/gamestage remove <player> <stage> (silent) |
2 | Revokes a stage from the player. |
/gamestage info (player) |
0 | Lists all stages currently held by the player. |
/gamestage check <player> <stage> |
2 | Returns a true/false check if the player has the specified stage. |
/gamestage clear (player) |
2 | Wipes all stage data from the player. |
/gamestage all (player) |
2 | Grants every stage defined in the known_stages.json file to the player. |
/gamestage reload |
2 | Reloads the configuration files and known stages list. |
Configuration
The mod uses two primary JSON configuration files located in the ~/config/gamestages/ directory.
Known Stages (known_stages.json)
While stages are created dynamically, listing them here is highly recommended. This file enables tab-completion for commands and prevents typos by issuing warnings for undefined stages.
Example:
[
"stone_age",
"iron_age",
"magic_tier_1"
]
Fake Players (fake_players.json)
Fake players (used by machines and automation mods) cannot naturally unlock stages. This file allows you to define default stages for specific fake player entities so they can interact with staged blocks or items.
Example:
[
{
"fakePlayerName": "[BuildCraft]",
"stages": ["industrial_age"]
}
]