Placeholders Guide
This page explains the permission-gated Placeholders controls used by authorized staff and testers. It is not a normal player feature.
What It Does
Section titled “What It Does”Placeholders combines the production %onemb_*% provider with the former Catalog, Probe, and Health tools behind one /_placeholders command and independently switchable modules.
How Staff Use It
Section titled “How Staff Use It”Authorized staff use /_placeholders status and /_placeholders modules to inspect the parent and hosted modules. Provider data and the established permission, config, and placeholder namespaces remain compatible, while retired diagnostic roots now live under the Catalog, Probe, and Health subcommands.
Available features include:
- The production
%onemb_*%PlaceholderAPI provider and its established data remain compatible. - Catalog search and concrete placeholder examples under
/_placeholders catalog. - Bounded ad hoc parsing and expansion diagnostics under
/_placeholders probe. - Configured operational checks and Markdown reports under
/_placeholders health. - Independent Provider, Catalog, Probe, and Health lifecycle switches.
Quick Start
Section titled “Quick Start”- Run
/_placeholders statusto inspect the provider and parent lifecycle. - Use
/_placeholders modulesto review all four hosted module states. - Open the full reference before enabling a dormant diagnostic module or editing provider data.
Commands
Section titled “Commands”| Command | What it does | Example |
|---|---|---|
/_placeholders status | Shows the parent lifecycle and production provider state. | /_placeholders status |
/_placeholders modules | Lists the Provider, Catalog, Probe, and Health module states. | /_placeholders modules |
/_placeholders module <provider| | Enables or disables one hosted placeholder module. | /_placeholders module provider true |
/_placeholders list [category] [page] | Lists configured production placeholder keys. | /_placeholders list |
/_placeholders get <key> | Shows one configured production placeholder value. | /_placeholders get server_name |
/_placeholders catalog check <keyword> [page] | Searches the known placeholder catalog by keyword. | /_placeholders catalog check player |
/_placeholders probe parse <placeholder> [online-player] | Safely parses one concrete placeholder for diagnostic review. | /_placeholders probe parse %onemb_server_name% |
/_placeholders health check [player] | Runs the configured operational placeholder sample set. | /_placeholders health check |
Examples
Section titled “Examples”/_placeholders status/_placeholders modules/_placeholders module provider true/_placeholders list/_placeholders get server_name/_placeholders catalog check player/_placeholders probe parse %onemb_server_name%/_placeholders health check
Good To Know
Section titled “Good To Know”- Placeholders is permission-gated and intended for authorized staff or test environments.
- The former
/cmiplaceholders,/placeholderprobe, and/placeholderhealthroots are retired; use the nested routes shown above. - The former 1MBPlaceholders provider data and
%onemb_*%expansion remain compatible. - Do not load any of the four former standalone jars beside the consolidated Placeholders jar.
Full Reference
Section titled “Full Reference”The full synced Placeholders reference is available for exact technical details.