Smooth

A bot on its own connects to Dofus and nothing more. What it does once it's in the game comes from a package: you install packages in your library, then give one to each bot. What a package holds A package is a small set of JavaScript files, its script, that Asterobot runs for a bot. You don't need to read or write that code to use a package. Besides the script, a package can declare package settings, the options you fill in on the bot's Settings tab (which resource to harvest, how long to wait), and actions, buttons on the same tab that run part of the script when you click them. Package settings and actions shows how to use both. A package can also depend on other packages and use their code. Those dependencies are packages like any other: they get their own row in your library and run together with the package that needs them. Your library The library is the set of packages installed in your Asterobot, on the computer where Asterobot runs. Library Manager shows it, one row per package version. Nothing about it is stored in your browser, so every Asteroboard connected to the same Asterobot sees the same library. Installing a package doesn't make it do anything. It runs when a bot plays it, and each bot that plays it runs a copy of its own. Trusting a package explains what that script is allowed to do with your bot. Versions side by side Each version of a package is installed on its own. my-harvester 1.0.0 and my-harvester 1.1.0 are two rows in Library Manager, and both stay until you remove one. That's on purpose. A bot is set to one exact version, so a new version arriving in your library never changes what your bots play. When you update a package from the marketplace, the new version lands next to the old one, and you move each bot to it when you're ready. Update packages walks through it. Where packages come from Source How it gets into your library Badge The marketplace, the Library category of asterobot.net Download package in Library Manager, or Download one wherever you choose a package for a bot. See Install from the marketplace. Community or Official A package you write New package in Library Manager, then the editor. See Create a package. Local A copy of one of your local packages Copy to a new version in the package's menu. See Manage your library. Local A .zip file Import a .zip in Library Manager. See Manage your library. Depends on the name you give it The command line The library install command. See Command line. Depends on the name you give it Local, Community and Official The Provenance column of Library Manager shows one of three badges. Asterobot picks it from the package's name. Badge The name looks like What it means Local my-harvester A package of your own, created, copied or imported under a plain name. Only local packages can be edited in Asteroboard. Community @some-author:auto-harvest Installed from a marketplace file that an asterobot.net member published. After the @ comes the author's name, after the : the file's title, both in lowercase with hyphens. Official @asterobot:auto-harvest Installed from a marketplace file that asterobot.net marks as official. A marketplace package keeps the name it got the first time you installed it. If its author renames the file on asterobot.net later, your package keeps its name, and updates still find it. Note A package imported from a .zip file gets the name you type, which can start with @. It then shows Community or Official without coming from the marketplace. Trusting a package explains how to check where a package really comes from. Script authors will find the naming rules in Names and versions and How your package is named. Compatible and Incompatible A package can state which versions of Asterobot it works with. When it does, the Compatibility column shows Compatible or Incompatible, depending on the Asterobot you run. When it states nothing, the column stays empty and no version is checked. An incompatible package stays in your library, and the package pickers still offer it, with (incompatible) after its name. It won't start, though: Play fails with Couldn't start the behavior, without saying why. On a bot set to that package, the Settings tab, under Package settings, gives the reason, which ends with package "<name>" requires asterobot <versions>, running <your version>. Update the package, or Asterobot, until the two match. Authors can read Compatibility. Dependencies The Dependencies column shows how many packages a package depends on. Hover the number to see their names. When you install a package from the marketplace, Asterobot also downloads the packages it depends on. When a dependency declares settings of its own, they get their own section on the bot's Settings tab. You can remove a package that another one depends on. Asteroboard warns you first, and the package that needed it then fails to start. Where to go next Install from the marketplace Run a package

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.toml and accounts.toml. Reset and start over

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. Where to go next MITM mode Disconnect, delete and restart Your account

Everything you chose when adding a bot can be changed later, except its name, on the Settings tab of its page. Two of them, Account and Game version, can only change while the bot is disconnected. Open the settings Open the bot's page and click Settings. Two sections sit at the top: Bot configuration, the bot's own settings, described on this page. Package settings, the settings and actions of the package the bot plays. See Package settings and actions. The two are saved separately, and switching between them keeps what you typed in each. The fields Field What it is When a change applies Name Shown so you can copy it. It can't be edited: to rename a bot, delete it and add it again. Account The stored Ankama account the bot signs in with. Same field as in Add a bot. When you save. The bot must be disconnected. Game version The Dofus version the bot works with, with the same badges as in Add a bot. When you save. The bot must be disconnected. Language See Language. When you save. Server selection and Force server How the bot picks a server when it signs in on its own. See Full socket mode. At the next Connect. Device identifier (HWID) See Device identifier. At the next Connect. Package The package the bot plays by default, with Download one to install one from the marketplace. At the next Play. A running script isn't touched. Unlike Add a bot, this page lets you save a game version that isn't ready yet. The bot can't connect until the version is ready. A bot's account can be replaced, but not removed: the list has no empty choice, and a bot without an account stays without one until you pick an account. To get a bot without an account, add a new one. The Package list can't be emptied either. To clear a bot's package, use Unload package in the package menu of its page, described in States and controls. Save Save settings saves the whole section at once: every change you made goes through together, or none does. Discard changes puts back the saved values. While you have unsaved changes, Unsaved changes shows next to the buttons, and a dot marks Bot configuration when you look at the other section. On success, Asteroboard shows Settings saved. On failure, it shows Couldn't save the settings with the reason. Save settings stays greyed out when: nothing changed; the chosen account shows Not signed in, or no longer exists in Account Manager; no game version is chosen; the account or the game version changed while the bot isn't Disconnected; Always this server is selected without a server. The bot's state changes constantly while you edit, as it connects or runs. Fields you edited keep your value; the others follow the bot. Fields locked while connected As long as the bot isn't Disconnected, including while it waits for your game client, Account and Game version are greyed out, with the notice "Disconnect this bot to change its account or its game version." Those two decide how the bot itself is built, so Asterobot rebuilds the bot when they change, and a live session belongs to the account that opened it. Click Disconnect in the header, make the change, then save. Warning Before choosing another account, check that no other bot uses it. When Asterobot refuses the new account or game version, for example this account is already associated with a bot, or when it can't confirm your asterobot.net account at that moment, the bot disappears from Bot Manager until Asterobot restarts. It comes back at the next start with its previous settings. Language The choices are Français, English, Deutsch, Español and Português. Today the bot's language changes one thing you can see: the language of server names and descriptions in the bot's server lists and on its Information tab. It doesn't change the language a script receives: every script started from Asteroboard gets fr, whatever this field says. See Identify and run. Two things set it back without you touching this field: Add a bot only saves its Language when a Library package is chosen. Otherwise the bot starts in French. Load a new package and Load a package and play it save French as the bot's language. Moving the bot to another version of its package, from the package name in the header, keeps the language as it is. Device identifier The device identifier, labelled Device identifier (HWID), is the value a bot sends to the game's login server for its device when it signs in on its own, the way Dofus sends one for the computer it runs on. It's 64 hexadecimal characters. A bot with an Ankama account gets a random one when it's added, unless you typed one. It's kept from then on: it doesn't change by itself between connections or when Asterobot restarts. A bot without an account has none at first. When it relays a game for the first time, it takes the identifier your Dofus sent, and keeps it even if a later client sends another. A relayed session always carries your game's own identifier, so this value is only a record. To change it, paste or type 64 hexadecimal characters, or click Generate for a random one, then save. Lowercase letters are accepted and saved as capitals. Anything else shows "Must be 64 hexadecimal characters." Emptying the field and saving keeps the current identifier. Where to go next Package settings and actions, for the other section of this tab. Run a package States and controls

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

In MITM mode, short for man-in-the-middle, you play Dofus as usual and a bot sits between your game and Ankama's servers, passing everything along in both directions. The bot sees the whole session and can run packages, and Asterobot never needs your Ankama login. Your first bot walks through a first setup. Caution A bot in MITM mode is still a bot. Using bots breaks Ankama's terms of use, and Ankama can sanction the accounts involved. Read Accounts and safety first. When to use it To follow or extend the game you're playing: read your chat and inventory, watch the messages, run a package alongside you. For accounts protected by Ankama Shield or two-factor authentication, which Full socket mode doesn't support. When you don't have a connection script. Your game already identified itself, so the bot is in the game as soon as the session reaches it. A script started on a relayed session is told it's resuming, which makes a connection script skip its identification step. See Identify and run. It isn't made for bots that play without you: every relayed session starts with someone launching Dofus and signing in. What you need Dofus 3 installed with the Ankama Launcher, on the computer where Asterobot runs. For a Dofus on another computer, see MITM across machines. The same Dofus version in Game Manager, downloaded and extracted. See Download a game version. A bot using that version, with or without an Ankama account. See Add a bot. Asterobot signed in to asterobot.net. server.tls off and server.basicAuth empty, which are their defaults. Warning MITM mode doesn't work while server.tls is on or server.basicAuth is set, even with Dofus and Asterobot on the same computer. Dofus fetches its connection settings from Asterobot, at the address in the ConfigUrl line described below. That address always starts with http://: with server.tls on, Asterobot only answers over HTTPS, so the request fails. With server.basicAuth set, Asterobot asks for a login and password that Dofus never sends. Either way, the bot starts waiting as usual, then stays Waiting for your game client while you play. Put both settings back to their defaults on Server > Config and restart Asterobot. Settings reference describes both settings, and MITM across machines covers setups where other devices need to reach Asterobot. The same version The Dofus you play states its version on the Version= line of Dofus_Data/StreamingAssets/version, in its folder. When a bot starts waiting, Asterobot compares that number with the version of its own copy and refuses when they differ. Only the version number counts, so a Linux or macOS client of the same version is fine. When your bots use different game versions, Asterobot may compare your game with any of them, not necessarily the bot that's waiting. Keep all your bots on the version you play while you use MITM mode. After an Ankama patch, follow When Dofus updates. Start waiting Open the bot's page and click Start waiting. It's also in the bot's menu in Bot Manager, and Wait for my game client does it right after adding a bot. The status turns to Waiting for your game client, and the bot's console shows Waiting for a game client. The bot can stay like this as long as you want. Start Dofus from the Ankama Launcher and sign in. If Dofus was already open, close it and start it again. When your session reaches the bot, the status turns to Connected to game server. The console shows Attached to Ankama account the first time, then A client is being sent to us and Relaying a game session. Your game plays exactly as usual. Nothing starts playing by itself: to run a package on the relayed session, press Play. See Run a package. When the bot can't start waiting Asteroboard shows Couldn't put the bot into waiting and the bot stays Disconnected. It doesn't say why, so go through the causes: Cause What to check The Dofus you play isn't the version in Game Manager Compare the Version= line of your version file with Game Manager, and download the version you play. Asterobot can't read the version file botmanager.mitmGamePath must be the Dofus folder itself, the one that contains Dofus_Data. The version file has no ConfigUrl line The file isn't a normal Dofus version file. Check the folder in botmanager.mitmGamePath. The ConfigUrl line still points at Asterobot from an earlier run, and Asterobot's copy of the game has no version file to read the original from Put the original line back by hand, as MITM problems describes, or click Download more files on the bot's game version with the default filter. Another program uses port 5555 or 5556 Close that program, or change botmanager.mitmSignInPort and botmanager.mitmSessionPort, then restart Asterobot. Both port settings have the same value Give them two different ports, then restart Asterobot. MITM problems goes through each case. The line Asterobot changes in your Dofus folder To send your game through Asterobot, Asterobot edits one line of one file: Dofus_Data/StreamingAssets/version, in your Dofus folder. That file's ConfigUrl line tells Dofus where to fetch its connection settings. When the first bot starts waiting, Asterobot remembers the original line and replaces it. With the default settings, it becomes: ConfigUrl=http://127.0.0.1:8080/botmanager/mitm/dofus3.json The address in it is botmanager.mitmAdvertiseHost, or botmanager.mitmBindHost when that one is empty, and the port is the one in server.listenAddress. The rest of the file isn't touched. When Dofus fetches that address, Asterobot answers with Ankama's real connection settings, changed in one place: the sign-in server is Asterobot's port 5555. Your game signs in through Asterobot, and Asterobot forwards everything to Ankama. Its log, in the terminal and on Server > Console, shows Pointed the played game at Asterobot when it edits the line. Asterobot puts the original line back: when no bot is waiting any more, because you disconnected or deleted the last one; when Asterobot stops normally, with Ctrl+C or Shutdown server; the next time Asterobot starts, if it was stopped abruptly and couldn't do it then. The log shows Restored a game install left pointing at Asterobot by a previous run. Asterobot reads the original line from its own copy of the game, which it finds through a bot that came back as it started, so this needs at least one bot restored at start and botmanager.mitmGamePath set. Otherwise, put the line back by hand. The first two print Pointed the played game back at Ankama. If a bot starts waiting and finds the line still pointing at Asterobot from an earlier run, Asterobot reads the original address from its own copy of the game and fixes it first, printing Recovering a ConfigUrl left pointing at Asterobot by a previous run. While the line points at Asterobot, a game signed in with an account no bot is waiting for passes through untouched and plays normally. When Asterobot isn't running at all, though, Dofus can't sign in. Start Asterobot again: it puts the line back as it starts, as long as one of your bots comes back with it. If it doesn't, see Dofus can't sign in. Where Asterobot looks for your Dofus folder The folder is the botmanager.mitmGamePath setting, on Server > Config. Its default is the Ankama Launcher's usual folder: System Default Windows %AppData%\Ankama\Dofus-dofus3 Linux ~/.config/Ankama/Dofus-dofus3, or the same folder under XDG_CONFIG_HOME when that's set macOS None The default is only filled in when that folder exists as Asterobot starts. If you installed Dofus after starting Asterobot, restart Asterobot, or set the folder yourself. On macOS, and whenever your Dofus is somewhere else, set botmanager.mitmGamePath to the folder that contains Dofus_Data/StreamingAssets/version. The setting applies without restarting, from the moment no bot is waiting: disconnect every waiting bot, change it, then click Start waiting again. Warning When botmanager.mitmGamePath is empty, a bot still starts waiting, but nothing is edited and your game never reaches it. If the log doesn't show Pointed the played game at Asterobot after a bot starts waiting, check this setting first. Which bot gets which game session Every game that signs in through Asterobot is matched with a waiting bot by the Ankama account it signed in with: A waiting bot already attached to that account gets the session. Otherwise, the first waiting bot that isn't attached to any account, in alphabetical order of names, takes it and attaches itself to that account. Otherwise, no bot takes it. The game goes straight to Ankama and plays normally, and Asterobot's log shows A game client signed in that no bot is waiting for. How long an attachment lasts depends on the bot: A bot without an Ankama account stays attached for good. The attachment is saved, so after a restart the bot still only takes that account's sessions. Asteroboard doesn't show the attached account until a session arrives, on the bot's Information tab, and it has no way to detach a bot. To relay another account, add another bot. A bot with an Ankama account attaches the same way, to whichever account signs in first, even if that isn't the account stored for it. That attachment isn't saved: it lasts until Asterobot restarts, or until you change the bot's account or game version. If a new session arrives for an account whose bot is already relaying one, it replaces the session the bot was carrying. Many bots shows how to set up several clients. When you quit Dofus The relayed session ends: the console shows Game connection lost and the status goes back to Waiting for your game client. A script that was running stops, with The behavior stopped with an error on the bot's page. The bot keeps waiting for your next session, and the line in your Dofus folder stays pointed at Asterobot. Next time you play, start Dofus and sign in: the bot takes the session again. Press Play if you want its package running. To stop for good, click Disconnect. The bot stops waiting and, if it was the last one, Asterobot puts the original line back. If you're in game at that moment, your game is disconnected, because the bot was carrying its session. The same happens when you delete the bot or stop Asterobot. A bot waiting for your game client or relaying it can't also sign in on its own: disconnect it first to use Full socket mode. Ports and settings All of these are on Server > Config. Setting Default What it does Restart needed botmanager.mitmSignInPort 5555 Port your Dofus signs in on. Yes botmanager.mitmSessionPort 5556 Port your Dofus opens its game session on, after signing in. One port serves every bot: Asterobot tells sessions apart by what they send. Yes botmanager.mitmBindHost 127.0.0.1 Network interface the two ports listen on. 127.0.0.1 only accepts connections from this computer. Yes botmanager.mitmAdvertiseHost Empty Address your Dofus is told to connect to. Empty uses botmanager.mitmBindHost, or 127.0.0.1 when that's 0.0.0.0. Yes botmanager.mitmGamePath See above The Dofus folder whose version file is read and edited. Nothing else is read from it: game data always comes from Asterobot's own copy. No server.tls and server.basicAuth aren't MITM settings, but both have to stay at their defaults for MITM mode to work, as the warning under What you need explains. The two ports only open while at least one bot is waiting, and close once none is. When they open, Asterobot's log shows Ready for game clients with the addresses in use, including the ConfigUrl value a Dofus on another computer needs. Relaying a Dofus that runs on another computer means changing botmanager.mitmBindHost, and editing the ConfigUrl line on that computer yourself, since Asterobot can only edit files on its own. MITM across machines explains the whole setup, and Security what opening the ports means. Where to go next Run a package on your relayed session. Network traffic, to watch your game's messages. Many bots, to relay several Dofus clients.

