Parameters
Configuration parameters, rule formats, and slippage modes.
Plugin Parameters
Configure these parameters in MT5 Administrator under the plugin settings.
| Parameter | Type | Default | Description |
|---|---|---|---|
API_Key | String | default | Secret key for the HTTP REST API. Leave empty to disable the API. |
API_Port | String | 8444 | HTTP port the API listens on |
PNL_Track_Account | Integer | 0 | Account login for DEAL_CHARGE tracking. 0 = disabled. |
Whitelist | String | (empty) | Comma-separated exempt account logins (e.g. 50123,50456) |
Rule_1 | String | (empty) | Slippage rule (see format below) |
Rule_2 | String | (empty) | Slippage rule |
| … | … | … | Through Rule_8 |
Rule_8 | String | (empty) | Slippage rule |
Rule Format
Each Rule_N parameter uses a pipe-delimited format:
target | threshold | mode | value | unit | apply_on | symbols | priority
| Field | Required | Default | Description |
|---|---|---|---|
target | Yes | — | Group mask (e.g. real\*) or account logins (e.g. 10005,10006) |
threshold | Yes | — | Time threshold in seconds (trades closed faster than this get slippage) |
mode | No | fixed_pips | fixed_pips, percent_profit, or scaled_time |
value | No | 1.5 | Slippage amount (pips, percentage, or ignored for scaled_time) |
unit | No | pips | pips or points |
apply_on | No | profitable | profitable (only winning trades) or all |
symbols | No | * | Comma-separated symbol list or * for all |
priority | No | 0 | Higher number = higher priority when multiple rules match |
10005,10006), it's treated as account logins. Otherwise it's treated as a group mask.Examples
Fixed Pips for All Real Groups
Rule_1 = real\* | 120 | fixed_pips | 1.5 | pips | profitable | * | 0
Apply 1.5 pips slippage to all profitable trades in real\* groups closed within 120 seconds.
Percent Profit for Crypto Accounts
Rule_2 = 10005,10006 | 60 | percent_profit | 20 | | profitable | BTCUSD,ADAUSD | 10
Capture 20% of profit on BTCUSD and ADAUSD trades for specific accounts closed within 60 seconds.
Points-Based for a Specific Group
Rule_3 = real\std\scalper | 120 | fixed_pips | 15 | points | all | * | 5
Apply 15 points slippage to all fast trades (profitable or not) in the scalper group.
VIP Group with Higher Priority
Rule_4 = real\vip\* | 90 | fixed_pips | 2.0 | pips | profitable | EURUSD,GBPUSD | 20
Apply 2.0 pips only on EURUSD and GBPUSD for VIP groups, with high priority.
Filters
| Filter | Description |
|---|---|
apply_on | profitable — only profitable trades. all — all fast trades. |
min_profit | Only apply if profit exceeds this dollar amount (API-managed rules only) |
min_volume | Only apply if volume exceeds this lot size (API-managed rules only) |
max_slippage_cap | Maximum slippage limit in pips. 0 = no cap (API-managed rules only) |
symbol_filter | Comma-separated symbols or * for all |
Priority & Fallback
- Account rules always win over group rules regardless of priority number
- Within the same scope, higher
prioritynumber wins - Rules whose
symbol_filterdoesn't match the trade symbol are skipped, allowing fallback to the next matching rule - Example: a
percent_profitrule forBTCUSD,ADAUSDat priority 10 + afixed_pipscatch-all at priority 1 → crypto uses percent, everything else uses fixed pips
Fallback Behavior
Rule_1 through Rule_8) are used only when no API-created rules exist. Once you create rules via the REST API, those take precedence and the parameter-based rules are ignored.API-created rules are persisted to BrokeretSmartExec_rules.dat next to the DLL and survive server restarts. Delete the .dat file to reset to parameter-based defaults. Changing plugin parameters in MT5 Admin triggers an immediate live reload.
Whitelist
Specific accounts and groups can be exempted from all slippage rules:
- Account whitelist — Set via the
Whitelistplugin parameter (comma-separated logins) or managed via the API - Group whitelist — Managed via the API using wildcard group masks (e.g.
real\vip\*) - Whitelisted accounts are checked before any rule evaluation for zero overhead
Next Steps
- API Reference — Manage rules, whitelists, and stats via REST
- Introduction — Back to the plugin overview