OPTIONAL SETUP
Run GoNuts without a game window.
Keep MultiMC as your launcher and add HeadlessMC’s LWJGL agent to one working instance. Minecraft and GoNuts still run; the game window and graphics rendering are omitted. This is optional for both individual bots and hives.
1. Start with a working visible instance
- Install the matching Minecraft, Fabric, Fabric API and GoNuts versions in MultiMC. For the GoNuts Minecraft 26.2 build, select a compatible Java 25 runtime in the instance’s Java settings.
- Launch normally, join the server and confirm the bot and scoreboard balance work. For a hive, use a separate instance and Minecraft account for each client; link the hive before hiding its windows.
- Enable GoNuts’ Join the server by itself setting. Open About → Dashboard, visit the dashboard, sign in with Discord and link this installation using its fresh code. Verify its online status, current activity and controls. Alternatively, verify the local web panel before continuing.
- Close Minecraft normally and wait for MultiMC to show the instance has stopped. Save a copy of its current Java arguments so you can restore them later.
Changing launcher arguments takes effect on the next launch. Do not stop a working trading bot just to try headless mode; configure it at a planned safe shutdown.
2. Add the HeadlessMC LWJGL agent
Download the agent from HeadlessMC’s official releases. Use the headlessmc-lwjgl … no-asm JAR, not the command-line launcher. Our Windows setup was verified with headlessmc-lwjgl-3.0.0-RC6-no-asm.jar; another version needs its own compatibility check.
- Put the agent in a stable folder without spaces, for example
C:/hmc/. It is a Java agent, so do not put it in the instance’s mods folder. - In MultiMC, right-click the instance and choose Edit Instance → Settings → Java. Enable the Java-arguments override for that instance.
- Keep the existing required arguments and append the following, replacing both agent paths with the actual file you downloaded:
-javaagent:C:/hmc/headlessmc-lwjgl-3.0.0-RC6-no-asm.jar -Djoml.nounsafe=true -Dfabric.systemLibraries=C:/hmc/headlessmc-lwjgl-3.0.0-RC6-no-asm.jar
If fabric.systemLibraries already exists, preserve its existing entries and add this agent using the platform’s path separator; do not add a conflicting second property. Disable graphics-dependent mods in the headless instance. Our verified setup disabled Sodium, Iris, ImmediatelyFast and Entity Culling while retaining Fabric API and GoNuts.
These agent flags follow the official HeadlessMC LWJGL instructions. MultiMC launches the instance normally; you do not need a second launcher or an offline account.
3. Launch and verify
- Launch the configured instance from MultiMC. No Minecraft window is expected; the instance should remain running.
- Open your GoNuts dashboard and verify that this specific client reconnects and its activity timestamps continue advancing. A running Java process alone does not prove the bot joined or is trading.
- Check the current bot state and any guard or recovery notice. Follow the normal recovery process for held stock; never clear its ledger to make it start.
- For additional accounts, repeat per instance. Each needs its own Minecraft account, dashboard link and confirmed settings. Headless mode does not change Swarm consent or enable trading automatically.
4. Close safely
Use the normal GoNuts controls to finish safely before a planned shutdown. In that instance’s Minecraft folder, create a text file named exactly send-command.txt containing:
!quitIn MultiMC, use the instance’s Minecraft-folder shortcut to locate the correct folder. Ensure Windows has not named the file send-command.txt.txt. GoNuts consumes the file and requests a normal game shutdown. Wait for MultiMC to confirm it stopped; do not use Kill while a purchase, listing or inventory operation is active.
5. Restore the game window
After a safe normal shutdown, remove the headless agent arguments you added, preserve any unrelated Java arguments and restore graphics mods if wanted. Launch again normally. Keep the same GoNuts config and database; no reset or re-pairing is required just to restore graphics.
Troubleshooting
It exits immediately
Check the instance log for the first failure. Verify the agent file exists at both specified paths, the Java runtime matches the Minecraft version and graphics mods are disabled. Do not change account credentials or delete the database to troubleshoot rendering.
The dashboard stays offline
Check whether the instance is still running, joined the server and was linked successfully before hiding it. Account authentication or a Microsoft sign-in may require returning to visible setup. Never share launcher tokens, dashboard credentials or full Java command lines.
I use the standalone HeadlessMC launcher
This guide describes MultiMC with the LWJGL agent. The standalone command-line launcher is a separate setup; use HeadlessMC’s launch documentation for it rather than mixing launcher commands into MultiMC’s Java-arguments field.