In Full socket mode, a bot does on its own what a Dofus client would do. Asterobot signs the bot's Ankama account in, picks a game server and opens the connection to it, with no Dofus window anywhere. From there, a package takes over. Caution Using bots breaks Ankama's terms of use, and Ankama can sanction the accounts involved. Read Accounts and safety first. What you need Asterobot signed in to asterobot.net. See Sign in with asterobot.net. An Ankama account stored and signed in, not used by any other bot, and not protected by Ankama Shield or two-factor authentication. See Add an account and Shield and two-factor authentication. A game version ready for a bot: game files downloaded and game data extracted. See Download a game version and Extract game data. A bot with that account and that game version. See Add a bot. A connection script, to get the bot into the game once it's connected. The next section explains why. Why a package has to identify the bot Asterobot's part ends once the connection to the game server is open. It doesn't send the identification the game server expects next, and it doesn't pick a character. Until something does, the bot is connected to a game server but not in the game. That's the job of a connection script: a package you run on the bot with Play, which identifies it and enters the game. Note Coming soon. Ready-made connection scripts, a basic one and a full one, will be published for you to run and reuse. Until then, you can write your own by following Identify and run in the developer docs, or use MITM mode, which needs no connection script. Connect Open the bot's page: click its name in Bot Manager. Click Connect in the header. For a bot without an account, it's greyed out, with the tooltip "This bot has no Ankama account to sign in with." Watch the status next to it. It shows Connecting…, and ends on Connected to game server. Click Play to start the connection script. See Run a package. Connect is also in the bot's menu in Bot Manager, and Sign in now does the same right after adding a bot. When the connection fails, Asteroboard shows Couldn't connect the bot with the reason, and a Couldn't connect this bot alert with the same reason stays under the bot's header. One failure gets its own notification: when the bot's game version isn't ready, Asteroboard shows Bot's game version isn't ready yet, asking you to check the version in Game Manager. The stages of a connection Before anything goes out to the network, Asterobot checks that it can confirm your asterobot.net account and that the bot's game version is ready. Then the connection goes through three stages. The bot's Console tab narrates each one. Stage What Asterobot does Status Console lines Ankama sign-in Uses the account's sign-in to get a one-time ticket for the game. When that sign-in has stopped working, Asterobot renews it, or signs in again through the browser for an account with a stored password. Connecting… Connecting to Zaap..., Connected to Zaap Login server Identifies with the ticket and the bot's device identifier, receives the account's server list and selects a server. Connecting…, or Awaiting your answer while you pick a server Connecting to login server..., Connected to login server, Identified with login server, Server selected, Login completed, Disconnected from login server Game server Opens the connection to the selected game server. Connected to login server for a moment, then Connecting… Connecting to game server..., Connected to game server When it's done, the status reads Connected to game server. The bot's Information tab then shows the Ankama account and the server the bot is on, as described in Information. Each exchange with the login server and each game server connection has a 30-second limit. When the login server doesn't answer in time, the connection fails with connect to login server: timed out waiting for a response. How the server is chosen Each bot has a Server selection setting, chosen in Add a bot and changed on the bot's Settings. Server selection What the bot does Most recently played The default. Picks the server where the account's most recently played character is, among the servers that are online and open to the account. If there's no such character, it takes the server this bot last connected to, then the first server that's online and open. Always this server Connects to the server you picked in Force server, every time. When that server is offline or not open to the account, the bot doesn't go anywhere else: it stops and asks you. Ask me each time Always stops and asks you to pick a server. Most recently played asks you too when no server at all is online and open to the account. After every successful login stage, Asterobot remembers the selected server as the one this bot last connected to, whichever mode picked it. The Pick a server card When a bot asks, its status turns to Awaiting your answer, and a Pick a server card appears under the header, on every tab of the bot's page. Its text, "This bot is set to always ask - choose which server to connect to below.", is the same when the bot asks because your forced server is unavailable. Wherever you are in Asteroboard, a notification also says the bot needs your input, with a Go to bot button. Each server card shows the server's picture, name and number, then badges: Online or Maintenance, the server's type, Mono-account for mono-account servers, and how many characters the account has there. The info icon next to the name shows the server's description. Only servers that are online and open to the account can be clicked; the others are greyed out. Click a server: the bot goes on right away, through the login server and to the game server, with no other click. If the answer doesn't go through, Asteroboard shows Couldn't send your answer. Asterobot sets no time limit on this question. To give up, click Disconnect. Connected to game server, but not in the game Connected to game server means the connection to the game server is open, nothing more. Asterobot can't tell whether the bot identified: the status reads the same whether the connection script did its job or not. If no script is running, nothing identifies the bot. Press Play with a connection script loaded. The script's own lines in the bot's Console tab tell you how the identification went. If the game server closes the connection, the console shows Game connection lost and the status goes back to Connected to login server, not Disconnected. A running script stops, and the bot's page shows The behavior stopped with an error with a message mentioning Game session closed. Nothing reconnects by itself: click Disconnect, then Connect, then Play. Bot doesn't connect covers a bot that connects but never gets into the game. Common connection errors The reason contains What it means this bot's game version is not ready to connect yet The bot's game files or game data aren't ready. Finish them in Game Manager. ankama account authorization required The account's sign-in no longer works, and it has no stored password to sign in again. Sign it in from Account Manager. account not found The bot's account was removed from Account Manager. identification was refused: account already connected elsewhere The account is already in the game, in Dofus or with another bot. this installation is not entitled to start bots Asterobot couldn't confirm your asterobot.net account. Check that it's signed in, from the account button in the sidebar, and that it can reach asterobot.net. Bot doesn't connect lists every error with its fix. Disconnect Click Disconnect in the header, or in the bot's menu in Bot Manager. It works at every stage: while connecting, while the bot waits for you to pick a server, and once it's connected. The running script stops, the connections close and the status turns to Disconnected. The bot keeps all its settings. See Disconnect, delete and restart. A bot connected in Full socket mode can't also wait for your game client: one Ankama account has one game session at a time. Disconnect it first to switch to MITM mode. Where to go next Run a package, to start the connection script. States and controls, for every state and button. Many bots, to run several accounts.

