Addons & packs

How addons work

Drop a .java file in ~/Arsenic/addons/ (C:\Users\<name>\Arsenic\addons on Windows). Arsenic compiles it with an embedded Java 8 compiler when the client starts, or when you run .addon reload in chat. A file with compile errors is skipped and the errors are printed in chat; the rest still load.

.addon new MyModule combat   # create a module from a template
.addon reload                # compile + load everything
.addon list | .addon folder

An addon is a normal module: @ModuleInfo, public Property fields, @EventLink listeners and onEnable/onDisable. You write against the usual MCP names (mc.thePlayer, mc.theWorld). Settings and enabled state are saved in configs and survive reloads.

Let an AI write it

Give any AI the link to ADDONS.md and describe the module you want. Save the file under its class name, run .addon reload, paste any compile errors back to the AI, then enable it in the ClickGUI.

Default packs

Packs are bundles of addons. The v3.0 repo ships these:

Good to know

• Addons run with the game's full permissions and there is no sandbox — only run addons you trust.
• No Mixins or ASM in addons; private Minecraft state is reached through accessor interfaces.
• Addon rules of thumb in the docs: silent rotations, jittered delays and bounded reach. They reduce flags but do not make anything undetectable.

Full reference: ADDONS.md and UTILITIES.md.