neverwolf
This EA is a utility that validates whether a user-selected timeframe input parameter falls within a predefined list of allowed timeframes. If the selected timeframe is invalid, the EA fails initialization and does not proceed. It contains no trading logic whatsoever.
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 has no trading strategy at all; it is purely a timeframe validation utility. Its core logic calls the checkTimeframePeriods function during OnInit to verify whether the user-provided Period_TF parameter belongs to a predefined list of allowed timeframes (M5, M10, M15, M20, M30, H1, H2, H3, H4, H6, H8, H12, D1, W1, MN1). If validation fails, the EA returns INIT_FAILED and attempts to call ExpertRemove, but ExpertRemove is placed after the return statement, making it unreachable dead code. Both OnTick and OnDeinit functions are empty shells with no position management, money management, or entry/exit logic. The EA appears to be designed as a template or component for other EAs to ensure timeframe parameter validity before proceeding with actual trading logic.
Strengths
- Provides a timeframe validation mechanism to prevent users from selecting invalid timeframe parameters
- The allowed timeframe list covers a comprehensive range from M5 to MN1
- Simple and clear code structure, easy to integrate into other EAs as an input validation module
Weaknesses
- ExpertRemove() call is placed after the return statement, making it dead code that never executes
- Lacks meaningful error messages, so users cannot know which specific parameter failed validation
- OnTick and OnDeinit are empty functions; the EA has no actual functionality beyond validation
Possible improvements
- Move ExpertRemove() before the return statement to ensure proper EA removal on init failure, and add an Alert message to inform the user of the invalid timeframe
- Use INIT_PARAMETERS_INCORRECT instead of INIT_FAILED to provide more precise differentiation of initialization failure reasons
Risk assessment
Overall risk: Safe
- Dead ExpertRemove code may leave the EA resident instead of auto-removing after init failure
- Lack of user notification on validation failure may cause confusion
Evaluation scores
Parameters
| Parameter | Default | Description |
|---|---|---|
Period_TF | PERIOD_M5 | Indicator timeframe for validation |
Similar Utility EAs
Backtests are historical simulations and do not guarantee future results. Not financial advice.