Aller au contenu
Afficher dans l'application

Une meilleure façon de naviguer. En savoir plus.

Asterobot

Une application plein écran sur votre écran d'accueil avec notifications push, badges et plus encore.

Pour installer cette application sur iOS et iPadOS
  1. Appuyez sur Icône de partage dans Safari
  2. Faites défiler le menu et appuyez sur Ajouter à l'écran d'accueil.
  3. Appuyez sur Ajouter dans le coin supérieur droit.
Pour installer cette application sur Android
  1. Appuyez sur le menu à trois points (⋮) dans le coin supérieur droit du navigateur.
  2. Appuyez sur Ajouter à l'écran d'accueil ou Installer l'application.
  3. Confirmez en appuyant sur Installer.

When Dofus updates

Asterobot doesn't follow Dofus patches on its own. Each patch is a new game version, and the version Asterobot already downloaded stays exactly as it was. Go through these steps after a patch, in this order. They matter most in MITM mode, where your bot's game version must match the Dofus you play. A bot that signs in on its own keeps the version set on it until you change it.

1. Check for a new version

  1. In Game Manager, open the menu of the version you use.
  2. Click Check for latest version.

Asteroboard answers Up to date or A newer version is available, followed in both cases by "Ankama's latest version is" and the version number. The same button is on the Information tab of the version's Game page.

In MITM mode, the Ankama Launcher updates your Dofus. MITM mode shows where to read the version you play.

2. Download and extract the new version

  1. Click Download a game.
  2. Keep the defaults, with latest in Version and Extract data after downloading checked. If the new version is missing from the suggestions, click Check for updates first.
  3. Click Download.
  4. Keep Asteroboard open until the new row shows Ready for bot, so the extraction starts on its own.

The new version gets its own row, next to the old one. Chunks Asterobot already stored for the old version aren't downloaded again. Download a game version covers every field of the dialog.

3. Look at the compatibility

Check the Compatibility column of the new row:

  • Compatible: your release of Asterobot was tested with this version.
  • Different version: it wasn't. The info icon next to the badge names the version Asterobot is tested with.

Different version doesn't block anything, but your bots may not work on that version yet. When Asterobot doesn't support the new version yet describes what you may see.

4. Move your bots

Repeat this for each bot that uses the old version.

  1. Open the bot's page. If the bot is connected, connecting or waiting for your game, click Disconnect. Its game version can't change while it's online: the Settings tab says "Disconnect this bot to change its account or its game version." and greys out the fields until you do.
  2. Open the Settings tab.
  3. Under Game version, choose the new version. If it's the tested version, the Use tested version button selects it in one click.
  4. Click Save settings. Asteroboard shows Settings saved.
  5. Bring the bot back online with Connect or Start waiting.

In MITM mode, click Start waiting only once your Dofus is up to date: while the two versions differ, the bot refuses to wait. Bot settings describes the rest of the Settings tab.

5. Remove the old version

Once no bot uses the old version, open its menu in Game Manager:

  • Delete frees the most space: the files, the extracted game data and the row go.
  • Uninstall deletes the files and keeps the row with its extracted game data.

Neither checks whether a bot still uses the version, so finish the previous step first. Manage game versions compares the two.

When Asterobot doesn't support the new version yet

Asterobot reads and writes the messages Dofus exchanges with its servers, and those messages change from one version to the next. Right after a patch, your release of Asterobot may not know the new version's messages yet. Here is what you can meet:

  • Different version in the Compatibility column, on the Information tab of the Game page and under Game version in a bot's settings.
  • A bot that signs in on its own doesn't connect. An alert titled Couldn't connect this bot appears at the top of its page, with the reason.
  • In MITM mode, your game is disconnected when it reaches the bot, and Asterobot's log shows Failed to relay a game session followed by the reason.
  • A script can't start, and its error begins with the game engine is not available:.

When your release of Asterobot is too old for the version the Asterobot team currently supports, the reason tells you to update Asterobot. In that case:

  1. Download the new release of Asterobot. When one is published, Asteroboard shows Asterobot update available with a View on asterobot.net button when Asterobot starts, and the terminal prints An Asterobot update is available.
  2. Update it as Updating Asterobot explains.
  3. Look at the Compatibility column again.

When the reason is only the game engine is not available, Asterobot couldn't get what it needs to read the game's messages at all, whatever the game version. Check that Asterobot is signed in to asterobot.net and can reach the internet, then try again. If it keeps happening, Getting help lists where to ask.

Script authors will find how to keep their scripts working through patches in After a game update.

Where to go next

Compte

Navigation

Recherche

Recherche

Configurer les notifications push du navigateur

Chrome (Android)
  1. Appuyez sur l'icône de cadenas à côté de la barre d'adresse.
  2. Tap Autorisations → Notifications.
  3. Ajustez vos préférences.
Chrome (Desktop)
  1. Cliquez sur l'icône représentant un cadenas dans la barre d'adresse..
  2. Select Paramètres du site.
  3. Find Notifications et ajustez vos préférences.