You probably need to put some settings here: http://prntscr.com/f408dx This is where you can say to the EA how much is 1 pips for each symbol or for each point (for all symbols with 0.0001 format for example)
But are you sure you want to modify SL for all 54 pais every time you create 1 trade in 1 pair?
If you uncheck this it will start to work: http://prntscr.com/f405mt
Maybe I can fix this somehow, but currently I'm redesigning the output code anyway
Pending order expiration is based on time, where do you see this "Pips"?
Every indicator is different, it depends 
Error messages? Give us more details of the problem.
There is a block to check consecutive losses. If the "wait X amount of time" is the hard thing to do, then try this block "Skip Ticks"
I think we wrote emails back then with okranoblues.
There is only a block that can detect round numbers, but it doesn't give you any values that can be used outside. I guess I need to add something in "Condition" block, but who knows when. Calculating round numbers may be actually easy, especially when the current price is used. In MT4 you can get the Ask/Bid price just by writing Ask or Bid, because they are predefined variables: https://docs.mql4.com/predefined
Here is some calculation:
MathCeil(Ask / gridsize) * gridsize
Let's imagine that Ask is 0.942 and you want to get the upper round number that is rounded to the second digit. You want "gridsize" to be 0.01. Then you have:
MathCeil(0.942 / 0.01) * 0.01
And the result is 0.95.
What is MathCeil()? You can see this function here: https://docs.mql4.com/math The function to be used for the lower side is MathFloor()
Well, I recommend to use those Bucket blocks to get the count. Statistics are more time consuming.
Interesting, I just wrote on another topic in the forum where someone else was reporting the same issue. I don't have any Apple device (I'm in Europe) and I don't know what exactly is the problem.
Do you have any error messages? Maybe they changed something in their compiler. On the server I prefer to use older compiler, because every new compiler that they produce is working even more slower.
Or... what if you download .mq4 file and then compile it. The .ex4 file should work of course. Then can you give me this .ex4 file produced on your machine and another .ex4 file of the same project that is downloaded from fxdreema that is not working?
I had some issues with the server and the website itself didn't worked for some hours, but when this happens you will probably not be able to do anything. If you have your output .ex4/.ex5 files successfully downloaded, then I expect the problem to be somewhere else.
If you still have problems with particular project, tell me the name of this project so I can look at it.
Chec this block called "Check profit (period of time)"
Renko charts should work the same as normal charts. The EA should detect offline chart and then get all the values that it needs. But if there is something that is not right, give me more information (and the EA/Indicator that produces the Renko chart), so I can check it.
If you think that block 16 is the problem, then try to write the name of that constant that is used in "Adjust" manually. Because this filed is a little bit specific and I'm not sure that the way you use the Constant there works as expected.
Anyway, you can always check when blocks pass - just place some "Draw Arrow" block after the block in question.
And also you can always check some value (of variable, indicator or anything else) - just use "Comment" or "Trace" block
The Trailing stop block needs to run on every tick (in most cases, this is not mandatory). Just placing the block somewhere does not guarantee that it will do the job continuously. When I first made this block, it was automatically working all the time. But then I decided that the person should be able to decide when to run this block by placing it under "Hours filter" or other blocks.
Blocks can have 1 or 2 outputs only. You probably ask for a block that could have multiple outputs, but they only have 1 or 2. Of course if you connect multiple Condition blocks one after another (each one connected after the yellow output of the previous one), you can do something like this. It will be if - else if - else if - else if...., but its similar
The first block asks for a Buy trade and because of that I don't expect anything to work on backtest. There is no Buy trade => there is no chance for this block to pass.
Otherwise I can suggest to put the trailing stop somewhere on top level, so it could run on every tick.
Probably, but I will suggest to put both MAs in Condition block and to use +5pips in the Adjust field on the MA 21 side. So then you have a condition that checks this: When MA 14 is bigger than MA 21 + 5 pips?
First you need to select the object and get the price. Some objects have 2 or even more prices, because they are made out of 2 or more points. So, it depends. But when you select the object properly, you can compare its price with some other value in Condition block, let's say with Ask price, or Candle Close. In Condition you can use the "Adjust" field for the distance.
Also, there is a block "Check distance"
I don't have your indicator. And I really prefer to test this on a project that contains only the most important blocks. This contains trailing stop, custom indicators...
But when something works on one side and doesn't work on the other, the first reason that pops in my mind is values in Condition block. If you have X < Y and you expect both values to be for example between 20 and 100, then everything will work fine if they are really between 20 and 100. But if X is an indicator, which could give you value of 0, then guess what... when X is 0 and Y is whatever number that is bigger than 0, then the Condition is right.
I don't like block 3. It passes when there is at least 1 Buy trade. But what is in the yellow output? It doesn't mean that it would pass only if there is at least 1 Sell trade. The yellow output is the opposite of the orange output. In this case, the orange output would pass if there is no Buy trade, but it doesn't matter how many Sell trades there are. So, i will suggest to use 2 blocks from these, one for Buy and one for Sell, if needed.
The Trailing stop block works with the current price (let's say Ask) and the current SL to decide when is the right time to modify SL. It looks at the difference between both levels all the time. Now, you want to modify SL at every 10 pips and to put SL at 50% of the difference between Ask and SL. You have absolute Step and relative Stop. You can try with this option "Multiple levels" for Trailing Stop, but the problem with this option is that you can define certain number of levels, it's not a formula that can work for infinite number of levels.
Again, the problem is that you need to somehow work with invisible grid of levels where each new level is exactly 10 pips above (or below) the previous one. But the Trailing stop block looks at the SL line to decide when to modify it again. You want the SL line to change like this:
This is the closest that was able to make: https://fxdreema.com/shared/MM7kc2SZb But because I use relative Step, the levels are not exactly 50, 60, 70, 80 and so on... But what is the chance to have more than 5-6 SL modifications, it's very low. I put some "Delay" block in "on Trade", so the EA will pause on each SL modification and you will be able to easily measure all the distances.
"double" is the data type for floating numbers. There is no type "numeric", I only use this word sometimes as a general, because I think that some people that does not know what is "double" will better understand when I'm talking about something that is numeric