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.

Shield and two-factor authentication

Ankama Shield and two-factor authentication add a step when an account signs in, such as a code to type or a device to approve. Asterobot doesn't support these accounts in Full socket mode. They work in MITM mode, where you sign in yourself, in Dofus.

Not supported in Full socket mode

In Full socket mode, Asterobot has to get through Ankama's sign-in and then the game's login server with nobody there to help. It has nothing for the extra step these accounts need:

  • Asteroboard has no field for a verification code, and automatic sign-in only types the Login ID and the password.
  • When Asterobot identifies the bot on the game's login server, the Shield certificate it sends is always empty, and so is the certificate it gives Ankama when it asks for a game connection.

So even if such an account ends up showing Signed in, Full socket mode doesn't support it: don't use it for Full socket bots.

What you'd see

Asterobot has no message of its own for these accounts. What you meet depends on the step where Ankama stops:

  • Automatic sign-in fails. Asterobot's log shows ankama did not accept the sign-in (wrong password, a verification step, or a challenge raised after submitting), because the browser can't pass the verification step. See Automatic sign-in.
  • Manual sign-in happens in your own browser, where you can answer Ankama's verification yourself, so the account can reach Signed in.
  • Connecting a bot is where it stops. When Ankama refuses, the reason it gives is shown in the bot's Couldn't connect this bot alert. A refusal from the game's login server reads identification was refused: followed by Ankama's reason.

Bot doesn't connect lists the connection errors.

Use MITM mode instead

In MITM mode, short for man-in-the-middle, you start Dofus from the Ankama Launcher and sign in as usual, Shield and codes included. Asterobot sits between your game and Ankama's servers, and the bot relays the session your game opened. Asterobot never signs the account in, and you don't store it in Account Manager at all.

  1. Add a bot without an account, and choose Wait for my game client on its Connection tab. See Add a bot.
  2. Start Dofus from the Ankama Launcher and sign in with the protected account.

The bot then shows Connected to game server, and it can run packages like any other bot. Your first bot walks through this setup step by step, and MITM mode explains it in full.

The trade-off is that someone has to start Dofus and sign in for every session. Full socket and MITM compares the two modes.

Where to go next

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.