Analyzing my grid accounts with medium risk (initial lot 0.01 for every $300 of balance - https://www.mql5.com/en/signals/1295791) and conservative risk (initial lot 0.01 for every $450 of balance - https://www.mql5.com/en/signals/748852), you can see that a drawdown of more than 30% happens about once every two years.

Thus, insurance in the form of forced closing of all positions at a 30% drawdown looks reasonable and pays off within 2-3 months.

On more aggressive accounts (for example, the initial lot is 0.01 for every $150 of balance - https://www.mql5.com/en/signals/920482), I see the use of closing at drawdowns as ineffective, since large drawdowns can be frequent. From such accounts, you need to periodically withdraw profits (every few months) to accounts with medium and low risk.

Utility update

1) It became possible to delete pending orders when closing positions.

"Also_delete_pending_orders_at_profit" - delete pending orders when closing in profit.

"Also_delete_pending_orders_at_loss" - deleting pending orders when closing at a loss.

2) Another position accounting model "Select_trades = one_given_magic_and_chart_symbol" has appeared. When choosing this model, ONLY positions with a magic number from the "One_given_magic_number" parameter for the chart symbol to which the utility is attached will be taken into account.

Hi, no, it won't stop, the current equity is estimated relative to the current balance. Thus, in your case, the floating drawdown should be -100$ to close trades.

Update 1.5 (optional update)

You can hide utility information on the chart: Info_on_Chart = false.

P.S. I opened my trading chat, join: https://www.mql5.com/en/messages/011e4f235b10dc01

Update 1.6

Added time parameters.

Time values ​​for when the utility will close positions (when the specified profit or loss conditions are met): Start_Time_Work and End_Time_Work (for activation, Time_for_Work=true).

Time values ​​for when the utility will not close positions under any circumstances: Start_Time_StopWork and End_Time_StopWork (for activation, Time_for_StopWork=true).