Best posts made by trader.philipps

@ambrogio cheers

@abubakar I don't think fxdreema was designed to do so. However, if you have the source code of the indicator, you might use custom mql blocks to adopt some of the indicator's logic. But I wouldn't recommand doing so.

As an alternative you might check the integrated indicators in order to fit to your requirements.

@ambrogio That's right, but I don't care so much for the block IDs inside a line - unless if I need something to run prior to another thing. I also start every block with a pass block so I can identify my starting blocks better.

@GeoFX I made some modifications as the indicator had some code that fxdreema doesn't like.

1. Using key variables names that fxdreema uses such as shift -> I added an "x" to each occurance
2. Cyrillic letters in code. Seems to be an issue - since I removed it all works fine.

0_1572658908781_twiggs_money_flow_org_smoothed_mtf_nmc_v3_fxdreema_fixed.mq4

@l-andorrà Hehe .. you are a rookie?

@reader1 Looks fine so far. The only thing I'd do different is to store the relevent prices and SL level in variables. As you let the code run once per tick, that may have a better performance (CPU usage for instance).

@reader1 Of course you're right. Was somehow thinking you'd check multiple times. However, check the conditions block. You twice use the ask price, what probably is a mistake. I just saw that you use that twice so I thought to look price up and store it in a variable. I guess one condition should have a bid price.

@ambrogio Yepp, that would do the trick for the following block. But be careful not to mix up things.

@rafaels919 The trade statistic block only works if you traded that trades and the losses occured. I f I understood you right, that's not what you want to do. You want to have fictive trades (not executed ones) and those have to produce 3 losses, right? Do those losses have to occur consecutively - which means 3 in a row and not loss, loss, win, loss ?!?

@l-andorrà what @roar tries to do is to calculate the pip value in the base currency. You might check this thread if there's an indicator doing the job for you. https://www.forexfactory.com/showthread.php?t=54800
I haven't tried any of those, but maybe that's what you need.
Once you know the pip value you can divide your risk money by your static lot size and then you know your SL in pips.

@rafaels919 Wow, I had a glitch in the virtual trade part that drove me nuts. However, it's fixed now. Project virtual_trades_count

0_1575223717794_virtual_trades_count.mq4

And that's how it looks during virtual trade:

What I didn't manage is to draw the virtual trades in the chart. The problem is that I stored the time the trade was opened in a variable. But I couldn't manage so far to set that date as the start for the trendline I want to draw. Maybe someone with more experience in chart object may have a look at that.

@fxamoneymaker Is that the previous candle you describe in your image?

@cpxiom Yes, you're right. Here is the advanced version. 0_1575333611385_BBandsStop.mq4

And the Project Link.

I was not sure about the trailing so I did both classic trading and BBands trailing to choose from.

@rafaels919 Here is the updated version.

For all others here....
DON'T USE THIS ON REAL ACCOUNT!! THE ENTRY CONDITIONS ARE SET TO GET MANY LOOSING TRADES!!

Changes:

1. Implemented Spread Betting Sequence
2. Tokenize Sequence in order to calculate max consecutive losses
3. Implemented Virtual Trades as trendlines in chart (thanks to @CPxiom for inspiring me). The issue was that I used datetime datatype in the trendline open instead of a string datatype)

Bugs fixed:

1. Fixed a glitch when changing from live to virtual trades. Cannot use Max Consequtive losses in combination with virtual trades.
2. Fixed an issue when virtual trade variables were cleared too early
3. Removed some debug stuff

0_1575349650831_virtual_trades_count.mq4

Link to project

And that's how it looks like now.

Here is an extract of a tester run in order to check lot sizes in correct order.

@reader1 That doesn't work lite that. TP must be known when you enter the trade. So you need to check the condition and close the trade by yourself seperately.

@rafaels919 As of last request, here is the latest version.

Changelog:

• Re- introduced max number of virtual trades configurable in EA settings for Phase 1

0_1575483529032_virtual_trades_count.mq4

project link

@Moon If you'd have used the search function of the forum, you would have easily found this thread.

@zackry I haven't work with terminal variables in fxdreema, but have some experience with them.

As long as your EA does not check the terminal variables, it will not do nothing. Also you might need to be careful with them as they survive a MT4 Terminal restart for instance.

@zackry Besides writing to files what is even more ugly or having some Windows DLLs to communicate between charts (which seems to be a bit oversized) I think the terminal variables are the right way to use.

@zackry That's what the forum is for.