There is a block "Seconds filter", but the problem is that you may not receive ticks in the last 10 seconds, or even more => you will miss some signal at sme point. If you care of course.
What would work is to place blocks under "on Timer" and set the timer to 1 second. For that, click on the bench icon for the project's settings. But this will not work in the Tester, it doesn't run that "on Timer" event, because its ticks are not based on time.
Well, it depends how you define "each time the actual price moves x pips away, from
a moving average indicator". The price is moving up and down all the time => indicator values as well (mostly for the current candle) => multiple crossovers actually happen in short periods of time. That's why I put this Turnover parameter, which is the size of the path the price must travel backwards before the block decides to give you signal for the same crossover again.
Otherwise if you only want to check whether the current price is above some level, use "Condition". It also has some type of crossover that is a little bit different that this one. Here is more about it - https://fxdreema.com/demo/mt4-crossover-indicators
This block is not to be used this way. There is a pink block "once per trade/order" instead. But again and again, when you use pink blocks, put some "For each Trade" somewhere!
https://fxdreema.com/examples/#Loop-(For-each..
I think it's fixed already. But I always expect problems from MetaTrader 5 anyway 
.ex4 files can't be uploaded, their content is encrypted and only MetaTrader understands it. But you can manually define inputs and buffers. Here is more
https://fxdreema.com/help/-/you%20shoul ... indicators
https://fxdreema.com/help/-/working%20w ... indicators
Condition - Market Properties - Highest point (hours period)
I think I need to rename this to "Highest price"
Virtual stops are just one setting - use them or not. Then in the EA everything what works for hard stops should work with virtual stops, so there is no difference in the EA. Only if there is some bug somewhere, who knows. Give me some simple project where everything works with hard stops, but as soon as you enable virtual stops they don't work the same?
Currently there is no such way. Only if you make the strategy to work with trades in some way.
But how many orders do you open? Maybe you can make things to happen less frequently
You don't get what?
If you have 10 small boxes and you expect all of them to be empty exept one, then what can you do to find the one that is not empty? You will start to open them one after another. For each box you will do that:
... and if you find that the first box is empty, what will you do? You will throw it away and you will do the same with the second box. Then with the third... until you find what you are searching for.
We can name this process "For each Box". It's exactly the same with "For each Trade", but you are opening trades instead of boxes.
Search for iCustom in the code and look in it's attributes. Also look in the logs, there must be something there - indicator not found, indicator loaded, or something like that.
No, your example will not work for one very basic reason that most people don't understand. The Trailing Stop block is like a black box, it doesn't care if you put it in a "For each Trades" loop, it has it's own loop inside!
Here is an example of how to make Trailing Stop using pink blocks - https://fxdreema.com/demo/mt4-loop-trailing-stop In this case you can also check for the age of the trade. But to actually do what you want, to start trailing after the new candle... this will require more stuff to be added and it's probably not a better idea anyway. What can be done is probably to compare the Time of the current candle with the OpenTime of the trade, but not directly. OpenTime will be used only to get the Time of the candle where the trade is created. Similar to this:
http://prntscr.com/afgso9
http://i.imgur.com/nB31lXQ.png
... but in this case the accepted value for the time is "Time stamp", which is a string value in format such as "00:00" or "12:53" or something like this. The OpenTime is in different format that is numeric, like here - http://www.epochconverter.com/. In other words, there is no easy to use way to convert OpenTime of a trade to the Time of the candle where the trade is created
I think the minimum value for most brokers was 10 minutes
Please, take a look at this example again and find the difference in "Comment" - https://fxdreema.com/demo/mt4-variables
SL (and/or TP) is sent to the server as a price value, absolute value. The Open Price (let's call it OP) is also sent, which is Ask for Buys and Bid for Sells, but it doesn't matter, because the broker may decide to open the position at a different price => this is slippage, deviation, or call it how you want. As a result OP can be different than the requested one, but SL and TP are gonna be the same as the requested, or there will not be position at all.
So I think that this happens. SL is calculated correctly with the current Ask/Bid price that is available at the moment. But while you send that position the price is moving.... and then on the server the trade is opened at a different price. SL/TP is again, the same as requested. As a result you have shorter SL and longer TP or longer SL and shorter TP.
I can't help for these slippages. This is what it is - you are telling the server to open the position at X price, but then it decides to open it in some other price. Even if in fxDreema SL/TP are defined as "Fixed pips", they are still sent as absolute values, they are not relative to OP.
Here is something I found:
https://forum.mql4.com/62441#946057
so, for Market execution (ECN) the rule is that the position is opened at the first market price available. For Instant execution you can specify maximum slippage, but I'm not sure that such brokers exists anymore
Try with "BUY" instead of BUY
I guess there are issues when many variables are used and I will eventually do something about this, but I will recommend to try to not use so many variables. Yes, sometimes they are good way to do something easier, but the idea of the EA builder is not to become second MetaEditor. Even when you code in any programming language, it's not a good idea to have many global variables.
Otherwise in the Variables list, when you hover with the mouse over one of them, the blocks where this Variable is used is glowing like this - http://prntscr.com/afgbpy
By the way, in this particular project I like how you initially put the values from each indicator in a Variable, so then you don't need to select the same indicator over and over again in the blocks.
In MT4 trades are closed by one function called OrderClose(). The same function is used to partially close a trade, because one of it's attributes is "lots". When a trade is closed partially, what happens is that new one is actually created. That new trade has new ticket number, but some of its parameters are the same as those in the original trade. So there is a way to detect that this new trade is a child, but otherwise you can't recognize it juts by looking at it. Sorry, I can't change that behaviour, this is how MT4 works.
The only other function that can close something is OrderCloseBy(), but again, what this function does is to combine 2 trades into 1. It accepts two different ticket numbers from two trades opposite to each other. This is not the same as having 1 trade and partially close it. OrderCloseBy() does not work for only 1 trade. And even if you have multiple trades, 2 of them must be specified.
I don't expect problems in blocks when working with custom indicators. But you must understand how they work. Here is more about the indicators:
https://fxdreema.com/help/-/you%20shoul ... indicators
https://fxdreema.com/help/-/working%20w ... indicators
I renamed "Indicator tester" to "Plot". I don't know, these days I will decide what will be the last name for this block.
The local version is older than 6 months. The last time I received reports for bugs was... I don't even remember