RunestoneMMO

📌 Recommended Group Structure

For the cleanest setup with LuckPerms, use:

• default → normal players
• mod → moderation staff
• admin → administrators
• mod inherits default
• admin inherits mod

This is the recommended layout instead of relying only on vanilla /op.

👤 Default Player Permissions

These are the recommended permissions for your basic default players:

/lp group default permission set runestone.skills true
/lp group default permission set runestone.chat true
/lp group default permission set runestone.combat.xp true
/lp group default permission set runestonecore.home.use true
/lp group default permission set runestonecore.claims.use true
/lp group default permission set runestonecore.playtime.use true
/lp group default permission set runestonecore.scoreboard.see true
/lp group default permission set runestonecore.scoreboard.use true
/lp group default permission set runestonecore.items.use true
/lp group default permission set runestonecore.towns.use true
/lp group default permission set runestonecore.daily.use true
/lp group default permission set runestonecore.resources.use true
/lp group default permission set runestonecore.holograms.use true
/lp group default permission set runestonecore.spawn.use true
/lp group default permission set runestonecore.back.use true
/lp group default permission set runestonecore.economy true
/lp group default permission set runestonecore.tpa.use true

✅ Includes access to

• Skills display
• Main chat/channel usage
• Combat XP
• Homes
• Claims
• Playtime
• Scoreboards
• Items / player-facing item tools
• Towns
• Daily rewards
• Resources / HUD features
• Holograms (basic player usage)
• Spawn
• Back
• Economy commands
• TPA / teleport request usage

🛡️ Moderator Group Setup

First create the moderator group and make it inherit the default group:

/lp creategroup mod
/lp group mod parent add default

Then apply the moderation/staff permissions:

/lp group mod permission set runestonecore.moderation true
/lp group mod permission set runestonecore.cooldown.view true
/lp group mod permission set runestonecore.playtime.others true
/lp group mod permission set runestonecore.staffchat.use true
/lp group mod permission set runestonecore.staffchat.see true
/lp group mod permission set runestone.staffchat true
/lp group mod permission set runestonecore.staff.alert true
/lp group mod permission set runestone.staff.alert true
/lp group mod permission set runestonecore.tpa.bypass_toggle true

✅ Intended moderator access

• Staff chat
• Moderation suite
• Cooldown viewing
• Viewing other player playtime
• Staff alerts
• Teleport-request bypass tools where needed
• General staff utility permissions

👑 Admin Group Setup

First create the admin group and make it inherit the mod group:

/lp creategroup admin
/lp group admin parent add mod

Then apply the admin permissions:

/lp group admin permission set runestonecore.admin true
/lp group admin permission set runestonecore.admin.reload true
/lp group admin permission set runestone.combat.debug true
/lp group admin permission set runestonecore.claims.bypass true
/lp group admin permission set runestonecore.claims.admin true
/lp group admin permission set runestonecore.economy.admin true
/lp group admin permission set runestonecore.worldrules true
/lp group admin permission set runestonecore.worldrules.reload true
/lp group admin permission set runestonecore.market.admin true
/lp group admin permission set runestonecore.items.give true
/lp group admin permission set runestonecore.items.admin true
/lp group admin permission set runestonecore.towns.create true
/lp group admin permission set runestonecore.towns.admin true
/lp group admin permission set runestonecore.towns.treasury.withdraw true
/lp group admin permission set runestonecore.towns.upgrade true
/lp group admin permission set runestonecore.resources.admin true
/lp group admin permission set runestonecore.holograms.admin true
/lp group admin permission set runestonecore.holograms.leaderboard true
/lp group admin permission set runestonecore.holograms.bypass_cost true
/lp group admin permission set runestonecore.perms.list true
/lp group admin permission set runestonecore.spawn.set true
/lp group admin permission set runestonecore.world.creative_flat.access true
/lp group admin permission set runestonecore.tpa.admin true
/lp group admin permission set runestonecore.teleport.bypass_cost true
/lp group admin permission set runestonecore.hud.bypass_gamemode_enforce true

✅ Intended admin access

