Requirements
- Windows PC (recommended for MT5 stability)
- MetaTrader 5 installed + logged in to your broker
- XAUUSD symbol enabled/visible in MT5 (Market Watch)
- Stable internet connection (feed freshness matters)
- Lair = safer baseline thresholds
- Hunter = tighter filters (more selective)
- Rampage = regime-aware tuning (can be more aggressive)
- Scout never trades — it shows the decision packet
Install & launch
This section is intentionally simple: get the HUD open, confirm the feed is live, and run a scan. You’ll configure deeper settings in Setup.
- Open MT5 and log in
- Open Market Watch and ensure XAUUSD is visible
- Keep MT5 running (don’t close it)
- Open the HUD in your browser / installed app
- Click Sync HUD (or your equivalent refresh control)
- Confirm the HUD shows a fresh feed timestamp
Connect MT5
- MT5 must be running and logged in
- Only one MT5 instance per terminal is recommended (avoid duplicates)
- Goldzilla reads broker symbol specs for sizing (contract size / tick value / digits)
Pre-flight checklist (do this every time)
- Price updates in real time
- Feed freshness is seconds, not minutes
- No frequent gaps / flatlines
- Spread is within your cap
- Avoid session transitions/news spikes
- Wide spreads = trade veto (expected)
- Correct account selected in MT5
- Symbol specs detected correctly
- Risk/sizing sanity checks pass
First run (Trial-safe workflow)
Even if you bought Pro/Pro+, the safest first run is the same: Scout first, validate decisions, then enable execution later when everything looks clean.
- Set Mode to Lair
- Run Scout (scan-only)
- Open the decision packet / scan details
- Confirm: spread OK, feed fresh, sizing OK, risk checks OK
- Repeat across sessions (London / NY / Asia) to learn behavior
- System Health shows fresh price feed
- Spread is below your cap most of the time
- No recurring veto reasons (or they make sense)
- Decision packet fields are populated (no missing data)
Reading System Health
Should be seconds. Minutes-old data means scans/trades are unsafe.
If spread exceeds your cap, Goldzilla should refuse execution (by design).
Any non-zero error loop means fix the root cause before enabling automation.
Dropped ticks / anomalies should be rare. Frequent issues usually point to feed problems.
Common refusal reasons (and what to do)
Next steps
Connect MT5, confirm symbol specs, risk settings, and execution readiness.
Learn Lair/Hunter/Rampage and what each is meant to do.
Spread caps, stale feed, MT5 failures, refusals, and common errors.
