CNewsFilter provides a single decision point for EAs: whether the current time falls into a configured news blackout window. It reads the built-in MT5 economic calendar, filters by selected currencies and minimum importance, and blocks trading minutes before and after each release.

Integration focuses on a small API: SetCurrenciesFromSymbol(symbol) for base/profit/margin currencies, or SetCurrencies("USD,EUR"). Use SetImportance(low/moderate/high) and SetWindow(before, after). IsNewsTime() returns true inside the window. CurrentEvent() and NextEvent() expose event name, currency, and time for UI panels. Total() and Event(i) return the loaded events sorted by time. SetRefresh(seconds) and SetLookAhead(hours) control cache refresh and horizon.

Operational notes: no web requests, DLLs, or terminal permissions. Times are trade-server time (TimeTradeServer()). O...

👉 Read | VPS | @mql5dev

Expert Advisors tag trades with a magic number. Magic Number Scorecard groups closed account trades by magic number to produce one result line per EA; magic 0 represents manual trading. This provides a fast view of which systems generate net results versus volume.

Per magic number, the report includes trades, wins, losses, win rate, gross profit, gross loss, profit factor, net profit, average trade, best and worst trade, maximum drawdown based on the closed-trade equity curve, and symbols traded. Rows are sorted by net profit.

Counting rules: one trade equals one closed position. All related deals are aggregated, including profit, swap, commission on entry and exit, and fees. Partial closes still count as one trade. Ownership is taken from the opening deal’s magic number, so manual closes remain attributed to the originating EA. Open or partially open positio...

👉 Read | Freelance | @mql5dev

MTF Trend Context [Vian] is a compact MT5 panel that reports trend state across five selected timeframes and summarizes alignment as ALL BULLISH/BEARISH, MOSTLY BULLISH/BEARISH, or MIXED.

Trend classification uses a single EMA rule per timeframe: Bullish when Close > Fast EMA > Slow EMA, Bearish when Close < Fast EMA < Slow EMA, Neutral otherwise. Default EMA lengths are 20 and 50, both configurable with Slow required to remain greater than Fast.

Each row is evaluated on the most recently closed bar of its own timeframe (shift 1), avoiding the current forming candle. Data readiness is validated before display; missing history or incomplete EMA calculations are shown as N/A rather than inferred.

Presets cover Scalping, Intraday, and Swing, plus a five-timeframe Custom set. If any row is N/A, alignment is not upgraded and remains MIXED with a count of...

👉 Read | Freelance | @mql5dev

A risk-check script estimates worst-case gap losses for all open positions ahead of weekend or holiday closures. It sums the projected losses and compares them with the remaining room under the next trading day’s daily loss limit.

Output includes the next day’s limit in account currency, the floating loss carried over, and per-position details: symbol, side, lots, configured gap for its group, and the loss that gap implies. A final verdict flags OK or TOO MUCH, including a per-position reduction amount.

Key point: stop-loss orders do not cap gap risk, since fills occur at the first available price after the gap.

Inputs cover account size (or current balance), daily loss limit and safety margin, whether carried floating loss counts against the next day, per-asset gap percentages (FX, metals, indices, crypto, other), and symbol group matching via name fr...

👉 Read | Signals | @mql5dev

MarketInfo is an information script for MetaTrader 5 that logs key telemetry for the active instrument and outputs a chart comment for quick review.

It reports current Bid, Ask, and spread in pips, along with symbol parameters such as minimum and maximum lot size, lot step, and price digits.

Volatility is calculated using ATR for a configurable period. The script also shows the time remaining until the current bar closes to support timing-sensitive execution and monitoring.

For a user-defined number of recent bars, it aggregates high, low, average close, average volume, and average range. A simple classification marks the current state as upward, downward, or sideways based on recent price behavior.

👉 Read | Docs | @mql5dev

MA Crossover EA is an automated strategy that places trades when two moving averages intersect. It supports any instrument and timeframe, with configurable fast and slow MA periods.

Trade logic is limited to one open position at a time. A BUY is opened when the fast moving average crosses above the slow moving average. A SELL is opened when the fast moving average crosses below the slow moving average.

Risk controls include optional Stop Loss and Take Profit levels defined in pips. Execution can be restricted to bar-close signals via a TradeOnNewBar setting to reduce intra-bar noise.

Key inputs typically include lot size, FastMAPeriod, SlowMAPeriod, StopLoss, TakeProfit, and a MagicNumber for trade identification. Validation in a strategy tester and parameter optimisation per symbol are recommended before live use.

👉 Read | VPS | @mql5dev

This article shows how to build market-pattern models in MetaTrader 5 using CatBoost, focusing on a small, well-chosen feature set instead of endless hand-tuned trading rules. The goal is to reduce overfitting caused by optimizing many inequalities across symbols and periods.

