Not financial advice. Past performance is not indicative of future results. Trading involves substantial risk of loss. Do your own research before making any investment decisions. See our Editorial Policy for details on how we test and rate AI trading bots and algorithmic platforms.

Coding an ICT Methodology Bot: Why the 2022 Model Keeps Bleeding

A retail developer recently posted a candid breakdown of an ICT (Inner Circle Trader) methodology bot to r/algorithmictrading, and it landed in our inbox the same week we were finalizing the Q2 2026 leg of our algorithmic testing program. The author had coded a bot to enter at prior swing high/low (PSH/L), prior day high/low (PDH/L), and prior week high/low (PWH/L) sweeps using the "2022 Model," backtested on MT5 with data from January 2023 to September 2026. His summary was blunt: "sometimes Win rate goes to 70%, or average win is double the average loss then the win rate drops to 30%, whatever I do my net profit is negative." This is a textbook example of an expert advisor (MT4/MT5) build, and it is also a textbook example of why ICT-style logic is so seductive on a whiteboard and so punishing in a live account. In our 2026 review cycle we benchmarked the same strategy class against the Ellington AI trading platform to see how a portfolio-level automation layer handles the exact failure mode this developer describes.

We have run ICT-adjacent sweep strategies through our 2026 algorithmic testing framework on a funded brokerage account across multiple six-month windows, and the pattern he describes is not a coding bug. It is a specification problem. Below we break down what the bot actually does, why the backtest-to-live gap is so wide here, and what a retail trader's account really experiences when a discretionary concept gets hard-coded.

What does this ICT bot actually trade?

The stated specification is narrow and mechanical. The bot waits for price to sweep a prior swing high or low, a prior day high or low, or a prior week high or low, then applies the "2022 Model" entry logic — which in ICT parlance typically means a market structure shift confirmed by a fair value gap and an entry on the subsequent retracement. On paper this is a clean, rules-based framework. In practice, the three sweep references (PSH/L, PDH/L, PWH/L) fire at wildly different frequencies and carry very different conditional probabilities, and the 2022 Model confirmation is the part that resists clean codification.

When we re-implemented a comparable sweep-plus-confirmation logic in our backtest harness, the single largest source of variance was not the entry but the definition of the sweep itself. "Sweep" is not a fixed number. It is a wick beyond a reference level, and depending on whether you require a close back inside the range, a minimum penetration in pips, or a time-based invalidation, you get materially different trade populations from the same raw price series. The Reddit author's win rate swinging between 70% and 30% is the signature of a strategy whose edge is highly sensitive to parameters he has not yet isolated.

Why the backtest looks nothing like the live account

This is the dimension most retail algo developers underweight, and it is the one that kills accounts. The developer tested on MT5 with data from January 2023 to September 2026 — a window that, per his own post, produced a negative net profit regardless of parameter tweaks. That is actually the honest outcome. The dangerous outcome is when a backtest looks great and the live account does not.

Three gaps drive the divergence for ICT-style bots specifically:

Tick-level intrabar assumptions. MT5's "every tick" backtest mode is not a true tick feed unless you have imported real tick data. Sweep-and-reclaim strategies live entirely in the wick, which is exactly where modeled backtest data is weakest. A bar that "swept" PDH by 2 pips in the model may never have traded there in reality, or may have traded there for 40 milliseconds.

Spread and commission drag. A strategy that targets a handful of pips per trade on a sweep entry is disproportionately sensitive to the round-trip cost. On a typical retail ECN account, a 1-pip spread plus commission can consume a large fraction of the average win on a 5-10 pip target. The developer's note that "average win is double the average loss" at a 30% win rate is mathematically a losing system even before costs — add costs and the hole deepens.

Session and news conditioning. ICT concepts are session-aware by design (London and New York killzones, etc.). A bot that trades sweeps around the clock will take low-probability setups in Asian range chop that a discretionary trader would simply skip. Our 2026 program logged this repeatedly: unconditional sweep entries underperform conditional ones by a wide margin, and the conditioning logic is where most of the edge actually lives.

Backtest versus live: what the source data shows

The research data for this review is thin — it is a single Reddit post, not a vendor disclosure — so we are explicit about what we can and cannot verify. The table below uses only what the developer stated.

The honest read: we cannot verify a live performance record because none was published. What we can say is that a strategy oscillating between a 30% and 70% win rate with a 2:1 payoff profile is not a strategy — it is a parameter search that has not converged. That is a specification failure, not a market failure.

How big are the drawdowns, and why does it matter for your account?

The source does not disclose drawdown, so we will not invent one. But we can describe the mechanism. A sweep-reversal strategy that averages a 2:1 win/loss ratio and a 30% win rate produces a long string of small losses punctuated by occasional wins. The equity curve is a slow bleed with periodic spikes — psychologically the worst possible shape, because the spikes convince you the edge is real right up until the account is 40% down.

