Work on a market replay/simulation stack continues with four components: Expert Advisor, position indicator, Chart Trade, and Mouse Study. Current guidance is demo-first; the EA and position indicator still require stability work, while Chart Trade and Mouse Study are safe but depend on the EA for execution.

Two cleanup issues are addressed: removing the EA leaves orphaned position indicators, and switching the tracked contract can leave misleading visuals. Handling DeInit in OnDeinit and deleting indicators by their short name (derived from the position ticket) resolves both.

A separate failure appears on timeframe changes due to pointer state across OnInit reinitialization. Explicitly resetting pointers in OnInit prevents runtime unloads.

Next focus is NETTING vs HEDGING behavior. NETTING changes average price on volume increases, but indicators...

👉 Read | Forum | @mql5dev

CKS Position Risk Dashboard is a lightweight MT5 chart indicator focused on pre-trade risk review and position visibility. It is informational only and does not open, modify, or close orders.

The panel shows account and symbol metrics including balance, equity, free margin, margin level, bid/ask, spread, and broker volume constraints (min/max/step). It also reports open-position count and floating P/L for the current chart symbol, plus estimated protected risk when a stop loss is present. Tick size, tick value, and symbol digits are handled automatically. Panel colors, placement, width, and refresh interval are configurable.

Key inputs include risk percent, planned stop distance in points, balance vs equity selection, and a maximum cap for suggested lot size. The suggested volume remains an estimate and should be verified against final margin and sym...

👉 Read | AppStore | @mql5dev

A multi-timeframe, multi-symbol SuperTrend setup can simplify monitoring when it is implemented with strict data handling and clear output.

Key requirements include per-symbol and per-timeframe state separation, deterministic bar indexing, and consistent ATR/SuperTrend parameterization across feeds. Updates should be event-driven to avoid redundant recalculation, with safeguards for missing history and session gaps.

For usability, dashboards should prioritize current direction, last flip time, and distance to the band. Alerts need debouncing and a cooldown window to prevent repeated signals during consolidation.

👉 Read | CodeBase | @mql5dev

Building time-aware EAs starts with timezone hygiene. Session-based logic breaks when broker server time shifts for DST, and MT5 testing does not provide reliable GMT via TimeGMT(). Without a verified broker UTC offset and DST rule, session windows cannot be mapped correctly.

A practical DST detector can be built from NFP timestamps in the MQL5 Economic Calendar plus EURUSD M15 volatility spikes. When the expected spike alignment flips by one hour, a DST transition is inferred and matched against EU/US/AU transition calendars computed from weekday-occurrence rules.

The implementation uses modular MQL5 architecture: indicator layer (multi-AMA pairwise voting across timeframes), strategy layer (signal-to-direction mapping), and a dedicated time layer (DST-aware session conversion, calendar filters, intraday open/mid/close windows). TimeTradeServer() ...

👉 Read | VPS | @mql5dev

The article breaks Forex arbitrage into a graph problem: currencies are vertices, tradable pairs are directed edges weighted by executable bid/ask prices. Profitable “cycles” are those where the rate product stays above 1 after subtracting relative spreads, enabling near-zero market risk when executed correctly.

It outlines an MT5 Expert Advisor built as modular components: real-time graph construction, cycle discovery using a modified Floyd–Warshall (maximize products, track spread growth, reconstruct paths) plus a DFS pass to enumerate alternative cycles while avoiding reuse of the same symbol.

A key engineering focus is zero-exposure sizing: lots are derived by propagating a base notional through the cycle, then normalized to broker constraints (contract size, min lot, step), with proportional downscaling to cap risk. Execution and fault handling are tr...

👉 Read | NeuroBook | @mql5dev

MetaTrader 5 ships with a single-timeframe volume histogram, but multi-timeframe volume context and anchoring require custom tooling. An MQL5 implementation can render synchronized profiles across the main chart and a subwindow using objects, not indicator plots.