A practical pipeline is outlined: generate predictors and a binary target directly from an MQL5 Expert Advisor, export samples to CSV, train CatBoost via a standalone exe (no Python/R), then run the trained model in MT5 using a CatBoost interpreter class.

Feature engineering emphasizes context: time features, price position vs. key levels, volatility, and oscillator values across multiple timeframes, sampled at several bar offsets to capture dynamics. The baseline signal is a simple MA-cross trend entry; ML is used to filter false entries in flat markets while keeping implementation ac...

👉 Read | Quotes | @mql5dev

Mean reversion triggers can be gated by a convergence indicator count to reduce noise. This setting defines how many independent signals must align before a reversion event is allowed to fire.

A lower threshold such as 5 increases trade frequency and can react earlier, but typically raises the false-positive rate in ranging conditions with weak confirmation.

A higher threshold such as 9 is more selective and may improve signal quality, but can delay entries and miss shorter reversals. Practical selection depends on symbol volatility, timeframe, and the number and correlation of indicators feeding the convergence check.

👉 Read | Forum | @mql5dev

A refreshed design-oriented market price view has been released, focused on clearer trend visibility and a cleaner chart presentation.

Deployment requires adding a bitmap asset. Download Mr.Wave.zip, extract surfer.bmp, and place it in the platform’s Images directory so the interface renders as intended.

If the image is missing or stored in a different path, the UI will fall back to a blank placeholder or fail to display the visual element, which can lead to inconsistent layout across installations.

👉 Read | Quotes | @mql5dev

Spread Monitor is a lightweight information indicator for MetaTrader 5 that shows the current spread in pips in real time.

The data is presented as a compact on-chart panel with colour-coded status markers and a level bar for quick visual assessment.

Designed for low overhead and continuous monitoring, it helps track spread changes during varying liquidity conditions and around news-driven volatility.

👉 Read | CodeBase | @mql5dev

Market structure can be quantified by tracking sequences of higher highs/higher lows or lower highs/lower lows, and flagging when that pattern changes. This indicator applies fixed swing rules and prints non-repainting labels.

Swing highs/lows are confirmed only after N candles close to the right (default N=5), so markings appear with a delay and never shift. Each confirmed swing is classified as HH/LH versus the prior swing high, and HL/LL versus the prior swing low.

Break logic supports BOS and CHoCH. BOS is triggered when a candle closes beyond the last swing in the current trend direction and is drawn as a dashed line. CHoCH is triggered when a candle closes beyond the last swing against the active trend and is drawn as a solid line. Break detection can use close (default) or wick.

Inputs include swing strength, bars to scan (default 3000), disp...

👉 Read | CodeBase | @mql5dev

Multi-period indicators with shifted lines require converting the shift into the current chart’s bar scale. A 1-bar shift on H4 becomes 4 bars on H1, and buffer copying must start from a shift-adjusted reference index to align values correctly.

Library updates: buffer shift setters now allow shifts on calculated buffers, and calculated buffer copy uses the line shift with an inverted sign to select the correct source start. Indicator factory methods (MA/AMA/DEMA/TEMA/VIDYA/Bands/Alligator, etc.) compute shiftBars = shift * periodBarRatio, pass that to the native handle, and apply the same shift to drawn and calculated buffers.

Common logic was consolidated: standard line types were normalized across indicators, universal preparation/clearing paths were reduced to 1/2/3-line cases, and a buffer-clear routine prevents artefacts from inactive indicators...

👉 Read | AppStore | @mql5dev

A new indicator package is available featuring a “Good Tendency Estimator” combined with coloured candlesticks. The estimator is designed to quantify directional bias and highlight potential transitions in trend conditions, while the candle colouring provides a fast visual filter for momentum and regime changes.

Typical usage focuses on aligning entries with the estimator’s direction and using colour shifts as confirmation or early warning. Key points to validate during testing include behaviour in low-volatility ranges, sensitivity to parameter changes, repainting risks, and performance across symbols and timeframes.

👉 Read | Freelance | @mql5dev

Perplexity AI is being used to accelerate development of rule-based trading systems by generating code drafts, test cases, and documentation for common patterns such as trend filters, mean reversion triggers, and risk controls. Output still requires strict validation: confirm indicator math, verify order sizing, and reconcile bar indexing to avoid lookahead.

A production-ready setup typically includes deterministic backtests, walk-forward checks, and Monte Carlo analysis on execution assumptions. Logging, parameter constraints, and fail-safe handling for connectivity and rejected orders are mandatory.

AI assistance can reduce iteration time, but strategy quality remains dependent on data hygiene, robust statistics, and disciplined change control.

