HSTG: Permissions

HSTG: Permissions is an addon for History Stages that ties commands to stages. Put /gamemode creative into a stage and only players who have that stage can use it, operators included. Put /kick and /tp into a “Moderator” stage and whoever gets it can use them without being an operator.

Think of it as a lightweight alternative to LuckPerms, built for servers that already run History Stages. Your roles are stages, an entry is written the way you type the command, and everything is set up in the same editor as the rest of your pack. No extra permission plugin, no web editor, no group files.

• 📖 Wiki — how entries work, the editor, ranks, config & known limits
• 💬 Discord — support & questions (the History Stages server)
• 🐛 Issue Tracker — bug reports & feature requests

🔑 One Rule

A command entry belongs to its stage. That’s it:

• Whoever has the stage may use the command, operator or not
• Everyone else may not, operators included
• A command no stage names follows Minecraft’s own rules

For a global stage that means once the world has it, for an individual stage once the player has it. Gaining or losing a stage changes what a player may use right away, no relogging.

📝 Entries

Entries are written the way you type the command, and each one covers everything after it:

• minecraft.gamemode.creative — locks creative mode, leaves /gamemode survival alone
• minecraft.tp — the whole /tp command
• minecraft.* — every vanilla command
• ftbquests.* — everything from FTB Quests
• * — every command. A stage with * gives its holders everything and takes nothing from anyone else. Handy for an admin role

🛡️ Safe by Default

A stage that hands out /op would be a backdoor, so some commands have special rules:

• Protected list — op, stop, ban, execute, whitelist and a few more can only be taken away, never handed out, not even through *. The list is editable in the config
• Never lockable — the commands of History Stages and this addon can’t be taken away, so you can never lock yourself out of /history
• Never checked — the console, command blocks and functions always run everything

The editor and /hstgperms check both tell you when an entry hits one of these rules.

⌨️ What Players See

• Tab completion only suggests commands the player may use
• /gamemode only suggests the game modes they may switch to
• F3+F4 and F3+N grey out and skip the modes they may not use
• A configurable message names the stage a locked command needs (or ??? if the stage is hidden)

🏷️ Ranks

An individual stage can carry a prefix and suffix, like [Admin] Steve, with colour codes and a priority. It shows in chat, the tab list and on name tags, and updates as soon as a player gains or loses the stage. Prefix and suffix are picked separately, so a donor suffix and an admin prefix can show at the same time.

🛠️ Built Into the Editor

Every stage gets a Commands tab in the History Stages editor:

• A searchable tree of every command on the server, grouped by mod (@ftbquests filters to one mod)
• Tick a command, a subcommand or a whole mod
• Typos and commands from missing mods show up in yellow
• Aliases like tp and teleport count as the same command

The protected list and the locked message live in an HSTG: Permissions section of the History Stages config editor.

🔍 Debugging

• /hstgperms check <player> <command> — may this player run this, and which stage decides?
• /hstgperms verbose on [player] — one chat line for every command players run, live, with the same answer check would give

📦 Dependencies

• History Stages 6.1.0 or newer — required
• NeoForge 1.21.1

❓ FAQ

Does it go on the server or the client?

The server needs it. On the client it’s optional: players without it can join, they just don’t get the editor tab, the greyed out F3+F4 menu or ranks on name tags.

Do I still need LuckPerms?

Not for commands. If all you want is to lock or hand out commands per stage or per role, this covers it.

Can I give a modded command to a non-operator?

Usually yes. Some mods check permissions a second time in their own code, and the addon can’t reach that. Taking those commands away always works, giving them may not. Details in the Limits page.

Why does /tp @p fail for my moderator?

NeoForge wants operator level 2 for selectors like @p and @a. /tp Steve works, /tp @p doesn’t.

Which versions are supported?

• 1.21.1 — NeoForge

Questions or found a bug? Join the Discord or open an issue — we read everything! 🙂