Topics created by MIKEIKE

What did you most recently change?

Errors can happen when you enter your own code or put fancy stuff in the Adjust boxes.
fxD also has a glitch on variable and constant entry. If you hit certain punctuation keys by mistake they may not be echoed to the screen but are put into the output code anyway.

If nothing else works download the mql code and have Metatrader compile it. It will show the error and what line it's on. You should be able to figure it out from there.

Sometimes erasing the value of a constant, with a few extra taps of the Backspace key to remove any hidden characters, will fix it.

Good luck.

I think you are talking about these blocks:
0_1533231561103_1a866ee9-f614-4d89-8562-27ac98f38436-image.png

Even I forgot how I made it and I keep them only because there are there for a long time. No data escapes from them. Basically, long time ago I wanted to make blocks for everything, but not all of my ideas were good. Now I think that for such things custom indicators should be used - they are better optimized to do such calculations and they also print the information on the chart.

0_1532812213340_c36e43ac-11dd-4ff3-9cb3-d0503b28e62c-image.png There is a button

If you have indicator in a subfolder in MQL5/Indicators, then in fxDreema you can add the subfolder in the name field. If the indicator is named "indicator", then you can write "subfolder/indicator"

No, you don't need to manually add indicators on the chart. The EA is connecting with the indicators on its own, you can't see this process.

"Shortname too long" - if this comes from the indicator itself, then I guess you can't help much. I think that this is some property of the indicator itself and is located in its code, but you don't have that code anyway.

Just use that Timeframe option in "More settings", set it to Daily

But 40% of 200 pips is 80 pips anyway 😮

It's okay I figured that would be a bit over the top.

Well, you have "No trade" at the top and when the first trade is created this block will not pass until that trade is closed. Try what will happen if this one is removed

Is normal Trailing stop with it's default settings work, or the problem is because of the magic number?

jeansoleil, what you are asking for happens like this by default. Only if you change the Magic input parameter or set the blocks to work with manual trades, only then the EA could work with other trades

Where you can see (each trade), then this block does what it does to each trade independently. It gets the first trade - it does what it does, then it gets the second trade... until it checks all the trades available.

Where you can see (group of trades), it first calculates the average value of what is needed (like the open price) of all trades, then it modifies what it needs to be modified (like the SL values) for each one, one by one.

This block, like all the other blocks with the same (pink) color are designed to work only after some of the "For each...." blocks! You have it after Break even, so the result from it will be... who knows.

Trading model:

if Ask is X pips above the open price in case of Buy trade if Bid is X pips below the open price in case of Sell trade

Chart model:
-the same for Buy trade

if Bid is X pips ABOVE the open price in case of Sell trade
So here you don't care whether the trade is Buy or Sell. If Pips away is positive value, then it will detect when the current price goes X pips above the open price, and if negative value - below.

Double-sided model:

If the price goes X pips away from the open price above or below, for Buy or for Sell

Yes, look at the Trailing Start option... this is basically the level beyond which the trailing stop is working, below that level it the same as you don't have trailing stop at all. And with this, maybe the break even is not needed.

😄 😄 😄 😄 THANKS! You Throw Some crumbs of info, can be frustrating, but it always helps!!!

The file directory was incorrect and it was pulling the wrong .ex file!!!!!! Solved And Working!!!!

THANK YOU!!!!

Now study this: https://fxdreema.com/demo/mt4-wrong-closing-rule

many people think that some block should wait for some time and then it will pass and go to the next block. Not true, this does not happen at all. What really happens is that blocks under "on Tick" become active on every tick, again and again, and again, and again - the very same blocks. Well, those on top level at least.

There is no block that will wait 15 candles for something. Blocks work NOW, at the moment. If it's some condition - it works now. If you want to check the current indicator values, fine. If you want to check past indicator values - also fine. Checking future indicator values... no way.

And because so many people think the wrong way, which is in fact the most intuitive way, I thought that I can make it that way... but then I realized that this is not a good idea for some reasons.

So again, you can check anything using the "Condition" block NOW, but the "Condition" block will not wait for the comparison inside to happen. The only block that can wait for some time (but not waiting for something to happen) is called "Delay".

What you can do is to check for crossover NOW and also check for the other indicator 15 candles in the past. Just thing in the opposite way.

Why is that better? Because MetaTrader already have history data that can be accessed. Also because saying that you want to check something in the future requires the use of some variables - the problem here is that if you restart the EA those variables will be gone, they are not persistent. But if you check the past data, in case you restart the EA, that data will still be there and the same, so the EA will continue working as before.

Here is some basic information of how indicators work: https://fxdreema.com/documentation/gett ... indicators
And here is some basic information of how to manually add custom indicators when you don't have .mqX file: https://fxdreema.com/documentation/proj ... indicators

What matters is the number of input parameters - they must be right. Also their data types - they can be only "string" and "double", but it's better if they are also right. Their names can be different, but it's better if they are the same. Their order matters, it must be the same. And the buffers count matters... buffer names don't.

But if your indicator does not use any buffers to send data to the EA, then you can only use the object that it draws. Which is another story 🙂

"Indicator appear" should detect only times when certain buffer goes from 0 to positive/negative value or from EMPTY_VALUE to positive/negative value.
Otherwise you can limit trades by time. For example using "Once per bar". After this block everything can happen 1 time per bar, as it's name says.

Use "Indicator tester" block to check if the indicator buffers can be used. If they can... use them. The "Condition" block is working fine.

Only pink blocks and the pink category in "Condition" needs "For each Trade". Break even point does not need it at all, as it has the loop closed inside.

I'm not sure about the meaning of the question, but to limit things in one bar - "Once per bar"

Thanks. One step ahead. Found That. But new issue regarding my new Stop Loss Post..... THANKS!!!