I mean to say if any one position is in $50 loss. then close half of it. and leave remaining positions. Currently it close 50% of all loosing positions once condition is met (50$ drawdown)
Account Protector
- Thread starter Enivid
- Start date
- Watchers 193
The filters should work for you if your trades are in separate currency pairs. If they are all with the same currency pair, same magic number, and same commentary, then the filters won't help.
yes. it is usually Gold only.. Was setting up Demo account to run EA.
Attachments
Perhaps, it makes sense to just use a stop-loss on each trade in your case?
yeah.. thats right.. but this is demo account.. just took trades to have some trades running in Drawdown so I can test EA.. this is not my real account..
But instead of account level of Floating drawdown. If we can do it on Trade level drawdown. that will be great. Reason of this is.
1st Entry.. Running in $100 drawdown
2nd Entry Running in $50 drawdown
3rd Entry Running in $10 drawdown
now when EA will activate.. it will close half of all 3 entries.. whereas if it close only 1st Entry, so we have better chances of recovering account and closing all in profits. as 3rd Entry is more likely to turn blue any moment. So may be in future release if you can add this feature to check condition separately for each entry rather than Floating Loss for all trades combined, that will be awesome. Thanks.
Dear fellow trader.
I suggest you make the trade method simple. It is very essential.
Account Protector has been updated to version 1.12. It brings some important changes. I recommend reading the changelog before updating:
- Added an option to connect conditions ticked on the Conditions tab with logical AND (WaitForAllConditions). This means that you can make the Account Protector react only when all the selected conditions are met, not just one of them. (Via GitHub)
- Added an option to connect Account Protectors using a signal action/condition. (@Almon)
- Added display of the daily opening balance for daily profit/loss percentage conditions. (@Tonywong131)
- Added input parameters to disable any condition.
- Added conditions based on the current account balance. (@GBPMaster)
- Added an option to execute orders in asynchronous mode in MT5 (AsyncMode).
- Added an input parameter to make the EA disable autotrading when equity trailing stop is hit (DisableAutoTradingOnTS).
- Added informative tooltips to most panel elements.
- Added an option to modify the Emergency button's behavior. If CloseOtherChartsOnEmergencyButton is set to true, the button will close all other charts instead of disabling autotrading.
- Added logging of order execution results in MT5.
- Changed the order of actions triggering to make sure that Close all other charts takes priority. (@Nico DFM)
- Changed how the positions closed via the Close action are filtered by profit/loss. They now ignore the profitable/losing options from the Filters tab and instead use the respective action setting. (@MrMaths)
- Changed how conditions are logged to avoid logging disabled conditions.
- Fixed initial daily balance calculation for cases when CountFloatingInDailyPL is set to true. (@Tonywong131)
- Fixed log file name to be exactly the same as given via the LogFileName input parameter. (@EnrichWave)
- Fixed a bug when the bottom condition on the Conditions tab could get overwritten by another condition (if enabled via input parameters).
- Fixed a bug with commission calculation in MT5.
- Fixed descriptions of some conditions.
Hello,
As soon as I attach the EA to the chart, I get these errors:
2025.01.26 12:26:47.062 Expert Account Protector AUDJPY,H1: removed
2025.01.26 12:26:47.062 Account Protector AUDJPY,H1: uninit reason 8
2025.01.26 12:26:47.062 Account Protector AUDJPY,H1: not initialized
2025.01.26 12:26:47.062 Account Protector AUDJPY,H1: zero divide in 'Account Protector.mqh' (1381,143)
Can you check, please?
Thank you.
As soon as I attach the EA to the chart, I get these errors:
2025.01.26 12:26:47.062 Expert Account Protector AUDJPY,H1: removed
2025.01.26 12:26:47.062 Account Protector AUDJPY,H1: uninit reason 8
2025.01.26 12:26:47.062 Account Protector AUDJPY,H1: not initialized
2025.01.26 12:26:47.062 Account Protector AUDJPY,H1: zero divide in 'Account Protector.mqh' (1381,143)
Can you check, please?
Thank you.
Which platform are you using (MT4 or MT5)? Which build?
What version of the Account Protector?
Are you connected to the trading account?
Anyway, please try the attached version and let me know if it works for you.
Attachments
Yes, I am connected to the trading accounts (even if the market is closed now).
Two different brokers, same MT4 version, same issues.
The EA version you provided does not show any error messages, and it seems to be working!
Thank you!
Account Protector has been updated to version 1.121 to address the potential division by zero situation reported by @FraTheKing.
Hello,
Thank you for this nice and useful EA.
Can you add please: "Enable autotrading tomorrow" or "Enable autotrading after [Input] days" in the "Actions" tab please?
Thank you so much.
I mean, after an Action "Disable Autotrading", the new option "Re-enable autotrading the day after or tomorrow" will re-enable the autotrading (with all previous Account trading parameters).
Sorry, now I understand. I have to add Account Protector in another chart and use the Timer option to Enable Autotrading. Thank you
Hello,
I would like to suggest an improvement to your EA.
I use the timer with the "Local time" option selected:
When MT4/MT5 restart, the EA does not remember that option and switch it to "Server time".
It would be nice if it could keep the previous setting/option when MetaTrader restarts.
Thank you.
I would like to suggest an improvement to your EA.
I use the timer with the "Local time" option selected:
When MT4/MT5 restart, the EA does not remember that option and switch it to "Server time".
It would be nice if it could keep the previous setting/option when MetaTrader restarts.
Thank you.
Account Protector updated to version 1.13 to address some important bugs reported recently:
- Fixed a bug that prevented the timer's time type from saving and loading correctly. (@FraTheKing)
- Fixed a potential array out range error that could arise in some situations. (GitHub issue)
- Fixed a potential division by zero error that could arise in some very rare circumstances.