no one cares

@why_not use pre-crossversion, russian kid :lenny:

@wtf thx

@mockslim69 turn off AntiBot

@Foreheadchan_ Thank you so much! I updated optifine to latest version and removed foamfix. Everything now is working fine

@Leejames2305 everything worked fine before windows update.

Tryna enabling players, dead and invisible in targets??????????

@fps14 there WILL be logs. liar!

Update Java to new version, i see problem in ticking entity. Also, it seems you have NBT modding mods (or like this mods), delete them. Them causes ticking screen & ticking entity while you have optifine/liquidbounce with this mods(Like as combine nbt modding mod + optifine/liquidbounce)
UPD: Also, remove texture pack

Not a bug probably. What LiquidBounce version are you using?

wdym? Latest Beta - ffe6cb6 is the one with many problems.

I currently using this as the alternative. http://www.mediafire.com/file/ee2ha0yvkvdopjn/OldCustomLiquidBounce-b73.jar/file

bc youre using labymod and that breaks some render modules

edit: also post a video or smth cause i might be wrong and it could be something else

That's what my tracers looked like when I used eventRender2D

fart build(PLZ DO NOT BAN ME!!!!)

@Senk-Ju said in liquidlauncher:

@Amy-Chang LiquidLauncher does not require a Java installation. We are working on an updated version which should hopefully fix all problems people are currently experiencing with it. For now, use the default launcher. Read the installation tutorial for more information.

@Amy-Chang LiquidLauncher does not require a Java installation. We are working on an updated version which should hopefully fix all problems people are currently experiencing with it. For now, use the default launcher. Read the installation tutorial for more information.

thank you so much

LiquidLauncher currently has some known bugs. A new version should be released relatively soon. For now just use the regular launcher.

@skiddermaster412 since you wrote e.getPacket().wrapped.y when you have event as a parameter, instead of writing event.getPacket().wrapped.y which you should have done

Just guessing.

Yeah, known bug.