Skip to main content

Extractioncraft Commands and Permissions

Extractioncraft registers the root command:

/extractioncraft
/exc

Subcommands are registered through the MagmaCore command manager at runtime.

Admin Commands

CommandPermissionDefaultSenderDescription
/exc initializeextractioncraft.initializeopPlayerOpens the first-time setup menu
/exc setupextractioncraft.setupopPlayerOpens the content package browser for installing, uninstalling, and managing content
/exc protection bypassextractioncraft.protection.bypassopPlayerToggles bypassing match instance protections (e.g. teleport restrictions, block protections)
/exc reloadextractioncraft.*opAnyReloads the plugin. A full server restart is recommended if the reload does not fully apply.

Player Commands

CommandPermissionDefaultSenderDescription
/exc createMatch <contentPackage.yml>extractioncraft.creatematchtruePlayerCreates a new match using the specified content package and places the player into it. Tab-completes available content package filenames.
/exc startextractioncraft.starttruePlayerStarts the match the player is currently in, if the minimum player count is met
/exc leave(none set)truePlayerLeaves the current match.
/exc quit(none set)truePlayerLeaves the current match. Same as /exc leave.

Additional Commands

CommandPermissionDefaultDescription
/logifylogify.*opPosts the current latest.log to mclo.gs, to make reporting bugs easier for admins

Permissions Summary

PermissionDefaultDescription
extractioncraft.initializeopAccess to /exc initialize
extractioncraft.setupopAccess to /exc setup
extractioncraft.protection.bypassopAccess to /exc protection bypass
extractioncraft.*opAccess to /exc reload
extractioncraft.creatematchtrueAccess to /exc createMatch
extractioncraft.starttrueAccess to /exc start
extractioncraft.leavetrueDeclared in plugin.yml for /exc leave, but not enforced at runtime (the command has no permission check)
logify.*opAccess to /logify

Notes

  • The plugin.yml declares root commands /extractioncraft and /logify. All subcommands are registered at runtime.
  • The quit and leave subcommands both remove the player from their current match. They are both registered through QuitMatchCommand. Note: an ExitMatchCommand class exists in source but is not registered at startup.