Posts made by roar

@svenw8
One more day, what you mean? To get tomorrow's values today?
You get readings from any history candle with the candle ID setting.

@geofx
Here's a tutorial,
https://fxdreema.com/tutorial/builder/constants-and-variables
BUT its a bit clunky, I have never used it lol.

Variable is basically a storage space, where you usually put a number that automatically changes according to your rules.
Their creation happens here:

Apply a variable to any input field by right-clicking it.
Generally variables can be altered in two ways: with the "modify variables" block, or the quick adjust window attached to each block.
Here's an example project where a variable keeps track of completed candles, and it resets when rsi >70.
Run a visual backtest to see the variable chaning in value.
https://fxdreema.com/shared/gmxHGco1d

The EA will not execute single blocks, so a pass is necessary

@alphaomega To get rid of the VolumePercent text, go through the drop-down (fixed, % of equity, % of balance, etc.) and uncheck the other settings.

In the long run, its better not to use those checkmarks at all. Use constants to change the values in mt4.
https://fxdreema.com/tutorial/builder/constants-and-variables

@alphaomega said in '1' Compilation errors with Mt4:

Am I doing this checking the correct way? Why does the value not change?

What value?

@alphaomega By "checking" I just meant fixing it. When I looked the .mq4, the volume was 0.1.1 which gave the error. Does it work now?

Check the volume in "buy now" block.

For the future, how to troubleshoot errors like this:

• download the .mq4 file
• try to compile it in your own metaeditor
• it gives the same error, and the line of code in question
• go to that line, scroll up a bit -> you'll see which fxdreema block is giving the error

@rafaels919 Ah, I see.
There's no simple fix, as far as I know. You could use a bunch of variables and custom coding to make your own betting system, which would be more flexible addressing different kind of closing methods (using the OnTrade tab, for instance).

However, I think that is too much hassle for zero benefit. I'd recommend staying away from betting systems, they don't really improve any trading strategy.

Its like polishing shit, you will never get gold no matter how hard you try

@khalids222 For the first problem: use the block "check type (last closed)".
I won't bother answering the second problem, because I just think that's going to the wrong direction. You shouldn't treat the market as a roulette table. Well, at least its good practise

@rafaels919 How do you count the loss? Backtest report?

If you want a purely technical solution, you could keep track of the trades closed with that block, and then subtract the value from total loss.

@geofx said in AND command block:

• block 2 appear once
• wait for the block 3 to pass
• !whilst! block 3(NRTR) is visible per each candle, wait for the block 5(Keltner price cross) to happen at least once
• trade

So in a nutshell, block 2 acts as a "trigger", and after the trigger has activated, the NRTR and keltner should pass simultaneously to open trade?

This trigger can be done via a variable, i.e. use values 1 and 0 as the on/off position.
Generally, if you want to create a sequence or anything else that requires a multi-candle process, variables are the key

Aand you can also simply use the name filtering in the loop block:

As you can see, I'm just guessing here lol

https://www.mql5.com/en/docs/strings/stringfind
You could use the string search function to filter strings with "x".
Or use substr function, get the first letter of the name, and make condition: substr(name, 1,1) == "x"
https://www.mql5.com/en/docs/strings/stringsubstr

A redneck like me would just use a unique color for x and y, though

Hi! I'm not an expert on this but I just can't keep my mouth shut lol.

You dont need the AND-block, and
you dont need the "wait to pass".

Also, I wouldnt use the "indicator is visible" and "indicator appear" blocks, they seem to behave somewhat unpredictable. If you can replace them with a simple condition block, for example, NRTR != 0 kinda means that the indicator is visible.

To further troubleshoot your custom indicators, you can put them into a comment block, and then use visual backtest to see what values they give on each candle.

@luisjunior1224 Just put in the number and the EA simulates the withdrawal (on every tick, if you dont restrict it).
I believe its based on this mql5 function:
https://www.mql5.com/en/docs/common/testerwithdrawal

here: https://fxdreema.com/shared/HGCY0hJ4dhttps://fxdreema.com/shared/HGCY0hJ4d

Theres no limit.

@mischa What you mean by "keeping track"?
You can directly read any single candle value, just change the candle ID setting.

You can literally "make the Williams to cross the MACD 0-line" by just scrolling with your mouse, or changing the scale setting. Its only graphical, you can't make an ea of that.

From your picture, you can estimate that the corresponding Williams level would be something like -70. Go ahead and make a condition: williams cross -70 level. If you then put the MACD to the same window, it will look like the william crosses the MACD 0-line. But when you scroll the chart, the level is suddenly -75, -65, -35, anything..