Posts made by l'andorrà

@EnriqueA04 That I'm afraid I don't know. I always use Tickstory data and I never have any problem when importing their data. It's not very expensive. Maybe you could try it too.

@Ruchit1341 You can try this general idea:

Please notice that this is the 'on trade' tab, not the 'on tick' one. Every time a pending order is triggered, you can program the next one. In my example, the purple block is selecting buys only. You need to create another block tree for sells.

I still think using a custom indicator is a better option. Doing that on fxDreema is feasible, but the number of code lines necessary for it will make the optimization later simply unacceptable.

What regulation will you be using?

What do you exactly mean by 'warehouse'?

@KLG Do you mean a common SL for all trades after the 5th one or no trade is having a SL until the 5th one is triggered?

What dos CMP mean?

This is how to do it:
https://www.youtube.com/watch?v=8TyTNrlxXgk

@FocForextz You need to do this:

@Hits You can do it this way in the 'on trade'. In this example, i did it for buys only:

https://fxdreema.com/shared/cmYiDfsQc

However, jstap is right. Almost no broker will allow you to do that close to the open price.

@MeHrAn_HmGi You can find a custom indicator (if it exists) doing what you need and then import it into your fxDreema account.

You can also try ambrogio's suggestion, but you'll need some programming help too, as yo can see.

@fana-tumi What's the point of closing buy trades before opening them at the end of a bullish candlestick?

@Cindi-operation Do you mean creating one for your bot?

Do you mean it works on demo but not on live?

Apparently, your current configuration is correct. Every time current price is at least at the distance set on 'Trailing stop in pips' constant from SL, then the SL will be moved the distance you selected on 'Trailing stop in pips' constant. Isn't that what you want?

The most efficient way is by using a custom indicator doing that. You can build a custom loop on fxDreema searching for that info, but that would make the bot FAR more inefficient and slow.

@MigSornrakrit Those blocks work correctly. The issue must be somewhere in the logic.

You're welcome!