It is now fixed and render modules should now work correctly. https://github.com/CCBlueX/LiquidBounce/commit/e99c92a4692709c0b62292626849c04ae690a703 0 1zun4 committed to CCBlueX/LiquidBounce Use minecraft render system (#1142) Rewrite all render-related modules that made use of our own Render Engine to use the Minecraft Render System. Added RenderShortcuts.kt file containing various rendering functions to simplify the process. The file includes functions to create a RenderEnvironment and modify it with withPosition and withColor functions. The RenderEnvironment can then be used to draw lines, boxes, outlined boxes, and solid boxes using the provided functions. **Rewritten:** - KillAura - ESP - BlockESP - StorageESP - HoleESP - ItemESP - Blink - Tracers - Breadcrumbs - AutoDodge - Rotations **WIP:** - Trajectories (Needs more work) - NameTags (Disabled for now) fixes https://github.com/CCBlueX/LiquidBounce/issues/668

yooo，After checking the relevant files, I now know how to handle this situation. Just clear your browser cache and re import the cookies

Fixed in b79.

I have updated LiquidLauncher today, which may solve your issue. If not please consider checking your Windows Firewall and AV.

@UPMMASTER I tried what you said and it didn't work. The solution I found so far is to set the keyboard language to "English", I usually use "Chinese".

@UPMMASTER Didn't the developer tell you not to use two hacked clients at once? Especially when the other could potentially target the same or similar functions of this client?

@UPMMASTER Not really. It would require us to change our injection in a way it does not conflict with other clients, which is not our main priority at the moment and likely never be. Even if we make it possible, we know it's working and we did it as well in the past, but out of joke. The usability of clients will drastically reduce.

@ybyyby_-awa Should be fixed...

@CzechHek Thank you for your answer

"fix pls", I mean what do you think we are doing in a development build? Most features are not even finished so they probably are not going to work for everyone. This is not reporting bugs, but reporting unfinished features which we already know. I appreciate if people report bugs, but not on this early stage.

@pepeshki microsoft does not like you. Joke besides, what JRE are you using (Do you use the Launcher?)? What browser is it opening?

@puffffffs You're most likely talking about LiquidBounce b2, that version is really old (5 year old), it has a weird and completely different ScriptAPI support if I remember correctly, so modern scripts will not work on that version. There is also cross-version, which is an unfinished 1.8.9/1.12.2 LiquidBounce b73 made by CCBlueX, it is really buggy, most scripts won't work at all, and some modules won't even work. It has been removed since April 2022. (Marco reverted the source code to pre-Crossversion and fixed the source code.). By the way, LiquidBounce b73 isn't updated by the developers and only pull requests are accepted most likely.