LiquidBounce for Minecraft 26.3 comes with a big change: configs and add-ons now live in one place, the marketplace. Here is how both work.
What is an add-on?
LiquidBounce can be extended in three ways:
- Themes change how the menus, the ClickGUI and the HUD look.
- Scripts are small JavaScript files that add a module or a command.
- Add-ons are extra packages for the client, built the same way as LiquidBounce itself. They can add modules, commands, HUD elements, whole new categories in the ClickGUI, and even a different browser for the menus.
Scripts still work, but they need the ScriptAPI add-on now, because the part of the client that runs them became an add-on too.
Installing an add-on
The ClickGUI now has a Marketplace tab. Open the ClickGUI with Right Shift, pick Marketplace, switch to Add-ons and click Install.
If you prefer the chat, type .marketplace subscribe Extras. Add-ons are loaded while the game starts, so restart LiquidBounce afterwards. .addon list shows what is installed, and .marketplace unsubscribe removes it again. The chat suggests what you have installed.
Every add-on is built for one Minecraft version. LiquidBounce only installs the ones that fit the version you play, so an add-on that has not been updated yet simply waits until it is.
These add-ons are on the marketplace right now:
- Extras brings modules that are not part of the client, for example AutoShearer, AutoSign and LightOverlay, which marks the blocks where monsters can spawn.
- ScriptAPI runs your scripts.
- Ultralight and Wry let you use a different browser for the menus. We compared them in a separate post.
An add-on can do everything the client can, so only install add-ons from the marketplace or from people you trust. Uploads are checked by our team before players get them, unless they come from a publisher we already trust.
Making your own
If you know a bit of Kotlin or Java, you can write an add-on yourself. Start from the add-on template, and the new Add-on API documentation explains modules, settings, commands, HUD elements and publishing, with an example for everything. Once your add-on is ready, publishing a GitHub release uploads it to the marketplace.
Configs from the community
A config is a saved set of module settings, for example one that works well on a certain server. Configs used to come only from us. Now anyone with a LiquidBounce account can publish one, and configs picked by our team are Featured and listed first.
In the Marketplace tab you click Load on a config. You can also load only some of its modules, for example just the KillAura settings.
Players report whether a config works or is broken, and those reports decide which configs are shown first. If you prefer the chat, .config list, .config search and .config load do the same.
After loading a config, the toolbar keeps track of it. When you change a setting, it shows Edited, and its menu lets you publish your changes, go back to the config, or restore the settings you had before loading it.
The AutoConfig module can also load the best config for a server by itself when you join. By default it only uses featured configs.
The config guide and the add-on guide explain everything in detail. Try it out, publish a config for your favorite server, and tell us what you think on our Discord.