Skip to content

Admin Commands

Admin Commands are designed for server administrators and staff members to manage Item Upgrader items and plugin configuration.

All commands use /itemupgrader. Unless otherwise stated, all commands can also be executed from the console.


Administrators with the itemupgrader.item permission can give the source or result item defined by an upgrade recipe to a player.

The final boolean controls which recipe item is given: true gives the original from item, while false gives the upgraded to item.

Terminal window
/itemupgrader item <player> <item_name> <true_if_from>

Administrators with the itemupgrader.reload permission can reload the upgrade recipes, allowed worlds, menu permission, and configuration files without restarting the server. Active upgrade menus close first so their reserved source items are restored. Customer YAML files are not rewritten.

Terminal window
/itemupgrader reload

Administrators with the itemupgrader.version permission can display detailed information about the plugin, server, Java runtime, JVM, and operating system.

This command is only accessible to players.

Terminal window
/itemupgrader version

Administrators with the itemupgrader.help permission can display commands allowed by the sender type, permission and operator rules. Players can hover for descriptions and click to suggest commands; console rows show the descriptions directly.

Terminal window
/itemupgrader help

All declared administrative nodes default to operators. The optional upgrade-menu-perm setting controls ordinary menu access independently of itemupgrader.*. Give non-operator staff only the specific nodes they need. The completion permission is itemupgrader.tabcompleter; suggestions are further filtered by each command’s access rules.

The item command is a configuration/testing helper. It gives a cloned recipe template, rather than performing an upgrade or charging a price. Test the actual menu to verify source/result amounts, inherited metadata and attempt rules.