Open Bot Manager and click Add a bot. The dialog has five tabs: Identity, Game, Connection, Behavior / Script and Live data. A ready game version is the only thing you can't skip; everything else can wait, and nearly all of it can be changed later on the bot's Settings. Your first bot walks through a MITM bot step by step. Identity Name Lowercase letters, digits and hyphens, from 1 to 64 characters, starting and ending with a letter or a digit. Anything else shows "Lowercase letters, digits, and hyphens only." under the field. Leave it empty and Asterobot picks a name made of three words joined by hyphens. The dice button next to the field, Generate a name, fills one in so you can see it or edit it first. The name only helps you recognize the bot: it isn't sent to the game. It can't be changed later, and it decides the order of the bots in Bot Manager, which also matters in MITM mode. Account The stored Ankama account this bot signs in with, for Full socket mode. It's optional: without one, the bot can only relay a game you play in MITM mode. The list shows every account in Account Manager, signed in or not. Under the list, the chosen account shows Signed in or Not signed in. For an account that isn't signed in, a Connect button opens the sign-in dialog. The button next to the list, Add or connect an account, adds a new account, opens the sign-in dialog for it and selects it. The hint under the field says what the bot will be able to do: with an account, sign in on its own and relay a session you sign in yourself; without one, relay only. Choose carefully: the list has no empty choice, so once you picked an account you can't go back to none in this dialog. Reload Asteroboard to start again with an empty form. A bot's account can't be removed later either, only replaced. An account can only belong to one bot. Picking one that another bot already uses makes Add bot fail with Couldn't add the bot. Game Game version The list offers the Dofus versions installed in Game Manager. When the version this release of Asterobot was tested with is installed, it's selected for you; after choosing another one, Use tested version followed by its number puts it back. Add a game opens the download dialog without leaving this one. See Download a game version. Badges under the field describe the chosen version: Badge Meaning Compatible or Different version Whether it's the version Asterobot was tested with. A different version isn't refused. Checking required files..., then Ready or Missing required files Whether the game files a bot needs are there. Download needed files fetches the missing ones. Not extracted, Extracting, Extracted or Extraction failed Whether its game data is extracted. Click Not extracted or Extraction failed to start the extraction. A version is only usable once its game files are in and its game data is extracted. Until then, a hint under the badges says so, the Connection tab stays greyed out and Add bot stays disabled. Extract game data explains what "ready for bot" means. Language Français, English, Deutsch, Español or Português. It starts on Français. This language is only saved with the bot when you pick a Library package on the Behavior / Script tab. With None or Inline script, the bot is saved in French whatever the field shows, and you change it afterwards on the bot's Settings. Bot settings explains what the language changes. Connection This tab stays greyed out until the chosen game version is ready. Once the bot is added Choice What happens when you click Add bot Do nothing The bot is added and stays Disconnected. Sign in now The bot signs in with its account and connects to a game server, in Full socket mode. It needs an account that shows Signed in. Without an account, the choice is greyed out and says so. Wait for my game client The bot starts waiting for a Dofus client you play, in MITM mode, short for man-in-the-middle. Nothing more happens until you start Dofus and sign in. Sign in now is selected when the dialog opens, even for a bot without an account. In that case, choose another option, or Add bot stays greyed out. Server selection How the bot picks a game server when it signs in on its own: Most recently played, Always this server or Ask me each time. Each one is explained in Full socket mode. A bot in MITM mode ignores this: your game picks the server. With Always this server, a Force server field shows the servers of the chosen game version, with their names in the language you picked. Click one to select it, and Clear to unselect it. Add bot stays greyed out until a server is selected. Device identifier (HWID) Leave it empty for a new bot: when the bot has an account, Asterobot generates one as it adds the bot. Generate fills in a random one here instead. A value you type must be 64 hexadecimal characters, or the field shows "Must be 64 hexadecimal characters." Bot settings explains what it is. Behavior / Script This tab chooses what the bot will play. Nothing you choose here runs unless Play behavior directly is checked. Choice What it does None The default. The bot is added with nothing to play. You can pick a package later on its page. Inline script A JavaScript module you paste in Behavior script, for quick tests. It's never saved, and it's only used when Sign in now and Play behavior directly are both selected. Otherwise it's thrown away when you add the bot. Library package An installed package, picked in Package, which becomes the bot's default package. Download one installs a package from the marketplace without leaving the dialog. A Library package also brings up the settings the package declares, so you can set them before the bot exists. Asterobot saves them right after adding the bot. Package settings and actions explains those settings, and Install from the marketplace the download. Play behavior directly This checkbox, "Start the behavior above right after connecting.", only appears once you chose an inline script or a package, and not with Wait for my game client. It can only be checked with Sign in now, and it checks itself when you choose a package while Sign in now is selected. Left unchecked, the bot is added with its package chosen but not started. With Wait for my game client and a package, the dialog says the behavior "begins the moment you launch the game and the session reaches it". It doesn't: nothing starts on its own. Once your game is relayed, press Play on the bot's page. See Run a package. Live data This tab chooses what the bot sends to Asteroboard while it's connected, so its page follows what happens in the game. It has four checkboxes, all checked when the dialog opens. Checkbox What it keeps up to date Character Level, experience, health, energy and characteristics, on the Character tab and in the row above the bot's tabs Chat Messages from the game's chat channels, in the bot's Console Inventory Items, kamas and pods, on the Inventory tab and in the row above the bot's tabs Map Position, players and monsters around, resources, on the Map tab Each checked box costs Asterobot and your browser some work for every message it brings, so uncheck the ones you won't look at. With nothing checked, the bot's pages stay empty. Asterobot saves your choice with the bot. To change it later, click the satellite dish button at the right end of the row above the bot's tabs. Its tooltip is Live data settings, and it has one switch for each checkbox. Why Add bot stays greyed out Add bot stays disabled until all of these are true: The name is empty, or follows the naming rules above. A game version is chosen, and it's ready: game files in and game data extracted. A chosen account still exists in Account Manager. With Sign in now, an account is chosen and shows Signed in. With Always this server, a server is selected. With Inline script, the script isn't empty; with Library package, a package is picked. After you click Add bot Asteroboard goes through these steps in order, and stops at the first that fails. Asterobot adds the bot, with the live data you checked. If it refuses, Asteroboard shows Couldn't add the bot and the dialog stays open, without saying why. The usual causes are a name already taken, an account another bot already uses, Asterobot not being signed in to asterobot.net, and the bot limit of your asterobot.net account. See Many bots. The package's settings are saved, if you set some. When that fails, Asteroboard shows Couldn't apply the settings with the package's name. The bot is added all the same, and you can set them again on its Settings. With Do nothing, the dialog closes. With Wait for my game client, the bot starts waiting and the dialog closes. If it can't, Asteroboard shows Bot added, but it couldn't be connected: the bot exists, disconnected, and MITM mode lists the reasons. With Sign in now, Asteroboard waits for the connection to settle: Connected: the dialog closes, unless there's a script to start. Waiting for you to pick a server: the dialog closes and Asteroboard shows Bot added - needs a login question answered, with a Go to bot button. Pick the server on the bot's page, as Full socket mode shows. Failed: the dialog closes and Asteroboard shows Bot added, but it couldn't be connected, with the reason under it. The same reason appears on the bot's page. With Play behavior directly, the script starts once the bot is connected, and the dialog closes. If it can't start, Asteroboard shows Bot added and connected, but the behavior couldn't be started. Warning In a few of these failures the dialog stays open with your choices still filled in: when the bot can't start waiting, when starting the script fails, and when a connection takes longer than 90 seconds (an automatic Ankama sign-in can), in which case the bot often keeps connecting in the background. The bot was added anyway. Close the dialog and look at the bot's page. Clicking Add bot again would try to add a second bot, and with an empty name it succeeds. Where to go next Full socket mode or MITM mode, to bring the bot online. Run a package, to give it something to do. Bot settings, to change what you chose here.

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.

Ankama Shield and two-factor authentication add a step when an account signs in, such as a code to type or a device to approve. Asterobot doesn't support these accounts in Full socket mode. They work in MITM mode, where you sign in yourself, in Dofus. Not supported in Full socket mode In Full socket mode, Asterobot has to get through Ankama's sign-in and then the game's login server with nobody there to help. It has nothing for the extra step these accounts need: Asteroboard has no field for a verification code, and automatic sign-in only types the Login ID and the password. When Asterobot identifies the bot on the game's login server, the Shield certificate it sends is always empty, and so is the certificate it gives Ankama when it asks for a game connection. So even if such an account ends up showing Signed in, Full socket mode doesn't support it: don't use it for Full socket bots. What you'd see Asterobot has no message of its own for these accounts. What you meet depends on the step where Ankama stops: Automatic sign-in fails. Asterobot's log shows ankama did not accept the sign-in (wrong password, a verification step, or a challenge raised after submitting), because the browser can't pass the verification step. See Automatic sign-in. Manual sign-in happens in your own browser, where you can answer Ankama's verification yourself, so the account can reach Signed in. Connecting a bot is where it stops. When Ankama refuses, the reason it gives is shown in the bot's Couldn't connect this bot alert. A refusal from the game's login server reads identification was refused: followed by Ankama's reason. Bot doesn't connect lists the connection errors. Use MITM mode instead In MITM mode, short for man-in-the-middle, you start Dofus from the Ankama Launcher and sign in as usual, Shield and codes included. Asterobot sits between your game and Ankama's servers, and the bot relays the session your game opened. Asterobot never signs the account in, and you don't store it in Account Manager at all. Add a bot without an account, and choose Wait for my game client on its Connection tab. See Add a bot. Start Dofus from the Ankama Launcher and sign in with the protected account. The bot then shows Connected to game server, and it can run packages like any other bot. Your first bot walks through this setup step by step, and MITM mode explains it in full. The trade-off is that someone has to start Dofus and sign in for every session. Full socket and MITM compares the two modes. Where to go next MITM mode Accounts and safety

Every account in Account Manager shows badges for its state and has a menu of actions. A Signed in badge only means Asterobot holds the account's sign-in, not that Ankama still accepts it. Status badges Badge Meaning Signed in Asterobot holds a sign-in for this account, received from Ankama. Not signed in Asterobot holds no sign-in for the account. Sign it in before you use it for a bot. Signs in on its own A password is stored. Asterobot signs the account in again by itself when it needs to. What "Signed in" really means Signed in only says that Asterobot has the account's tokens. Asterobot doesn't watch for them to expire, and Ankama can end them at any time, so an account can show Signed in long after its sign-in stopped working. Two things find out for sure. Verify asks Ankama right away. And every time a bot connects with the account, Asterobot uses the sign-in for real: when it has stopped working, Asterobot renews it quietly if Ankama accepts, signs in again through the browser for an account with a stored password, and otherwise the bot's connection fails with a message that contains ankama account authorization required. The Sign in now option of the Add a bot dialog only accepts an account that shows Signed in. Actions Open an account's menu with the three dots at the end of its row. Action Available What it does Sign in automatically Only when a password is stored Signs the account in through Asterobot's browser, in one click. See Automatic sign-in. Connect For an account that isn't signed in Opens the sign-in dialog. See Manual sign-in. Reconnect For an account that's signed in Opens the same dialog. The account keeps its current sign-in until the new one works. Verify For a signed-in account Checks the sign-in with Ankama right now. Force refresh token For a signed-in account Renews the sign-in with Ankama straight away, even if it still works. Disconnect For a signed-in account Revokes the sign-in and forgets its tokens. Remove Always Deletes the account from Asterobot. Verify Asks Ankama whether the account's sign-in works right now. When it does, Asteroboard shows Verified as followed by the account's Ankama nickname. When the sign-in has stopped working, Verify repairs it first, the same way a connecting bot would: a quiet renewal, then a browser sign-in for an account with a stored password. If nothing works, Asteroboard shows Verification failed - try reconnecting. Use Reconnect then. Verify connects nothing to the game. Force refresh token Trades the account's refresh token with Ankama for a new one, right away, whether the sign-in still works or not. Asterobot already does this on its own when a sign-in stops working, so you'll rarely need it. It's there for testing, or to replace a sign-in you'd rather not keep. On success, Asteroboard shows Token refreshed. When Ankama refuses the refresh token, or there isn't one, it shows Couldn't refresh the token - try reconnecting, and only a new sign-in helps. Unlike Verify, this action never falls back to the browser. Disconnect Asks Ankama to revoke the account's sign-in, then forgets the tokens in Asterobot. The tokens are forgotten even when Ankama refuses or doesn't answer the revocation: Asteroboard shows Account disconnected and the badge turns to Not signed in either way. Two things stay as they were: Bots aren't touched. Asterobot doesn't disconnect a bot that is connected with this account. The stored password is kept. An account with Signs in on its own signs itself in again the next time a bot connects with it. To prevent that, remove the account. If Asteroboard shows Couldn't disconnect the account, nothing changed and the account is still signed in. Asterobot couldn't reach Ankama to prepare the request, or couldn't save its account file. Remove Click Remove. The Remove this account? dialog opens. Click Yes, remove. Asterobot deletes the account from accounts.toml, with its password and tokens. It doesn't revoke anything with Ankama first: click Disconnect before Remove if you want that. The account's browser profile and its last failure screenshot stay in Asterobot's folders. If removing fails, Asteroboard shows Couldn't remove the account. Removing an account doesn't delete the bots that use it, but it changes what they can do: A bot already connected with the account stays connected, and a bot waiting for your game client keeps waiting. Neither needs the stored account for that. The next time you click Connect on such a bot, the connection fails with account not found: LoginID followed by the Login ID. The bot's Settings can't be saved until you choose another signed-in account for it. When Asterobot next starts, the bot isn't brought back and disappears from Bot Manager. Its configuration stays saved, and the bot returns at a later start once the account exists again. See Disconnect, delete and restart. Adding the account again with the same Login ID, and signing it in, undoes all of this. Where to go next Add a bot with a signed-in account. Full socket mode, to see how a bot uses the account. Sign-in problems, when an account won't stay signed in.

