Where to Install an Anticheat on Velocity or BungeeCord

Should the anticheat go on the proxy or the backends?

On a Velocity or BungeeCord network, gameplay and combat happen on backend servers, so combat anticheats usually belong there. The proxy forwards connections and sees less of each player's actions. Install the anticheat on every backend where players fight or build. Check each vendor's documentation before adding it to the proxy.

Each backend runs its own server software. The anticheat, any dependency it requires, and its configuration live in that backend's plugins folder. A proxy install is a separate artifact and does not replace a backend install.

How do the proxy and backend roles differ?

Use this table to decide where each piece belongs. Confirm each row against the vendor's listing before you install anything.

Write the decision down per backend, including the reason. A later change to the network, such as adding a Folia backend or moving a game mode, is easier to review when each placement has a recorded reason.

How do I install the anticheat on each backend?

Repeat the same install on every backend that runs combat or building. Use one anticheat version everywhere so alerts from different backends stay comparable.

If backends run different server builds, check each anticheat release's support list for each build. Do not assume that a release tested on one backend applies to the others.

• List every backend that runs combat, building, or inventory play.
• Install the anticheat and its required dependencies on each one, at the same release.
• Start each backend and read its console for dependency or class-loading errors.
• Confirm that alerts from each backend reach your staff channel.
• Run a legit fight and a legit build on each game mode before you open it to players.

How do I keep configuration consistent across backends?

Each backend reads its own config file, so a change on one backend does not reach the others. There are two common patterns. You can copy one config to every backend and track differences by hand. Or you can keep one template and sync it through your deploy tool. Either way, record every intentional difference between backends.

Keep the layout explicit so you can see what each backend loads.

velocity/
  plugins/                  proxy plugins only, no combat anticheat unless the vendor supports it
backend-pvp-1/
  plugins/
    <anticheat>.jar
    <packetevents>.jar
    config.yml
backend-pvp-2/
  plugins/
    <anticheat>.jar
    <packetevents>.jar
    config.yml

How do staff tell which backend raised an alert?

Staff need to know which backend raised an alert before they act on it. Include the server name in your alert routing or log naming, and confirm that the alert text identifies the backend.

Limit commands per staff role. FairPlay's permission reference lists fairplay.command as the gate for its commands, with child grants for each function. Assign only the grants a role needs.

What if I run more than one anticheat?

Test the full path your players take. Move a test account between two backends and confirm that its alerts, permissions, and any stored state behave the way your staff expect, because a transfer changes which backend handles the player.

Running two anticheats on one backend can duplicate alerts or cause conflicts. Review the stacking guidance before you install a second one, and test the combined setup on staging.

Do not run a second anticheat on the proxy just to cover backends. Proxy-level plugins are a separate decision with their own vendor requirements, and mixing placements makes it harder to tell which layer raised an alert.

How should I roll out a new backend?

Add a new backend to staging first, with the same plugins, config template, and permissions as the production backends it will join. Then connect it to a staging proxy and move a test account through the same routes players use.

Only after that should you add the backend to production. Keep the previous proxy and backend configuration so that a bad backend can be removed from routing without rebuilding the network.

What have we not verified?

We have not tested any proxy version with any anticheat, and this article makes no claim that a given anticheat works on a proxy. Performance and transfer behavior depend on your network, so test a player moving between backends on staging before you rely on it.