Step 1 — Match environment
- Symbol matches your broker naming (e.g.
XAUUSDvsGOLD). - Timeframe matches the preset (e.g. M5 vs M15).
- Session behavior aligns with the symbol (indices/commodities differ from FX).
1) Naming convention
Preset names encode intent. A preset should make it obvious where and how it is meant to be used.
Format (example):
CORE_EURUSD_M15_R1
Meaning:
CORE = core engine family
EURUSD = symbol target
M15 = intended timeframe
R1 = risk profile (R1 conservative → R3 more aggressive)
If your current presets don’t include
R1/R2/R3, you can still use this page as guidance.
The core idea is: symbol + timeframe + risk intent.
2) How to select the right preset
Select presets by matching your chart environment first. Only then consider risk.
Step 2 — Match intent
- Choose a risk profile you can tolerate (start conservative).
- If a “regime” label exists, choose the one that matches current conditions.
- Validate execution on demo before scaling.
3) Risk profiles (R1 / R2 / R3)
Risk profiles are not “better vs worse”. They are different operating modes designed around exposure and tolerance.
R1 — Conservative
Lowest exposure. Designed for validation runs and risk-sensitive accounts.
- Smaller base risk
- Stricter filters
- Fewer trades (often)
R2 — Balanced
Default-like profile. Balanced between selectivity and activity.
- Moderate exposure
- Standard filters
- Baseline behavior
R3 — Assertive
Higher exposure and/or looser conditions. Only for users who understand risk and behavior.
- Higher base risk
- Looser thresholds
- More trades (often)
Default recommendation: Start with R1 or the most conservative preset available, then scale carefully.
4) Regime intent (why presets differ by market conditions)
Many strategies behave differently across volatility and trend regimes. Presets exist to avoid “one-size-fits-all”.
Typical regime dimensions
- Volatility: low vs high (spreads/ATR behavior changes)
- Trend: trending vs ranging
- Liquidity: stable session vs thin hours
What a regime preset changes
- Filter thresholds (e.g., spread/volatility guardrails)
- Stops/targets distance (symbol-dependent)
- Entry sensitivity (stricter vs looser)
Regime presets are a safety mechanism. They keep behavior consistent under changing conditions.
5) What you can safely adjust
If you must customize, prefer “outer-layer” knobs that change risk and operations — not the strategy core.
Safe adjustments
- Base risk % (small increments)
- Max spread threshold (conservative)
- Session window (avoid thin hours)
- Max positions / concurrency limits
Operational adjustments
- Enable/disable news windows (if available)
- Disable symbols temporarily during abnormal conditions
- Run one symbol first, then scale
Support note: If you change many parameters, your setup becomes “custom”.
Support becomes slower because behavior is no longer preset-defined.
6) What not to change (unless you know exactly why)
These are “core behavior” parameters. Randomly changing them often breaks the strategy logic or increases failure modes.
- Signal thresholds and entry logic parameters
- Regime filter timeframes (unless you understand data availability implications)
- Stop/target logic multipliers if you haven’t validated symbol constraints
- Anything labeled “experimental” or “internal” (if present)
Rule: One change at a time. Document what you changed and why.
7) Versioning & traceability
Presets should be traceable. When releases happen, it must be clear which parameters changed and why.
Good practice
- Keep preset names stable
- Document changes in release notes
- Version presets internally (e.g., v1.2) if needed
Why it matters
- Reduces support ambiguity
- Enables controlled iteration
- Prevents “silent behavior changes”
8) Support-ready pack (copy/paste)
If you ask for help, send this once. It prevents long back-and-forth.
Symbol / Timeframe: …
Preset name: …
Risk profile: R1 / R2 / R3 (or “most conservative”)
Broker: …
Account: demo / live
Changes made: none / list changes
What you expected: …
What happened: …
Logs: paste 20–50 lines around the event
Screenshots: chart + parameters
Reminder: Orion Core Forge provides software tools and documentation. Nothing here is financial advice.