Position Building Schedules

Most EAs that scale into a position bury the scaling logic inside the trading loop itself: a chain of if-price-moved-X-pips-add-Y-lots checks tangled up with the OrderSend calls that execute them. That makes the schedule itself impossible to unit test, and impossible to reuse between an EA that pyramids winners and one that averages into losers, even though the underlying question - "given where price is now, is a step due, and how big is it" - is identical in both cases. This library separates that question from the trading. A PositionBuildSchedule is a fixed sequence of steps, each carrying a trigger offset in pips from the initial entry price and a fraction of the schedule's total target lots. PositionBuildScheduleNextDueStep answers "which unfilled step, if any, has price already reached" given nothing but the schedule and the current price - no order pool access at all - and PositionBuildScheduleLotsForStep hands back that step's lot size already normalised to the symbol's lot step and clamped to its min/max, with the same epsilon-guarded rounding house style requires everywhere volume is computed. The caller (an EA) is responsible for actually sending the order and then calling PositionBuildScheduleMarkFilled; this library only ever computes, never trades. Two ready-made builders cover the common shapes: BuildPyramid produces N equal steps that arm as price moves favourably (adding to a winner), and BuildAveragingIn produces N geometrically front-loaded steps that arm as price moves against the initial entry (averaging into a drawdown, largest step first). Averaging into a loser carries real risk of its own - this library computes the schedule faithfully but takes no position on whether that is a sound strategy for the reader's account. Notes and limitations - A schedule holds at most 20 steps (POSITION_BUILD_MAX_STEPS). AddStep/the builder functions return false rather than overflow. - The library never touches the order pool and never calls OrderSend - it only computes trigger prices and lot sizes. All risk of averaging into a loser, exceeding margin, or violating a broker's max-lot rules is entirely the caller's to manage. - PositionBuildScheduleLotsForStep re-reads MODE_LOTSTEP/MODE_MINLOT/ MODE_MAXLOT from the broker on every call rather than caching them, since those can differ between symbols and change between brokers. - Trigger checking assumes the caller polls (e.g. once per tick); the library has no timer or event of its own to detect a due step. - If price gaps straight past more than one step's trigger in a single tick, PositionBuildScheduleNextDueStep still returns them one at a time in schedule order on repeated calls - loop it (as the demo does) until it returns -1 to catch every step a gap jumped over.

Script · MT5 · v1.0 · Free

Tags: MT5 Script · MQL5 Source Code

MQL4 & MQL5 scripts · PolyMaria