Setup checklist (in the right order)
Do these steps once. After that, day-to-day use is simple: keep MT5 running, keep the HUD open, and Scout before you execute.
Jump to
Requirements
You need
- Windows PC (recommended for MT5 stability)
- MetaTrader 5 installed + logged into your broker
- XAUUSD visible in Market Watch
- Stable internet (feed freshness matters)
Use a VPS if your home machine sleeps/restarts. MT5 must stay open for the feed + execution.
Before you trade, you must be able to answer:
- Is my feed fresh (seconds, not minutes)?
- Is my spread within my cap most of the time?
- Does sizing match my broker specs (no surprises)?
- Do I understand my mode + action (what will happen next)?
If not, start with Getting Started first.
MT5 terminal settings
Step-by-step (MT5)
- Open MT5 and log in to the correct account (demo/live).
- Open Market Watch and ensure XAUUSD is visible and updating.
- Open: Tools → Options → Expert Advisors
- Enable Allow algorithmic trading.
- If your configuration requires it, enable Allow DLL imports (some environments need it). Keep it off unless your setup demands it.
- Keep MT5 running. Avoid multiple MT5 terminals pointed at different brokers on the same machine.
Rule: if bid/ask doesn’t move in MT5, do not trust any scan. Fix MT5 first.
XAUUSD symbol & broker specs
Make sure you’re trading the right symbol
- Some brokers use suffixes (e.g., XAUUSDm, XAUUSD.)
- Your HUD should show the exact symbol name it’s reading
- Spread caps and sizing depend on the correct symbol
If your HUD is scanning one XAUUSD symbol but you execute on a different one, sizing and fills can break.
Broker specs you must verify (once)
- Digits / point size
- Contract size
- Min / max lot + lot step
- Stops level / freeze level (if your broker enforces them)
If you see “sizing sanity check failed”, this is the first place to look.
Risk & sizing guardrails
Set your risk profile (don’t skip)
- Choose a fixed risk amount or a conservative % of equity
- Ensure your lot sizing respects min/max lot + lot step
- Confirm your stop distance is realistic for XAUUSD volatility
Goldzilla is designed to refuse unsafe trades. If you try to risk too much for the stop distance, it should veto and tell you why.
Recommended first-run defaults
- Mode: Lair (safer baseline)
- Action: Scout (no execution)
- Start during a liquid session (London/NY overlap is usually cleaner)
- Keep the HUD open while testing
You can tighten or loosen later — but don’t “tune” before your feed and sizing are verified.
Spread caps & execution veto
This is the #1 reason trades don’t fire (by design)
If the live spread is above your configured cap, Goldzilla should block execution and show a clear veto reason (example: WIDE_SPREAD).
Good behavior
- Spread cap is enforced
- HUD shows current spread
- Decision packet records the veto reason
What you do
- Trade during more liquid times
- Avoid rollover/news spikes
- If spreads are always wide, consider broker conditions
Sessions (London / NY / Asia)
Why sessions matter
- Volatility + spread behavior changes by session
- Goldzilla can apply session-aware thresholds
- Session transitions can widen spreads and trigger vetoes
If you see frequent “refused trade” events around a session switch, that’s usually healthy behavior — not a bug.
How to validate sessions safely
- Run Scout in Lair during each session
- Compare spread + veto reasons
- Only enable execution after you understand your broker’s conditions
Read: Modes for when to use Lair vs Hunter vs Rampage.
Actions & tiers (Trial / Pro / Pro+)
Actions (what happens)
- Scout → scan only (no trade)
- Slay Gold → place one MT5 trade if filters pass
- Go Hunting → run the 15m auto loop (scan + execute at boundaries)
- Bank Gold → manage open trades (locks/tighten/retarget/exit)
- Go Home → stops the auto loop immediately
Tier gates (what’s allowed)
- Trial: Scout + Lair only (scan-only)
- Pro: adds Slay Gold + Hunter (manual execution)
- Pro+: adds Go Hunting + Bank Gold + Discord alerts + Rampage
If you select an action your tier can’t use, Goldzilla should block it and show a clear reason.
Verify setup (safe first run)
1) Confirm live feed
- Bid/ask updates
- Freshness in seconds
- No gap/flatline warnings
2) Run Scout (Lair)
- Check decision packet fields populate
- Check spread cap behavior
- Check risk/sizing sanity checks pass
3) Only then enable execution
- Pro: test Slay Gold once
- Pro+: enable Go Hunting only when stable
- Keep HUD visible during first sessions
If anything feels wrong: stop execution and fix the cause first.
Use Troubleshooting and include a System Health screenshot + veto reason when asking for help.
Ready to run your first safe scan?
Start with Scout in Lair. Confirm feed freshness, spread caps, and sizing sanity checks. Then (and only then) move to execution.