Dépannage

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, o

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 li

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

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

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 Setting

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

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 Res