Cmdibuzz Configuration

Main configuration file settings for economy, database, and general options

Updated August 12, 2026

config.json Structure

The main configuration file controls global settings, economy, and database options.

{
  "general": {
    "debug": false,
    "prefix": "<gold>[Cmdibuzz]<reset>",
    "default_permission": true,
    "text_format": "legacy"
  },
  "economy": {
    "provider": "none",
    "initial_balance": 100.0,
    "currency_name": "coin",
    "currency_name_plural": "coins"
  },
  "database": {
    "type": "sqlite",
    "host": "localhost",
    "port": 3306,
    "database": "cmdibuzz",
    "username": "",
    "password": ""
  }
}

General Settings

FieldDescription
debugEnables verbose logging
prefixPrefix shown before mod messages (supports MiniMessage)
default_permissionWhether commands without a permission field are allowed by default
text_format"legacy" (default) supports & color codes. "minimessage" supports tags like <red>, gradients, hex colors, and converted legacy codes.

Economy Settings

FieldDescription
provider"none" (disabled), "impactor" (requires Impactor mod), or "mock" (built-in SQLite)
initial_balanceStarting balance for new players (mock economy)
currency_nameSingular currency name
currency_name_pluralPlural currency name

Database Settings

FieldDescription
type"sqlite" (default, no setup needed) or "mysql"
hostMySQL host (only for MySQL)
portMySQL port
databaseDatabase name
usernameMySQL username
passwordMySQL password

Reloading

After making changes to the config, run:

/cmdibuzz reload

This reloads all command files and re-registers commands without restarting the server. It does not reset SQLite balances, cooldowns, one-time-use records, or PlayerData values.

Command File Rules

  • Use valid JSON: double quotes are required, comments are not allowed, and trailing commas are not allowed.
  • Put one command object in each file under commands/; arrays of command objects are not supported.
  • Commands can be stored in subfolders. The filename without .json becomes the command ID when id is omitted.
  • Event commands must have register: true (the default) to run. If command is omitted or empty, Cmdibuzz falls back to the command id.
  • A command with register: false is ignored by both command registration and event dispatch.

If runcmd is omitted, null, or empty, the type field runs using the value of command. Always provide runcmd for multi-action and roulette commands.