AckAlgo EA Builder guide: build an EA for MT5

AckAlgo EA Builder is a browser-based visual rule editor for MetaTrader 5 (MT5). Supported graphs generate MQL5 source files with the .mq5 extension. The website does not run backtests or connect to a brokerage account.

• Use a desktop computer and a modern browser to edit. Mobile supports templates, strategy settings, existing-node parameters, JSON import/export and preflight. Use desktop or tablet to add, connect and arrange graph nodes.
• Write down entry and exit rules, symbol, timeframe and sizing. If the rules are not yet precise, use a starter template to learn the workflow.
• MT5 and MetaEditor are separate applications needed for compilation and testing. Initially keep InpAllowTrading=false and InpAllowRealAccount=false.

Read proof states separately: Preflight passed means local structure checks passed; Generated means source exists; Compiled requires a compiler record for that exact file; Tested requires its MT5 report. None guarantees profitability.

This walkthrough uses MA Crossover on EURUSD / M15 to explain the controls. All values are educational examples, not investment recommendations. The endpoint is a file to verify, not a live trading session.

1. Open Builder → Builder settings → Export strategy JSON to back up any existing work, then close Settings.
2. Choose Templates → MA Crossover. If replacement confirmation appears, proceed only after backing up. You should see Fast EMA 20, Slow EMA 50, EMA Crossover, Market Entry, Risk and Protected Exit.
3. Set Strategy name to something recognizable, such as EMA practice 01. Check Broker symbol is EURUSD and Timeframe is M15. The symbol must match your broker at testing time.
4. Select Fast EMA 20 → Inspector: Period 20, MA method Exponential, Applied price Close. Select Slow EMA 50 and check Period 50 on the same timeframe.
5. Select EMA Crossover. Check Left operand is Fast EMA, Right operand is Slow EMA, Operator is Crosses above and bar shift is 1. With Signal set to Long & short, also inspect Reverse rule for short entries.
6. Select Market Entry. Check direction, maximum 1 open position and Limit to one trade per bar. Select Risk and inspect sizing, Stop loss, Take profit and Maximum spread, including their units.
7. Open Problems. Resolve every Error using Go to node and read each Warning. Press Preflight → Summary. Expect MQL5 source ready to download, with compiler/tester still Not run for this file.
8. Use Download for Strategy Tester / demo, then expand Technical details for Download tester manifest. Open MQL5 Source to inspect or Copy source. Close Preflight and Export strategy JSON again. Keep the three files together.
9. Continue with Compile and test in MT5 below. Any rule change requires a new export and fresh verification.

Choose a template by rule behavior. The downloads below are generated from the same data as Builder. Open them through Settings → Import strategy JSON and recheck Problems. Importing is not compilation.

• MA Crossover JSON ↓
• RSI Reversal JSON ↓
• Breakout JSON ↓
• Broker Session + ATR JSON ↓

• Add: choose an indicator from Indicators or search, for example RSI. Use Logic for Compare Values / Session Filter, Entry & Exit for actions, and Risk for sizing.
• Quick add: the + control on a node inserts a next-step block based on its kind. Always inspect the resulting connection and rule; it is not automatic strategy design.
• Connect: drag from output to input, or open Canvas outline, select a source, then Connect to …. Incompatible links are rejected. Adding a data input can change a condition operand.
• Remove a connection by selecting it and pressing Delete/Backspace, or using Remove in the outline. Delete a node in Inspector and use Undo if needed. Recheck Problems for broken references.
• Navigate: drag nodes to move them and empty canvas to pan. Use Zoom in / Zoom out / Fit strategy in view and the minimap. Shift supports multi-selection; Inspector edits one selected node at a time.
• Duplicate copies the selected node, not the whole strategy with its wiring. Inspect and connect the copy yourself.
• Recent contains recently used indicators; Favorites are explicit stars; My Blocks contains configured nodes saved with Save as Block. All are browser-local.
• Save as Block supports self-contained single nodes. If disabled, save the independent source node or Export strategy JSON for the entire graph. My Blocks retains up to 20 recent saved blocks.

Indicator → Condition carries values; Condition → Market Entry carries signals; Entry → Risk → Exit defines sizing and protection. Session gates time; ATR → Risk binds a stop-distance source. A drawable edge still needs semantic Preflight validation.

Select an indicator and set Timeframe, Output and its parameters using the catalog below. Changing Indicator resets parameters to the new defaults. Indicator line Shift is different from a condition bar shift: bar shift 1 is the latest closed candle; 0 is an unfinished candle and is not Builder's evaluation mode.

Multiple timeframes can be used within one symbol. Ensure MT5 has the required history. Values must be confirmed at signal time, not future data. Multiple connected conditions are not an unrestricted AND/OR expression editor: inspect the source and test the resulting behavior.

For example, Stop loss 0.5 percent means a distance of 0.5% of price, not a maximum account loss of 0.5% and not 0.5 pip. Actual risk can change with slippage, gaps and execution conditions.

Output constraints: nonzero Shift / Jaw shift / Teeth shift / Lips shift can trigger PLOT_SHIFT_ALIGNMENT_REQUIRED. Set them to 0 before exporting and review the changed rule. Ichimoku Tenkan/Kijun are supported, while Senkou A/B and Chikou are blocked pending alignment. Fractals require bar shift at least 3; last-non-empty lookup uses a 1–500 bar lookback as in Breakout. MT5 native does not mean every parameter/output combination is exportable.

