Impressionnant ! Ça m'a énormément aidé et ça marche du tonnerre. En plus, le vendeur est un vrai crack : il répond à la vitesse de l'éclair, il est super disponible et il m'a donné un sacré coup de main. Un vrai plaisir, tellement reconnaissant pour sa gentillesse et son aide ! 🙏🔥
Marketplace›Dofus Touch›Run Kamas Astrub 100% Astrub Dofus Argenté TDM
Run Kamas Astrub 100% Astrub Dofus Argenté TDM
by Maspa 3.7 · 3 reviews 61 downloads
Description
Run Kamas Astrub
The script that turns your Sacriers into kamas machines.
Run Kamas Astrub takes a character right after the tutorial, completes all of Astrub's content (quests, dungeons, TDM, companion, sets), sends all the kamas and all the items to the banker, notifies you on Discord, then starts over with a new character. Without intervention.
Designed to run on as many bots as possible, as fast as possible, with the Router, the Controller and the native Controller (optional) provided for free.
🆕 What's new in this version
- 5-character limit handled per account (not per server): creation is no longer refused (
TooManyCharacters). Full account: the finished character is deleted and replaced in the same operation. - Multi-server rotation (optional): an achievement only gives its rewards (kamas + items) to the first character of the account on a server. The script can make a character on each open server (Tiliwan, Kelerog, Blair, Talok) before rerolling in a loop on the server of your choice.
- Pre-run without kamas: short of the 740 kamas for the zaap to Bélladone? The bot checks the bank only once, otherwise it farms the kamas itself (2 monsters max below level 25, 3 afterwards) instead of looping.
- More stable Duo: no more bot disconnection/reconnection in the group system (they used up the cap of 8 reconnections per 24 h and took the bot offline for hours). After repeated failures, the duo pauses and then re-forms, with the bot still connected.
- Native Controller (optional): account supervision can run in the Controllers tab of MoonBot, without occupying a bot. The classic Controller then keeps only the banker role.
- Better diagnostics: refusals (character creation, group, script launch, configuration loading) now display their reason in the console.
📊 Results: average of 100 tests
| Metric | Average result |
|---|---|
| Bot level at the end of the run | 52 (first bot) |
| CASH kamas generated per account (first run, otherwise half) | 100 000 and change |
| Duration of a full run | ≈ 2 hours (with speedhack) |
| Average yield | ≈ 50 000 kamas / hour / account |
| Actual results for 100 bots (end of run) | ≈ 10M kamas cash + ~5M in resources |
99% WINRATE
Average of 100 full runs. The yield is calculated from the figures above.
Results add up from one account to the next: the more bots you launch, the more production climbs.
⚙️ What the script does, from start to finish
1. It resumes after the tutorial
The script plugs into the quest « Prochain arrêt : Astrub ! », right after the Incarnam tutorial (prerequisite: having completed the Albuera quest). It reaches Astrub on its own and carries on.
2. It works through 100% of Astrub's quests
- 40 quests and quest chains handled, including the devotion quests.
- More than 320 objectives coded one by one: movements, dialogues with NPCs, interactions with scenery elements, targeted fights, drop collection, purchases...
- It reads the actual state of your quests on each cycle. After a crash, a disconnection or a restart, it picks up where it left off.
3. It levels up to level 40 and gets its set and its companion
It levels the character up to level 40, equips itself, then completes the companion quests, equips the companion and disables its manual control so that it does not get in the way of fights.
Pre-run (zaap to Bélladone): the trip costs 740 kamas (340 outbound + 340 return). If the character does not have that amount, it opens its bank only once; if it is empty or inaccessible, it farms the kamas with light fighting (2 monsters max below level 25, 3 from level 25) until it has enough to take the zaap, then continues up to level 40.
4. It crafts its Piou set (skip if it already has the tanière sets)
- The script unlocks the profession required, goes to the workshop and crafts the Piou set suited to the class.
- It buys the ingredients at the HDV: the price is re-evaluated before each purchase, with a maximum price, so as to never buy at an aberrant market price.
- If it is short of kamas, it farms the resources itself on the Pious (feathers, seeds) instead of staying stuck.
- It equips the result.
- Skips an item if it could crash the run.
5. It chains the 4 Astrub dungeons… as a duo
Champs, Ensablé, Tofu and Gobball Dungeons: 3 rooms each, 12 rooms in total.
- The bots group up by themselves in each room: no group configuration to set up.
- The system handles collisions (two bots creating a group at the same time), enforces a strict limit of 2 players (Duo), and checks that the partner is actually in the group before each fight.
- Both bots must be on the same server: the script ignores bots from another server, even on an identical map.
- If the duo formation drags on, a full reset (group deleted, party left) restarts the formation after a pause. No disconnection: the bot stays connected.
- The group is disbanded at the end of each dungeon, including in the game.
- Never a dungeon fight solo, or with more than a duo.
6. It fights with an AI dedicated to the Sacrier
The script controls each fight turn itself, thanks to a very advanced AI for the Sacrier class:
- Smart placement on the starting grid.
- Spells handled: Pied du Sacrieur, Attirance, Épée Volante (with summon control), Coagulation, Châtiment Vitalesque and Châtiment du Martyr.
- Calculation of lines and distances before each attack, and checking of the path before an attraction.
- Tactical fight against the Chevalier de l'Automne: special AI to handle the last tactical fight.
7. It runs the TDM quests in parallel
The TDM quests (monster hunts in Astrub, including the field monsters and other zones) are started during the progression, so as not to lose any time.
8. It finishes, hands everything over to the banker and starts again
- It confirms the claiming of all achievements at the end of the journey.
- It goes to the Brakmar Militia using a Brakmar potion, or buys one at the HDV if it has none.
- It trades with the banker of its server: all the kamas and all the items, equipped and unequipped.
- The banker sends a Discord notification with the kamas received for one run and the accumulated total.
- Depending on your choice (
FIN_DE_RUN):REROLL: creation of a new Sacrier, and the cycle starts again. The script counts the characters across the whole account (limit of 5): as long as there is room, the finished character is kept; once the account is full, it is deleted and replaced in the same operation.GARDER: simple disconnection, the account is kept.
- With
ROTATION_SERVEURS = true, the new character is created on the next server where the account does not yet have a character (Tiliwan → Kelerog → Blair → Talok), in order to collect all the achievement rewards of each server, then the script rerolls in a loop on theSERVEUR_BOUCLEserver.
🛡️ Built to run unattended
- Automatic resume at any time thanks to reading the state of the quests.
- Death handling (very rare, but not impossible): the bot finds a phoenix, resurrects and sets off again.
- Protections against API errors, especially right after a map change, to avoid crashes.
- Robust HDV: prices reloaded before each purchase, retries, price ceiling.
- Absent banker: the script connects it itself and retries until it is available.
- Failed trade (banker busy): new attempt every 5 seconds.
- Secured reroll: the creation is never requested again in a loop, a refusal from the server is remembered, and you are alerted on Discord if the reroll fails after 3 attempts.
- Precise tracking in the console:
[DUO],[BANKER],[FIN],[REROLL],[PRERUN]… to know at any time what each bot is doing.
🚀 Large-scale automation
With the Router and the Controller (free), your accounts become a production line (literally a Kamas generator):
New: the native Controller (mooncontroller, optional) does the same supervision from the Controllers tab of MoonBot, without occupying a bot. The classic Controller is then only used as a banker.
✅ Good to know before buying
- Required class: Sacrier. The combat AI is specific to this class, and the reroll recreates a Sacrier.
- One banker account per server is required to collect the kamas, otherwise a house.
- Dungeons are done with 2 players: launch at least 2 bots on the same server. With an even number of bots, the duos form naturally.
- 5 characters maximum per account (all servers combined): the script handles it on its own.
- With
FIN_DE_RUN = "REROLL", if the account is full, the character is deleted at the end of the run, after the trade with the banker. Run your first tests withGARDER. - MoonBot v558 or newer recommended: more reliable stops (no more cascading stops) and refusal reasons displayed in the console.
📎 Provided for free
- Router: routes each account to the right script.
- Controller: runs your accounts 24 hours a day and acts as banker.
- Native Controller (
mooncontroller): account supervision from the Controllers tab, optional.
Instructions
Installation (single bot)
- Subscribe to add the script to your library.
- Open the Bot tab, select the character and then the Run Kamas Astrub script.
- Open the parameter block at the top of the script and fill in your banker (see the Parameters section).
- Prepare your server's banker account: connected, in game, and placed on the Brakmar Militia map (
13631488). - Launch the script on your character.
Important: dungeons are done with 2 players. A bot launched alone progresses normally up to the first dungeon, then waits indefinitely for a Duo in the room (
[DUO] Attente du Duo sur cette map...). For a full run, launch at least 2 bots on the same server, in the same MoonBot. They group up automatically. Two bots on different servers do not group up, even on an identical map.
No combat setting is needed: the script itself activates the Script tactic.
MoonBot version: use v558 or newer (“Update” button). This version makes bot stops more reliable (no more cascading stops) and displays the reason for refusals in the console. After the update, your bots stop: restart them.
Starting point
- Class: Sacrier.
- Progression: Albuera tutorial completed.
- Map: no starting map is required. The script reaches the NPCs and the quest zones on its own.
- Banker: a dedicated account on the same server, placed at the Brakmar Militia (see above).
- Servers: the script is set up for servers 530 (Tiliwan), 531 (Kelerog), 532 (Blair), 533 (Talok). For any other server, add a line in the
BANQUIERStable (see the Parameters section).
Parameters
To be set in the parameter block, at the top of the script.
| Parameter | Recommended value | Role |
|---|---|---|
BANQUIERS | One line per server: email + banker's UUID | Lets the script connect the banker if it is offline, read its state and start the trade. |
WEBHOOK | URL of your Discord webhook | Destination of the “accumulated kamas” notification sent after each trade. |
FIN_DE_RUN | "GARDER" to test, "REROLL" in production | GARDER: disconnection at the end of the run. REROLL: creation of a new Sacrier (deletion of the finished character if the account is full). |
ROTATION_SERVEURS | false (default) or true | true: before rerolling on the same server, the account creates one character on each open server to collect all the achievement rewards. Works with FIN_DE_RUN = "REROLL". |
SERVEUR_BOUCLE | 530, 531, 532 or 533 | Server on which the account rerolls endlessly once all servers are done (only with the rotation). |
Configure the banker for each server
In the BANQUIERS table, replace the two values on the line for your server ([530] Tiliwan, [531] Kelerog, [532] Blair, [533] Talok):
- First value: account name (email) of the banker.
- Second value: the banker's identifier (UUID) in MoonBot.
For a server that is not in the list, add a line [XXX] = { "e-mail", "uuid" }, (and its name in ROTATION_IDS / ROTATION_NAMES if you want to include it in the rotation).
Warning: if the server is not recognized, the banker is disabled and no trade takes place. With
FIN_DE_RUN = "REROLL", the script will stop; setFIN_DE_RUN = "GARDER"to continue the run. Always check this configuration before going to production.
Multi-server rotation in practice
An achievement only gives its rewards (kamas and items) to the first character of the account on a server; the following ones only earn experience. With ROTATION_SERVEURS = true:
- The script looks at which servers the account already has a character on.
- The next character is created on the first open server where the account does not have one yet (order 530, 531, 532, 533).
- When all servers have their character, the account rerolls in a loop on
SERVEUR_BOUCLE.
A server is skipped by the rotation if it is closed or if its banker is not configured (UUID still xxxxx-...): configure the banker of each server you want to include. No reserve of 1000 kamas is kept in the bank when the next character goes to another server (the banks are specific to each server).
The 5-character limit
The MoonBot/Dofus Touch limit is 5 characters per account, all servers combined. The script adds up the characters from all servers:
- There is room left: the finished character is kept and a new Sacrier is created.
- Full account: the finished character is deleted and replaced in the same operation.
- Unknown counts: as a precaution, the script treats it as a full account (it never exceeds the limit). It runs a scan of the servers only once (one reconnection).
Automating across as many bots as possible (Router + Controller)
This is where Run Kamas Astrub takes on its full value: dozens/hundreds of accounts running in a loop with no intervention. Follow these steps in order.
What you need in your library
| Script | Role |
|---|---|
| Run Kamas Astrub | The main script (this one). |
| Router | Chooses which script to launch on each account. |
| Controller | Connects, relaunches and acts as banker. |
| mooncontroller (optional) | Native Controller: supervises the accounts from the Controllers tab, without occupying a bot. |
| The Albuera tutorial script (offered for free by Maegal in the marketplace) | Used to get through the tutorial for rerolled characters. |
Step 1: Prepare the bankers
- Create one banker account per server, on the same server as your farm accounts.
- Place each banker at the Brakmar Militia (
13631488). - Note down the identifier (UUID) and the account name of each banker.
Step 2: Configure Run Kamas Astrub
Fill in the BANQUIERS table and WEBHOOK (see Parameters). Keep FIN_DE_RUN = "REROLL" for the full loop. Enable ROTATION_SERVEURS if you want the multi-server rotation.
Step 3: Configure the Router
Open the Router and check its exact names:
| Router parameter | Value to set |
|---|---|
SCRIPT_MAIN | The exact name of Run Kamas Astrub as it appears in your library (capital letters, spaces and hyphens included) |
SCRIPT_TUTO | The exact name of your tutorial script |
CONFIG_MAIN / CONFIG_TUTO | The exact name of the configuration to apply before each script (dashboard library), or "" to load none |
QUETE_COMMUNE / STEP_MAIN / OBJECTIFS_MAIN | Change nothing: 4282, 4964 and 14024, 14048, 14040 are already set for Run Kamas Astrub |
If a configuration cannot be found, the console now displays the reason:
[ROUTER] Configuration '…' NON chargee : …. The script then starts with the current configuration.
Step 3b: Configure the Controller
Open the Controller and check:
| Controller parameter | Value to set |
|---|---|
SCRIPT_ROUTER | The exact name of the Router in your library (by default router) |
SCRIPT_MAIN | The exact name of Run Kamas Astrub (used for the direct relaunch, see below) |
BLACKLIST | The identifiers (UUID) of all your bankers and other bots already running a different script, otherwise the Controller would try to control them |
WHITELIST | Empty, to control all the other accounts |
WEBHOOK | Your Discord webhook URL |
SUPERVISER | true (default): the Controller supervises the accounts and acts as banker. false: banker only (to be used with the native Controller) |
Advanced settings (recommended default values):
| Parameter | Default | Role |
|---|---|---|
STUCK_AFTER_S | 180 | An account that is “connected” but not in game for more than N seconds is considered stuck (24 h reconnection cap, cooldown after authentication error…): the Controller disconnects it and then reconnects it manually. A manual reconnection does not count toward the cap of 8 automatic reconnections per 24 h. |
STUCK_MAX_KICKS / STUCK_BACKOFF_S | 3 / 1800 | After 3 manual reconnections without getting into the game, the account is paused for 30 minutes and you are alerted on Discord. |
MAIN_FALLBACK / QUICK_DEATH_S | true / 60 | If the script launched by the Router stops less than 60 s after starting, the Controller relaunches Run Kamas Astrub directly (without going through the Router). If it stops again, it goes back through the Router. |
A misspelled script name is the number one cause of failure. Copy it from your library rather than retyping it.
Step 4: Launch the Controller
- Select the banker account in the Bot tab.
- Choose the Controller script, then launch it.
- Only one Controller per banker is needed: if you have one banker per server, launch it on each one.
Your farm accounts have nothing to do: the Controller connects them (if it does not, it is probably because it does not know them yet; connect them only the first time and relaunch), launches the Router, which launches the right script.
Option: native Controller (mooncontroller)
The native Controller does the supervision (connection, launching, unblocking of accounts) directly in the Controllers tab of MoonBot: it does not consume a bot and relaunches itself. The classic Controller is then only used as a banker.
- In the Controllers tab, create a Controller and paste the mooncontroller script.
- In its editor, tick your farm accounts in the write scope and do not tick the bankers (they are also in the script's
BLACKLIST). - Check
SCRIPT_ROUTER,SCRIPT_MAINandBLACKLIST(same names as for the classic Controller). - In the classic Controller (the banker's one), set
SUPERVISER = false. - Start the native Controller. Never run both supervisions at the same time: they would get in each other's way.
Step 5: Check that everything is running
In the console, you should see the following go by, in this order:
| Message | What it means |
|---|---|
[CTRL] … deconnecte -> connexion... (or [MOON] … deconnecte -> demarrage) | The Controller connects an account. |
[CTRL] … inactif -> lancement 'router' (or [MOON] … 'router' lance) | The Controller launches the Router. |
[ROUTER] Tutoriel termine -> lancement de '…' | The Router has chosen Run Kamas Astrub. |
[BUILD] vX.X.X | The script is launched (loaded version). |
[PRERUN] … | The bot prepares the zaap to Bélladone (bank, kamas farming). |
[DUO] Combat duo ! | A duo has formed in a dungeon. |
[BANKER] Echange termine : … kamas, … item(s) | The banker has received the loot. |
[REROLL] Compte : X/5 persos … | The script has counted the account's characters and chosen the next server. |
[FIN] Reroll : … | The cycle starts again (creation, or deletion + recreation if the account is full). |
Sizing your fleet properly
- Aim for an even number of bots per server: an odd bot would wait for a Duo at the dungeon.
- Your bots must be in the same MoonBot and on the same server in order to group up.
- Launch them in widely spaced waves if you have hundreds of bots per server: the more they progress at the same pace, the more some maps will be filled with too many Sacriers XD.
Troubleshooting
| Symptom in the console | Probable cause | Solution |
|---|---|---|
[DUO] Attente du Duo sur cette map... | Only one bot has reached the dungeon | Launch a 2nd bot on the same server, or wait for another bot to arrive |
[DUO] … est sur la meme map mais sur un AUTRE serveur … | The partner is on another server | Both bots of a duo must be on the same server |
serverId '…' non reconnu or banquierNDC non défini | Your server is not in the BANQUIERS table | Add a line [XXX] = { "e-mail", "uuid" }, (see Parameters) |
Impossible de connecter le bot Banquier | The banker account does not respond | Check the email and UUID in BANQUIERS, then launch the Controller on the banker |
Impossible d'effectuer un échange avec le banquier | Banker busy (let it retry a few times), badly placed or script stopped | Check that it is at the Brakmar Militia and that the Controller is running |
[CTRL] … echec lancement '…' : | Incorrect script name, or launch refused | Read the reason; fix SCRIPT_ROUTER / SCRIPT_MAIN (Controller) or SCRIPT_MAIN / SCRIPT_TUTO (Router) |
[ROUTER] Configuration '…' NON chargee : … | Configuration name not found or duplicated | Fix CONFIG_MAIN / CONFIG_TUTO (exact name from the library) |
Creation refusee par le serveur: TooManyCharacters | The account already has 5 characters (all servers combined) | Nothing to do: the script switches on its own to deletion + recreation |
[FIN] Echec createCharacter … : | Creation refused by MoonBot | Read the reason; after 3 attempts the bot disconnects and you are alerted on Discord |
Cap reconnexions 24h atteint (8/24h) | The bot has used up its automatic reconnections | The Controller disconnects it and then reconnects it manually after STUCK_AFTER_S seconds |
[CTRL] … bloque hors jeu depuis … s | Account connected but not in game (cap, authentication error) | Automatic: manual reconnection. After 3 failures, 30 min pause + Discord alert |
Loop router → runKamasAstrub arrete | Cascading stops from older versions of MoonBot | Update MoonBot (v558+); otherwise MAIN_FALLBACK relaunches Run Kamas Astrub directly |
| The Controller does nothing on an account | Account on the blacklist or missing from the whitelist | Fix BLACKLIST / WHITELIST |
Tips
First launch a short session with 2 bots and
FIN_DE_RUN = "GARDER"to check the banker, the trade and the Discord notification. Once everything is validated, switch toREROLLand let it run.
- Do not touch a bot during a run (movements, fights, groups): the script would not always recover.
- Give each account an alias in MoonBot to read the logs easily.
- Check your Discord channel regularly but mute it: each trade leaves a trace there with the accumulated total, risk of Discord message spam.
- The Discord webhook is a secret: do not share it (screenshot, copy of the script…). Anyone who has it can write in your channel.
The detailed settings and the script itself are in the app, once the script is in your library.
What’s new
- Version V3.4October 24, 2026
test
- Version V3.3October 24, 2026
Fix recréation
- Version V3.2October 23, 2026
- Prérun : le zaap vers Bélladone ne demande plus que 370 kamas (aller seulement). Le retour se paie avec les kamas gagnés en montant niveau 40.
- Prérun : si le bot a déjà 370 kamas, il part directement, sans ouvrir la banque.
- Prérun : la banque n’est plus rouverte (50 kamas à chaque fois) après une relance du script, grâce à une marque dans la console.
- Nouveau paramètre ALIAS_ECRASER (true par défaut) : le statut remplace toujours l’alias, sauf s’il commence par Banker. Avec false, un alias personnalisé est conservé.
- Version V3.1October 23, 2026
- Plusieurs banquiers par serveur : seul le principal se déclare dans BANQUIERS (alias ou UUID), les helpers …1, …2 sont détectés automatiquement.
- Si le banquier est occupé (errorType=2), absent ou hors ligne, le bot essaie le suivant, puis retente le principal.
- Le banquier se déclare par alias : plus besoin de l’e-mail.
- Le statut du run s’écrit dans l’alias du compte (actualisez la page Ctrl + F5 si vous ne les visualisez pas) : [PRE], [En Cours...], [BANQUE], [REROLL], [FIN] (ALIAS_STATUTS, ALIAS_NOM). Un alias personnalisé n’est jamais écrasé.
User reviews
Avant l’achat, on m’avait également indiqué que je pouvais faire jusqu’à 5 runs par jour. Une fois que j’ai acheté le script et tout le reste, on m’a finalement dit que c’était seulement 1 run compte. Ce n’est pas du tout ce qui m’avait été présenté au départ.
Le pire, c’est que maintenant le vendeur ne répond même plus à mes messages, alors que mon abonnement continue de tourner. Je perds donc du temps et de l’argent sans pouvoir utiliser correctement ce que j’ai acheté.
Je ne recommande absolument pas ce vendeur. Les informations données avant l’achat ne correspondent pas à ce qui m’a été expliqué après le paiement, le script ne fonctionne pas correctement pour moi et le support ne répond plus.
Je conteste plusieurs points de cet avis, notamment les conditions (nombre de runs, utilisation du proxy), qui sont celles indiquées avant l'achat. Nous avons échangé à plusieurs reprises pour te guider, mais ce type d'outil demande une certaine prise en main technique, et il se peut qu'il ne corresponde pas à ton profil (fish brain qui oublie tout au bout de 2 minutes max). Je suis en déplacement professionnel ces derniers jours, ce qui explique mon retard de réponse, et je m'en excuse. Malgré que je sois en déplacement, je fais de mon mieux, et ce sera bien meilleur une fois rentré. T'es pas le seul, sauf que t'es le seul à te plaindre sans donner aucune raison ni bug que je dois fix, contrairement aux autres dont je corrige les problèmes dans la journée au plus bref délai (check l'historique des mises à jour). Pour finir une fois pour toutes, je procèderai dès mon retour au remboursement complet. Je te souhaite une bonne continuation :)
Je tiens à remercier Maspa pour ce beau projet qui gère tout en un seul clic. Le script s'occupe de l'intégralité du processus, du dépôt jusqu'au retrait, avec succès et sans aucune intervention nécessaire. Je recommande vivement !
This script runs in MoonBot, the cloud Dofus Touch bot: nothing to install, your accounts play on our servers.
From the same creator

Controller Multi-account control + Bot Bank
MMaspa
The Controller runs on a dedicated account (a banker for example), connected permanently. It fulfills two missions at once: Supervisor: it monitors…
View details →
Router Automatic script dispatcher
MMaspa
The Router is a small single entry-point script that decides, for you, which script to launch on an account depending on its progress in the game.…
View details →PROFESSION PACK
MMaspa
Proxy + free accounts to come with the script (permanent subscription only) Before launching the script, read all the features carefully. In short…
View details →
HDV AUTO: Selling & Update Inventory + Bank + House
MMaspa
Are you looking for a convenient way to manage the sale of your resources, consumables or runes in Dofus? Discover our script for managing your…
View details →More Dofus Touch scripts
All Dofus Touch scripts →
Gobball Dungeon (bank return + hdv key purchase)
KKamas-Touch
Automatic loop: The script chains the Gobball Dungeon without interruption. Once launched, it runs on its own and restarts each run automatically…
View details →
Fields dungeon (return to bank + hdv key purchase)
KKamas-Touch
Automatic loop: This script chains Gobball Dungeons without interruption. Once launched, it runs on its own, looping this dungeon automatically…
View details →
Dofus Touch Tutorial
MMoonBot team
The Albuera tutorial completed for you, up to the arrival in Astrub. The script chains the six tutorial quests: Bien débuter, Les indésirables…
View details →Piwi Farm Script in a Loop (Multi-Account / Group)
MMewRox
Need feathers in bulk or an XP boost for your new characters? This script automates Piwi farming in a loop for your team in the starting zones. It's…
View details →