The left side is correct, the right is not. This is also explained here: https://fxdreema.com/demo/mt4-wrong-closing-rule

http://prntscr.com/8fglc2

Great! Thank you so much for looking into this. 😛

The idea of those counters is to count how many times the block runs. Optionally any counter can be reset, but the block to reset is normally located somewhere else, under another condition. You have the reset at the same place where the counter is, so the counter counts nothing.

But I will suggest to not use counters, because their memory is temporary. It's much better if you use only conditions who check things about the trades - their type, count, profit or something like this.

____Have you Set "MagicStart" = 0 ???[/quote:39pgb1f8]

no, ill try, thank u[/quote:39pgb1f8]

it works, have to set the magic start to 0
thank u Markre

Thanks
I went back to an older version. And redid most of the changes
So far so good
No stack overflow yet

Here: https://fxdreema.com/studio/
Not many people are using it, I also rewrote this thing as well and what was written for it before is not very accurate now. But if it works, you can create a new block (upper left), then write some code for it, save it and use it. Optionally input parameters can be defined for this block.

Here is how it looks for me now, if it helps: http://prntscr.com/8emuzf
~next~ ~inext~ and ~error~ are the keywords behind the 3 possible outputs (orange, yellow and gray) and they are replaced with function calls for the next blocks connected to this one.

Maybe you have the same EA put on 2 sharts? Otherwise I don't know what can be the problem, show me the project at least. I have no reports for such behaviour from "Buy now" or "Sell now", even for MT5.

We can, but then the result will be different. "Once per bar" can pass one time within a candle - from it's creation until it's closed. In the beginning, in the middle, in the end... If it's on top level, it passes on the first tick, because nothing is preventing it from that. If there is a condition, then it can pass later in the candle.

What, you are controlling millions? I don't believe that, but in any case if you ever decide to control big amounts of money, be sure that you have extra functions in your EA to protect the trades in weird situations. For example, if a the equity falls X% below the balance => terminate the EA. Or similar, it depends on the EA. Be extra careful.

F.E.
When I have "frozen" my buys, it is a way to follow the correct trend.

Well, under "on Tick" any blocks are doing what they do in the current moment. Conditions are checking things now. Of course, old data can be used, but it is used at the moment. If you know at which candle the crossover must happen, then you can detect it for this candle. Otherwise, of the crossover can be anywhere... well... why not just using > or <, because if line A crosses over line B at some moment or candle, then after this cross line A is > line B for sure.

When a block runs and does what it has to do, it's output becomes active, which immediately causes the next block to run. This will continue until some block of the chain does not pass or the chain ends. Then other groups of blocks come.

I will try that
should ahve thought of that, darn 😉

Yeah, Thats what I was looking for,

Thanks for your response, Its working in the I wanted it to.

in "Adjust" a value like +50% should work only because % is transformed to /100 by fxDreema while generating the output file. Otherwise 50% or 50/100 can't be used as a value for variables, because variables are defined before the EA even start to work.

This is expected, because Moving Average is read from the main chart and it's values there are different than the values of Trix. In case you wonder, currently MA placed on other indicator can't be read by "Condition"

Includes are possible, but via custom blocks.
Here https://fxdreema.com/studio/ there is this field down below http://prntscr.com/89y8i1 where certain things can be added - includes, imports or global variables. But if you try to export .ex4/.ex5 it will probably return an error, because the include file does not exists on the server.

The other thing can be made much easily, just put the block "Counter: Pass once" in "on Tick" and connect next blocks after it's second output.