Topics created by OD

@OD Then I don't know what can be the issue. It should work.

Variables work like a constant, I have never done it but you need to change the variable to one of these when you need: https://www.mql5.com/en/docs/constants/chartconstants/enum_timeframes

Change the type into an int and see what that does

@jstap Very interesting. Thank you,

This block passes constantly, it just only affects trades if settings allow. above the block put a condition, for each trade - candle 0 close is < or > open price (in loop), adjusted by x pips

If you create a constant instead of a variable they can be optimised, you can set a variable from a constant,

Yes add to a modify block, you could also use custom code.

@jstap This works thanks a lot

Good for you! 😉

Interesting, to block numbers, always correct themselves, something to look out for

@od i'm sorry, i can't help you

When 1 TF crosses set a flag to true when it crosses back set flag to false, do the same with a different flag on the other TF, check flags before buy/sell.

@od No you can do it on back test.

@ambrogio No prob I'll try to build another better one. You have my appreciation for the support.

@od That's fine if it works as needed.

@od In the pink blocks you have pips away, you also have the option to only allow once per trade, or you can set for parent trade or current partial trade. One of these options should work but I have not used them much, I would setup a small project so I could back test each option, and find the one that works best for my needs.

@od No . You are comparing a price level (for example 1.2326) with a distance in pips (30). You need to compare equivalent elements, like two prices ro two pips distances.

@od You should use the blocks on the 'on trade' tab as suggested by jstap.

@od You are using the same value (ie variable) to define that pending order open price and stop loss. Your broker will nevew allow that. You need to use different values (ie variables).