Part 2 extends the Cairo-style split between geometry and rendering by adding Path.mqh as a common shape representation.

A path is geometry only: points grouped into outlines, with no color, thickness, fill rule, or destination buffer. This removes shape-specific render loops and enables reuse across different fills and transforms.

Points are stored as doubles to preserve sub-pixel coordinates. This is required for later anti-aliasing, smooth animation, and curve flattening without quantization.

A path can contain multiple contours (open or closed) to support glyph holes, rings, borders, and multi-part icons. Storage uses one flat vertex array plus a contour start index array and a closed-flag array for contiguous traversal and low overhead.

👉 Read | AlgoBook | @mql5dev

Gopalakrishnan Range Index (GRI), published in TASC in 2001, measures market activity using the closing-price range over N bars, normalized on a log scale. It remains a practical volatility gauge and is easy to implement in MetaTrader 5.

Implementation computes High/Low of Close over ChaoticPeriod, takes log10(range)/log10(N), returning 0 when range is zero. For range < 1, values become negative; a shifted range can clamp the minimum toward zero. Scaling by Point makes thresholds usable in EA inputs.

In testing, an EA using TEMA for direction and AMA for confirmation improved behavior when trades were filtered by rising GRI, avoiding low-activity phases. GRI is a condition filter, not a directional signal, and benefits from per-symbol threshold calibration and backtesting.

👉 Read | Quotes | @mql5dev

Post-trade stats typically report what a trade earned. This utility records what each trade had available, and what it returned.

On first detection it captures the initial stop distance as 1R, then measures max favorable and adverse excursion in R until the position closes. Trailing stops do not alter the reference, so the measurement stays consistent.

One CSV row per closed position is written to MQL5\Files: ticket, symbol, side, open/close time, entry, risk distance, peak R, worst R, realised R, and profit. Trades without a stop are skipped and counted.

Use case: equity curves that spike and fade can come from trades reaching high peak R and giving it back, or from trades never traveling far. Comparing average peak R vs realised R, plus average giveback on the chart panel, separates these cases.

The EA is read-only: no open/modify/close. Attach alongsid...

👉 Read | VPS | @mql5dev

A read-only MQL5 Expert Advisor logs each closed position to CSV with market-state context at entry and exit. Recorded fields include RSI, Stochastic, EMA20/EMA50 distance, Bollinger %B, ATR, and ADX on two timeframes, enabling post-trade rule reconstruction and strategy evaluation without relying on undocumented logic.

Several data-loss traps are handled explicitly. Deduplication avoids position_id and close_time watermarks; position_id reflects open order, not close order, and datetime has 1-second resolution. A set of logged position IDs is rebuilt from the CSV on restart. HistorySelectByPosition() is isolated from the main scan to prevent global history selection from being overwritten during iteration.

Close detection includes DEAL_ENTRY_OUT and DEAL_ENTRY_OUT_BY. Magic filtering reads the opening deal’s magic, not the closing deal, to avoid dropping m...

👉 Read | AlgoBook | @mql5dev

MetaTrader 5 includes an economic calendar accessible from MQL5 via CalendarValueHistory(), but external tooling cannot query it. The Python MetaTrader5 package exposes market data and trading state, yet provides no calendar API, leaving research scripts, dashboards, bots, and spreadsheets blind to upcoming releases.

A read-only Expert Advisor can bridge this gap by exporting calendar data to a CSV file under MQL5\Files on a fixed interval. It never opens, closes, or modifies positions.

Key implementation points: UTF-8 output to preserve localized event names, chronological sorting across currencies, atomic write (build in memory, then write once), HTML entity decoding (e.g., S&amp;P), and a freshness header with server time, event count, and UTC offset. Update time is taken from the trade server clock, not the last tick.

Inputs include currency filter, ho...

👉 Read | AlgoBook | @mql5dev

Trade Guardian is a defensive Expert Advisor designed for risk supervision rather than trade entry. It monitors existing positions and reacts when configured limits are breached. Each function is independent, and position closing is disabled by default to allow warning-only operation on live charts.

Stop-loss enforcement checks open positions on timer events and flags orders without a stop. If enabled, it places a stop at an ATR-based distance using the chart timeframe, respecting a minimum distance in points and the broker stop level. Stops are applied only to the chart symbol.

