Turtle Soup EA

Turtle Soup starts with a familiar market behavior: price trades beyond a visible high or low, takes liquidity, and then fails to hold the breakout. The EA turns that idea into rules instead of reacting to every wick on the chart.

Turtle Soup EA automates one specific false-breakout workflow in MetaTrader 5: define the level, wait for the sweep, confirm the reclaim, then apply the configured entry, stop, target, risk, and filter rules.

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

The market idea

Many traders watch the same highs and lows. Those levels often attract breakout orders, stop-loss orders, and pending liquidity. A Turtle Soup setup starts when price moves beyond one of those visible levels but does not continue cleanly.

A sweep by itself is not enough. Price can break a level and keep going. The setup only becomes relevant when price moves back inside the prior structure. That reclaim is the first sign that the breakout may have failed and that the move beyond the level may have mainly collected liquidity.

This is why Turtle Soup is a false-breakout model, not a prediction model. It does not assume that every stop run must reverse. It asks a narrower question: did price take out a clear level, fail to hold beyond it, and return quickly enough for a structured counter-move to be tested?

Why the logic can be useful

The model can be useful because it gives the trader a defined sequence. The reference level comes first. The sweep must meet distance rules. The reclaim must happen inside a limited number of candles. The entry, stop, target, and filters are then handled by settings rather than by memory or mood.

That matters because manual false-breakout trading can drift. One chart may use a pivot high. Another may use a session high. One trade may wait for a candle close back inside the range. Another may enter on an intrabar touch. One setup may be skipped because spread is high. Another may be taken anyway.

The EA does not make those choices correct by default. It makes them visible. Once the rules are visible, the trader can test whether the model has enough structure for a specific symbol, timeframe, broker, and account rule set.

How the EA reads a setup

The first job is reference-level selection. The EA can work with pivot-style highs and lows, highest-lowest logic, previous day or week levels, and session-based levels. The common purpose is the same: find a level that is meaningful enough to be worth testing as liquidity.

After the level exists, the sweep logic decides whether price has moved far enough beyond it. The sweep can be measured with fixed points and ATR-based distance. Using volatility in the sweep check helps avoid treating every small tick through a level as meaningful.

The reclaim logic then decides whether price returned back inside the level quickly enough and with enough candle quality. A close-confirmed reclaim is usually more stable for testing than reacting to intrabar noise. Optional candle-body and wick rules can make the model stricter, but stricter is not always better. A filter that improves one market may block useful setups in another.

Only after the setup passes those checks does execution become relevant. The EA can use market-style entries after the reclaim, pending orders around the swept level, break-style entries, or retest-style entries depending on the selected mode. It then calculates the stop, checks the target logic, and applies the active risk controls.

That final filter layer is important. Session windows, weekdays, Friday cutoff, spread, ATR volatility, trade count, open positions, losing sequences, and broker stop-distance rules can all decide whether an otherwise valid setup is allowed to trade.

Settings to configure first

Start with the settings that define the setup before changing trade management. Reference-level mode, pivot left and right bars, lookback, level age, and untouched-level rules determine what the EA is allowed to treat as liquidity.

Then tune sweep and reclaim strictness. Review MinSweepPoints, MinSweepATRMultiplier, MaxBarsAfterSweepForReclaim, close-back-inside requirements, reclaim candle quality, and maximum reclaim age. These settings decide whether the EA is reading a real failed breakout or just reacting to chart noise.

Only after that should stop, target, and management rules be adjusted. The manual uses sweep extreme with ATR buffer as the clean default stop concept, while fixed risk-reward targets are easier to compare during optimization. Partial closes, break-even, and trailing can change the shape of results, so test them separately before combining them.

Risk settings deserve their 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, but they can prevent one weak regime from turning into uncontrolled execution.

Testing workflow

Use the included setfiles as research baselines. The current product package includes EURUSD M30, NASDAQ M30, and XAUUSD M30 v1.1 configurations. They are not live trading instructions. They are starting points for MetaTrader 5 Strategy Tester work.

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

Do not optimize everything at once. A strong-looking backtest that depends on many tightly tuned settings can become fragile. Use out-of-sample periods, higher spread assumptions, worse slippage, and demo execution before considering live risk.

Reading the evidence

The product page links published Strategy Tester snapshots for the EURUSD M30 and XAUUSD M30 v1.1 setfiles. Those snapshots document specific historical tests with named setfiles, periods, modelling quality, result metrics, and source images.

That is useful evidence, but it has a narrow meaning. It shows how those exact configurations behaved in those tester conditions. It does not prove that the same result will repeat, that another broker will match it, or that live execution will behave like the test. Spread, commission, slippage, tick data, stop levels, and server time can change the outcome.

The correct reading is practical: use the snapshots to understand the tested scenario, then reproduce and challenge the assumptions on your own installation.

When not to use it

Avoid blind live deployment. Avoid using the EA during news conditions, unstable spreads, symbols you have not tested, or broker environments where stop distances and execution rules are unclear.

Be cautious in strong trend conditions. A level can be swept and reclaimed briefly, then fail again as the larger move continues. False breakouts can fail like any other setup.

Turtle Soup EA is best treated as a systematic research and execution tool. It can make the rules consistent. It cannot make the market predictable, and it cannot replace account rules, risk limits, or trader responsibility.