Use these settings

@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.
@seb-0 well, I do optimize some times, but much less than before.
To my experience, with optimization you can make any EA look super good. Whats the point... the performance will not repeat in live trading.
So, if the EA doesnt look promising with random inputs backtest, I dont usually bother to force it look good with optimization.
Its 98% about the strategy itself, 2% about the input values.
How about this
once per bar (M15) ->
close all trades ->
your condition -> buy/sell
@ambrogio hmh? 
What is the celebration here?
@DanZig55 I have used those 3 bullet points in many EAs.
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
@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
@l-andorrΓ I just used them for troubleshooting, should have removed from the shared version
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
@BBMess MA method is always an enumeration by itself, that might cause problems.
https://www.mql5.com/en/docs/constants/indicatorconstants/enum_ma_method
Please send a shared link of your example
Open the generated .mq4 file in the metaeditor - the about-stuff is right in the beginning, you will figure it out 
@richard96816 Agreed, fxdreema has some very versatile functions. It's very good to see other's ideas too, avoiding "tunnel vision" with the alone development.
Some say that sharing good eas doesn't happen because nobody would give away free money like that. I don't believe that approach at all - no matter how profitable your system is, there is always a risk present with trading, and the risk is higher if you don't even know the system you are using. So you have to learn the system, and thus you can also develop it further. Collaborative effort is the way to go
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!
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 