Configuration

MMOUpgrade Config A-Z

This page is the full config map. Each generated file owns a specific area; use the detailed pages for full examples and explanations.

Config File Map

File	Purpose	Detailed Page
`config.yml`	License key and Premium modifier debug logging.	Free vs Premium
`commands.yml`	Root command, aliases, permissions, subcommand names, argument names, and tab suggestions.	Commands
`gui.yml`	Inventory title, size, buttons, placeholder slots, cost, money placeholder, charge command, model, and tooltip options.	GUI & Economy
`items.yml`	MMOItems used as upgrade stones, lucky charms, and protect charms.	Stones & Charms
`upgrade.yml`	Max level, Free limits, allowed types, level display, consumed items, failure behavior, and success chance.	Upgrade Rules
`stat-registration.yml`	Custom stats that MMOUpgrade registers into MMOItems.	Custom Stats
`stat-modifiers.yml`	MMOItems stat scaling plus Premium element and enchantment modifiers when items gain or lose levels.	Stat Modifiers
`message.yml`	Messages sent to players/admins and broadcast text.	Messages
`announcements.yml`	Enables or disables broadcasts when an item reaches configured level milestones.	Messages

Set license-key if you use Premium. If it is empty, review the Free limits in upgrade.yml.
Edit items.yml so upgrade stones, lucky charms, and protect charms match real MMOItems IDs.
Edit upgrade.yml to set max level, allowed types, success formula, and failure behavior.
Edit gui.yml to set slots, cost, charge command, and GUI visuals.
Edit stat-modifiers.yml to decide how items become stronger at each level.
Edit message.yml and announcements.yml for server-facing text.
Run /mmoupgrade reload, then test with a real MMOItems item.

Text supports MiniMessage tags such as <red>, <aqua>, hex colors, and legacy ampersand colors where conversion is supported.

MMOUpgrade variables use curly braces, such as {level}, {name}, {cost}, and {money}, to avoid MiniMessage conflicts.

PlaceholderAPI placeholders use %placeholder%, such as %vault_eco_balance_fixed%. Money checks must return a plain number.

In items.yml, IDs must use TYPE:ITEM_ID, for example CONSUMABLE:UPGRADE_STONE_1.