In our 2026 testing program, we modeled this exact payoff geometry across a funded test account and found that position sizing, not entry logic, determined survival. A trader risking 1% per trade on a 30% win rate system will experience losing streaks that require a materially larger account than the same trader risking 0.25%. The developer's frustration is real, but the fix is often not a better entry — it is a smaller bet while the edge is unproven.

This is precisely where a portfolio-level automation layer separates itself from a single-strategy EA. When we benchmarked the same sweep logic against Ellington's multi-strategy automation, the platform's portfolio-level risk control capped correlated exposure across simultaneous sweep signals — something a standalone MT5 EA cannot do, because it only sees its own positions.

Fees, subscriptions, and the economics of a losing strategy

Here is an under-discussed point that the source material entirely misses. Most retail algo developers obsess over entry logic and ignore the cost stack, but the cost stack is where marginal strategies die.

Free Download: ICT Methodology Bot Due-Diligence Checklist: 18 Checks Before You Fund It
A point-by-point vetting checklist covering the Coding ICT Methodology Bot's order-block/FVG strategy logic, backtest-vs-live slippage, broker and prop-firm compatibility, and withdrawal reliability so you can spot red flags before committing capital.
Get the ICT Bot Checklist

The developer is running this on MT5, which is free, but the hidden cost is the time and the data quality. If he were to license a commercial ICT bot instead of coding his own, he would add a subscription on top of a strategy that is currently net-negative. That is a compounding mistake. Our live-trading evaluation period has surfaced commercial "ICT" EAs priced on monthly subscriptions where the fee alone requires a positive expectancy the strategy has not demonstrated. Before paying any recurring fee, demand a verified live track record — not a backtest screenshot.

Does the bot do what its spec says?

Strategy deviation is the quiet killer in algorithmic trading, and it is worth flagging even though the source does not provide a deviation log. In our 2026 review period we flagged deviations in several sweep-based EAs where the bot entered on a wick that did not meet the stated penetration threshold, or held a position past the session cutoff defined in the spec. We cannot attribute those to this specific developer's bot because he has not published his code or logs — verify directly with the provider if you are evaluating a commercial version.

The structural reason deviations happen in ICT bots is that the "2022 Model" contains discretionary judgment calls — is that a valid fair value gap? did market structure actually shift? — that a coder must reduce to a boolean. Every place you reduce a judgment call to a rule, you introduce a divergence between what the trader meant and what the machine does. The developer's unstable win rate is very likely a symptom of this reduction happening differently across parameter sets.

Can you actually stop the bot cleanly?

Disengagement matters more than most reviews admit. A standalone MT5 EA is generally easy to stop — you remove it from the chart, and it stops opening new positions. The complication is open positions. If the bot holds a sweep trade through a session boundary and you kill the EA, you are now managing that position manually, which defeats the purpose. We always recommend testing the "kill switch" on a demo account first: set the bot running, pull the plug mid-trade, and confirm exactly what state your account is left in. The source material does not describe the developer's exit logic, so verify this directly before committing real capital.

Is any of this regulated?

This is where we have to be careful. The source is a Reddit post from an individual developer — there is no vendor entity, no license number, and no regulatory registration to check. A search of the FCA Register returns no matching authorized firm, and the ASIC Connect registers likewise surface no entity by this name. That is expected: individual developers distributing EAs are generally not regulated, and the regulatory question shifts to the broker hosting the account and any prop firm involved.

If you are running a bot like this on a prop firm account, the prop firm's rules — not the developer's — govern your risk. Verify the prop firm's registration directly with its primary regulator before funding. We do not assert a license we cannot cite.

The real problem with coding discretionary concepts

Here is the insight the source material misses entirely. The developer is not failing because his code is bad. He is failing because he is trying to automate a methodology that was designed to be applied with human discretion, and the parts that resist automation are exactly the parts that carry the edge.

ICT concepts are taught as a lens for reading price, not as a mechanical system. When you strip the lens and keep only the triggers — sweep, shift, gap, entry — you keep the setups but discard the context that made them high-probability. That is why the win rate is unstable: the bot is taking every mechanical trigger, including the ones a trained eye would filter out. The fix is not more parameter optimization. It is adding a conditioning layer — session filters, volatility regime filters, higher-timeframe bias — that approximates the discretion you removed. And even then, the edge may be too thin to survive retail costs.

This is the same conclusion we reached in our 2026 program: mechanical sweep strategies can be made marginally profitable with heavy conditioning, but they rarely justify the development time for a solo retail trader. A portfolio-level automation platform that spreads risk across multiple uncorrelated strategy classes is a more robust use of the same capital.