• Full subsystem administration
• Core reload access
• Claim bypass and claim administration
• World rule controls
• Market administration
• Item give/admin tools
• Town administration
• Resource administration
• Hologram administration
• Spawn management
• Permission inspection tools
• Dev-flat access
• Teleport/mana-cost bypass controls
• HUD enforcement bypass
• Full admin utility coverage

⚔️ Moderation Parent Permission

RunestoneCore uses the following parent moderation node:

runestonecore.moderation

This is intended to cover the moderation suite, including things such as:

• Kick / ban / tempban
• Mute / tempmute / unmute / warn
• Jail / unjail / jail management
• Freeze / unfreeze
• History / pardon / staff notes
• Reports
• Staff utility tools
• Chat moderation
• Alerts and staffchat-related tools
• Broadcast tools

Because of that, you usually do not need to add every single moderation node one by one if you already grant:

/lp group mod permission set runestonecore.moderation true

💬 Chat / Channel Notes

RunestoneCore currently uses:

runestone.chat

for the main /channel command.

That covers the player-facing chat channel system, including the current direction of:

• global as the main server chat
• local chat
• party chat
• staff chat routing

For staff chat access, the code currently accepts any of the following:

runestone.staffchat
runestonecore.staffchat.use
runestonecore.staffchat.see

For the cleanest staff setup, the recommended mod/admin examples above grant the compatible nodes directly.

🏘️ Town / Village Notes

The current codebase uses town permissions under:

runestonecore.towns.use
runestonecore.towns.create
runestonecore.towns.admin
runestonecore.towns.treasury.withdraw
runestonecore.towns.upgrade

These are the correct nodes to keep using for the unified town direction, even while command cleanup continues around /town and /village.

👥 Party / Team Notes

Party/team chat currently sits under the chat/channel flow rather than a fully separate public permission family.

For player access, the important permission is still:

runestone.chat

That is the node players need for channel switching, including the current party channel direction while party/team handling is being unified.

📢 Broadcast / Announcement Notes

Broadcast access is controlled through the moderation/server permission tree and directly by:

runestonecore.moderation.broadcast

If you grant the moderator parent node:

runestonecore.moderation

that already includes broadcast access through the declared permission tree.

🧭 Teleport / Devflat Notes

The staff creative/dev world permission is:

runestonecore.world.creative_flat.access

This is the node used for /devflat.

Additional code-used teleport-related nodes include:

runestonecore.tpa.use
runestonecore.tpa.bypass_toggle
runestonecore.tpa.admin
runestonecore.teleport.bypass_cost

➕ Assigning Players to Groups

Use these commands to place players into their groups:

/lp user YourName parent add default
/lp user YourName parent add mod
/lp user YourName parent add admin

Replace YourName with the player’s Minecraft username.

📌 Notes

• This page is for RunestoneCore only.
• runestone.skills is still included here because RunestoneCore declares and uses it for /skills.
• RunestoneSkills-only admin nodes are intentionally not included on this page.
• The current codebase uses a few important permission checks that are used in code/config even if not fully documented in plugin.yml, including:

runestonecore.tpa.use
runestonecore.tpa.bypass_toggle
runestonecore.tpa.admin
runestonecore.cooldown.view
runestonecore.teleport.bypass_cost
runestonecore.hud.bypass_gamemode_enforce
runestone.staff.alert

• Economy note: in the current snapshot, runestonecore.economy is declared as default: op in plugin.yml, but on a real server you will usually want to grant it to the default group so players can use economy commands like /balance, /pay, /bank, /exchange, /ah, and /market.
• Staff alert note: the staff alert system currently falls back to runestone.staff.alert, so granting both runestonecore.staff.alert and runestone.staff.alert to staff/admins is the safest setup.
• Legacy note: some code still checks runestone.core.admin as a fallback, but the main declared admin node is runestonecore.admin.

✅ Recommended Final Layout

For most servers, this is the cleanest permission structure:

• default → regular players
• mod → moderation team
• admin → full administrative access

This gives you better control, cleaner scaling, and easier long-term management than relying only on /op.