MQL4/MQL5 • PINE SCRIPT • CTRADER • EDITABLE SOURCE

Your MT4/MT5 Bot Defect Fixed and Proved.

If you own editable MT4 or MT5 source and can reproduce one defect, I repair it against three written tests. Editable source, compile evidence and handoff checks are included. New bots and cross-platform work remain available after the free brief identifies the right scope.

Arnold Holm

Independent developer in Germany

Public source

Inspect MQL5 CodeBase and GitHub work first

Clear acceptance

Agreed cases, editable source and test notes

Public source-backed proof

Inspect the work before hiring

These projects expose source, compiler-verifiable artefacts and concrete acceptance logic. They are engineering evidence, not trading-performance claims.

Editable source
Inspect the logic instead of trusting a claim.
Compile and test evidence
See what was checked and in which environment.
Three-case acceptance
Expected, must-not-happen and failure-path behaviour.
MQL5Public script #76039

MT5 EA Acceptance Harness

A non-trading MetaTrader 5 script that executes eight synthetic entry-state fixtures before timing, duplicate, cooldown and daily-lock rules are connected to broker behavior.

Original MQL5 source and ZIP published in MQL5 CodeBase item #76039

MQL5#75981

MT5 Cash Risk Probe

A read-only MetaTrader 5 script that estimates entry-to-stop cash loss in account currency, reserves explicit costs and floors volume to the broker grid without sending an order.

Original MQL5 source and ZIP published in MQL5 CodeBase item #75981

Pine Script v6Public Pine v6 source

Pine v6 Partial Exit State Inspector

A deterministic Pine Script diagnostic that makes initial-versus-remaining quantity semantics explicit for 50%, 33% and 25% partial exits and emits each tier once on a confirmed bar.

Original MPL-2.0 Pine v6 source published on GitHub

One primary paid first step

Free brief first. Then one tightly bounded repair.

The brief checks whether the 49 USD repair fits before you buy. Complete builds and migrations remain available when your written facts require them, but they do not compete with the smallest useful first result.

Primary First Step

R49

48-Hour MT4/MT5 Bot Fix & Proof Sprint

49 USD

One reproducible MQL4/MQL5 defect fixed and proved in 48 hours

  • One platform, one defect, source up to 500 lines
  • Three written acceptance cases
  • Editable source and compiled result
  • Change note and one scope-conformance revision

Included value stack

  • + Broker Compatibility Preflight
  • + Restart & Duplicate-Trade Regression Sheet
  • + 7-Day Handoff Verification Checklist
Check the fit with the free brief

Only when the brief selects a larger scope

E149 · 149 USD

MT4/MT5 Rules-to-Bot Build Sprint

One simple bot from deterministic rules

M179 · 179 USD

Cross-Platform Bot Parity Sprint

One bounded behaviour migrated between platforms

Bot Care is a post-delivery option after a successful first order, never a first purchase.

The three written acceptance cases pass, or the agreed delivery is not finished. Report a failing agreed case within 7 days using the original inputs and a reproducible result. I correct that agreed case without an added fee. New rules, another platform, changed broker conditions or a different defect are new scope. No direct checkout occurs on this site. I accept no more than two concurrent funded builds. The next start date is confirmed only after source review and funding; no artificial slots or countdowns are used.

From requirements to tested source code

The goal is not merely code that compiles, but behaviour that can be checked against the agreed specification.

01

Audit

I freeze entry, exit, risk, sessions, ownership and edge cases in writing.

02

Build

I implement the agreed solution with explicit state, guards and useful logging.

03

Verify

I verify compile checks, acceptance examples, parameter sanity and failure modes.

04

Deploy

You receive the agreed source, configuration, test notes and setup guide.

Before you hire

Clear answers before code starts

What do I need before the project starts?

The target platform, authorized editable source or complete rules, current and expected behaviour, and three acceptance cases: one expected case, one must-not-happen case and one restart or failure-path case.

Do I receive the source code?

Yes. Every applicable repair, build and migration includes editable source, a compiled result when the platform supports it, setup notes and a concise change record.

What happens if the first version does not pass?

The three written acceptance cases must pass or the delivery is not finished. One scope-conformance revision is included. This guarantees agreed software behaviour, not trading performance.

Which changes cost extra?

A change costs extra only when it adds rules, platforms, strategies, integrations or unrelated defects outside the frozen scope. I identify that before doing the added work.

Why can a backtest differ from live behaviour?

Data, spread, execution timing, symbol rules, account mode and restart state can differ. The scope freezes those assumptions so the agreed test evidence stays interpretable.

How are revisions kept finite?

Acceptance is tied to three written cases and explicit exclusions. A revision corrects the agreed behaviour; new features become a separate scope instead of an endless revision loop.

Free · private · no signup

Turn your bot problem into a brief that is easy to quote.

Answer a few structured questions. You leave with a copyable specification, three clear pass-or-fail cases and the smallest fitting next step.

About two minutes Your input stays in your browser

Your finished bot brief

Ready to copy, save or send

Clear scope
01

Platform and environment

MT4, MT5, Pine or cTrader plus the relevant timing context

02

Behaviour gap

What happens now and what the bot must do instead

03

Three acceptance cases

One positive, one must-not-happen and one boundary case

One useful result

A complete brief plus the smallest fitting Upwork route, or a clear explanation of what must be decided first.

Trading risk disclosure

Futures and forex trading contains substantial risk and is not for every investor. An investor could potentially lose all or more than the initial investment. Risk capital is money that can be lost without jeopardizing one's financial security or lifestyle. Only risk capital should be used for trading, and only those with sufficient risk capital should consider trading. Past performance is not necessarily indicative of future results.

Hypothetical performance disclosure

Hypothetical performance results have many inherent limitations. No representation is being made that any account will or is likely to achieve profits or losses similar to those shown. There are frequently sharp differences between hypothetical performance results and the actual results subsequently achieved by any particular trading program. Hypothetical results are generally prepared with the benefit of hindsight, do not involve financial risk, and cannot completely account for the impact of financial risk in actual trading. Market conditions, the ability to withstand losses, and adherence to a trading program can all materially affect actual results.

NinjaTrader trademark disclosure

NinjaTrader® is a registered trademark of NinjaTrader Group, LLC. No NinjaTrader company has any affiliation with the owner, developer, or provider of the products or services described herein, or any interest, ownership or otherwise, in any such product or service, or endorses, recommends or approves any such product or service.

Testimonials, when shown, may not represent the experience of other clients and are not a guarantee of future performance or success. Virtual-currency trading carries additional risks. See the CFTC customer advisories. Read the full financial risk disclaimer.