Skip to main content

Blacklist Configuration

Configure player and item blacklists.

Blacklist Settings​

blacklist:
  enabled: true
  players: []
  items: []

Player Blacklist​

enabled​

Type: Boolean
Default: true
Description: Enable blacklist system

players​

Type: List of Strings
Default: []
Description: List of blacklisted player UUIDs or names

Examples:

blacklist:
  enabled: true
  players:
    - "550e8400-e29b-41d4-a716-446655440000"  # UUID
    - "PlayerName"                              # Name

Behavior:

  • Blacklisted players cannot create orders
  • Blacklisted players cannot deliver to orders
  • Can use UUID or player name

Item Blacklist​

items​

Type: List of Strings
Default: []
Description: List of blacklisted item materials

Examples:

blacklist:
  enabled: true
  items:
    - BEDROCK
    - BARRIER
    - COMMAND_BLOCK
    - SPAWNER

Note: Shulker boxes and bundles are hardcoded as blocked and cannot be ordered.

Hardcoded Blocked Items​

These items are always blocked (cannot be ordered):

  • All shulker box variants
  • Bundle

This prevents data loss and exploits.

Configuration Examples​

Basic Blacklist​

blacklist:
  enabled: true
  players: []
  items:
    - BEDROCK
    - BARRIER

Comprehensive Blacklist​

blacklist:
  enabled: true
  players:
    - "problem-player-uuid"
  items:
    - BEDROCK
    - BARRIER
    - COMMAND_BLOCK
    - SPAWNER
    - STRUCTURE_BLOCK

Disabled Blacklist​

blacklist:
  enabled: false
  players: []
  items: []

Managing Blacklist​

Adding Players​

Edit config.yml:

blacklist:
  players:
    - "player-uuid-or-name"

Then reload: /orders reload

Removing Players​

Remove from config.yml and reload.

Adding Items​

Edit config.yml:

blacklist:
  items:
    - ITEM_NAME

Then reload: /orders reload

Best Practices​

  1. Use UUIDs: More reliable than names (names can change)
  2. Document Reasons: Keep notes of why players/items are blacklisted
  3. Regular Review: Review blacklist periodically
  4. Test Changes: Test blacklist changes before production