Proxies and other clients
Separate retained Paper integration paths from combinations that still need testing.
Velocity and BungeeCord
Paper’s forwarding mechanisms remain relevant. This repository does not certify every proxy, authentication plugin, release, and hosting topology. API preservation is not end-to-end testing of all combinations.
Follow the official Velocity forwarding guide or your proxy’s official documentation. Match both sides’ forwarding mode and protect backend access against direct connections bypassing the proxy.
Do not disable authentication on an openly reachable server just to make login work. Review forwarding secrets, client identity, firewall rules, and backend access together.
ViaVersion and Geyser
ViaVersion supports selected cross-version protocol combinations. Geyser bridges Bedrock clients through its integration. Neither establishes native support for every version or removes the need to test inventory, items, movement, chat, and plugins.
Select builds explicitly supporting this 1.21.11 server. Consult ViaVersion setup and Geyser documentation. Current latest versions may target newer Minecraft releases; check their support matrix rather than assuming latest is suitable.
Test the topology
Check login paths, UUIDs/permissions, correctly forwarded client identities, server switching, inventory, and reconnects. Test each intended client type. Native Java-client plugin loading alone does not verify Bedrock authentication or older protocol clients.
If all clients appear behind one address, fix forwarding and review IP-based plugin policies before disabling protection.