Troubleshooting

What to check when Asteroboard shows Server disconnected, when Asterobot stops as soon as it starts, or when another device can't reach it. 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

Fix an asterobot.net sign-in code that doesn't go through, and an Ankama account that won't sign in automatically or by hand. 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 explain

Why a bot can't be added, fails to connect, stays stuck on a state, or connects in Full socket mode without ever entering the game, and what to do about each. 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 rea

Fix a bot that can't start waiting, a game that never reaches its bot, a Dofus that can't sign in, and scripts that misbehave on a relayed session. 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 expla

What the messages about packages mean and what you can do, when a package won't install, won't start, stops with an error or won't update. 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 wit

Fix a game version that won't download, stops with Failed, never becomes Ready for bot, or fails to extract its game data. 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 t

Pick the smallest reset that fixes your problem, from Asteroboard's browser data to Asterobot's folders, and know exactly what each one deletes and keeps. 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 ol

Why a bot does nothing in a fight or is disconnected during one, passes its turns, plays a profile you didn't pick, keeps refusing actions or ignores your clicks on a relayed session, and what to do about each. When the fight module doesn't play the way you expect, two places tell you why. The bot's Console tab says when a fight starts, whether the module plays it, and every action it sends. The Turn log on the Fight tab keeps every decision of the last 10 fights, with what each one counted (Th