Home
Codex (formerly ProMCCore) is the core library plugin for the MageMonkey Studio / VoidEdge plugin suite. It is a dependency plugin: on its own it provides a handful of utility features, but its main job is to give downstream plugins such as Fabled and Divinity a shared foundation — version compatibility, menus, hooks, an actions engine, item providers, and configuration handling.
| Page | What's in it |
|---|---|
| Installation | Requirements, supported servers, optional dependencies |
| Configuration | Every key in config.yml, explained |
| Commands | The full command tree |
| Permissions | Every permission node |
| Join and Interact Commands |
onJoin, onFirstJoin, onInteract
|
| Localization | Language files and message placeholders |
| Version Support | Which Minecraft versions are supported |
|
Chat Module |
Deprecated — player prefixes and display names |
|
Scoreboard Module |
Deprecated — scoreboard cycling and display |
| Page | What's in it |
|---|---|
| Developer Getting Started | Maven coordinates, extending CodexPlugin
|
| Actions Engine | The YAML-driven action/condition/target system |
| Item Providers | Cross-plugin item resolution (Oraxen, Nexo, ItemsAdder) |
| Menus and GUIs | Building paged inventory menus |
| Compat and NMS | Writing version-independent code |
| Hooks | Vault, WorldGuard, MythicMobs, Citizens, Nexo |
| Events | Custom events Codex fires |
| Utilities | The *UT helper classes |
- Download Codex and drop it in
plugins/. - Start the server once to generate
plugins/CodexCore/config.yml. - Install the plugins that depend on Codex (Fabled, Divinity, …).
Codex loads at server startup (before worlds load), because dependent plugins need its compatibility layer available very early. See Installation for details.
Three names are in play, and they differ on purpose:
| Codex | The project |
| CodexCore | The Bukkit plugin name — the data folder, depend: entry, and permission prefix |
| codex | The Maven artifactId |
So the config lives at plugins/CodexCore/config.yml, permissions read codexcore.admin, and Maven
wants studio.magemonkey:codex.
Codex was previously called ProMCCore and still declares provides: ProMCCore, so plugins
depending on the old name resolve against it. On first startup it automatically renames an
existing plugins/ProMCCore/ folder to plugins/CodexCore/. Remove the old ProMCCore.jar before
starting — running both causes duplicate class conflicts. Back up first; see Installation.
Source lives at magemonkeystudio/codex. Issues and pull requests are welcome.