Manual sign-in works for any stored account and needs nothing installed next to Asterobot. You sign in on Ankama's page in your own browser, then copy one link back into Asteroboard. Use it for an account without a stored password, when automatic sign-in fails, or when Asterobot runs on a machine where no browser can be started. Open the sign-in dialog In Account Manager, open the account's menu, the three dots at the end of its row, and click Connect. For an account that's already signed in, the same item reads Reconnect, and signing in again only replaces its sign-in once the new one works. The dialog also opens from the Add a bot dialog: right after you add an account with the button next to Account, and from the Connect button that appears under that field when the selected account isn't signed in. When the account has a stored password, the dialog starts with Sign in automatically. The manual way is underneath, after "or sign in yourself". Sign in Click Open Ankama sign-in. Ankama's sign-in page opens in a new tab of your browser, and the dialog switches to a field for the code. In that tab, sign in with the account, the same way you would in the Ankama Launcher. Answer anything Ankama asks along the way. Ankama ends on a Congratulations page with a Continue button. Don't click it. Right-click it and copy the link address instead. It starts with zaap://login?code=. Back in Asteroboard, paste it in Authorization code. The whole link works, and so does the code alone, the part after code=. Click Submit. It stays greyed out while the field is empty. Asterobot trades the code for the account's sign-in and checks it with Ankama straight away. When everything works, Asteroboard shows the Login ID followed by is connected, the dialog closes and the account shows Signed in. If you closed Ankama's tab too early, Reopen the sign-in page opens it again without starting over. Asterobot doesn't open a port or wait for Ankama to call it back: the link you paste is the only way the code reaches it. That's why this works just as well when Asteroboard runs on a phone or another computer than Asterobot. When Submit fails Asteroboard shows Couldn't complete the sign-in - the code may have expired, try again. A code works once, for the sign-in it was created for. Common causes: The link was copied incompletely, or it's the address of the Congratulations page itself rather than the Continue button's link. The code was already used, or it comes from an older tab: each click on Open Ankama sign-in starts a new sign-in, and only its own code matches. Asterobot restarted after you clicked Open Ankama sign-in. A sign-in in progress doesn't survive a restart. In every case, close the dialog, open it again and start from step 1. If Open Ankama sign-in itself fails, Asteroboard shows Couldn't start the sign-in. The first time Asterobot prepares an Ankama sign-in after starting, it fetches the current Ankama Launcher version from Ankama, and that step failed. Check the internet connection of the computer Asterobot runs on, then try again. Store or change the password The same dialog manages the password used for automatic sign-in. At the bottom of the dialog, click Store an Ankama password for automatic sign-in. For an account that already has one, it reads Change the stored Ankama password. Type the password in Ankama password. Click Save password. Asteroboard shows Password saved, and the account gets the Signs in on its own badge. Saving a password doesn't sign the account in. Click Sign in automatically, which now appears at the top of the dialog, or sign in manually as above. If saving fails, Asteroboard shows Couldn't save the password. Asteroboard never shows a stored password again. The text under the field says you can clear it to turn automatic sign-in off, but Save password stays greyed out while the field is empty, so that isn't possible from here. To stop an account from signing in on its own, remove it in Account Manager and add it again without a password. Account status and actions explains what removing does to the bots that use it. The password is stored in plain text on the computer where Asterobot runs. Add an account explains where. Enter tokens manually (debug) The last part of the dialog, Enter tokens manually instead (debug), is for tokens you got some other way. It skips the sign-in entirely. Field What to enter Access token The account's access token. Refresh token Its refresh token. Expires When the access token expires, as an ISO 8601 date and time, such as 2026-12-31T23:59:59Z. Save tokens stays greyed out until all three fields are filled. Asterobot stores the tokens as they are, without asking Ankama whether they work, so the account shows Signed in either way. Click Verify in the account's menu afterwards to find out. If Asterobot refuses the values, for example a date it can't read, Asteroboard shows Couldn't complete the sign-in - the code may have expired, try again. Tokens give access to the Ankama account the same way a password does. Only use tokens you got yourself. Where to go next Account status and actions, to verify the account and learn every action. Add a bot, now that the account is signed in. Sign-in problems, if Ankama keeps refusing.

When an account has a stored password, Asterobot can sign it in for you. It starts a real browser on the computer where it runs, fills in Ankama's sign-in page and reads the result, without showing any window by default. When Ankama doesn't let it through, Asterobot's log says why. What it needs A password stored for the account. See Add an account. Sign in automatically only appears for accounts that have one. Google Chrome, Chromium or Microsoft Edge on the computer where Asterobot runs. Not on the device you open Asteroboard on, if that's a different one. Asterobot looks for Chrome or Chromium first, and tries Edge only when neither can be started: System Where Asterobot looks Windows chrome on the command path; Chrome in C:\Program Files\Google\Chrome\Application or C:\Program Files (x86)\Google\Chrome\Application; Chrome or Chromium in your user's AppData\Local; then Edge on the command path or in C:\Program Files (x86)\Microsoft\Edge\Application or C:\Program Files\Microsoft\Edge\Application macOS Chromium or Google Chrome in /Applications, then Microsoft Edge in /Applications Linux chromium, chromium-browser, google-chrome, google-chrome-stable, chrome or /snap/bin/chromium, among a few other names, on the command path; then microsoft-edge, microsoft-edge-stable or /opt/microsoft/msedge/msedge For a browser installed anywhere else, or another Chromium-based browser such as Brave, Vivaldi or Opera, enter its full path in the zaapmanager.browserPath setting, described below. Firefox and Safari can't be used. Sign an account in The quickest way is from Account Manager: Open the account's menu, the three dots at the end of its row. Click Sign in automatically. Wait. A sign-in can take up to two minutes. When it works, Asteroboard shows the Login ID followed by signed in on its own, and the badge turns to Signed in. You can also do it from the sign-in dialog: click Connect or Reconnect in the same menu, then Sign in automatically at the top of the dialog. When it works, Asteroboard shows the Login ID followed by is connected and closes the dialog. When it fails, the dialog stays open with Automatic sign-in failed - sign in yourself below and a picture of the page, as explained further down. The reason itself is only in Asterobot's log. You don't always have to click anything. When a bot connects with this account and the account's sign-in has stopped working, Asterobot signs it in the same way as part of the connection. Full socket mode describes that connection, and Verify in Account status and actions can trigger it too. What happens during a sign-in If the account's current sign-in still works, Asterobot keeps it and stops there. No browser is started. Otherwise, it asks Ankama to renew the sign-in quietly, still without a browser. Only when that's refused does it start the browser, with the account's own profile, and open Ankama's sign-in page. Its log, in the terminal and on Server > Console, shows Signing in to Ankama through a browser. If the profile still holds a valid Ankama session, Ankama skips the form and goes straight to its confirmation page. Otherwise, the browser types the Login ID and the password into Ankama's form and submits it. On Ankama's confirmation page, Asterobot reads the link behind the Continue button. That link carries a one-time code, which Asterobot trades for the account's sign-in. Asterobot checks the new sign-in with Ankama straight away, then closes the browser. Three time limits apply: 30 seconds for Ankama's sign-in form to appear, 60 seconds after submitting it for the confirmation page, and two minutes for the whole attempt. No window by default The browser runs without any window, because zaapmanager.browserHeadless is on by default. That's what lets automatic sign-in work on a computer nobody is sitting at, such as a server. You can turn the window on when you need to see what Ankama is asking, as explained below. One browser profile per account Each account gets its own browser profile, kept between sign-ins in the zaapmanager/browser-profiles folder of Asterobot's data folder. Accounts never share one. Because the profile keeps the account's Ankama session, a later sign-in often goes straight to the confirmation page without meeting the form again. It also means the profile is as sensitive as the password itself. When Ankama asks for a person Sometimes Ankama puts a challenge or a captcha in front of its sign-in form. Asterobot doesn't try to get past it: it gives up and lets a person take over. You have two ways out. Sign in yourself, in your own browser. The sign-in dialog offers it right under the automatic button, below "or sign in yourself". See Manual sign-in. This always works, wherever Asterobot runs. Answer the challenge in the sign-in browser's window. This only works when Asterobot runs on a computer with a screen you're sitting at: On Server > Config, turn off zaapmanager.browserHeadless. It applies from the next sign-in, without restarting Asterobot. Start the automatic sign-in again. A browser window opens on the computer where Asterobot runs. Answer what Ankama asks in that window, quickly: the form has to appear within 30 seconds, and the confirmation page within 60 seconds after the form is sent. When the account shows Signed in, turn zaapmanager.browserHeadless back on. When it fails A failed attempt shows Automatic sign-in failed - sign in yourself below in the dialog, or Automatic sign-in failed as a notification when you started it from the menu. The message under it starts with ankama account authorization required, followed by the address of Ankama's sign-in page. Ignore the end of that message, which mentions saving a code to the configuration: signing in happens in the dialog, as Manual sign-in shows. That message is the same whatever went wrong. The real reason is in Asterobot's log. Find the reason In the terminal where Asterobot runs, or on Server > Console, look for the warning Automatic Ankama sign-in failed, a person has to sign in. Its error says what happened, and most of the time it ends with the title and address of the page the browser was on: The error contains What happened What to do failed to start a browser (is Chrome, Chromium or Edge installed?) Asterobot found no browser it could start. Install Chrome, Chromium or Edge on the computer where Asterobot runs, or set zaapmanager.browserPath. ankama's sign-in page is asking for a human (bot challenge or captcha) Ankama's sign-in form didn't show up within 30 seconds, or the page wasn't the form Asterobot expects. That's how a challenge looks from Asterobot's side. See When Ankama asks for a person. the request was refused by Ankama's edge network before Ankama saw it The browser got a block page from the network in front of Ankama. The account itself wasn't checked. Try again later, or sign in manually. ankama did not accept the sign-in (wrong password, a verification step, or a challenge raised after submitting) The form was sent, but Ankama's confirmation page didn't come within 60 seconds. Check the password and store it again if needed. If Ankama asks this account for a verification step, it can't sign in automatically: see Shield and two-factor authentication. failed to open ankama's sign-in page, failed to fill ankama's sign-in form or failed to submit ankama's sign-in form The browser couldn't load Ankama's page, or couldn't type into or submit its form. Check the internet connection of the computer where Asterobot runs, then sign in manually. browser signed in but the Continue link carried no code The sign-in went through, but the link behind Continue had no code in it. Sign in manually. Sign-in problems goes through these one by one. The screenshot When the browser got as far as showing a page, Asterobot takes a picture of it at the moment it gives up. Right after a failure started from the dialog's own Sign in automatically button, the dialog shows that picture under the alert, with the caption "What the browser was looking at when it gave up - click to open full size". Click it to see it full size. It's often the fastest way to tell a captcha from a wrong password. Asterobot keeps one picture per account, in the zaapmanager folder of its cache folder, and replaces it at the next failure. The terminal prints Captured what the browser saw when the Ankama sign-in failed with the file's path. When the browser couldn't start at all, there's no picture. Settings for automatic sign-in These three settings are on Server > Config. None of them needs a restart: each sign-in reads them again. Setting Default What it changes zaapmanager.browserHeadless On Runs the sign-in browser without a window. Turn it off to watch the sign-in and answer a challenge by hand. zaapmanager.browserPath Empty Full path of the browser to use. Empty means Asterobot looks for Chrome, Chromium, then Edge. When you set it, Asterobot uses that browser only and doesn't look for another one if it fails to start. zaapmanager.browserUserAgent Empty How the sign-in browser identifies itself to the pages it opens. Empty presents it as Chrome on Windows 11, with the major version number of the browser actually installed. Whatever you enter replaces that identity. Settings reference lists every setting, and The Config page shows how to change one. Where to go next Manual sign-in, when automatic sign-in isn't an option. Account status and actions, to check that a signed-in account still works. Sign-in problems, for every error in detail.

A bot in Full socket mode signs in to Ankama on its own, so it needs an Ankama account stored in Asterobot. You add it in Account Manager, with or without its password. If your bots only use MITM mode, short for man-in-the-middle, where a bot relays the game you play yourself, you don't need any of this: those bots never use a stored account. Caution Using bots breaks Ankama's terms of use, and Ankama can sanction the accounts involved. Read Accounts and safety before you store an account you care about. Open Account Manager In the sidebar, click Account Manager. The page lists your stored accounts, one per row: Column What it shows Login ID The login you type on Ankama's sign-in page. Status Signed in or Not signed in, plus Signs in on its own when a password is stored. Account status and actions explains what each badge really means. Type in Filter... to find an account in a long list. Before you add anything, the table reads "No accounts stored yet." Add the account Click Add an account. The Add a bot account dialog opens. In Login ID, type the login you use on Ankama's sign-in page. Spaces around it are removed. Fill in Ankama password (optional) only if you want Asterobot to sign this account in by itself. The next section explains the difference. Click Add. It stays greyed out while Login ID is empty. The account appears in the table as Not signed in. Adding it doesn't contact Ankama at all, so a wrong login or password isn't detected at this point. Sign the account in next, with Automatic sign-in if you stored a password, or Manual sign-in otherwise. If Asteroboard shows Couldn't add the account, the usual reason is that an account with the same Login ID is already stored. A Login ID can only be stored once. You don't have to leave the Add a bot dialog to do this. The button next to its Account field opens the same dialog, then the sign-in dialog, and selects the new account for the bot. See Add a bot. With or without a password The password is the whole switch for automatic sign-in. There's no other setting to turn it on. With a password, the account gets the Signs in on its own badge. You can sign it in with one click, and when a bot later needs the account and its sign-in has stopped working, Asterobot signs it in again by itself, through a browser it drives. Asterobot always tries a quiet renewal with Ankama first and only opens that browser when the renewal is refused. Without a password, the account works exactly the same while its sign-in is valid. The difference shows up when that sign-in stops working and can't be renewed quietly: a person then has to sign it in again, and a bot that tries to connect before that fails. You can store a password later, or replace it, from the sign-in dialog. See Manual sign-in. Asteroboard can't clear a stored password, though: to turn automatic sign-in off again, remove the account and add it back without one. What Asterobot keeps, and where Asterobot saves your accounts in a file called accounts.toml, in its data folder. Files and folders shows where that folder is on each system. For each account, the file holds: the Login ID; the password, if you stored one; the sign-in Ankama gave Asterobot: an access token and a refresh token, with when they were issued and when they expire. The password is not encrypted. It's written in the file as plain text, because Asterobot has to type it into Ankama's sign-in page. On Linux and macOS, Asterobot restricts the file so only your user account can read or change it, and applies that restriction again every time it starts. On Windows that restriction has no effect. In every case, anyone who can open files as your user, or who gets a copy of the file, can read the password and use the tokens. Accounts that sign in automatically leave two more things behind: A browser profile per account, in the zaapmanager/browser-profiles folder of Asterobot's data folder. It holds the account's Ankama session in the sign-in browser, which is what lets a later sign-in skip Ankama's form. On Linux and macOS, only your user can open it. Treat it like the password. A screenshot of the last failed automatic sign-in, in the zaapmanager folder of Asterobot's cache folder. There's one per account, replaced at each new failure. Automatic sign-in explains what it's for. Asterobot never sends the password back to Asteroboard: all it tells Asteroboard about an account is whether a password is stored and whether the account is signed in. Caution Never share accounts.toml, the browser profiles, or Asterobot's data folder, not even to get help. Getting help lists what's safe to share. One bot per account An Ankama account can belong to one bot only. Dofus allows one game session per account, and Asterobot enforces the same rule: adding a second bot with an account that already has one fails with Couldn't add the bot, and choosing it on a bot's Settings page is refused with this account is already associated with a bot. To run several bots in Full socket mode, store one account for each. See Many bots. Accounts and MITM mode A bot in MITM mode never uses a stored account, even when it has one: you sign in yourself, in Dofus, and the bot relays that session. That's why accounts protected by Ankama Shield or two-factor authentication can still be used in MITM mode. See Shield and two-factor authentication. Where to go next Automatic sign-in, if you stored a password. Manual sign-in, to sign the account in yourself. Add a bot, once the account shows Signed in.