Search a name or description, then expand an entry for parameters, defaults, options and outputs. Defaults are software starting values, not optimized market settings. MT5 native means source generation is supported; Catalog only means selectable for exploration but export-blocked.

No matches. Change the search or turn off the filter.

1. Open Problems: Errors block source and downloads. Warnings permit export but require review. Dismissing guidance does not fix an invalid rule.
2. Use Go to node and fix the relevant field or connection. If the cause is unclear, record the code and full message, and Export strategy JSON for review.
3. Preflight → Summary separates Export validation, MQL5 source, MetaEditor compiler, MT5 Strategy Tester and Source SHA-256. Keep these states aligned with the actual evidence.
4. MQL5 Source displays code and Copy source. If clipboard access fails, use Download .mq5. Download manifest preserves the full hash and strategy to bind evidence to the file.

1. In MT5, use File → Open Data Folder → MQL5 → Experts and place the .mq5 there. Open it in MetaEditor and press F7. This guide's delivery criterion is 0 errors / 0 warnings. Keep the log and .ex5.
2. Open Strategy Tester and select the EA compiled from that file. Set broker symbol, timeframe, date range, simulated deposit and tick model for the test. Record the configuration.
3. No input changes needed: in Strategy Tester the EA places simulated orders automatically (the Journal shows Strategy Tester detected). On live charts it stays in DRY RUN until InpAllowTrading=true; keep InpAllowRealAccount=false.
4. Inspect Journal, signal times, direction, lots, spread and SL/TP. Use visual mode to compare behavior against the rule. No trades can mean no qualifying signal or a filter rejection; do not disable every protection to force activity.
5. Save the tester report with date range, broker/symbol and modeled costs. After checking behavior, assess separate data periods and demo operation independently. Historical results do not guarantee future outcomes.

MT5 Setup in Preflight is guidance; it does not detect the application or execute a test for you. Without MT5, hand off source + manifest + strategy JSON and report compiler/tester as Not run.

Autosave uses this browser's local storage, not a user account. Switching browsers, clearing site data or using private mode can make previous work unavailable. Export strategy JSON before closing or moving computers.

• Import: Builder settings → Import strategy JSON → select file → structural validation → replacement confirmation → check name and Problems. Workspace schema 1.0 and supported strategy structures are accepted.
• Local save failed: the open work remains in memory. Export strategy JSON immediately, before refreshing. Check browser storage permissions and capacity.
• Local autosave is paused: export current work, and Download recovery bytes for old data if available. Resume local save writes storage again after confirmation; read what will be replaced first.
• Corrupt data or a newer schema: do not change a version number just to bypass validation. Preserve recovery bytes and share the file with its error message for diagnosis.
• Clear saved browser data removes saved Builder data. Back up first; this is not a general error-fixing step.

An AI can read this HTML guide or download Markdown and reference.json. Builder has no public execution API, broker API or server compilation service. Interaction requires a user-authorized browser, or a JSON file that the user imports.

1. Collect: rules, symbol/timeframe, direction, sizing/stops/spread and the current strategy file. Ask about missing details that change behavior; do not invent risk settings.
2. Start from a supported example JSON. Preserve schemaVersion, node IDs, edges and references while editing. Consult reference.json for parameter keys and allowed values.
3. In browser automation, use names and labels such as Builder settings, Canvas outline and Preflight; read the new state after edits. Avoid guessed coordinates or direct local storage writes.
4. Do not clear data, confirm replacements, transmit customer files elsewhere or enable real trading outside the owner's authorization.
5. Deliver: a rule summary, strategy JSON, source/manifest if generated, warnings/blockers and actual verification evidence. Mark unperformed compiler/tester steps Not run.

Help me build a strategy in AckAlgo EA Builder using this guide.
Entry rules: [specify]
Exit rules: [specify]
Broker symbol / timeframe: [specify]
Direction / position sizing / stop loss / take profit / spread: [specify with units]
Use supported tools only. Ask about missing requirements.
Back up strategy JSON before editing and review replacement confirmations.
Check Problems and Preflight; deliver strategy JSON, .mq5 and manifest when generated.
Report local validation, source generation, exact-file compilation and MT5 testing separately.
Do not claim unperformed compiler/backtest results. Do not enable real accounts or place real orders.

Available: templates, visual graphs, indicator parameters, closed-bar conditions, broker sessions, market entries, sizing, stop/target, JSON import/export, local preflight and MQL5 source export for supported graphs.

Not supported: Catalog only extensions, tolerance-based Equals, UTC session export, pending orders, multiple symbols per strategy, full mobile editing, custom indicator uploads, cloud sync, payments, web backtests, server compilation and broker connections. A visible UI option is not proof of export support.

For an unsupported requirement, hand off the intended rule, an example and the blocker for development assessment. Do not silently change the strategy's meaning just to pass Preflight.

Source generation supports trailing stops, break-even, opposite-signal exits and session-close exits when a Session node exists, plus averaging, martingale, basket limits and position count settings. Review each value in the source and test it in MT5 separately. Export support does not certify trading results.

The Strategy Tester / demo download sets InpAllowTrading=false. The explicit Download with live trading ON option sets it to true. Both variants set InpAllowRealAccount=false. Compile and test each exact file before use.

• Complete guide as Markdown ↓
• Machine-readable tool reference (JSON)
• AI navigation index (llms.txt)
• Sitemap
• MT5 Strategy Tester ↗
• MQL5 indicator reference ↗

Tool names, parameters and outputs are generated against the Builder revision used for this guide. Examples are educational, not backtest results or trading recommendations. If a later UI differs, preserve the file and exact message before requesting help.