LiquidBounce Forum

Update 1.0.9 important changes: - MatrixClickTP: -> works with way less packets, flagless, kickless -> new UI, selection & more - AutoInsultReloaded: -> completely reworked, more customization -> improved reliability klick for... release 1.0.9 full changelog

while it's not as perfectionist and architecturally clean as i'd imagine a perfect flutter refactor would be, this is the ultimate change that pretty much fixes any practical problems one could experience. Well handled! this is very much everything a reasonable person could ask for, great change! I mean it's still a browser after all but the debate is heavily shifted into code & implementation cleanliness rather than end-user impact like crashes and imposed browser choices Hats off!

Neat. Not very useful but something working. If you want, you can submit it to the LiquidBounce Resources or by adding it through a pull request to examples: https://github.com/CCBlueX/LiquidBounce-Addon-ScriptAPI/tree/main/examples Both will make it available through the Marketplace command.

i was wrong about combat, combat only breaks after use in SINGLEPLAYER world

@vClutch Most configs that are available online are created by the community itself. However, many of them do not receive proper updates and become outdated over time. For example, I personally know a config for FunTime: its last update was 15 months ago. Meanwhile, the server uses the Polar anti-cheat. I don't think I need to explain that such a config is most likely no longer relevant, even if it is still labeled as "bypassing." I would recommend either creating your own config or looking for a newer one online.

Android isn't supported, and it won't be. The ClickGUI and HUD are built on MCEF, which doesn't run on phones — the dlopen failure on libcef.so is exactly that. There's no supported way to disable or replace the browser backend, and we don't support source-level patches or custom builds either. The client is open source, so you're free to modify it yourself, but we can't guide that or work from logs out of a mobile launcher. Supported platforms are Windows, macOS and Linux. 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.

你下载Coludflame warp就可以了

There is no need for a Trigger Bot script. Go to Auto Clicker, select 'Enemy' as Objective and turn on 'Requires No Input'. That's it.

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.

It should not.

@izuna I'LL CRY THEN

Thank you.

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.

That was a bug. It has been fixed already.

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.

Happy to help you get your first script working. Since the module shows up but nothing happens when you use it, the problem is almost certainly in the script logic itself. Could you paste the contents of WindChargeThrower.js so I can actually look at it? You can drop the file at https://paste.ccbluex.net and send the link here. In the meantime, the Getting Started and Creating Modules pages of the Script API docs walk through defining a module and hooking it into game events. A very common first-project issue is the event handler not being registered at all — worth double-checking that before anything else. 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.