Smooth

Asterobot keeps its own copy of Dofus, separate from the one you play, and neither that copy nor Asterobot updates itself. Why does Asterobot download Dofus when I already have it? Because Asterobot works from its own copy of the game files. Bots, scripts and the Game page all read the game data, maps and texts from that copy, never from the Dofus you play. By default it only downloads the files a bot needs, not the whole game, and always the Windows version. See Why Asterobot downloads Dofus. How much disk space does it need? It depends on the Dofus version, and Asterobot doesn't give a total. A few sizes, all approximate: 545 MB for the world map artwork and 450 MB for the map data (measured on Dofus 3.6.10.10), both part of every game version you download, and 900 MB for the game's music, only if you download it from the Game page's Music tab. Extracting the game data takes more space on top of the files. Asterobot doesn't check the free space before a download. When the disk fills up, the download stops and its status turns to Failed. See Why Asterobot downloads Dofus. How do I free disk space? From Game Manager. Remove all chunks deletes the stored pieces game versions are rebuilt from, at the cost of a slower next download. Uninstall deletes a version's files and keeps its extracted game data, and Delete removes the version completely. Neither Uninstall nor Delete checks whether a bot still uses the version. See Manage game versions. Dofus just got a patch. What do I do? Download the new game version, move your bots to it, then remove the old one: In Game Manager, click Download a game, keep latest in Version and Extract data after downloading checked, and click Download. Keep Asteroboard open until the new row shows Ready for bot. On each bot, click Disconnect, choose the new version on its Settings tab, and click Save settings. Once no bot uses the old version, delete or uninstall it. It matters most in MITM mode, where your bot's game version must be the Dofus version you play. See When Dofus updates. Why does my MITM bot refuse to start waiting after a patch? Because the Dofus you play and your bot's game version are no longer the same version. Asteroboard shows Couldn't put the bot into waiting, without saying why. Download the new version, move the bot to it and click Start waiting again. When your bots use different game versions, keep them all on the version you play. See MITM mode. What do Compatible and Different version mean? Compatible means your release of Asterobot was tested with that Dofus version, and Different version means it wasn't. A different version isn't blocked, but the game's messages change from one version to the next, so a bot on it may fail to connect, and its game data may not match what you expect. See Why Asterobot downloads Dofus. What happens when Asterobot doesn't support the new Dofus version yet? Your bots may not work on it. You can meet Different version in Game Manager, a Full socket bot that doesn't connect and shows Couldn't connect this bot, a MITM game that gets disconnected as it reaches the bot, and scripts that can't start, with an error beginning with the game engine is not available:. When the reason tells you to update Asterobot, download its new release. See When Dofus updates. Does Asterobot update the Dofus I play? No. The Ankama Launcher updates your Dofus. Asterobot doesn't follow patches either: each patch is a new game version you download in Game Manager, and the versions already there stay as they were. See When Dofus updates. Can I keep several game versions? Yes. Each version has its own row in Game Manager, each bot uses the version set on it, and pieces of content that several versions share are stored once. See Manage game versions. How do I know a new Asterobot is out? Asterobot checks asterobot.net each time it starts. When a newer version is published, the terminal prints An Asterobot update is available, and Asteroboard shows Asterobot update available with a View on asterobot.net button. A version published while Asterobot runs is only noticed at its next start. See Messages and updates. How do I update Asterobot? Download the new archive, stop Asterobot, replace the program file with the new one, and start it again. On macOS and Linux, make the new file executable with chmod +x asterobot first. Your bots, accounts, packages, game versions and settings stay, since they live in other folders. After the update, bring your bots back online and look at the Compatibility column of Game Manager. See Updating Asterobot. Will my packages still work after an update? They can stop working in two cases. A package that states which versions of Asterobot it works with can turn Incompatible after you update Asterobot, and it won't start then. And a Dofus patch can change the messages a script relies on, until its author adapts it. Authors can read After a game update.

How bots connect, how many you can run, and what happens to them when things stop. Should I use Full socket mode or MITM mode? Start with MITM mode. You play Dofus as usual and the bot joins your session: there's nothing to store in Asterobot and no connection script to find, and it works with accounts protected by Ankama Shield or two-factor authentication. Full socket mode is for bots that play without you and without a Dofus window, but each bot needs its own Ankama account and a connection script to enter the game. See Full socket and MITM. Why doesn't my Full socket bot enter the game? Because Asterobot's part ends once the connection to the game server is open. It signs the account in, picks a server and connects, but it doesn't identify the bot on the game server or choose a character. A connection script does that: a package you start with Play. Connected to game server only means the connection is open, whether the bot got into the game or not. Note Coming soon. Ready-made connection scripts will take a Full socket bot into the game. Until then, use MITM mode, or write your own by following Identify and run. Full socket mode explains it in full, and Bot doesn't connect covers the errors. Can I play Dofus while a bot uses my account? In MITM mode, yes: that's what the mode is for. You keep playing, and a package running on the bot controls the same character as you, with nothing to coordinate the two of you. In Full socket mode, no. An Ankama account has one game session at a time, and a bot that connects while the account is already in the game fails with identification was refused: account already connected elsewhere. See MITM mode, and for script authors, Sessions. Does Asterobot change my Dofus installation? Only one line, and only in MITM mode. Asterobot edits the ConfigUrl line of Dofus_Data/StreamingAssets/version, in your Dofus folder, so your game signs in through Asterobot. It puts the original line back when no bot is waiting any more and when Asterobot stops normally, or the next time it starts after an abrupt stop, provided one of your bots comes back as it starts. It never installs or updates your Dofus. See MITM mode. Dofus won't sign in since Asterobot stopped. What do I do? Start Asterobot again. While that line points at Asterobot, Dofus can't sign in without it, and Asterobot puts the line back as it starts, provided one of your bots comes back with it. If the log doesn't show Restored a game install left pointing at Asterobot by a previous run, put the line back by hand. See MITM problems. Why does my MITM bot stay on Waiting for your game client? Your game isn't reaching the bot. The usual causes: Dofus was already open when the bot started waiting. Close it and start it again. botmanager.mitmGamePath is empty or points at the wrong folder. Asterobot's log shows Pointed the played game at Asterobot when it edited your Dofus folder. The bot is attached to another Ankama account. It only takes the sessions of the account it attached to the first time. server.tls is on or server.basicAuth is set. MITM mode doesn't work with either of them. See MITM mode and MITM problems. What happens to my game when I stop a bot? That depends on the button. Stop only stops the bot's script, and your game carries on. Disconnect on a MITM bot ends the session it relays, so your Dofus is disconnected if you're in the game. Stopping Asterobot does the same to every bot. See Disconnect, delete and restart. What happens when I quit Dofus in MITM mode? The bot goes back to Waiting for your game client and takes your next session by itself. The script it was running stopped, though: press Play again once your game is back. See MITM mode. How many bots can I run? As many as your asterobot.net account allows. Every bot listed in Bot Manager counts, connected or not, and past that number Add a bot fails with Couldn't add the bot. In Full socket mode, each bot also needs its own Ankama account, and in MITM mode each bot relays one Dofus client. See Many bots. Can two bots use the same Ankama account? No. An Ankama account can belong to one bot only, since Dofus allows one game session per account. Adding a second bot with it fails with Couldn't add the bot, and choosing it on a bot's Settings is refused with this account is already associated with a bot. Store one account for each Full socket bot. See Many bots. Can one bot use both modes? Yes, but not at the same time. A bot with an Ankama account offers both Connect and Start waiting, and a bot without one can only wait for your game. Disconnect the bot before you switch. See Full socket and MITM. Do my bots reconnect by themselves? No. Asterobot never connects a bot or starts a script on its own. After Asterobot restarts, every bot is Disconnected and nothing plays. When a Full socket bot's connection drops, click Disconnect, then Connect, then Play. See Disconnect, delete and restart. Are my bots kept when Asterobot restarts? Yes. Every bot is saved in bots.toml, with its settings, its package, its package settings and its message selection, and comes back disconnected when Asterobot starts. Its console history doesn't come back, and neither does an inline script loaded on it. See Disconnect, delete and restart. Why is a bot missing after I restarted Asterobot? Asterobot skipped it. That happens when the bot's Ankama account is no longer in Account Manager, when its game version is no longer installed, when Asterobot couldn't prepare Ankama sign-ins, or when it couldn't confirm your asterobot.net account in its first seconds. The terminal shows a warning starting with skipping bot restore:, followed by the reason. The bot's configuration is still saved: fix the cause and restart Asterobot. Don't add a new bot with the same name, which replaces the saved one for good. See Disconnect, delete and restart. I play several accounts in MITM mode. Which bot gets which game? Each game goes to the waiting bot attached to its Ankama account. 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, and keeps that attachment for good. To decide which bot relays which account, start waiting on one bot at a time and sign in with the account you want on it. See Many bots. Can I use other computers? Yes. Asteroboard can run on a phone or another computer, Asterobot on a server or a computer you don't sit at, and in MITM mode Dofus can even be on a third computer. None of this works with the default settings, which only accept connections from Asterobot's own computer. How the parts connect shows each setup, and Asteroboard and network answers the common questions.

Read these answers before you use Asterobot with an Ankama account you care about. Can my Ankama account get banned? Yes. Using a bot breaks Ankama's terms of use, and Ankama can sanction the accounts involved at any time. That holds in Full socket mode and in MITM mode, with a package you wrote or one from the marketplace. Nobody can promise that an account stays safe, and these docs give no advice on avoiding detection. Only use an Ankama account with Asterobot if you accept that risk. Is MITM mode safer for my account? No. A bot in MITM mode is still a bot, and it breaks Ankama's terms of use just the same. What MITM mode changes is who holds your login: you sign in yourself, in Dofus, and never give Asterobot your Ankama login or password. See Full socket and MITM. Where does Asterobot keep my Ankama password? In a file called accounts.toml, in Asterobot's data folder, as plain text, and only if you chose to store one. It isn't encrypted because Asterobot has to type it into Ankama's sign-in page. The same file holds each account's Login ID and the tokens Ankama gave Asterobot. On Linux and macOS, Asterobot restricts the file so only your user account can read it. On Windows that restriction has no effect. Either way, anyone who can open files as your user, or who gets a copy of the file, can read the password and use the tokens. Asterobot never sends the password back to Asteroboard. Add an account has the details, and Files and folders shows where the data folder is. Do I have to store my Ankama password? No. The password only serves automatic sign-in. Without one, you sign the account in yourself from Asteroboard whenever its sign-in stops working, as Manual sign-in shows. MITM mode needs no stored account at all. What else on my computer gives access to my accounts? A few files and folders, each worth protecting like a password: What Where What it gives access to accounts.toml The data folder Your Ankama Login IDs, the passwords you stored, and Ankama's tokens zaapmanager/browser-profiles/ The data folder A live Ankama session for each account that signed in automatically website.token config.toml, in the settings folder Your asterobot.net account, through Asterobot's sign-in server.basicAuth config.toml Asterobot's port, with passwords written in plain text On Linux and macOS, only your user can read these. On Windows, that protection has no effect. Never share any of them, not even to get help: Getting help lists what must stay private. Can I use an account protected by Ankama Shield or two-factor authentication? Only in MITM mode. Full socket mode doesn't support these accounts: Asteroboard has no field for a verification code, and automatic sign-in only types the Login ID and the password. In MITM mode, you sign in yourself in Dofus, codes included, and the bot relays that session. See Shield and two-factor authentication. What happens when Ankama shows a captcha during automatic sign-in? Asterobot gives up, and a person has to sign in. You have two ways out: Sign in yourself from the sign-in dialog. This always works, wherever Asterobot runs. When Asterobot runs on a computer you're sitting at, turn off zaapmanager.browserHeadless on Server > Config, start the automatic sign-in again, and answer the challenge in the browser window that opens. Turn the setting back on afterwards. See Automatic sign-in. Why doesn't Asteroboard say why automatic sign-in failed? Because its message is the same whatever went wrong, starting with ankama account authorization required. The real reason is only in Asterobot's log. In the terminal or on Server > Console, look for the warning Automatic Ankama sign-in failed, a person has to sign in: its error says what happened. When you started the sign-in from the dialog's own button, the dialog also shows a picture of the page the browser was on, which often tells a captcha from a wrong password. See Automatic sign-in. What can a package do with my account? Everything your character can do in the game. A package's script can send any message to the game server as your character, to move, fight, trade, sell or delete items. It reads everything the game sends, can read the session's game ticket and can close the game connection. On a MITM bot, it can also change or block what your Dofus and the server send each other. It can't read your Ankama login or password, open files on your computer, use the internet or reach your other bots. Only play packages from authors you trust. Trusting a package lists everything. Do package permissions limit what a package can do? Not yet. A package can list permissions in its manifest, but Asterobot doesn't enforce them: a package that lists none can still do everything described above. Note Coming soon. Asterobot will enforce the permissions a package lists. Until then, don't count on them to limit what a package does. See Trusting a package. What do I do if I think someone used my Asterobot? Stop Asterobot, or put server.listenAddress back to 127.0.0.1:8080 and restart it. Then change the basic auth passwords, click Disconnect on each Ankama account in Account Manager, change the Ankama passwords you had stored, and log Asterobot out of asterobot.net before signing in again. Security goes through each step, and explains who can reach Asterobot in the first place.

The basics: what Asterobot is, where it runs, and what keeps working when you close things. What is Asterobot? Asterobot is a program you run on your own computer to run bots for Dofus 3. A bot either signs in and plays on its own, in Full socket mode, or joins the game you play, in MITM mode (short for man-in-the-middle). What a bot does in the game comes from a package: a small JavaScript program from the marketplace, or one you write. Asterobot also lets you browse the game's data, maps and texts without any bot. What is Asterobot gives the full tour. What's the difference between Asterobot, Asteroboard and asterobot.net? Asterobot is the program that does the work, Asteroboard is the web interface you control it from, and asterobot.net is the website. Asteroboard opens at https://asteroboard.asterobot.net, but everything it shows comes straight from your Asterobot. asterobot.net holds your account, the downloads, the marketplace and the forum. See The three parts. Which systems does Asterobot run on? Windows, macOS and Linux, each on x86-64 (Intel or AMD) and ARM64 processors. That makes six builds, including one for Macs with Apple silicon and one for ARM boards such as the Raspberry Pi 4 and 5. The x86-64 builds need a processor with the x86-64-v2 instruction set, which every x86-64 processor made since about 2009 has. Requirements lists everything else you need. Which Dofus does it work with? Dofus 3. Bots only play Dofus 3, and Asterobot always downloads the Windows version of its game files, even on macOS or Linux. Each release of Asterobot is tested with one Dofus version, which Asteroboard marks Compatible. Why Asterobot downloads Dofus explains the tested version. Do I need Dofus installed? Only for MITM mode, where you play Dofus yourself and a bot joins your session. A Full socket bot needs no Dofus client at all. Either way, Asterobot downloads its own copy of the game files, separate from the Dofus you play. Full socket and MITM compares the two modes. Do I need to know how to code? No. Running a bot in MITM mode, installing a package from the marketplace and changing its settings all happen in Asteroboard. You need JavaScript to write packages of your own, and for now to get a Full socket bot into the game. Note Coming soon. Ready-made connection scripts will take a Full socket bot into the game without any code from you. Until then, use MITM mode, or write your own with Identify and run. Can I use Asterobot without running a bot? Yes. With a game version downloaded and extracted, the Game page lets you browse the world map, inspect maps cell by cell, search the game data, query it in SQL, read the game's texts and listen to its music. See Game page. Can I leave my bots running all day? Yes, as long as Asterobot keeps running and each bot's connection lasts. Asteroboard doesn't need to stay open. Keep in mind that nothing reconnects or starts again by itself: when a bot's connection drops, or when Asterobot restarts, you bring the bot back online and press Play yourself. In MITM mode, every session also starts with someone launching Dofus. Disconnect, delete and restart covers each case, and Asterobot on a remote machine shows how to keep Asterobot running on a machine you don't sit at. What happens when I close the browser or Asteroboard? Nothing stops. Your bots stay connected, their scripts keep running and downloads carry on, because all of that happens inside Asterobot. What only lived in the page goes away with it: the messages a bot's Traffic panel had captured and the chat lines its console showed from them, the contents of a bot's Inventory tab until the character enters the game again, the lines on Server > Console, the Extract data after downloading choice of a download that hasn't finished, and the music playing from the Game page. See The three parts. What happens when I close Asterobot's terminal window? Asterobot stops, and everything with it. Every bot disconnects, including a bot relaying the game you play, so your Dofus is disconnected too, and scripts and downloads stop. To stop it cleanly, press Ctrl+C in its terminal or click Shutdown server on Server > Status. Asterobot then also puts back the line it changed in your Dofus folder for MITM mode. After an abrupt stop, it puts that line back the next time it starts, provided one of your bots comes back with it (MITM problems). See First launch. Can Asteroboard start Asterobot again? No. Once Asterobot has stopped, you need access to the computer it runs on to start it. Meanwhile Asteroboard shows Server disconnected, and connects again by itself as soon as Asterobot is back. See First launch. Does Asterobot update itself? No. When a new version is out, Asterobot tells you as it starts, and you replace the program by hand. Your bots, accounts, packages, game versions and settings are kept. Asteroboard, on the other hand, updates itself. See Updating Asterobot. Is there an app? Asterobot has no window of its own: on Windows it runs in a terminal window, and on macOS and Linux you start it from a terminal. Asteroboard can be installed as an app from your browser, and then opens in its own window. See Tour of Asteroboard. Which languages is Asteroboard available in? English, French and Spanish. It follows your browser's language, and starts in French when your browser uses another one. To change it, open Preferences and pick one under Language. See Preferences. Where does Asterobot keep its files? In folders of your user profile, not next to the program: one for its settings, with config.toml, one for its data, such as bots, Ankama accounts and packages, and one for its cache, which holds the game versions. Files and folders shows where they are on each system and how to back them up. How do I reset Asterobot or start over? Pick the smallest reset that fixes your problem, since each one deletes something for good. Reset offline data and Reset preferences, on Preferences, only clear what Asteroboard keeps in your browser. Reset all, on Server > Config, puts your settings back to their defaults and signs Asterobot out of asterobot.net. cache reset deletes every game version, and keeps your settings, bots, Ankama accounts and library. Reset and start over helps you choose.

