I see it can be difficult, rather than change things just count the hours difference between market watch and your computer, then use this for what the ea is doing.

Ok, above the block modify a variable to add all the constants together with text code input, then add this variable to the block

@tradingforward23 👍

what type of ea u r building?

Yes, you can get that in the standard blocks, but if you want the EA to react when ZZ changes direction you will need to detect the change

@AymaniX try this one 3c8cb1cf-049b-4e0d-a496-5b443233b9df-image.png

Candle close 0 is the current moving price, generally if you check candle1 then as this closes candle 0 opens and can check candle 1, there is also once per bar to prevent things happening more than once in a candle

@amiinkiaei
Check
https://docs.mql4.com/constants/chartconstants/enum_timeframes

Actually, it is the number represented by the string that matters

They should close normally. That error is stopping new trades to be open, not to stop closing those that are open now.

@Khun-Som-Ath Definitely they are not needed if the bot is supposed to be 100% automatic (is no human intervention at all). So let's begin with those initial distance calculations. Here you have a first structure:

https://fxdreema.com/shared/KJ2qALMbb

I created a Constant that is supposed to select the distance in pips for both trades to be activated. Then on the chart you will see both price levels. If this is what you want, we can move on from there.

@Tehern Yes, you should use two separate 'for each trade' block trees, one for each function. You current use of a blue 'trailing stop' block connected below a 'for each trade' is not good because you are connecting a loop to another loop. You'd better use pink block only on both blot trees.

@honeylogs86 I knew that. My question was why do you need that if the bot is supposed to be 100% automatic with no human intervention.

Many thanks!!

line drawing is perfect on chart, but dont taking even single trade at any line.... i tried many settings.... but dont know whats the problem...

@jstap I'm not in front of the computer

@Morpheus_0 👍

@YOSEF It refers to the most recent history. That means that if you are looking for 2 consecutive losses, as soon as they happen (ie, at the second one), the counter will immediately reset. Same if there is one loss and then one win. The counter resets immediately.