Barmenteros Fx

Barmenteros Fx We firmly believe that striving for perfection is the road to excellence. We also program for TradingView, NinjaTrader and TradeStation.

With this as our keystone, we provide tailored MT4 programming service (also MT5) for Forex traders worldwide. With this as our keystone, Barmenteros FX is devoted to providing tailored MT4 programming service (also MT5) for Forex traders worldwide. In addition to MetaTrader, we also program for other popular trading platforms as TradingView, NinjaTrader and TradeStation. With years of experience,

we have improved the methods and processes that enable us to create high-quality, robust and stable programs for Forex market. We aim to create long term partnerships with our customers by exceeding expectations with a top level of professionalism, honesty, and transparency.

Your converted Expert Advisor compiled without a single error, and that is the part nobody should find reassuring.Since ...
21/08/2026

Your converted Expert Advisor compiled without a single error, and that is the part nobody should find reassuring.

Since MetaTrader 5 build 6060 in July 2026, the MetaEditor your EA already lives in ships an AI assistant, free on the MQL5 Lite plan. One of MetaQuotes' own published example prompts reads: "Convert this MQL4 Expert Advisor to MQL5 using modern language features and the Standard Library." The conversion is now one prompt away. The checking is not.

The characteristic failure of an MT4 to MT5 migration does not produce anything wrong to find. It produces an absence — something that should have happened and didn't. The compiler, the Strategy Tester and the demo account are error detectors, and this failure class does not produce errors.

One break-even manager held three open positions and moved none of them to break-even. The loop iterated OrdersTotal(), which on MT5 counts pending orders only. Three positions, no pending orders, so a faithfully recompiled MT4 loop correctly iterated over nothing. Time to detection: indefinite. There was no event to notice.

The one that costs more is subtler. A crossover EA read the wrong end of a CopyBuffer array, and because the wrong-end read applied uniformly to every bar, the equity curve came out mediocre rather than obviously broken. A broken backtest gets investigated. A mediocre one gets re-optimised — and every hour of that work fits the parameters more tightly to the bug.

Translation is not the risky part. These tools are good at it. The risky part is that a clean compile plus a matching backtest is the specific pair of signals least able to detect how conversions actually break.

If the failures are absences, the only way to find them is to write down what should be present before you go looking. Which of your EA's actions would leave no trace at all if they silently stopped happening?

10/08/2026

Six months of manual entries, and the only losing trades were the ones taken late. What varies between a good and a bad ex*****on of the same rules is the seconds between the bar closing and the order going in. That is latency, not discipline.

Six months of manual entries, and the only losing trades were the ones you took late. That delay is a code problem, not ...
05/08/2026

Six months of manual entries, and the only losing trades were the ones you took late. That delay is a code problem, not a discipline problem.

Most traders who come to us for automation open with an apology. They tell us their ex*****on has been inconsistent, that they have been chasing entries, that they need to be more disciplined.

Then we look at the trade log, and the pattern is almost always the same. The setups were identified correctly. The rules were applied correctly. What varied was the number of seconds between the bar closing and the order going in — and the trades that lost were disproportionately the slow ones.

That is not a character flaw. It is a latency problem, and it has an engineering solution.

Here is the part worth being precise about: automating a strategy does not improve the strategy. If the rules have no edge, executing them faster produces losses faster. What automation removes is the variance you did not choose — the entry you missed because you were in a meeting, the one you hesitated on because the last two lost, the one you took four candles late because you were asleep when the London session opened.

The engineering that matters is mostly invisible. It is what happens when the terminal restarts mid-position and the EA has to know what it already owns. It is what happens when the broker fills you partially, or requotes, or moves the stop level under you. A backtest never shows any of this, which is why code that passes one can still fail on a live account overnight.

We build from your rules, not a template and not an AI first draft that compiles cleanly and then behaves unpredictably with real money on it. Scope is defined by tier, delivery typically runs two to six weeks depending on complexity, and support continues after the invoice.

We will not tell you what your strategy will return. That was always yours. We will tell you it fires the same way every time it triggers.

If you have a strategy you have traded manually long enough to trust, describe it to us and we will scope it properly — what it takes, what it costs, and what the tier boundaries actually mean. Link is in the first comment.

04/08/2026

A clean compile proves the syntax is valid. It never checks whether the right order was selected before the close, what happens when the broker rejects a request, or whether your Expert Advisor still knows its positions after a restart.