Everything you do in Dofus turns into messages between your game and Ankama's servers. This tutorial shows a few of them live on the MITM bot from Your first bot, while you walk and chat. No package is needed. Caution Don't tick IdentificationRequest for this tutorial. It's the first message your game sends, and it carries the ticket that opens your game session: never share a screenshot or a copy of it. 1. Bring your bot online On your bot's page, click Start waiting. Start Dofus from the Ankama Launcher, sign in and enter the game with your character. The bot's status turns to Connected to game server. 2. Choose a few messages On the bot's page, click Tools. The Network tool opens on its Traffic panel. Click Settings. The list holds every message Asterobot can name, with a box to tick for each. Type MapMovement in Filter messages..., then tick MapMovementRequest and MapMovementEvent. Replace the filter with ChatChannelMessage, and tick ChatChannelMessageEvent. If you turned on Live chat in Your first bot, it's ticked already. Click Apply. The button shows how many messages are ticked, and a notification confirms how many message types the bot now mirrors. Message Sent by What it says MapMovementRequest Your game Your character asks to walk along a path of cells. MapMovementEvent The server Someone on your map walks along a path: your character or another one. ChatChannelMessageEvent The server A chat message reaches you. 3. Play and watch Click Traffic. In Dofus, click a cell to walk there. A MapMovementRequest row marked Out appears, and a MapMovementEvent row marked In comes after it. Wait for other players to move on your map: each of their walks adds a MapMovementEvent row. When a chat message reaches you, a ChatChannelMessageEvent row appears, marked In. New rows arrive at the bottom, and the list follows them while you're at the bottom. Pause freezes the list, but messages that arrive while it's on aren't kept. The colour of each row tells the kind of message: Network traffic explains them. 4. Read a message Click a MapMovementEvent row. It opens and shows every field of the message as JSON. Find cells: the path the character walks, as a list of cell numbers. Another field holds the id of the character that moves, which tells your own walks from other players'. Click a ChatChannelMessageEvent row and find content: the text of the message. Large numbers, such as ids, show as text in quotes. To keep one kind of message in the list, type name:MapMovementEvent in the search box above it. The Dofus protocol reference describes every message and field. 5. Tidy up The messages you chose stay selected with the bot, and Asterobot keeps passing them on to Asteroboard, until you untick them. When you no longer need them, untick them in Settings and click Apply again. Clear, on Traffic, empties the list, and removes the chat lines from the Console tab too. When you're done, quit Dofus, and click Disconnect if you want the bot to stop waiting. Where to go next Network traffic, for the search syntax and every part of the panel. Send messages by hand React to messages, to act on a message in a script of your own.

This tutorial takes a package from the marketplace on asterobot.net to your bot, and runs it while you watch what it does. It uses the MITM bot from Your first bot: set that one up first if you haven't yet. Caution A package acts as your character: it can send any message to the game server in your name. Read Trusting a package before you run one, and remember that using bots breaks Ankama's terms of use (Accounts and safety). 1. Pick a package Open the marketplace, https://asterobot.net/files/category/10-library/. Open the page of a package that interests you, and read what it does, what its author says it needs, and who published it. Copy the page's address from your browser. 2. Install it In Asteroboard, open Library Manager and click Download package. Paste the address in File ID or URL, then click Preview. Check the card. Official or Community tells whether asterobot.net marks the file as official, and Will install as gives the name and version the package will have in your library. Click Install. Package installed appears, and the package gets a row in Library Manager, along with its dependencies if it has any. If a message shows up instead, Install from the marketplace explains it. 3. Give it to your bot Bring your bot online: on its page, click Start waiting, then start Dofus, sign in and enter the game with your character. The status turns to Connected to game server. Open the bot's Settings tab. It opens on Bot configuration. Under Package, pick the package you installed, listed as name@version. Click Save settings. Asteroboard shows Settings saved, and the bot's header now shows the package. The bot keeps this package from now on, across restarts. Run a package shows the other ways to choose one. 4. Change its settings Still on Settings, click Package settings, next to Bot configuration. The first card belongs to your package, and it's open. Its fields and their descriptions come from the package. Change a value. Not applied appears on the card's title. Click Apply. A notification confirms that the package's settings are applied. If the section says "This behavior declares no settings and no actions.", the package has nothing to adjust: go on to the next step. Package settings and actions covers every kind of field, and what happens when a value is refused. 5. Play and watch In the bot's header, click Play. It turns into Stop: the package's script is running. Open the Console tab. Lines from the Asterobot and Script sources appear as they're written. To follow the script alone, keep only Script ticked under Sources. Play as usual, or let the package do its job, and follow the console. Settings you apply while the script runs reach it straight away, without a restart. Whether it acts on them at once depends on how the package is written. If Play stays greyed out, the bot isn't connected to a game yet. If Couldn't start the behavior appears, or the alert The behavior stopped with an error shows up at the top of the page, see Run a package. When you quit Dofus, the relayed session ends and the script stops with it, with The behavior stopped with an error. Click Play again the next time you're in the game. 6. Stop Click Stop in the bot's header. The script ends and the bot stays connected: your game carries on as usual. When you're done playing, quit Dofus. The bot goes back to Waiting for your game client. To stop it waiting, click Disconnect. Next time, click Start waiting, enter the game and click Play: the bot still has the package and its settings. Where to go next Update packages, when the author publishes a new version. Console, for everything the console can filter and copy. Developer docs, to write a package of your own.

This tutorial finds where a resource grows, using the world map of a game version, then opens the maps of that region. It takes a few minutes and needs no bot. You only need a Dofus version that's downloaded and extracted in Game Manager: Download a game version sets one up. 1. Open the world map In the sidebar, open Game Manager. On your Dofus version's row, click the game's name or Inspect. The version's Game page opens. Open the Maps tab. It starts on the World view. In the page's header, set Language to the language you know the resource's name in. 2. Search for the resource Click the search box, "Search for a monster, resource, item...", and type the start of the resource's name. Each word you type matches the start of a word in the name. Results appear as buttons while you type. A resource is an item: its button shows its name, the table it comes from, items, and its number after #. Two records can share a name, and the number tells them apart. Click the resource. The world map highlights the regions where the resource can be found, and a button above the map shows its name with the number of highlighted regions. Click that button later to remove the highlight. Two things to know about the highlight: It covers the regions where the resource is gathered, and also the regions of the monsters that drop it. Step 3 tells them apart. Regions on another world map, or without an outline, can't be highlighted. They're listed after "Also in:", and clicking one shows it in the region panel. When the button says the resource "appears on no region here", look at "Also in:", or pick another world map in the list at the top left. 3. Check a region Click a highlighted square. The region panel under the map describes its region. Look at Harvestables, with its count. If the resource is in that list, it grows in this region. Point at it to read "Gathered with" and the job that gathers it. If it isn't there, look at Drops: the region is highlighted because one of its monsters drops the resource. Note the region's Level badge, and whether it has a Zaap button, which opens the map of the zaap that serves the region. The game data lists resources by region, not by map or by cell, so the panel can't say on which maps of the region the resource grows. Its note, "Gathered on the maps of this area.", is a reminder of that. 4. Walk through the region's maps In the region panel, click the button that opens its maps, such as Open the 12 map(s). The Map view opens on the first map of the region. Under View, keep Terrain. Cells the game marks for harvesting take the Harvest colour of the legend, and Summary, under the map, counts them as Harvest cells. Under Layers, check that Interactive is on: it puts a dot on each cell where an interactive element stands. Click the arrows on the sides of the map, or press the arrow keys, to move to the neighbouring maps. To go back to the world map, click the button that shows the map's coordinates, such as Show at [4, -19] on the world map. Neither the cell colours nor the dots say what stands on a cell: the map data doesn't name the resource of each spot. They show you where to look, and the game shows the rest once you're there. Tip Click Split at the top of the tab to keep the world map next to the map you walk through, and turn on Follow the map so the world map stays centred on it. Where to go next World map and Map viewer explain everything these views show. Game data shows a resource's full record, which the "Open in game data" button next to each search result opens.

When something is broken and nothing else helps, a reset puts part of Asterobot or Asteroboard back in a clean state. Every reset deletes something for good, so start with the smallest one that can fix your problem. The resets below go from the lightest to the most drastic. Choose a reset Problem Reset Section Asteroboard shows an old version, or behaves oddly after an update Reset offline data Reset offline data Asteroboard's language, colors or layout are wrong Reset preferences Reset preferences A setting you changed broke something That setting's reset, or Reset all Asterobot's settings Asterobot won't start because of a setting Edit config.toml, or run config reset Asterobot won't start because of a setting One game version is broken, or the disk is full Verify files, Re-extract data, Uninstall, Delete or Remove all chunks Game versions Every game version at once cache reset cache reset One bot, account or package is broken, or Asterobot uses the wrong asterobot.net account Remove that one thing One thing at a time Everything, as on a new computer Delete Asterobot's folders Start completely over In your browser Asteroboard keeps a few things in each browser you use it in. Both of these buttons are on Preferences, in the Danger zone section, and neither touches Asterobot: your bots, accounts, packages and settings stay as they are. Your browser asks you to confirm each one, then the page reloads. Reset offline data Deletes the copy of Asteroboard your browser keeps to open quickly and to work offline, then downloads Asteroboard again, which needs an internet connection. Click Reset offline data. Confirm "This clears all offline data cached by Asteroboard and reloads the page. Continue?" It keeps your preferences and your Server URL. The button is greyed out when your browser can't run Asteroboard offline at all. If the reset fails, Asteroboard shows Couldn't reset offline data, with "Try again, or clear this site's data from your browser's settings." Reset preferences Puts Asteroboard's language, color mode, colors, radius and sidebar layout back to their defaults, and the language of game texts on the Game page back to following Asteroboard's language. Click Reset preferences. Confirm "This resets language, appearance and dashboard layout preferences back to their defaults and reloads the page. Continue?" It keeps the Server URL, the level buttons of Server > Console, and a few other choices such as the world map layers and the music volume. Preferences compares the two buttons. To remove everything Asteroboard stored in a browser, the Server URL included, clear the site data of asteroboard.asterobot.net in that browser's settings. Afterwards, open Asterobot's own address, http://127.0.0.1:8080 by default, to set the Server URL again. Asterobot's settings On Server > Config, you can reset one setting with Reset to default at the end of its row, one group with the button in its card's header, or every setting you changed with Reset all, which asks Reset every modified setting? first. A reset puts the default back and removes the value from config.toml. Settings marked Restart required take their default at the next start. Warning Once Asterobot is signed in to asterobot.net, its sign-in is a modified setting, website.token. Reset all, or resetting the website group, signs Asterobot out, and you'll have to confirm a new sign-in code. Your bots, Ankama accounts, packages and game versions are kept. The Config page explains each button. Asterobot won't start because of a setting When a setting keeps Asterobot from starting, such as a server.listenAddress it can't listen on, Asteroboard can't reach it to change anything. Fix config.toml instead: Open config.toml with a text editor. Files and folders shows where it is. Remove the line of the setting that causes the problem. A setting without a line takes its default. Save the file and start Asterobot. If you don't know which setting it is, use config reset. config reset config reset empties config.toml and puts every setting back to its default. Stop Asterobot, if it runs. Open a terminal in the folder where you put Asterobot and run: ./asterobot config reset On Windows, in PowerShell: .\asterobot.exe config reset If you start Asterobot with --config-dir or ASTEROBOT_CONFIG_DIR, give the command the same folder. When it asks Put every setting back to its default value? [y/N], type y and press Enter. It prints Resetting the configuration.. then All configuration settings have been reset to their default values. Start Asterobot, and confirm the asterobot.net sign-in code it asks for. Any other answer to the question stops the command, and nothing changes. It deletes It keeps Every setting you changed Your bots The asterobot.net sign-in Your Ankama accounts and their sign-ins server.listenAddress, server.basicAuth and server.tls, which go back to accepting this computer only, without a password Your packages Your MITM ports, hosts and Dofus folder, and your automatic sign-in settings Your game versions and their game data If you had clicked Log out before, that choice goes too: Asterobot asks you to sign in again by itself. Command line has more about the command. Game versions These actions are in each version's menu in Game Manager, except Remove all chunks, which sits above the table. From the gentlest: Action It deletes It keeps Verify files The files that don't match, which it downloads again Everything else Re-extract data The game data, which it builds again from the files The files Remove extracted data The game data, the extracted pictures and the extracted music The files and the row Uninstall The downloaded files The row and the game data Delete The files, the game data and the row The shared chunks Remove all chunks Every stored chunk, for every version Every version's files and game data Warning None of these checks whether a bot uses the version. A bot that signs in on its own can't connect with a version that isn't ready, and a bot whose version was deleted is skipped when Asterobot starts. Move your bots first, as When Dofus updates shows. Manage game versions explains each action. cache reset cache reset deletes Asterobot's whole cache folder, then creates it again, empty. Stop Asterobot with Ctrl+C in its terminal, or with Shutdown server. It must not run during the reset, and stopping it normally puts back the line it may have changed in your Dofus folder, which it can't do once its copy of the game is gone. Open a terminal in the folder where you put Asterobot and run ./asterobot cache reset, or .\asterobot.exe cache reset in PowerShell on Windows. If you start Asterobot with --cache-dir or ASTEROBOT_CACHE_DIR, give the command the same folder. When it asks Delete <folder> with everything in it? [y/N], check that <folder> is the cache folder you mean, then type y and press Enter. It prints Resetting the cache.. then All cache have been removed. Start Asterobot, then download and extract the game versions your bots use. It deletes It keeps Every game version, with its files and game data The settings folder: config.toml and the asterobot.net sign-in Every stored chunk The data folder: bots, Ankama accounts and library Ankama's download lists The screenshots of failed automatic sign-ins Bots set to a deleted game version are skipped when Asterobot starts, until you download and extract that version again. Command line has more about the command. One thing at a time To remove Where What goes What stays A bot Delete bot in the bot's menu in Bot Manager, then Yes, delete The bot, its settings, package settings, message selection, console history and MITM attachment Its Ankama account An Ankama account's sign-in Disconnect in the account's menu in Account Manager Its tokens. Asterobot asks Ankama to revoke them, and forgets them either way The account and its stored password An Ankama account Remove in the account's menu in Account Manager, then Yes, remove The account, with its password and tokens. Nothing is revoked with Ankama Its browser profile, its last failure screenshot, and the bots that use it A package version Remove in the package's menu in Library Manager, then Yes, remove That version Other versions, the packages it depends on, and the bots set to it The asterobot.net sign-in Log out in the account button's menu Asterobot's sign-in. It stays signed out, even after a restart, until you click Sign in Everything else What follows from each: A bot that used a removed account can't connect, and it's skipped at the next start until the account is back with the same Login ID. See Account status and actions. A bot set to a removed package version can't start its script until you move it to another version. See Manage your library. While Asterobot is signed out, it can't add bots or download packages, and it skips every saved bot when it starts. See Your account. A deleted bot only comes back if you add it again from scratch. See Disconnect, delete and restart. Start completely over Deleting Asterobot's folders takes it back to its first launch. Nothing is stored next to the program, so deleting or replacing the program file alone changes nothing. Caution These folders hold your Ankama passwords and tokens and your asterobot.net sign-in. Deleting them is final: back up anything you might need first (Files and folders). Stop Asterobot with Ctrl+C in its terminal, or with Shutdown server on Server > Status, so it puts back the line it may have changed in your Dofus folder. Once its cache folder is gone, it can no longer read the original line back. Delete the folders you want to reset. Files and folders shows where each one is on your system. Start Asterobot. It creates the folders again, empty, and asks you to sign in to asterobot.net, as on its first launch. What each folder takes with it: Folder Deleting it loses Settings config.toml: every setting you changed, and the asterobot.net sign-in Data bots.toml with every bot, accounts.toml with your Ankama accounts, your library of packages, the HTTPS certificate and the sign-in browser profiles Cache Every game version with its game data, the stored chunks, Ankama's download lists and the screenshots of failed sign-ins If you start Asterobot with folder options or their environment variables, the folders to delete are the ones they name (Command line). Asteroboard's Server URL and preferences live in each browser, not in these folders. Clear them as described in In your browser if you want them gone too. Where to go next Files and folders Command line Getting help

Bots and the Game page need a game version that's downloaded and extracted, and either step can go wrong, from a download that won't queue to an extraction that fails without saying why. Download a game version and Extract game data explain how both work. Couldn't queue the download Asteroboard shows Couldn't queue the download when you click Download: Asterobot refused the request, or couldn't be reached. Asteroboard isn't connected. Look for a red dot on Preferences in the sidebar, and see Asteroboard can't connect. latest can't be resolved, because the game, platform or environment you typed isn't on Ankama's list. Pick the values from the suggestions, or keep the defaults dofus, windows and dofus3. Asterobot can't reach Ankama. Check the internet connection of the computer where Asterobot runs, then click Check for updates in the dialog. Stays on Queued Only one download or file verification runs at a time, whatever the game or the version. Look at the other rows of Game Manager: when one shows Downloading or Verifying, yours starts after it. Extractions don't wait in that queue. Failed The download stopped. Point at the info icon next to Failed to read the reason. The reason What to do Mentions the network or Ankama's servers Open the version's menu and click Retry. The download resumes where it stopped and keeps the finished files. Contains invalid file filter or invalid fragment filter A filter isn't a valid regular expression. Click Retry and correct it in the dialog, or put the default File filter (regex) back. Is 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. Says there's no space left on the disk Asterobot doesn't check free space before downloading. Free some space as Free disk space explains, then click Retry. Installed, but Not ready The Status column says Installed and the Ready column says Not ready. A version is only ready for a bot once the files a bot needs are in and its game data is extracted. The causes: Asterobot was stopped during the download. When it starts again, the version shows Installed although files are missing. The version was downloaded with a narrower File filter (regex) than the default. It was uninstalled. Uninstall deletes the files and keeps the status Installed. It isn't extracted. Look at the Extracted column. Open the version's menu and click Download more files. Keep the default File filter (regex) and confirm. Only missing files are downloaded. Once it's done, if the Extracted column doesn't say Extracted, click Extract data in the same menu. Click Check if ready for bot. Asteroboard answers Ready for bot or Not ready for bot. The version's Game page tells you which half is missing: its Required files card says Missing when files are. See Ready for bot. Stays Not extracted after the download Asteroboard is what starts the extraction when a download ends with Extract data after downloading checked. If you closed or reloaded Asteroboard before the end, or the box wasn't checked, nothing extracts. The box also comes back unchecked the next time you open the download dialog after starting a download. Open the version's menu and click Extract data. Extraction failed Asteroboard doesn't show why. The reason is in Asterobot's log, on a line starting with Failed to extract game data, in the terminal or on Server > Console. The usual cause is a missing file: Open the version's Game page, with its name or its Inspect button in Game Manager. If the Required files card says Missing, click Download needed files and wait for the download to finish. Back in Game Manager, click Extract data in the version's menu. Extraction only works for Dofus for Windows. A version of another game or platform fails however many times you try. Extraction failed stays until you extract again or restart Asterobot, which then shows Extracted or Not extracted from what's on disk. Couldn't start extraction The request didn't reach Asterobot. Check that Asteroboard is connected, then try again. Extract data isn't offered while that version is already extracting. Bot's game version isn't ready yet A bot that signs in on its own refuses to connect with a version that isn't Ready for bot, and Add a bot doesn't accept one. Get the version ready as described in Installed, but Not ready. See also Bot doesn't connect. Missing required files in a bot's settings On the Game tab of Add a bot, or on a bot's Settings tab, Missing required files means the version lacks files a bot needs. Click Download needed files next to it. When the badge turns to Ready, click the extraction badge if the version isn't extracted. If the download can't start, Asteroboard shows Couldn't download the required files. The newest version doesn't show up In the Version suggestions. Click Check for updates at the top of the download dialog, so Asterobot fetches Ankama's list again. latest downloads an older version. When Ankama can't be reached, Asterobot resolves latest from the last list it saved. Check the internet connection, then use Check for latest version in a version's menu. It answers Up to date or A newer version is available, with Ankama's latest version number. Couldn't check the latest version means Asterobot couldn't ask. A version downloaded with the gamemanager download command only appears in Game Manager after Rescan or a restart. If the rescan fails, Asteroboard shows Couldn't rescan. That command never extracts: click Extract data afterwards. Uninstall, Delete and the chunk tools Message What it means What to do Couldn't uninstall or Couldn't delete Asterobot refused, for example because a download or a verification of that version started in the meantime. Wait for it to end, then try again. Couldn't remove the chunks A download, a verification or a chunk check started before your click reached Asterobot. Remove all chunks is greyed out while one runs. Wait until nothing downloads, verifies or checks chunks. Couldn't start the chunk check The request didn't reach Asterobot. Check that Asteroboard is connected. Chunk check failed, with a reason The check stopped. Read the reason, then click Check all chunks again. Couldn't start verification Verify files couldn't be sent. Check that Asteroboard is connected. Verify files isn't offered for a Failed version: use Retry. The disk fills up Asterobot doesn't check free space before a download, and game versions are by far the largest thing it stores. From the gentlest to the most drastic: Remove all chunks, then Uninstall or Delete the versions you don't use. See Free disk space, and read Reset and start over before you reach for cache reset. Music Music is a separate download, from the Game page's Music tab. If it can't start, Asteroboard shows Couldn't start the download or Couldn't start the extraction with the reason, and Couldn't load the music when the tab can't read it at all. See Music. Version mismatches In MITM mode, the version in Game Manager must be exactly the one you play, or the bot refuses to wait: see MITM problems. A version marked Different version in the Compatibility column downloads and extracts normally, but bots may not work on it yet: see When Dofus updates. Where to go next Manage game versions Reset and start over

