What kinds of fault do you fix?

Freezes, order and execution errors, memory growth, wrong lot or stop calculations, and logic that does not match what the robot is meant to do.

I only have the .ex5 file. Can you still help?

No. Without the readable source nothing can be fixed, so I need the .mq5 files.

Will the repair make it profitable?

No. A repair only makes the robot follow its own rules. Judging the rules themselves is outside this package.

What if it cannot be saved?

Then I tell you what I found and why, and you are not charged for a repair I could not carry out.

Can you add a feature while you are inside the code?

Not within this package. A new feature is a separate job, which keeps the repair easy to check.

Is my code kept private?

Yes. I do not share or reuse your code. Ask before sending it if you want a written confidentiality note.

Fixed price · €65

Fix an Expert Advisor

Your robot hangs when the market gets busy, throws order errors, or trades differently from what its rules say. Perhaps the person who wrote it has gone quiet. I read the code, find the faults and repair them, or I tell you plainly when it is better to start again.

Please read. An Expert Advisor is a tool that follows rules. It does not predict the market, trading carries a high level of risk, and nothing I write comes with a promise of profit. Test every program on a demo account first, and use a real account only when everything works as you expect. Read the Risk Disclosure.

Who it is for

Owners of an Expert Advisor with the source file that no longer behaves
Traders whose developer disappeared or left the job half done
People who bought or inherited a robot and cannot tell whether it is sound

Price

€65 fixed, EUR, no VAT added

For a standard case as described on this page. If your case is bigger, I tell you before any extra work.

Ordering opens soon Ask me about this package

What is included

A line by line look at your MQL5 source, covering the trading logic, how orders are sent and confirmed, and anything that can stall the terminal
Repairs for the faults I find, such as endless loops, wasteful indicator calls, order requests that are never checked, and rules that contradict each other
A straight answer if the code is too tangled to patch, with what a clean rebuild would involve
The repaired robot run on a demo account
The repaired files and a short list of what was wrong and what I changed

What is not included

New features or a changed strategy. Those start a separate job so that the repair stays clear
Robots you only hold as a compiled file (.ex5). Without the source nothing can be repaired, and I do not take apart other people's programs
MQL4 files, which belong to the Convert package
A full rewrite. If one is needed I say so and quote it separately
Any promise that the robot will make money after it is repaired

What you receive

The repaired source and the compiled file
A change list: what was wrong, what I changed and why
My demo-account test notes
A clear recommendation if I think the project should be rebuilt instead

How it works

Send the source and the symptoms. Attach the .mq5 files and tell me what you expected and what you actually see.
I read and reproduce. I go through the code, try to reproduce the fault, and keep notes on each cause.
You hear the verdict. Before I spend your money I tell you whether the code can be saved, and what the repair will touch.
I repair and test. I fix the faults and run the result on a demo account.
Delivery and a week of follow-up. You receive the files and the change list, and for seven days I fix any genuine bug in what I changed, in up to three rounds.

Timeline. A standard case usually takes two to five working days. Very big or messy projects get a first look, and I tell you what to expect before charging for more.

What to send me

All the .mq5 and .mqh files the robot needs
What it should do, in a few sentences
What it does instead: any error text from the Experts or Journal tab helps a lot
The broker, account type and symbol where it fails, if you know them
Settings you use (a saved .set file is ideal)

Corrections and ownership

Seven days after delivery for genuine bugs in the repaired parts, up to three rounds. Wanting the robot to do something new is a new job.

The code written for you is yours once you have paid in full. I keep my general techniques but never your private rules, and I do not share or reuse what you send me.

Cases like yours

A robot that froze in fast markets

The terminal became slow whenever volatility rose. The cause was in how the program asked for indicator values, and the fix was structural.

An abandoned project

A developer stopped answering halfway. The code needed an honest look to decide between finishing it and starting clean.

Orders that vanished

Trades were sent but not always opened, and nothing checked the result. Adding proper checks and retries made the behaviour predictable.

Frequently asked questions

What kinds of fault do you fix?: Freezes, order and execution errors, memory growth, wrong lot or stop calculations, and logic that does not match what the robot is meant to do.
I only have the .ex5 file. Can you still help?: No. Without the readable source nothing can be fixed, so I need the .mq5 files.
Will the repair make it profitable?: No. A repair only makes the robot follow its own rules. Judging the rules themselves is outside this package.
What if it cannot be saved?: Then I tell you what I found and why, and you are not charged for a repair I could not carry out.
Can you add a feature while you are inside the code?: Not within this package. A new feature is a separate job, which keeps the repair easy to check.
Is my code kept private?: Yes. I do not share or reuse your code. Ask before sending it if you want a written confidentiality note.

Prices are in pounds sterling. Questions before you order? Send me a message. See the Terms of Service and the Refund Policy.