Quick Help & Setup

Please include:

Most issues are resolved by checking license tier (must be ELITE) and matching indicator names exactly.

1) What Trading Smarter Is
What exactly is the Suite?

A two-part system: **Indicator** = logic + visuals + alerts + outputs • Analyzes market conditions and writes signals via indicator buffers and (optionally) GlobalVariables **EA** = execution + management • Reads the indicator outputs (buffers/GlobalVariables) and opens/manages trades based on your rules

No. The indicator does not execute orders.
No. This EA depends on loading the indicator through iCustom() and reading valid buffers.
No. It’s rule-based automation and trade management. Losses are possible.
2) Licensing & Tiers
What tier is required for automation?

**ELITE** The EA will not open new trades unless the license is valid and ELITE. The indicator will clear/disable automation outputs unless the tier is ELITE.

Usually no, because the indicator won’t produce usable automation outputs.
Even if the EA loosens its own guard, the indicator is typically still FREE/BASIC by default, which means the EA usually still receives no valid automation signals.
No. It’s rule-based automation and trade management. Losses are possible.
Controlled by InpLicCheckMinutes (commonly 10 minutes by default).
Yes—both run their own validation and tier logic.
3) Installation
Where do I put the files?

**Indicator** .mq5/.ex5 → MQL5\Indicators\ **EA** .mq5/.ex5 → MQL5\Experts\

• Restart MT5 or Navigator → Refresh • If you have .mq5: open MetaEditor → Compile → confirm an .ex5 is created with no errors
Most common cause: name mismatch (see next section).
4) Indicator Name Mismatch
What should I set in EA InpIndicatorName?
It must match the compiled indicator file name (the .ex5 name), without .ex5.
Only if the compiled .ex5 has the exact same name and the EA’s InpIndicatorName matches it exactly.
Pick ONE:
**Option A (recommended):** set EA InpIndicatorName to your real compiled indicator name
**Option B:** rename the indicator source/file so the compiled .ex5 matches what the EA expects
5) Backend Mode vs HUD Mode
Why doesn't the indicator show HUD/buttons when the EA runs?
Because the EA loads the indicator in backend mode by passing P1 = 1.0, mapped to the indicator’s InpBackendMode: InpBackendMode = 1 → backend (no HUD/buttons)
Attach the indicator manually to the chart and set: InpBackendMode = 0.0 → full visuals/buttons
Yes:
• EA runs its own backend instance for signals
• You attach a separate indicator instance for visuals/buttons
6) Buffer Map (EA ↔ Indicator)
Which indicator buffers does the EA read?
Hardcoded buffer indexes:
• #2 = Early BOS signal
• #3 = Retest Hit signal
• #4 = Immediate / Breakout signal (life-aware)
• #7 = OB Confirm signal
No. Those are diagnostic only (probing/logging). Actual reading is fixed to 2/3/4/7.
EA reads signals differently:
• Buffers 2/3/7 → live-bar only (current bar)
• Buffer 4 → life-aware (EA scans back up to InpSignalLifeBars)
By default, the EA expects:
• non-zero
• not EMPTY_VALUE
• typically +1 buy / -1 sell
 
