Every pull request to LiquidBounce now starts the real game and plays on our test server against Grim. If something breaks or gets flagged, we don't merge it.
Why
LiquidBounce hooks deep into Minecraft. After a version update, code can compile fine and still crash, or a module stops working and nobody notices until the bug reports come in. We also get more and more pull requests written with AI tools, and that code often compiles fine and then breaks in game.
What runs
- verify-pr builds the client and runs our unit tests.
- gametest (local) starts the game and uses the client like a player would, with commands, configs, the marketplace and shaders. It also checks our player simulation against vanilla movement tick by tick.
- gametest (vanilla) and gametest (grim) join test.ccbluex.net with one bot and one world per test. A flag, setback or kick fails the test.
That takes about five minutes, or around 15 when navigation changed.
No flags on Grim
Movement features have to get through Grim without a single flag. That includes Sprint in Legit mode, walking and parkour with .goto, swimming, boats, horses, elytra with rockets and AutoWindCharge. The first runs already found three bugs in Parkour and elytra navigation, and we fixed them the same day.
Test your own client
The server and the harness are open to everyone. CCBlueX Gametest runs Fabric's automated tests on test.ccbluex.net, also from CI. You need the API token from your account page, and GAMETEST_SERVER_ANTICHEAT picks the anticheat (Grim by default).
Writing an add-on? The testing guide shows how to use the same setup.
If you send us a feature, please add a game test for it. Questions go to our Discord.
