Stone or charm is rejected
Check that items.yml uses TYPE:ITEM_ID. The inserted item must be a real MMOItems item generated or given by MMOItems.
Start here when the GUI rejects an item, chances look wrong, levels are capped, or Premium features do not apply.
Check that items.yml uses TYPE:ITEM_ID. The inserted item must be a real MMOItems item generated or given by MMOItems.
Add the MMOItems type to upgrade.yml allowed-types. Premium can also set MMOUPGRADE_ENABLED: true on a specific item.
The server is probably in Free mode or the license was not verified. Free mode is capped by license-limits.free.max-level.
Free mode is capped by license-limits.free.max-success-chance. Premium uses success-chance.max-percent.
Check Premium mode, exact stat IDs, correct value types, and whether the item was regenerated or given again after editing MMOItems config.
Element modifiers are Premium-only. Use flattened IDs such as fire-damage or fire-defense-percent, and make sure the element stat already exists on the item.
enchantments: is Premium-only. If Premium is active, enable debug.enchant-modifiers: true to inspect skip/apply logs.
Check that charge-command works from console. {amount} must be placed where your economy plugin expects the amount.
money-placeholder must return a plain number. Do not use a placeholder with commas, currency symbols, or text for balance checks.
/mmoupgrade reload after editing files./mmoupgrade stats to verify stat IDs before writing stat-modifiers.yml.element.<element>.<stat> entry before testing the upgrade.debug.enchant-modifiers when debugging Premium enchantment modifiers.