A package can fail at several moments: while you install it, when a bot starts it, or while it runs. If you write packages, Error messages in the developer docs lists every text with its cause. Find the reason first Several package messages come without their reason, which is always somewhere else: Where What you find there The behavior stopped with an error, under the bot's header The full error of a script that started, then failed. Copy puts it on your clipboard. The bot's Settings tab, under Package settings Couldn't read this package's settings, with the reason, when the bot's package can't be loaded at all. The editor of a local package The error badge in its top bar, such as "3 error(s)", which counts the problems across every file of the package. The bot's Console tab What the script itself writes, warnings included. Couldn't start the behavior You clicked Play, and the script couldn't even start. The notification gives no reason, and the bot's page shows no alert. Check that the bot is Connected to game server. Load a package and play it on a bot that isn't connected loads the package, then shows this message. Open the bot's Settings tab and click Package settings. When the package can't be loaded, Couldn't read this package's settings shows the reason. Find that reason in Reasons a package can't load. Three other messages work the same way, without a reason: Couldn't load the selection after loading a package, Couldn't switch version after picking another version in the bot's header, and Couldn't run the package after Run in the editor. Look under Package settings for each. Reasons a package can't load requires asterobot The text reads like package "<name>" requires asterobot <range>, running <version>. The package states which versions of Asterobot it works with, and yours isn't one of them. Library Manager marks it Incompatible, and its name turns orange in the bot's header. If the range asks for a newer Asterobot, update it: see Updating Asterobot. If another installed version of the package is compatible, move the bot to it: see Switch to another version. For a marketplace package, click Check for updates in Library Manager: a newer version may support your Asterobot. Otherwise, contact the author. has an invalid compatibleVersion constraint means the author wrote that range wrong. Only the author can fix it. package source integrity mismatch The files of a package installed from the marketplace no longer match the ones Asterobot downloaded, for example because they were edited by hand. Asterobot refuses to load it. In Library Manager, open the package's menu, click Remove, then Yes, remove. Install it again from the marketplace, with the same file link. See Install from the marketplace. Move the bot back to that version if it changed. Trusting a package explains the check. read package or is not installed The package, or one of the packages it depends on, isn't in your library at the version the bot needs. The text names the missing one, as in read package <name>@<version> sources:. It happens after a package or a dependency was removed, or when installing a dependency failed. For a marketplace package, install it again from the marketplace: Asterobot downloads the dependencies it lacks along with it. If you removed that version on purpose, move the bot to a version that's installed. parse module or resolve A text that contains parse module or resolve means the package's code has an error: a syntax mistake, or an import that points at nothing. For a package from the marketplace, check for an update, and tell its author, with the full text. For a local package, open it with Edit code: the error badge leads you to the problem. Error messages explains each text. The behavior stopped with an error The script started, then failed. The alert shows its full error, and the Behavior column of Bot Manager says Failed. The bot stays connected, and a relayed game keeps playing. These are the texts players meet most: The text contains What it means What to do Game session closed The game connection closed while the script ran: you quit Dofus, the bot was disconnected, or the connection dropped. Bring the bot back online, then click Play. IdentificationRequest.token: unknown protobuf field The script was built from an old example that sends the wrong fields to enter the game. Update the package, or ask its author to. Authors: see Identify and run. JavaScript execution deadline exceeded The script worked for more than 250 ms without a pause. Tell the author. behavior event-loop queue overflow The script couldn't keep up with the messages it receives. Tell the author. unhandled Promise rejection: An error in the script that nothing caught. Tell the author, with the full text. behavior requested Game disconnect The script disconnected the bot on purpose. Nothing, if the package is meant to do that. the game engine is not available: Asterobot couldn't read the game's messages. See When Dofus updates. To start the script again, click Play. If the same error comes back, the package needs a fix. Installing from the marketplace Message What to do Not a valid file ID or asterobot.net file URL. Copy the address of the file's own page on asterobot.net, or its number, not the address of the category. File not found, or you don't have permission to view it. Check the address. Then check the account button at the bottom of the sidebar: Asterobot has to be signed in to asterobot.net to ask about a file. You don't have permission to download this file. Your asterobot.net account isn't allowed to download this file, and nothing in Asterobot changes that. Couldn't install the package The download or the installation failed, without a reason. The file may not be a package, have more than one attachment, weigh more than 32 MiB, or have a dependency that can't be installed. When a dependency failed, the package itself may already be in your library without it, and it won't start. Install from the marketplace has the details. Updating Couldn't check for updates: the check didn't go through. Check that Asteroboard is connected and that Asterobot is signed in to asterobot.net, then try again. Couldn't install the update: the same causes as a first installation, and no reason either. No Update to button, although the author published a new version: nothing is checked by itself, so click Check for updates. A version lower than yours isn't offered, and a file that can't be read on asterobot.net any more is skipped without a message. See Update packages. Importing and removing Couldn't import the package, without a reason: the file may not be a .zip, have no index.js, weigh more than 32 MiB, or contain an invalid asterobot.json. The name messages of the import dialog are in Manage your library. Couldn't remove the script: nothing was removed. Try again. After you removed a version, a bot set to it keeps running its script until the script stops, then gets Couldn't start the behavior at the next Play. Move the bot to another version. Package settings and actions These appear on the bot's Settings tab, under Package settings: Message What it means What to do Couldn't apply the settings, with a reason A value doesn't fit what the package expects. Nothing from the form was saved. Correct the value the reason names, then click Apply again. Couldn't start the action, with no behavior is running on this bot Actions only run while the package plays. Click Play, then the action. Couldn't start the action, with another reason An argument doesn't fit, or the running script doesn't have that action. Correct the value, or click Stop and Play so the running script matches the package. The action's name followed by failed The action's own code failed. The script keeps running. Tell the author. Action buttons stay greyed out with "The bot has to be playing a behavior before an action can run." while no script runs. See Package settings and actions. Contact the author Only its author can fix the code of a marketplace package. In Library Manager, click the package's name. In its details, click View on asterobot.net, in the Source row. It opens the file the package came from. Contact the author from there, or ask on the forum at https://asterobot.net/forums/. Include the full error text copied with Copy, the package's version, your Asterobot version from Server > Status, and the bot's game version. Never include your config.toml, a token or a password. Getting help lists what must stay private. Where to go next Run a package Manage your library Error messages, for script authors

In MITM mode, short for man-in-the-middle, a bot relays the Dofus client you play: Asterobot points your game at itself by changing one line in your Dofus folder, then passes everything on to Ankama. Most things that go wrong here show no reason in Asteroboard, so this page lists the causes to check, in the order they usually happen. MITM mode explains how the mode works. Couldn't put the bot into waiting Asteroboard shows Couldn't put the bot into waiting when you click Start waiting, or Bot added, but it couldn't be connected when you add a bot with Wait for my game client. The bot stays Disconnected. Asterobot refused, but the reason isn't shown in Asteroboard or written in the log, so go through the causes: Cause What to check The Dofus you play isn't the version Asterobot downloaded In your Dofus folder, open Dofus_Data/StreamingAssets/version and read the Version= line. It must be exactly the version the bot uses in Game Manager. When your bots use different versions, Asterobot may compare your game with any of them, so keep every bot on the version you play. Asterobot can't read the version file botmanager.mitmGamePath, on Server > Config, must be the Dofus folder itself, the one that contains Dofus_Data. The version file has no ConfigUrl line The folder in botmanager.mitmGamePath isn't a normal Dofus install. 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 described in Put the line back by hand, or click Download more files on the bot's game version with the default filter, which includes the version file. Another program uses port 5555 or 5556 Close that program, or change botmanager.mitmSignInPort and botmanager.mitmSessionPort, then restart Asterobot. botmanager.mitmSignInPort and botmanager.mitmSessionPort have the same value Give them two different ports, then restart Asterobot. Then click Start waiting again. After an Ankama patch, the version is the usual culprit: the Ankama Launcher updated your Dofus, and Asterobot still has the previous version. Download the new one and move the bot to it, as When Dofus updates explains. The bot waits, but your game never reaches it The bot shows Waiting for your game client while you play, and nothing arrives. Check these in order. Asterobot didn't change the line When the first bot starts waiting, Asterobot's log, in the terminal and on Server > Console, shows Pointed the played game at Asterobot. A second waiting bot doesn't print it again, so look further up if another bot was already waiting. When the line never appears, botmanager.mitmGamePath is empty. On macOS it always is at first, since there's no default, and elsewhere it's empty when Dofus wasn't in the Ankama Launcher's usual folder as Asterobot started. The bot waits anyway, but nothing is edited and your game never comes. On Server > Config, set botmanager.mitmGamePath to your Dofus folder, the one that contains Dofus_Data. Click Disconnect on every waiting bot, then Start waiting again. Check that the log now shows Pointed the played game at Asterobot. See Where Asterobot looks for your Dofus folder. Dofus was already open A Dofus started before the bot was waiting doesn't go through Asterobot. Close it, and start it again from the Ankama Launcher. A game client signed in that no bot is waiting for Your game went through Asterobot, but no waiting bot took it, and it went straight to Ankama. Each bot takes sessions by Ankama account: a bot that relayed an account once only takes that account's sessions from then on. A bot without an Ankama account stays attached to its first account for good, even after a restart, and Asteroboard has no way to detach it. Play with the account the bot is attached to. Its Information tab shows the account once a session has arrived. To relay another account, add another bot without an account and click Start waiting on it. See Which bot gets which game session. Dofus runs on another computer Asterobot can only edit a Dofus folder on its own computer. For a game on another computer, you change the line there yourself and open Asterobot's ports: see MITM across machines. Dofus can't sign in Asterobot isn't running While a bot waits, the ConfigUrl line of your Dofus folder points at Asterobot. If Asterobot then stops without closing properly, for example because its terminal window was closed, the line stays that way and Dofus can't sign in at all. Start Asterobot again. As it starts, it puts the line back and prints Restored a game install left pointing at Asterobot by a previous run. Start Dofus. Asterobot reads the original line from its own copy of the game, which it finds through your bots. If it doesn't print that line, for example because every bot was skipped as it started, or because botmanager.mitmGamePath is empty, put the line back by hand as described below. A bot that starts waiting also repairs the line first, and prints Recovering a ConfigUrl left pointing at Asterobot by a previous run. Stopping Asterobot with Ctrl+C or Shutdown server puts the line back at once, and so does disconnecting the last waiting bot. HTTPS or a password is set MITM mode doesn't work while server.tls is on or server.basicAuth holds anything, even with Dofus and Asterobot on the same computer. The line Asterobot writes always tells Dofus to fetch its connection settings over plain http://, without a password. With HTTPS, Asterobot's port only answers HTTPS requests, and with basic auth it asks for a password Dofus can't give. Either way, Dofus doesn't get its connection settings and can't sign in through Asterobot. On Server > Config, turn off server.tls and click Reset to default on server.basicAuth. Restart Asterobot. On the computer where Asterobot runs, open http://127.0.0.1:8080, so Asteroboard uses the plain address again. Click Start waiting, then start Dofus. To use Asteroboard from another device and keep MITM mode, use an SSH tunnel instead of HTTPS: see Asterobot on a remote machine. Failed to fetch the real game configuration When Dofus asks Asterobot for its connection settings, Asterobot fetches Ankama's real ones and changes the sign-in address in them. This error in the log means it couldn't reach Ankama for that. Failed to reach the Ankama login server means the same for the sign-in itself. Check the internet connection of the computer where Asterobot runs, then start Dofus again. Put the line back by hand When Asterobot can't restore your Dofus folder, you can do it yourself: Close Dofus. Find Asterobot's own copy of the same game version, in Asterobot's cache folder, under game/dofus/dofus3/windows/ followed by the version number. Files and folders shows where the cache folder is. Asterobot never edits that copy. If the version isn't there any more, download it again in Game Manager first. Open that copy's Dofus_Data/StreamingAssets/version file and copy its ConfigUrl= line. In your own Dofus folder, open Dofus_Data/StreamingAssets/version with a text editor, and replace its ConfigUrl= line with the one you copied. Leave the other lines as they are. Save the file and start Dofus. A ConfigUrl line that ends with /botmanager/mitm/dofus3.json is one Asterobot wrote. The line Asterobot changes explains it. Your game is disconnected as it reaches the bot You sign in, and the game disconnects as it enters. Asterobot's log shows Failed to relay a game session, followed by the reason. The reason mentions dial the real game server: Asterobot couldn't reach the game server. Check the internet connection and the firewall of the computer where Asterobot runs. Right after an Ankama patch, your release of Asterobot may not support the new version yet. See When Dofus updates. Your game is disconnected while you play The bot carries your session, so whatever ends the bot's session ends your game: Disconnect on the bot, Delete bot, or stopping Asterobot. A package that closes the game connection. Click Stop and play without it to find out. Another Dofus signing in with the same Ankama account: the new session replaces the one the bot was carrying. When you quit Dofus, the bot goes back to Waiting for your game client, and a running script stops with The behavior stopped with an error. That's expected: press Play again once your game is back. Scripts on a relayed session Refused to forward a message that would re-authenticate a relayed session This warning appears in the bot's Console tab. The script sent IdentificationRequest, the message a Full socket connection script sends to enter the game. Your Dofus already did that, and sending it again would end your session, so Asterobot didn't forward it. The script keeps running. When the script waits for an answer to that message instead, it gets mitm relay refuses to identify: this Game session was already authenticated by the real DOFUS client, and stops with The behavior stopped with an error unless it handles the error. A connection script should only identify on its first launch, when launch.reason is "initial", which never happens on a relayed session. If you wrote it, see Identify and run. If you didn't, tell its author. interceptor failed: A package can change or block the messages between your game and the server. This error line in the bot's console means one of the functions doing that threw an error or ran for more than 250 ms: the message went through unchanged, and the script keeps running. A function written as async behaves differently: it always lets the message through, and when it fails, the whole script stops with unhandled Promise rejection: in The behavior stopped with an error. Either way, the package has a bug. Tell its author, or see Intercepting if it's yours. What the bot shows makes no sense When your Dofus and the bot's game version differ, Asterobot reads your game's messages with the definitions of another version: names, fields and items can look plausible and still be wrong. On a single computer, Asterobot refuses to wait in that case. Across machines, nothing checks it: compare the Version= line on the Dofus computer with Game Manager after every Dofus update. Where to go next MITM mode MITM across machines Package errors

