LiquidBounce for Minecraft 26.3 changes how configs and add-ons work: both now live in the marketplace.
Add-ons
LiquidBounce can be extended with themes, scripts, and add-ons.
Themes change how the menus, ClickGUI and HUD look. Scripts are small JavaScript extensions that add modules or commands. Add-ons are more powerful packages built like LiquidBounce itself and can add modules, commands, HUD elements, ClickGUI categories and even replace the browser used for menus.
Scripts still work, but now require the ScriptAPI add-on.
Installing add-ons
The easiest way is with LiquidLauncher 0.7.0+.
Open Settings → Client. From there you can see your LiquidBounce build, mods and installed add-ons.
Click Browse next to Add-ons and install what you want. Themes and scripts from the marketplace show up there too.
The launcher automatically installs the correct add-on version for the Minecraft version you launch. If an add-on has not been updated yet, it simply stays disabled until a compatible version exists.
You can also manage add-ons from chat:
.marketplace subscribe Extras.addon list.marketplace unsubscribe
Add-ons load when the game starts, so restart LiquidBounce after installing one. The launcher and client use the same subscription list.
Current add-ons include:
- Extras — extra modules like AutoShearer, AutoSign and LightOverlay.
- ScriptAPI — adds script support.
- Ultralight and Wry — alternative browsers for LiquidBounce menus. We compared them here.
Add-ons can do everything LiquidBounce can, so only install them from sources you trust. Marketplace uploads are reviewed by our team unless they come from an already trusted publisher.
Making your own
If you know Kotlin or Java, start with the add-on template.
The Add-on API documentation covers modules, settings, commands, HUD elements and publishing.
Once your add-on is ready, publishing a GitHub release uploads it to the marketplace.
Community configs
Configs are saved module settings, usually made for a specific server.
Previously, configs only came from us. Now anyone with a LiquidBounce account can publish them. Configs selected by our team are marked Featured and shown first.
The important commands are:
.config list/.config search— find configs.config load— load one.config report works/.config report broken— rate whether it works.config revert— reset back to the loaded config.config restore— restore your settings from before loading it.config publish new— publish your current settings
You can also load only parts of a config, such as its KillAura settings.
Reports affect which configs are shown first, so good configs should naturally move up over time.
The AutoConfig module can automatically pick a config when you join a server. By default, it only uses featured configs.
More details are in the config guide and add-on guide.
Try the marketplace, publish something useful, and tell us what you think on Discord.