Your english is bad 
Here is something about these pink blocks: https://fxdreema.com/demo/mt4-loop-how-it-works When you use pink block, put some "For each..." block above. Otherwise the result is unexpected.
Whatever you are trying to do, I don't think that you really need to use Group numbers
In block 29 I can see that "Pips away" is 0. I don't get the idea here at all
Both: if the end time is empty field (which means the current time)
Closed trades: if the end time is something else
The other way is something like this: http://prntscr.com/btfyh3
Ok. I don't see any payment, but blockchain.info is such a buggy shit, so I'm gonna remove the Blockchain option. By the way, can you give me any details of this payment?
I think that "Betting: Custom sequence" can be used instead
Well, there is one input field for extra stuff - http://prntscr.com/btflb4
In this field you can write custom conditions using Order...() functions. If the trade does not match the condition, it will be excluded. I used StringToTime(), but everything that returns "datetime" values can be used instead
Yes, boolean is true/false, which is like 1/0
Use "int" data type for whole numbers
Note that the "Set..." block sets the timeframe, but only for it's own group of blocks.
I'm nost sure about these x> and x< that you are using... why crossovers. Better use < and >
If you try to put an order at the same price where it's currently placed, then nothing should happen anyway, so you don't have to ask.
I think that your EA is overcomplicated, because it has many similar groups of blocks. Anyway, now the problem is that the real names of the objects are not exactly what you want, so try with these settings: http://prntscr.com/btfe8w
Check profit (period of time) - this block collects the total amount of profits from the existing trades. It doesn't care what Equity or Balance is. The block does not know what was Equity at 01:00 am.
(Condition) => Market properties => Highest Price (or Lowest Price). Timeframe is optional there.
I don't remember how all blocks work all the time, there are maybe over 100 blocks, not to mention how many functions This is the code of "Time Bomb Up"
static double levl_last=0;
static datetime time_last=0;
double levl_diff;
datetime time_diff;
bool reset=false;
bool next=false;
datetime time_now = TimeCurrent();
double levl_now = SymbolAsk(SYMBOL);
if (levl_last>0) {
levl_diff = toPips(levl_now-levl_last);
time_diff = time_now-time_last;
if (levl_diff >= PipsInTime && time_diff <= TimeToWait)
{
if (levl_now > levl_last /* raises up */) {next=true;}
reset=true;
}
if (time_diff >= TimeToWait) {reset=true;}
}
else {reset=true;}
if (reset==true) {
levl_last = levl_now;
time_last = time_now;
}
if (next==true) {~next~} else {~inext~}
Even I need some time to refresh my memory for how this works. The idea was to detect if the price moved at least X pips for Y seconds. I think that the block measures the pips movement in periods of time. Like... for Y seconds it waits for the price to move with X seconds. Then again with the following Y seconds. I guess this is not the best method, but I don't think that this leads to such a big difference in brokers.
In 14 and 22, will it work if you use < and >
Block 32 like that... check this one: https://fxdreema.com/demo/mt4-loop-how-it-works
____This EA doesn't even export. Better don't use these checkboxes when you have Constants in the input field. Constants are already input parameters, there is no need to make them input parameters twice
These are the blocks for modifying pending orders. I don't know other blocks for that now that I'm thinking[/quote:13uvvn3w]
Yes, Yes, Ive had numbers in there before I shared it with you and forgot to uncheck it. It should export now. The constants are there to replace the numbers and define the grid size, respectively levels. Could these constants also be used as the level to which the pending order would be "slid" ? Or should I make them as variables? Also, in the slide order block, what is the "Positive direction for SELL" for? And why would I include "slide with pips" if I have a specific level to which I want it to move. I dont know how many pips will the pending order be deviated, and wether above or below the level because slippage is unpredictable :P[/quote:13uvvn3w]
if you have specific level, then use the "Custom (price level)" option.
I think you don't need to touch the direction option, and if you use price level it will probably have no effect anyway. This option is only for Sells.
Variables are... variables. They can be modified and everything. Use Constants only if you want them to appear in the input parameters and don't try to modify them.
This EA doesn't even export. Better don't use these checkboxes when you have Constants in the input field. Constants are already input parameters, there is no need to make them input parameters twice
These are the blocks for modifying pending orders. I don't know other blocks for that now that I'm thinking
But this is the block who can modify the position of pending orders You set the open price and orders should be moved at that price. Maybe the block should be named "modify pending order", but "slide order" works for me
The other block who can move pending orders is Trailing pending orders.
What if you backtest on Daily and you don't use block 1. If it's the same.. well, maybe at the time the conditions were true. If you want to see everything at this particular moment when the Sell is created, you can put "Terminate" immediately after the sell block and the EA will stop there. Or use "Delay" (but edit its settings so it can pause the EA while backtesting) and in Visual mode you can see exactly what is going on at the moment
__https://fxdreema.com/shared/k88FEQhwb[/quote:f007s84s]
If this works, I would add some "Once per..." block above. Yes, depending on the first 2 options in each "Draw..." block the number of objects can be controlled, but if you don't need new objects all the time, it's better to run these blocks only when needed.