Firefoux Dungeon in Dofus Retro uses an open progression structure. After solving Touchparak, the party defeats six groups and collects six distinct Firefacts before entering Peki Peki’s den.
The boss fights alone, yet invisibility, abundant MP, position swapping and six-cell pushes make the room dangerous. A dependable strategy places detection immediately after its turn, anchors it away from walls and validates all six objects.
Why run Firefoux Dungeon
Peki supplies sought-after Fabric, Magic Tail and Hair. The route also awards the Peki pet through its intended reward path. Firefoux experience makes repetitions attractive to parties able to handle varied resistance.
This dungeon has a broader intent than simply farming Peki Peki: access, all six chambers and quest inventory belong to the run. Preparation time is part of every victory’s true cost.
Feudala access and dungeon entrance
The entrance is in Feudala. Check that all accounts can reach the area, share a coherent Pandala starting point and avoid aggressive groups. The Pandala Village route supplies a reference for the first leg.
Navigation waits for every character before interaction. A multi-account route never lets its leader cross maps while a follower still loads the previous one.
Firefoux key and inventory gate
Every character brings a Firefoux Dungeon key. Check exact name and quantity rather than assuming the leader covers everyone. The Firefoux key recipe supports repeat preparation.
Reserve tracking capacity for six Firefacts and pods for drops. Bring invisibility detection, lock, MP reduction, pushes, healing and several non-Fire damage sources.
Prepare: one key each, Feudala access, six Firefacts to validate, detection, lock, MP control, collision protection and non-Fire damage.
Touchparak, grey tile and lever
The opening room has no ordinary monster group. Block Touchparak to guide her onto the grey tile, then operate the lever. Positioning and interaction require coordinated characters.
The script defines a blocker, destination and lever account. If Touchparak leaves the planned route, it recomputes instead of repeating moves. Door opening is confirmed before transition.
Clear all six cave rooms
The next area contains six distinct groups. Defeating each awards a different Firefact. Branch order may vary, but the final collection needs all six identifiers rather than assumed duplicates.
MoonBot maintains a set per account and selects the missing chamber next. It reads the awarded object before closing a branch. “Six victories” never substitutes for six unique Firefacts.
Zillas and random extreme weakness
Every group includes a Zilla. This flame has an extreme weakness in one random element, near -95%, while other paths resist more. Inspect it anew in every battle.
Compatible attackers remove it quickly. A mono-element party may need longer control, whereas a versatile group exploits the favourable colour immediately.
Zilla MP loss, healing and Vitality
Zilla removes MP, heals allies and grants them Vitality. Leaving it active extends the room and can save a target scheduled to die before its turn.
Attack through its weakness whenever possible. If no character covers that element, block lines or unbewitch only the dangerous bonus. Health forecasts include temporary Vitality.
Maho, Soryo and Yokai Firefoux
Maho, Soryo and Yokai families have different roles and resistance. One rotation across all six chambers wastes attacks.
Read resistance, range and active state before focusing. Zilla comes first when it can heal several allies; a mobile Firefoux rises when it threatens detection or healing roles.
Target order across six fights
Identify Zilla’s weak element first. If the party covers it, remove support. Otherwise finish one accessible Firefoux and contain the flame until a suitable line exists.
Do not spread damage. Every death removes an action, possible heal and locking zone. Save major protection for placements exposing multiple accounts.
Validate six Firefacts per account
Before the den, open every quest inventory and compare the six expected names. The Firefoux key must also be present at the required moment. Nobody crosses while incomplete.
If one object is absent, that account repeats the matching room with required support. Logs preserve chamber, result, Firefact and time, preventing six random replays.
Peki resistance and the element to avoid
Peki Peki has 100% Fire resistance. Fire attackers change path, provide support or control mobility. Allocate Air, Water, Earth or Neutral damage according to displayed values.
Make this change before entry because the boss is alone and offers no alternate target. Party boosts favour characters capable of dealing effective damage.
Transpekisation and invisibility
Transpekisation unbewitches Peki, turns it invisible, grants Agility and swaps it with a target while dealing Air damage. It often selects the same character, allowing a deliberate bait role.
Place a Sram, Ecaflip or other detection immediately after the boss in initiative. Store the swapped target, original cell and last known location. Detection cast too early expires before it matters.
Bark and Air poison pressure
Bark applies Air pressure similar to poison. An affected character stops serving as bait when projected health falls below threshold. Healing anticipates the next tick.
Air resistance and protection reduce danger, while Peki’s self-unbewitching can change buff timing. Track boss effects separately from character states.
Croutage, six-cell push and collisions
Croutage pushes six cells. Direct damage is modest, but wall collision becomes enormous, especially because Peki can repeat the spell several times on one target.
The bait never ends aligned with an obstacle inside six cells. Maintain an open retreat lane and recompute after every swap. A cell safe before Transpekisation may become lethal afterward.
Leap, abundant MP and locking
Peki combines many MP with Leap, so one removal source is insufficient. It remains susceptible to a prepared locking plan and frequently stays beside a character it can tackle.
Use the durable bait as an anchor, then layer MP reduction and obstacles. The locker retains healing access and avoids walls. Recalculate escape after Peki’s Agility bonus.
Recommended Peki combat sequence
Spread away from walls and establish bait in round one. After Transpekisation, record the swap, let detection act, then focus non-Fire attacks on the revealed cell.
Renew MP control, retreat lane and healing before secondary damage. When detection fails, no expensive spell targets a guessed cell. Control continues until new evidence appears.
Peki drops and pet reward
Fabric, Magic Tail, Hair and stones contribute to victory value. Link stacks to demanded recipes and use achievable prices. Displayed rarity does not guarantee a fast sale.
Record the Peki pet reward separately from resources. Confirm its presence and available pods on every relevant account before leaving.
Calculate full profitability
Cost includes key, Feudala travel, puzzle, six rooms, consumables, banking and failures. Measuring only time beside Peki greatly overstates yield.
Compare raw resources with crafting use. Experience series also report net XP and correctly consumed Firefact sets per hour.
Automate Firefoux Dungeon with MoonBot
MoonBot handles Touchparak as a state puzzle, then tracks Firefacts as a unique set per account. Rooms read Zilla’s weakness before assigning attackers.
Against Peki, the profile stores bait, last cell, detection, invisibility, wall distance and retreat lane. Drops and rewards are validated only after confirmed victory.
Frequent Firefoux Dungeon mistakes
- Operating the lever before Touchparak reaches the tile.
- Counting six wins without checking six distinct Firefacts.
- Ignoring Zilla’s random elemental weakness.
- Bringing almost exclusively Fire damage against Peki.
- Detecting before invisibility or attacking a guessed cell.
- Ending bait against a wall on Croutage’s axis.
Validation plan before repeated runs
Test a Touchparak deviation, every Firefact branch and an uncovered Zilla weakness. At the boss, force swap, invisibility and a push through an open lane.
The route passes when every account owns six unique objects, detection reveals Peki after its turn and no avoidable wall collision occurs. Increase loops under key, food, pod and defeat limits.
Botting breaches the game's terms of service and carries a sanction risk. No tool can guarantee that an account will never be banned.