You can change interpretation via: •InpNonEmptyAsTrue
• InpBuyMatchValue
• InpSellMatchValue
7) Timeframes & Trading Symbol
What timeframe does the EA read signals from?
InpSignalTF
• PERIOD_CURRENT = the chart timeframe where the EA is attached
Set InpSignalTF = PERIOD_H1.
No. This EA trades only the chart symbol (_Symbol). Use multiple charts for multiple symbols.
8) Signal Life & Timing
What does InpSignalLifeBars do?
It controls how far back the EA will accept buffer #4 (Immediate/Breakout). Example: InpSignalLifeBars = 3 → signal stays valid up to 3 bars old.
Common causes:
• Buffer #4 is life-aware (entry can happen within the life window)
• InpTradeOnSameBar = false blocks same-bar entries (new-bar gate)
• Spread block, max positions, cooldown, license guard delayed entry
• true → can enter as soon as the signal appears
• false → enters only when the “fresh bar” gate allows it
9) Manual Buttons (BUY / SELL / CLOSE ALL)
Do the Indicator buttons place trades directly?
No. Buttons write GlobalVariables commands. The EA reads and executes them.
Bridge keys include: • MTD / MTS = manual Buy/Sell request (with timestamp) • MCA = manual Close-All request • AT = allow-trading toggle (enables/disables entries)
• true → can enter as soon as the signal appears
• false → enters only when the “fresh bar” gate allows it
10) Channel / Instance / TradeId
Do the Indicator buttons place trades directly?
A namespace so the EA and indicator communicate only with each other (via GlobalVariables).
Lets you run multiple setups on the same symbol without collisions.
Extra separation for multiple EAs using the same channel/instance; affects magic/comment tagging and instance-lock behavior.
Make sure both tools match:
• InpChannelId
• InpInstanceId
11) Legacy Compatibility
What is legacy magic GV compatibility?
Older builds used magic-based GlobalVariable keys. New builds use channel-based keys.
Indicator: InpGVCompatWriteLegacyMagicKeys + InpStrategyMagic EA:
InpGVCompatReadLegacyMagicKeys + InpLegacyStrategyMagic
Only when mixing old/new builds together. If both files are current vNext, channel-based keys are typically enough.
12) EA Entry Rules
What can block entries even if a signal exists?
Common blockers:
• License guard (not valid / not ELITE)
• Allow-trading toggle off (AT)
• Spread too high: InpBlockEntryHighSpread + InpEntryMaxSpreadPips
• Max positions: InpMaxOpenPositions
• Cooldown: InpCooldownBarsAfterEntry
• Max entries per signal event: InpMaxEntriesPerSignalEvent
• New-bar gate when InpTradeOnSameBar = false
MT5 Experts tab. Look for tags:
• [GUARD] license/tier blocks
• [SKIP] entry blocked (reason included)
• [DECIDE] decision flow
• [SIG-DBG] signal/buffer debug
13) Risk & Sizing
Does the EA use risk % position sizing?
No. This build uses fixed lot per order: InpFixedLot (normalized to broker min/max/step)
Multi-TP opens multiple orders. Total exposure ≈ InpFixedLot × number_of_orders.
Auto-detected: • 5-digit / 3-digit symbols → 10 × _Point • Otherwise → _Point • BTC-style symbols default pip size to 1.0 • Override with InpPipSizeOverride when needed
14) SL/TP Logic
What SL types exist?
InpSLType supports:
• Pips
• ATR
• Percent
• BY_MAX (max of pips/ATR/%)
InpTPType supports:
• Pips
• ATR
• Percent
• BY_MAX
The TP ladder uses InpTP1_Pips … InpTP20_Pips and InpTPx_Trades, but final distances come from internal distance logic (depends on InpTPType).
If InpTPType is ATR / Percent / BY_MAX, per-level pip inputs can be overridden by ATR/% logic.
 
If you want unique per-level distances, set:
InpTPType = SLTP_PIPS
The EA enforces minimum distances: • Broker stop level / freeze rules • Optional spread floors: InpSLvsSpread, InpTPvsSpread You can cap expansion with: InpMaxFloorPips
15) Exit Mode: Multi-TP vs Partial-TP
What is Multi-TP mode?
InpSLType supports:
• Pips
• ATR
• Percent
• BY_MAX (max of pips/ATR/%)
InpTPType supports:
• Pips
• ATR
• Percent
• BY_MAX
The TP ladder uses InpTP1_Pips … InpTP20_Pips and InpTPx_Trades, but final distances come from internal distance logic (depends on InpTPType).
If InpTPType is ATR / Percent / BY_MAX, per-level pip inputs can be overridden by ATR/% logic.
 
If you want unique per-level distances, set:
InpTPType = SLTP_PIPS
16) Break-Even, Lock Profit, Trailing
Break-even supported?
Yes:
• InpBE_Enable
• InpBE_TriggerPips
• InpBE_Offset
Yes:
• InpLock_Enable
• InpLock_TriggerPips
• InpLock_OffsetPips
Yes:
• InpTrail_Enable
• InpGTrail_Start
• InpGTrail_Distance
• InpGTrail_Step
Check:
• InpBlockExitHighSpread (management pauses when spread is wide)
• broker freeze/stop rules
• market has no ticks (quiet/closed)
• triggers don’t match the instrument’s pip sizing (use InpPipSizeOverride if needed)
17) Spread Controls
Block entries when spread is high
• InpBlockEntryHighSpread = true
• set InpEntryMaxSpreadPips
• InpBlockExitHighSpread = true
• set InpExitMaxSpreadPips
 
