That's the MovementCorrection setting inside KillAura's Rotations group. By default it's on Silent, which only sends the rotation to the server — your camera stays where you point it. Set it to ChangeLook and your actual view will snap to the target, so it looks the same on your screen as it does server-side. Details on the other options here: https://liquidbounce.net/docs/modules/shared-settings/rotations Automated support reply. If this does not help, a human will take a look — you can also reach us on Discord or through the contact form.

@izuna I'LL CRY THEN

That was a bug. It has been fixed already.

LiquidBounce only runs on the current Minecraft version — there's no 1.20.1 build, and the client's base version is fixed and can't be downgraded. So it won't load inside a 1.20.1 Fabric modpack; the mods have to match whatever version the client itself is built for (see the manual installation page, which covers the current setup and its video). The one thing that can get you onto older servers is ViaFabricPlus (drop-down in the top-right of the Multiplayer menu), which translates the protocol so the current client can join servers back to 1.7 — but that doesn't make the client run on 1.20.1 for a local modpack. For a 1.20.1 modpack, you'd either play it without LiquidBounce, or use an older LiquidBounce build built for that version — which is outdated and no longer supported, so I'd avoid it. Automated support reply. If this does not help, a human will take a look — you can also reach us on Discord or through the contact form.

This "combos then the damage stops" pattern is usually the server's anticheat reacting to sustained KillAura and cancelling the damage server-side — the swings look like they land, but the server stops applying it. That's not something a single setting fixes. The right starting point is a config tuned for the specific server/anticheat you're on. Check what's available with .config list, then load one for your server with .config load <name>. Also make sure the combat Targets are right (.targets combat Players) and that AntiBot isn't filtering the people you want to hit. Automated support reply. If this does not help, a human will take a look — you can also reach us on Discord or through the contact form.

Your mods don't load because the updated client now runs a newer base Minecraft version than 1.21.11, and you can't switch it back. The version picker in the Multiplayer menu only changes the protocol spoken to the server, not the actual Minecraft version your mods run against, so mods built for 1.21.11 won't load on the new build. Get updated mods built for the client's current version and add them through the launcher's Install button (the mods folder is rebuilt on every launch, so dropping jars in there gets wiped). You also don't need to disable Sodium — it's one of the launcher's shipped mods, not a conflict. Automated support reply. If this does not help, a human will take a look — you can also reach us on Discord or through the contact form.

KillAura only attacks entities that are ticked as combat targets, and that list isn't inside KillAura — it's the global Targets setting (alias "Enemies"), shared by every combat module. Open that and make sure Players is ticked, or just run .targets combat Players. It's on by default, so if you're on defaults it should already be set. If Players is ticked and it still does nothing, the usual silent blockers are: AntiBot is filtering the player out (turn it off if the server has no bots). The player is on your friend list — friends are never targeted. Teams is on in a gamemode with no teams, which makes the client treat everyone as a teammate and skip them. Also make sure KillAura itself is actually toggled on — it's off by default. Automated support reply. If this does not help, a human will take a look — you can also reach us on Discord or through the contact form.

What does the error actually say? Without the exact wording (or better, the log) there's nothing to go on. Reproduce the crash, then grab latest.log from %APPDATA%\CCBlueX\LiquidLauncher\data\gameDir\nextgen\logs, paste it to https://paste.ccbluex.net and post the link here. The end of the file is where the cause will be. Also worth mentioning: whether you added any mods or resource packs yourself, since those are the usual reason for a crash during loading. Automated support reply. If this does not help, a human will take a look — you can also reach us on Discord or through the contact form.

There's no KillAura setting that makes every hit register — the module only aims and clicks, and the server decides whether a hit counts. On a server with a working anticheat, part of your hits getting cancelled is the anticheat doing its job, and pushing range/CPS up just gets you flagged sooner. What actually helps is starting from a config built for the anticheat that server runs rather than hand-tuning: Enable AntiCheatDetect and join — it prints the detected anticheat in chat. The anticheats page lists servers and their anticheats too. .config list shows the community configs; there's none for donutsmp specifically, so load the one matching the anticheat (e.g. .config load grim) and use it as your base. Settings reference: KillAura. Keep the range near vanilla — high reach is one of the easiest things for a server to catch. Automated support reply. If this does not help, a human will take a look — you can also reach us on Discord or through the contact form.

Two ways, depending on where the config comes from: Community configs (recommended) — nothing to install, just load them in game: .config list .config load <name> A config file someone gave you — it has to be a LiquidBounce .json file: .localconfig browse — opens the folder LiquidBounce reads local configs from. Drop the .json in there directly (no subfolder, and watch out for Windows hiding the real extension, so you don't end up with name.json.json). .localconfig list to check it shows up, then .localconfig load <name>. If loading errors out, the file usually isn't a valid nextgen config (a .txt, or one made for another client/older build) — renaming it won't help. Also make sure your client is on the current release; old builds fail to load configs that otherwise work fine. All of the config commands are listed here: https://liquidbounce.net/docs/commands/client Automated support reply. If this does not help, a human will take a look — you can also reach us on Discord or through the contact form.

necroposting... Sorry! The link is dead, does anyone have an archive of it that's working?

I think it was one of the early versions around Minecraft 1.20.4.

You can't.

i tried with port 25565 and it worked. change it if you still have the problem, or get the right port from the server's website or forum if have any.

No one will be able to help you when all you post is an image of it not working. I bet it's an connection issue, which makes it unable to download the AI engine. Without log though, that is nothing we can tell exactly.

@sqwennyy Only for servers. Your game will always stay on 1.21.11 or newer.