A few things worth knowing.

JNbot manages Minecraft bots and automates repetitive tasks. Record your actions, replay them with a bot, run scripts, and manage your accounts from one workspace.

Server rules vary. Check your server's automation rules before running a bot or plugin. A plugin being available in JNbot does not guarantee that a server permits it.

Head to the download page, pick your OS (Windows, macOS, or Linux), and follow the installer. The site auto-detects your platform.

Gkit collector and upgrader, kit collector, book sorter, alt scanner, bot manager, and packet proxy, plus a full extension API. You can add your own logic with the plugin system or write a JavaScript plugin against the JNbot API.

No. JNbot acts as a Minecraft client without the heavy UI, so it is lightweight and runs in the background. You do not need the game launched alongside it.

Yes. Use the CLI version on a VPS, a Raspberry Pi, or any machine with Node.js (18.0.0 or higher). It runs headlessly and keeps your bots online while your main PC is off. Get the CLI build.

First check you are on the latest version. Then scan the troubleshooting section below. If you are still stuck, join our Discord for hands-on help.

The desktop app is free. The mobile app may show ads and offer a one-time purchase to remove them.

JNbot works on many Minecraft servers. Most of the scripts assume a fairly standard setup, so they may not behave the same everywhere. You can change the host in settings to use the underlying bot framework on other premium or cracked servers, but the script library may not work as expected.

Yes. Create a Recording plugin, choose a connected Minecraft client, and perform your task. You can edit its actions and timing before replaying it with a bot. Read the recording guide.

You choose. Replay at the original world coordinates, or use positions relative to the bot's starting point. Choose original coordinates for tasks tied to a specific location.

Some scripts (gkit collector, kit collector) have a setting like skip alts with no gkits. If that is enabled and an alt does not meet the requirement, it gets skipped. Toggle the option off in settings if you want every alt to join.

The server stopped responding to the bot. This is usually a flaky internet connection. Try again, or switch networks if it keeps happening.

The connection was closed unexpectedly, which could be network or server side. Reconnect the bot. If it keeps happening, lengthen the delay between actions: settings → script → delay between actions.

Report it in the Discord. False flags from anti-cheat are tracked there and patched as bugs.

This usually happens when too many alts join in too short a window. Either reduce the concurrent count, or increase the join delay: settings → scripts → bot join delay.