Permission Condition

The Permission condition allows you to create custom join and leave messages for players who have a specific permission node.

Overview

This is one of the most commonly used conditions, perfect for creating VIP, staff, or rank-based messages.

Configuration

To create a permission condition, set the type to PERMISSION and provide the permission node as the value.

Basic Example

conditions:
  permissionExample:
    type: PERMISSION
    value: "example.permission"
    join: "&e&lVIP &7{player} joined!"
    leave: "&e&lVIP &7{player} left!"

How It Works

When a player joins or leaves:

RocketJoin checks if the player has the specified permission
If they do, the custom message is displayed
If they don’t, the default message (or next matching condition) is used

Real-World Examples

VIP Players

conditions:
  vip:
    type: PERMISSION
    value: "rocketjoin.vip"
    join: "&e&l» &6&lVIP &7{player} joined!"
    leave: "&e&l» &6&lVIP &7{player} left!"
    sound: true
    sound-type: "entity.experience_orb.pickup"

Staff Members

conditions:
  staff:
    type: PERMISSION
    value: "rocketjoin.staff"
    join: "&b&l[STAFF] &7{player} joined!"
    leave: "&b&l[STAFF] &7{player} left!"
    sound: true
    sound-type: "entity.player.levelup"

Administrators

conditions:
  admin:
    type: PERMISSION
    value: "rocketjoin.admin"
    join: "&c&l[ADMIN] &7{player} joined!"
    leave: "&c&l[ADMIN] &7{player} left!"
    sound: true
    sound-type: "ui.toast.challenge_complete"
    fireworks: true
    fireworks-amount: 3

Permission Node Best Practices

Use descriptive permission nodes that follow a clear hierarchy:

rocketjoin.vip - For VIP players
rocketjoin.staff - For staff members
rocketjoin.admin - For administrators
rocketjoin.moderator - For moderators

Combining with Other Options

You can combine permission conditions with sounds, fireworks, and commands:

conditions:
  premium:
    type: PERMISSION
    value: "rocketjoin.premium"
    join: "&6&l[PREMIUM] &7{player} joined!"
    leave: "&6&l[PREMIUM] &7{player} left!"
    sound: true
    sound-type: "entity.experience_orb.pickup"
    fireworks: true
    fireworks-amount: 5
    commands:
      - "say Welcome back, {player}!"

Priority Considerations

Remember that conditions are evaluated in order. If a player has multiple permissions, the first matching condition will be used. Example:

conditions:
  vip:
    type: PERMISSION
    value: "rocketjoin.vip"
    join: "&eVIP {player} joined!"
  
  premium:
    type: PERMISSION
    value: "rocketjoin.premium"
    join: "&6PREMIUM {player} joined!"

If a player has both permissions, they’ll see the VIP message because it’s listed first.

Conditions Overview - Learn about all condition types
First Join Condition - First join condition
Configuration - General configuration guide

RocketJoin

RocketPlaceholders

MultiLang

Permission Condition

Permission Condition

Overview

Configuration

Basic Example

How It Works

Real-World Examples

VIP Players

Staff Members

Administrators

Permission Node Best Practices

Combining with Other Options

Priority Considerations

​Permission Condition

​Overview

​Configuration

​Basic Example

​How It Works

​Real-World Examples

​VIP Players

​Staff Members

​Administrators

​Permission Node Best Practices

​Combining with Other Options

​Priority Considerations

​Related Guides

Permission Condition

Overview

Configuration

Basic Example

How It Works

Real-World Examples

VIP Players

Staff Members

Administrators

Permission Node Best Practices

Combining with Other Options

Priority Considerations

Related Guides