Asterobot doesn't follow Dofus patches on its own. Each patch is a new game version, and the version Asterobot already downloaded stays exactly as it was. Go through these steps after a patch, in this order. They matter most in MITM mode, where your bot's game version must match the Dofus you play. A bot that signs in on its own keeps the version set on it until you change it. 1. Check for a new version In Game Manager, open the menu of the version you use. Click Check for latest version. Asteroboard answers Up to date or A newer version is available, followed in both cases by "Ankama's latest version is" and the version number. The same button is on the Information tab of the version's Game page. In MITM mode, the Ankama Launcher updates your Dofus. MITM mode shows where to read the version you play. 2. Download and extract the new version Click Download a game. Keep the defaults, with latest in Version and Extract data after downloading checked. If the new version is missing from the suggestions, click Check for updates first. Click Download. Keep Asteroboard open until the new row shows Ready for bot, so the extraction starts on its own. The new version gets its own row, next to the old one. Chunks Asterobot already stored for the old version aren't downloaded again. Download a game version covers every field of the dialog. 3. Look at the compatibility Check the Compatibility column of the new row: Compatible: your release of Asterobot was tested with this version. Different version: it wasn't. The info icon next to the badge names the version Asterobot is tested with. Different version doesn't block anything, but your bots may not work on that version yet. When Asterobot doesn't support the new version yet describes what you may see. 4. Move your bots Repeat this for each bot that uses the old version. Open the bot's page. If the bot is connected, connecting or waiting for your game, click Disconnect. Its game version can't change while it's online: the Settings tab says "Disconnect this bot to change its account or its game version." and greys out the fields until you do. Open the Settings tab. Under Game version, choose the new version. If it's the tested version, the Use tested version button selects it in one click. Click Save settings. Asteroboard shows Settings saved. Bring the bot back online with Connect or Start waiting. In MITM mode, click Start waiting only once your Dofus is up to date: while the two versions differ, the bot refuses to wait. Bot settings describes the rest of the Settings tab. 5. Remove the old version Once no bot uses the old version, open its menu in Game Manager: Delete frees the most space: the files, the extracted game data and the row go. Uninstall deletes the files and keeps the row with its extracted game data. Neither checks whether a bot still uses the version, so finish the previous step first. Manage game versions compares the two. When Asterobot doesn't support the new version yet Asterobot reads and writes the messages Dofus exchanges with its servers, and those messages change from one version to the next. Right after a patch, your release of Asterobot may not know the new version's messages yet. Here is what you can meet: Different version in the Compatibility column, on the Information tab of the Game page and under Game version in a bot's settings. A bot that signs in on its own doesn't connect. An alert titled Couldn't connect this bot appears at the top of its page, with the reason. In MITM mode, your game is disconnected when it reaches the bot, and Asterobot's log shows Failed to relay a game session followed by the reason. A script can't start, and its error begins with the game engine is not available:. When your release of Asterobot is too old for the version the Asterobot team currently supports, the reason tells you to update Asterobot. In that case: Download the new release of Asterobot. When one is published, Asteroboard shows Asterobot update available with a View on asterobot.net button when Asterobot starts, and the terminal prints An Asterobot update is available. Update it as Updating Asterobot explains. Look at the Compatibility column again. When the reason is only the game engine is not available, Asterobot couldn't get what it needs to read the game's messages at all, whatever the game version. Check that Asterobot is signed in to asterobot.net and can reach the internet, then try again. If it keeps happening, Getting help lists where to ask. Script authors will find how to keep their scripts working through patches in After a game update. Where to go next MITM mode Bot settings Game and updates in the FAQ

Game Manager lists every game version Asterobot knows about, with the tools to keep them in shape: check a version's files, add files to it, free disk space or remove it. The page Above the table sit Rescan, Check all chunks and Remove all chunks on the left, and Download a game on the right (Download a game version). Right above the rows, Filter... keeps the rows that contain what you type, and Columns hides or shows columns. Click a column's title to sort by it. At the bottom of the Version column, a count such as "2 / 3 installed" tells how many versions are installed out of all the rows, and page buttons appear when the list gets long. When nothing has been downloaded yet, the table says "No games yet." Columns Column What it shows Game The game's icon and name, once its download has finished, with its code, such as dofus, underneath. For an installed Dofus version for Windows, the name opens the version's Game page. Environment The environment, dofus3 for the Dofus that bots use. Platform The platform, windows for the Dofus that bots use. Version The version number. Status Where the download stands: Queued, Downloading, Verifying, Installed or Failed. A progress bar and a counter follow while downloading or verifying, and an info icon next to Failed shows the reason. See Download a game version. Extracted Where the extraction stands: Not extracted, Extracting, Extracted or Extraction failed. See Extract game data. Ready Ready for bot or Not ready. See Extract game data. Compatibility Compatible or Different version, compared with the Dofus version this release of Asterobot was tested with. Only for versions with the environment dofus3 and the platform windows. See Why Asterobot downloads Dofus. No title An Inspect button that opens the version's Game page, on the same rows as the link in Game. Actions on a version Each row ends with a menu button, and right-clicking a row opens the same menu. The Information tab of the version's Game page has the same actions as buttons (Game page). Action What it does Not available Verify files Checks the downloaded files and downloads again the ones that don't match. While the version is queued, downloading or verifying, and when it's Failed Download more files Downloads more files for this version, chosen with filters. Reads Retry on a Failed version. While the version is queued, downloading or verifying Extract data Extracts the game data. Reads Re-extract data once extracted. Until the version is Installed, and while it's extracting Remove extracted data Deletes the extracted game data and keeps the files. When nothing is extracted, and while it's extracting Check if ready for bot Checks on disk whether a bot can use the version, and answers in a notification. Always available Check for latest version Asks Ankama's download servers for the newest version with the same game, platform and environment, and answers Up to date or A newer version is available with "Ankama's latest version is" and its number. Always available Uninstall Deletes the downloaded files, keeps the row and the extracted game data. Until the version is Installed, and while it's queued, downloading or verifying Delete Deletes the files, the extracted game data and the row. While the version is queued, downloading or verifying Verify files Verify files reads every file of the version that is on disk, compares it with the list Ankama publishes for that version, deletes the files that don't match and downloads those again. The Status reads Verifying as soon as you click, even while the check waits for its turn, then Installed. It only checks files that were downloaded. It never adds files a narrower download left out: that's the job of Download more files. Verifications wait in the same queue as downloads, so one doesn't start while a version downloads. If the request can't be sent, Asteroboard shows Couldn't start verification. Download more files and Retry Download more files opens the Download more files dialog. Game, Platform, Environment and Version are locked to the version's own, and the rest works as in the download dialog: File filter (regex) starts with the pattern for the files a bot needs. Clear it to download every remaining file of the version. Fragment filter (regex) starts empty. Extract data after downloading starts checked. Files already on disk are left alone: only what newly matches the filters is downloaded. On a Failed version, the menu shows Retry and the dialog is titled Retry download. It resumes the download where it stopped, keeping the files that were finished. If the download can't be queued, Asteroboard shows Couldn't queue the download. Uninstall or Delete Both free the space the version's files take, and both ask you to confirm. They differ in what they leave behind: Uninstall Delete Downloaded files Deleted Deleted Extracted game data Kept Deleted The version's row Kept, with the status Installed Removed Ready Not ready No row left Shared chunks Kept Kept Getting the files back Download more files on the row Download a game again Uninstall suits a version you may need again soon: once Download more files brings its files back, it's Ready for bot without a new extraction. Its Status keeps saying Installed even with no file left, so look at the Ready column. Confirm in the Uninstall this game version? dialog with Yes, uninstall. Delete forgets the version entirely. Confirm in the Delete this game version? dialog with Yes, delete. As the dialog says, shared chunks are kept, so downloading the version again later is faster than the first time. Warning Neither action checks whether bots use the version. A bot that signs in on its own can't connect with an uninstalled version, and a bot whose version was deleted is skipped when Asterobot starts. Move your bots to another version first, as When Dofus updates shows. If Asterobot refuses, for example because a download of that version started in the meantime, Asteroboard shows Couldn't uninstall or Couldn't delete. Rescan Asterobot keeps track of the versions it downloaded. If you add or remove a version's folder by hand in its cache folder, click Rescan. Asterobot looks at the disk, adds each version folder it finds as Installed, and forgets the installed versions whose folder is gone. Rows that are queued, downloading, verifying or failed aren't touched. Asteroboard answers Rescan complete with the number of game versions that changed, or Couldn't rescan. Asterobot runs the same check each time it starts. A folder counts as installed as soon as it exists, whatever it holds, so look at the Ready column of the versions it adds. How chunks are stored Ankama's download servers deliver game content in chunks. Asterobot saves each chunk once, in a store shared by every game and every version, and rebuilds each version's files from them. This has three consequences: A chunk already in the store is never downloaded again, whichever version asks for it. Deleting a version leaves its chunks in the store, because other versions may use them. Chunks stay after the files are rebuilt, so they take space on top of the files. Check all chunks Check all chunks reads every stored chunk and deletes the ones whose content no longer matches, for example after a disk error. While it runs, the button shows a progress bar and a counter. It can run while a version downloads. When it's done, Asteroboard shows Chunk check completed, or Chunk check failed with the reason, whichever page you're on. A deleted chunk is downloaded again the next time a download needs it. The check doesn't repair the files a version already rebuilt: Verify files on that version does. If the check can't start, Asteroboard shows Couldn't start the chunk check. Remove all chunks Remove all chunks deletes every stored chunk, for every game and version. Nothing is lost for good: the next download or verification fetches the chunks it needs again, which makes it slower. Click Remove all chunks. In the Remove all stored chunks? dialog, click Yes, remove all chunks. The button is greyed out while any version is queued, downloading or verifying, and while Check all chunks runs. If one of those starts before your click reaches Asterobot, Asteroboard shows Couldn't remove the chunks. Free disk space From the gentlest to the most drastic: Remove all chunks. Your versions keep working: bots and the Game page read the rebuilt files and the extracted game data, not the chunks. Uninstall the versions no bot uses but that you may want back without extracting again. Delete the versions you don't need any more. The cache reset command deletes all of it at once: every game version, its extracted game data and every chunk, along with the rest of Asterobot's cache. Reset and start over shows how. From the command line Asterobot's command line can also download a version, list the versions, check a version's files, remove a version, and check or remove the chunks, without Asteroboard. Command line describes these commands. Where to go next When Dofus updates Game download problems