The design uses a draggable vertical anchor to define the start of analysis, with the viewport’s right edge as the end. Anchor time is normalized to valid bar times, restored if deleted, and auto-centered when needed. HTF selection is validated to ensure it is above the chart timeframe.

Bin sizing is interactive and stateful. Edit mode activates only when the anchor is selected: double-click E to enter numeric input, double-click S to commit. Invalid or empty input falls back to the last valid value. OnChartEvent drives recalculation on zoom, scroll, drag, and keystrokes, while rendering POC and...

👉 Read | AlgoBook | @mql5dev

AFML’s sequential bootstrap is often presented as the fix for bagging with overlapping triple-barrier labels, by supposedly decorrelating trees. This study isolates what actually reduces between-tree correlation: fewer sampled rows, not the sequential sampling rule itself.

A four-regime experiment holds the same DecisionTree base learner constant and varies only the row sampler: full vs uniqueness-throttled sample count, and standard vs sequential draw rule. The key metric is correlation of out-of-bag probability predictions, making the AFML variance term observable.

Results are consistent across tick, tick-imbalance, and a higher-density M5 replication: cutting max_samples to average uniqueness produces most of the decorrelation; switching to sequential sampling at the same count adds little and can even worsen correlation at full count. Out-of-bag...

👉 Read | NeuroBook | @mql5dev

This article digs into why random-access file code fails when the file’s internal layout is misunderstood. The key takeaway: file position doesn’t advance by “one byte” in a meaningful way unless reads and writes are defined by an explicit structure.

Using MQL5-style examples, it contrasts text parsing (tab-delimited strings) with binary layouts, showing how a small format change turns clean reads into garbage output. The fix is to design a self-describing record: write a length field, then the payload, and use FileSeek to backfill the length after writing.

For trading systems, this enables fast, reliable logging and replay of variable-length messages, with deterministic offsets and safer recovery during analysis or debugging.

👉 Read | NeuroBook | @mql5dev

Part 8 adds the missing bar-by-bar trend readout on NQ M1: a continuous micro-trend strength score in [-1, +1] that measures how cleanly fast/medium/slow EMAs align and accelerate, instead of relying on lagging, binary crossovers.

GetMicroTrendStrength() combines four EMA-derived components: 5/8/13 EMA ordering, ATR-normalized price position with tanh bounding, 5-bar slope agreement, and a bounded volume multiplier. A contradiction penalty sharply reduces the score when EMA alignment disagrees with price vs the fast EMA, suppressing common false positives during reversals.

The signal plugs into the Part 7 regime layer via confidence-scaled thresholds: high-confidence Trending/Informed sessions loosen cutoffs, low-confidence Stressed/Noisy sessions tighten them. On 514 NY sessions (May 2024–May 2026), Trending shows the most persistent directional ...

👉 Read | CodeBase | @mql5dev

Trading systems degrade when regimes shift, and fixed-window indicators react after the distribution has already changed. A sequential CUSUM detector updates bar by bar, accumulates evidence, and flags a breakpoint the moment a threshold is crossed.

The detector runs on standardized log-returns z_t built from a strictly historical rolling window. Two accumulators track upward and downward drift with a slack term k, then reset to zero after a hit. Threshold h sets the false-alarm versus detection-speed trade-off, often expressed via ARL0, with theory only approximate on real returns.

Implementation notes for MetaTrader 5 focus on execution constraints: handling full vs incremental recalculation in OnCalculate(), persisting S+ and S− via indicator buffers, and creating chart objects idempotently to avoid duplicates on live ticks.

👉 Read | AppStore | @mql5dev

Alpha-Beta Trend Filter is a predictive smoothing indicator based on steady-state estimation. Unlike SMA/EMA-style averaging, it maintains an internal price estimate and a trend velocity term, updating both each bar via a prediction step and a residual-based correction using alpha (price sensitivity) and beta (velocity sensitivity).

This MQL5 build extends the classic single-line output with a multi-symbol, multi-timeframe matrix dashboard. The chart plot uses DRAW_COLOR_LINE to switch state from bullish to bearish based on the velocity sign, while the dashboard renders Bull/Bear/Wait across selectable timeframes for a parsed symbol list.