A Full socket bot, which Asterobot signs in on its own, can get stuck anywhere from Add bot refusing to a bot that shows Connected to game server and still never enters the game. For a bot that waits for your Dofus client, see MITM problems. Find the reason When a connection fails, Asteroboard shows Couldn't connect the bot with the reason, and the same reason stays in a Couldn't connect this bot alert under the bot's header, on every tab. Copy puts it on your clipboard. The bot's Console tab narrates each stage of the connection, so its last lines tell you where it stopped. Two failures come without any reason: Couldn't add the bot, and a bot that disappears from Bot Manager. Their causes are listed below. Couldn't add the bot Asterobot refused the new bot, and Asteroboard doesn't say why. The dialog stays open with your choices. The causes: The name is already taken by a bot in Bot Manager. The account already belongs to another bot. An Ankama account can only belong to one bot. Asterobot couldn't confirm your asterobot.net account, for example because it isn't signed in. See this installation is not entitled to start bots. Your asterobot.net account's bot limit is reached. Every bot listed in Bot Manager counts, connected or not. Check the account button at the bottom of the sidebar: it should show your asterobot.net name. Check that no bot in Bot Manager has the same name, and that no other bot uses the account. If you have many bots, delete one you no longer use. Click Add bot again. Warning In a few other failures, the bot was added although the dialog stays open, for example when a connection takes longer than 90 seconds. Look at Bot Manager before you click Add bot again: with an empty name, a second bot would be added. See Add a bot. Add bot stays greyed out The dialog waits until everything it needs is set, such as a game version that's ready, a signed-in account for Sign in now, which is selected when the dialog opens, or a server for Always this server. Add a bot lists every condition. Connect is greyed out The bot isn't Disconnected. While the bot connects, waits or is connected, the header shows Disconnect instead. Click it first. The bot has no Ankama account. The tooltip says "This bot has no Ankama account to sign in with." It can only relay a game you play, in MITM mode. To let it sign in on its own, pick a signed-in account on its Settings tab while it's disconnected. Bot's game version isn't ready yet Asteroboard shows Bot's game version isn't ready yet, with "Its game files or extracted data aren't fully ready - check the Game Manager for this version." The reason in the alert is this bot's game version is not ready to connect yet. Asterobot checks this before anything goes out to the network. Open Game Manager and find the bot's version. Its Ready column says Not ready. If files are missing, open the version's menu and click Download more files, with the default filter. Once the download is done, click Extract data in the same menu, and wait for Ready for bot. Click Connect again. Game download problems helps when the download or the extraction fails. Reasons a connection fails 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. Asterobot checks this when you add a bot, change a bot's account or game version, click Connect, and when it brings bots back as it starts. Putting a bot in waiting for your Dofus client isn't affected. Look at the account button at the bottom of the sidebar. If it doesn't show your asterobot.net name, sign in as Sign in with asterobot.net explains. Make sure the computer where Asterobot runs can reach asterobot.net, and check https://status.asterobot.net. Click Connect again. If it keeps happening while Asterobot is signed in and online, ask on the forum at https://asterobot.net/forums/ or on Discord at https://discord.asterobot.net. this account's bot limit has been reached You already have as many bots as your asterobot.net account allows. Every bot in Bot Manager counts, disconnected ones included. Delete a bot you don't use any more, then try again. If the count looks wrong to you, ask on the forum or on Discord. ankama account authorization required The bot's Ankama account no longer has a working sign-in, and Asterobot couldn't renew it: Ankama refused the quiet renewal, and the account either has no stored password or its automatic sign-in failed. Open Account Manager and click Reconnect in the account's menu. Sign the account in. Sign-in problems helps if that fails. Click Connect on the bot again. account not found The bot's account was removed from Account Manager. The reason is followed by the Login ID. Add the account again with the same Login ID and sign it in, then click Connect. Or pick another signed-in account on the bot's Settings tab, while the bot is disconnected. identification was refused: account already connected elsewhere The account is already in the game: in Dofus, or through another bot, including a bot that relays your Dofus in MITM mode. Close the other session: quit Dofus, or disconnect the other bot. Wait a moment, then click Connect again. When the reason reads identification was refused: followed by something else, that's Ankama's own reason for refusing the account. Accounts protected by Ankama Shield or two-factor authentication can end here: see Shield and two-factor authentication. connect to login server: timed out waiting for a response The game's login server didn't answer within 30 seconds. Check the internet connection of the computer where Asterobot runs, and whether the game servers are in maintenance, then try again. server selection was refused: The login server refused the server the bot picked, with its own reason after the colon. Try again later, or set Server selection to Ask me each time on the bot's Settings tab and pick another server. connect bot to game server: The login stage worked, but the bot couldn't open its connection to the game server it was sent to. Check the internet connection and the firewall of the computer where Asterobot runs, then click Disconnect and Connect again. a connection attempt is already in progress A bot runs one connection attempt at a time, and a second one arrived, usually from another open Asteroboard tab. Wait for the first attempt to end, or click Disconnect and start again from a single tab. bot must be disconnected before starting a new login connection and this bot is relaying a session: stop it before signing in on its own are the same kind of refusal: the bot is already connected, or waiting for your game client. Click Disconnect first. After a Dofus update Right after an Ankama patch, a bot on the new version may not connect until your release of Asterobot supports it. When Dofus updates lists what you may see, including a reason that tells you to update Asterobot. Stuck on Connecting… An automatic Ankama sign-in is running. When the account's sign-in stopped working and a password is stored, Asterobot signs in again through the browser, which can take up to two minutes. Another account is signing in. Ankama sign-ins happen one at a time across all your accounts, so a bot waits for the one before it. The login server is slow. Each exchange with it has a 30-second limit, after which the connection fails with a reason. To give up, click Disconnect: it cancels the attempt at any stage. Stuck on Awaiting your answer The bot waits for you to pick a server in the Pick a server card, under its header. It asks when its Server selection is Ask me each time, when the server chosen with Always this server is offline or not open to the account, and when no server at all is online and open to the account. Asterobot sets no time limit on the question. Open the bot's page. A notification such as Bot "my-bot" needs your input has a Go to bot button that opens it. Click a server that isn't greyed out. If Asteroboard shows Couldn't send your answer, the server may have gone offline in the meantime: pick another one, or click Disconnect, then Connect. See Full socket mode. Connected to game server, but the bot never enters the game This is the most common surprise in Full socket mode. Connected to game server means the connection to the game server is open, nothing more. Asterobot doesn't identify the bot on the game server and doesn't pick a character: a connection script, a package the bot plays, has to do that. The status reads the same whether the script did its job or not. 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 need a script of your own: Identify and run shows the identification every Full socket script needs. Or use MITM mode, which needs no connection script. Go through these checks: Is a script running? The header shows the package and Stop while it runs, and the Behavior column of Bot Manager says Running. With No package selected, or Play still showing, nothing identifies the bot: load a connection script and click Play. See Run a package. Is the package a connection script? A package made for something else, such as logging the chat, doesn't identify the bot. Neither does the starter code New package creates. What does the bot's Console say? The script's own lines tell you how the identification went. Did the script stop? A The behavior stopped with an error alert under the header gives the error. With IdentificationRequest.token: unknown protobuf field, the script was copied from an old example that sends token and lang: it needs the identification block of Identify and run. If you didn't write the package, ask its author for an update. Package errors covers the other errors. The status goes back to Connected to login server The bot's game connection closed. The console shows Game connection lost, and the status stays on Connected to login server instead of Disconnected. A running script stops, with The behavior stopped with an error and a message that mentions Game session closed. Nothing reconnects by itself: Click Disconnect. Click Connect, and wait for Connected to game server. Click Play. If the connection drops again right after Play, read the script's lines in the bot's console to see what it sent. A bot disappeared from Bot Manager After Asterobot started. Asterobot skipped the bot, because its Ankama account or its game version is missing, because it couldn't prepare Ankama sign-ins, or because it couldn't confirm your asterobot.net account in its first seconds. In that last case, every bot is skipped. The terminal shows a warning starting with skipping bot restore:, with the reason. The bot's configuration is kept: fix the cause and restart Asterobot. See Disconnect, delete and restart. Right after you saved its settings. When Asterobot refuses a new account or game version, for example with this account is already associated with a bot, or can't confirm your asterobot.net account at that moment, the bot disappears until Asterobot restarts, and comes back with its previous settings. See Bot settings. Warning Don't add a new bot with the name of a bot that disappeared: it replaces the missing bot's saved configuration for good. Couldn't save the settings Asteroboard shows the reason under Couldn't save the settings. The ones you'll meet most are this account is already associated with a bot, when another bot uses the account you picked, and this installation is not entitled to start bots, covered above. Bot settings lists when Save settings stays greyed out. Where to go next States and controls Full socket mode Package errors

Asterobot deals with two sign-ins that have nothing to do with each other. It signs itself in to your asterobot.net account, with a code you confirm on the website, and it signs in the Ankama accounts your Full socket bots play with. A bot in MITM mode needs no Ankama sign-in in Asterobot: you sign in yourself, in Dofus. asterobot.net Sign in with asterobot.net explains how the code works when everything goes right. Clicking Sign in does nothing The account button stays on Sign in, and no link comes. Either Asterobot asked asterobot.net for a code and didn't get one, or your click never reached Asterobot. Asteroboard shows no message in both cases. Check that Asteroboard is connected: no red dot on Preferences in the sidebar. If there is one, see Asteroboard can't connect. Look in Asterobot's terminal, or on Server > Console, for the warning Failed to request a sign-in code, followed by the reason. Check that the computer where Asterobot runs can reach asterobot.net, and look at https://status.asterobot.net. Click Sign in again. Sign-in pending, but no tab opened Asterobot opens a browser tab by itself only for the first code after it lost its sign-in, and only on the computer where it runs. On a machine without a desktop, the terminal shows Failed to open the web browser instead. The code is waiting all the same. Click the account button, which reads Sign-in pending: it opens the sign-in link in a new tab, on the device you're using. Or copy the link from the terminal, on the line after Website sign-in required. Please visit this link to authorize access to your account; the app will continue automatically once authorized. Or turn on website.showQRCode on Server > Config, and scan the QR code the terminal shows with the next code. Sign-in was not completed in time; it will be offered again Asterobot stopped waiting for the code. Either nobody confirmed it within 15 minutes, or someone refused it on asterobot.net: both end with this same line. The account button goes back to Sign in, and Asterobot asks for a new code by itself within a few minutes. For a new code right away, reload Asteroboard. If the account button reads Sign in, click it. Open the new link and confirm the code within 15 minutes. This code is invalid or has expired. Check the code displayed on your device and try again. asterobot.net shows this when the code doesn't match a sign-in that's waiting: it was mistyped, it was already used, or it's more than 15 minutes old. Compare it with the code at the end of the link, after code=. A code has eight characters, digits and letters from A to F. Spaces, hyphens and small letters don't matter. If it's older than 15 minutes, get a new one as described in the previous section. Too many incorrect codes have been entered. Wait a few minutes and try again. 20 codes that didn't match any waiting sign-in were typed from your internet connection within 15 minutes, and asterobot.net stopped checking codes from that connection for a while. A code that doesn't have the right format doesn't count. Stop typing codes. Wait. You can type codes again at most 15 minutes after the last wrong one. Open the link from the account button instead of typing the code: it carries the code for you. The authorization was denied. You can close this page; your device will stop waiting shortly. Someone refused access to Asterobot on asterobot.net's authorization page. Asterobot stops waiting and prints Sign-in was not completed in time; it will be offered again. If that was a mistake, get a new code and allow access this time. Start again from your device. Three messages on asterobot.net end this way: This authorization link is invalid or has expired. Start again from your device. This authorization session has expired. Start again from your device. The authorization could not be completed. Start again from your device. The page was opened from an outdated or damaged link, the code expired while you were signing in, or asterobot.net couldn't finish. Open the newest link from the account button. If the button reads Sign in, click it for a new code. Website rejected the token asterobot.net stopped accepting Asterobot's sign-in, for example because it expired or was revoked. Asterobot forgets it and starts a new sign-in at once: after this warning, the terminal shows a new link, and the account button switches to Sign-in pending. Confirm the new code. Asterobot stays signed out after a restart After Log out on the account button, or Disconnect on the Account page, Asterobot doesn't sign back in by itself, not even when it restarts. Click Sign in on the account button. See Your account. Asterobot is signed in with the wrong account The code is confirmed for whichever account your browser is signed in with on asterobot.net at that moment. Log Asterobot out, sign in to the right account on the website, then click Sign in again. Your account goes through it. Signed in, but bots are refused When Asterobot is signed in and still refuses to add or connect bots with this installation is not entitled to start bots, see Bot doesn't connect. Ankama accounts Automatic sign-in and Manual sign-in explain both ways of signing an account in. Sign in automatically isn't in the menu Sign in automatically only appears for an account with a stored password. Open the account's menu, click Connect, then store the password with Store an Ankama password for automatic sign-in at the bottom of the dialog. See Manual sign-in. Automatic sign-in failed: ankama account authorization required After Automatic sign-in failed, the message starts with ankama account authorization required, followed by the address of Ankama's sign-in page, and ends by asking you to save a code to the configuration. Ignore that end: signing in happens in Asteroboard's dialog. The message is the same whatever went wrong, so find the real reason first. Open Asterobot's terminal, or Server > Console. Look for the warning Automatic Ankama sign-in failed, a person has to sign in. Its error starts with browser sign-in failed:, then says what happened. Find that text in the table below. 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 on its computer. Install Chrome, Chromium or Edge on the computer where Asterobot runs, or set its path in zaapmanager.browserPath. When that setting is filled in, Asterobot tries that browser only. ankama's sign-in page is asking for a human (bot challenge or captcha) Ankama's sign-in form didn't appear within 30 seconds, or the page wasn't the form Asterobot expects. See Ankama asks for a person. the request was refused by Ankama's edge network before Ankama saw it The browser got a block page before reaching 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 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 use 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. When you started the attempt with the dialog's own Sign in automatically button, the dialog also shows a picture of the page the browser was on when it gave up. It's often the fastest way to tell a captcha from a wrong password. Ankama asks for a person Ankama sometimes puts a challenge or a captcha in front of its form, and automatic sign-in doesn't try to get past it. You have two ways out: Sign in manually, in your own browser, from the account's sign-in dialog, below "or sign in yourself". This works wherever Asterobot runs. See Manual sign-in. Answer it in the sign-in browser's window, when Asterobot runs on a computer you're sitting at: turn off zaapmanager.browserHeadless on Server > Config, start the automatic sign-in again, answer quickly in the window that opens, then turn the setting back on. See Automatic sign-in. Sign in automatically seems stuck A sign-in through the browser can take up to two minutes. Ankama sign-ins also happen one at a time across all your accounts, so an account waits while another one signs in. Wait for the result before you click again. Couldn't start the sign-in Open Ankama sign-in failed. The first time Asterobot prepares an Ankama sign-in after starting, it fetches the current Ankama Launcher version from Ankama, and that step didn't work. Check the internet connection of the computer where Asterobot runs, then click Open Ankama sign-in again. Couldn't complete the sign-in - the code may have expired, try again Asterobot couldn't trade what you pasted for the account's sign-in. A code works once, and only for the sign-in it was created for. The common causes: The link was copied incompletely, or it's the address of Ankama's Congratulations page rather than the link behind its Continue button. The code was already used, or 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. Close the dialog. Open it again from the account's menu and click Open Ankama sign-in. Sign in, right-click Continue, copy the link address, which starts with zaap://login?code=, and paste it in Authorization code. Click Submit. The same message appears when Asterobot refuses tokens typed in Enter tokens manually instead (debug), for example an expiry date it can't read. Verification failed - try reconnecting Verify asked Ankama, the account's sign-in didn't work, and Asterobot couldn't repair it: the quiet renewal was refused, and a browser sign-in wasn't possible or failed too. Click Reconnect in the account's menu and sign in again. Couldn't refresh the token - try reconnecting Ankama refused Force refresh token, or the account has no refresh token. This action never falls back to the browser. Click Reconnect and sign in again. The account shows Signed in, and bots fail with ankama account authorization required Signed in only means Asterobot holds the account's tokens, not that Ankama still accepts them. When a bot connects, Asterobot uses the sign-in for real: it renews it quietly when Ankama allows, signs in again through the browser for an account with a stored password, and otherwise the connection fails with this message. In Account Manager, click Verify in the account's menu. If it fails, click Reconnect and sign in. Connect the bot again. When the account has a stored password and still fails, Asterobot's log gives the reason, as described in Automatic sign-in failed. Accounts with Ankama Shield or two-factor authentication These accounts can't be used in Full socket mode: automatic sign-in can't answer the extra step, and Full socket mode doesn't support them even when they show Signed in. Use MITM mode, where you sign in yourself in Dofus. See Shield and two-factor authentication. Where to go next Bot doesn't connect Account status and actions Getting help

Asteroboard has nothing to show on its own: every bot, setting and game version on its pages comes from your Asterobot. When the two can't talk, pages stay empty and nothing you click goes through. The causes below start with the most common. How to tell Where What you see A notification Server disconnected, with "Asteroboard lost connection to the Asterobot server. Retrying automatically…" The sidebar A pulsing red dot on Preferences Server > Status A red dot and Disconnected, or an amber dot and Connecting… while Asteroboard tries Preferences, in the Server section The Disconnected badge next to Test connection A bot's page "This bot isn't registered (or was removed)." with "It may have been removed, or the server it lives on isn't reachable." Asteroboard tries to reconnect by itself, once a second, for as long as the page is open. It shows Server disconnected once when it loses Asterobot, not at every attempt, and Server connected once it's back. You don't need to reload the page. To check right now, open Preferences, go to the Server section and click Test connection. It sends one request to the address in Server URL: Server reachable, with a line such as "Round-trip latency: 12ms": Asterobot answered. If the badge didn't say Connected yet, Asteroboard reconnects at once. Server unreachable: nothing answered at that address. Read on. Asterobot isn't running This is the most common cause. Asterobot stops when its terminal window is closed, when someone clicks Shutdown server, when Ctrl+C is pressed in its terminal, or when the computer restarts. Asteroboard can't start it again. Go to the computer where Asterobot runs and look for its terminal window. If there's none, start Asterobot again as First launch shows. Wait for Server listening in the terminal. Asteroboard connects by itself and shows Server connected. Your bots come back disconnected, and nothing reconnects or plays on its own. See Disconnect, delete and restart. An error occurred during the server's initialization process Asterobot prints this and stops a moment after starting: it couldn't listen on its address. The rest of the line starts with failed to make server listen:, followed by the reason your system gave. Two things can mislead you. The terminal shows Server listening right before the error, because Asterobot prints that line before it tries. And your browser may still open http://127.0.0.1:8080, which then shows whatever already uses that port: if it's another copy of Asterobot, you land on an Asteroboard connected to that other copy. The usual causes: Another copy of Asterobot is already running, in another terminal window, in a terminal multiplexer such as tmux, or as a service. Use that one, or stop it before starting a new one. Another program uses port 8080. Give Asterobot another port, as below. server.listenAddress names an address this computer doesn't have, for example a network address that changed since you set it. Set it back to 127.0.0.1:8080, or to the current address. Since Asterobot isn't running, change the setting in config.toml with a text editor. Files and folders shows where the file is. Open config.toml. Add these lines, or change the value if a [server] section is already there: [server] listenAddress = "127.0.0.1:8081" Save the file and start Asterobot again. Open http://127.0.0.1:8081 in your browser, so Asteroboard picks up the new address. In MITM mode, the line Asterobot writes in your Dofus folder follows the new port by itself. How the parts connect also covers the two MITM ports. The Server URL points somewhere else Asterobot runs, its terminal shows Server listening, and Asteroboard still stays disconnected. Asteroboard connects to the address saved as its Server URL in the browser you use, and that address doesn't lead to your Asterobot. It happens after you change server.listenAddress, when the browser still holds the address of another Asterobot, such as a remote one or an SSH tunnel on another port, or after a typo. On the computer where Asterobot runs, open http://127.0.0.1:8080 in the browser, with the port of server.listenAddress if you changed it. Asterobot sends you on to Asteroboard, which replaces its Server URL with that address. From another device, or to type the address yourself, open Preferences, type it in Server URL with the scheme, the address and the port, such as http://127.0.0.1:8080, and press Enter. Click Test connection. Each browser keeps its own Server URL, one at a time. Preferences explains the field. The address opens, but Asteroboard stays disconnected This is almost always HTTPS or a password, set with server.tls and server.basicAuth. Asteroboard's own requests can't show a certificate warning or a password prompt, so they fail without a word until the browser has accepted both on a page you opened yourself. What you see What to do Client sent an HTTP request to an HTTPS server. server.tls is on, and the address starts with http://. Use https://. Server disconnected right after a restart that turned server.tls on Asteroboard's Server URL still starts with http://. Open https://127.0.0.1:8080, accept the warning, and Asteroboard takes the new address. Server unreachable, although the https:// address is right Open that address in a tab of the same browser, accept the certificate warning and enter a login and password from server.basicAuth. Then go back to Asteroboard. It worked yesterday and stopped today Browsers forget the password when they close, and some forget the certificate choice after a while. Open the address again. The browser keeps asking for the password The login and password must match a pair in server.basicAuth exactly. Important With server.tls on, or anything in server.basicAuth, MITM mode stops working. See MITM problems. From a phone or another computer By default, Asterobot only accepts connections from the computer it runs on, so another device can't reach it at all. Opening it to your network takes a few settings and a restart: Asteroboard on another device walks through them, and Asterobot on a remote machine covers a server. When you've done that and it still doesn't connect, check these: The address starts with https://. Browsers don't let the Asteroboard page, which is HTTPS, send plain http:// requests to another device. Only the device the browser runs on is allowed, which is why http://127.0.0.1:8080 works there and nowhere else. The other way around it is an SSH tunnel. Asterobot was restarted after you changed server.listenAddress, server.tls or server.basicAuth. None of them applies before. server.listenAddress no longer starts with 127.0.0.1, an address no other device can reach. The firewall of the computer running Asterobot accepts incoming TCP connections on the port. Your browser's permission. Some browsers ask whether asteroboard.asterobot.net can access devices on your local network. Allow it. The SSH tunnel is still open, if you use one. When it closes, Asteroboard shows Server disconnected, and connects again by itself once the tunnel is back. Asteroboard itself doesn't load Asteroboard's page comes from https://asteroboard.asterobot.net. The first time you open it in a browser, that browser needs an internet connection. After that, Asteroboard opens without one, as long as it can reach Asterobot. What you see What it means What to do The page doesn't open at all The browser can't reach asteroboard.asterobot.net and has no copy of it yet. Check your internet connection, and https://status.asterobot.net. Offline mode unavailable "This device couldn't get everything ready for offline use." Asteroboard works, but some features may need an internet connection. Nothing, unless you need it offline. Update available, with Refresh now A new version of Asteroboard is ready. Click Refresh now, or reload the page. An old version, or odd behavior after an update The browser's copy of Asteroboard is out of step. Use Reset offline data. See Reset and start over. Page not found The address doesn't match any page of Asteroboard. Click Go to dashboard. Something went wrong "Asteroboard couldn't display this page." Click Go back, or reload. If it keeps happening, open Technical details and note the Status and the Requested address for your help request. Still stuck Read Asterobot's terminal. Server > Console only receives lines while Asteroboard is connected, so the terminal is the only place that shows what happened before. Ask on the forum or on Discord, with your Asterobot version, the address you use and the last lines of the terminal. Getting help lists what to include and what never to share. Where to go next How the parts connect Preferences Status and console

