Hytale Permission Nodes: Complete List & Explanation

Understanding Permission Node Structure

Before diving into the full list, let's understand how permission nodes are structured in Hytale and HyperPerms.

Node Naming Convention

Permission nodes follow a hierarchical dot notation:

<plugin>.<category>.<action>

For example:

• hytale.chat.send — Hytale plugin, chat category, send action
• hyperperms.group.create — HyperPerms plugin, group category, create action

Wildcard Permissions

The asterisk (*) acts as a wildcard:

• hytale.chat.* — All chat-related permissions
• hyperperms.* — All HyperPerms permissions
• * — Every permission (use with extreme caution!)

Permission Values

Permissions can be:

• true — Grants the permission
• false — Explicitly denies the permission (overrides inheritance)

Denying a permission with false is powerful for exceptions. If moderators have hytale.teleport.* but shouldn't teleport to spawn, set hytale.teleport.spawn: false.

---

Core Hytale Permissions

These are the fundamental permissions for basic gameplay.

Building & World Interaction

Chat & Communication

Movement & Teleportation

---

Moderation Permissions

Permissions for staff members managing players.

Player Management

Server Monitoring

---

Administrative Permissions

High-level permissions for server administrators.

Server Control

World Management

Game Control

---

HyperPerms Plugin Permissions

Permissions specific to managing HyperPerms itself.

Group Management

User Management

System Permissions

---

Context-Specific Permissions

HyperPerms supports context-aware permissions that only apply in certain situations.

World Contexts

Apply permissions only in specific worlds:

/hp user Player permission set hytale.fly true world=creative

Now the player can only fly in the "creative" world.

Gamemode Contexts

Apply permissions based on gamemode:

/hp group builder permission set hytale.fly true gamemode=creative

Time-Based Contexts

Apply permissions during certain times:

/hp group vip permission set hytale.bonus.* true time=night

---

Best Practices for Permission Assignment

Start Restrictive

Begin with minimal permissions and add more as needed. It's easier to grant permissions than to revoke them after players are used to having them.

Use Groups, Not Individual Permissions

Instead of giving each player permissions directly, always use groups. This makes management scalable.

Document Your Setup

Keep notes on what each custom permission does and which groups have them. Future you will thank present you.

Test Before Deploying

Use HyperPerms' check command to verify permissions:

/hp user check PlayerName hytale.fly

---

Quick Reference Card

Essential Player Permissions:

• hytale.build, hytale.chat, hytale.teleport.home

Essential Moderator Permissions:

• hytale.kick, hytale.mute, hytale.ban.temporary

Essential Admin Permissions:

• hytale.ban, hytale.gamemode, hyperperms.user.*

Essential Owner Permissions:

• hyperperms.admin, hytale.stop, * (full access)

For a searchable, filterable list of all permissions, try HyperPerms' visual editor which includes a complete permission database with descriptions and categories.