Download files:
https://drive.google.com/drive/folders/ … sp=sharing

FSB News Companion indicator for MT4 (FSBNewsCompanion_fix5.mq4)

I tried to implement something similar for FSB Pro using the same news-feed.txt data source as used by Expert Advisor Studio .

The solution is using 3 components:

1. Downloader = data source updater for MT4
2. Gate = strategy execution filter on FSB Pro and exported strategies for MT4
3. Companion = chart UI / situational awareness for MT4 (optional)

What makes this architecture especially clean is that the three components are tightly related, but loosely coupled. They share the same local source news-feed.txt and the same health globals, but they do not overlap responsibilities. The feed is downloaded and served locally for other strategies or charts for manual trading, which makes this very lightweight.

The FSB news ecosystem achieves by splitting responsibilities into three focused components: a Downloader that maintains the local data source, a Companion that visualizes upcoming events on MT4 charts, and a Gate that applies the actual trade-permission logic inside exported strategies. The result is a workflow that is both practical and lightweight: Downloader = data source updater for MT4, Companion = chart UI / situational awareness for MT4, Gate = strategy execution filter on FSB Pro and exported strategies for MT4.

1) FSB News Downloader = feed maintenance service (FSBNewsDownloaderEAv2_2_fix1.mq4)

Uses only one FSB News Downloader EA for single MT4 instance.
Default feed refresh value is 360 minutes, do not make this smaller.

The Downloader is the foundation of the entire stack. Its role is not to decide trades and not to decorate charts. Its role is simply to keep the feed current, healthy, and locally available for the rest of the system. In the FSBNewsDownloaderEAv2_2 line, the EA downloads news-feed.txt, saves it into the MT4 files area.

Need to edit MT4 settings - allow WebRequests to https://forexsb.com

FSB News Downloader EA for MT4

2) Gate = strategy execution filter for FSB Pro and MT4 (FSBNewsGate_v2_1.cs and FSBNewsGate_v2_1.mqh)

FSBNewsGate_v2_1 was designed as a directionless LIVE MT4 news permission gate. On the FSB Pro side (.cs), the indicator keeps a clean UI and parameter contract, but always outputs allow=1 during FSB Pro runtime because the indicator is forward-looking and depends on live feed behavior. On the MT4 side (.mqh), the real blocking logic happens: it reads the offline news-feed.txt, applies symbol/currency matching, applies the configured news-priority mode and pre/post windows, and decides whether long and short entries are currently allowed.

That distinction is crucial. The Gate is not a downloader and not a visual aid. It is a strategy execution filter. It is the final policy layer that tells the strategy whether to open trades around upcoming news. In v2.1, the design was improved further by mirroring the priority mode into an MT4-visible numeric parameter so operators can choose Disabled / High only / High and Medium directly from MT4 after export. That keeps FSB Pro and MT4 aligned while still preserving the execution responsibility inside the Gate itself.

FSB NewsGate indicator for FSB Pro and MT4

3) Companion = chart UI / situational awareness (FSBNewsCompanion_fix5.mq4) (Optional)

The Companion exists because having a healthy feed is not the same as seeing the market context. FSBNewsCompanion_fix5.mq4 is deliberately chart-focused: it reads the local news-feed.txt, filters events to the current symbol, optionally includes USD on all charts, limits visibility to M1-H1 by default, and draws future events as vertical dotted markers with human-readable tooltips. It does not download anything and it does not make trade decisions. It is a visibility layer a situational-awareness tool for MT4 charts.

FSB News Companion indicator for MT4 (FSBNewsCompanion_fix5.mq4)

Download files:
https://drive.google.com/drive/folders/ … sp=sharing

I mean, there are slots like:
List:
1.Percent
2.Amount

TakeProfit = 0
StopLoss = 0;

If you choose Percent, the TP and SL values are based on the Percent. If you choose Amount, the TP and SL are based on the Amount. However, if the TP and SL values are 0, it is inactive.

This is similar to the "Account Percent Stop" indicator, but it applies the TP and SL to the same value, and there is no Amount option.