Note: blocking exit management can pause BE/lock/trailing and partial closes until spread normalizes.
 
18) Unified Early Alert
What is it?
The indicator can write an early directional preference via GlobalVariables:
• EAD = direction
• EATS = timestamp
Yes, if enabled:
EA InpUseUnifiedEarlyAlert = true
As a fallback only:
If no final buffer signal is present (sig == 0), it may enter using the early alert direction if still fresh.
19) Indicator Alerts
I saw a setup but got no alert — why?
Common input causes:
• InpNotifyOnlyOnEntryPass = true (alerts only when entry gates pass)
• early alert filters required (VWAP/RSI side, etc.)
• cooldown active (InpEarlyAlert_CooldownMin/Sec)
• retest scheduling gated (InpRetestOnlyOnEntryPass = true)
InpAuthorizeAlertsOnRetestHit = true can loosen internal authorization so retest-hit alerts can trigger even when earlier gating was strict.
20) Order Blocks (OB) & OB Confirm
Does the EA trade OB Confirm?
Optional:
EA InpAllowOBConfirm = true (often default is false)
Indicator buffer #7.
21) Performance & Stability
MT5 lagging / indicator heavy — what should I disable first?
Reduce object-heavy and scan-heavy features, starting with:
• large scan ranges
• multi-timeframe overlays
• extra zone drawings / dense chart objects
 
Tip: keep the EA’s indicator instance in backend mode and run a separate visual instance only where needed.
Remove and re-add the indicator, or delete chart objects with a common prefix (your MTZ object naming). Tier changes can also trigger refresh/cleanup behavior.
22) Instance Lock
Why does the EA refuse to start with an instance lock message?
InpEnableInstanceLock = true prevents duplicates on the same symbol/channel/instance.
• Ensure only one EA instance is running for that symbol/channel/instance
• Wait InpInstanceLockTimeoutSec
• If stuck: remove duplicates and restart MT5
23) Backtesting
Can I backtest this EA?
Yes, with caveats:
• licensing WebRequest may fail in Strategy Tester unless allowed
• spreads/ticks are modeled differently than live
• live-bar behaviors (especially buffers read “current bar”) can differ in simulation
Spread variability, slippage, tick density, execution speed, and live-bar evaluation differences.
24) Troubleshooting
"EA attached, but zero trades forever."
Yes, with caveats:
• licensing WebRequest may fail in Strategy Tester unless allowed
• spreads/ticks are modeled differently than live
• live-bar behaviors (especially buffers read “current bar”) can differ in simulation
Check in this order:
1. License valid + ELITE in EA and indicator
2. WebRequest allowed for licensing domain
3. InpIndicatorName matches the compiled indicator .ex5
4. Signals actually appear in buffers 2/3/4/7 (enable InpDebugSignals = true)
5. Spread blocks, max positions, cooldown, allow-trading toggle (AT)
Early BOS/Retest are live-bar only and can be missed if they flash quickly. Options:
• keep InpTradeOnSameBar = true
• consider enabling Unified Early Alert fallback if that fits your workflow
Usually broker stop/freeze rules blocked placement or modification. Check Experts log retcodes for the exact rejection.
Check:
• pip sizing (override if needed)
• trigger distance relative to the instrument’s movement
• exit management not blocked by InpBlockExitHighSpread
25) Logging & Support
What logs should I send?
• MT5 Experts lines around the issue
• MT5 Journal lines around the issue
• screenshots of EA Inputs + Indicator Inputs
• InpDebugSignals = true (shows [SIG-DBG] + decision)
• InpLogLevel (increase if available)
• InpLogSignalProbe = true (extra buffer probing)
• [GUARD] New trades disabled… → licensing/tier \
• [SKIP] … → exact block reason
• [SIG-DBG] … → what the EA actually read from buffers