Posts made by fxDreema

It is not a scam. The sad truth is that most of the time I'm lazy to look at people's questions and often I'm late with days. I'm talking about the forum, forum messages, emails... everywhere

About Bitcoin payments, I don't have system to automatically approve the payments... yet... I'm working on that. To see when someone paid I rely on a message from Electrum, but if for some reason I restart my PC, then I can forget to open the program and I'm not notified in time. Now I think I can just use some mobile wallet But in any case, I'm secretly giving more days for Bitcoin people, so even if I'm late with day or two, I compensate that.

I think I fixed it

Here is what I did. First, I used this custom indicator - https://www.mql5.com/en/code/7982 It works like the one in MetaTrader, but it is a custom indicator. Why? Because only for custom indicators in "More settings" there are extra settings.

https://fxdreema.com/shared/EqWKTmPod

Small problem is that in all Condition blocks my "My settings" are closed, which is because I use the current Symbol and Period settings... and "My settings" stays open if one of these is something different.

In block 1 I'm detecting that the newest fractal is Up (red dot above the chart):

Block 2 is to limit the signal to 1 per bar.

In block 3 I want to know if the newest Up fractal is < than the previous Up fractal. See that I'm looking for "Value by Visible ID", where Visible ID is the relative number of the fractal on the chart - 0 is the latest one, 1 is the previous:

In block 4 I check whether the position relative to the current candle of the previous Up (red) fractal is bigger than the position of the latest Down (blue) fractal. Or in other words, whether the previous red dot is left of the latest blue dot:

In block 5 I check whether the previous blue dot is more left than the previous red dot. Because it looks that the indicator can place two consecutive Up arrows, or Down arrows.

if you really want to have inputs, try Constants - https://fxdreema.com/tutorial/builder/constants-and-variables

Under "on Trade" better don't put that Buy block above the event-filter purple blocks. Like that you would see a new trade every time some trade event happens...even the creation of the buy trade itself... the chance is that you now have endless loop of buying trades.

First of all, for the EA to work with manually created trades, do this:

To set SL/TP on a newly created trade, you can use the "on Trade" event, but with something like Trade created -> Modify stops

It's similat to detect when TP or SL is hit - with those "Trade closed" blocks. Open their parameters and you will see options. You can detect the type (buy or sell) also in "Trade closed". "For each Closed Trade" are not needed.

I think this is a bug when this check is used:

And I see you checked almost all parameters... there is no real need to do that. These are if you want to make some quick optimization and you need few parameters to be input parameters of the EA. I know that some people are checking all of those, but I don't know why, it's not mandatory. Maybe they want to try different parameters in MetaTrader, but I there is a better idea. What I personally do is to change the parameters in the project itself and export a new EA every time. This plugin helps - https://chrome.google.com/webstore/detail/fxdreema-download-files/lnlppnklledgeaafojedgemkdhjdgdkp

I also don't understand the question. "Draw arrow" is a block who can print an arrow on the chart and it has nothing to do with Buy and Sell blocks.

I would ask for the age of the last trade, something like that:

This will also work if you restart MetaTrader, because no temporary variables are used.

Also this block "Check profit (period of time)" can be used I think. The idea is that you can define certain period of time and ask for the profit... to be 0 I guess.

Can you make a simple example that shows the problem? I can see your latest project, but it is big and also Buy and Sell blocks are disabled

When I use Google Translate, it says that you want to manually close a trade with its number. But what number, the ticket number? And manually... you mean using your mouse in MetaTrader? I don't understand the question, because everybody know how to close a trade manually.

What is this, you want to work with RSI and MA, or have MA over RSI, or RSI over MA? By the way, I don't know how to put MA over another indicator. I know that this is possible in the terminal, but I don't know how to do it in the EA

To make things simple, don't make hedging strategies. As I said so many times, these strategies only make things complicated and it seems that this topic is a proof of that. The whole idea of trading is to make one number bigger - the money you have. There is nothing magical in using opposite trade instead of SL. So it's better to just close the trade and continue with the real strategy.

So the red line is a false break, because the candle closed below the line. And the blue line is a true break, because it closed above the line. It sounds to me that you want to check whether Candle Close is above the line, but after the candle closes... which makes it candle 1.

It should be possible. In any case, if something doesn't happen as expected, look at the logs for errors. Also note that the block will take the input value and turn it into the nearest possible value, because you can't open any lot size, there is minimum, maximum and lot step.

The type of the variable should be "double".

But I see your projects and I can see that now you are setting this value in the Init section... I don't think it can be very dynamic that way.

Are you woman?

Try this:

I can see your project and I see that you have 2 Condition block in a row, both of which have x> inside. The problem is that x> detects a crossover that happens on the given candle, but before of after that candle you cannot find the same crossover. With your conditions you are saying that you want 2 separate crossovers (one with MA, one with Awesome Oscillator) to be true at the same candle. This could happen sometimes I guess, but I think that you don't want that.

So, try with one crossover. Change the other with > or >=. The thing is that if now line A is > than line B, then for sure line A crossed line B somewhere in the past.

Also I don't like where you placed the blue blocks - break even and trailing stop. Take a look at this example: https://fxdreema.com/demo/mt4-wrong-closing-rule
Also, only one of these blocks can work for both, buys and sells. So in short, disconnect block 6 from block 3 and remove blocks 8 and 9

The Trade event fires when there is some trade... event. Like a new trade created, deleted or modified. So the blocks under "on Trade" can run on any of these occasions. But you normally want to detect what exactly happened and that's why those purple blocks (like Trade closed) are used, so you can filter the particular trade event that you want. And of course, these blocks should be located at the top.

Also instead of Numeric -> Value -> OrderLots() you can use that:

I think you want to add to volume on loss, here is an example - https://fxdreema.com/demo/mt4-loop-add-to-volume-on-loss

It should work in the same way. If you find a difference, show me small example of how you draw it and I will compare that in MT4 and MT5