New to the Algo scene and learning the ropes with FSB atm, I am having an issue with one brokers historical data being imported into FSB pro by dragging and dropping the json files after exporting from MT5, see attached file for error. I have tried exporting wtih different settings by I get the same error. I have tried importing other currency pairs and no issues.. has anyone else had this issue before?

I downloaded the Forex Strategy Builder (CSV) from https://data.eatradingacademy.com/. I copied the files in the Import folder. Selected the Output folder. When I press Import I get this message

"Cannot find JForex files in input directory!

Import completed."

Why is that so ?

Здраствуйте  друзья!У меня вопрос!У меня портфолио из 10 роботов на монете SOL.Минимальный лот брокера 0.1 Sol.Кредитное плечо равно 2!Я удивляюсь что 10 роботов торгуют в данных портфолио с депозитом 150 долларов?Как это возможно?Портфолио заключило 600 сделок за месяц!Это значит примерно 20 сделок в день.Но гарантийное обеспечение на сделку на данный момент 85 долларов!Почему портфолио врет!Или не врет!

We released FSB Pro v4.3.4 with MQL Code v58.

Changes:
- Updated the MQL 5 code  to comply with the latest MetaTrader 5 updates
- Fixed a bug in the MQL 4 code, which causes compilation error.
- Updated the included Data Export code to v6.2 (You know that you can export files form MetaTrader and drag and drop them over FSB Pro right?)

Trade Safe!

I am trying to download the Eightcap Gold data history and it is not working, is there a problem or is it just me?

I exported some EAs from FSBPro today and tried to back test using Tick Data Suite with the all tick backtester. However I kept getting the following error.

Open prices and control points worked fine with TDS but tick backtesting did not?

Do you know why this would be and how it can be fixed?

The errors on the journal tab were:

"2024.10.24 21:19:21.259    2017.11.01 03:00:00  EA Studio EURUSD M15 210611755 EURUSD,H1: LabelDelete: failed to delete a text label! Error code = 4202

2024.10.24 21:19:21.259    2017.11.01 03:00:00  EA Studio EURUSD M15 210611755 EURUSD,H1: initialization failed (1)

2024.10.24 21:19:21.259    2017.11.01 03:00:00  EA Studio EURUSD M15 210611755 EURUSD,H1: ExpertRemove function called

2024.10.24 21:19:21.259    2017.11.01 03:00:00  EA Studio EURUSD M15 210611755 EURUSD,H1:
Cannot load enough bars! The expert needs minimum 206 bars.
Please check the "Use date" option and set the "From:" and "To:" dates properly.
"

It seems to suggest not enough bars but this has never been a problem testing EA Studio EAs and also simply by changing to control point or open prices everything works fine so it looks like something in the FSBPro code is clashing?

Help reolving so can backtest FSBPro EAs using the full tick model with TDS would be much appreciated :-)

How do implement this into my strategy where we apply the martingale system only when we experience a loss. Here's how it would work across three scenarios:

First Scenario:

First trade: If we lose with a lot size of 0.01, then
Second trade: Double the lot size to 0.02. If this trade wins, revert to the original lot size of 0.01 for the subsequent trade.

Second Scenario:

First trade: If we lose with a lot size of 0.01, then
Second trade: Double the lot size to 0.02. If this trade also loses, then
Third trade: Increase the lot size to 0.03. If this trade wins, revert back to 0.01 for the next trade. If it loses, continue increasing the lot size for the following trade.

Third Scenario:

First trade: If we win with a lot size of 0.01, continue using the same lot size for the next trade.
This strategy uses incremental increases in the lot size following losses, with a reset to the base lot size following a winning trade.

Please note that I want to maintain the martingale system as follows: if the initial trade with a lot size of 0.01 results in a loss, increase the lot size for the next trade to 0.02. If this trade also results in a loss, then increase the lot size to 0.03 for the subsequent trade, and so forth. Continue this pattern, incrementally increasing the lot size by 0.01 after each loss, until a win is achieved.