A downloaded game version is a folder of game files that bots, scripts and the Game page can't read as they are. Extracting turns them into game data: the game's tables and texts in a form Asterobot can search and query, plus the pictures the Game page draws. A version must be extracted before you can add a bot with it. If Extract data after downloading was checked when you downloaded the version, extraction has already started or finished. Otherwise, start it yourself, as Extract a version shows. What extraction builds Extraction only reads files already downloaded: it doesn't download anything. It runs these steps in order, and the progress counter starts again from zero at each step, several times during the game data: Pictures: the server illustrations shown when you pick a server, the item icons and the icons drawn on the world map. The world map artwork: 1,216 images covering the 40 world maps at each zoom level. The game data: the game's own tables (items, monsters, spells, maps, quests and the rest), the tables Asterobot derives from them, such as the index of every name in every language, the world travel graph, and the texts of every language whose text file was downloaded. The music, only when the version's sound banks were downloaded from the Music tab. If the music can't be extracted, the extraction still succeeds. The result is stored apart from the game files, in Asterobot's cache folder (Files and folders). Game data shows how to browse it, and scripts read it with asterobot:gamedata. Extract a version Open Game Manager. Open the menu at the end of the version's row, or right-click the row. Click Extract data. The Extracted column switches to Extracting, with a progress bar and a counter. Extraction runs inside Asterobot, so you can close Asteroboard in the meantime. Extract data is only available once the version's Status is Installed, and not while that version is already extracting. You'll find the same button on the version's Game page, in the Extracted data card of the Information tab. In the Add a bot dialog, you can also click the Not extracted or Extraction failed badge of the selected version. Each version extracts on its own. Extraction doesn't wait in the download queue, so it runs while another version downloads, and two versions can extract at the same time. The Extracted column Status Meaning Not extracted No complete extraction of this version is on disk. Extracting An extraction is running. The counter follows the current step. Extracted Every step left its output on disk: the pictures, the world map artwork and the game data. Extraction failed The last extraction stopped with an error. Asteroboard doesn't show why an extraction failed. The reason is in Asterobot's log, on a line starting with Failed to extract game data, which you can read in Asterobot's terminal or on Server > Console (Status and console). Extraction failed stays until you extract again or restart Asterobot. After a restart, Asterobot looks at what's on disk and shows Extracted or Not extracted. The usual cause is a missing file. A version downloaded with a narrower File filter (regex) than the default doesn't have everything extraction reads. Open the version's Game page: if its Required files card says Missing, click Download needed files, wait for the download to finish, then extract again. Ready for bot The Ready column says Ready for bot when a version has both halves a bot needs, and Not ready otherwise: the files a bot needs are downloaded: the game texts, the data tables, the map data and the world travel graph; the game data is extracted, along with the server illustrations. Neither half implies the other. A freshly downloaded version is Not ready until it's extracted, and a version whose files you uninstalled keeps its extracted game data but is Not ready too. The world map artwork and the item icons aren't part of the check: only the Game page uses them. Add a bot only accepts a version that is Ready for bot. A bot that signs in on its own also refuses to connect while its version isn't ready: Asteroboard then shows Bot's game version isn't ready yet, with "Its game files or extracted data aren't fully ready". The badge updates when a download or an extraction of the version finishes. To check right now, click Check if ready for bot in the version's menu or on its Game page. Asterobot looks at the disk and Asteroboard answers Ready for bot, Not ready for bot, or Couldn't check readiness when Asterobot couldn't be asked. Extract again Once a version is Extracted, the menu entry reads Re-extract data. It runs the whole extraction from scratch and overwrites what was there. Use it when the game data looks incomplete, or after you downloaded more files for the version. Scripts already running on that version pick up the new game data at their next lookup, as Game data overview explains. Remove extracted data Remove extracted data, in the version's menu or in the Extracted data card of its Game page, deletes the version's game data, its extracted pictures and its extracted music. The downloaded game files stay. The version turns Not extracted and Not ready, so a bot that signs in on its own can't connect with it until you extract it again. The action isn't available while the version is extracting, or when nothing is extracted. If an extraction starts before your click reaches Asterobot, Asteroboard shows Couldn't remove extracted data. Delete also removes the extracted game data, together with the files and the version's row: see Manage game versions. If extraction doesn't start Couldn't start extraction means the request didn't reach Asterobot. Check that Asteroboard is connected: the Preferences entry of the sidebar has no red dot. Then try again. Where to go next Manage game versions Game page Add a bot

Bots and the Game page work from game versions that Asterobot downloaded from Ankama's download servers. Your first bot downloads one with the default values. Open the download dialog In the sidebar, open Game Manager. Click Download a game. The Download a game version dialog opens, already filled in for the Dofus that bots use. The same dialog opens from Add a game, on the Game tab of the Add a bot dialog. The fields Field Default What it does Game dofus The game to download. Platform windows The platform whose files to download. Environment dofus3 The game's environment. Version latest A version number, such as 3.6.6.6, or latest for the newest version Ankama publishes. File filter (regex) The files a bot needs A regular expression matched against the paths of the game's files. Only matching files are downloaded. Empty downloads every file. Fragment filter (regex) Empty A regular expression matched against the names of the parts Ankama splits a game into. Empty downloads every part. Extract data after downloading Checked Starts extracting the version's game data as soon as the download finishes. Download stays greyed out until Game, Platform, Environment and Version are all filled in. Cancel closes the dialog without downloading. Game, Platform and Environment These three fields accept any text and suggest values as you type. The suggestions come from the list of games and versions Ankama publishes, which includes other Ankama games besides Dofus. Each field only suggests what goes with the fields above it: the platforms of the chosen game, then the environments of that game on that platform. Only one combination works with bots: dofus, windows and dofus3. A Dofus version for Windows in another environment still gets a Game page. Versions of other games or platforms download and show in the table like any other, but no bot can use them, they have no Game page, and extracting them fails. Check for updates, at the top of the dialog, fetches Ankama's list again, so the suggestions include what was published since. When Ankama can't be reached, the suggestions come from the lists Asterobot saved earlier. When Asteroboard can't reach Asterobot, it shows Couldn't check for updates, and you can still type the values yourself. Version The suggestions include every version found in the lists Asterobot saved, not only the newest one. The cytrus.keepMostRecentIndexes setting decides how many of these lists Asterobot keeps, and cytrus.keepMostRecentGamesManifests how many file lists it keeps for each game (Settings reference). latest is resolved when you click Download: Asterobot asks Ankama for its current list and takes the newest version for the chosen game, platform and environment. If Ankama can't be reached, Asterobot uses the last list it saved. The table always shows the real version number, never latest. File filter (regex) The field starts with the pattern Asterobot uses for the files a bot needs: the game texts, the data tables, the map data, the world travel graph, the version file and a few sets of pictures. Keep it unless you know you need more. An empty field downloads the whole game. To add files to a version later, use Download more files in its menu rather than downloading it again (Manage game versions). Fragment filter (regex) Ankama splits each game version into named parts. This filter only keeps the files of the parts whose name matches, on top of the file filter. The field suggests win64 as an example. Leave it empty unless you have a reason to narrow the download. A filter that isn't a valid regular expression makes the download fail, with a reason that mentions invalid file filter or invalid fragment filter. Extract data after downloading When it's checked, Asteroboard starts the extraction the moment the download finishes, exactly as if you clicked Extract data yourself (Extract game data). The box is checked when the dialog first opens. After you start a download, Asteroboard leaves it unchecked the next time you open the dialog, until you leave the page, so check it again when you want it. Important Asteroboard is what starts that extraction, so keep it open until the download finishes. If you close or reload it before then, the download carries on, but the version stays Not extracted. Open its menu and click Extract data. Download a version you already have Download a game doesn't download anything for a version already in the table as Queued, Downloading, Verifying or Installed: the filters are ignored and the version stays as it is. With Extract data after downloading checked, an installed version is extracted again. To add files to it, use Download more files. A version whose status is Failed is downloaded again, with the filters you give. One download at a time Downloads and file verifications wait in a single queue, and only one of them runs at a time, whatever the game or the version. The others show Queued until their turn. Extractions and the chunk check don't wait in that queue. Follow the download The version appears in the Game Manager table as soon as you click Download. Status Meaning Queued The download waits for its turn. Downloading Files are downloading. A progress bar and a counter follow. Verifying The version's files are being checked after Verify files. Installed The download finished. Failed The download stopped. Point at the info icon next to the status to read the reason. The counter counts chunks and rebuilt files, not bytes, so it gives an idea of the progress rather than a size. Once the download is done, the Game column shows the game's icon and name. With Extract data after downloading checked, the Extracted column then goes to Extracting and Extracted, and Ready turns to Ready for bot. Closing Asteroboard doesn't stop a download, since it runs inside Asterobot. Stopping Asterobot does. When Asterobot starts again, a version interrupted that way shows Installed although files are missing, and its Ready column says Not ready. Open its menu, click Download more files and keep the default filter: the finished files are kept and only the rest is downloaded. Asterobot doesn't check the free space on your disk before downloading. If the disk fills up, the download stops with Failed. When a download fails What you see What to do Couldn't queue the download when you click Download Asterobot refused the request or couldn't be reached. The usual cause is a latest that can't be resolved, because the game, platform or environment isn't on Ankama's list. Pick them from the suggestions, click Check for updates, and check that Asterobot can reach the internet. Failed, with a reason about the network or Ankama's servers Open the version's menu and click Retry. The download resumes where it stopped. Failed, with invalid file filter or invalid fragment filter in the reason Click Retry and correct the filter in the dialog. Failed, with download queue is full or the server is shutting down Asterobot was stopping, or too many downloads were waiting. Click Retry once Asterobot runs normally. Game download problems covers more cases. Download needed files for a bot On the Game tab of the Add a bot dialog, and on a bot's Settings tab, Asteroboard checks the version selected under Game version and shows badges next to it: Compatible or Different version (Why Asterobot downloads Dofus); "Checking required files...", then Ready when the files a bot needs are on disk, or Missing required files with a Download needed files button; the extraction status, such as Not extracted, which you can click to extract the version. Download needed files downloads only the missing files of that version, in the same queue as other downloads. When it's done, the badge turns to Ready. It doesn't extract the version: click the extraction badge once the download is finished. If the download fails, Asteroboard shows Couldn't download the required files. As long as the version lacks its files or its game data, the tab says "This version needs both its game files and extracted data before a bot can connect with it". The same check is on the Information tab of the version's Game page, in the Required files card (Game page). Add a bot describes the rest of the dialog. From the command line Asterobot's gamemanager download command downloads a version without Asteroboard. Command line lists its options. Where to go next Extract game data Manage game versions

Asterobot doesn't take game files or game data from the Dofus you play. It downloads its own copy of the game files from Ankama's download servers, one game version at a time, and works from that copy. Download a game version shows how to get one. A copy of its own The Dofus you installed with the Ankama Launcher stays yours. Asterobot doesn't take game data, maps or texts from it, and it doesn't install or update it. The only time it touches that folder is in MITM mode, short for man-in-the-middle: it reads the version number in its version file and changes one line of that file so your game signs in through Asterobot. MITM mode explains that line. Asterobot's copy is always the Windows version of Dofus, even when Asterobot runs on macOS or Linux. And by default it isn't the whole game, only the files a bot needs: the game texts, in every language the game ships; the game's data tables: items, monsters, spells, servers and the rest; the map data; the world travel graph the game uses to plan long trips, through zaaps and boats; a few sets of pictures: the server illustrations, the world map artwork, the item icons and the icons drawn on the world map; the file that states the version number. The game's music isn't part of it. You can get it later from the Game page, as Music explains. Several game versions can sit side by side, each with its own row in Game Manager. What the copy is used for Downloading is only half of the job. Asterobot then extracts the game files into game data, which is what everything else reads (Extract game data). What What it needs Adding a bot A game version that is Ready for bot: the files a bot needs are downloaded and its game data is extracted. A bot that signs in on its own also refuses to connect while its version isn't ready. Scripts The game data of the bot's game version, to turn the numbers in the game's messages into items, monsters, maps and texts. See Game data overview. The Game page The game data and the files of the version, for the world map, the map viewer, the game data browser, the texts and the music. See Game page. The tested version Every release of Asterobot is tested with one Dofus version: the tested version. Asteroboard compares each Dofus version you download with it and shows a badge: Compatible when the version is the tested version. Different version when it isn't. The info icon next to the badge shows "Asterobot is tested with", followed by the tested version of your release, and "This version may not work as expected." The badge appears in the Compatibility column of Game Manager, on the Information tab of the version's Game page, and under Game version in the Add a bot dialog and on a bot's Settings tab. It's only shown for Dofus versions with the environment dofus3 and the platform windows, the ones bots can use. When the tested version is downloaded, Add a bot selects it for you. Whenever another version is selected, a Use tested version button, followed by the version number, switches back to it in one click. A different version isn't blocked: you can still add a bot with it. But the messages Dofus exchanges with its servers change from one version to the next, and Asterobot speaks those of the tested version, so a bot on another version may fail to connect. Map ids, table columns and game texts also move between versions, which means the game data of one version doesn't always match another. When Dofus updates covers what to do after a patch. MITM mode needs the same version In MITM mode, the Dofus you play and your bot's game version must be exactly the same version. When they differ, the bot refuses to start waiting for your game. So each time the launcher updates your Dofus, download the new version in Asterobot too. MITM mode shows how to compare the two versions. Disk space Game versions live in Asterobot's cache folder, listed in Files and folders. Three kinds of things go there: Chunks. Ankama's download servers deliver game content in pieces called chunks. Asterobot stores each chunk once, named after its content, whatever version or game it came from. The files of each game version, rebuilt from those chunks. The extracted game data of each version. Because chunks are stored by content, a chunk Asterobot already has is never downloaded again, whichever version needs it. The chunks stay after the files are rebuilt, though, so the same content takes space twice until you remove them. Remove all chunks in Game Manager frees that space, at the cost of a slower next download (Manage game versions). The code gives a few sizes, which change with game updates: Item Approximate size The world map artwork, part of the files a bot needs 545 MB The map data, part of the files a bot needs 450 MB, measured on Dofus 3.6.10.10 The game's music, downloaded only from the Music tab 900 MB Asterobot doesn't check the free space on your disk before a download. If the disk fills up, the download stops and its status turns to Failed. Requirements sums up the space to plan for. Where to go next Download a game version Extract game data When Dofus updates

