A Dofus Retro Eniripsa configuration in MoonBot must choose among emergency, protection, AP support, attack, movement and fallback from real state. A fixed list fails when an ally is nearly full, Vampiric loses its line or Stimulating opens no action.
This guide describes a testable model for Fire, Water, Air, solo and team. Use ranks from the spell guide and values from the gear profile. Keep automation supervised: it can breach Dofus Retro terms and cause sanctions.
Separate data, rules and objectives
Store ranks, costs, range, limits, cooldowns, characteristics and resistances in one layer. Keep decision rules in a second and farming metrics in a third.
This lets an item change without rewriting healing and compares objectives with identical mechanics. Version each layer.
Build combat state
Capture AP/MP, current and maximum health, effects, cooldowns, positions, obstacles, allies, enemies, resistance, summons, free cells and initiative. Add projected next-round state.
Never silently replace unknown data with zero. Mark it unavailable and take a prudent branch.
Write global priority order
A starting order is: prevent immediate defeat, save a threatened target, stop a spike, apply amortised support, remove a threat, prepare the next action and end.
Every block has an exit condition. Once emergency is treated, Eniripsa should not keep healing merely because it is next in a list.
Calculate useful healing
For each spell and target calculate low value, missing health, actual healing, danger before next turn, AP, range, line, cooldown and trade-off.
Score attacks or defeat prevented. Subtract overheal and displaced offence. A low but safe target can follow an elimination.
Define distinct healing thresholds
Create routine, emergency and critical thresholds. Routine follows output; emergency protects before the next enemy action; critical permits Sacrifice or Recovery where safe.
Avoid one percentage for every monster and phase. Use prudent maximum damage observed.
Rank healing targets
Score probable death, role, remaining initiative, protection, position, planned heal and ability to remove the source. Deduplicate multiple healers.
Log why a target wins: “attacked before its next turn” is more useful than “lowest health.”
Configure Curative and Healing Word
Curative covers self; Healing targets an ally. Read active-rank rules and create separate candidates with low value and range.
Refuse dominant overheal and preserve fallback AP. Solo, Curative directly competes with removing the source.
Configure Revitalizing Word
Project every area target and calculate total useful healing, including undesirable effects where applicable under rank geometry and rules. Do not use character count alone.
Add minimum useful health and grouping cost. An area forcing three allies away from damage cells can lose.
Configure Regenerating Word
Estimate triggers before finish, immediate danger and existing effects. Delayed healing wins in a long stable phase, not an emergency killing first.
Prevent duplicates and stop refreshes where target or fight will not last.
Configure Sacrifice and Recovery
Reserve strong heals for thresholds where cheaper options do not secure survival. Check range, cooldown, trade-off, Eniripsa health and plan afterwards.
Score useful health rather than raw amount. Log the reason and retain secondary healing during cooldown.
Control Word of Altruism
Calculate total missing health, threatened targets, side effects, cooldown and future state. Require collective improvement over available targeted heals.
Keep it in a rare observable branch. Refuse where overheal or trade-off dominates.
Configure Stimulating Word
For each beneficiary, simulate its rotation without and with AP. Count attacks, placement or protection genuinely opened during duration.
Score those actions minus cast cost and abandoned target. Add minimum fight duration and stop near finish.
Configure Preventing Word
Estimate damage before effect ends, observed reduction and existing protection. Select the target where an attack, heal or defeat is prevented.
Do not cast on an untargeted unit. Recalculate emergency after protection to avoid redundant healing.
Configure Frightening Word
Generate legal final cells by axis, obstacles, edge and occupancy. Score restored distance, attack prevented, line opened and pushed-target safety.
Plan the next action with remaining AP. A push without attack or exit can only move the problem.
Configure Forbidden Word for Fire
For every enemy, calculate post-resistance low damage, cost, casts, remaining health, final cell and danger. Prioritise elimination, dangerous action removed, then useful damage per AP.
Reserve AP for emergency. The Fire profile supplies thresholds.
Configure Vampiric Word for Water
Require range, line, sight, limit and acceptable resistance. Calculate damage, health truly stolen and required cell; separate offence and recovery scores.
At full health life steal loses part of its value. The Water profile keeps a no-line fallback.
Configure Wounding Word for Air
Calculate target, low damage, Air resistance, legal casts, distance and exit. Include the risk of being trapped after movement.
The Air profile separates Agility and damage. Avoid entering contact for marginal gain.
Configure Draining, Paralyzing and Silencing
Model enemy AP/MP thresholds, main action and dangerous cells. Score attacks or placements removed rather than average points removed.
Rebuild the enemy turn after each attempt. Stop disruption when it prevents nothing and convert AP into damage.
Configure Friendship and Coney
Require space, expected duration and a cell blocking neither line nor retreat. Estimate useful healing, diverted attack and occupancy cost.
Refuse saturated corridors and endgame turns. Log observed consequences to adjust frequency.
Configure Word of Youth
List active effects, owner, value and expected unbewitching result at active rank. Use a whitelist of verified hostile effects instead of “whenever a buff exists.”
On uncertainty preserve the spell. Removing a useful allied effect or altering the wrong phase can be irreversible.
Configure Lifting Word
Simulate targets before and after range and keep only newly legal ones. The cost must leave a spell worth more than the alternative.
Refuse where line of sight blocks or MP reaches the same result. Log the spell opened.
Score movement cells
For every reachable cell calculate targets, heals, incoming attacks, lock, obstacles, exit, allied lines and next-round state. Apply bans before scores.
Do not hide attack and escape in one opaque weight. Keep reasons such as open line, leave contact, heal or prepare.
Configure the weapon
Encode AP, minimum range, line, cell, conditions, resistance and low damage or healing. Compare the full turn with the best spell sequence.
Historical wand affinity alone does not make it priority. The weapon solves a specific geometry or resistance.
Separate solo and team profiles
Solo scores self-health, exit and output. Teams include allied rotations, reserved cells, protection and outside healing.
Create independent configurations. The team guide supplies roles and initiative.
Configure group and board filters
Filter combined level, size, families, resistance, summons, obstacles, distance and exits. Link every refusal to a reason and path.
The zone guide defines complete output. Combat rules cannot repair bad selection.
Design the Eniripsa log
Record state, candidates, low values, rejection reasons, score, chosen action, cell, result, duration and next cooldown. Exclude unnecessary sensitive data.
Keep enough detail to replay the first divergence, not merely “spell failed.” Add configuration version.
Write test scenarios
Cover nearly full ally, emergency before next turn, no line, contact at an edge, Vampiric at full health, unamortised Stimulating, redundant protection, blocking summon and major spell cooling down.
Each scenario defines state, expected and forbidden actions. Replay after gear or rank changes.
Roll out progressively
Archive the control, use simulation where available, then ten supervised fights on known boards. Extend to thirty before a new zone.
Stop at the first unexplained action. Change one rule and preserve immediate rollback.
Avoid configuration mistakes
- Using one healing percentage.
- Stimulating without ally simulation.
- Calculating Vampiric without line or missing health.
- Removing AP/MP without a prevented action.
- Reusing solo rules in a team.
- Deploying a new board unsupervised.
Validate the configuration
Record version, ranks, stats, AP/MP, low healing, low damage, priorities, thresholds, cells, targets, cooldowns, fallbacks, filters, logs, scenarios and control. Verify paths separately.
The configuration is ready where every decision has a readable cause and reproducible test. No output gain justifies hiding unsafe behaviour or sanction risk.
Botting breaches the game's terms of service and carries a sanction risk. No tool can guarantee that an account will never be banned.
