RCore Setup
RCore supplies the shared runtime, profiles, displays, reporting and network services used by Suite plugins.Requirements
Install matching Suite artifacts on Paper or Folia. Release JARs are adapted to Java 17 bytecode; your Minecraft server may require a newer Java runtime. Use the compatibility guide to choose the server and Java combination.
Installation
Stop the server and back up the plugin data and database when upgrading. Put matching RCore and one runtime JAR for each selected plugin in plugins/. Remove replaced JARs from that directory, then start the server and check that the plugins enable.
Minimal configuration
For a local first run, review plugins/RCore/config.yml and the generated database/hibernate.properties. Central credentials are needed only when connecting Central features. Review display defaults before giving players access.
First task
Join as a player and run /hud. Enable a supported provider from the personal display settings. /hud off hides personal channels, and /hud resume restores visibility and opens settings. The rcore.hud permission defaults to true.
Verification
Run /rc info with rcore.command and rcore.command.info, then check a player display. On Folia, the bundled settings leave sidebar support unavailable. Test the bossbar/provider combinations your server uses.
Optional models
Set models.enabled to true in plugins/RCore/config.yml and restart. Store model definitions and artwork under plugins/RCore/models/. RModel is embedded in RCore. Use /rmodel status to inspect it, /rmodel pack <model-id> as a player to request a pack, and /rmodel reload as an administrator.
Next integrations
Connect Central for dashboard reporting or install the same unified RCore JAR on Velocity for network features. These are separate setup paths.