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)
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)
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
Yes this can be automated but a working example is a lot of work, make a start just doing 1 thing, then add a shared link asking how to sort something
on the tick to place a trade, on trade to modify a running trade
This will check the last number of candles chosen in the inputs, and print in variable/comment the largest, it works on total candle size, if you want body High - Low would need changed to Open - Close. Should do what you want, for example, variable == 1 would give you the signal for 1 being the biggest: https://fxdreema.com/shared/t0H77rtkd
Message support and ask them, no 1 on the forum can change this: https://fxdreema.com/support
Then don't close them, you will need other blocks saving the %, for example start day balance = x.xx, x.xx /100 *20 saved in a variable is 20%, use the variable in the check profit block
@JaydaiMoney pink blocks - for each closed trade - modify variable set to loop SL value, put variable in a comment to see the result
What exactly do you mean? I assume the constant is a string...
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
Technically it shouldn't, maybe try tidying it up a little. I also do not get how the delay will ever be greater than 0?

There is a problem with martingale. Although the principle of if it goes up, it will come down is true and works, the drawdown or runaway will happen at times. In my book, there is a martingale EA and how to create it, but the set-up can be a very personal choice, so learning the reason why something happens is important and will change the reason why you have an EA doing something.
Yes, for testing I would set timeframes to current
set conditions and flags in separate trees,
no buy trade - candle 0 close x> MA - set a flag true
check flag true - candle 0 close x< - place buy - set flag back to false
no sell trade create another 2 opposite trees for sell
This will give you a good start to work with
Yes it's possible, start a project and add a shared link if it is not working and say why
on trade tab - purple trade closed block - delete line block