Risk limits include a daily loss cap referenced to the balance at the day’s start, auto-refreshed on each new day, and a total drawdown cap referenced to the equity peak. A cooldown can rebase the peak to current equity so the guard can re-arm, with rebase events logged.

Scope can ...

👉 Read | Forum | @mql5dev

EOSA (Ebola Optimization Search Algorithm, 2021) is a bio-inspired metaheuristic derived from a SEIR-HDVQ epidemic model, mapping short-range transmission to exploitation and long-range transmission to exploration. Quarantine is used to reduce premature convergence by keeping part of the population static.

A literal implementation exposes issues in the paper’s core equations: missing direction vectors in movement updates, identical exploitation/exploration forms, and a bounds bug in initialization (L + rand(U+L) instead of L + rand(U-L)). These defects can cause non-improving motion and rapid population collapse.

A practical variant keeps the intended mechanics but simplifies to active agents only, adds directed moves, pBest memory, fitness-biased strategy selection, Lévy flights for global search, and a ρ schedule from 1.0 to 0.5, with boundary re...

👉 Read | NeuroBook | @mql5dev

This article focuses on practical debugging in MQL5 using MetaEditor and the terminal logs, bridging the gap between basic syntax and building reliable Expert Advisors.

It breaks down compiler diagnostics (warnings vs errors, file/line/column navigation) and shows why fixing issues top-to-bottom reduces cascading messages, especially when porting MQL4 code with mismatched function signatures.

Runtime failures get equal attention: dynamic arrays without sizing, “array out of range” cases from unloaded history or off-by-one indexing, and silent logic bugs where an EA simply never trades.

The workflow starts from entry points (OnInit/OnStart, OnTick/OnCalculate, OnTimer), encourages structural analysis, buffer/property checks for indicators, and uses targeted Print/PrintFormat output to pinpoint control-flow mistakes like an accidental semicolon after a loop.

👉 Read | AlgoBook | @mql5dev

This article builds a Fisher Transform–style oscillator for MetaTrader 5, showing how to turn recent price position into a bounded value, smooth it, clamp it near ±1 to keep the logarithm stable, then apply the log transform and recursive smoothing to make extremes and reversals visually sharp.

Key implementation work focuses on correctness in MQL5: preserving recursive state via a calculation buffer, handling series indexing consistently, guarding minimum bars and zero-range windows, and recalculating only new bars for performance.

For trading logic, the signal is not a threshold cross. It waits for the line to exceed an extreme (often ±1.5 to ±2) and then turn back toward zero on closed bars, enabling a non-repainting EA to act on confirmed peaks/troughs across symbols.

👉 Read | Forum | @mql5dev

This article turns the reusable CSwingEngine into a double top/bottom detector that prioritizes market structure over chart “shapes”. The EA first confirms H4 trend (up for double top, down for double bottom) using labeled swings (HH/HL or LL/LH); if the context is range, it refuses to evaluate the pattern.

Validation is based on confirmed swing points: two matching swings with exactly one opposite swing between them, peaks/troughs within a configurable H4-ATR tolerance, a minimum pattern height in H4-ATR, and time width measured from swing timestamps. ATR is always taken from the swing timeframe to keep thresholds scaled to structure.

Execution is separated from detection via a three-state machine: scan, lock a single pattern once, then wait for a neckline break on the trading chart timeframe with expiry and “no re-entry” identity tracking. Entries add pra...

👉 Read | Calendar | @mql5dev

Mamba4Cast is presented as a modular time-series forecasting core for high-frequency market data, combining compact feature extraction, multi-window convolutions for noise-resistant signal detection, and an SSM-based long-memory block to keep context across dozens of candles. A key design choice is forecasting across the full planning horizon rather than only the next step, improving stability for trading decisions.

The framework is integrated into an Actor–Director–Critic agent. The Environment State Encoder normalizes raw OHLCV and indicators (using noisy batch norm for better generalization), adds H1/D1 harmonic time embeddings, then applies stacked convolution + pooling + Chimera SSM blocks, followed by a convolutional decoder and denormalization.

The Actor aligns account state with per-feature latent embeddings via stacked cross-attention before...

👉 Read | Forum | @mql5dev

Destructors in MQL5 become clearer when compared to MetaTrader’s event model. OnInit/OnDeinit behave like constructor/destructor pairs: allocate resources (create chart objects) on init, and reliably release them on deinit.