This walkthrough gets a first bot running in MITM mode, short for man-in-the-middle: you play Dofus as usual, and the bot joins your game session through Asterobot. It needs no Ankama account in Asterobot and no package, so it's the quickest way to see Asterobot at work. Plan for the game download to take a while the first time. Before you start, you need: Dofus 3 installed with the Ankama Launcher on the computer where Asterobot runs, and up to date. Asterobot running and signed in to asterobot.net. See First launch and Sign in with asterobot.net. Caution A bot in MITM mode is still a bot. Using bots breaks Ankama's terms of use, and Ankama can sanction the accounts involved. Read Accounts and safety first. 1. Download the same Dofus version Asterobot doesn't use the Dofus you play for game files: it only reads the version number in its version file and changes one line there, as What Asterobot just changed explains. It needs its own copy of the same version, downloaded from Ankama. In the sidebar, open Game Manager and click Download a game. Leave the fields as they are: Game dofus, Platform windows, Environment dofus3 and Version latest, which means the newest version Ankama publishes. When your Dofus is up to date, that's the version you play. Leave File filter (regex) as it is. It limits the download to the files a bot needs. Make sure Extract data after downloading is checked. Click Download. The version appears in the table. Its Status goes from Queued to Downloading, then Installed. The Extracted column then goes from Extracting to Extracted, and Ready turns to Ready for bot. Important Keep Asteroboard open until the download finishes. Asteroboard is what starts the extraction once the files are in, so if you close it earlier, the version stays Not extracted. In that case, open the version's menu in the table and click Extract data. The Dofus you play states its version in the file Dofus_Data/StreamingAssets/version of its folder, on the Version= line. It must be exactly the version in Game Manager: when Dofus updates, download the new version too, as When Dofus updates explains. 2. Add the bot Open Bot Manager and click Add a bot. On Identity, type a name in lowercase letters, digits and hyphens, or leave it empty and Asterobot picks one. Leave Account empty: without an account, the bot can only relay a game you play yourself, which is exactly what you want here. On Game, choose the version you downloaded under Game version. Its badges should read Ready and Extracted. Leave Language as it is: the dialog only sends it when you choose a library package on Behavior / Script, so a bot added with no package is saved in French whatever you pick. The language sets the game texts a package reads and the server names shown for the bot, and you can change it later on the bot's Settings tab. Add a bot explains every field of this dialog. On Connection, under Once the bot is added, choose Wait for my game client. Sign in now is selected at first, but it needs an account, and Add bot stays greyed out until you choose another option. Leave Server selection and Device identifier (HWID) as they are: they matter when a bot signs in on its own, and a relaying bot takes the device identifier of your game. On Behavior / Script, leave None selected. Click Add bot. The dialog closes, and the bot appears in the table with Waiting for your game client in its Network column. Click its name to open its page. If Asteroboard shows Bot added, but it couldn't be connected, the bot exists but isn't waiting. That happens when the Dofus you play isn't the version you downloaded, when Asterobot can't read the version file of your Dofus folder, or when another program already uses port 5555 or 5556. Fix the cause, then click Start waiting on the bot's page. What Asterobot just changed To send your game through Asterobot, Asterobot edited one line of Dofus_Data/StreamingAssets/version in your Dofus folder: the ConfigUrl line, which tells Dofus where to sign in. It now points at Asterobot. The rest of the file is untouched, and Asterobot puts the original line back once no bot is waiting any more, or when it stops normally. Asterobot's terminal, and the Console tab of the Server page, show Pointed the played game at Asterobot when it makes the change. Asterobot looks for your Dofus folder in the Ankama Launcher's usual place: %AppData%\Ankama\Dofus-dofus3 on Windows and ~/.config/Ankama/Dofus-dofus3 on Linux. On macOS, or when your game is installed somewhere else, enter the folder yourself in the botmanager.mitmGamePath setting on Server > Config, then click Disconnect and Start waiting on the bot's page. Warning When botmanager.mitmGamePath is empty, the bot still waits, but nothing is edited and your game never reaches it. If you don't see Pointed the played game at Asterobot after the bot starts waiting, check that setting first. 3. Start Dofus and play Start Dofus from the Ankama Launcher, now that the bot is waiting. If Dofus was already open, close it and start it again. Sign in, choose your server and your character as you always do. Once your game joins its server, the bot's status changes to Connected to game server. Its Console tab shows the steps, among them Attached to Ankama account, A client is being sent to us and Relaying a game session. Your game plays exactly as usual. The bot remembers the Ankama account it attached to. From now on it only takes game sessions from that account, and a game signed in with another account plays normally without going through this bot. The Information tab now shows your account's details and the server you're on. 4. Read your chat and your inventory Messages from your game only reach Asteroboard when you ask for them. Two switches do that for the most useful ones: On the bot's Console tab, turn on Live chat. From now on, chat messages your game receives appear in the console with the speaker's name. On the Inventory tab, turn on Live inventory. The game sends the full inventory once, when your character enters the game, so the Inventory tab can stay on Waiting for the inventory at first. Go back to character selection in Dofus and enter the game again: your kamas, pods and items appear. Next time, turn Live inventory on while the bot is waiting, before you choose your character. Both switches are saved with the bot. Warning The box at the bottom of the Console tab really sends a message in the game chat, as your character. 5. Look at your game's messages On the bot's page, open Tools. The Network tool opens on its Traffic panel. Switch to Settings. The list holds every message Asterobot can name. The ones behind your two switches are already checked. Type a word in Filter messages... to narrow the list, check the messages you want to follow, then click Apply. Go back to Traffic and play a little. Messages appear as they pass: green for events the server announces, red for requests, blue for responses. Click a message to see its fields. Pause freezes the list: messages that arrive while it's paused are dropped, not kept for later, even though the notice on screen says they're still recorded. Clear empties the list. Network traffic explains every part of the panel. 6. Stop When you quit Dofus, the bot goes back to Waiting for your game client, ready for the next time you play. It keeps the line in your Dofus folder pointed at Asterobot while it waits. To stop the bot for good, click Disconnect on its page. The bot stops waiting, Asterobot puts the original line back in your Dofus folder and prints Pointed the played game back at Ankama. If you're still in game at that moment, your game is disconnected: the bot was carrying its session. Next time, open the bot's page, click Start waiting, then start Dofus. Bots never start waiting on their own when Asterobot starts. If something goes wrong The bot never leaves "Waiting for your game client" while you play: check botmanager.mitmGamePath, make sure you started Dofus after the bot was waiting, and play with the Ankama account the bot attached to the first time. Couldn't put the bot into waiting: the causes are the same as for Bot added, but it couldn't be connected in step 2. Start by comparing the Version= line of your Dofus with Game Manager. Dofus won't sign in after Asterobot stopped abruptly: start Asterobot again. It puts the line back as it starts, as long as your bot comes back with it. If it doesn't, put the line back by hand. MITM problems covers every error in detail. What next Give your bot something to do: Run a package, or follow the tutorial Run a marketplace package. Learn everything about this mode in MITM mode. Run a bot without a game client with Full socket mode.

Asteroboard is where you do everything with Asterobot. This tour shows where things are, so the rest of the guide makes sense when it says "open Game Manager". It assumes Asterobot is running and Asteroboard is connected to it, as in First launch. The sidebar The sidebar lists Asteroboard's pages. At its top, next to the name, the version number of Asteroboard links to its release notes on asterobot.net. Entry What you do there Dashboard The start page, with a short welcome message. Bot Manager Add bots and control them. See Add a bot. Game Manager Download game versions from Ankama and extract their game data. See Download a game version. Account Manager Store Ankama accounts and sign them in. See Add an account. Library Manager Install, create and remove packages. See Manage your library. Server Asterobot's own Status, Console and Config tabs. See Status and console and The Config page. About Links to help, the Discord server and the status page, and the version of Asteroboard. Preferences Asteroboard's language, appearance and the address of your Asterobot. See Preferences. Badges give you a status at a glance without opening a page: Bot Manager, Game Manager, Account Manager and Library Manager show how many bots, game versions, accounts and packages they hold. Bot Manager also has a green number on its icon: how many bots are connected right now. Preferences shows a pulsing red dot whenever Asteroboard isn't connected to Asterobot. The button at the top left of every page folds the sidebar down to icons, and you can drag the sidebar's edge to make it wider or narrower. Asteroboard remembers the layout in your browser. The account button At the bottom of the sidebar, the account button shows whether Asterobot is signed in to asterobot.net. Once it is, the button shows your avatar and name, and opens a menu with Account, Online Profile and Log out. Sign in with asterobot.net explains each state. Notifications Asteroboard reports events in small notifications that pop up over the page. These are the ones you'll meet first: Notification When Server connected Asteroboard reached Asterobot. Server disconnected Asteroboard lost Asterobot. It keeps trying to reconnect on its own. Logged in as followed by your name Asterobot finished signing in to asterobot.net. Asterobot update available A newer Asterobot is on asterobot.net. Its View on asterobot.net button opens the download. It stays until you close it. See Updating Asterobot. Update available A new version of Asteroboard is ready. See Install Asteroboard as an app. A message with a megaphone icon An announcement from the Asterobot team. See Messages and updates. Most errors also appear as notifications, right after the action that failed. Bot pages Click a bot's name in the Bot Manager table to open its page. Every tab of a bot page shares the same header: The bot's name. Its connection: a status such as Disconnected or Connected to game server, next to Connect and Start waiting while the bot is disconnected, or Disconnect as soon as it's connecting, waiting or connected. See States and controls. Its package: the package the bot plays, next to Play (or Stop while it runs) and a menu with Load a new package, Load a package and play it and Unload package. See Run a package. Its tabs: Console, Information, Map, Inventory, Tools and Settings. Two things can appear under the header: a Pick a server card, when a bot's connection waits for you to choose a server, and red alerts when the bot couldn't connect or its script stopped with an error. Bot page describes all of it. Note Coming soon. The Map tab will show where your bot is. For now it always says "This bot hasn't reported a map yet." To look at maps, use the Game page below. The Game page Each installed game version has a page of its own. Open it from Game Manager, with the game's name or the Inspect button on the version's row. Its tabs are Information, Text, Maps, Game data and Music. Every tab except Information and Music has a Language selector that sets the language game texts are shown in. See Game page. Once you play music there, small player controls stay in the top bar while you browse other pages. Package pages In Library Manager, click a package's name to open its page. It shows where the package comes from, whether it works with your version of Asterobot, its manifest, the other versions you have installed and the bots set to play this version. A local package also has an Edit code button, which opens the editor. See Manage your library and The editor. Install Asteroboard as an app Asteroboard can be installed like an app from your browser, and then opens in its own window. Installed or not, it keeps working without an internet connection once it has loaded, as long as it can reach Asterobot. Asteroboard updates itself. While it's open, it checks for a new version every 30 minutes. When one is ready, it shows Update available with a Refresh now button, and switches to the new version when you click it or reload the page. If your browser can't prepare Asteroboard for offline use, it shows Offline mode unavailable: Asteroboard still works, but some features may then need an internet connection. Change the language In the sidebar, click Preferences. The Appearance section opens. Pick a language under Language: English, French or Spanish. By default, Asteroboard follows your browser's language. If your browser uses another language, Asteroboard starts in French. Once you've picked a language, a button next to the list, Use system language, goes back to following the browser. The choice only applies to this browser. Game texts on the Game page follow Asteroboard's language until you pick another one in the Game page's own Language selector. Each bot's language is a separate setting of the bot. The address of your Asterobot Preferences also has a Server section, with the Server URL Asteroboard connects to and a Test connection button. The address is filled in for you when you open Asterobot's own address, so you only need it for special setups. See Preferences. Where to go next Your first bot