Asterobot doesn't update itself: when a new version is out, you replace the program by hand. It takes a few minutes, and your bots, accounts, packages, game versions and settings are all kept. Asteroboard, on the other hand, updates on its own. Know when a new version is out Each time Asterobot starts, it checks asterobot.net. When a newer version is published, the terminal prints An Asterobot update is available with the version and the link, and Asteroboard shows Asterobot update available with a View on asterobot.net button. Messages and updates explains the check in detail. You can also compare yourself: your version is on Server > Status, and the latest one on the Asterobot file at https://asterobot.net/files/category/3-asterobot/. What an update keeps The program is a single file, and Asterobot stores nothing next to it. Everything else lives in the folders of your user profile (Files and folders), which the new version uses as they are: your bots, Ankama accounts and packages; your game versions and their extracted game data; the settings you changed, and the asterobot.net sign-in. A setting you never changed takes the new version's default, if that default changed. A setting you changed keeps your value (The Config page). Nothing needs to be exported first. If you want a safety copy anyway, follow Back up your Asterobot. Update Asterobot Download the new archive for your system and processor, the same kind as the one you use now, and check it with checksums.txt. Download Asterobot shows both. Stop Asterobot, with Ctrl+C in its terminal or Shutdown server on Server > Status, and wait until it has exited. Stopping it normally lets it disconnect your bots and put back the line it may have changed in your Dofus folder for MITM mode. Unpack the archive and replace the old program with the new one: asterobot.exe on Windows, asterobot on macOS and Linux. You can also put it in another folder and delete the old one. On macOS and Linux, make the new file executable again, from its folder: chmod +x asterobot Start Asterobot as usual (First launch). The first line in the terminal now shows the new version, and so does Version on Server > Status. The update notification doesn't show any more. After the update Bring your bots back online. As after any restart, they come back disconnected and nothing plays by itself: click Connect or Start waiting, then Play (Disconnect, delete and restart). Look at the Compatibility column of Game Manager. Each release of Asterobot is tested with one Dofus version, which can change from one release to the next. A game version that matches shows Compatible (Why Asterobot downloads Dofus). Look at your packages. A package that states which versions of Asterobot it works with can switch between Compatible and Incompatible after an update (What is a package). Asteroboard updates on its own There's nothing to download for Asteroboard. While it's open, it checks for a new version every 30 minutes, and shows Update available when one is ready. Click Refresh now, or reload the page when it suits you, to switch to it. Messages and updates has the details, and what to do when it doesn't switch. Asterobot and Asteroboard have separate versions and update separately. Where each version number is shown Version of Where to read it Asterobot The first line Asterobot prints when it starts, right after the word Asterobot. The Version row on Server > Status. The command ./asterobot --version, or .\asterobot.exe --version on Windows (Command line). Asteroboard The top of the sidebar, next to the name, as v followed by the number. It links to Asteroboard's release notes, at https://asterobot.net/release-note-asteroboard. The About page, after "Asteroboard version". Where to go next Files and folders Messages and updates

Preferences holds Asteroboard's own options: how it looks, and which Asterobot it connects to. They're saved in the browser you use, so each browser and each device has its own, and none of them changes anything in Asterobot. Asterobot's settings are on Server > Config instead (The Config page). In the sidebar, click Preferences. The page has three sections, switched at the top: Appearance, which opens first, Server and Danger zone. Appearance Every change applies at once. Field What it changes Choices Default Language The language of Asteroboard's interface. English, French, Spanish Your browser's language, or French when your browser uses another one Color mode Light or dark interface. System, Light, Dark System, which follows your system Primary color The main accent color. 17 colors, from Red to Rose Green Neutral color The gray tone of text, borders and backgrounds. Slate, Gray, Zinc, Neutral, Stone, Taupe, Mauve, Mist, Olive Slate Radius How rounded the corners of buttons, cards and fields are. 0, 0.125, 0.25, 0.375, 0.5 0.25 The language list shows each language in its own name, followed by its name in the current language, such as "Français (French)". Once you've changed a field, a small button next to it goes back to the default: Use system language for the language, Use default for the colors and the radius. Color mode needs none, since System is one of its choices. Tour of Asteroboard shows how the language affects game texts on the Game page. Server This section tells Asteroboard where your Asterobot is. Without a working address, Asteroboard has nothing to show. Server URL The address Asteroboard connects to. It's http://127.0.0.1:8080 by default, which is right when Asterobot runs on the same computer with its default settings. You rarely have to type it. When you open Asterobot's own address in your browser, http://127.0.0.1:8080 by default, you land on Asteroboard with that address already in Server URL. It replaces whatever the field held, without asking. To change it by hand: Type the address in Server URL, with http:// or https://, the computer's address and the port, such as http://192.168.1.20:8080. Press Enter or click outside the field. Asteroboard connects to the new address right away. It drops what it showed about the previous Asterobot, including the lines of Server > Console, and loads everything again from the new one. Slashes at the end of the address are removed. You'll need this for Asterobot on another device, on another port, or with HTTPS: see Asteroboard on another device. Connection The badge shows the live state of the connection: Connecting…, Connected or Disconnected. Test connection sends a single request to Asterobot and tells you how it went: Server reachable, with the time the round trip took, such as "Round-trip latency: 12ms". If the badge didn't say Connected yet, Asteroboard reconnects right away. Server unreachable: Asterobot didn't answer at that address. Check that Asterobot is running and that Server URL is right, then see Asteroboard can't connect. A test is handy right after you changed the address or restarted Asterobot. Danger zone These two buttons clear what Asteroboard keeps in the browser you use, then reload the page. They never touch Asterobot: your bots, accounts, packages and settings stay as they are. Your browser asks you to confirm each one. Reset offline data Asteroboard keeps a copy of itself in your browser so it opens quickly and works without an internet connection. Reset offline data deletes that copy and reloads the page, which downloads Asteroboard again. The browser needs an internet connection for that. Click Reset offline data. Confirm "This clears all offline data cached by Asteroboard and reloads the page. Continue?" Use it when Asteroboard keeps showing an old version, or behaves oddly after an update. Your preferences and your Server URL stay. If you installed Asteroboard as an app, it stays installed. The button is greyed out when your browser can't run Asteroboard offline at all. If the reset fails, Asteroboard shows Couldn't reset offline data: "Try again, or clear this site's data from your browser's settings." Reset preferences Reset preferences puts Asteroboard's look and layout back to their defaults, then reloads the page. Click Reset preferences. Confirm "This resets language, appearance and dashboard layout preferences back to their defaults and reloads the page. Continue?" What each reset clears Reset offline data Reset preferences Language, color mode, colors and radius Kept Back to defaults The language of game texts on the Game page Kept Back to following Asteroboard's language Sidebar layout: folded or not, and its width Kept Back to defaults Server URL Kept Kept The level buttons of Server > Console Kept Kept Asteroboard's offline copy Deleted, then downloaded again Kept Everything in Asterobot Kept Kept A few other choices are remembered in your browser and kept by both resets, such as the layers of the world map and the volume of the music player. To remove everything Asteroboard stored in a browser, clear the site data of asteroboard.asterobot.net in that browser's settings. Where to go next Asteroboard on another device Updating Asterobot

The Server page is about Asterobot itself rather than your bots. Its Status tab tells you whether Asteroboard is connected and which Asterobot it's talking to, and its Console tab shows Asterobot's log as it happens. The terminal Asterobot runs in shows the same log, with a little more detail. The Status tab In the sidebar, click Server: the Status tab opens first. It has four parts, from top to bottom. Connection state A large dot with a word tells you how Asteroboard's connection to Asterobot is doing: State Dot What it means Connected Green, pulsing Asteroboard is connected and receives everything live. Connecting… Amber Asteroboard is trying to connect. Disconnected Red Asteroboard can't reach Asterobot. It tries again every second. When Asteroboard stays Disconnected, see Asteroboard can't connect. The Connection card Row What it shows Server URL The address Asteroboard uses to reach Asterobot, set in Preferences. Version The version of Asterobot, not of Asteroboard. Transport Encrypted (HTTPS) when the Server URL starts with https://, otherwise Not encrypted (HTTP). Authentication Password protected when server.basicAuth holds at least one login, otherwise No password. Transport is read from the address Asteroboard uses, and Authentication from the saved setting. Since server.basicAuth only takes effect after a restart, Password protected can show before the password is actually required. Asteroboard on another device explains HTTPS and passwords. The Debug card The Debug card gives technical numbers about the running Asterobot. You don't need them day to day, but someone helping you may ask for a few of them. Value What it is CPUs How many processor cores Asterobot can use. Goroutines How many tasks are running inside Asterobot at that moment. Cgo calls A technical counter, only useful for troubleshooting. Go version The version of Go, the programming language Asterobot is built with. OS The system this Asterobot was built for: windows, darwin for macOS, or linux. Architecture The processor type it was built for: amd64 or arm64. Compiler The compiler used to build it. Allocated and Heap allocated The memory Asterobot uses for its data right now. Total allocated All the memory Asterobot has used for its data since it started, added up, including what it has already freed. System memory The memory Asterobot has reserved from your system. The numbers are read when the card loads and again after Free memory now. They don't update on their own. Free memory now asks Asterobot to give back the memory it no longer uses right away, instead of when it would do so on its own. As the card says, it shouldn't normally be necessary. Asteroboard confirms with Garbage collection triggered, or shows Couldn't trigger garbage collection. Shut Asterobot down The Shutdown card stops Asterobot: "Stops the Asterobot server. Only do this if you know how to start it again." Click Shutdown server. The Shutdown the server? dialog reminds you that Asteroboard can't restart Asterobot: unless it's set up to start again on its own, someone needs access to the computer it runs on. Click Yes, shutdown, or Cancel. Asteroboard shows Shutdown requested, and Asterobot stops about two seconds later, closing everything properly as with Ctrl+C in its terminal. Asteroboard then shows Disconnected. If the request doesn't reach Asterobot, Asteroboard shows Couldn't shut down the server and nothing stops. Stopping Asterobot disconnects every bot, including a bot relaying the game you play. First launch covers starting it again. The Console tab Server > Console shows Asterobot's log live: what it does, the warnings and errors it meets, and the lines scripts write with asterobot:console. What it shows Each line shows the time, in your browser's time zone, the level (DEBUG, INFO, WARN or ERROR) and the text. Only the text: the details the terminal prints after a message, such as the address in Server listening, don't appear here. Lines written by a script with asterobot:console don't say which bot wrote them. A bot's own lines are on its Console tab instead (Console). The Console tab only has what arrived while Asteroboard was open. Asterobot keeps no history for it, so lines from before you opened Asteroboard aren't there: look in the terminal for those. Asteroboard keeps the last 500 lines, forgets them when you reload or close the page, and clears them when you change its Server URL. When nothing has arrived yet, the console says "No log messages yet." The right end of the top bar shows whether Asteroboard is connected: Connected, Connecting… or Disconnected. Show and hide levels The four buttons at the top, Debug, Info, Warning and Error, show or hide the lines of each level. A filled button means its lines are shown. Asteroboard remembers your choice in this browser. These buttons only filter lines Asteroboard has already received. Lines below the server level never arrive in the first place. Server level The Server level list next to the buttons sets logger.webLevel: the lowest level Asterobot sends to the console. As its tooltip says, anything below it never arrives here at all, whatever the buttons show. It's INFO by default, so debug lines don't reach the console until you pick DEBUG. The change applies at once, for every Asteroboard, and stays after Asterobot restarts because it's a saved setting. If it can't be saved, Asteroboard shows Couldn't update the server log level. Send a message The box at the bottom, "Send a message to the server console...", writes a line into Asterobot's own log. Type your text. Pick its level in the list under the box: Info by default. Press Enter, or click the send button. Asterobot logs your text like one of its own lines. It appears in the terminal if its level is at or above the terminal's level, and on every open Console tab if it's at or above the server level: a Debug message never shows while the server level is INFO. If the message can't be sent, Asteroboard shows Couldn't send message. A message is handy to mark a moment in the log, for example right before you reproduce a problem for a bug report. The terminal The terminal Asterobot runs in shows its log from the very first line, including everything before Asteroboard was opened. Each line starts with the date and time, then the level and the message, followed by its details as name=value pairs, in color. How much it prints is set by logger.cliLevel, on Server > Config. The change applies at once, and it's independent of the console's level: you can keep a quiet terminal and a detailed console, or the other way round. A few things in the terminal aren't log lines and always show, whatever the level: the QR code of a sign-in link, the progress bars of commands, and what commands such as gamemanager list print. Asterobot writes no log file. When you close the terminal window, its lines are gone. Choose a log level Both logger.cliLevel and logger.webLevel take the same four values. Each level shows its own lines and every level above it: Level What you see DEBUG Everything, including detailed lines meant for troubleshooting. INFO Normal activity. The default for both. WARN Warnings and errors only. ERROR Errors only. Switch to DEBUG when you investigate a problem or someone helping you asks for detailed logs, then go back to INFO: debug lines are numerous and bury the useful ones. Where to go next The Config page Getting help

Asterobot keeps nothing next to the program itself. It stores everything in standard folders of your user profile: one for its settings, one for its data and one for its cache. Knowing which is which tells you what to copy when you back up your Asterobot or move it to another computer. Where the folders are Folder Windows macOS Linux Settings %LocalAppData%\asterobot\config ~/Library/Application Support/asterobot/config ~/.config/asterobot Data %LocalAppData%\asterobot\appdata ~/Library/Application Support/asterobot/appdata ~/.local/share/asterobot Cache %LocalAppData%\asterobot\cache ~/Library/Caches/asterobot ~/.cache/asterobot Asterobot creates them the first time it starts. They're always three separate folders: Asterobot refuses to start with one of them inside another. On Windows, %LocalAppData% usually stands for C:\Users\<your name>\AppData\Local. Typing the path, % signs included, in File Explorer's address bar opens the folder. On macOS and Linux, ~ is your home folder. On Linux, the variables XDG_CONFIG_HOME, XDG_DATA_HOME and XDG_CACHE_HOME replace ~/.config, ~/.local/share and ~/.cache when they hold an absolute path. On every system, the options --config-dir, --appdata-dir and --cache-dir, or their environment variables, choose other folders. Command line explains them. The settings folder It holds a single file, config.toml, with the settings you changed on Server > Config. Settings still at their default aren't written in it, which is why the file is empty after a first launch. The Config page explains how Asterobot reads and writes it, including when you edit it by hand. config.toml contains two secrets once they're set: website.token, Asterobot's sign-in on asterobot.net, and the logins and passwords of server.basicAuth, in plain text. The data folder Inside What it holds More bots.toml Every bot, with everything you set for it. What is a bot accounts.toml Your Ankama accounts: Login IDs, the passwords you stored, in plain text, and the tokens Ankama gave Asterobot. Add an account library/packages/ Your packages, one folder per version, such as library/packages/my-harvester/1.0.0/ or library/packages/@some-author/auto-harvest/1.2.0/. Manage your library tls/cert.pem and tls/key.pem The HTTPS certificate and its private key, created the first time Asterobot starts with server.tls on. Settings reference zaapmanager/browser-profiles/ One sign-in browser profile for each account that signed in automatically. Each holds a live Ankama session. Automatic sign-in This is the folder that makes your Asterobot yours. Losing it means adding your bots, accounts and packages again. The cache folder Inside What it holds game/ The files of each game version, one folder per version, such as game/dofus/dofus3/windows/3.6.11.13/. game_extracted/ The game data extracted from each version. zaapmanager/ The screenshot of the last failed automatic sign-in of each account. The last folder holds the chunks game versions are rebuilt from, in its chunk subfolder (How chunks are stored), and the lists of versions and files Ankama's download servers publish, with a few other files they provide. Everything in the cache can be downloaded or rebuilt again. Losing it costs time, not settings: you download and extract your game versions again. It's also by far the largest folder, since it holds the game versions (Why Asterobot downloads Dofus). No log files Asterobot doesn't write any log file. Its log goes to the terminal it runs in, and to Server > Console while an Asteroboard is open. Once the terminal window is closed, its lines are gone, so copy what you need first. Status and console covers both places. Permissions On Linux and macOS, Asterobot restricts the files that hold secrets to your own user account: File or folder Who can read it config.toml Only your user. If other users can read it, Asterobot restricts it when it reads the file, and the terminal shows Restricted the configuration file to its owner. accounts.toml Only your user. Asterobot applies it again every time it starts and every time it saves the file. zaapmanager/browser-profiles/ Only your user. tls/key.pem Only your user. Everything else Created readable by the other users of the computer. On Windows, these restrictions have no effect. In every case, anyone who can open files as your user, or who gets a copy of these files, can read the passwords and use the tokens in them. Getting help lists what must never be shared. Editing the files by hand config.toml: Asterobot watches it and applies your changes as soon as you save. See The Config page. bots.toml and accounts.toml: Asterobot reads them only when it starts, and writes them again each time something changes. A change you make while it runs is overwritten. Stop Asterobot before you edit them, and keep a copy of the original. Game version folders: after adding or removing one by hand, click Rescan in Game Manager (Manage game versions). Package folders: don't change the files of a package installed from the marketplace. Asterobot checks them each time the package loads and refuses them if they changed (Trusting a package). Back up your Asterobot Stop Asterobot, so it isn't writing any file while you copy (First launch). Copy the settings folder and the data folder somewhere safe. The cache folder is optional: everything in it can be downloaded again, but that takes time. Start Asterobot again. To restore a backup, stop Asterobot, put the folders back in place, then start it. Caution A backup contains your Ankama passwords, your tokens and your asterobot.net sign-in. Keep it somewhere only you can reach. Move to another computer Download and unpack Asterobot on the new computer (Download Asterobot). Stop Asterobot on the old computer. Copy the settings folder and the data folder to the places listed at the top of this page for the new computer's system. Copy the cache folder too if you don't want to download your game versions again. Start Asterobot on the new computer. The files and folders inside keep the same names on every system, only their locations change. Then check a few things: Asterobot is still signed in to asterobot.net, since the sign-in travels in config.toml. Your bots come back disconnected, as after any restart. A bot whose game version isn't in the cache is skipped until you download and extract that version (Disconnect, delete and restart). Settings that name a folder of the old computer still point there if you had changed them: botmanager.mitmGamePath and zaapmanager.browserPath. Settings you never changed take the new computer's defaults. Asteroboard remembers its Server URL per browser. On a new computer or browser, open the new Asterobot's address once to connect (Preferences). What each reset deletes Reset Where What it deletes What it keeps Reset to default, a group's reset, Reset all Server > Config The values you set, from config.toml. The asterobot.net sign-in goes too when website.token is included. The data and cache folders config reset Command line Everything in config.toml, the sign-in included The data and cache folders cache reset Command line The whole cache folder The settings and data folders Uninstall, Delete, Remove all chunks Game Manager Parts of the cache folder (Manage game versions) Everything else Remove Library Manager One package version's folder Everything else Reset offline data, Reset preferences Preferences Only what Asteroboard stores in your browser (Preferences) All of Asterobot's folders Reset and start over helps you pick the right one when something is broken. Where to go next Command line Updating Asterobot

