Frequently asked questions

An AFK bot is a Minecraft client that connects to a server without a game window and keeps a player online. It stays in the world and moves a little so the server does not kick it for inactivity, which is useful for alt accounts, playtime rewards, farms and keeping a server awake.

No. Bots run on a worker on a server, either our cloud node or your own VPS. You control them from the web dashboard and can close the browser and your PC.

Yes. The worker is a small Node.js program. Start it on any Linux or Windows VPS with a token, add the node URL in the dashboard, and choose it when creating bots. Paid plans include custom nodes.

Add SOCKS5, SOCKS4 or HTTP proxies in the dashboard. Assign one to a bot, or choose the rotation pool so each reconnect uses a different proxy. Bots connect through the proxy, so the server sees the proxy IP.

Java Edition, from 1.8 up to the newest versions supported by the Mineflayer library. Leave the version on auto-detect or pin one. Bedrock Edition, Realms and modded servers are not supported.

Yes. Choose Microsoft auth, start the bot, and the dashboard shows a device code to sign in at microsoft.com/link. The token is cached on the node so you only sign in once.

We cannot promise that. Many servers forbid bots or AFK macros and some detect them. Read the rules of the server, use an alt account, and keep the human-like AFK plugin enabled. You are responsible for how you use the bots.

Checkout is handled by Shoppex, which supports cards and crypto depending on the store configuration. You get access right after payment is confirmed.

Plans are prepaid for the period you choose. Buying a higher plan applies immediately, and when a period ends the account drops back to the 15-minute trial automatically, so there is no surprise renewal.

Yes. Every new account gets a trial: one bot with 15-minute sessions on the cloud node and anti-AFK. It is enough to check that your server accepts the bot before you buy a plan.

The worker is the same kind of Mineflayer code you would write, but you also get a web dashboard, a live console, proxy handling, reconnect logic, Discord alerts, plugins and multi-VPS management without writing or maintaining any of it.

The built-in cloud node is included in every plan up to your bot limit. If you connect your own VPS you pay your hosting provider, not us, and plans only cap how many bots and nodes you can manage from the dashboard.

A headless bot is light. As a rough guide, a 2 GB VPS runs 40 to 80 idle AFK bots comfortably. Plugins that pathfind, farm or fight use more CPU, so watch the CPU and RAM tiles in the Nodes page and add a node when they climb.

Yes. Bots join as normal players, receive chunks around them and are counted as online. That is why they work for playtime rewards, keeping a small server awake and chunk loading where the server allows it.

Yes. Open a bot in the dashboard to read its live console and send chat messages or commands as that bot. Movement is automated by plugins and macros rather than steered by hand.

Yes. Choose offline login, enter any valid username, and optionally set an auto-login password. The bot sends /register and /login for you on every join, which suits servers that use AuthMe or a similar plugin.

Bots speak the protocol of the version they connect with. Leave the version blank to auto-detect, or pin one that the server accepts. Servers that run ViaVersion accept several client versions, so a slightly older or newer bot usually still joins.

With auto-reconnect on, the bot waits a randomised, growing delay and joins again, switching to a fresh proxy if you use a pool. The kick reason shows in the console, and a Discord webhook can notify you.

Yes. The crop farmer harvests ripe crops and replants them, the tree chopper cuts logs, auto-fish handles fishing and the item collector picks up drops. You still need to give the bot tools and seeds in its inventory and place it near the work area.

Yes. Player alerts post to your Discord webhook when players join or leave, and chat relay streams chat lines there. Chat triggers can also reply in game when a keyword appears.

No. Everything runs on the worker in the cloud or on your VPS, and you manage it from a web browser. Nothing is installed on your computer.

Passwords are hashed, sessions use signed cookies and node tokens are never sent back to your browser. Proxy passwords are masked in the dashboard. Use a separate alt account instead of your main Minecraft account for any bot.

Only where it is allowed. Many networks ban bots and macros, and joining a server you do not own can break its rules. Ask the owner, read the rules and use accounts you can afford to lose. We do not support raiding, griefing or overloading servers, and join delays are built in.

No. The engine supports Minecraft Java Edition servers running vanilla-compatible protocols. Bedrock, Realms and Forge or Fabric modpack servers are not supported.

About two minutes on the cloud node: create an account, add a bot with the server address and username, and press start. Connecting your own VPS takes a few more minutes to install the worker and paste its URL and token.

Plans are prepaid and you can run a free 15-minute test first to check that your server works. If something is broken on our side, contact support and we will make it right.