Commands and Permissions

Every CoreLib command and permission node is listed below, followed by the operations you will use most

The main command of EmakiCoreLib is /emakicorelib, with /corelib and /emakicore as aliases. You use these commands as a server administrator to reload CoreLib, run config prechecks (an early pass that checks your configuration for you), list or execute registered Actions, and troubleshoot loop Action tasks

Commands

Command	Permission	Description
/corelib reload	emakicorelib.reload or emakicorelib.admin	Reload CoreLib configuration and the Action system. If precheck fails, the previous config remains active
/corelib check [module|report|--fix]	emakicorelib.admin	Run config prechecks, check one module, or show the latest report. --fix is currently read-only and does not apply automatic fixes
/corelib action list	emakicorelib.admin	List registered stages with id, kind (source/gate/action), and owner
/corelib action run <actionId> key=value ...	emakicorelib.admin	Execute one currently registered Action. /corelib action <actionId> key=value ... is also accepted as shorthand
/corelib pdc-convert <players|containers|entities|all> [--dry-run]	emakicorelib.admin	Convert legacy dotted PDC keys to flat keys. --dry-run only counts and writes nothing
/corelib debug all [on|off|status]	emakicorelib.admin	Toggle the global Debug switch at runtime. Without an argument it behaves as status. A reload restores the configured debug.global_all value
/corelib debug loops [list|player|key|cancel|cancel-player]	emakicorelib.admin	Inspect active loop Action tasks and cancel them by key or player
/corelib help	none	Show subcommand help. Also shown when no argument or an unknown subcommand is given

There are two spellings for the same thing: the action subcommand may also be written as actions, and both are equivalent

Permissions

Permission	Default	Description
emakicorelib.reload	op	Allows CoreLib reload
emakicorelib.admin	op	Administrative fallback permission; includes emakicorelib.reload

Common operations

Reload CoreLib

/corelib reload

Run it whenever you change CoreLib configuration, language files, or Actions. Reload runs a config precheck first; if the precheck fails, the currently active configuration is kept

Run config prechecks

/corelib check
/corelib check report
/corelib check corelib

check validates configuration references, Action templates, item sources, and CoreLib-related settings. For the latest precheck result, use report; to check a single module, pass its module id

List and execute registered Actions

/corelib action list
/corelib action run send_message text="hello"

Use action list to confirm what is currently registered; each line prints id, kind, and owner. action run hands the whole line to the pipeline compiler as a normal pipeline line, so parameters, quoting, if <condition> [ ... ] branches, and gate syntax follow the same rules as pipeline lines you write in configuration files. Note that console execution has no player context, so stages that require a player fail through normal validation

Convert legacy PDC keys

/corelib pdc-convert players
/corelib pdc-convert containers
/corelib pdc-convert entities
/corelib pdc-convert all --dry-run

Pick a scope first: one of players, containers, entities, or all. The conversion scans asynchronously and then reports scanned / migrated / skipped / failed counts per scope plus a total migrated count. Start with --dry-run, which only counts and writes nothing, so you can size the impact first

Debug loop Actions

/corelib debug loops list
/corelib debug loops player Steve
/corelib debug loops key some-loop-key
/corelib debug loops cancel some-loop-key
/corelib debug loops cancel-player Steve

These commands exist only for troubleshooting or cleaning up loop Actions. Keep in mind that you should not leave large-scale loop task debugging enabled on production servers

Toggle global Debug

/corelib debug all status
/corelib debug all on
/corelib debug all off

This does the same thing as temporarily overriding debug.global_all in config.yml, and it affects every Emaki module that uses CoreLib's DebugLogger. The toggle is not written back to the config file; running /corelib reload picks up the configured value again