fxDreema can do that, but before trying you need to be completely sure the platform can correctly identify the indicator's buffers AND checking if the indicator doesn't repaint. If any of those conditions fails, the indicator will not work on fxDreema.
@bigfoot No, once you turn off your PC all information regarding previous trades is lost. The only two ways to do that is by using 'terminal variables' (not the 'normal' variables) or by using a specific 'for each trade' structure in the 'on init' tab with this block:
Then remove blocks 45, 50 and 44. They are not necessary.
@Suraj0544 Here you have some changes you should do:
Block 32 can be removed. You don't need it.
Blocks on top of each block tree are wrong. They should be ordered from lower to higher ID number. This means Block 10 should be block 1, block 3 should be block 2, block 1 should be blocks 3, block 16 should be block 4 and block 33 should be block 5.
@Piet-Pompies Then connect this block immediately below block 45 and then connect it by using the YELLOW output dot to block 44.
@Salmuranda You should defnitely try other VPS. Depending on where your IP provider is located, where your VPS is located and where your broker's server is located, execution time can be even worse than that. This is why me, living in Western Europe I only select Western European VPS and only use Western European broker's servers.
@Suraj0544 You will need several 'condition' blocks in order to define what you understand as a 'hammer' candlestick. For example, you will need something like this to define the minimum body size of candle ID 1:
Then another one for the upper/lower wick and so on.
In case of an engulfing, you will need twice as many blocks. Some of them for candle ID 1 the the same for candle ID 2.
Do you mean someone reviewing an existing fxDreema or building it from scratch?
@Joomlun Is this the whole project or just part of it?
Interesting. Because I'm not a programmer, I have no idea if that can be the best solution or not.
@sktsec Interesting. Thank you.
Variables can ALWAYS be modified. Constants can NEVER be modified. That is the rule.
I never use 'basket of trades' blocks. I always use 'for each trade' structures instead. They are 100% effective. You should substitute them IMHO.
Remove both 'once per tick blocks. They are redundant there. Additionally, don't use GMT time on both time filters. They are not fully effective. Use server time instead.
@Xeta50 I remember someone complaint about this some weeks ago. I don't remember who was. You can use the search tool on the forum to find the solution.
