TheNextLvlTheNextLvl

Resetting Commands

Reset commands to their original state

GitHub Edit on GitHub

Resetting Commands

The reset command allows you to completely restore a command to its original state, removing all Commander modifications including hiding, unregistering, and permission overrides.

Command

Reset a Command

Usage: /command reset <command>
Completely resets a command to its original state, removing all modifications made by Commander.

Examples:

# Reset specific commands
/command reset luckperms
/command reset fly
/command reset plugins
/command reset op

# Reset ALL commands (restore everything to original state)
/command reset "*"

# Reset all bukkit namespaced commands
/command reset "bukkit:*"

# Reset all namespaced commands
/command reset "*:*"

Resetting a command will remove ALL Commander modifications.
If you only want to remove specific modifications, use the appropriate command instead:

  • Use /command reveal to only unhide a command
  • Use /command register to only restore an unregistered command
  • Use /command permission reset to only remove a permission override

Resetting commands that were unregistered for security reasons may expose them to all players again.

Configuration Changes

When you reset a command, Commander will:

  1. Remove the command from all configuration files
  2. Update the hidden commands list
  3. Update the unregistered commands list
  4. Update the permission overrides list
  5. Apply the changes immediately

Tips

  • Use reset when you want to completely start over with a command
  • Consider the security implications of resetting unregistered commands
  • Test the command after resetting to ensure it works as expected

Last updated on

Managing Permissions

Manage and override command permissions

Configuration Management

Manage Commander configuration files

On this page

Resetting Commands
Command
Reset a Command
Configuration Changes
Tips