A freeze that hits right as the terrain starts loading on join is usually memory: joining a busy server spikes RAM usage, and if the allocation or your total system RAM is too low the game becomes unresponsive. Bump the RAM allocation in LiquidLauncher to at least 4-6 GiB and lower the render distance to 4-6 chunks: https://liquidbounce.net/docs/tutorials/fixing-fps If it still hangs, paste the end of latest.log to https://paste.ccbluex.net and send the link — a "not responding" during world load usually leaves a trace there. Also let me know whether it happens on every server or just one. 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 is almost certainly AutoConfig re-loading a community config when you join the server, which switches its modules back on — including a fly-type module. Turn AutoConfig off (Misc category), then rejoin. If you're still floating after that, run .panic once in-game to switch every module off, and send the link from .debug so we can see what's actually enabled. 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.

That rainbow/colored pixel scatter across the screen is the classic look of graphics corruption, and by far the most common cause is an outdated GPU driver. Update your graphics driver (full clean install, then reboot) and test again. If it keeps happening, tell me whether it also shows in a plain vanilla/Fabric setup or only with LiquidBounce, and send a screenshot plus your GPU model (read it off Device Manager or Task Manager). 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.

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.

Use minecraft premium account

@kawaiinekololis Yes, according to Minecraft mechanics, a critical hit is already possible on the 11th tick, which is around 0.92 cooldown. However, regardless of what value is set in Item Cooldown, the attack still happens only on the 12th tick (around 1.00 cooldown). This happens not only in Always Criticals, but also in Smart Criticals. In both cases the module waits for almost a full cooldown, even though a critical hit is already possible earlier. So as I mentioned before, a critical hit is already possible on the 11th tick, but the system still attacks only on the 12th tick, which wastes a small amount of time. I also attached a video on GitHub showing this behavior in case the message is unclear. Regarding Always Criticals Mode — as I mentioned above, this issue also affects Smart Criticals. In both cases, critical attacks happen only on the 12th tick. And yes, to some extent I agree that Smart mode is better, because the game is not always perfectly smooth. For example, even a simple knockback can interfere with performing a critical hit, which sometimes causes Always mode to lose DPS compared to Smart. However, as can be seen from the issue description and the examples shown on GitHub, Smart mode also does not work perfectly and sometimes misses critical hits.

@kawaiinekololis Thank you for your swift response. I’m looking forward to the upcoming update and appreciate your continued efforts.

You need to be more specific. Show us your issue.

Don't spam the forum This tells us nothing about your issue. You need to provide the log if you want help.

1 frame every 3 seconds

There was a fix regarding that: https://github.com/CCBlueX/LiquidBounce/pull/6305 MukjepScarlet opened this pull request in CCBlueX/LiquidBounce closed fix(InventoryCleaner): sharpness calculation on 1.8.x #6305

@Templom YOU GOTTA BE KIDDING ME ITS BEEN 3 YEARS

@Rayyzon unzip and extract the texture packs

@recorefor Update your AMD GPU drivers.

Update your AMD drivers.