Running Asterobot without a command starts it, as you do every day. The same program also has commands for jobs you can do without Asteroboard: listing and downloading game versions, managing the library, and resetting settings or the cache. Run a command Commands run in a terminal, from the folder where you put Asterobot: Windows: open PowerShell in that folder and type .\asterobot.exe, then the command and its options. macOS and Linux: open a terminal in that folder and type ./asterobot, then the command and its options. Commands come in groups, one for each part of Asterobot they work on: gamemanager for game versions, library for packages, config for settings and cache for the cache folder. You type the group, then the command. For example, to list your game versions: .\asterobot.exe gamemanager list ./asterobot gamemanager list The examples below use ./asterobot. On Windows, write .\asterobot.exe instead. Options start with two hyphens and take a value after a space: --version latest. Put quotes around a value that contains spaces or special characters, such as a regular expression. Every command first prints the same line as a normal start, with Asterobot's version, then does its job. A command that takes a while, such as a download, shows a progress bar, and Ctrl+C interrupts it. When a command fails, it prints a line with asterobot execution failed, followed by the reason. When the command line itself is wrong, nothing happens: Asterobot prints a line with Incorrect usage:, followed by the mistake. Mistake What follows Incorrect usage: A group that doesn't exist unknown command "gamemanger". Did you mean "gamemanager"? A command the group doesn't have No help topic for 'lst'. Did you mean "list"? A required option left out Required flag "version" not set, after the command's options are listed Help and version Type To get ./asterobot --help or ./asterobot -h The list of groups, then the folder options with this computer's default folders. ./asterobot gamemanager or ./asterobot gamemanager --help The commands of one group. ./asterobot gamemanager download --help The options of one command, then the folder options under GLOBAL OPTIONS. ./asterobot --version or ./asterobot -v The version, on a line that reads Asterobot version followed by the number. Choose the folders Asterobot keeps its files in three folders, one for its settings, one for its data and one for its cache (Files and folders). An option puts each of them somewhere else, for a normal start as for any command: Option Environment variable Folder --config-dir ASTEROBOT_CONFIG_DIR The settings folder, with config.toml --appdata-dir ASTEROBOT_APPDATA_DIR The data folder: bots, Ankama accounts, packages and the rest of your data --cache-dir ASTEROBOT_CACHE_DIR The cache folder: game versions and everything else that can be downloaded again For example, to keep the game versions on another disk: ./asterobot --cache-dir /mnt/games/asterobot-cache Asterobot uses the folder you give as it is, without adding a subfolder, and creates it when it's missing. A relative path starts from the folder the terminal is in. The option can come before or after the command, as in ./asterobot gamemanager list --cache-dir /mnt/games/asterobot-cache. An environment variable works like its option for every run that sees it, and the option wins when both are set. Asterobot doesn't remember these folders. A run without the option or its environment variable uses the default folder, so give the same folders to every start and every command: a game version downloaded with --cache-dir only shows in Game Manager when Asterobot starts with the same cache folder. The three folders have to stay apart, and away from your home folder, since cache reset deletes everything in the cache folder. Before it runs anything, Asterobot refuses these folders with a line with Incorrect usage:: Folders What follows Incorrect usage:, for example Two options with the same folder, or one option's folder inside another's --appdata-dir and --cache-dir must be separate folders, neither inside the other: /data and /data/cache Your home folder, or a folder that contains it --cache-dir can't be your home folder or a folder that contains it: /home/me An empty value, such as an environment variable set to nothing --cache-dir needs a folder All commands Command What it does In Asteroboard server Starts Asterobot. Same as running it without a command. gamemanager list Lists the game versions Asterobot knows. Game Manager gamemanager registry Lists the game versions Ankama's download servers offer. gamemanager download Downloads a game version. Download a game gamemanager verify Checks a version's files and downloads again the ones that don't match. Verify files gamemanager remove Deletes a game version. Delete gamemanager chunks verify Checks every stored chunk. Check all chunks gamemanager chunks clear Deletes every stored chunk. Remove all chunks library list Lists the packages in your library. Library Manager library install Installs a package from a folder. Import a .zip library remove Removes one package version. Remove config reset Puts every setting back to its default. Reset all on Server > Config cache reset Deletes Asterobot's cache folder. While Asterobot is running A command works on the same files as Asterobot when both use the same folders, and an Asterobot already running in another terminal isn't told what a command changed. A game version downloaded with gamemanager download, for example, only appears in Game Manager after Rescan or a restart (Manage game versions). To stay on the safe side, stop Asterobot before you run a command that changes files, and start it again afterwards. For cache reset, stopping it first is a must. Game versions The commands that name a version take the same four options, and all four are required: Option What to give Example --game The game's code dofus --environment The environment dofus3 --platform The platform windows --version The version number 3.6.11.13 These are the values the Game, Environment, Platform and Version columns of Game Manager show. Download a game version explains them. gamemanager list ./asterobot gamemanager list Prints a table of the game versions Asterobot knows, installed or not, one row per version: game, environment, platform, version and status, such as installed, downloading or failed. GAME ENVIRONMENT PLATFORM VERSION STATUS dofus dofus3 windows 3.6.11.13 installed gamemanager registry ./asterobot gamemanager registry Prints a table of the game versions found in the lists of Ankama's download servers that Asterobot keeps in its cache folder: game, environment, platform and version. How many lists are kept depends on cytrus.keepMostRecentIndexes (Settings reference). gamemanager download ./asterobot gamemanager download --game dofus --environment dofus3 --platform windows --version latest Downloads a game version and waits until it's done, with a progress bar. Besides the four options above: Option What it does --version latest Downloads the newest version Ankama offers for that game, environment and platform. --file-filter A regular expression. Only the files whose path matches are downloaded. --fragment-filter A regular expression matched against the names of the parts Ankama splits a game into. Only the matching parts are downloaded. The command works differently from Download a game in two ways: Without --file-filter, it downloads every file of the version, not only the ones a bot needs, which takes much more space. To download only what bots need, copy the pattern from the File filter (regex) field of Asteroboard's download dialog and give it to --file-filter, between quotes. It doesn't extract game data. Extract the version from Game Manager afterwards (Extract game data). gamemanager verify ./asterobot gamemanager verify --game dofus --environment dofus3 --platform windows --version 3.6.11.13 Checks the files of a version that are on disk against the list Ankama publishes, and downloads again the ones that don't match. It needs the exact version number: latest only works with gamemanager download. --file-filter and --fragment-filter narrow the check to part of the files, and never add files that weren't downloaded. gamemanager remove ./asterobot gamemanager remove --game dofus --environment dofus3 --platform windows --version 3.6.11.13 Deletes a game version: its files and its extracted game data. Stored chunks stay, like with Delete in Game Manager. It prints Game removed, or fails with game is not installed when Asterobot doesn't know that version. Bots set to the version aren't checked: move them first (When Dofus updates). gamemanager chunks verify ./asterobot gamemanager chunks verify Reads every stored chunk and deletes the ones whose content doesn't match, with a progress bar. It ends with All chunks have been validated!. A deleted chunk is downloaded again the next time a download needs it. gamemanager chunks clear ./asterobot gamemanager chunks clear Deletes every stored chunk, for every game and version, and prints Chunks removed. Your game versions keep working. The next download or check fetches the chunks it needs again, which makes it slower. Manage game versions explains chunks. Packages Note The package commands also set up Asterobot's asterobot.net sign-in. If Asterobot isn't signed in, they print a sign-in link and may open it in your browser. You can ignore it: listing, installing and removing local packages doesn't need the sign-in. library list ./asterobot library list Prints a table of the package versions in your library, one row per version: name, version, provenance (local, community or official) and publisher. library install ./asterobot library install --path ./my-harvester --name my-harvester --version 1.0.0 Installs a package from a folder on your computer. All three options are required: Option What to give --path The folder that holds the package's .js or .mjs files, with index.js directly inside it, and its asterobot.json if it has one. --name The name the package gets in your library. A plain name, such as my-harvester, makes a local package. A name like @publisher:name makes it show Community, or Official with @asterobot:. --version The exact version, such as 1.0.0. It prints Package my-harvester@1.0.0 installed. When that name and version are already installed, the files are replaced. A missing option stops the command with an error such as Required flag "version" not set. Script authors working with an external editor will find more in Zip files and the command line. library remove ./asterobot library remove --name my-harvester --version 1.0.0 Removes one version of a package and prints Package removed. Both options are required. Unlike Remove in Library Manager, it doesn't warn you about bots set to that version or packages that depend on it. Resets Both resets delete things for good, so each one asks before it does anything. [y/N] at the end of the question means Enter alone answers no: type y or yes, then Enter, to go ahead. Any other answer stops the command with not confirmed, and nothing changes. To answer yes in advance, for example in a script, add --yes after the command. Without --yes, a reset reads its answer from the terminal. When its input is a pipe or a file instead, it doesn't ask and stops with this command needs a confirmation: run it again with --yes, so piping y into it doesn't confirm anything. A reset works on the folders of its own run. If you start Asterobot with folder options or their environment variables, give the reset the same folders. config reset ./asterobot config reset It asks Put every setting back to its default value? [y/N]. Once you confirm, it puts every setting back to its default and empties config.toml, printing Resetting the configuration.. then All configuration settings have been reset to their default values. What you lose is everything you changed on Server > Config, including: Asterobot's asterobot.net sign-in: you'll confirm a new sign-in code. The network settings, such as server.listenAddress, server.basicAuth and server.tls, which go back to accepting connections from this computer only, without a password. Your MITM ports, hosts and Dofus folder, and your automatic sign-in settings. Your bots, Ankama accounts, packages and game versions are kept. If Asterobot is running, it reads the emptied file right away, as it does after a hand edit: it's signed out at once, and the settings that need a restart go back to their defaults at the next start. cache reset ./asterobot cache reset It asks Delete <folder> with everything in it? [y/N], with the full path of the cache folder in place of <folder>, so check that it's the folder you mean. Once you confirm, it deletes the cache folder with everything in it, then creates it again, empty, printing Resetting the cache.. then All cache have been removed. What you lose: every game version, with its files and extracted game data, every stored chunk, Ankama's download lists, and the screenshots of failed automatic sign-ins. Bots set to a deleted game version are skipped when Asterobot starts, until you download and extract that version again. Your settings, bots, Ankama accounts and library stay, since their folders are never inside the cache folder. Stop Asterobot before you run it. Reset and start over helps you choose the right reset. Where to go next Files and folders Settings reference

Asterobot has 19 settings, grouped here by what they're about. You change them on Server > Config (The Config page) or in config.toml. Settings marked as needing a restart only take effect the next time Asterobot starts. All settings at a glance Key Type Default Restart needed server.listenAddress Text 127.0.0.1:8080 Yes server.basicAuth Logins and passwords Empty Yes server.tls On or off Off Yes server.skipOpenFrontend On or off Off No logger.cliLevel Log level INFO No logger.webLevel Log level INFO No website.token Text, hidden Empty No website.showQRCode On or off Off No website.signedOut On or off Off No botmanager.mitmSignInPort Number 5555 Yes botmanager.mitmSessionPort Number 5556 Yes botmanager.mitmBindHost Text 127.0.0.1 Yes botmanager.mitmAdvertiseHost Text Empty Yes botmanager.mitmGamePath Text Depends on the system No zaapmanager.browserHeadless On or off On No zaapmanager.browserPath Text Empty No zaapmanager.browserUserAgent Text Empty No cytrus.keepMostRecentIndexes Number 5 No cytrus.keepMostRecentGamesManifests Number 5 No On the Config page, each group is a card named after the first part of its keys, and the cards come in alphabetical order rather than in the order of this page. Connection to Asteroboard These settings decide where and how Asteroboard reaches Asterobot. The defaults only accept connections from the computer Asterobot runs on. To reach Asterobot from another device, follow Asteroboard on another device rather than changing them one by one, and read Security first. server.listenAddress Text. Default 127.0.0.1:8080. Restart needed. The address and port where Asterobot waits for Asteroboard, written as address:port. With 127.0.0.1, only the computer Asterobot runs on can connect. 0.0.0.0:8080 accepts connections on every network interface of the computer. Change it when another program already uses port 8080, or when Asteroboard runs on another device. Keep in mind: If Asterobot can't use the address, for example because the port is taken, it stops right after starting with An error occurred during the server's initialization process. When Asterobot starts, it opens your browser on 127.0.0.1 with this port. That only works when the value is an IP address followed by a port. With a name such as localhost:8080, the terminal shows Failed to open frontend, and Asterobot keeps running: open Asteroboard yourself. Asteroboard keeps using its old Server URL after the restart. Open Asterobot's new address in your browser, or change Server URL in Preferences. The port also appears in the line Asterobot writes in your Dofus folder for MITM mode (MITM mode). server.basicAuth Logins and passwords. Default empty. Restart needed. Hidden. The logins and passwords someone must enter to reach Asterobot. Empty means no password at all, which is fine as long as only your own computer can connect. It's edited as JSON on the Config page, one login per entry: {"alice": "a long password", "bob": "another long password"} The passwords are stored in plain text in config.toml. Once a login is set, Server > Status shows Password protected (Status and console). Warning With this set, MITM mode stops working, even on a single computer. MITM mode explains why, and an SSH tunnel lets other devices in without it. server.tls On or off. Default off. Restart needed. Serves Asterobot over HTTPS instead of HTTP. The first time Asterobot starts with this on, it creates its own certificate, tls/cert.pem, and its private key, tls/key.pem, in its data folder (Files and folders). The certificate is valid for three years, only for the names localhost, 127.0.0.1 and ::1, and signed by Asterobot itself, so browsers warn about it until you accept it. The description on the Config page mentions the file cache directory, but the two files are in the data folder. To get a new certificate, delete them and start Asterobot again. With this on, Asteroboard's Server URL must start with https://, and the browser Asterobot opens at start uses https://127.0.0.1 with the port of server.listenAddress. Warning With this on, MITM mode stops working, even on a single computer. MITM mode explains why, and an SSH tunnel lets other devices in without it. server.skipOpenFrontend On or off. Default off. No restart needed. Asterobot opens your browser on Asteroboard each time it starts. Turn this on to stop that, for example on a computer without a screen, or when Asteroboard is already open. It's read each time Asterobot starts. Logs The two log levels are independent: one for the terminal Asterobot runs in, one for Server > Console. Both take one of four values, and a level shows its own lines and every level above it: Level What you see DEBUG Everything, including detailed lines meant for troubleshooting. INFO Normal activity. The default. WARN Warnings and errors only. ERROR Errors only. Status and console explains both places in detail. logger.cliLevel Log level. Default INFO. No restart needed. How much the terminal Asterobot was started from prints. Set it to DEBUG when someone helping you asks for detailed logs, and back to INFO afterwards: debug lines are numerous. logger.webLevel Log level. Default INFO. No restart needed. How much reaches Server > Console. Lines below this level are never sent to Asteroboard at all. The Server level list on the Console tab changes this same setting. asterobot.net sign-in website.token Text. Default empty. No restart needed. Hidden. The sign-in Asterobot uses on asterobot.net. Asterobot stores it when you confirm a sign-in code, and empties it when you log out. There's no reason to type anything here. Anyone who gets this value can use your asterobot.net access, so never share it (Getting help). Resetting it signs Asterobot out. website.showQRCode On or off. Default off. No restart needed. Prints the sign-in link as a QR code in the terminal, so you can confirm the code from a phone. Useful when Asterobot runs on a machine without a browser. It applies from the next code Asterobot asks for. See Sign in with asterobot.net. website.signedOut On or off. Default off. No restart needed. Turned on when you log out, and off again when you sign in. While it's on, Asterobot never starts a sign-in by itself, not even after a restart. Leave it to the account button: turning it off by hand only lets Asterobot start a new sign-in on its own the next time it needs your account. See Your account. MITM mode These settings only matter for bots in MITM mode, short for man-in-the-middle, where a bot relays the Dofus you play. A bot that signs in on its own never uses them. MITM mode explains the mode, and MITM across machines the setups where Dofus runs on another computer. botmanager.mitmSignInPort Number. Default 5555. Restart needed. The port your Dofus signs in on once its files point at Asterobot. Change it only when another program on this computer already uses the port. It must differ from botmanager.mitmSessionPort. botmanager.mitmSessionPort Number. Default 5556. Restart needed. The port your Dofus opens its game session on, after signing in. One port serves every relayed bot: Asterobot tells the sessions apart by what they send. Change it only when another program already uses the port. botmanager.mitmBindHost Text. Default 127.0.0.1. Restart needed. The network interface the two ports listen on. 127.0.0.1 only accepts connections from this computer, which is right when you play on it. To relay a Dofus running on another computer, set this computer's address on your network, or 0.0.0.0 for every interface. Anything on that network can then reach the two ports. botmanager.mitmAdvertiseHost Text. Default empty. Restart needed. The address your Dofus is told to connect to. Empty uses botmanager.mitmBindHost, or 127.0.0.1 when that one is 0.0.0.0. Set it when Asterobot is bound to 0.0.0.0, or sits behind a NAT, to the address the Dofus computer can actually reach. botmanager.mitmGamePath Text. Default depends on the system. No restart needed. The folder of the Dofus you play, the one the Ankama Launcher installed. Asterobot reads the version number of its Dofus_Data/StreamingAssets/version file and edits one line of it while a bot waits for your game, and reads nothing else from that 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 Empty The default is only filled in when that folder exists as Asterobot starts. Set the folder yourself on macOS, or when your Dofus is installed somewhere else. A new value applies once no bot is waiting for your game. Automatic Ankama sign-in These settings refine how Asterobot signs Ankama accounts in through a browser. None of them is needed for automatic sign-in to work: storing an account's password is what turns it on. Automatic sign-in explains the whole process. zaapmanager.browserHeadless On or off. Default on. No restart needed. Runs the sign-in browser without a window. Turn it off, on a computer with a screen you're sitting at, to watch the sign-in and answer a challenge Ankama shows. Turn it back on afterwards. It applies from the next sign-in. zaapmanager.browserPath Text. Default empty. No restart needed. The full path of the browser used to sign in to Ankama. Empty makes Asterobot look for Google Chrome, Chromium or Microsoft Edge in their usual places. Set it for a browser installed somewhere unusual, or for another Chromium-based browser such as Brave, Vivaldi or Opera. When it's set, Asterobot uses that browser only. zaapmanager.browserUserAgent Text. Default empty. No restart needed. 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. Leave it empty unless you have a precise reason to change it. Game download lists When Asterobot downloads game versions, it keeps copies of two kinds of lists from Ankama's download servers in its cache folder: the list of available game versions, and for each version, the list of files it's made of. These two settings limit how many copies it keeps. You'll rarely need to change them. cytrus.keepMostRecentIndexes Number. Default 5. No restart needed. How many copies of the list of available game versions Asterobot keeps. Older copies are deleted. 0 keeps every copy. The gamemanager registry command lists the versions found in the copies that are kept (Command line). cytrus.keepMostRecentGamesManifests Number. Default 5. No restart needed. How many lists of files Asterobot keeps for each game. Older ones are deleted. 0 keeps them all. Where to go next The Config page Command line

