MultiOrdersExpert
This EA is a thin wrapper that includes multi.mq5 and delegates all event handlers (OnInit, OnDeinit, OnTick, OnChartEvent) to the included file. It contains no trading logic of its own and acts purely as an entry point for the multi.mq5 module, which likely provides a multi-order management panel or utility interface.
Open the interactive view (equity curve, symbol switch)Key facts
Backtest results (H1, about 1 year)
Not backtested yet — this EA could not be converted automatically.
Strategy analysis
This EA contains no trading strategy of its own; it is purely a delegation layer that forwards all core functionality to the multi.mq5 file. Based on the filename 'MultiOrdersExpert' and the included 'multi.mq5', this is most likely a multi-order management utility for batch placing, modifying, or closing multiple orders. Since all event handlers directly call identically-named functions, this is a simple modular design pattern separating logic from the entry point. Entry and exit conditions are entirely dependent on the multi.mq5 implementation and cannot be determined from this file alone. Position sizing and money management are likewise decided by the referenced module. A critical architectural risk is recursive calling — if multi.mq5 also has identically-named functions that call themselves, it will cause infinite recursion and a stack overflow crash.
Strengths
- Modular design separating entry point from core logic
- Clean and minimal code that is easy to understand and maintain
- Supports full MQL5 event handling (Tick, ChartEvent, etc.)
- Logic reuse enabled through the include mechanism
Weaknesses
- Critical recursive call risk: identically-named functions OnInit/OnDeinit/OnTick/OnChartEvent will conflict with themselves after inclusion, causing infinite recursion and stack overflow
- Contains no proprietary logic, entirely dependent on the external multi.mq5 file
- No input parameters defined, extremely low flexibility
- Missing error handling and return value checks
- Cannot run independently; compilation fails if multi.mq5 is absent
Possible improvements
- Rename delegation functions to avoid recursive conflicts with identically-named functions in multi.mq5, e.g. using namespaces or prefixes
- Add input parameters to configure the behavior of the multi.mq5 module for greater flexibility
- Add existence checks and error handling for the multi.mq5 dependency
Risk assessment
Overall risk: High risk
- Recursive function call risk: after #include, functions like OnInit calling themselves form infinite recursion leading to EA crash
- Complete dependency on external multi.mq5 file; any issue in that file disables all functionality
- No visible risk control logic; an order management tool without safeguards could cause batch misoperations
Evaluation scores
Parameters
| Parameter | Default | Description |
|---|---|---|
N/A (no parameters defined) | N/A | No input parameters defined; all parameters from multi.mq5 |
Similar Utility EAs
Backtests are historical simulations and do not guarantee future results. Not financial advice.