ViaVersion and Anticheat Version Mismatch Explained

Why do multi-version clients cause anticheat problems?

A version mismatch happens when clients on a protocol other than the server's native one join through a translation layer such as ViaVersion. The anticheat then reads packets that were rewritten compared with what a native client sends. A check tuned for one protocol can flag legitimate play on another. Test every client version you allow before you open the server.

ViaVersion's project documentation describes how it translates protocols on the server. This article does not measure how any anticheat handles translated packets. Your staging results are the evidence that matters.

Which symptoms point to a version mismatch?

A mismatch rarely shows up as one clear error. Look for patterns tied to a single client version.

• Alerts appear only for players on one client version.
• Movement or combat flags on a version the server otherwise handles cleanly.
• Players on one client report teleports or position snaps that other clients do not.
• Latency or transaction values look wrong for one version only.
• Console errors that name packet or protocol classes after a plugin update.

Why does the same action look different per version?

Translation can change timing, position updates, and the order of packets a client sends. A movement check that expects one sequence may read a translated sequence as an impossible jump or a delayed response. The mismatch is in the input the check receives, not in the player's behavior.

This is why a single test account on one client does not settle the question. Repeat the same action on each version and compare the packet-driven values the anticheat reports, such as latency, transaction state, and velocity context.

What should I test before I allow a version?

Build a small matrix and run the same actions on each version. Use clean accounts, and repeat each test at least once. Replace the version rows with the exact clients your players use.

In what order should I install the plugins?

Install in a fixed order on a clean staging copy. Each startup error then points to one new plugin. This is a testing practice, not a rule from any vendor.

• Start from a clean copy of the server software at the version you will run.
• Install the anticheat's required dependencies. FairPlay requires PacketEvents, so install it first.
• Install ViaVersion and any protocol add-on. Start the server and join with one client from each version you allow.
• Install the anticheat, restart, and read the startup log.
• Run the matrix with clean accounts and record the alerts for each version.
• Add other plugins only after the matrix passes.

What should I do when one version floods alerts?

Do not disable every check to stop the noise. Find the check that fires on that version and decide whether to tune it in staging, move it to observation, or restrict that version.

Write down the decision and the evidence behind it. If a staff member later asks why a version is restricted, the matrix results and alert counts answer the question without guesswork.

FairPlay's per-check settings are described in its configuration reference. Change one check at a time, and record the before and after alert counts for each client version.

How do I update ViaVersion and the anticheat safely?

Treat a ViaVersion update as a change to the packets your anticheat reads. Rerun the full matrix after every update, even if the anticheat release did not change.

Keep the previous ViaVersion and anticheat jars. If the matrix fails after an update, you can roll back one plugin at a time and see which change introduced the alerts.

What have we not verified?

We have not tested any combination of ViaVersion release, anticheat release, and client version. This article makes no compatibility or accuracy claim for any of them, and it does not state which client versions FairPlay supports beyond what its own documentation says.