Guide for the forthcoming edition. The old version 3.14 PDFs are retained as an archive, not instructions for this edition. Replacement PDFs follow completed acceptance checks.
Choose one or two triggers — whichever comes first
Select one or two of: a supported direct protection instruction from the signal source; a favourable distance measured in explicitly configured pips; or a customer-set percentage of the path towards the configured profit target. With two triggers, either may initiate protection first; both are not required.
Set the numeric thresholds yourself. A pip needs an exact definition for the symbol and broker. A percentage needs a valid target reference; missing or conflicting targets must be reviewed. The software does not invent a threshold or reinterpret an ambiguous source instruction as permission.
Protection must be confirmed before trailing
Reaching a trigger requests the configured stop adjustment. Protection is confirmed only after the broker accepts the change. Trailing begins after confirmed break-even protection and the configured additional distance. Pending, rejected or unknown modifications must remain visible.
A refreshed broker check must prevent a new request from weakening an already improved stop. Broker stop/freeze rules, freshness, ownership and costs still apply. New settings do not rewrite frozen plans of existing setups automatically.
Observe what happened
Review the trigger, progress, requested stop and broker result for the owned position. A stop still at its original level can mean the trigger was not reached, a target or pip definition is missing, the connection is unavailable, ownership is unresolved, or the broker rejected the modification. Read the recorded reason rather than resending a signal.
On Demo, check both trigger orderings, successful and rejected stop modifications, trailing after confirmation and recovery after restart. Confirm each result from the broker before choosing Live.
Account changes and expiry
The signed file belongs to the device and local customer identity, not permanently to an MT5 account. Changing accounts requires an explicit verified connection and supervision of exposure on the previous account.
Paid-license expiry must not stop protection of previously owned positions. The application must remain running and connected, with fresh ownership. Pause and Emergency stop prevent new entries; neither automatically closes positions.