RCore on Velocity
Use the same RCore edition jar on a Velocity proxy to connect Raindrop backends for authenticated live events, presence, transfers, and recent-combat reconnects.Install and choose transport
Install exactly one RCore Free or Premium jar in Velocity plugins/. RCore supplies the proxy runtime itself; remove the former RaindropNetwork-Velocity companion jar when upgrading.VELOCITY mode connects backends on one proxy without Redis. REDIS mode relays across multiple proxies and needs a shared Redis deployment, matching network ID and prefix, and a unique proxy ID.Match backend settings
Configure plugins/rcore/config.properties on Velocity and the network section of plugins/RCore/config.yml on each Paper or Folia backend. Match network-id, channel, and shared-secret; set each backend server-id to its registered Velocity server name and enable networking on participating backends.A new Velocity configuration leaves networking disabled until a shared secret of at least 16 UTF-8 bytes is supplied. Keep this secret outside version control. Cross-server RDR trading also needs a shared authoritative SQL database and matching trade.live.network_id.Recent-combat reconnect
When a participating backend reports a PvP hit, Velocity can send a reconnecting player back to that backend while the hit is fresh and the backend remains registered. combat-reconnect-seconds defaults to 10 in the proxy configuration; 0 disables this routing.The backend combat tag duration and the proxy reconnect window are separate settings. Test routing with two backend servers before advertising it to players.