Skip to content

Keep your Minecraft clients online, automated, and under control.

Stop babysitting your accounts. Novo Adbot runs each client on the right server, through the right proxy, with the right script attached, and shows you exactly what it is doing. Write code if you want, or snap blocks together if you don't.

Every client, one register.

Add each Minecraft account once, then start and stop clients individually or in bulk. Every session shows its account, server, proxy, script, and uptime.

Automate behavior as code.

Attach a script to any client and let it handle things: log in when it joins, answer chat, come back after a drop. You write against a small async client API with wait and chat built in.

events
join · chat · disconnect · timers
actions
chat · commands · reconnect · move
lifecycle
attach to any client, stop instantly

The same engine, as blocks.

The visual builder compiles to the same automation model as scripts, so nothing is locked to one interface.

Proxies as infrastructure.

Add SOCKS or HTTP proxies. Multiple proxies can be used for an account, but you have to approve each one.

Logs that explain failures.

A combined log for every client, filtered by account or level. When something fails you see the error, the reason, and what the script did next.

From account to running client in four steps.

No server software to install, no per-client config files. The workflow is the same whether you run two accounts or twenty.

  1. 01

    Add your Minecraft account

    Sign in with your account once. Novo Adbot stores the session and tracks its authentication state.

  2. 02

    Choose a server and proxy

    Point the client at a server and route it through one of your proxies, or connect directly.

  3. 03

    Attach a script

    Pick a script or build a block workflow: log in on join, keep a queue alive, fish, guard, idle.

  4. 04

    Start the client

    Start it from the dashboard. Watch status, uptime, and logs live; stop or restart at any time.

FAQ

A managed Minecraft client that stays connected to a server without you playing. Novo Adbot runs it, keeps it online, runs your scripts, and reports status and logs back to your dashboard.

No. Clients run in Novo Adbot and are controlled from the dashboard. You do not need the game or a game window open on your own machine.

That's the whole point. Add each account once and run them all side by side, each with its own server, proxy, and script. Control them one by one or all at once.

Yes. Add SOCKS or HTTP proxies and approve which ones an account may use. You can see at any time which connection a client is using and swap out a failing one.

No. The block builder handles the usual stuff like joining, waiting, sending chat, and reacting to disconnects, all without writing a line. If you do code, the script editor gives you the full client API.

Send chat and commands, wait with jitter, reconnect with backoff, react to chat and events, move, rotate, and schedule actions. Scripts and block flows run on the same engine with the same capabilities.

You'll know right away. The session flips to an error state with the reason in the log, and if your script handles disconnects it reconnects the way you told it to. Otherwise it waits for you.

Yes. The docs cover setup, accounts, scripts, the client API, and troubleshooting. Read them here.

Stop babysitting your accounts.

Set up your first client in minutes: add an account, pick a server, attach a script, and start. One license covers everything: $10 a month, as many accounts as you like.