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, talking to the login server or opening the game server connection. | Wait, or click Disconnect to cancel it. |
| Awaiting your answer | The bot needs you to pick a server in the Pick a server card. | Pick a server, or click Disconnect. |
| Connected to login server | The login stage is done but no game server connection is open. It shows for a moment between two stages of a Full socket connection, and it stays after a Full socket bot's game connection dropped. | Click Disconnect, then Connect again. |
| Waiting for your game client | The bot waits for a Dofus client you play, in MITM mode. It can stay like this indefinitely. | Start Dofus and sign in, or click Disconnect. |
| Connected to game server | The bot has a game server connection: its own in Full socket mode, or your game's session in MITM mode. | Play, or Disconnect. |
A bot only changes state because you asked it to, or because a connection attempt finished, a relayed session arrived, or a connection dropped. When a connection drops, nothing reconnects: a Full socket bot stays on Connected to login server, and a MITM bot goes back to Waiting for your game client.
Full socket mode and MITM mode describe the path through these states in each mode.
Script states
The Behavior column of Bot Manager shows the state of the bot's script:
| State | Meaning |
|---|---|
| Running | The script of the loaded package runs. |
| Stopped | No script runs. The bot may still have a package loaded. |
| Failed | The script stopped with an error. The bot's page shows why. |
The header of a bot's page
The header has two groups of controls, one for the connection and one for the package.
Connection
- While the bot is Disconnected, the group shows Connect and Start waiting. Connect is greyed out for a bot without an account, with the tooltip "This bot has no Ankama account to sign in with."
- In every other state, it shows Disconnect, which ends whatever is happening: a connection attempt, waiting, or a connection.
When Connect fails, Asteroboard shows Couldn't connect the bot with the reason. When Start waiting fails, it shows Couldn't put the bot into waiting, and when Disconnect fails, Couldn't disconnect the bot.
Package
- The package the bot will play: its name and version, Inline script for a pasted script, or No package selected. When several versions of that package are installed, it's a menu to move the bot to another version, with a link to the package's page. Run a package explains the version switch.
- Play starts the script of the loaded package. It's greyed out until the bot is Connected to game server, with the tooltip "Connect the bot to a game before playing a behavior." With nothing loaded, it opens the load dialog instead of playing. If the script can't start, Asteroboard shows Couldn't start the behavior.
- Stop replaces Play while the script runs. It stops the script and leaves the connection as it is. Couldn't stop the behavior means it failed.
- The menu at the end of the group holds three entries:
- Load a new package opens the Load a behavior selection dialog. Choose Library package, and pick an installed package or click Download one, or choose Inline script and paste a script, then click Load a new package at the bottom of the dialog. The script that was running is stopped first, and the new choice isn't started: press Play afterwards. The dialog's own description says loading doesn't affect a running script, but it does stop it. If loading fails, Asteroboard shows Couldn't load the selection.
- Load a package and play it opens the same dialog and presses Play once the package is loaded.
- Unload package stops the running script and clears the bot's package, which then shows No package selected. Couldn't unload the package means it failed.
There's no reload button: to restart a script, click Stop, then Play. Loading a package with the dialog also sets the bot's language back to French, as Bot settings explains. Run a package covers playing packages in detail.
Row actions in Bot Manager
The three dots at the end of a bot's row in Bot Manager open the same actions, grouped the same way, plus Delete bot:
| Action | Available |
|---|---|
| Connect | While the bot is Disconnected and has an account. |
| Start waiting | While the bot is Disconnected. |
| Disconnect | In every other state. |
| Play, or Stop while the script runs | Play once the bot is Connected to game server. |
| Load a new package | Always. |
| Unload package | Only when the bot has a package or an inline script loaded. |
| Delete bot | Always. See Disconnect, delete and restart. |
Load a package and play it is only in the header of the bot's page, and Delete bot only in this menu.
Problems alerts
When something fails, a red alert appears under the header, on every tab of the bot's page:
| Alert | When it appears |
|---|---|
| Couldn't connect this bot | The bot's last connection attempt failed. It shows the reason. |
| The behavior stopped with an error | The script ended with an error, including when its game connection was lost. It shows the error. |
The text is selectable, Copy puts it on your clipboard, and Dismiss hides the alert. A dismissed alert stays hidden until a different error comes or you reload the page. The connection alert goes away when you click Connect again.
Some script errors never reach this alert. When a script can't even be loaded, for example because of a syntax error or an import that doesn't resolve, Asteroboard only shows Couldn't start the behavior, without the reason. For a package from your library, the bot's Settings tab shows the reason, under Package settings. Errors thrown once the script has started do reach the alert. Package errors helps with both.
One connection attempt at a time
A bot runs one connection attempt at a time. Asteroboard only offers Connect and Start waiting while a bot is disconnected, so you rarely run into this. If a second attempt arrives anyway, for example from another open Asteroboard tab, Asterobot refuses it and Asteroboard shows Couldn't connect the bot.
A bot also has one game session at a time: it can't wait for your game client while it's connected on its own, or sign in on its own while it relays your game.
Where to go next
- Bot page, for the tabs of a bot's page.
- Run a package
- Disconnect, delete and restart