Walking Through a Grid: How the EA Averages Into a Position

One of the more misunderstood parts of LORENTZIAN’s configuration is the grid system, so this post walks through exactly how it behaves, step by step. The numbers below are illustrative to explain the mechanism — they are not a real trade, a backtest result, or a performance claim.

The relevant inputs

• USE_GRID — turns the grid system on or off
• GRID_DIST_PIPS — how far price has to move against an open position before the next grid order is added
• MAX_GRID_ORDERS — the hard cap on how many orders the grid can stack for one position
• GRID_MULTIPLIER — how lot size scales with each additional grid order
• PAUSE_GRID_WEAK_TREND — pauses new grid additions if the AI’s confidence score for the current trend has weakened since the position was opened

A worked example

Say GRID_DIST_PIPS is set to 8 and MAX_GRID_ORDERS to 5. An initial position opens, and price moves 8 pips against it. Rather than closing at a loss immediately, the EA adds a second order at that level, effectively improving the average entry price if the move reverses. If price continues against the position by another 8 pips, a third order is added — and so on, up to the 5-order cap. Beyond that cap, no further orders are added regardless of how far price moves; the position’s risk is now bounded by whatever stop-loss and the account-level drawdown breaker are configured to allow.

PAUSE_GRID_WEAK_TREND adds a second layer on top of pure distance: if the AI’s own confidence in the current trend has dropped since the position opened, the EA will hold off on adding the next grid order even if price has moved far enough to normally trigger one. The idea is to stop « doubling down » mechanically once the system’s own read on the market has already started to sour — distance alone isn’t treated as sufficient justification.

Why this needs care, not just defaults

Grid-style averaging is a genuine trade-off: it can improve average entry price during a temporary pullback, but it also increases exposure the longer an adverse move continues, which is exactly why MAX_GRID_ORDERS, the account drawdown breaker, and the concurrent-pairs limit all exist as hard caps working alongside it rather than being left to run unbounded. Review these settings against your own account size and risk tolerance before enabling the grid on a live account — the defaults are a starting point, not a recommendation for your specific situation.