Server > Config lists every setting of your Asterobot, the ones you changed and the ones still at their default. What you change there is saved in Asterobot's config.toml file at once. What each setting does is in Settings reference. Open it In the sidebar, click Server. Click the Config tab. The page starts with "Every configuration value stored on the Asterobot server. Changes apply live." Under it sit the filter, the counters and two buttons, then one card per group of settings. How settings are grouped Every setting has a key made of two parts, such as server.listenAddress. The part before the dot names the group, and each group gets a card, in alphabetical order of their names. The card's header shows the group's name, how many of its settings are listed, and how many of them are modified. Inside a card, each row shows the part after the dot, such as listenAddress, with everything about that setting: Part of the row What it shows The name The second part of the key. The copy button next to it, Copy key, copies the whole key, such as server.listenAddress. Modified You set this setting yourself. See Modified and default. Restart required Asterobot only uses a new value when it starts. See Restart required. The description What the setting does. The descriptions of the botmanager settings stay in English whatever language Asteroboard uses. Default: The value the setting has when nobody changed it. (empty) means empty text. The control Where you change the value: a switch, a list, a text box or Edit as JSON. The reset button Reset to default puts the default back. It's greyed out, with the tooltip Already the default, when the setting isn't modified. Find a setting Filter settings... keeps the settings whose key or description contains what you type, ignoring upper and lower case. The description counts, so typing https finds server.tls, whose description talks about HTTPS. Modified only hides every setting you haven't changed. The badge next to them counts what you see, such as "3 of 19 · 2 modified": 3 settings shown out of 19, and 2 modified in total. When nothing matches, the page says "No setting matches this filter." Change a setting The control depends on the kind of value: Kind of value Control When the change is saved On or off A switch As soon as you flip it. One of a few values, such as a log level A list As soon as you pick a value. Text or a number A text box When you press Enter or click outside the box. Leaving the box without changing the text saves nothing. Logins and passwords, like server.basicAuth Edit as JSON When you click Apply. A saved change goes straight into config.toml, and every Asteroboard connected to this Asterobot shows it. Unless the setting has the Restart required badge, Asterobot uses the new value right away. When a change can't be saved, Asteroboard shows Couldn't save with the setting's key, and the control goes back to the saved value. That happens, for example, when the value isn't of the kind the setting holds. Numbers A setting that holds a number only accepts a number. Anything else, an empty box included, shows That isn't a number and the box goes back to the saved value. Settings edited as JSON server.basicAuth holds a list of logins with their passwords, which a single text box can't show. Click Edit as JSON to open an editor under the row: Change the value, for example {"alice": "a long password"} for a single login. Click Apply. Cancel, or Hide JSON on the row, closes the editor without saving. If the text isn't valid JSON, Asteroboard shows That isn't valid JSON and leaves the editor open so you can fix it. Modified and default A setting becomes Modified as soon as you save a value for it, even if that value is the same as the default. Only modified settings are written in config.toml. That difference matters when you update Asterobot. A setting left at its default follows the new version: if the new version changes the default, the setting changes with it. A modified setting keeps your value, whatever the new default is. So only save a value when you really mean to keep it. The reset button undoes that choice: the setting goes back to its default, loses the Modified badge and leaves config.toml. Restart required A few settings are only read when Asterobot starts, and carry the Restart required badge: server.listenAddress, server.basicAuth, server.tls, botmanager.mitmSignInPort, botmanager.mitmSessionPort, botmanager.mitmBindHost and botmanager.mitmAdvertiseHost. When one of them changes while the page is open, an alert appears at the top: Restart to apply, "Some changed settings only take effect after asterobot restarts." To restart, stop Asterobot and start it again, as First launch shows. The alert also appears when the change came from somewhere else, such as another Asteroboard, and it stays until you reload Asteroboard, even after the restart. Warning server.listenAddress, server.basicAuth and server.tls change how Asteroboard reaches Asterobot. After the restart, Asteroboard may no longer connect with its current Server URL. Read Asteroboard on another device before you change them, and keep access to the computer Asterobot runs on. Reset settings You can reset at three levels: One setting: the reset button at the end of its row. One group: the reset button in the card's header, Reset this service's settings. It only appears when the group has modified settings. Everything: Reset all, at the top right. It's greyed out while nothing is modified. Reset all asks first, with Reset every modified setting? and "This puts 2 modified setting(s) back to their defaults." Click Reset all in that alert to go ahead, or Cancel. Asteroboard confirms with Settings reset. It does the same as the config reset command (Command line). If a reset fails, Asteroboard shows Couldn't reset the setting. Warning Once Asterobot is signed in to asterobot.net, website.token is a modified setting. Resetting it, alone, with the website group or with Reset all, signs Asterobot out. Asterobot then starts a new sign-in the next time it needs your account, or when you click Sign in on the account button. See Sign in with asterobot.net. Hidden values Two settings hold secrets and are never shown by default: website.token, the sign-in Asterobot uses on asterobot.net. Its box shows dots, and the eye button next to it reveals the value. server.basicAuth, the logins and passwords that protect Asterobot. Its default shows as dots, but Edit as JSON shows the logins and passwords in clear text. A setting Asterobot says nothing about is hidden the same way when its key contains token, password or secret. Don't reveal these values, or open server.basicAuth in the editor, while someone can see your screen. Getting help explains why. Settings not registered by any service A row that says "Not registered by any service", instead of a default, is a setting that config.toml contains but no part of Asterobot uses. It's usually left over from an older version, or a key typed by hand with a mistake in it. It has no effect. Its reset button removes it from config.toml. Reload all Reload all reads every setting from Asterobot again. The page normally keeps itself up to date, so you'll rarely need it. If the reload fails, Asteroboard shows Couldn't reload settings, which usually means it isn't connected to Asterobot. While the settings load, the page says "Loading settings...", and "No settings loaded yet." when Asteroboard has nothing to show. Edit config.toml by hand You can also change settings in config.toml with a text editor. Asterobot watches the file: save it, and Asterobot applies the change within a moment, exactly as if you had made it on the Config page, and Asteroboard updates. The terminal shows Config loaded from followed by the file's path. The file is in TOML format, with one section per group, and only holds the settings you changed. For example: [logger] cliLevel = "DEBUG" [server] skipOpenFrontend = true [server.basicAuth] alice = "a long password" Removing a line puts that setting back to its default. Files and folders shows where the file is on each system. If the file can't be read after your edit, for example because of a missing quote, the terminal shows the warning Failed to reload config from file and Asterobot keeps the values it had. Fix the file and save it again. Asterobot doesn't overwrite a file it can't read, not even when it stops. Where to go next Settings reference Files and folders

Asterobot has no user accounts of its own: whoever reaches its port is treated as you. That's fine while it only listens on your own computer, and it's the one thing to keep in mind before you let other machines in. Anyone who reaches Asterobot can do what you do Asteroboard does everything through Asterobot's port, the one in server.listenAddress. Anyone whose browser or program reaches that port, and gets past basic auth when you've set it, can do all of it too: Read every setting, including website.token, the sign-in Asterobot uses for your asterobot.net account, and the basic auth passwords themselves. Use your Ankama accounts: connect bots with them, send messages in the game as your characters, and disconnect the game you're playing. Run code on your bots: install packages from the marketplace with your asterobot.net account, write new ones in the editor, and play them. Watch your games: read bot consoles, chat and traffic, including IdentificationRequest, the message that opens a game session, once they tick it. Change or delete anything: settings, bots, accounts, packages and game versions. That includes opening the MITM ports to the network, or turning basic auth off. Shut Asterobot down. One thing stays out of reach. Asteroboard never receives your stored Ankama passwords or the Ankama sign-ins, so nobody can read them through Asterobot's port. They can still use them, by connecting your bots. What the defaults protect Asterobot's port and the two MITM ports all listen on 127.0.0.1, which only the computer running Asterobot can reach. On a shared computer, that still includes the other people who use it, and every program running on it. The MITM ports only open while a bot waits for your game. config.toml, which holds the asterobot.net sign-in and the basic auth passwords, is only readable by your own user on Linux and macOS. Asterobot writes it that way, and when it finds the file open to others, it restricts it again and prints Restricted the configuration file to its owner. There's no password and no HTTPS by default, because only this computer can reach those ports. Before you open it Go through this list before any other machine can reach Asterobot: Prefer an SSH tunnel. It keeps Asterobot on 127.0.0.1, encrypts the connection and only lets in people who can sign in to the machine. It's also the only option that keeps MITM mode working. See Asterobot on a remote machine. Otherwise, set basic auth, with a long password you don't use anywhere else. Turn on TLS, so that password and everything else don't cross the network in a readable form. Limit the port in your firewall to the devices that need it, and don't forward it from your router to the internet. Open only what you use. Leave botmanager.mitmBindHost on 127.0.0.1 unless Dofus runs on another computer. Check the result on Server > Status, from the device you connect with: Transport should read Encrypted (HTTPS), and Authentication should read Password protected. Basic auth and TLS both stop MITM mode. When you need MITM mode with Dofus or Asteroboard on another machine, use SSH tunnels, or keep the setup on a network you trust, as MITM across machines does. Basic auth server.basicAuth holds user names and their passwords. When it holds at least one, Asterobot asks for a user name and a password on every request to its port, from every browser and program. It takes effect when Asterobot restarts. Asteroboard on another device shows how to set it. What to know about it: The passwords are stored in plain text in config.toml, exactly as you typed them. Anyone who can read that file can read them, and so can anyone who gets in with one of them, on Server > Config. Nothing limits wrong guesses. Asterobot doesn't slow down or lock anyone out after failed attempts, so a long password matters. Without TLS, the password travels readable. The browser sends it with every request, and anyone who can watch the network between the browser and Asterobot can read it. It covers everything on the port, including the connection settings Dofus fetches in MITM mode. Dofus can't send a password, so MITM mode stops working. The browser asks for it when you open Asterobot's address, and Asteroboard then uses what the browser remembers. Browsers usually forget it when they close. TLS server.tls makes Asterobot's port speak HTTPS, so what goes between your browser and Asterobot can't be read on the way. It takes effect when Asterobot restarts. The certificate is self-signed, and it only covers localhost, 127.0.0.1 and ::1. Browsers warn about it the first time. Accept that warning only for the address of your own Asterobot. It's valid for 3 years, and Asterobot doesn't renew it. Asteroboard on another device explains where it's stored and how to replace it. It stops MITM mode, because Dofus fetches its connection settings over plain HTTP. The MITM ports The sign-in port (botmanager.mitmSignInPort, 5555) and the session port (botmanager.mitmSessionPort, 5556) exist for Dofus clients. They listen on botmanager.mitmBindHost, 127.0.0.1 by default, and only while at least one bot is waiting. What they accept: The sign-in port takes any Dofus client that connects, and passes its sign-in on to Ankama. Asterobot asks for nothing: Ankama checks the account. A waiting bot that isn't attached to an Ankama account takes the first session that arrives, and attaches itself to that account. A bot without an Ankama account keeps that attachment for good. The session port only takes a game session whose ticket came through the sign-in port, and each ticket works once. Any other connection is closed. Port 8080 answers Dofus's request for connection settings with Ankama's public settings, where only the sign-in address is changed. So when the MITM ports are open to a network, anyone on that network can send their own game through your Asterobot, and your waiting bot can end up attached to their account instead of yours. It then no longer takes your sessions: delete it and add it again (see MITM mode). Relaying a Dofus from another computer also means leaving port 8080 open without a password, with everything that allows. If someone got in If you think someone used your Asterobot without you: Stop Asterobot, or set server.listenAddress back to 127.0.0.1:8080 and restart it. Change the basic auth passwords, and every other place you used them. In Account Manager, click Disconnect on each Ankama account: Asterobot asks Ankama to cancel the account's sign-in, then forgets it (Account status and actions). If passwords were stored, change them on Ankama's side. Log out of asterobot.net from the account button, then sign in again. Logging out makes Asterobot forget its sign-in, but it doesn't cancel a copy someone else may have taken. Getting help explains how to reach the team. Check Library Manager, Bot Manager and Server > Config for anything you didn't do. Where to go next How the parts connect Accounts and safety

In MITM mode, short for man-in-the-middle, a bot relays the game you play. When Dofus and Asterobot share a computer, Asterobot edits one line of your Dofus folder by itself (MITM mode). When Dofus runs on another computer, Asterobot can't reach that file, so you make the change yourself and open Asterobot's ports to that computer. This page uses three computers: PC A runs Dofus, installed with the Ankama Launcher. PC B runs Asterobot. PC C runs Asteroboard in a browser. PC C is optional. Asteroboard can run on PC B, where the default settings work, or on PC A, which then connects the way PC C does. The address 192.168.1.20 stands for PC B's address on your network. How the game reaches Asterobot PC A: Dofus → PC B: Asterobot (8080, 5555, 5556) PC A: Dofus → Ankama's servers (everything else) PC B: Asterobot → Ankama's servers PC C: Asteroboard → PC B: Asterobot (SSH tunnel) Dofus on PC A reads the ConfigUrl line of its version file, and fetches its connection settings from that address: Asterobot's port 8080, on PC B. Asterobot answers with Ankama's real settings, where the sign-in server is replaced with its own sign-in port, 5555. Dofus signs in on port 5555 of PC B, and Asterobot passes the sign-in on to Ankama. When Ankama tells Dofus which game server to join, Asterobot replaces that address with its own session port, 5556. Dofus opens its game session on port 5556, and the waiting bot relays it to the game server. So PC A must reach three ports on PC B, all at the same address: the one Asterobot gives Dofus. Everything else Dofus uses still goes straight to Ankama. What you need Dofus 3 on PC A, installed with the Ankama Launcher. Asterobot on PC B, signed in to asterobot.net, with PC A's Dofus version downloaded and extracted in Game Manager, and a bot using that version. Your first bot walks through both. PC A able to reach PC B: on the same local network, or through port forwarding (see Firewall and NAT). 1. Check the version by hand On a single computer, Asterobot compares your Dofus version with its own copy, and refuses to wait when they differ. PC A's files are out of its reach, so nothing checks it here. On PC A, open Dofus_Data/StreamingAssets/version in the Dofus folder, and read the Version= line. The Ankama Launcher's usual folder is %AppData%\Ankama\Dofus-dofus3 on Windows and ~/.config/Ankama/Dofus-dofus3 on Linux. On PC B, check in Game Manager that this exact version is downloaded and extracted, and that the bot uses it. When they differ, Asterobot reads the game's messages with the definitions of another version, and nothing the bot shows or a package sees can be trusted. Check again after every Dofus update. 2. Open Asterobot to PC A On PC B, open Server > Config. Caution With these settings, every device on your network can reach Asterobot's port 8080 without a password, which gives full control of Asterobot, and can send its own game session to your waiting bot. Only do this on a network you trust. Security explains the risks. Change these settings: Setting Set it to Why server.listenAddress 0.0.0.0:8080 Dofus fetches its connection settings from this port. 0.0.0.0 also keeps 127.0.0.1 working on PC B, which the SSH tunnel from PC C uses. botmanager.mitmBindHost 192.168.1.20, PC B's address The sign-in and session ports then accept connections from your network. botmanager.mitmAdvertiseHost Leave it empty Empty means the same address as botmanager.mitmBindHost, which is right here. server.tls Off Dofus fetches its settings over plain HTTP. server.basicAuth Empty Dofus can't send a password. Set botmanager.mitmAdvertiseHost only when PC A has to use another address than botmanager.mitmBindHost: when botmanager.mitmBindHost is 0.0.0.0. That value means every interface, but it isn't an address anything can connect to, so Asterobot then tells Dofus to use 127.0.0.1, which only works on PC B; when PC A reaches PC B through NAT, with another address (see Firewall and NAT). Restart Asterobot on PC B: every setting in the table takes effect at the next start. If Dofus is also installed on PC B, in the folder named by botmanager.mitmGamePath, Asterobot still edits that copy whenever a bot starts waiting, and refuses to wait when that copy's version isn't its own. If you don't play on PC B, empty botmanager.mitmGamePath. That one applies without a restart. 3. Start waiting and copy the value for PC A In Asteroboard, open the bot's page and click Start waiting. The status turns to Waiting for your game client. Asterobot opens its sign-in and session ports and writes Ready for game clients in its log, in PC B's terminal and on Server > Console. That line lists the addresses in use. Check that the advertised address is PC B's, not 127.0.0.1. Copy the configUrl value of that line. With the settings above, it reads: http://192.168.1.20:8080/botmanager/mitm/dofus3.json The value is always built the same way: http://, the advertised address, a colon and the port of server.listenAddress, then /botmanager/mitm/dofus3.json. It stays the same as long as those settings don't change. With no Dofus on PC B, the log doesn't show Pointed the played game at Asterobot. That's expected: there's nothing on PC B to edit. 4. Edit the line on PC A Close Dofus on PC A, if it's open. Open Dofus_Data/StreamingAssets/version, in the Dofus folder, with a text editor. Find the line that starts with ConfigUrl=, and copy it somewhere safe. You'll need it to put the file back. Replace everything after ConfigUrl= with the value from step 3, and leave the other lines as they are: ConfigUrl=http://192.168.1.20:8080/botmanager/mitm/dofus3.json Save the file. 5. Play Start Dofus from the Ankama Launcher on PC A, sign in and choose your character. On the bot's page, the status turns to Connected to game server, as it would on one computer. Game sessions are matched with waiting bots by Ankama account, exactly as MITM mode describes. While its ConfigUrl line points at PC B, the Dofus on PC A only signs in when Asterobot runs on PC B with at least one bot waiting. When no bot waits, the sign-in port is closed, and when Asterobot is stopped, Dofus can't even get its connection settings. On one computer, Asterobot puts the line back at those moments. Across machines, that's up to you. Put the line back To play on PC A without Asterobot: Close Dofus. In Dofus_Data/StreamingAssets/version, replace the ConfigUrl= line with the original you saved. Save the file and start Dofus. If you lost the original line, take it from Asterobot's own copy of the same version on PC B, which Asterobot never edits. Its version file is in Asterobot's cache folder, under game/dofus/dofus3/windows/, then the version number, then Dofus_Data/StreamingAssets/version. Files and folders shows where the cache folder is. Control it from PC C PC C's browser has to reach Asterobot on PC B. From another device, that usually means HTTPS (Asteroboard on another device), but HTTPS stops MITM mode. Use an SSH tunnel from PC C to PC B instead: Make sure PC B runs an SSH server that accepts your sign-in. On PC C, run: ssh -L 8080:127.0.0.1:8080 user@192.168.1.20 In PC C's browser, open http://127.0.0.1:8080. Asterobot on a remote machine explains the tunnel in detail. Some browsers let Asteroboard reach http://192.168.1.20:8080 directly, once you allow access to your local network. If yours does, opening that address on PC C works without a tunnel, but many browsers refuse it. Without opening any port If PC A can sign in to PC B over SSH, a tunnel can carry the game as well, and Asterobot keeps every port on 127.0.0.1: On PC B, keep the defaults: server.listenAddress on 127.0.0.1:8080, botmanager.mitmBindHost on 127.0.0.1 and botmanager.mitmAdvertiseHost empty. Restart Asterobot if you had changed them. On PC A, open a tunnel for the three ports, and keep it open while you play: ssh -L 8080:127.0.0.1:8080 -L 5555:127.0.0.1:5555 -L 5556:127.0.0.1:5556 user@192.168.1.20 On PC A, set the ConfigUrl line to the value Asterobot prints with the default settings: ConfigUrl=http://127.0.0.1:8080/botmanager/mitm/dofus3.json Dofus on PC A then connects to 127.0.0.1, and the tunnel carries each connection to the same port on PC B. Ports 8080, 5555 and 5556 must be free on PC A, so no Asterobot can run there at the same time. The same tunnel gives PC A Asteroboard at http://127.0.0.1:8080. Firewall and NAT Firewall. PC B has to accept incoming TCP connections from PC A on three ports: the port of server.listenAddress (8080), botmanager.mitmSignInPort (5555) and botmanager.mitmSessionPort (5556). On Windows, the system may ask whether to let Asterobot communicate on your networks the first time it listens on them. Otherwise, add rules for these ports, limited to your local network. The sign-in and session ports only listen while a bot waits, so test the connection from PC A at a moment when one does. NAT. When PC A isn't on PC B's network, for example with PC B at home and PC A somewhere else, PC A reaches PC B through your router's public address. Then: On the router, forward TCP ports 8080, 5555 and 5556 to PC B. On PC B, set botmanager.mitmAdvertiseHost to the router's public address, since PC B's local address means nothing to PC A. Keep botmanager.mitmBindHost on PC B's local address, and restart Asterobot. Use the configUrl value Asterobot prints after that, which contains the public address. Caution Forwarding these ports puts Asterobot's port 8080 on the internet with no password, since MITM mode can't use one. Anyone who finds it controls your Asterobot, your bots and your accounts. Prefer the SSH tunnel above whenever PC A can use it. When it doesn't work What you see What to check The bot stays Waiting for your game client while you play on PC A The ConfigUrl line on PC A holds the exact configUrl value, Dofus was started after the change, PC B's firewall lets PC A through on the three ports, server.tls is off and server.basicAuth is empty. PC B's log shows A game client signed in that no bot is waiting for Your game went through Asterobot, but no waiting bot took it, because the bot is attached to another Ankama account. See MITM mode. Ready for game clients shows 127.0.0.1 as the advertised address botmanager.mitmBindHost is still 127.0.0.1, or it's 0.0.0.0 while botmanager.mitmAdvertiseHost is empty. Fix it and restart Asterobot. Dofus on PC A can't sign in No bot is waiting on PC B, or Asterobot isn't running. Start waiting, or put the original line back. Couldn't put the bot into waiting The causes listed in MITM mode, including a Dofus copy on PC B, in botmanager.mitmGamePath, whose version isn't the bot's. The bot connects, but what it shows makes no sense PC A's Dofus version isn't the one the bot uses. MITM problems covers more errors. Where to go next Security, for what the open ports allow. Many bots, to relay several Dofus clients.

