Ecfx Xau Warden R2 cTrader Manual

Chapter 01

Understand the portfolio

Three engines on one account

Engine A uses price-level breakout profiles with pending orders and strategy-specific exits. Engine B combines a session range breakout and a scheduled entry module; its additional session C module is disabled by default. Engine C combines the Pattern12 portfolio, a trend complement and structure strategies. These are configurable software components, not guaranteed sources of diversification.

Ownership and shared risk

Distinct magic-number ranges identify the positions and orders owned by each engine. All enabled engines still share account balance, equity, available margin and market exposure. An unrelated trade can change the equity used by a guard even when that guard closes only Warden positions. Test on an isolated demo account first.

Choose the right edition

Use only the package and preset for your platform and software version. MT5 .set files and cTrader parameter presets are not interchangeable. A similar product name, chart or historical result does not establish equal execution or performance.

What this manual covers

This manual explains installation, broker checks, sizing and guards, backtesting, daily operation and troubleshooting. The reference appendix lists every exposed input and its factory default in this documented build. Saved presets, marketplace updates and your current settings can differ from those defaults.

Chapter 02

Install and configure cTrader

Version and package

This edition documents Ecfx Xau Warden R2 for cTrader build 2.010, project version 2.0.10. Use the corresponding .algo package or official Store installation for that build. The manual does not imply that a local package is already published in cTrader Store. Compare the version in startup logs and the panel before using its reference defaults.

Install and create an instance

Open the authorised .algo package in cTrader or install the purchased item using the Store workflow. In cTrader’s algo/Automate workspace, find Ecfx Xau Warden R2 and add an instance on the intended broker’s Gold symbol and H1 starting layout. Use a hedged demo account. Review parameters, save an edition-specific preset and run a short visual backtest before starting a demo instance.

Account and permissions

The declared cBot access rights are None. The documented engine C requires a hedged account, including backtesting. Execution mode selects tester only, demo only or demo/real plus tester. Do not interpret access-rights None as trading disabled; the cBot can place trades when account mode and runtime permissions allow them.

Map the strategy clock

The cBot runs in UTC but maps MT5-style strategy times using MT5 broker UTC offset (minutes). This fixed offset does not automatically change with daylight saving. A +120 value maps UTC to a strategy clock two hours ahead. Compare session order times to the target broker convention, and update/retest the offset for seasonal periods where required.

Map distances and volume

MT5 point size (0 = symbol digits) controls the strategy point: zero uses 10 to the power of minus symbol digits. MT5 stops level and freeze level retain strategy distance checks. These do not replace native broker execution restrictions. Engine C pip size is a separate positive setting in this build; do not assume it equals cTrader’s native pip. Strategy lots are converted through Symbol.QuantityToVolumeInUnits and normalized to broker volume rules.

Shared portfolio breaker

Shared equity breaker defaults true, Peak equity drawdown trigger (%) defaults 20, and New order size multiplier defaults 0.5. The multiplier reduces new-order volume and rounds down to valid units; scaled volume below the minimum is rejected. The breaker observes whole-account equity against the peak since this run started. On breach it latches for the remainder of the run, attempts to cancel owned Warden pending orders and close owned positions on the instance symbol, and retries failures. Execution can overshoot the trigger.

Restart and news limitations

Restarting starts a new run-level breaker reference; it does not restore the previous shared breaker latch as a permanent account limit. Investigate any breach before restarting. MQL5’s calendar is unavailable in this port: exact NFP broker timestamps take priority, otherwise an approximate first-Friday fallback is used. Do not assume cTrader and MT5 news blocking are identical.

Run locally until deployment is validated

Keep the tested instance on the intended desktop/VPS environment while validating logs, persistence, timers and execution. Do not assume a cloud instance has identical state, API support or timing merely because the .algo installs. Verify cloud availability and behaviour for the actual marketplace build before relying on it.

Chapter 03

Broker checks before the first run

Use the intended Gold symbol

Select the broker’s actual Gold instrument rather than typing a symbol guessed from another broker. Examples can include XAUUSD, XAUUSDp or GOLD, but availability and contract specifications vary. This is the Gold Warden portfolio; it is not the Warden crypto basket.

Inspect the contract

Record digits, point size, tick size, tick value, lot or contract size, minimum volume, maximum volume, volume step, leverage, margin requirements and trading hours. Record spread, commission and swap. A pip, point and price unit are different concepts. Do not copy distance settings between brokers without checking their units.

Use a hedging account for portfolio separation

A hedging account allows separate positions on one symbol. A netting account combines same-symbol exposure and can change strategy ownership and exits. Use a hedging demo account to evaluate the intended portfolio behaviour. Platform-specific startup handling is explained later.

Start with H1 as a working layout

An H1 chart is a practical starting layout for the multi-timeframe Gold portfolio. Several strategies load their own timeframes internally. The visible chart timeframe does not convert every strategy into H1. Load sufficient historical data for the enabled strategies before assessing missing trades.

Chapter 04

Engine A settings and behaviour

Strategy selection

