Connect a server to Central
Connect RCore for dashboard presence, linked-player reporting and Central-owned features.Before connecting
Install and enable RCore. Sign in to Central, connect your Microsoft account from Settings → Connected accounts, and confirm the linked Minecraft identity. Create a server API key from the dashboard. Keep the key in server configuration.
Configure RCore
Set central.apiKey in plugins/RCore/config.yml, keep central.enabled true, and use the HTTPS Central API address. Restart after editing.
central:
enabled: true
baseUrl: "https://api.raindropcentral.com"
apiKey: "rc_v1_<key-id>_<secret>"Connect as the linked player
Join the server as the Minecraft player linked to your account. Run /rc connect. This player-only command requires rcore.command and rcore.command.central.admin. Do not send an API key as a command argument.
/rc connectVerify presence and reporting
Check the command result and server log, then confirm the server appears in your dashboard and receives heartbeats. Presence, vanilla statistics and individual plugin reports have separate settings; an online badge alone does not prove every report is enabled.
Disconnect and recover
Use /rc disconnect with the same command permission pair when you want to stop heartbeats and mark the server offline. If connection fails, check the linked identity, credential, HTTPS address, clock and outbound network access before creating another key.
Local gameplay and networks
A Central outage does not stop ordinary local fishing. Other features still need their own providers and databases. The RCore Velocity bridge is a separate network configuration used for cross-server events and transfers.