administrators

@f0xy nextgen does not support linux atm

@CzechHek Yes that would make sense, making it possible to access certain important utility functions in a standardised matter that we are not going to change to support scripts as long as possible.

@guosic This is the problem that prevents the macro script from loading in newer versions.

Instead of accessing the commandManager using the predefined variable, it tries to access it using a static variable (which no longer exists) directly from the LiquidBounce class.

I will update the script on the Scripts page as soon as possible, but I am currently working on the new Marketplace / User Resources page, so it will be replaced very soon anyway.

Download: Macros-2.0.1.js

@Tabio stinks that people can't manage to use the more modern ScriptAPI v2 after more than 3 years, knowing that v1 is deprecated.

/// api_version=2
var script = registerScript({
    name: "MyScript",
    version: "1.0.0",
    authors: ["My Name"]
});

script.registerModule({
    name: "MyModule",
    category: "Misc", 
    description: "An example module created with LiquidBounce's script API."
}, function (module) {
    module.on("enable", function() {
        Chat.print("Module enabled");
    });
});

Looks pretty straightforward to me : )

Hello everyone.

It's been over 3 years since we introduced ScriptAPI v2 and with the many changes that have been made to LiquidBounce in the last few months, we have decided to remove support for ScriptAPI v1 to ensure that no issues arise.

An example of such an issue can be seen here:
https://forums.ccbluex.net/topic/7671/why-i-can-t-use-commandmanager-or-modulemanager-in-my-script

Please update your scripts to ScriptAPI v2 to ensure they will work on future versions.
See https://liquidbounce.net/docs/ScriptAPI/Getting for more information.

@isnotpuppy Put this tag on the top of your script:

/// api_version=2

...
code

This will fix the issue.
See: https://liquidbounce.net/docs/ScriptAPI/Getting Started

Also fixed in future versions by removing support for ScriptAPI v1:
https://github.com/CCBlueX/LiquidBounce/commit/3e92903f1372e1c96225bca057f0f136928d3bd5

0 1zun4 committed to CCBlueX/LiquidBounce

removed support for ScriptAPI v1

Please update your script to ScriptAPI v2 to avoid issues in the future.
See https://liquidbounce.net/docs/ScriptAPI/Getting%20Started for further information.

This change fixes module and command manager not being defined correctly.
See https://forums.ccbluex.net/topic/7671/why-i-can-t-use-commandmanager-or-modulemanager-in-my-script/

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");

@CobraSteal This means the server has patched the exploit.

The message looks like that because the translation seems to be missing... whoops

Especially when I see people actively contributing to forks or other clients, I wonder what we did wrong.

When it comes to Legacy, I am very open to not taking coding standards that seriously. I would be very happy if people would commit their bypasses to Legacy or even Nextgen. I also wrote a post about this some time ago: https://forums.ccbluex.net/topic/7570/do-not-be-afraid-to-contribute