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 | Stopped | Stopped |
| Connection | Closed. A relayed session ends too, which disconnects your Dofus. | Closed, the same way |
| Waiting for your game client | Stopped. If no other bot waits, the line in your Dofus folder is put back. | Stopped, the same way |
| The bot and its settings | Kept | Forgotten |
| Package settings and message selection | Kept | Forgotten |
| Console history | Kept | Gone |
| Account attached in MITM mode | Kept | Forgotten |
| Stored Ankama account | Kept | Kept |
| To use the bot again | Connect or Start waiting | Add it again from scratch |
To delete a bot:
- In Bot Manager, open the bot's menu and click Delete bot.
- The Delete this bot? dialog reminds you that it stops the running behavior, closes the bot's connections and forgets the bot and its saved configuration, while the stored account is kept. Click Yes, delete.
If deleting fails, Asteroboard shows Couldn't delete the bot. Delete isn't in the header of the bot's page, so it can't be clicked by mistake while you watch a bot run.
What Asterobot brings back when it starts
Every bot is saved in bots.toml, in Asterobot's data folder. When Asterobot starts, it brings each one back with everything you set: its name, account, game version, language, server selection, device identifier, default package, package settings and message selection. It also keeps what it learned: the server the bot last connected to and, for a bot without an account, the Ankama account it attached to. The terminal shows Bots restored from config with how many were restored out of how many were saved.
What doesn't come back:
- Connections. Every bot starts Disconnected, including bots that were waiting for your game client.
- Running scripts. Nothing plays.
- An inline script you loaded on a bot. Its default package stays.
- The console history. Asterobot keeps the last 200 lines of each bot's console while it runs, and starts empty.
- The attachment of a bot with an account that waited for your game client. Bots without an account keep theirs.
Nothing reconnects or plays by itself
Asterobot never connects a bot or starts a script on its own. Signing accounts in to Ankama, or starting scripts, is something that only happens when you click. That holds in every situation:
- When Asterobot starts, bring each bot online again with Connect or Start waiting, then press Play on the ones that should run a package.
- When a Full socket bot's game connection drops, the bot shows Connected to login server and its script stops. Click Disconnect, then Connect, then Play.
- When you quit Dofus in MITM mode, the bot keeps waiting and takes your next session by itself, because you left it waiting. The script that was running stopped, though: press Play again once your game is back.
Bots that don't come back
Asterobot skips a bot at start, instead of failing, when:
- its Ankama account is no longer in Account Manager;
- its game version is no longer installed in Game Manager;
- Asterobot couldn't prepare Ankama sign-ins, for example because the computer had no internet access as Asterobot started. This only affects bots with an account;
- Asterobot couldn't confirm your asterobot.net account in the first seconds after starting, for example because it wasn't signed in or asterobot.net didn't answer in time. Then every bot is skipped.
A skipped bot doesn't appear in Bot Manager, and its page says "This bot isn't registered (or was removed)." The terminal shows a warning starting with skipping bot restore: followed by the reason, such as account not found or game version not installed.
Its configuration isn't lost. It stays in bots.toml, and the bot comes back at the next start once the cause is fixed: add the account again with the same Login ID, reinstall the game version, or sign Asterobot in, then restart Asterobot.
Warning
Adding a new bot with the name of a skipped bot replaces the skipped bot's saved configuration for good.
Closing Asteroboard, stopping Asterobot
Closing Asteroboard stops nothing. Your bots stay connected and their scripts keep running, because they live in Asterobot, not in the page. Open Asteroboard again, from any browser, to find them as they are.
Stopping Asterobot stops everything. Every bot disconnects, including bots relaying the game you're playing, so your Dofus is disconnected too, and every script stops. Stopped normally, with Ctrl+C or Shutdown server, Asterobot also puts back the line it changed in your Dofus folder. If it's stopped abruptly, it puts that line back the next time it starts.
The three parts explains what lives where, and First launch how to stop and start Asterobot.
Where to go next
- States and controls
- Files and folders, to back up
bots.tomlandaccounts.toml. - Reset and start over