Cmdibuzz Admin Commands

Admin Commands

All built-in admin commands check OP level 4 and a permission node. Grant the node, or a parent node through LuckPerms, if a non-OP needs access.

Command	Permission Node	Description
/cmdibuzz	cmdibuzz.admin	Show help
/cmdibuzz reload	cmdibuzz.admin.reload	Reload all configs and re-register commands
/cmdibuzz list	cmdibuzz.admin.list	List all registered commands
/cmdibuzz attachcmd <command>	cmdibuzz.admin.attachcmd	Attach a command to the held item
/cmdibuzz cooldown clear <player>	cmdibuzz.admin.cooldown.clear	Clear all cooldowns for a player
/cmdibuzz playerdata	cmdibuzz.admin.playerdata	Show playerdata usage
/cmdibuzz playerdata list	cmdibuzz.admin.playerdata.list	List all custom variables
/cmdibuzz playerdata create <name> <type>	cmdibuzz.admin.playerdata.create	Create a custom variable
/cmdibuzz playerdata delete <name>	cmdibuzz.admin.playerdata.delete	Delete a custom variable
/cmdibuzz playerdata set <name> <value> <player>	cmdibuzz.admin.playerdata.set	Set a CV value for a player
/cmdibuzz playerdata add <name> <amount> <player>	cmdibuzz.admin.playerdata.add	Add to an integer CV
/cmdibuzz playerdata minus <name> <amount> <player>	cmdibuzz.admin.playerdata.minus	Subtract from an integer CV
/cmdibuzz playerdata check <name> <player>	cmdibuzz.admin.playerdata.check	Check a CV value for a player

Migration from v1.x

If you are upgrading from Cmdibuzz v1.x, the mod will automatically detect and convert your old configuration on first startup.

What Gets Converted

The old config.json format used command_pools:

{
  "command_pools": [
    {
      "example1": [
        "say Hello {player}",
        "give {player} minecraft:diamond 1",
        "op {player}"
      ]
    }
  ]
}

Conversion Process

On the first server start with v2.x:

1. The mod detects command_pools in your existing config.json
2. Each pool is converted to a dedicated command file in config/cmdibuzz/commands/<pool_name>.json
3. Pool commands become roulette_commands entries with equal weight
4. {player} references are replaced with $target
5. Your old config.json is backed up to config.json.backup
6. A fresh config.json with defaults is written

After Conversion

Each old pool becomes a working Brigadier command:

{
  "id": "example1",
  "command": "example1 <target>",
  "arguments": [
    { "name": "target", "type": "player" }
  ],
  "roulette_commands": [
    { "command": "say Hello $target", "weight": 1.0 },
    { "command": "give $target minecraft:diamond 1", "weight": 1.0 },
    { "command": "op $target", "weight": 1.0 }
  ]
}

Important Notes

• The conversion is automatic and irreversible — the old config.json is backed up
• Custom settings (economy, database, etc.) must be re-applied after conversion
• The old command pool system triggered pools via external events; in v2.x, each pool is a standalone command