Turtle Soup EA

Turtle Soup EA automates a defined false-breakout workflow in MetaTrader 5. It selects a reference level, waits for a sweep, confirms the reclaim, and then applies configured entry, stop, target, risk, session, spread, volatility, and safety filters.

It is not a general breakout robot or signal service. The value is that the sweep-and-reclaim model becomes explicit enough to test, accept, reject, or adjust with evidence.

Market model

Visible highs and lows attract breakout orders, stop orders, and pending liquidity. A Turtle Soup setup starts when price trades beyond such a level but fails to hold the breakout.

A sweep alone is not enough. Price can break a level and keep going. The setup becomes relevant only when price reclaims the prior structure quickly enough to suggest that the breakout may have failed.

This makes Turtle Soup a false-breakout model, not a prediction model. It asks a narrow question: did price take out a clear level, fail to hold beyond it, and return inside the structure with enough quality for a systematic test?

What the EA controls

The EA controls reference-level selection, sweep distance, ATR-based sweep checks, reclaim timing, candle quality, entry style, stop model, target model, position sizing, daily and weekly loss limits, session windows, weekdays, Friday cutoff, spread, volatility, trade count, losing-sequence rules, dashboard, and tester visuals.

Those controls reduce setup drift. One trader may use a pivot high, another a session high. One may require a close back inside the range, another may enter on an intrabar touch. Turtle Soup EA makes those choices visible and testable.

Setup evaluation

The first layer is reference level. The EA can work with pivot highs and lows, highest-lowest logic, previous day or week levels, and session-based levels. The purpose is to find a level meaningful enough to test as liquidity.

The second layer is sweep validation. Fixed points and ATR distance decide whether price moved far enough beyond the level. This helps avoid treating every small tick through a level as meaningful.

The third layer is reclaim quality. A close-confirmed reclaim is usually more stable for testing than intrabar noise. Candle-body and wick rules can make the model stricter, but stricter is not always better.

Only after those checks does execution matter. The EA can use market-style entries, pending orders around the swept level, break-style entries, or retest-style entries depending on mode. Then it calculates stop, target, and active risk controls.

Configuration workflow

Start with setup definition: reference-level mode, pivot left and right bars, lookback, level age, and untouched-level rules.

Then tune sweep and reclaim strictness. Review MinSweepPoints, MinSweepATRMultiplier, MaxBarsAfterSweepForReclaim, close-back-inside requirements, reclaim candle quality, and maximum reclaim age.

After that, adjust stop, target, and management. Sweep extreme with ATR buffer is the clean default stop concept. Fixed risk-reward targets are easier to compare during optimization. Partial closes, break-even, and trailing should be tested separately before being combined.

Risk deserves its own pass. Percent risk, maximum trades per day, maximum positions, daily and weekly loss limits, cooldown, and stop-after-loss controls are guardrails. They do not remove market risk.

Evidence and testing limits

The product package includes EURUSD M30, NASDAQ M30, and XAUUSD M30 v1.1 setfiles. The page links published Strategy Tester snapshots for the EURUSD M30 and XAUUSD M30 v1.1 setfiles. These are documented scenarios, not live instructions.

Test one symbol and one timeframe at a time. Start with the matching setfile, then confirm broker symbol specification, spread, commission, point size, server time, and session mapping. Change one group at a time: reference levels, sweep and reclaim, stop and target, then management and filters.

A strong-looking backtest can become fragile if many settings are tightly tuned together. Use out-of-sample periods, higher spread assumptions, worse slippage, and demo execution before live risk.

When not to use it

Avoid blind live deployment, news conditions, unstable spreads, untested symbols, and broker environments with unclear stop-distance or execution rules.

Be cautious in strong trend conditions. A level can sweep and reclaim briefly, then fail again as the larger move continues. Turtle Soup EA can make the rules consistent. It cannot make the market predictable or replace account rules, risk limits, and trader responsibility.