Asterobot doesn't need a screen. It can run on a rented server, a Raspberry Pi in a cupboard or a PC in another house, while you use Asteroboard in your own browser. The examples use Linux, the usual system on servers, and the same ideas apply on Windows and macOS. Install it Asterobot is published for Linux on two kinds of processor: Asterobot_VERSION_linux_amd64.7z for Intel and AMD, and Asterobot_VERSION_linux_arm64.7z for ARM, such as a Raspberry Pi 4 or 5 or an ARM server. Run uname -m on the machine to find out which one you need: x86_64 means amd64, and aarch64 means arm64. On your own computer, download the archive from https://asterobot.net/files/category/3-asterobot/, then copy it to the machine, for example with scp. On the machine, unpack it and make it executable: 7zz x Asterobot_VERSION_linux_amd64.7z chmod +x asterobot Download Asterobot explains each step and how to check the download. Plan disk space for the game versions your bots will use: see Requirements. Start it without a desktop Start Asterobot from a terminal on the machine, such as an SSH session: ./asterobot It runs as it would on a desktop computer, with two differences. It can't open a browser. Asterobot tries to open Asteroboard as it starts, and the asterobot.net sign-in page when it needs you to sign in. On a machine without a desktop, it prints Failed to open frontend and Failed to open the web browser instead, and carries on. Neither one is a problem. Turn on server.skipOpenFrontend if you'd rather not see the first one. You can't reach it yet. Asterobot listens on 127.0.0.1:8080, which only the machine itself can reach. Leave it that way and use an SSH tunnel. Reach it through an SSH tunnel An SSH tunnel carries one port of the remote machine over to your own computer, inside your SSH connection. Asterobot keeps listening on 127.0.0.1, nothing new is opened to the internet, and your browser talks to 127.0.0.1 on your own computer, which Asteroboard is allowed to reach without HTTPS. On your own computer, open a terminal and run this, with your user name and the machine's address: ssh -L 8080:127.0.0.1:8080 user@server Any SSH client that can forward a port works too. Leave that connection open. As long as it's open, port 8080 of your computer leads to Asterobot on the machine. In your browser, open http://127.0.0.1:8080. Asterobot sends you on to Asteroboard, which saves that address as its Server URL and shows Server connected. When the SSH connection closes, Asteroboard shows Server disconnected. It keeps trying, and connects again by itself once the tunnel is back. If Asterobot also runs on your own computer, port 8080 is already taken there. Put another port on the left side of the tunnel, and open that one: ssh -L 9080:127.0.0.1:8080 user@server Then open http://127.0.0.1:9080. A browser keeps one Server URL at a time, so to switch between your two Asterobots, open the address of the one you want. Through a tunnel, Asterobot needs no password and no HTTPS: SSH already encrypts the connection, and only people who can sign in to the machine get through. Keep in mind that everyone with an account on that machine can reach 127.0.0.1:8080 too. If you turned server.tls or server.basicAuth on anyway, open https://127.0.0.1:8080 instead, and expect the certificate warning and the password prompt described in Asteroboard on another device. MITM mode needs both of them off. Or open the port Asterobot can also listen on the machine's public address, the way Asteroboard on another device sets it up on a home network: server.basicAuth with a password, server.tls on, server.listenAddress set to 0.0.0.0:8080, a restart, and the port allowed in the firewall. You then open https:// followed by the machine's address and :8080, from any device. Caution An open port on a server can be reached by anyone on the internet. Without a password, whoever finds it controls your Asterobot, your bots and your Ankama accounts. Never open the port without both server.basicAuth and server.tls, and limit it in the firewall to your own addresses if you can. See Security. SSH tunnel Open port Open to the internet Nothing more than SSH Port 8080 Who gets in People who can sign in to the machine Anyone with a password from server.basicAuth Encryption SSH server.tls Certificate warning None Once per browser Devices Those with an SSH client Any browser MITM mode Keeps working Stops working Sign in to asterobot.net On its first start, Asterobot has to be signed in to asterobot.net. It prints the link in the terminal, on the line after Website sign-in required. Please visit this link to authorize access to your account; the app will continue automatically once authorized. You can open it in any of these ways: Copy the link from your SSH terminal into your browser. Once the tunnel is open, click the account button at the bottom of Asteroboard's sidebar. It reads Sign-in pending, and opens the same link. Turn on website.showQRCode on Server > Config, and scan the QR code the terminal shows with the next sign-in code. Confirm on asterobot.net, and Asterobot carries on by itself. Sign in with asterobot.net explains the whole flow. Sign in your Ankama accounts Full socket bots on the machine sign in with Ankama accounts stored in that Asterobot. Manual sign-in works from wherever you use Asteroboard. Open Ankama sign-in opens Ankama's page in your own browser, and you paste the link back into Asteroboard. Nothing has to be installed on the machine. See Manual sign-in. Automatic sign-in starts a browser on the machine itself, so Chrome, Chromium or Edge must be installed there. It runs without a window by default, which works on a machine without a desktop. When Ankama asks for a person, you can't show that window on a server: sign in manually instead. See Automatic sign-in. MITM mode works with a remote Asterobot too, but your Dofus client runs on your own computer, where Asterobot can't edit any file: see MITM across machines. Keep it running Asterobot stops when its terminal closes, and ending the SSH session you started it from closes that terminal. Two common ways keep it running: A terminal multiplexer, such as tmux or screen. Start Asterobot inside it, detach, log out, and attach again later to read what it printed. A system service, such as a systemd unit on Linux, so Asterobot starts with the machine. Asterobot doesn't come with a service file, so you write one that runs the Asterobot program. Run it as the user you set Asterobot up with: Asterobot keeps its settings and data in folders of the user that runs it (Files and folders), and another user starts with none of them. Without a terminal in front of you, read what Asterobot prints on Server > Console in Asteroboard. See Status and console. Two more things matter on a machine you don't sit at: Shutdown server in Asteroboard stops Asterobot, and Asteroboard can't start it again. You'll need an SSH session, or a service set up to start it. When Asterobot starts again, after a reboot for instance, your bots come back disconnected, and nothing reconnects or plays on its own. Bring them online from Asteroboard. See Disconnect, delete and restart. To update Asterobot, replace the program file, as Updating Asterobot explains. Where to go next Security MITM across machines

Out of the box, only the computer running Asterobot can use Asteroboard. You can open it to the other devices of your home network: your phone on the sofa, a laptop in another room. For a machine that isn't on your network, such as a rented server, see Asterobot on a remote machine. The examples call the computer running Asterobot "the Asterobot computer", and give it the address 192.168.1.20 on your network. Use yours instead. Why it takes HTTPS Asteroboard comes from https://asteroboard.asterobot.net, an HTTPS page. Browsers don't let an HTTPS page send plain http:// requests, except to the device the browser runs on, such as 127.0.0.1. That exception is why the default setup works on the Asterobot computer, and why a phone pointed at http://192.168.1.20:8080 stays disconnected. Another device can still reach Asterobot in two ways: HTTPS on Asterobot SSH tunnel How it works Asterobot serves HTTPS on your network, behind a password The device's browser talks to 127.0.0.1, and SSH carries that to the Asterobot computer What it needs Nothing to install An SSH server on the Asterobot computer, an SSH client on the device Devices Phones, tablets and computers Mostly computers Certificate warning Once per browser None MITM mode Stops working Keeps working This page sets up HTTPS. The SSH tunnel is explained in Asterobot on a remote machine, and works the same way on a home network. Some browsers let an HTTPS page reach a plain http:// address on your local network once you give them permission. Not every browser does, so this page doesn't count on it. Warning HTTPS and a password both stop MITM mode from working, including for a Dofus client on the Asterobot computer itself. Dofus asks Asterobot for its connection settings over plain HTTP, without a password, and Asterobot refuses. If you play with a MITM bot, use the SSH tunnel instead. Before you start Find the address of the Asterobot computer on your network. On Windows, ipconfig shows it as "IPv4 Address". On Linux, ip addr lists it. On macOS, it's in the network settings. Keep the device on the same network as the Asterobot computer. Read Security. Once Asterobot listens on your network, everything connected to that network can reach it, which is why the steps below add a password. 1. Add a password The server.basicAuth setting holds user names and their passwords. When it holds at least one, Asterobot asks for a user name and a password on every request, from every browser, including the one on its own computer. In Asteroboard, open Server > Config and type basicAuth in Filter settings.... Click Edit as JSON on the basicAuth row. Replace {} with a user name and its password, each in double quotes: { "me": "a long password you use nowhere else" } For several people, separate the pairs with commas: { "me": "...", "alex": "..." }. Click Apply. The row now shows Modified and Restart required. If what you typed isn't valid JSON, Asteroboard shows That isn't valid JSON and keeps your text so you can fix it. If Asterobot refuses the value, Couldn't save appears. Caution Asterobot stores these passwords exactly as you type them, in plain text, in config.toml. Anyone who gets in with one of them can read all of them with Edit as JSON. Don't reuse a password from any other account. 2. Turn on HTTPS On the same page, find tls and turn it on. The row shows Restart required. The next time Asterobot starts, it serves HTTPS instead of HTTP on its port. If it has no certificate yet, it creates one first: The certificate is self-signed: Asterobot made it, not an authority your browsers trust. Every browser warns about it the first time. It only covers localhost, 127.0.0.1 and ::1. A browser that reaches Asterobot through 192.168.1.20 also reports that the certificate doesn't match the address. It's valid for 3 years, and Asterobot doesn't renew it. When it expires, stop Asterobot, delete the two files below, and start it again: Asterobot creates a new one. It's stored as tls/cert.pem, with its key in tls/key.pem, in Asterobot's data folder (Files and folders). The setting's description on the Config page mentions the cache folder, but the data folder is where they are. Asterobot uses whatever pair of files it finds there. If you have a certificate of your own for the address you use, in PEM format, you can put it and its key in place of these two files. 3. Listen on your network Find listenAddress, type the new value and press Enter: Value Who can connect 127.0.0.1:8080 Only the Asterobot computer. The default. 0.0.0.0:8080 Every network the Asterobot computer is connected to, and the computer itself. 192.168.1.20:8080 Only through that address. The Asterobot computer has to use it too, since 127.0.0.1 no longer answers. 0.0.0.0:8080 is the simplest. With a single address, the browser Asterobot opens as it starts goes to 127.0.0.1 and finds nothing there: open https://192.168.1.20:8080 yourself, or turn on server.skipOpenFrontend. Keep port 8080 unless another program uses it. 4. Restart Asterobot The three settings take effect when Asterobot starts again. Stop it with Ctrl+C in its terminal, or with Shutdown server on Server > Status, then start it the usual way (First launch). As it starts, Asterobot opens https://127.0.0.1:8080 in the Asterobot computer's browser, unless server.skipOpenFrontend is on. In a tab that was already open, Asteroboard shows Server disconnected until the browser has opened the https:// address once, because its Server URL still starts with http://. When it does, the browser warns about the certificate and asks for a user name and a password, the same as in step 6. 5. Open the firewall The Asterobot computer has to accept incoming connections on TCP port 8080. On Windows, the system may ask whether to let Asterobot communicate on your networks the first time it listens on them: allow it for private networks. Otherwise, add a rule for incoming TCP connections on port 8080 in your firewall, limited to your local network if it lets you. 6. Connect from the other device In the device's browser, open https://192.168.1.20:8080, with the Asterobot computer's address. Type https:// in full. The browser warns that the connection isn't private, or that the certificate isn't trusted. Check that the address is the Asterobot computer's, then choose to continue to the site. Most browsers keep that choice behind an option for advanced users. The browser asks for a user name and a password. Enter a pair from server.basicAuth. You land on Asteroboard. It saves https://192.168.1.20:8080 as its Server URL and shows Server connected. Your browser may also ask whether asteroboard.asterobot.net can access devices on your local network. Allow it, or Asteroboard can't reach Asterobot. Always open the address itself first, rather than typing it in Preferences straight away. The certificate warning and the password prompt only appear on a page you open. Requests from Asteroboard can't show them: they fail, and Asteroboard stays disconnected. 7. Check the connection On Server > Status, the card under the connection status sums up the connection of the device you're on: Line What it shows Server URL The address this browser uses. Version The version of Asterobot. Transport Encrypted (HTTPS) when the Server URL starts with https://, Not encrypted (HTTP) otherwise. Authentication Password protected when server.basicAuth holds at least one pair, No password otherwise. Preferences has a Server section too. Its Connection line shows Connected, Connecting… or Disconnected, and Test connection checks once more: Server reachable, with the round-trip time in milliseconds, or Server unreachable. Type the address yourself To set the Server URL by hand, for example on a device that has already accepted the certificate: Open Preferences and find Server URL in the Server section. Type the scheme, the address and the port, with nothing after them: https://192.168.1.20:8080. Press Enter, or click outside the field. Asteroboard connects to the new address right away. Click Test connection. A browser keeps one Server URL. To come back to an Asterobot running on the device you're on, open http://127.0.0.1:8080, or type that address the same way. When you come back later Browsers don't keep the password and the certificate choice forever. Most forget the password when they close, and some forget the certificate choice after a while. When Asteroboard shows Server disconnected on the device while Asterobot is running, open https://192.168.1.20:8080 again, as in step 6. Go back to the default On Server > Config, click the Reset to default button, the round arrow, on the rows of listenAddress, tls and basicAuth. Restart Asterobot. On the Asterobot computer, open http://127.0.0.1:8080. When it doesn't work What you see What to check The address doesn't load on the device Asterobot was restarted after the changes, the firewall allows TCP port 8080, both devices are on the same network, and the address starts with https://. Client sent an HTTP request to an HTTPS server. The address starts with http:// while server.tls is on. Use https://. The browser keeps asking for the password The user name and password must match a pair in server.basicAuth exactly. Asteroboard stays Disconnected, and Test connection says Server unreachable Open the address itself first, to accept the certificate and enter the password. A Server URL that starts with http:// is blocked by most browsers: use https://. The Asterobot computer shows Server disconnected after the restart Its Server URL still starts with http://. Open https://127.0.0.1:8080 there. Your MITM bot no longer receives your game HTTPS and the password stop MITM mode. Go back to the default, and use an SSH tunnel for the other device. Asteroboard can't connect covers other connection problems. Where to go next Security Preferences