🎉 Custom Commands v1.1.4 - Folia Player Commands Fix

🐛 Bug Fix: Player-Type Commands on Folia

Fixed the error when using type: "Player" commands on Folia servers.

🔧 What Was Fixed

Folia "Thread failed main thread check: Dispatching command async"

• Error: Thread failed main thread check: Dispatching command async when players used commands with type: "Player"
• Issue: Player-type commands were scheduled on the global region; Folia requires them to run on the entity's region
• Fix: Player-type commands now use EntityScheduler (player's region); console-type commands still use GlobalRegionScheduler
• Impact: Only affected Folia servers using type: "Player" in custom commands

✅ What This Means

• ✅ Player-type commands (e.g. /pomoc, /home) now work on Folia
• ✅ Console-type commands unchanged and still work
• ✅ No config changes needed

📦 Installation

Update to v1.1.4 – existing configs work as before.

Full Changelog:

• Fixed "Dispatching command async" when executing player-type commands on Folia
• Use EntityScheduler for type: "Player", GlobalRegionScheduler for type: "Console" on Folia

🎉 Custom Commands v1.1.3 - Critical Bugfixes

🐛 Bug Fixes: Folia Command Execution & Command Registration

Fixed two critical bugs that were preventing commands from working properly!

🔧 What Was Fixed

1. Folia Command Execution Error

• Error: NoSuchMethodException: io.papermc.paper.threadedregions.scheduler.GlobalRegionScheduler.get(org.bukkit.plugin.Plugin)
• Issue: Commands failed to execute on Folia 1.21.11 servers due to incorrect API method usage
• Fix: Updated to use the correct Folia API: Bukkit.getServer().getGlobalRegionScheduler().run(Plugin, Consumer<ScheduledTask>)
• Impact: This bug only affected Folia 1.21.11+ servers - Paper servers were not affected

2. Command Registration Failure

• Issue: Custom commands weren't registering at all - commands like /discord or /website did nothing
• Symptoms: No errors in console, but commands simply didn't work
• Fix:
  • Fixed command registration logic to properly handle aliases
  • Improved command cleanup before registration (prevents conflicts)
  • Added better debug logging to track registration issues
• Impact: This bug affected all server types - Paper and Folia

✅ What This Means

• ✅ Commands now execute correctly on Folia servers
• ✅ Commands now properly register and work as expected
• ✅ Better error handling and debug logging for troubleshooting
• ✅ No changes needed to your configuration
• ✅ All existing features work as expected

📦 Installation

Simply update to v1.1.3 - your configs work exactly as before!

Full Changelog:

• Fixed NoSuchMethodException when executing commands on Folia 1.21.11+ servers
• Updated Folia API usage to Bukkit.getServer().getGlobalRegionScheduler().run(Plugin, Consumer<ScheduledTask>)
• Fixed command registration failure - commands now properly register
• Improved alias handling - commands work correctly with aliases
• Added better debug logging for command registration
• Improved command cleanup before registration to prevent conflicts
• Enhanced error messages for better debugging

Need help? Join our Discord

🎉 Custom Commands v1.1.2 - Folia Bugfix

🐛 Bug Fix: Folia Command Execution

Fixed a critical bug that prevented commands from executing on Folia servers!

🔧 What Was Fixed

Folia Command Execution Error

• Error: NoSuchMethodException: io.papermc.paper.threadedregions.scheduler.GlobalRegionScheduler.getScheduler()
• Issue: Commands failed to execute on Folia servers due to incorrect API usage
• Fix: Updated to use the correct Folia API: GlobalRegionScheduler.get(plugin).run(Runnable)
• Impact: This bug only affected Folia servers - Paper servers were not affected

✅ What This Means

• ✅ Commands now execute correctly on Folia servers
• ✅ No changes needed to your configuration
• ✅ All existing features work as expected
• ✅ Improved error handling for better debugging

📦 Installation

Simply update to v1.1.2 - your configs work exactly as before!

Full Changelog:

• Fixed NoSuchMethodException when executing commands on Folia servers
• Updated Folia API usage to GlobalRegionScheduler.get(plugin).run(Runnable)
• Improved error messages for better debugging
• This fix only affects Folia servers - Paper/Spigot servers were not impacted

Need help? Join our Discord: https://discord.gg/ypa7Gvn433

🎉 Custom Commands v1.1.1 - Required Arguments & Individual Argument Variables

🚀 New Feature: Required/Optional Arguments

We've added powerful new argument handling features that make commands even more flexible!

✨ New Features

📝 Required Arguments Support

• Mark individual arguments as required using required-args: [0]
• First argument required, second optional? Now possible!
• Perfect for commands like /ah sell <price> [amount]
• Clear error messages when required arguments are missing

🔢 Individual Argument Variables

• New variables: {arg:1}, {arg:2}, {arg:3}, etc.
• Access each argument individually (1-based index)
• {arg:1} = First argument
• {arg:2} = Second argument (empty string if not provided)
• {arg:N} = Nth argument
• {args} = All arguments as string (backward compatible)

📋 Example Usage

ah:
  subcommands:
    sell:                                    # /ah sell <price> [amount]
      arguments:
        required-args: [0]                   # First argument (price) is REQUIRED
        no-arguments: false
      commands:
        - "tellraw {player} [\"\",{\"text\":\"Price: \",\"color\":\"gold\"},{\"text\":\"{arg:1}\",\"color\":\"green\"}]"
        # {arg:1} = price (required)
        # {arg:2} = amount (optional, empty if not provided)

Usage:

• ✅ /ah sell 100 → {arg:1} = "100", {arg:2} = ""
• ✅ /ah sell 100 64 → {arg:1} = "100", {arg:2} = "64"
• ❌ /ah sell → Error: "Usage: /ah sell [amount]"

🔧 Technical Improvements

• Enhanced argument validation system
• Individual argument extraction and processing
• Improved variable replacement in messages and commands
• Better error messages for missing required arguments

📝 What Changed

• Added required-args configuration option
• Implemented individual argument variables ({arg:1}, {arg:2}, etc.)
• Enhanced argument validation to check required arguments
• Updated variable replacement system

🎯 Compatibility

• ✅ Fully backward compatible - All existing {args} usage still works
• ✅ No breaking changes - Existing configurations work as before
• ✅ Optional feature - Only use if you need required/optional arguments

📦 Installation

Simply update to v1.1.1 - no configuration changes needed! Your existing commands will work exactly as before.

Full Changelog:

• Added required-args configuration option for marking individual arguments as required
• Implemented individual argument variables: {arg:1}, {arg:2}, {arg:3}, etc.
• Enhanced argument validation to check for required arguments
• Improved variable replacement system for better argument handling
• Updated documentation with new examples

Need help? Join our Discord: https://discord.gg/2a4a3mWR4r

🎉 Custom Commands v1.1.0 - Folia Support & bStats Integration

🚀 Major Update: Folia Compatibility

We're excited to announce full Folia support! Custom Commands now works seamlessly on both Paper and Folia servers.

✨ New Features

🌿 Folia Support

• Full Folia compatibility - Works on Folia servers without any issues
• Automatic detection and proper scheduler usage
• No configuration needed - it just works!

🔧 Technical Improvements

• Smart Scheduler Detection: Automatically uses the correct scheduler for your server type
• Reflection-based Folia Support: No additional dependencies required
• Improved Error Handling: Better error messages and logging

📝 What Changed

• Added folia-supported: true to plugin.yml
• Implemented Folia scheduler detection in command execution
• Integrated bStats metrics with custom charts
• Enhanced logging for better debugging

🎯 Compatibility

• ✅ Paper 1.21.x: Fully supported
• ✅ Folia 1.21.x: Now fully supported!
• ✅ Backward Compatible: All existing configurations work as before

📦 Installation

Simply update to v1.1.0 - no configuration changes needed! Your existing commands will work exactly as before.

🐛 Bug Fixes

• Fixed scheduler compatibility issues
• Improved command execution reliability

Full Changelog:

• Added Folia server support
• Improved scheduler detection and usage
• Enhanced error handling and logging

Need help? Join our Discord: https://discord.gg/2a4a3mWR4r

I found a major problem in the plugin that was mishandling commands.

Custom Commands Major Update - Arguments, Nesting & Player Validation

🎮 New Features

We've added three powerful features that make custom commands more flexible and user-friendly!

✨ Feature 1: Arguments System

Dynamic Command Arguments

• Add arguments to any custom command or subcommand
• Use {args} variable in messages and commands to access arguments
• Configure whitelists, validation, and required arguments
• Support for arguments with spaces

Configuration:

arguments:
  whitelist: ["hello", "goodbye"]  # Allowed arguments
  whitelist-only: true              # Only allow whitelisted args
  no-arguments: true                 # Allow command without args
  invalid-message: "&cInvalid arguments!"

Example:

say:
  arguments:
    whitelist: ["hello", "goodbye", "help"]
    whitelist-only: true
  commands:
    - "say {player}: {args}"  # Use {args} in commands

✨ Feature 2: Nested Subcommands

Unlimited Command Nesting

• Subcommands can now have their own subcommands (unlimited depth!)
• Perfect for organizing complex command structures
• Each level has its own permissions and messages

Example:

admin:
  subcommands:
    player:
      subcommands:  # Nested subcommands!
        kick:
          commands:
            - "kick {args} Kicked by admin"
        ban:
          commands:
            - "ban {args} Banned by admin"

Usage:

• /admin player kick Steve - Kicks a player
• /admin player ban Steve - Bans a player
• /admin server restart - Restarts the server

✨ Feature 3: Player Arguments (player-args)

Automatic Player Validation

• Mark specific arguments as player names using player-args: [0]
• Automatic validation ensures players exist and are online
• Smart tab-completion shows all online players
• Clear error messages for invalid players

Configuration:

kick:
  arguments:
    player-args: [0]  # First argument = player name
    no-arguments: false
  commands:
    - "kick {args} Kicked by {player}"

Features:

• ✅ Prevents typos and invalid player names
• ✅ Faster command usage with tab-completion
• ✅ Works with nested subcommands
• ✅ Multiple player arguments supported: player-args: [0, 1]

📝 Combined Example

All three features work together perfectly:

admin:
  permission: "customcommands.admin"
  subcommands:
    player:
      permission: "customcommands.admin.player"
      subcommands:  # Nested subcommands
        kick:
          permission: "customcommands.admin.player.kick"
          arguments:
            player-args: [0]  # Player validation
            no-arguments: false
          commands:
            - "kick {args} Kicked by {player}"

Usage: /admin player kick Steve

• Uses nested subcommands (admin → player → kick)
• Validates that Steve is a valid online player
• Executes the kick command with the player name

🎯 Benefits

Arguments System:

• ✅ Flexible command input
• ✅ Input validation
• ✅ Whitelist support
• ✅ Use arguments in messages and commands

Nested Subcommands:

• ✅ Better command organization
• ✅ Unlimited nesting depth
• ✅ Individual permissions per level
• ✅ Clean command structure

Player Arguments:

• ✅ Automatic player validation
• ✅ Tab-completion for players
• ✅ Error prevention
• ✅ Better user experience

Full Changelog:

• Added arguments system with whitelist and validation support
• Implemented nested subcommands (unlimited depth)
• Added player-args configuration for automatic player name validation
• Implemented automatic tab-completion for player arguments
• Added player-specific error messages
• Fixed spam issue with tellraw commands
• Improved argument handling and validation
• Enhanced tab-completion system

Custom Commands v1.0.1 Update

✨ New Feature: Command Type System

⚙️ Console vs Player Execution

You can now control how commands are executed when using custom commands!

• Console Type (default): Commands execute as server console with full permissions
• Player Type: Commands execute as the player who used the command (respects player permissions)

🎯 Use Cases

Console Type - Perfect for admin commands:

• Give effects, teleport players, kick/ban
• Works even if player doesn't have permission

Player Type - Perfect for plugin integration:

• Execute commands like /home, /warp, /balance, /spawn
• Player needs permission for the command to work

🎨 Example Usage

# Player executes /balance when using /hi
hi:
  type: "Player"
  commands:
    - "/balance"
  message:
    - "&eChecking your balance..."

# Console executes effect command (works without player permission)
glow:
  type: "Console"
  commands:
    - "effect give {player} minecraft:glowing 10 1 true"
  message:
    - "&eYou are now glowing!"

🔄 Upgrade Guide

If you're upgrading from v1.0.0, you need to update your config.yml:

1. Change Field Name

Change: console_commands: → commands:

2. Add Type Field (Optional)

Add the type field to control command execution. If not specified, defaults to "Console".

Example:

# Old (v1.0.0)
example:
  console_commands:
    - "/balance"
    - "effect give {player} minecraft:glowing 10 1 true"

# New (v1.0.1) - Console Type (default)
example:
  type: "Console"  # Optional: defaults to "Console" if not specified
  commands:
    - "/balance"
    - "effect give {player} minecraft:glowing 10 1 true"

# New (v1.0.1) - Player Type
example:
  type: "Player"  # Commands execute as the player
  commands:
    - "/balance"  # Player needs permission for /balance

Steps:

1. Replace all console_commands: with commands: in your config
2. (Optional) Add type: "Console" or type: "Player" to each command that has commands:
3. If type is not specified, it defaults to "Console" (same behavior as before)

The field name change makes more sense since commands can now execute as either Console or Player depending on the type setting.

📋 Technical Details

• Commands are executed on the main server thread
• Full variable support: {player}, {world}, {x}, {y}, {z}, etc.
• Works with all Minecraft commands and plugin commands
• Thread-safe and performance optimized

🔗 Links

• Discord: Join our Discord