Asterobot has to be signed in to your asterobot.net account before you can add a bot, and it installs marketplace packages with that account too. You never type your password into Asterobot for this: Asterobot gets a sign-in code, and you confirm that code on asterobot.net in your browser. When a code expires, Asterobot asks for a new one by itself. When Asterobot asks you to sign in Asterobot starts a sign-in on its own whenever it has none stored, which is the case on its first launch. It also starts one when asterobot.net stops accepting the sign-in it had, and when you click Sign in in Asteroboard after signing out. Each time, you can reach the sign-in link from three places: The terminal, on the line right after Website sign-in required. Please visit this link to authorize access to your account; the app will continue automatically once authorized. A browser tab that Asterobot opens by itself, on the computer where it runs. It does that for the first code only: if that code expires, the next ones don't open a tab. Asteroboard's account button, at the bottom of the sidebar, which now reads Sign-in pending. Confirm the code Open the link: click the account button in Asteroboard, or switch to the tab Asterobot opened. If asterobot.net asks you to sign in, sign in with your asterobot.net account. If you don't have one yet, you can create it now. Allow Asterobot to access your account. Close the tab. Within a few seconds, the terminal prints Website sign-in completed, Asteroboard shows Logged in as followed by your name, and the account button shows your asterobot.net avatar and name. Asterobot stays signed in after that, even when you restart it. The code The code has eight characters, digits and letters from A to F, and the link already contains it, after code=. Opening the link fills it in for you. If you open the address without the code at the end, for example because you typed the link by hand on another device, asterobot.net shows a Connect a device page instead. Type the eight characters in the Device code field and confirm. Spaces, hyphens and small letters don't matter. A code is valid for 15 minutes. If you don't confirm it in time, the terminal prints Sign-in was not completed in time; it will be offered again, and Asterobot asks for a new code by itself within a few minutes. The account button then opens the new link. For a new code right away, reload Asteroboard: if the account button reads Sign in, click it. Messages on asterobot.net Message What happened What to do "This code is invalid or has expired. Check the code displayed on your device and try again." The code was mistyped, was already used, or is more than 15 minutes old. Check the code, or open the newest link Asterobot gave you. "Too many incorrect codes have been entered. Wait a few minutes and try again." 20 codes that didn't match were typed from your connection within 15 minutes. Wait. You can type codes again at most 15 minutes after the last wrong one. "The authorization was denied. You can close this page; your device will stop waiting shortly." You refused access to Asterobot. Nothing, if that's what you meant. Asterobot stops waiting and asks again later. "This authorization link is invalid or has expired. Start again from your device." The page was opened from an outdated or damaged link. Open the newest link Asterobot gave you. "This authorization session has expired. Start again from your device." The code expired while you were signing in. Open the newest link Asterobot gave you. "The authorization could not be completed. Start again from your device." asterobot.net couldn't finish the sign-in. Open the newest link Asterobot gave you, or reload Asteroboard and click Sign in. Sign in from a phone When Asterobot runs on a machine where you can't open a browser, such as a server, it can print the link as a QR code in its terminal: In Asteroboard, open Server > Config and turn on website.showQRCode. Wait for the next code. The QR code appears in the terminal above the line Alternatively, scan the QR code above to open the link directly. Scan it with your phone and confirm the code there. The setting applies from the next code Asterobot asks for. If a code is already waiting, the QR code comes with the following one, or when Asterobot starts again without a sign-in. The account button The account button shows What it means What a click does Sign in, with a red dot Asterobot isn't signed in and isn't waiting for a code. Starts a new sign-in. Sign-in pending A code is waiting for you. Opens the sign-in link in a new tab. Your avatar and name, or Signed in while your profile loads Asterobot is signed in. Opens a menu with Account, Online Profile and Log out. Account opens a page about your asterobot.net account, described in Your account. Sign out and back in Click the account button, then Log out. The Disconnect button on the Account page does the same thing. Confirm. Asterobot forgets its sign-in, and the account button reads Sign in again. After you sign out, Asterobot doesn't sign back in by itself, not even when it restarts. To sign in again, click Sign in on the account button. Asterobot asks for a new code and opens the link in a browser tab on the computer where it runs, and the account button opens it too. When the sign-in stops working asterobot.net can stop accepting Asterobot's sign-in, for example once it has expired or has been revoked. When that happens, Asterobot forgets it and starts a new sign-in right away. The terminal shows a warning, such as Website rejected the token, then a new link, and the account button switches to Sign-in pending. Confirm the new code as described above. Keep the sign-in private Asterobot saves its sign-in in config.toml, as the website.token setting, which is how it stays signed in across restarts. Anyone who gets that value can use your asterobot.net access through it. Never share it, or the config.toml file that holds it. Getting help lists what's safe to share when you ask for help. Where to go next Tour of Asteroboard Your first bot

Asterobot runs in a terminal window and opens Asteroboard in your browser as it starts. You need the program unpacked as described in Download Asterobot. Start Asterobot On Windows Double-click asterobot.exe. A terminal window opens, and Asterobot runs inside it. Tip If Asterobot stops right after starting, its window closes before you can read why. Start it from PowerShell instead, in the folder where you put it, and the messages stay on screen: .\asterobot.exe On macOS and Linux Open a terminal in the folder where you put Asterobot and run: ./asterobot Commands and version Running Asterobot without a command starts it normally, exactly like ./asterobot server. The program also has commands for other jobs, such as downloading a game version or resetting the settings, all listed in Command line. To see which version you have without starting it, run ./asterobot --version (.\asterobot.exe --version on Windows). The last line it prints reads Asterobot version followed by the version number. What the terminal shows Asterobot writes what it's doing to the terminal, one line at a time, starting with a line that gives its version and the website's address. On a first launch, these are the lines worth looking for: Line What it means Bots restored from config Asterobot loaded your saved bots. On a first launch, there are none. Server listening Asterobot is ready at the address that follows: 127.0.0.1:8080 by default. Website sign-in required. Please visit this link to authorize access to your account; the app will continue automatically once authorized. Asterobot isn't signed in to asterobot.net. The next line is the link to open. Website sign-in completed You confirmed the sign-in on asterobot.net. An Asterobot update is available A newer version is published on asterobot.net. The line ends with its version number and its link. Failed to open frontend Asterobot couldn't open your browser. Open Asteroboard yourself, as explained below. Asterobot prints other lines as well. Status and console explains how much it prints and how to change that. Asteroboard opens Once it's ready, Asterobot opens your browser at http://127.0.0.1:8080. That address sends the browser on to https://asteroboard.asterobot.net with Asterobot's address attached, which is how Asteroboard knows where to connect. Asteroboard saves the address as its Server URL, removes it from the address bar, and shows Server connected once it has reached Asterobot. If no browser window opens, go to http://127.0.0.1:8080 in your browser yourself. If you'd rather Asterobot never opens the browser when it starts, turn on the server.skipOpenFrontend setting on Server > Config. On a first launch, a second tab opens on asterobot.net at the same time. That's Asterobot asking you to sign in: Sign in with asterobot.net explains what to do there. What Asterobot creates on your computer On its first launch, Asterobot creates its folders in your user profile, for its settings (a config.toml file, empty for now), its data and its cache. On Linux, those are three separate folders. On Windows, the data and the cache share one folder, and on macOS, the settings and the data do. They stay when Asterobot stops, and it finds everything in them the next time it starts. Files and folders shows where they are on each system. Keep it running Asterobot only works while it runs. Leave its terminal window open for as long as you use your bots: you can minimize it, but closing it ends Asterobot. Closing Asteroboard, on the other hand, doesn't stop anything, as The three parts explains. Stop Asterobot Stop Asterobot from its terminal or from Asteroboard. Both ways let it close things properly: it disconnects your bots, and puts back the line it may have changed in your Dofus folder for MITM mode, where a bot joins the game you play. From the terminal Press Ctrl+C in Asterobot's terminal window. Asterobot prints Shutting down server, closes everything and exits. From Asteroboard In the sidebar, click Server. The Status tab opens. In the Shutdown card, click Shutdown server. In the Shutdown the server? dialog, click Yes, shutdown. Asteroboard shows Shutdown requested, and Asterobot stops about two seconds later. Asteroboard then shows Server disconnected. Important Asteroboard can't start Asterobot again. After a shutdown, you need access to the computer Asterobot runs on to start it. Closing the terminal window also ends Asterobot, but it may not get the chance to close things properly. If it left your Dofus folder changed, it puts it back the next time it starts. Start it again Start Asterobot the same way as the first time. What you set up is still there: Asterobot is still signed in to asterobot.net, so you don't need a new code. Your bots come back, disconnected. Nothing reconnects or starts playing on its own: you bring each bot online again from Asteroboard. See Disconnect, delete and restart. Your browser opens Asteroboard again, unless you turned on server.skipOpenFrontend. If Asterobot stops right away with An error occurred during the server's initialization process, it couldn't use its address, for example because another copy of Asterobot is already running. Asteroboard can't connect helps you sort it out. Where to go next Sign in with asterobot.net Tour of Asteroboard

Asterobot is a single program packed in a .7z archive. There's no installer: you download the archive made for your computer, check it if you like, and unpack it wherever you want to keep it. Pick the right archive Asterobot is published at https://asterobot.net/files/category/3-asterobot/. Open the Asterobot file there. Each version comes with six archives, one for each system and processor, and a checksums.txt file. The archive names follow the pattern Asterobot_VERSION_SYSTEM_PROCESSOR.7z, where VERSION is the version number: Your computer Archive to download Windows with an Intel or AMD processor Asterobot_VERSION_windows_amd64.7z Windows with an ARM processor Asterobot_VERSION_windows_arm64.7z Mac with Apple silicon Asterobot_VERSION_darwin_arm64.7z Mac with an Intel processor Asterobot_VERSION_darwin_amd64.7z Linux with an Intel or AMD processor Asterobot_VERSION_linux_amd64.7z Linux with an ARM processor Asterobot_VERSION_linux_arm64.7z In these names, darwin means macOS, amd64 means an x86-64 processor from Intel or AMD, and arm64 means an ARM processor. Requirements lists which computers each build supports. Find your processor type Windows: open Settings > System > About and read System type. "x64-based processor" means amd64, and "ARM-based processor" means arm64. macOS: open the Apple menu > About This Mac. If it shows a Chip such as Apple M1, you need arm64. If it shows an Intel Processor, you need amd64. Linux: run uname -m in a terminal. x86_64 means amd64, and aarch64 means arm64. Check the download checksums.txt lists the SHA-256 checksum of every archive of the version. If the checksum of the file you downloaded matches its line, the file is exactly the one that was published. Checking takes a few seconds: download checksums.txt into the same folder as your archive, then follow the steps for your system. On Linux Run this in the folder that holds both files: sha256sum --ignore-missing -c checksums.txt It prints the name of your archive followed by OK. The --ignore-missing option skips the archives you didn't download. On macOS Run this in the folder that holds the archive, with your archive's real name: shasum -a 256 Asterobot_VERSION_darwin_arm64.7z Compare the long code it prints with the code on your archive's line in checksums.txt. On Windows Open PowerShell in the folder that holds the archive and run this, with your archive's real name: Get-FileHash -Algorithm SHA256 .\Asterobot_VERSION_windows_amd64.7z Compare the Hash it shows with the code on your archive's line in checksums.txt. PowerShell writes it in capital letters and checksums.txt in small ones, which makes no difference. If the codes don't match, don't run the file. Delete it and download it again. Unpack the archive The archive contains a single file: asterobot.exe on Windows, asterobot on macOS and Linux. Windows: open the archive with 7-Zip or any other program that reads .7z files, and extract asterobot.exe. macOS: open the archive with an app that reads .7z files, and extract asterobot. Linux: extract it with 7-Zip's command line. On Debian and Ubuntu, it's the 7zz command from the 7zip package: 7zz x Asterobot_VERSION_linux_amd64.7z Choose where to keep it Put the program in any folder you like. Asterobot doesn't store anything next to itself: your settings, bots, Ankama accounts, game versions and packages all go to folders of your user profile, listed in Files and folders. You can move the program later without losing anything, and updating Asterobot means replacing this one file (see Updating Asterobot). Make it executable on macOS and Linux On macOS and Linux, give the file permission to run before you start it. In a terminal, from the folder where you put it: chmod +x asterobot Where to go next First launch starts Asterobot for the first time.

Asterobot works together with an account on asterobot.net, the Asterobot website. If you already have one, you can go straight to Download Asterobot. What the account is for Signing Asterobot in. The first time Asterobot starts, it asks you to sign in with your asterobot.net account, and you can't add a bot until it's signed in. Sign in with asterobot.net walks you through it. The marketplace. When you install a package from the marketplace, Asterobot fetches it with the account it's signed in with. Sharing a package of your own there also needs an account. See The marketplace. The forum. You need it to ask questions and to reply to other players on https://asterobot.net/forums/. Create it Open https://asterobot.net and create your account with the website's sign-up option. You can also wait until Asterobot asks you to sign in. The sign-in code it gives you stays valid for 15 minutes, which leaves time to create the account on asterobot.net first and then confirm the code. Tip Asterobot never asks for your asterobot.net password. You only ever type it on asterobot.net itself, and Asterobot gets access through the code you confirm there. Where to go next Download Asterobot