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 identity. Its page address and its saved configuration hang off it, so it can't be changed. | Chosen in Add a bot |
| Ankama account | Optional. Lets the bot sign in on its own in Full socket mode. A bot without one can only relay a game you play, in MITM mode. | Add a bot, Settings |
| Game version | The Dofus version, downloaded by Asterobot, that the bot works with. | Add a bot, Settings |
| Language | A game language saved with the bot. Asteroboard shows the bot's server names in it. | Add a bot, Settings |
| Server selection | How the bot picks a game server when it signs in on its own, and the server it must use when you force one. | Add a bot, Settings |
| Device identifier | The identifier the bot announces for its device when it signs in on its own. | Add a bot, Settings |
| Package | The package the bot plays by default. | Add a bot, Settings, the package menu of the bot's page |
| Package settings | The values you gave the settings its packages declare. | Settings > Package settings |
| Message selection | Which game messages Asteroboard receives from the bot, including the ones behind live chat and live inventory. | Console, Inventory, Tools |
Asterobot also records a few things by itself: the server the bot last connected to, and for a bot without an account, the Ankama account it attached to when it relayed a game for the first time. Bot settings covers every field you can change.
Bots live in Asterobot
Asterobot saves every bot in a file called bots.toml, in its data folder, described in Files and folders. Nothing about a bot is stored in your browser, so any browser or device connected to the same Asterobot shows the same bots. When Asterobot starts, it brings them all back, disconnected. See Disconnect, delete and restart.
Two ways to connect, one bot
A bot doesn't belong to a mode. What it does when you bring it online is your choice each time:
- Connect signs the bot in with its Ankama account and opens a game connection of its own. That's Full socket mode, and it needs an account.
- Start waiting makes the bot wait for a Dofus client you play, and relay its session. That's MITM mode, short for man-in-the-middle, and it works with or without an account.
A bot does one or the other at a time. Full socket and MITM helps you choose.
Connection, package and script
A bot's state has three parts, and each one changes on its own:
- The connection: whether the bot is disconnected, connecting, waiting for your game, or connected to a game server.
- The package: which package the bot will play, if any. Loading a package doesn't start it.
- The script: whether the package's script is running right now. It can only start once the bot is connected to a game server, and it can stop, or fail, while the connection stays up.
So a bot that shows Connected to game server, with a package loaded and its script stopped, is in a perfectly normal state: it's connected, and it will run the package when you press Play. States and controls lists every state and button.
The Bot Manager table
In the sidebar, click Bot Manager. Every bot gets a row:
| Column | What it shows |
|---|---|
| Name | The bot's name. Click it to open the bot's page. |
| Login ID | The Ankama account the bot signs in with, or no account. |
| Game version | The Dofus version the bot works with. |
| Network | The connection state, such as Disconnected, Waiting for your game client or Connected to game server. |
| Behavior | The script state: Running, Stopped, or Failed when it stopped with an error. |
The three dots at the end of a row open the bot's actions, described in States and controls. Click a column title to sort by it, and type in Filter... to narrow the list. With no bot yet, the table reads "No bots yet."
The table doesn't show which package a bot has loaded. Its page does, in the header.
Where to go next
- Add a bot, for every field of the dialog.
- Your first bot, if you haven't set one up yet.