Implementation details include ArraySetAsSeries() alignment, a helper that computes state from a minimal CopyClose() window without iCustom, and full UI cleanup on deinit. Typical tuning ranges: alpha 0.1–0.9, beta ...

👉 Read | AlgoBook | @mql5dev

Adaptive trading framework for FX, crypto, and high-digit instruments using a velocity-driven baseline and ER-based bands.

Trend filter uses baseline color: LimeGreen signals positive acceleration, Crimson signals negative acceleration. Volatility state is defined by band width: compressed bands indicate low ER and pending expansion; expanded bands indicate high ER and potential trend efficiency or extension.

Momentum breakout: wait for a squeeze and flat baseline. Go long on a candle close above the upper band with baseline turning LimeGreen. Go short on a close below the lower band with baseline turning Crimson. Stop sits beyond the baseline or opposite band. Hold while baseline color persists; exit on a color flip.

Mean reversion: require a flat baseline with wide bands. Enter only after a probe outside a band fails to flip the baseline, then p...

👉 Read | VPS | @mql5dev

Backtest output is bounded by history quality, yet MT5 data gaps often go unverified. A read-only Python audit can export M5 bars from multiple terminals, cache them as Parquet, and report missing bars per pair and per year instead of a single “History Quality” number.

The workflow validates terminal identity, avoids concurrent API sessions, and resolves broker-specific symbol suffixes. One broker required paging via copy_rates_from_pos, which exposed synthetic “fill” bars detectable only by timestamp spacing.

On a shared 2025-02-07 to 2026-06-12 window, the same deterministic breakout strategy drifted by 2,300–4,400 net pips across three feeds. Spread differences dominated, but data/price differences and missing-bar trade mismatches remained material.

👉 Read | NeuroBook | @mql5dev

Market structure analysis in MQL5 often ships as closed indicators that mix computation with rendering, expose limited buffers, and provide no stable query interface. Integration into EAs typically requires copying indicator logic or rebuilding it, increasing coupling, duplication, and maintenance cost.

A prototype modular framework addresses this by separating swing detection, level tracking, break detection, BOS/CHoCH classification, an event bus with deduplication, a market state machine, optional CSV persistence, and a unified public API. It runs as a standard custom indicator but behaves like a reusable service for EAs, dashboards, and research pipelines.

The codebase is split into 10 include modules plus one indicator entry point, supports internal and external timeframes, and avoids full recomputation via incremental bar processing. Trend a...

👉 Read | Calendar | @mql5dev

Backtest headlines can hide fragility: the same net profit and win rate may come from a repeatable edge or from a few oversized trades. This article builds an MT5-native analyzer that shows where profits really come from by measuring profit concentration.

The script reads closed deals from a simple Date/Profit CSV and computes top-N contribution (vs net and gross profit), the Gini coefficient over winning trades, and a stress test that removes the best winners to see if profitability survives.

It also aggregates results by day to flag “one big day” risk against prop-firm consistency limits, then combines concentration, consistency, and survival into a weighted A+–F grade with actionable recommendations.

👉 Read | Calendar | @mql5dev

External Range Liquidity (ERL) is a custom MetaTrader 4 indicator aimed at Price Action and Smart Money Concepts workflows. It scans swings to map market structure and flags liquidity sweeps where price pierces a prior swing but closes back inside the range, leaving a wick.

Structure labeling is applied in real time using HH/HL for bullish conditions and LH/LL for bearish conditions. When a sweep condition is detected, the prior swing level is relabeled as “Sweep”, supporting analysis of stop hunts and failed breakouts.

Key options include swing validation (InpSwingCandles, default 5), history scan cap (InpMaxBarsToScan, default 200), projection line length (InpLineLengthBars, default 15), plus colors, line style/width, and text size/offset. Visual output uses projected horizontal levels to keep charts readable with low terminal overhead.

👉 Read | AlgoBook | @mql5dev