👉 Read | Signals | @mql5dev

Mistral Trend Candles color-code trend state using Hull MA slope and an ADX regime filter.

Green marks a confirmed uptrend when the slope is above the configured threshold and ADX indicates a trend regime. Red marks a confirmed downtrend under the same conditions.

In weak or lateral markets, candles retain the last confirmed trend color to keep continuous green/red zones for faster visual reading.

The logic is non-repainting: closed candles keep their final color. Only the currently forming candle can change until close.

Rendering uses chart objects placed above native candles, fully covering them.

For M1–M5, lowering ADX_TrendMin to ~18–19 can improve responsiveness. Higher timeframes typically need a higher ADX_TrendMin. HMA_Period and Slope_MinATR control reactivity and noise tolerance.

👉 Read | AlgoBook | @mql5dev

DeepSeek Quantum Apex Color is a chart-based indicator intended to visualize the dominant trend while reducing noise through a rules-based filter stack.

Regime filtering is driven by ADX. Trend-following logic is active only when directional strength exceeds a threshold (default >20), limiting signals during sideways conditions.

Momentum and exhaustion checks combine RSI and Z-Score. RSI provides directional bias (RSI >50 long, <50 short), while Z-Score measures price deviation from a moving average to reject statistical outliers and reduce early entries.

Signal history is computed on the last closed bar (Bar 1) to avoid repainting and keep backtest results consistent.

👉 Read | Forum | @mql5dev

A trend-following trading system built around OpenAI models typically separates signal generation from execution and risk controls. Market data is normalized into features, prompts are constrained to structured outputs, and model responses are treated as probabilistic inputs rather than deterministic rules.

Key design points include strict data boundaries to prevent leakage, reproducible backtests with walk-forward validation, and hard limits on position sizing, leverage, and drawdown. Execution should rely on deterministic order logic, while the model is limited to regime classification, filtering, or parameter selection.

Operational requirements include latency and rate-limit handling, audit logs of inputs and outputs, and continuous monitoring for drift. Any deployment should include fail-closed behavior and clear rules for disabling automation un...

👉 Read | NeuroBook | @mql5dev

A source text is required to generate the post. Only “by Grok AI” was provided, which is not enough to rewrite into an 800-character technical news-style update.

Send the full text to convert, and include any constraints such as platform (X/LinkedIn), product/topic, and whether company or project names must be kept or removed.

👉 Read | Forum | @mql5dev

Spread Monitor is a lightweight information indicator for MetaTrader 5 focused on real-time spread visibility.

It shows the current spread in pips along with Bid and Ask values. The display uses configurable color states (green, yellow, red) to reflect low, medium, and high spread conditions. Language support is available in Russian and English. The UI is limited to a single text panel to keep chart rendering clean.

Key settings include language selection, X/Y offsets for panel placement, MidThreshold and HighThreshold in points, per-state colors (ColorLow/ColorMid/ColorHigh), and font size.

Typical use is spread verification before order placement, especially around news releases and during low-liquidity sessions where execution costs can change quickly.

👉 Read | NeuroBook | @mql5dev

This EA builds signals on a classic two-brick Renko reversal. Oscillators update only on completed bricks, with one active mode: RSI Re-entry, RSI Midline, MACD Signal, or MACD Zero. RSI uses Wilder smoothing; MACD is EMA-diff with an SMA signal line. Periods count completed bricks. Multi-brick completion in one tick updates per brick, but only the last brick can trigger an entry. Orders execute at market quotes; blocked signals are not queued.

Entry is blocked if a position or order already exists for the symbol/Magic. Exits rely on virtual SL/TP or a holding-time limit; opposite signals do not close positions. A brick-based cooldown applies after exit; spread-to-brick filtering affects entries only.

A included test example reports XAUUSD M1 real-tick backtest results (Jan–Oct 2026): 178 trades, PF 1.49, max DD 5.99%, net profit $2,348.57. Parameters were chos...

👉 Read | VPS | @mql5dev

A Risk of Ruin script estimates the probability of hitting a defined drawdown floor before a strategy’s edge shows up. It reads closed trades from account history, converts each result into an R-multiple (net P&L divided by average absolute loss), then runs a bootstrap simulation.

Each simulated path resamples historical R-multiples with replacement, applies a user-selected risk % per trade, compounds equity trade by trade, and flags “ruin” if equity drops below the configured floor. The method is independent of the original traded lot sizes; only the win/loss distribution and current risk settings drive outcomes.

Reported metrics include chance of hitting the floor, chance of ending profitable, median ending balance, and the 95% range of final balances. Median is used to reduce distortion from long-tail winners. Higher risk per trade typically increases th...

👉 Read | AppStore | @mql5dev