Extractioncraft Commands and Permissions

Extractioncraft registers the root command:

/extractioncraft
/exc

Subcommands are registered through the MagmaCore command manager at runtime.

Admin Commands

Command	Permission	Default	Sender	Description
/exc initialize	extractioncraft.initialize	op	Player	Opens the first-time setup menu
/exc setup	extractioncraft.setup	op	Player	Opens the content package browser for installing, uninstalling, and managing content
/exc protection bypass	extractioncraft.protection.bypass	op	Player	Toggles bypassing match instance protections (e.g. teleport restrictions, block protections)
/exc reload	extractioncraft.*	op	Any	Reloads the plugin. A full server restart is recommended if the reload does not fully apply.

Player Commands

Command	Permission	Default	Sender	Description
/exc createMatch <contentPackage.yml>	extractioncraft.creatematch	true	Player	Creates a new match using the specified content package and places the player into it. Tab-completes available content package filenames.
/exc start	extractioncraft.start	true	Player	Starts the match the player is currently in, if the minimum player count is met
/exc leave	(none set)	true	Player	Leaves the current match.
/exc quit	(none set)	true	Player	Leaves the current match. Same as /exc leave.

MagmaCore Shared Commands

MagmaCore is bundled into Extractioncraft, so these commands ship with the plugin too.

Command	Permission	Default	Sender	Description
/exc recommendedplugins	extractioncraft.setup	op	Any	Opens (for players) or prints (for console) the list of companion plugins recommended for Extractioncraft.
/nightbreak plugins	nightbreak.plugins	op	Any	Opens the Nightbreak plugin catalog to browse and download MagmaGuy's other plugins. Registered once globally by MagmaCore.
/nightbreaklogin <token>	nightbreak.login	op	Any	Registers your nightbreak.io account token in-game so the server can fetch licensed content. Registered once globally by MagmaCore.
/nightbreaklogout	nightbreak.login	op	Any	Clears the stored nightbreak.io account token from the server. Registered once globally by MagmaCore.
/logify	logify.*	op	Any	Posts the current latest.log to mclo.gs, to make reporting bugs easier for admins. Registered once globally by MagmaCore.

Permissions Summary

Permission	Default	Description
extractioncraft.initialize	op	Access to /exc initialize
extractioncraft.setup	op	Access to /exc setup and /exc recommendedplugins
extractioncraft.protection.bypass	op	Access to /exc protection bypass
extractioncraft.*	op	Access to /exc reload
extractioncraft.creatematch	true	Access to /exc createMatch
extractioncraft.start	true	Access to /exc start
extractioncraft.leave	true	Declared in plugin.yml for /exc leave, but not enforced at runtime (the registered quit/leave command has no permission check)
nightbreak.plugins	op	Access to /nightbreak plugins (registered by MagmaCore)
nightbreak.login	op	Access to /nightbreaklogin and /nightbreaklogout (registered by MagmaCore)
logify.*	op	Access to /logify (registered by MagmaCore)

Notes

• The plugin.yml declares root commands /extractioncraft and /logify. The /extractioncraft subcommands are registered at runtime through the MagmaCore command manager.
• extractioncraft.* is used by /exc reload but is not declared in plugin.yml, so it is not a registered permission node. Operators pass it automatically; anyone else needs it granted explicitly by a permissions plugin.
• The quit and leave subcommands both remove the player from their current match. They are both registered through QuitMatchCommand (which has no permission check). Note: a separate ExitMatchCommand class (aliases exit/leave, permission extractioncraft.leave) exists in source but is not registered at startup, so the extractioncraft.leave node is never enforced.
• /logify, /nightbreak, /nightbreaklogin, and /nightbreaklogout are registered globally by MagmaCore (which is bundled into the plugin), each only once across all MagmaCore plugins on the server. If another MagmaGuy plugin already claimed one of those names, Extractioncraft skips registering it and the existing one is used.
• Running /exc with no arguments prints the usage line of every registered subcommand.
• A subcommand registered without a permission node (currently only quit/leave) passes the permission check for every sender.
• The info button inside /exc setup advertises /extractioncraft downloadall. That subcommand is not registered by Extractioncraft, so the suggestion does nothing — use the setup menu itself to manage content.