Best posts made by jstap

Add a shared link to see what you have done, I have used it lots.

@sheeraz @Abbas25 Once per bar can also be used to limit crosses and stop the re-entering, I prefer stopping trading until I want it to restart.

Pink blocks, pips away - buy/sell

Try something like this: https://fxdreema.com/shared/jkvf1tQad

Remove the AND block and connect in a row, connecting orange and yellow makes the block irrelevant because this says if true or false pass onto the next block

To make this a little dynamic in 1 condition Bloch, text code input MathMod(constant, 2) == 0
orange dot would be true and yellow dot would odd

Do you mean the attribute? Yes but don't trust on MT5

In MT5 most bucket actions don't work as well as in MT4. in MT5 you are better off using a more complicated way, and recording the value into a variable like this: https://fxdreema.com/shared/VPIlGJ96c

You have to use different trees to get the different results
https://fxdreema.com/shared/itNWJzpqd

Surely you can just log in start your meta trader platform and open the inputs?

Remove the once per object as it has no reference to what you are doing. You can not use - candle IDs, use ID 1 & 2, ID 3 for your reference ID, and ID 4 & 5 to complete the 5 candle set

Yes but that was the whole point in your post, for a breakout price has to be < > the trendline price, so use this value to trigger a signal. Candle x< or place trade or candle closes < >, or something similar.

project page - projects - create shared kink - open in web page - copy address bar - paste here

Custom indicators work correctly on FX, if not either you are expecting it to work differently to how it does, or it is a badly written indicator.

above buy/sell tree - check profit (period of time) < day profit - place trade
If you want all trades to close if profit is made - separate tree - check profit (period of time) > day profit - close

When you export the EX file copy all the inputs as they are written in the exact order they are in although 123 is a number it is actually a enum in cases like this

enum - HistoryLoadMode - In Days
datetime - HistoryStartTime - (can't see this value)
int - HistoryMonths - 0 (can't see this value)

This is the first 3, the rest are something similar (the last one is a bool type)

What do you mean by alert parts? This looks correct; just ensure spelling, type, and value are correct for all inputs. You will probably need to add buffers. Look in your platform's date window and see how many the indicator has.

An indicator added by MQ will already have this added, so you do not need to do anything