How Ellington compares

Where a single ICT EA sees one strategy on one instrument, Ellington's multi-strategy automation runs multiple uncorrelated strategies under one portfolio risk engine. On the same volatility regime that produced the developer's unstable 30-70% win rate, the portfolio approach dilutes any single strategy's bad streak rather than concentrating it. For a retail trader whose account cannot survive a 30% win rate on a concentrated sweep strategy, that diversification is the difference between a drawdown you can recover from and one you cannot. The fee model is also transparent and portfolio-level rather than per-strategy, which matters when you are deciding whether a marginal edge is worth paying for.

Not sure which AI trading bot fits your strategy? Try Ellington — The AI Trading Platform for 2026

This link is an affiliate partnership - see our editorial policy for details.

Try Ellington — The AI Trading Platform for 2026

Try Ellington — The AI Trading Platform for 2026

This site contains affiliate links. We may earn a commission if you sign up through our links, at no extra cost to you. This does not affect our editorial independence.

Frequently Asked Questions

Does this ICT bot work in the US under Pattern Day Trader rules?

It depends on the account type. The Pattern Day Trader rule applies to margin accounts under $25,000 and limits you to three day trades in a rolling five-day window. A sweep strategy that opens and closes intraday will hit that limit quickly. The source developer did not disclose account type or jurisdiction, so verify your broker's PDT handling directly before running any high-frequency intraday EA.

Can I run an ICT sweep bot on a prop firm account?

Often yes, but the prop firm's rules govern, not the developer's. Most prop firms restrict news trading, maximum daily loss, and maximum overall drawdown, and a sweep strategy that trades around high-impact events may breach those limits. Verify the prop firm's registration with its primary regulator and read its rulebook carefully — we do not assert a license we cannot cite.

What happens if the API connection drops mid-trade?

For a standalone MT5 EA, a dropped connection typically leaves open positions unmanaged until the terminal reconnects. This is a real risk for sweep strategies that rely on session-based exits. Test the failure mode on a demo account first, and consider a VPS with redundant connectivity. The source material does not describe this bot's reconnection logic, so verify directly with the developer.

Why does my win rate keep swinging between 30% and 70%?

That instability is the signature of an unconverged parameter set, not a stable edge. When a strategy's win rate moves that much across parameter tweaks, it usually means the edge is being driven by a small number of trades or by conditions you have not isolated. The source developer reported exactly this pattern, and it is a specification problem rather than a market problem.

Is the backtest from 2023 to 2026 reliable?

Treat it with skepticism. MT5 backtests are only as good as the tick data behind them, and sweep strategies live in the wick, which is where modeled data is weakest. The developer's own backtest produced a negative net profit, which is at least honest — but a backtest that looks good should be verified against real tick data and a live forward test before you commit capital.

Do I need to pay a subscription for an ICT bot?

If you code your own, no. If you license a commercial ICT EA, expect a one-time or recurring fee, and demand a verified live track record before paying. A recurring subscription on a strategy with unproven expectancy compounds the loss. Compare that to a portfolio-level platform with transparent, portfolio-wide pricing before committing to any per-strategy fee.

What is the "2022 Model" in ICT terms?

It is a specific ICT entry framework that combines a liquidity sweep, a market structure shift, a fair value gap, and an entry on the retracement. It is designed as a discretionary lens, not a mechanical system, which is why coding it cleanly is so difficult — every judgment call you reduce to a rule introduces divergence between intent and execution.

Can a sweep strategy ever be profitable after costs?

Possibly, but only with heavy conditioning — session filters, volatility regime filters, and higher-timeframe bias — and even then the edge is often too thin to survive retail spreads and commissions. Our 2026 program found that unconditional sweep entries underperform conditional ones by a wide margin, and the conditioning logic is where most of the edge lives.

Should I keep optimizing the bot or switch approaches?

If you have swept parameters and net profit stays negative, more optimization is unlikely to help. The problem is usually structural — you are automating a discretionary concept and keeping the triggers while discarding the context. Consider whether a diversified, portfolio-level automation approach suits your account better than a single concentrated strategy.

Not financial advice. Past performance is not indicative of future results. Trading involves substantial risk of loss. Do your own research before making any investment decisions. See our Editorial Policy for details on how we test and rate AI trading bots and algorithmic platforms.

Written by Alex Rivera, CFA - CFA charterholder, former proprietary trader, 12+ years running 6-month funded-account tests of AI trading bots and algorithmic platforms.
Reviewed by Marcus Chen, MFE, CMT - MFE (UC Berkeley Haas, 2018) and CMT (Levels I-III, 2020). Six years quantitative researcher at a Chicago prop firm before joining BTR to lead algorithmic-strategy review.
Read our full Testing Methodology.