The header every bot page shares, with the character's status, its connection and package controls, the tabs below it, the server choice card and the alerts that report problems.
Each bot has a page where you watch it and control it. Open Bot Manager and click the bot's name: the page opens on the Console tab. Every tab shares the same header, so the controls and the alerts described here are always in reach.
The header
The bot's name sits on the left, with its character's status beside it. On the right are two groups of controls: one for the bot's connection, one for its package.
Status
The menu beside the bot's name is the game's status menu, the one at the game's chat box. It shows your character's status with its dot, in the game's colours, and changes it.
Warning
This really changes your character's status in the game, for every player.
| Status | What the game says about it |
|---|---|
| Available (green) | "Anyone can interact with you." |
| Away (orange) | "Nobody can interact with you, but you can receive private messages." |
| Away... (orange) | The same, with a message the game sends back to whoever whispers your character: a window asks for the Reason for being away:, 256 characters at most. Hovering over the menu shows your message. |
| Private (blue) | "Only your friends can interact with you. This status is not retained after logging out." |
| Solo (red) | "Nobody can interact with you." |
The names, the descriptions and the colours are the game's, in Asteroboard's language. The menu shows the status the game confirms: if the game refuses the change, or you change the status from your own game client on a relayed bot, it shows what the game says. Idle, orange too, is the status the game client sets by itself after a while without activity: the menu shows it when the game reports it, but doesn't offer it, as in the game.
As in the game client, a character entering the game counts as Available until the game reports a change. The menu is greyed out until the bot is Connected to game server, with the tooltip "The character must be in the game to change its status." Each change also prints the game's own line in the console, such as "Away status activated.": see Console.
If the dots are all grey, the game version was downloaded or extracted before Asterobot read the status colours. Use Download more files in the version's menu, then extract it again: see Manage game versions and Extract the game data.
Connection
The first group shows the bot's connection state, next to the buttons that change it.
| State | Buttons |
|---|---|
| Disconnected | Connect, which signs the bot in with its Ankama account, and Start waiting, which makes it wait for your Dofus client. Connect is greyed out for a bot without an account, with the tooltip "This bot has no Ankama account to sign in with." |
| Any other state: Connecting…, Connected to login server, Awaiting your answer, Waiting for your game client or Connected to game server | Disconnect, which ends whatever the bot is doing. |
States and controls explains each state. Full socket mode and MITM mode explain the two ways to connect.
When one of these buttons fails, a notification says so: Couldn't connect the bot with the reason, Bot's game version isn't ready yet, Couldn't put the bot into waiting or Couldn't disconnect the bot. See The bot doesn't connect.
Package
The second group is about the bot's package:
- The package the bot is set to play, as
name@version, Inline script or No package selected. When several versions of that package are installed, it's a menu to switch between them; otherwise it opens the package's page. It turns orange when the version is incompatible with your Asterobot. - Play, which becomes Stop while the script runs. Play is greyed out until the bot is Connected to game server, with the tooltip "Connect the bot to a game before playing a behavior."
- A menu with Load a new package, Load a package and play it and Unload package.
Run a package explains each of them.
Tabs
| Tab | What it's for |
|---|---|
| Console | What Asterobot says about the bot, what its script writes, and the game chat. See Console. |
| Character | The character sheet as the game sends it, with the game's own icons and the class portrait, and the Jobs card: each job's level, its experience to the next level, what it harvests at that level, and the next resource it unlocks with the level it needs. The jobs show as soon as the character has entered the game, without the live character switch, and stay as Last known once the bot disconnects. |
| Information | The Ankama account and the server of the bot's session. Its name turns orange while the bot waits for you to pick a server. See Information. |
| Map | The character's map, live: who is around and what can be used, and controls to walk, change map and use doors, zaaps and resources. See Map. |
| Fight | The fight module: whether it plays the bot's fights, the profile and speed it plays them with, and the turn log of the last fights. See The fight module. |
| Chat | The chat module: whether the bot talks on its own, and which of its ads, replies, triggers, commands and status, the chat profiles they come from, the guard's state with Stop sending, each ad's state and the last lines, commands and triggers. See The chat module. |
| Inventory | The character's items, kamas and pods. See Inventory. |
| Tools | The Network tool, to watch the bot's messages and send messages by hand, and the Memory tool, which shows what the bot's scripts keep in its memory. See Network traffic and Send messages by hand. |
| Settings | Bot configuration, the bot's own settings (see Bot settings), and Package settings (see Package settings and actions). |
Each tab has its own address, so reloading the page keeps you on the same tab.
Pick a server
A bot's connection sometimes stops to ask you which game server to join: when the bot is set to ask every time, or when it can't choose by itself because its forced server isn't available or no server is online and open to the account. The state then reads Awaiting your answer, and a Pick a server card appears under the tabs, whichever tab is open, with "This bot is set to always ask - choose which server to connect to below."
The card shows one tile per server, with its picture, name and number, a status badge (Online or Maintenance), its server type, Mono-account for mono-account servers and, where the account has characters, how many. The information icon next to a name shows the server's description. Only the servers you can join right now can be clicked; the others are greyed out.
Click a server, and the connection carries on. If your answer can't be sent, Couldn't send your answer appears.
When a bot starts waiting for an answer while you're somewhere else in Asteroboard, a notification tells you, such as Bot "my-bot" needs your input, with a Go to bot button. Server selection itself is explained in Full socket mode.
Problems
Red alerts under the tabs report what went wrong, on every tab:
| Alert | What it reports |
|---|---|
| Couldn't connect this bot | The bot's last connection attempt failed. The text is the reason. |
| The behavior stopped with an error | The bot's script failed. The text is the error it stopped with. |
Each alert shows the complete text in a box you can select, with a Copy button and a Dismiss button. Dismiss hides that exact message. It comes back after you reload the page, and a different message always shows.
Not every failure reaches this area. When a package can't even start, because it's missing, incompatible or has an error in one of its files, you only get a Couldn't start the behavior notification without a reason. The bot's Settings tab, under Package settings, then shows the reason. Package errors covers each error, and script authors will find more in Errors.
When the bot doesn't exist
If the bot was deleted, or Asteroboard can't reach the Asterobot it belongs to, the page says "This bot isn't registered (or was removed)." with "It may have been removed, or the server it lives on isn't reachable."