# Run a legacy-client combat and anti-cheat acceptance test

Older and newer Minecraft clients differ in combat presentation and packet behaviour. ViaRewind compatibility alone does not certify an anti-cheat or competitive ruleset. A controlled acceptance test can reveal false positives without weakening protection for the entire server.

## Record the starting point

Create a private arena and use consenting test accounts with ordinary permissions. Record server, Via family, anti-cheat and client versions. Save the anti-cheat configuration and decide which simple actions count as expected play before beginning the trial.

## Work through the change

1. Run movement, jumping, melee hits and a normal inventory swap with the native client. Record alerts and server behaviour as a baseline.
2. Repeat the same actions with the supported legacy client. Keep timing and equipment comparable, and distinguish an alert from an automatic kick or cancelled action.
3. Check the anti-cheat maintainer's supported Via integration and known limitations. Trial a documented compatible release or scoped adjustment on a private copy rather than disabling all checks.
4. Repeat both client tests after the adjustment. Include a normal non-staff login so a bypass permission cannot make the result appear successful.

## Check the result

Ordinary test actions should complete consistently without unexplained kicks, and the community's intended combat rules should remain clear. Save timestamps and the small action list. A test of harmless movement does not prove that every combat exploit is detected.

## If the result differs

If only one minigame fails, inspect its mechanics and packet hooks alongside the anti-cheat. If every client triggers the same alert, the baseline itself needs attention. Send a redacted minimal reproduction to the relevant maintainer rather than exposing full player histories.

Restore the saved anti-cheat setting if it introduces new false positives or weakens an unrelated check. Pause legacy competitive access if compatibility remains unresolved. Keep worlds, player inventories and the server's authentication policy unchanged.

## References and related help

- [ViaRewind maintainer reference 1](https://github.com/ViaVersion/ViaRewind)
- [ViaRewind maintainer reference 2](https://github.com/ViaVersion/ViaBackwards)
- [Evaluate legacy Java client support with ViaRewind](https://help.cloudexa-hosting.com/books/minecraft-plugins/page/evaluate-legacy-java-client-support-with-viarewind)
- [Find Minecraft logs and send useful troubleshooting details](https://help.cloudexa-hosting.com/books/game-hosting/page/find-minecraft-logs-and-send-useful-troubleshooting-details)