DEVENIR RICHE AVEC LES RUNS CAUCHEMAR 3 SUR DOFUS

Storyline (context)

• The video is about Dofus “Nightmare 3” dream runs and how the creator farms them for profit.
• There’s no narrative storyline focus; instead, the “story” is the progression through waves in Nightmare 3 (boss mechanics, wave-specific constraints, and end-of-run survival).

Gameplay highlights / what the creator is doing

• Reason for playing Nightmare 3: the dreams now have permanent death, making fights more improvised and often longer, but also giving the player more time to think.
• Run goal: maximize kamas/bribes while maintaining a near-100% success rate by adapting to each wave and avoiding defeats (defeats slow farming the most).
• Representative “legit” fight shown: the creator demonstrates a full Nightmare 3 wave progression and explains what makes certain waves manageable or dangerous.

Profitability & run metrics (key points)

• They compare performance since boss nerfs (e.g., a “Menou/Me… torque nerf”) to avoid distorting data.
• Variance in number of waves per run: about 19–35 waves, depending on factors—especially the Domi / Domi Visi effect and when the “solar arrives” (timing-dependent).
• Average kamas per run: roughly ~12,000 kamas bribes per character per run, translating to about ~50 million kamas on their server (as stated).
• Run duration variance: roughly 3 to 8 hours.
  • Around 3 hours happens when they have a strong Domi that “folds” fights early (e.g., from wave 1).
  • Without Domi, they cite a best record of 13 “legit waves” once, multiple 12/11/10 runs, and estimate a ~8–9 wave average.
• They argue Nightmare is competitive with Paradox for farming time, but note Paradox counters often show combat time only, not preparation/room-change time (they estimate +5 to 10 minutes).

Strategies and key tips (by mechanics / team approach)

Core strategy: build for spawn-kills + minimize failures

• Because Nightmare waves are designed to be difficult, the player recommends a “spawn-kill” style setup for wave start.
• They emphasize that when mobs spawn, they want to delete targets immediately, avoiding wasted turns on enemies that can’t survive meaningfully.

Team composition (final-fight style)

• They say they almost always use Panda plus two other classes (the other two vary).
• Why Panda:
  • It’s their main character.
  • It enables spawn killing / carrying to manipulate boss mechanics (and in many boss systems, mechanics don’t apply to the carried unit).
• Why Sadida (Sadi) is a preferred DPS for this:
  • Better “spawn kill” practicality: dolls must be pre-setup (more setup than some direct attackers), but it’s done before the wave pops rather than reacting after.
  • Strong damage with a hybrid/stat-focused approach and support for multi-spell setups.
  • They mention Sadida pairs well with ideas like hybrid builds and strong zone/kit synergy (e.g., AP/zone damage).

Passive amplification (their damage engine)

• They heavily leverage a passive effect (and/or “Parmage”) where being hit grants boosts:
  • Each time the character is hit, the hit character gains 10% of their elemental stats for two turns (stacking/cumulative), affecting allied damage too.
• A common interaction:
  • Apply the amplification where it benefits certain allies (they mention examples like Heliotrope, Zobal, Feca, depending on setup).
  • They use a contain/lock effect concept (via “Utrop/box” in their wording) to stop an ally from spamming disruptive spells while still letting amplified damage apply.

Carrying and boss-mechanic exploitation

• Major idea: many boss mechanics apply in an area/circle and don’t apply to the carried target, making carrying the Sadida strategically profitable.
• Concrete examples include bypassing mechanics that would otherwise punish:
  • one-shot style mechanics,
  • PM reduction,
  • and “slashes” (as referenced in their wording).

Wave-by-wave notes (main mechanics mentioned)

General wave pattern

• “If it can be one-shot, one-shot it; if it can’t, focus the rest as quickly as possible.”

Wave 2: debuffs / carry interaction

• Mecamout described applying debuffs; carried Sadida can prevent certain effects (e.g., no AP/MP poison for Sadida).

Wave 4 (Glour / Hush behavior)

• If a boss becomes invulnerable only if a character starts their turn, then on wave spawn nobody has started a turn yet, so they can sometimes hit invulnerable-like targets immediately.

Wave 5 (Miss / counters spawn-kills)

• They note spawn-kill counters where enemies become invulnerable and require decoding/cleanup.
• They recover by infecting/controlling with spells like Miasma + Mandragor to keep mobs affected and finish after mobs act.

Wave 6 (Coutoulou restrictive boss)

• Heavy-line damage gets punished (risk of one-shots).
• Solution: don’t rely on many damage lines; instead use brute force / very high damage bursts so enemies die quickly and “madness” stacking doesn’t escalate.
• They also mention Salida pacifist behavior that can happen due to carrying (Sadida doesn’t get initial status).

Wave 7 (Nemeses combined + erosion adds)

• They describe constraints where they need to wait a turn before killing everything.
• They discuss a Rune-related optimization for movement/turn setup (prioritizing P1; P2 often useless in most cases).
• They use Corruption on Torquedonia to prevent the Tormenter/Torqu boss from dying unsafely while Sadida is carrying it.

Wave 8 (reflection mechanics / “Four horsemen”)

• They explain using Prohibition / stabilization on Sadida to manage reflection enemies.
• Workaround when needed:
  • Go into melee range so the boss can’t reflect back the “normal” way.
  • Use Harmony so trees absorb/reflection is tanked while still enabling high burst damage.
• If they can’t use Prohibition:
  • they use Animated Bag plus Harmony logic to absorb multiple reflections.

Wave 9

• A “horse-like / non-scaling” boss described as a “free wave” in difficulty, though still time-consuming due to delay before attacks become possible.

Wave 10 (Torqu timing optimization)

• They time wave initiative so killing with Panda is advantageous, then Torque ensures Sadida can act without waiting.
• They place an “archonvre” (as stated) and use high Sadida damage to quickly remove rift parts/towers.
• They avoid countdown timer risks via precise placement (stave positioning to bypass countdown/TP).

Wave 11

• Vortex is criticized as not matching wave-based dream design; they find it frustrating/cheap.

Their late-run “mistake/scam”

• They misjudge turn order: a weapon effect (“front” vs “after damage” / blade raids AP) causes the Ice Knight to gain/trigger effects earlier than expected.
• Despite that, they finish by securing remaining bosses and then continue.

Key overall takeaway

Nightmare 3 farming effectiveness comes from:

• Adaptation to each wave’s mechanic
• Spawn-kill optimization
• Carrying when mechanics allow bypassing
• Stacking the passive damage engine
• Avoiding defeats above all, even if Paradox looks faster on raw combat speed

Gamers / sources featured

• No other gamers or external sources are mentioned by name in the subtitles, aside from general references like Discord/forum/community (not specific creators).