The article refactors a simple regression-channel example from an indicator into a script, then into a class where the destructor (~ClassName) deletes the OBJ_REGRESSION automatically when the instance goes out of scope. No explicit call is needed; lifetime rules trigger cleanup.

Key rules: destructors return nothing, take no parameters, and are invoked implicitly. To reuse the pattern across scripts, indicators, and EAs, the class is moved into a header and included where needed, making chart-object management predictable and leak-free.

👉 Read | AppStore | @mql5dev

An EA can place a valid trade while still accumulating unsafe account exposure. Multiple “correct” entries on the same symbol can turn 1% per trade into 3–6% combined risk, increase margin usage, and extend time spent underwater.

The fix is basket accounting: total volume, volume-weighted average entry, floating P/L including swap, estimated margin via OrderCalcMargin, position count, oldest open time, plus MAE/MFE and peak count for diagnostics. Netting vs hedging changes what “position count” means, but money-based aggregates still apply.

Controls split into every-bar protections (aggregate loss cut, time stop, MAE tracking, pending-order cleanup) and pre-trade admissions (position ceilings, margin ceilings, implied-risk caps). A target-sized mean-reversion demo highlights that profit-target sizing makes risk an output, requiring separate implied-loss che...

👉 Read | CodeBase | @mql5dev

Backtests showing 0% history quality usually come down to missing tick data. A tester can still run across periods with no real ticks, silently generating ticks from M1 bars. That produces smooth intra-bar movement, no gaps, no spread expansion, and can make fragile systems look profitable, especially grids, martingales, tight-stop scalpers, and small-target strategies.

A TickAudit script queries the terminal month by month and prints what exists before running a test: real ticks, partial ticks (holes), GENERATED TICKS (bars only), or nothing. The key risk is months that have bars but no ticks, because they still output results.

Outputs include the month where continuous real ticks begin and how many months would force synthetic ticks. Options include a full daily scan (slow), sampling, a wait time for downloads, and optional CSV export. It places no or...

👉 Read | Calendar | @mql5dev

A harmonic pattern script can reduce late entries by combining multi-scale structure detection with live PRZ validation.

A dual Zigzag engine runs “Major” and “Minor” wave scans in parallel. The logic prioritizes macro setups, then falls back to minor structure when the broader swing becomes noisy.

Point D is tracked in real time using the current candle wick, updating Fibonacci ratios as price moves into the Potential Reversal Zone instead of waiting for a confirmed pivot.

Entry signals are gated by RSI momentum exhaustion. Bull and Bear triggers are issued only when Point D forms and RSI crosses the configured oversold/overbought thresholds.

On trigger, risk and targets are plotted automatically: TP1 at 38.2% and TP2 at 61.8% of the A–D retracement. Stop loss is placed 20% beyond Point D’s structural size to account for deeper extensions.

👉 Read | NeuroBook | @mql5dev

Grid, martingale, and averaging risk is often misread by focusing on loss at the last planned level. Account failure typically happens earlier, when margin level hits broker stop-out while the position chain is still open.

A read-only EA calculates the adverse move that triggers stop-out, then scans the symbol’s M1 history to count how often a move of that size occurred over a chosen window. This turns a cash figure into a probability-relevant frequency and shows whether failure occurs before the configured leg cap is reached.

Key corrections: floating loss grows as step × N(N−1)/2, not step × N. Margin usage rises with open legs, so equity drops while margin used increases. Stop-out is percentage-based, so liquidation can occur after partial equity loss.

Outputs include full chain span, floating loss, margin locked, stop-out move distance, legs open at st...

👉 Read | AppStore | @mql5dev

A lightweight approach to customizing the MetaTrader 5 AI Assistant is shown via a prompt file generated by an MQL5 script. The assistant’s language, persona, menu structure, and response behavior can be adjusted by editing a plain text prompt, without using an AI API, DLL, or external service.

The AI_Prompt_Writer.mq5 script writes AI_Prompt.txt into the terminal’s MQL5\Files folder. Users select one of 11 response languages and a predefined persona, optionally set the output filename, and choose whether to overwrite an existing file. After loading the prompt in the assistant, a custom numbered menu becomes available for actions such as news checks, chart analysis, and trade review.

The sample is positioned as a template rather than a complete solution. It also enforces strict safety limits: no order placement or modification, no position management, no para...

👉 Read | Quotes | @mql5dev