Aurum Risk Sentinel
- Utilities
-
Shakir Mehmed
I have built and tested trading software for more than eight years. I build and test gold (XAUUSD) Expert Advisors, which are trading robots, for MetaTrader 5 and 4. Ideas start in a Python engine, then go through the MT5 Strategy Tester (MetaTrader's backtesting tool) on 1-minute OHLC, which builds - Version: 1.1
Aurum Risk Sentinel is a risk utility for MetaTrader 5. It watches account equity and selected exposure during a server day. It is not a trading strategy and it does not open trades.
Logic
- Records the start-of-day equity and a running peak equity.
- Calculates the current daily loss and the drawdown from the stored peak.
- Counts the managed open positions.
- Enters a locked state when a configured limit is reached or the managed position count is above its limit.
- When locked, attempts to close matching positions and delete matching pending orders, according to the inputs.
- Saves its state in terminal global variables for the account login and checks the saved values after a restart.
- Shows equity, daily loss, peak drawdown, position count and state on the chart.
Default inputs
- Maximum daily loss: 3.0%
- Maximum peak drawdown: 8.0%
- Maximum open positions: 6
- Close positions when locked: enabled
- Cancel pending orders when locked: enabled
- Magic filter: -1, which manages all magic numbers
- Status prefix: Aurum Sentinel
The limits are inputs. Check them for the account, symbols, broker and operating process before use. Set a magic number in the filter to manage only the positions and orders that carry it.
Important limits
The utility depends on the MetaTrader 5 terminal, account data, trading permissions, broker responses and network access. A close or delete request can be rejected, delayed or filled at a different price. A stopped or disconnected terminal cannot monitor the account. The utility does not prevent losses and does not replace supervision. Use a demo account first. It provides monitoring and order-management actions only, and trading decisions remain with the user.
