BYO-Bot Foundations: Build an MT5 EA | Free Academy

TopTradingEAs Free Academy · Course 9

BYO-Bot Foundations: From Idea to MT5 EA

Turn one written strategy into a documented build. Learn where local testing, export permissions, compilation and independent MT5 validation fit in the workflow.

Learning path: Build without coding · Prerequisites: MT5 workspace and the backtesting course · Free reading and practical tasks.

Choose the right completion route

Reading route: prepare the rule sheet and inspect the historical walkthroughs without purchasing software. Free Edition route: build and test locally, then export an eligible Single Position strategy using standard exits with Loss Recovery off. Premium-export route: use an active monthly licence for Grid Basket Recovery, Advanced Adaptive Exit or Single Position Loss Recovery exports. Legacy Gold Matrix portfolio exports are also paid. Compile the exported source and investigate its behaviour in MT5. Mark only tasks you actually complete.

This course uses existing versioned walkthroughs and the current product information. It is not certification that every current release or generated strategy has been independently tested. Check the installed version and current manual before following interface-specific steps. Shared article previous/next links follow Course 1; use this page for the specialist task order.

Broker context before independent testing

MT5 testing needs the intended broker’s symbol and account context. Read the broker comparison and verify regional account terms directly. FxPro Nano eligibility and denomination do not establish the contract exposure; for example, 1,000 USC denotes USD 10, while position risk still depends on the contract and trade size. Do not assume Tickmill uses the same account structure.

These links are affiliate links and we may receive compensation. No broker or account type guarantees strategy results.

Your build-to-validation workflow

  1. Write the strategy before opening the builder
  2. Prepare the package and identify the version
  3. Build one configuration and preserve it
  4. Run and interpret the builder test
  5. Identify what you are exporting
  6. Compile, then check actual behaviour
  7. Create an independent MT5 record and demo plan

1. Write the strategy before opening the builder

Save: A rule sheet you can check against the software.

Start with the complete no-code EA walkthrough and the versioned BYO-Bot review. Write the entry condition, signal timeframe, confirmation conditions, position-sizing basis, maximum intended exposure, exit rules and protection actions. Use “unknown” for details you cannot establish.

Choose one manageable example: Alligator, Candle Time Run or Solaris. Treat each as a historical walkthrough, not a recommended profitable setup. Do not merge settings from different versions or examples without documenting a new configuration.

Practice: explain one entry and one exit in plain language. If the rule depends on a completed candle, a session or an indicator timeframe, make that dependency explicit.

Previous task · Build record · Next task

2. Prepare the package and identify the version

Save: A known environment and an honest list of licence limits.

Use the current product page and the manual linked there to obtain the complete authorised package. Record its version, Windows environment and data-pack identity. Existing articles show v3.4.2; if your installed release differs, compare the interface and instructions before following a screen-specific step.

The documented package keeps the application with its StarterData folder. Check the current instructions for installing data and confirming it is ready. A missing data file is a setup issue to investigate, not a reason to copy a favourable output from a tutorial.

Practice: record your package and data versions, access mode and selected configuration. Free Edition exports your actual successfully tested Single Position strategy using standard exits with Loss Recovery off. For premium configurations, record the feature requiring a monthly licence rather than expecting a fixed sample file.

Previous task · Build record · Next task

3. Build one configuration and preserve it

Save: A saved project that corresponds to the written rules.

Follow your chosen walkthrough. Review the template before changing an entry module. Record each selected signal, timeframe, confirmation, sizing, trade-management, exit and protection setting. A template can contain important defaults beyond the visible signal name.

Save a dated project. Change one item at a time and keep a short reason for each change. Do not add recovery or basket management merely to improve a historical headline; explain how it changes aggregate exposure first. The separate lesson individual stops versus basket exits helps frame that question.

Practice: reopen the saved project and compare it with your rule sheet. If the interface offers a control not covered by the walkthrough, record it separately rather than assuming its action.

Previous task · Build record · Next task

4. Run and interpret the builder test

Save: A local research output tied to the current configuration.

Run the local test for the configuration you actually saved. Preserve the period, data identity, settings and output, including failed tests and losing sequences. After changing settings, run a fresh test rather than treating an earlier output as evidence for the new configuration.

The existing review describes local CSV history without historical spread and synthetic minute-count volume. Keep these limitations explicit. Local builder output is useful for investigating the configured idea, but it is not an MT5 broker-data backtest and does not establish future performance.

Practice: record what the builder result helps you inspect and at least two differences you must check in MT5. Do not require a profitable result to count the observation as useful research.

Previous task · Build record · Next task

5. Identify what you are exporting

