First Setup

This guide walks you through setting up your first groups, creating a rank hierarchy, and assigning permissions to players.

Understanding the Default State

After installation, HyperPerms creates a single group called default. All new players are automatically assigned to this group. Let's build on this foundation.

Planning Your Rank Structure

Before creating groups, plan your rank hierarchy. A typical server might have:

Owner (weight: 100)
  ↑
Admin (weight: 90)
  ↑
Moderator (weight: 50)
  ↑
VIP (weight: 20)
  ↑
Default (weight: 0)

Higher weight means higher priority. When a player has multiple groups, the highest-weight group determines their prefix/suffix display.

Step 1: Create Your Groups

Let's create a basic rank hierarchy:

Step 2: Set Group Weights

Assign weights to establish priority (higher = more important):

Step 3: Set Up Inheritance

Make each rank inherit from the one below. This way, admins automatically get all moderator permissions, moderators get all VIP permissions, and so on.

Step 4: Configure Display Names and Prefixes

Make your ranks visually distinct in chat:

Step 5: Add Basic Permissions

Default Group Permissions

Basic permissions for all players:

VIP Group Permissions

Extra perks for VIP players:

Moderator Group Permissions

Moderation tools:

Admin Group Permissions

Server administration:

Owner Group Permissions

Full server control:

Step 6: Assign Players to Groups

Now add players to their appropriate ranks:

Step 7: Test Your Setup

Verify permissions are working correctly:

With verbose mode enabled, you'll see every permission check in chat, making it easy to debug issues.

Example: Complete Setup Script

Here's all the commands in order for a fresh server:

# Create groups
/hp group create vip
/hp group create mod
/hp group create admin
/hp group create owner

# Set weights
/hp group setweight default 0
/hp group setweight vip 20
/hp group setweight mod 50
/hp group setweight admin 90
/hp group setweight owner 100

# Set up inheritance
/hp group addparent vip default
/hp group addparent mod vip
/hp group addparent admin mod
/hp group addparent owner admin

# Set prefixes
/hp group setprefix default "&7"
/hp group setprefix vip "&a[VIP] "
/hp group setprefix mod "&9[Mod] "
/hp group setprefix admin "&c[Admin] "
/hp group setprefix owner "&4[Owner] "

# Default permissions
/hp group addpermission default chat.use true
/hp group addpermission default teleport.spawn true

# VIP permissions
/hp group addpermission vip chat.color true
/hp group addpermission vip home.multiple true

# Mod permissions
/hp group addpermission mod mod.kick true
/hp group addpermission mod mod.mute true

# Admin permissions
/hp group addpermission admin mod.ban true
/hp group addpermission admin hyperperms.user true

# Owner permissions
/hp group addpermission owner * true

Common Setup Patterns

Donor Ranks Separate from Staff

Keep donation ranks and staff ranks in separate inheritance chains so donors don't automatically get staff permissions:

# Staff track
default → helper → mod → admin → owner

# Donor track
default → vip → vip+ → mvp

# Player can have both: mod + vip+
# They get permissions from both chains

World-Specific Permissions

Use contexts for permissions that only apply in certain worlds:

# Allow building only in creative world
/hp group addpermission default build.place true world=creative
/hp group addpermission default build.break true world=creative

# Deny building in spawn
/hp group addpermission default build.place false world=spawn

Next Steps

• Learn more about inheritance
• Set up promotion tracks
• Use the web editor for easier management
• Full command reference