Aegis Quantum Lite is a free educational Expert Advisor for MetaTrader 5, distributed as a single commented MQ5 file. It implements a completed-candle trend entry with a compact on-chart dashboard.

Buy logic requires Fast EMA above Slow EMA, RSI above the configured buy level, spread within the maximum, no existing position on the symbol, and a new completed candle. Sell logic mirrors this with Fast EMA below Slow EMA and RSI below the configured sell level.

Default inputs: FastEMA 9, SlowEMA 21, RSIPeriod 14, BuyRSILevel 48, SellRSILevel 52, FixedLot 0.01, MaximumSpreadPoints 50, StopLossPoints 500, TakeProfitPoints 500, OneEntryPerCandle true. The dashboard shows symbol, timeframe, EMA/RSI values, spread, signal, and trading status.

Execution safeguards include fixed lot only, no grid or martingale, position blocking per symbol, permission and margin che...

👉 Read | Calendar | @mql5dev

Markets switch regimes. A fixed 14-period moving average can track momentum in trends, then generate repeated whipsaws during consolidation. An auto-optimizer mitigates this by continuously testing a period range (for example 10–100) and selecting the parameter set that best matches current price behavior.

Direction alone is not an edge. The optimization layer scores candidates by mathematical expectancy, combining win rate and average payoff to avoid high-hit-rate/low-net systems and low-hit-rate/high-variance profiles.

Take-profit placement can be made objective. By measuring maximum favorable excursion and maintaining an average peak distance before reversal, exits can be based on observed distribution rather than arbitrary ratios.

Single-timeframe signals are filtered by higher-timeframe alignment. Multi-timeframe state checks reduce counter-t...

👉 Read | CodeBase | @mql5dev

Simple moving averages lag trend changes because they only aggregate past prices. A velocity-adjusted average can reduce that lag by incorporating the average rate of price movement into the calculation.

This indicator offers three measurement modes. Central velocity produces a smoother output. Forward velocity is calculated relative to the current bar, increasing sensitivity to recent moves. Backward velocity is calculated relative to the initial bar, preserving more information about earlier movement within the window.

Any mode aims to reduce lag versus a standard SMA, making the result suitable as an SMA replacement where faster reaction is required.

Parameters: Type selects the velocity mode. iPeriod sets the calculation length.

👉 Read | Docs | @mql5dev

Linear regression is commonly used to estimate market slope, but many MQL5 indicators recompute rolling OLS on every bar. On tick charts, large lookbacks, or multi-symbol scanners, that O(n) per-bar cost becomes a measurable bottleneck.

Recursive Least Squares (RLS) keeps a compact state and updates it with the latest observation using a Sherman–Morrison rank-1 update. The result is O(1) work per bar, independent of history length, with an adjustable forgetting factor (typical λ range: 0.95–0.99).

A complete MQL5 implementation is outlined via a reusable CRLSRegression class plus two indicators: RLSForecast.mq5 plots a 1-bar-ahead forecast on the main chart, and RLSSlope.mq5 plots a signed slope histogram in a subwindow. Both run incrementally, reset cleanly on full recalculation, and gate output until a minimum warm-up observation count is reached.

👉 Read | Forum | @mql5dev

Dingo Optimization Algorithm (DOA) was proposed in 2021 by Peraza-Vázquez et al. in Mathematical Problems in Engineering (DOI: 10.1155/2021/9107547). It is a population-based metaheuristic with three update modes plus a survival rule.

Core behaviors: group attack (subset averaging, then update relative to the best solution with a signed β1 term), chase (update biased toward the best solution using a random neighbor distance scaled by exp(β2)), and scavenging (random neighbor reference with optional sign inversion to increase step variance).

Implementation notes: a C_AO_DOA_dingo class typically exposes popSize, P (hunt vs scavenging), and Q (group attack vs chase). Moving() initializes positions once, updates survival, selects a mode per agent via P/Q, applies bounds/step quantization, then triggers a survival procedure when survival < 0.3.

👉 Read | Quotes | @mql5dev