Checking whether a prop firm allows Expert Advisors is the one condition almost nobody is disqualified under.Automation ...
29/07/2026

Checking whether a prop firm allows Expert Advisors is the one condition almost nobody is disqualified under.

Automation permission is not where firms compete. They differentiate on payout splits, drawdown limits, and challenge fees. Whether you may attach an EA is a checkbox, and a checkbox reading "yes" says nothing about the conditions attached to it.

What ends automated accounts is a second layer of rules that never mentions Expert Advisors at all. Those clauses restrict behaviour: how long a position stays open, when orders may be placed, how quickly they follow a price move, and how many accounts carry correlated flow.

There are five families worth reading for. Minimum hold time. News window restrictions. Tick scalping and latency clauses. Account correlation and copy trading. Prohibited strategy classes.

Only one of the five can an EA evaluate about itself with no outside input. Three more become checkable once you supply what the code cannot derive — a hold-time threshold, your firm's event list mapped onto a calendar feed, a latency limit. The last one it cannot resolve at any price.

That last one is account correlation, and it is the reason a code review is not enough. Running the same strategy across several evaluations, or beside a personal account, produces near-identical order flow. The EA is compliant. The deployment is not. A code audit clears it every time because there is nothing in the code to find.

Which means the ordering matters. Work the clauses your EA cannot resolve on its own first — those are settled before it ever runs, by how you deploy rather than by what you write.

If you are about to pay a challenge fee, the useful question is not whether the firm allows EAs. It is which of the five your EA can enforce, which it can only detect, and which no code change reaches.

28/07/2026

Your Expert Advisor compiled on the first try — and that is the part that should worry you. A clean compile proves the syntax is valid, not that the code will behave correctly with real money on the line.

This is the exact order we read an Expert Advisor in when a trader sends one for review, along with the written report that comes back. If you would rather have the ex*****on path read for you, start here.

Your EA compiled on the first try. That's the part that should worry you.A clean compile proves one thing: the syntax is...
22/07/2026

Your EA compiled on the first try. That's the part that should worry you.

A clean compile proves one thing: the syntax is valid. The compiler confirmed your brackets match and your types line up. It did not check whether the code selects the right order before modifying it, what happens when the broker rejects a request, or whether the EA still knows about its open positions after a terminal restart.

That gap is where most of the AI-generated code we review fails. The generator writes something plausible, and plausible compiles. The confidence is real; the accuracy is not.

So here is the order we actually read an EA in, when a trader sends us one to review.

First, initialisation and state. What does this code know when it starts, and where does that knowledge come from? If the answer is "whatever is in memory," the EA has already lost every position it held before the last restart.

Second, the order-selection path. Every modification, close, or partial close depends on having selected the correct order first. We trace each one back to the selection that precedes it. This is where wrong lot sizes and orphaned trades are usually born.

Third, the error-return path. Every broker request returns a result. We follow what the code does with each one. In most reviewed code, the answer is nothing at all, which means failures happen silently and the account absorbs them without a single log line.

Three checks you can run yourself, before calling anyone: search your code for every close or modify call and confirm a selection precedes it; search for the return value of each trade request and confirm something reads it; restart your terminal mid-trade and see whether the EA still recognises its own position.

If those three checks make you uncomfortable, that discomfort is the useful signal. We do standalone reviews with a written report, so you understand what was wrong before deciding who fixes it.

21/07/2026

The MQL5 Market covers marketplace sales — not your direct sales, custom builds, or trials, where an account-number check protects nothing.

16/07/2026

.ex4 files reach pirate forums within days of release, and a hardcoded check can't disable a leaked copy — every download after that is a lost sale.

11/07/2026

The licensed account is baked into your source, so every new customer means another edit and recompile — miss one and you ship a build that runs anywhere.

Dirección

Avenida Principe Salman, 6, 5th-JEW
Marbella
29603

Horario de Apertura

Lunes 09:00 - 17:00
Martes 09:00 - 17:00
Miércoles 09:00 - 17:00
Jueves 09:00 - 17:00
Viernes 09:00 - 17:00

Teléfono

+34951898160

Página web

Notificaciones

Sé el primero en enterarse y déjanos enviarle un correo electrónico cuando Barmenteros Fx publique noticias y promociones. Su dirección de correo electrónico no se utilizará para ningún otro fin, y puede darse de baja en cualquier momento.

Atajos

Compartir

Categoría