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: names are the only thing that tells bots apart in lists and in their page addresses, and they can't be changed later. Bot Manager sorts bots by name.
In MITM mode, names also decide which bot takes a new game session first, as explained below.
Full socket mode: one Ankama account per bot
Every Full socket bot needs an Ankama account of its own. Dofus allows one game session per account, and Asterobot refuses a second bot for an account that already has one: Add a bot fails with Couldn't add the bot, and a bot's Settings refuse it with this account is already associated with a bot. So store one account for each bot in Account Manager, as Add an account shows.
Each bot connects when you click its own Connect. There's no button to connect every bot at once.
Ankama sign-ins happen one at a time across all your accounts. When several bots connect at once, each one waits for the previous account's sign-in step to finish, and an account signing in through the browser, which can take up to two minutes, keeps the others on Connecting… in the meantime. Connecting bots one after the other avoids the wait piling up.
Each bot also gets its own random device identifier when it's added. See Bot settings.
MITM mode with several Dofus clients
In MITM mode, short for man-in-the-middle, every Dofus client started from the same Dofus folder goes through Asterobot while at least one bot is waiting: the line Asterobot changes in that folder applies to all of them. All clients share the same two ports, and Asterobot matches each session with a bot by the Ankama account it signed in with. MITM mode explains the rule.
The first time, a bot without an account attaches itself to the first account whose session it takes, in alphabetical order of the waiting bots. To decide which bot relays which account, attach them one by one:
- Add one bot per account you play, without accounts, with names you'll recognize.
- Click Start waiting on the first bot only.
- Start a Dofus client and sign in with the account you want on that bot. The bot shows Connected to game server, and its console shows
Attached to Ankama account. - Click Start waiting on the next bot, start another client and sign in with the next account. Repeat for each bot.
From then on, click Start waiting on all of them and start your clients in any order: each session goes to the bot attached to its account, even after Asterobot restarts. A session for an account no bot is attached to goes to any waiting bot that isn't attached yet, and when there's none, it plays normally without going through a bot.
A bot with an Ankama account can wait too, but its attachment isn't kept across restarts, and it doesn't have to match the account stored for it. For relaying several games, bots without accounts are easier to keep in order.
For clients running on other computers, see MITM across machines.
The bot limit
Adding bots and connecting them in Full socket mode depend on your asterobot.net account. Two messages can stop you:
| Message | What it means |
|---|---|
this installation is not entitled to start bots |
Asterobot couldn't confirm your asterobot.net account. That happens when Asterobot isn't signed in, when it hasn't reached asterobot.net for more than an hour, or when asterobot.net refused it. |
this account's bot limit has been reached |
You already have as many bots as your asterobot.net account allows. |
The first one is checked when you add a bot, when you change a bot's account or game version, when you click Connect, and when Asterobot brings bots back as it starts. The second one is checked when you add a bot and when Asterobot brings bots back as it starts, and every bot listed in Bot Manager counts towards it, connected or not. Putting a bot in waiting for your game client isn't subject to either check.
Where you see them depends on what you did. Connect shows the message in Couldn't connect the bot and in the bot's alert, and Save settings shows it in Couldn't save the settings. Add a bot only shows Couldn't add the bot, without the reason.
What to do:
- For the first message, check the account button at the bottom of the sidebar. If it doesn't show your asterobot.net name, sign in again as Sign in with asterobot.net explains, and make sure the computer where Asterobot runs can reach asterobot.net.
- For the second, delete a bot you no longer use, then add the new one.