@l-andorrà can you elaborate, how the loop block uses local time?
In your example, you just check that the candle ID is 0. Candles are always server time...
Can you test by printing out the "Close Time (UNIX)" variable from each closed trade, so we see what timezone those values will be?
I would test myself, but I have the same timezone as my broker..
@titangeorge Sounds good, I hope it works for you!
Personally I have no interest in strategies that I can't backtest, but we all have different styles.
How about this
once per bar (M15) ->
close all trades ->
your condition -> buy/sell
@l-andorrà you dont have to guess, just look: get the close time of that order, put it in a variable and see what the value is
@ambrogio hmh? 
What is the celebration here?
https://fxdreema.com/shared/GEUH4hBoe
Maybe this helps.
I didn't really understand your example, but I think I know what youre meaning
In your example, connecting that AND block back to the "once per bar" creates a loop which never changes - thats bad
If ZigZag indicator had a low at candle ID 1, the low would be printed to the candle low 1.
Candle close 1 is never below candle low 1, and close 1 never crosses below candle low 1.
@traderea6 ok this is a fairly large subject, so I'll make a tutorial to the tutorial section of this forum, check it out!
https://fxdreema.com/forum/topic/9406/tutorial-test-eas-like-a-pro
Strategy optimizer always tries to "trick" you by finding profitable trades from totally random set of possibilities, i.e. profit in history but random result in future.
With this mindset, the goal in optimization is to find results that are least likely random coincidences, i.e. results with high statistical significance. This significance increases when you have
Open the generated .mq4 file in the metaeditor - the about-stuff is right in the beginning, you will figure it out 
@Mantadiver you have 10000 unique blocks without any pattern among the blocks?
If not, I'm willing to bet you can reduce at least 70% with some new structuring. You up for it?
The "once per bar" works only at the beginning of each bar, so the price is essentially the open price. That's why its not very beneficial to check both open and close prices at the first tick, because they are the same.
I would use this logic:
In English: once per bar we check the current candle open (current candle = id 0) and compare it to the indicator (blocks 5 and 6).
If that condition is true -> open trade
Then check close price, and not current candle close but LAST candle close (id 1) (blocks 7 & 
Note that this is somewhat silly logic because 2 of the 4 conditions must always be true - the bot trades 2 times every bar!
Those price constants are determined by mql5 themselves: https://www.mql5.com/en/docs/constants/indicatorconstants/prices
"Average" might not be the optimal term there, but the calculation is correct nevertheless
What I dont like:
What I like:
Just my (personal) (and probably foolish) thoughts 
They all execute on the same tick, no matter if there was 1000 horizontally connected blocks
It seems MT5 got a resolution selection in the latest update. I suppose this helps with objects
@cesardefez just do it like in the upper picture, its fine.
