Bots

What a bot is in Asterobot, what it remembers, how its connection, package and script relate, and how to read the Bot Manager table. In Asterobot, a bot is a saved setup: a name, a game version and a few preferences, plus an Ankama account and a package if you want them. It isn't a running program. Adding a bot connects nothing and plays nothing: you bring it online, and start its script, when you decide to. What a bot remembers Part What it is Where you change it Name The bot's identi

Every tab and field of the Add a bot dialog, why Add bot can stay greyed out, and what happens after you click it. Open Bot Manager and click Add a bot. The dialog has five tabs: Identity, Game, Connection, Behavior / Script and Live data. A ready game version is the only thing you can't skip; everything else can wait, and nearly all of it can be changed later on the bot's Settings. Your first bot walks through a MITM bot step by step. Identity Name Lowercase letters, digits and hyphens, fro

Connect a bot that signs in and talks to the game servers on its own, with no Dofus client, and follow each stage of its connection. In Full socket mode, a bot does on its own what a Dofus client would do. Asterobot signs the bot's Ankama account in, picks a game server and opens the connection to it, with no Dofus window anywhere. From there, a package takes over. Caution Using bots breaks Ankama's terms of use, and Ankama can sanction the accounts involved. Read Accounts and safety first.

Let a bot relay the Dofus client you play, understand the one line Asterobot changes in your Dofus folder, and know which bot gets which game session. In MITM mode, short for man-in-the-middle, you play Dofus as usual and a bot sits between your game and Ankama's servers, passing everything along in both directions. The bot sees the whole session and can run packages, and Asterobot never needs your Ankama login. Your first bot walks through a first setup. Caution A bot in MITM mode is still a

Every connection state a bot can show, what each button on a bot does, and the alerts that appear when a connection or a script fails. A bot's connection and its script each have a state, and the bot's page and Bot Manager give you the buttons to change them. Connection states State What it means What you can do Disconnected No connection, and not waiting for a game client. Connect, with an account, or Start waiting. Connecting… A connection attempt is running: signing in to Ankama,

Change a bot's account, game version, language, server selection, device identifier and default package after adding it, and know when each change applies. Everything you chose when adding a bot can be changed later, except its name, on the Settings tab of its page. Two of them, Account and Game version, can only change while the bot is disconnected. Open the settings Open the bot's page and click Settings. Two sections sit at the top: Bot configuration, the bot's own settings, described on

Run several bots from one Asterobot, with one Ankama account each in Full socket mode or several Dofus clients in MITM mode, and understand the bot limit. One Asterobot can run many bots side by side. Each one is added and controlled on its own, the way Add a bot and States and controls describe. What changes with several bots is how accounts, game sessions and names fit together, and that's what this page is about. Names Pick names you'll recognize at a glance, such as farm-astrub or alt-2:

The difference between disconnecting and deleting a bot, what Asterobot brings back when it starts, and why nothing reconnects or plays by itself without a schedule. Disconnecting a bot and deleting it both stop it, but only one of them keeps it. Closing Asteroboard and stopping Asterobot don't do the same to your bots either. Disconnect or delete Disconnect Delete bot Where Header of the bot's page, and its menu in Bot Manager Only the bot's menu in Bot Manager Running script Stopp

Choose when each bot is in the game and what it plays, week by week, and let Asterobot connect it, play the right package and disconnect it on time. A schedule tells Asterobot when a bot should be in the game, as a set of weekly time slots such as Monday from 08:00 to 12:30, and what it plays in each: one package in the morning and another in the evening, for example. When a time slot starts, Asterobot connects the bot and plays the time slot's package, or the bot's own. When it ends, Asterobot