Save: A correctly labelled source and settings pair, or a documented premium-export restriction.

Check the current release’s export instructions and licence status. The documented workflow ties custom export to a successfully tested current configuration. Record the bot name, version, identifier and export filenames. Keep the MQ5 source and its matching SET configuration together.

Free Edition exports the selected eligible strategy, not a fixed Gold Matrix sample. Confirm Single Position management, standard exits and Loss Recovery off, then retest after any change. Grid Basket Recovery, Advanced Adaptive Exit and Single Position Loss Recovery require an active monthly licence for export; the legacy Gold Matrix portfolio is also paid. Building and local testing remain available free, including premium combinations.

Practice: write “Free Edition Single Position export” or “premium export” in the run record. Record the management mode, exit selection, recovery setting, successful test and matching MQ5/SET files. If export is blocked, identify the actual restriction. Do not share licence keys or redistribute a package without permission.

Previous task · Build record · Next task

6. Compile, then check actual behaviour

Save: A compiler result separated from a trading-behaviour check.

Follow the export and MetaEditor walkthrough. Open the authorised MQ5 file in MetaEditor 5, compile it and retain the compiler output. Resolve errors using the exact release instructions or support; changing unrelated strategy rules would create a new experiment.

A compiled EX5 establishes that the source passed compilation. It does not establish that the EA uses the intended rule, places trades on the chosen data or behaves identically to the builder. Check the relevant SET inputs and initialization log before interpreting a test result.

Practice: identify one observed entry and exit in a controlled MT5 historical test and compare them with the written rules. If no trades appear, use the MT5 troubleshooting checklist. Document unresolved behaviour rather than declaring the build validated.

Previous task · Build record · Next task

7. Create an independent MT5 record and demo plan

Save: An evidence pack with its limitations and next action.

Work through Course 5: Your First Reproducible MT5 Backtest for the exported configuration. Preserve the broker symbol, modelling mode, costs, dates, deposit currency and sizing basis. Record differences from the builder output rather than forcing the two results to agree.

Choose validation boundaries before tuning against them. Keep a demo observation log with the exact build/preset, open exposure, closed outcomes, cash flows, errors and configuration changes. Decide what evidence is missing before considering any live use.

Practice: write a handoff note explaining what was built, what was exported, what ran in MT5, what remains unknown and which next observation could resolve it.

Previous task · Build record · Next task

Copy this build record

CheckpointWhat to record
Rule sheetEntry, signal timeframe, confirmations, sizing, exposure, exits and protection
EnvironmentBYO-Bot build, data pack, licence route, MT5 build and broker symbol
ProjectTemplate or blank setup, dated project filename, each changed input
Local resultTest period, configuration identity, output and data limitations
ExportFree Edition or premium export, management/exit/recovery settings, MQ5/SET filenames, version and identifier
MT5 checkCompiler output, initialization log, observed entry/exit, report and discrepancies
ValidationUntouched interval if available, demo plan, changes, cash flows and unresolved questions

Keep the files and notes in your own folder. No progress account or paid course enrolment is required.

Completion check

  • I can explain the selected entry, exit and exposure rules without relying on a bot name.
  • I recorded the software/data versions and any undocumented behaviour.
  • I reopened a saved configuration or clearly marked this as a reading-only exercise.
  • I separated local test output from MT5 broker-data evidence.
  • I labelled the exported strategy and its free or premium feature settings accurately.
  • I distinguished compilation from observed trading behaviour.
  • I preserved unresolved differences and a validation/demo plan.

The export route requires its actual export and MT5 tasks, whether you use an eligible Free Edition strategy or premium features. Reading or running a local test alone does not establish that a strategy has been exported or reproduced in MT5.

Further walkthroughs and next tasks

Awesome Oscillator walkthrough · Bears Power walkthrough · Check indicator repainting

The dedicated entry-rule, exit-design and generator courses remain planned. Start with one documented manual build before treating generated candidates as a new research project. The current product materials include a generator tutorial; it is optional further viewing, not evidence that a candidate is ready for live trading.

Previous practical course: reproducible backtesting · Build-without-coding learning path · Trading Tools, including the MT5-to-cTrader copier · Explore Expert Advisors

View more forward trading results

Sources and version notes

Use the linked full walkthrough, versioned review and current BYO-Bot product page for package and manual information. This course’s access guidance reflects v3.9.28: eligible Single Position exports are free; premium export features require a monthly licence. Older walkthroughs may show retired pricing or sample-export rules. This course does not promise to resolve release-specific errors.

Trading involves risk. Local tests, historical reports, generated candidates and successful compilation do not guarantee future returns. Grid or recovery settings can increase exposure. Use independent historical and demo research before considering live deployment.