TradeFrequency offers conservative through extreme choices, automatic selection and manual selection. Manual mode uses the RunStrat1 through RunStrat9 switches. Do not assume all nine switches determine the active set in every frequency mode. Changing the selection changes the portfolio and its sizing assumptions.

Position size

Risk selects StartLots, per-strategy risk or the maximum-total-drawdown sizing model. StartLots is the fixed starting-lot input. MaxRiskPerStrategy_ and the per-strategy weights affect risk-based sizing. MaxAllowedDD is a sizing reference, not a promised maximum account loss. ManualBalance, UseEquity and OnlyUp change the sizing basis; OnlyUp can retain a prior higher basis after losses.

Drawdown enforcement is separate

EnforceMaxTotalDrawdownGuard is false by default in this documented build. Entering a MaxAllowedDD value alone does not enable its total drawdown stop. PropFirmMaxDailyDD defaults to 0, which disables that daily threshold. TotalDDUsesHighWatermark selects a peak-equity reference when enabled; otherwise the total reference is the initial balance. ClosePositionsAtRiskLock affects the response to a lock.

Pending orders and protective exits

The strategy groups define level timeframes, pivot confirmation, entry offsets, stops, targets, order expiry, position caps and rearm delays. Trailing and break-even parameters can move exits. Virtual_expiration requires the bot to remain running to enforce virtual expiry. If stops are set after entry, there can be a period before protection is attached. Changing offsets, target or adverse-target controls changes the trading strategy.

News and Friday windows

NFP filtering, exact NFP dates, time offsets and pre/post-event windows affect eligibility and optional closures. FridayStopHour 25 disables the Friday entry-stop window. Enabled filters do not provide a complete calendar of all economic events. Confirm the actual broker-time schedule in logs and a visual test.

Chapter 05

Engine B sessions and position sizing

Session modules are separate from engine letters

PG_InpEnableA and PG_InpEnableB are session modules inside Engine B; they are not the top-level Engine A and Engine B switches. PG_InpEnableC is the extra multi-day breakout/momentum module and defaults to false. The top-level ComboEnablePropGold controls the whole Engine B.

Three sizing modes

PG_InpRiskType is 0 for automatic sizing, 1 for risk percent and 2 for fixed lots. The risk-percent mode requires a positive PG_InpRiskPercent; fixed-lot mode requires positive PG_InpLots. PG_InpRiskLevel is 0 low, 1 medium and 2 high. PG_InpBaseMoneyMode is 0 initial funds, 1 balance and 2 equity; PG_InpCustomBalance can provide a custom basis. Defaults are software defaults, not a recommendation for your account.

Read session times as minutes after midnight

Engine B session inputs use broker-server minutes. For example, 120 means 02:00, 420 means 07:00 and 1080 means 18:00 in the strategy clock. PG_InpSessionShiftMinutes adjusts the schedule. Verify the broker timezone and seasonal offset before copying session settings.

Spread and equity filters

PG_InpSpreadFilter defaults false. The 100-point maximum becomes a spread gate only when that filter is enabled. PG_InpCloseTradesOnEquityDrawdown also defaults false; its 4% threshold does not activate it by itself. PG_InpActivateTester controls additional target/loss test behaviour. Account-wide closing must remain disabled in the combined portfolio.

Repeatable timing variations

PG_InpRandomize enables deterministic variations in time, level, stop and size using PG_InpRandomSeed. Record the seed and variation settings when comparing tests. A changed seed or timing shift is a different configuration even when the product version is unchanged.

Chapter 06

Engine C models and protection

Enabled model families

Pattern12 uses twelve strategy lanes with separate internal timeframes, exposure caps and exit rules. The trend complement uses range, ATR, EMA and directional conditions. Structure strategies have separate ownership, sizing and trade-management controls. OB_EnableTrading and the family switches determine which components can trade.

Legacy families

OB_EnableLock30xEngine and OB_EnableAurumEngine default false and are rejected when enabled in this documented combined build. They are not supported alternative configurations of this release. Leave inactive compatibility fields and excluded legacy families at their supplied values.

Shared equity guards

OB_SelectDailyEquityLossPct defaults to 1% and OB_SelectMaxEquityDrawdownPct to 6%. These use account equity to gate Engine C; they do not imply that the entire account is capped at either percentage. OB_SelectCloseOnRiskLock controls owned-exposure closure. Pattern12 and the other families also have their own sizing, exposure and risk controls.

Tester and chart behaviour can differ

OB_BacktestBypassPermanentMaxDrawdownLock defaults true. In the tester this bypasses Engine C’s permanent shared maximum-drawdown lock. A historical test using that bypass is not evidence of identical risk-lock behaviour on a demo or real chart. Run a comparison with the bypass disabled and record both configurations.

Pattern12 exits and exposure

OB_MaxExposureSlots includes pending and open exposure limits; OB_MaxOpenPositions and OB_MaxSameDirection add separate caps. Break-even and trailing controls use R multiples and volatility settings. Here R refers to the trade’s initial risk distance, not a guaranteed money return. Some exits depend on the application continuing to run.

Chapter 07

A reproducible backtest workflow

First run a short visual check

