Versión 8.0
2020.02.10
-->Minor internal coding modification.
Versión 7.60
2019.09.24
-->Minor Update.
-->Improved Coding.
Versión 7.40
2019.04.11
-->Fix Bugs
1. Lots Multiple will not work when you set Lot type = Lots Base On XBalance
-->Improved Logic.
Versión 7.0
2019.01.24
-Minor Bugs Fix
-Add New Inputs
--> News Time in Mins (before & after) : You can set mins to stop on news time. Example if you set 60 that mean EA will stop trade before and after 60 mins. (total 1 hours) on new time.
Versión 6.10
2019.01.15
--Bugs Found
--->Found bugs Daily Max Trade not work properly. This bugs fixed this version.
Versión 6.0
2018.12.27
-->Minor Update
-->EA Use Four Internal different strategy. Previous version EA has only one input of "MagicNumber" in Basic section. In new version EA has hour different MagicNumber. So now it is safe EA use both Strategy (ST1 and ST2) in same account.
IMPORTANT- Update only when you have no existing trade.
Versión 5.60
2018.12.24
--By default work was stop from Dec-22 to Jan-2. But i remove this restriction from this version. But still i recommended not to use EA this time
Versión 5.50
2018.12.19
--Delete some input
--->Enable Grid (Deleted).
--->TakeProfit For Grid and StopLoss For Grid (Deleted). TakeProfit and StopLoss value will count as for TakeProfit For Grid and StopLoss for Grid.
We remove some input for easy way to find optimize setting.
Versión 5.10
2018.12.11
--Faster backtest then previous version.
--Auto Adaptive Setting add on for strategy_1
--ReverseSignal not working properly in previous version. We fixed it.
Versión 5.0
2018.12.03
--Individual TP/SL not work properly. Fixed this version
--Improved Logic
Versión 4.70
2018.11.23
-Some Bugs Fixed.
-Some Input setting changed.
Versión 4.60
2018.11.16
--Improve coding.
--Add Manual trading strategy
Excellent EA, good performance.
It would be interesting that in a next version you could include a dynamic TrailStop.
Example.
Define a trigger point and from there shoot a trail stop. And instead of defining a fixed distance in points, it would be better to define a percentage of the size of the operation.
thus, as you move away from the starting point, the movement range increases for the oscillations.
and then place a second trigger. when it reaches a second level
something similar to the stop of this project
https://www.mql5.com/en/code/9248