Config Mode and Lazy Trader 3 optimization

The main blocks in this workflow

• Config Mode: the place where optimization presets are configured before they appear in tester inputs.
• advisor inputs: advisor parameters that Strategy Tester can iterate through start / stop / step values.
• structure preset, Direction preset, Box preset, Time preset, and Base config preset: compact bundles of settings instead of direct brute force across every UI control.
• result table: the table where each row represents one optimization pass with its selected values, profit, trades, drawdown, and other metrics.
• Generated plan cfg: the file you can move from Common/Files/ZEN/admin_cfg into MQL5/Files/ZEN/plan_cfg, load in the normal UI, and combine with other plans.

Why optimization is built around presets

• Every Lazy Trader canvas contains many internal parameters. If each button were optimized directly, the number of combinations would become unmanageable very quickly.
• structure preset packages several structure settings into one switch. For example, a Swing Structure set can be reused in Start After, Imp Rearm Structure, structure models, and Swing Direction.
• Direction preset covers custom Direction modes: Box Direction, MA Direction, and Swing Direction. Long / Short remain simple static modes.
• Box preset is more complex than a regular preset: it can contain from one to five time boxes, and every box has its own preset page.
• Time preset and Base config preset also use internal pages because they contain too many parameters for one interface page.
• The model families shown in the video are Box Fractal, Larry Williams, Classic Structure 1, Classic Structure 2, Classic Structure Reversal, BPR, and MIMA. The second Classic Structure entry is left as an extra structural variation.

Practical test order

1. Enable Master on/off for Admin Optimization.
2. Select only the inputs you actually want to iterate in this run.
3. Keep only one model enabled, not all models at once.
4. Select one weekday, for example Monday only.
5. Choose Direction logic that matches the test: MA Direction, Box Direction, Swing Direction, or static Long / Short.
6. Run optimization and wait until the table contains enough useful results.
7. Choose rows by more than profit: inspect drawdown, trade count, stability, and risk fit.

How to read the result table

• Every row in the result table is one optimization pass with its own selected input values.
• Right-clicking the table lets you add or remove statistics columns.
• Evaluate the row as a whole: profit, drawdown, trades, expected payoff / accepted payoff, stability, and whether the row fits your risk profile.
• A point on the optimization chart corresponds to a table row, so the row is more important than the visual point without context.

How to turn one result row into a plan cfg

1. Before selecting a row, enable Save generated admin plan cfg and midi.
2. Double-click the row with the result you want. Once the run starts, it can be stopped immediately; the file has already been generated.
3. Open the tester Data Folder and find the file in Common/Files/ZEN/admin_cfg. Its generated name may look like a timestamp or random symbols.
4. Rename the file to a readable suffix, for example 123 or 234.
5. Move it into the normal terminal folder: MQL5/Files/ZEN/plan_cfg.
6. In the Lazy Trader UI, add a plan, type the suffix, press Load, and resave the plan after loading if you see the name change.

Minimum testing discipline

• For serious conclusions, use a long enough history window, not two weeks. The video uses about three years as a practical reference: less is too little, more is usually unnecessary.
• Do not leave extra true / false conditions enabled by habit. Check PDH, PDL, PVH, PDL, and similar filters before launching a multi-day test.
• Save discovered plan files under readable names and keep the mapping: asset, broker, model, weekday, date range, and key preset values.
• Compare not only maximum profit, but also whether drawdowns are predictable and whether risk is distributed logically.