LiquidBounce Forum

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.

¿Dónde intentas iniciar sesión con Microsoft exactamente: en el iniciador (LiquidLauncher) al conectar la cuenta, o en el Gestor de Cuentas dentro del juego? ¿Qué te muestra la página cuando te redirige? Con esos datos puedo ayudarte mejor. 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.

AutoMace isn't an attribute swap — it only fires when a mace smash is actually available, meaning you're falling. Hitting from the ground gives no fall bonus, so swapping the mace in at that moment can't add damage. That's the documented behaviour of the toggle, not a bug: see AutoWeapon. If you want the smash damage without falling, the module for that is MaceKill — it fakes the fall height at the moment you swing the mace (FallHeight setting). Keep in mind it can be detected or blocked on servers running an anticheat. 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.