LiquidBounce Forum

Hello, yes I know. It's been a long time we released a offical version und you might be wondering what the heck we're doing.

First of all we've done our cross version system to provide latest builds for 1.8.9 and 1.12.2. We thought it would be a good idea, but in the end it's just a bloody mess. @superblaubeere27 did his best and even was able to finish it. I don't even know how he was able to not just quit and throw everything out of his window. Now we're trying to get a useable b73 done (+ with a lot of other features). It's not going to be a good update for script makers and contributers, but it's not going to last long. Our next plan is to update to 1.16.2 (or newer) and implement a viaversion like support. It's a way easier and less messy approach, which means we can even use LWJGL 3 and other new stuff.

A very important thing is that we want to get out of our "just download scripts to bypass" situation. We really want to work on new bypasses and you might seen that we're going to update our hypixel bypasses for b73.
LiquidBounce was supposed to be a strongly bypassing client for every anticheat and server, but currently there are not that many specific bypasses and up-to-date configs (please do pull requests, thank you). It should change as soon we're ready to focus on bypasses.

Oh and I'm a human. I can't work 24/7 on a free project while doing school and lying in bed (I'm not LAZY! ✓ just tired).

Hello, just wanted to say that we're heavily working on the nextgen branch of LiquidBounce.

We already added many client features, but it might take a while until we're getting our design and modules done. We're focusing on making the client base as future proof as possible. We don't want to rush it, but I can say that we're getting closer to a useable state. There might be still a few issues that we'll have to figure out, but at least we are able to reach our main goals.

Our goals also has changed a bit. We planned to use Sciter as HTML engine, but we're now using Ultralight and it's a great "Next-Generation HTML Renderer", which fits perfectly in our client and to our base.

LiquidBounce is running on FabricMC on 1.16.5, but is able to join every server from 1.7.X up to 1.16.X using ViaFabric.

As a developer I can tell, that it was the best decision to work on a new base, to make adding new features as dynamic as possible and making it easier to add new modules or commands.
Even making bypasses is getting easier than it ever was.

I'm probably going to post some status updates in the future.

Concepts

Hello,

after our Discord server was terminated for the third time recently, we decided to give Guilded a try. Let's see how this goes.

https://www.guilded.gg/CCBlueX

Hey, long time no see.

We are currently working on the legacy version on the rebacke branch and revert all changes caused by the cross-version. This takes time, but @Senk-Ju and me are already working very well together to get it done quickly. We were able to get from 7k errors (caused by removing the cross-version backend) to around 935, which is still a lot but every hour we get around 200 errors done. You might wonder why we are reverting the cross-version, basically the code is so abstract that developing features gets too complicated for every script developer and even for us and we don't have to support any other versions besides 1.8.9. When we are done, I'll push it to the public and will merge it into the legacy branch. After that, we'll do a lot of testing and implement an updated alt manager fitted for the new Microsoft authentication which is based on Elixir.

After that we will continue working on the LiquidLauncher again. It is almost done and in a useable state, yet it lacks automatic JRE download, auto update and Microsoft auth support and a few design things which are done by @Senk-Ju.

We don't know how the future will be when accounts get much harder to get because of the ms migration, but it is not impossible and yet there are always other servers out there to explore.

After legacy is updated and launcher is released, we can continue working on Nextgen and hopefully get a regular update flow.

I will post updates on this topic every time we get something done.

rebacke is now merged into legacy branch without any of the cross-version backend left. Nothing is wrapped anymore. This means scripts can now be used like in b72. But take care, there might be a few issues left to be fixed.

Note: We know the current build is crashing when used in regular minecraft launcher. This is caused by the github artifact building. We are looking into this. fixed

ViaForge (1.8.X to 1.18.X) and ReplayMod can now be used with latest b73 nightly build thanks to @mems.
Support for cooldown in killaura on 1.9+ server soon!

@kawaiinekololis said in Current status in 2022:

After that we will continue working on the LiquidLauncher again. It is almost done and in a useable state, yet it lacks automatic JRE download, auto update and Microsoft auth support and a few design things which are done by @Senk-Ju.

I will now focus on the Launcher. It is working very well, still a few features are missing and the design has not been fully implemented yet. We will soon create an installer, so you can try it out.

Demo of LiquidLauncher, written in Rust – 01:39
— Izuna 生活

You are not allowed to distrubute a obfuscated version of liquidbounce, without sharing the source code of it.
Please read the GNU General Public License v3.0. (https://github.com/CCBlueX/LiquidBounce/blob/nextgen/LICENSE)

Of couse you can obfuscate it for private use or trying out code obfuscation, but I can gurantee that using ProGuard is not the best choice for Kotlin related projects.

It also does not help if you are just saying: "it will cause a crash". No one can and will help you with this issue. We are not the ProGuard forum or something.

@idk-my-name

We are using access transformer in our forge version:
https://github.com/CCBlueX/LiquidBounce/blob/master/1.8.9-Forge/src/main/resources/liquidbounce_at.cfg
docs: https://mcforge.readthedocs.io/en/1.15.x/advanced/accesstransformers/

In fabric there is something similar named access widener:
https://github.com/CCBlueX/LiquidBounce/blob/nextgen/src/main/resources/liquidbounce.accesswidener
docs: https://www.fabricmc.net/wiki/tutorial:accesswideners

We have now decided to use Tauri instead of Sciter as our frontend HTML/CSS/JS engine while keeping our Rust-lang launcher backend due to limited functionality of Sciter.

The transition went smoothly but required a rewrite of the GUI code (but the design concept is the same) to make it fit for Webview instead of Sciter their own engine.

It now uses acrylic background on Windows 10/11. On Windows 7 it will fall back to blur/translucent.
On macOS it will use vibrancy.
On Linux it... wont be blurred. (might be added when we figured smth out)

Hey, just wanted to say that I am uploading videos to the CCBlueX youtube channel again.

You might want to check them out:
https://www.youtube.com/ccbluex

SkyWars on Hypixel w/ #liquidbounce Nextgen – 01:03
— CCBlueX

BedWars and Smash on CYTOOXIEN w/ #liquidbounce Nextgen – 01:52
— CCBlueX

Hey,

today we have updated Nextgen to Minecraft 1.20.4. Enjoy!
Use our LiquidLauncher to get the newest build of Nextgen.

Minecraft 1.20.4 HACKED CLIENT | LiquidBounce Nextgen – 00:34
— CCBlueX

b73 is now out and can be downloaded from our website or via LiquidLauncher.

My changes from yesterday on the LiquidLauncher:

• Microsoft authentication done.
• Offline auth now will pull UUID of name
• Options has been added and somewhat implemented into design (needs a lil bit of work - but we're getting closer).
• Social buttons will now open the links when clicked on.

LiquidLauncher - Microsoft Authentication implementation – 00:30
— Izuna 生活

1 – 00:19
— Izuna 生活

GitHub Actions always provide a latest binary for Windows (Linux, macOS comming soon)
https://github.com/CCBlueX/LiquidLauncher/actions

and almost ready to be published.

Since 2021, not much has happened in the development of LiquidBounce Nextgen, but with the start of 2023 and the release of our new LiquidLauncher, we are focusing on LiquidBounce Nextgen again.

This shows our contribution statistics and the frequent nightly builds that are uploaded and tested on our new launcher.
Please note that these are still development builds, not official release builds, and may be unstable or have bugs.

Now I am trying to work as hard as I can to complete all the features in the 1.0.0 milestone and make the client as stable as possible. After that we can focus on much more specific bypasses, but from my testing so far the client bypasses very well on most servers without any server specific bypasses. This is due to our mindset of considering every detail.

Because some people have not understood that yet:
We will not go back to working on legacy. Rarely people will make pull requests, which we will confirm and merge, but there will be no changes from me.

LiquidLauncher v0.1.9 is now out, which features a bug-fix for Minecraft 1.20.4 offline authentication.
If you were running into issues before, try again now:

https://github.com/CCBlueX/LiquidLauncher/releases/tag/0.1.9

Hey, I'm actively doing Let's Hacks on our CCBlueX YouTube channel. Currently we are bypassing so many different servers:

CubeCraft (Sentinel)
CUBECRAFT, WHERE IS YOUR ANTICHEAT? w/ #liquidbounce Nextgen v0.1.2 – 02:21
— CCBlueX

Hypixel (Watchdog)
HACKING ON HYPIXEL with FASTEST SCAFFOLD (again) w/ #liquidbounce feat. #lunarclient – 01:27
— CCBlueX

ZoneCraft.ES (Grim)
GODMODE on ZONECRAFT.ES (GRIM ANTICHEAT) w/ #liquidbounce – 02:37
— CCBlueX

Gamster (Intave)
Let's Hack on Gamster BedWars w/ LiquidBounce Nextgen – 01:32
— CCBlueX

Pika-Network (Polar)
HACKING on POLAR ANTICHEAT (Pika Network) w/ #liquidbounce Nextgen – 01:32
— CCBlueX

As you can see, Nextgen offers a variety of bypasses, just like in the old days

So I've been looking into this and I noticed following:

try {
    Chat.print(typeof(scriptManager)); // object
    Chat.print(JSON.stringify(scriptManager)); // undefined
    scriptManager.unloadScripts();
    Chat.print("done"); // works
}catch (e) {
    Chat.print(e);
}


try {
    Chat.print(typeof(commandManager)); // [object]
    Chat.print(JSON.stringify(commandManager)); // {}
    commandManager.registerCommands(); // not working -> TypeError: commandManager.registerCommands is not a function
    commandManager.executeCommands('killaura range 3.4'); // not working, stopped above
}catch (e) {
    Chat.print(e);
}

try {
    Chat.print(typeof(moduleManager)); // [object]
    Chat.print(JSON.stringify(moduleManager)); // {}
    moduleManager.registerModules(); // not working -> TypeError: moduleManager.registerModules is not a function
    moduleManager.getModule('KillAura').setState(false); // not working, stopped above
}catch (e) {
    Chat.print(e);
}

After changing the variable name of commandManager and moduleManager to pickaxe and stone it suddenly worked!

scriptEngine.put("stone", moduleManager)
scriptEngine.put("pickaxe", commandManager)
scriptEngine.put("scriptManager", scriptManager)

So it seems to be conflicting with something else.

Oh my god... I realized. It was caused by the ScriptAPI v1 legacy support script. >(

    this.moduleManager = Java.type("net.ccbluex.liquidbounce.LiquidBounce").moduleManager;
    this.Module = Java.type("net.ccbluex.liquidbounce.features.module.Module");
    this.ArrayList = Java.type("java.util.ArrayList");