Begin with a short date range. Confirm that initialization succeeds, the intended engines are enabled, volumes match your calculation, entries occur at the expected strategy clock, stops and targets are accepted, and logs contain no unresolved errors. A successful compile, installed file or displayed panel is not a completed backtest.

Then test representative history

Use data with an appropriate tick model and realistic costs. Include trending, ranging and volatile periods. Save the exact software version, platform build, broker, symbol, timeframe, dates, deposit, account currency, leverage, spread, commission, swap and every input or preset. Save report, trade history and logs after the test finishes.

Test engines separately and together

Create separate A-only, B-only, C-only and combined presets. Compare both balance and equity drawdown, margin usage, exposure, losing sequences, costs, trade count and net result. Combined results cannot be obtained by simply adding separate engine profits because the engines share equity and margin.

Use separate validation dates

Keep dates that were not used to choose inputs. Check less favourable cost assumptions and multiple broker specifications. An attractive visual curve is not a forecast. Avoid selecting a configuration from profit alone.

Forward demo before considering live use

Observe the exact intended settings on a hedging demo account. Check actual order acceptance, timing, stop movement, reconnects and market closures. Compare the demo logs to your backtest. This documentation does not certify broker compatibility, prop-firm eligibility or future performance.

Chapter 08

Read the panel and operate the bot

Balance and equity

Balance reflects closed-account changes; equity includes floating profit and loss. A profitable balance curve can coexist with substantial floating losses. Drawdown figures depend on the reference used. The panel’s observed drawdown is not a broker-enforced loss ceiling.

Engine state and trade counts

Check the state of each engine, owned open positions, pending orders, spread and recent error logs. A panel that says active means the engine is enabled; it does not mean a trade is due. Filters, warmup, cooldowns, market hours and risk locks can all suppress new entries.

Restart carefully

Save the preset before changing parameters. Review existing positions and pending orders before stopping, removing or restarting an instance. Stopping the software does not guarantee that all open positions close. Server-side stops may remain, but virtual expiry, timers and dynamic exits need the application running.

Avoid ownership collisions

Do not run two instances on the same symbol with overlapping magic numbers or labels. Engine A uses ST1_MagicNumber through its nine-strategy range; Engine B uses PG_InpMagicNumber; Engine C reserves OB_MagicBase+1 through +306. Different identifiers reduce collisions but do not separate account equity or margin.

Monitoring checklist

At each review check connection, terminal/bot running state, expected symbol, input version, exposure, margin, current spread, news or session blocks, guard state and failed operations. Save a dated configuration change log. Do not restart a guard merely to force trading to resume without investigating the drawdown.

Chapter 09

Troubleshooting and support

Initialization rejected

Check account/execution mode, enabled engines, valid panel scale, positive sizing values, non-overlapping identifiers and session consistency. At least one top-level engine must be enabled. Engine B account-wide closing is rejected in the combined bot. Read the first relevant error, not just the final initialization message.

No trades

Check symbol availability, market hours, historical data, engine and family switches, spread/news/session filters, cooldowns, trade/exposure limits, margin, execution permissions and guard locks. A no-trade period can be valid. Do not increase size or disable every safeguard simply to generate activity.

Invalid volume or stops

Inspect the actual symbol’s minimum volume, maximum volume, volume step, tick size and stop distance rules. A percentage or lot input can normalize below the broker minimum. Rejected stops or close/delete operations may require waiting for a valid price distance; software retries are not a guarantee of immediate execution.

Results differ from a video

Compare version, preset, dates, broker data, costs, account currency, leverage, volume rules, offsets and drawdown bypasses. The video may show an earlier build. Matching the name or final profit does not establish an equivalent test.

Provide a useful support bundle

Send the platform and bot version, broker and Gold symbol, timeframe, saved preset, exact test dates and costs, report, relevant log lines and a screenshot of the problem. Remove passwords, API keys, account numbers and unrelated personal details. MT5 Market support should use product comments or MQL5 messages.

Chapter 10

Glossary and test record

Key terms

EA: Expert Advisor for MetaTrader 5. cBot: automated robot for cTrader. Pending order: an instruction that waits for a trigger price. Magic number/label: an ownership identifier. Point: a platform/strategy price increment. Pip: a configured price-distance unit. Drawdown: a decline from a stated reference. High watermark: the greatest observed balance or equity used as a reference.

Record before each test

Software version: ______ Platform build: ______ Broker: ______ Symbol: ______ Account mode: ______ Currency: ______ Deposit: ______ Leverage: ______ Dates: ______ Tick/data model: ______ Spread: ______ Commission: ______ Swap: ______ Preset and seed: ______ Offsets and pip/point sizes: ______

Record after completion

Completion time: ______ Trades: ______ Net result: ______ Balance drawdown: ______ Equity drawdown: ______ Maximum margin/exposure: ______ Errors or rejected operations: ______ Report/history/log locations: ______ Next validation step: ______

Risk disclosure

Automated leveraged Gold trading can produce substantial losses. Multiple concurrent orders and positions can amplify exposure. Gaps, slippage, rejected operations, disconnections and execution delays can exceed software thresholds. Historical simulations and demo results do not guarantee future performance. ExpertCodeFX supplies trading software and documentation; this manual is not personalised financial advice.