Overview
Choose server and proxy platforms and keep their distributions and native clients compatible.
A platform supplies the distribution, configuration, and readiness behavior for a managed process. Server and proxy platforms share the same scenario lifecycle and are selected explicitly in your build.
Choose a platform role
| Role | Available platforms | Used for |
|---|---|---|
| Servers | Paper, Spigot, NeoForge | Running worlds and server plugins, directly or behind a proxy |
| Proxies | Velocity, BungeeCord | Accepting player connections and routing them to declared servers |
A proxy scenario applies a unit plugin for the proxy and for every backend platform it uses. Select every required platform explicitly.
Build up from one server
Start with the server guides, which include pinned examples. Add a proxy only when the behavior depends on routing or forwarded identity. The proxy guide builds on a named backend server.
When adapting an example, use Platform provisioning to choose a remote build, checksum, or supplied artifact, and Versions and compatibility to check native-client and Java requirements. Every reachable backend must be compatible with the player.
Once the topology is declared, use Provisioning to supply its software and Configuration to choose execution settings.
Platform unit plugins supply the provider and its matching agent artifact. Anvil installs the agents into managed workspaces and allocates their authenticated endpoints automatically. To implement another platform, use the platform extension guide.