The Feca in Dofus Retro reduces damage before it becomes a problem. Shields make long sessions consistent, glyphs punish predictable paths and protection gives the team time to establish its plan. Feca rarely wins through one spectacular hit; it wins because mistakes become less expensive.
That quality is valuable in automated farming, provided the character does not cast every protection without context. A short fight does not need a dungeon rotation. This guide builds a Feca capable of choosing between speed, safety and support according to the target group.
Define the Feca's role
Solo, Feca combines steady damage and reduction to limit bread between encounters. It looks for maps where enemies group or use predictable corridors. In teams, it protects exposed characters, stabilizes dangerous turns and prepares zones that positioners can exploit.
Protection is not an end by itself. A shield that consumes a full turn when the group could finish immediately lowers return. A good Feca knows when to protect, when to establish a glyph and when a direct attack is the correct defensive action.
Fire build and utility variants
Fire is the clearest progression: Intelligence, ranged attacks and support form one coherent package. A utility direction adds wisdom, range or vitality for stronger control and survival. Other elemental variants can work, but they should answer one specific resistance or equipment milestone.
| Direction | Strength | Trade-off |
|---|---|---|
| Fire | Steady damage and available gear | Fire-resistant targets |
| Fire / wisdom | Control and progression | Lower direct damage |
| Fire / vitality | Long sessions and safety | Potentially slower fights |
Remain mono-element through early milestones. Feca already manages several protection decisions; adding a second damage path too soon increases cost without necessarily shortening ordinary encounters.
Choose which shields to cast
A shield must answer damage that is actually present. Observe the area's monsters, identify their elements and prioritize protection against attacks that frequently hit important characters. Disable an irrelevant shield in that profile.
Timing matters just as much. In a quick series, a first-turn shield may cost more time than it saves in healing. In a long encounter, the same action can be excellent. Prepare an offensive profile for weak groups and a difficult-group profile that permits the full defensive cycle.
Practical decision: compare the cost of one protection turn with the number of attacks it should reduce before the expected end.
Place glyphs without obstructing the team
An effective glyph covers cells that enemies will use, not merely a large empty area. Positioning, locking and obstacles increase its value. A melee team can instead lose time when a glyph occupies its route or forces a detour.
Evaluate target density and expected duration. Against one fragile enemy, a direct attack is usually stronger. Against several monsters held together for multiple turns, a glyph converts movement into value. Automated rules should therefore check target count and, where supported, ally presence.
Characteristics and Feca gear
Intelligence supports the Fire build. Vitality adds error tolerance and wisdom accompanies control and XP. Range lets Feca attack and protect without abandoning a safe position. AP should enable a clear sequence, such as one protection plus one attack or two offensive actions.
A simple Fire set is sufficient early. In mid progression, secure the AP threshold, then range and resistances. At high level, judge gear across a full run: average damage, bread, stability and speed. A defensive item can produce more hourly kamas when it removes repeated healing trips.
Feca-friendly XP areas
Groups dealing a limited set of elements make shield selection easier. Narrow corridors reward glyphs, while scattered monsters lower their value. Initially avoid frequent unbewitching if the profile depends entirely on active protection.
Measure experience per hour and consumption, not just reward. Feca can defeat hard groups safely, but a secure ten-minute fight is not always the best leveling spot. The MoonBot monster guides help compare resistance and behavior before testing.
Team synergies
Iop and Sacrier particularly appreciate protection while remaining in melee. Pandawa places monsters inside glyphs. Cra uses the time created by reduction and control. With Eniripsa, divide protection and healing responsibilities so two actions are not wasted on a threat already neutralized.
In multi-account play, give Feca early initiative when shields must cover the enemy turn. If its primary job is placing a glyph after enemies are grouped, let the positioner act first. The right order follows the scenario rather than one universal rule.
Configure Feca in MoonBot
Create one condition for each shield: group type, minimum duration or danger level. Reserve glyphs for several targets and retain a direct default attack. Set a preferred distance that preserves lines of sight without moving too far from allies who need coverage.
Test cooldowns and effect expiration in longer fights. Add health thresholds, bread and banking. In teams, confirm that area rules do not conflict with melee destination cells. The MoonBot combat guide provides the general method.
Frequent Feca mistakes
- Casting every shield against damage types it cannot reduce.
- Protecting for a full turn when one attack would finish the final enemy.
- Placing a glyph where monsters will immediately leave it.
- Ignoring melee allies in area conditions.
- Confusing the ability to survive with actual hourly return.
Recommended progression plan
Begin with Fire, one primary attack and protection matched to the area. Equip the AP threshold for the normal turn, then add range, vitality and wisdom as required. Measure an offensive baseline first and enable only defensive tools that demonstrably reduce healing or defeats.
A well-configured Feca does not cast the largest possible number of shields; it selects the defensive action with a measurable result.
Botting breaches the game's terms of service and carries a sanction risk. No tool can guarantee that an account will never be banned.
