You say "my direction" - is this the profitable direction or when you lose? 
Because normally people double the lot size when they lose, which is probably not "their direction" :))
By the way there is some example for creating new trade on every 10 pips - https://fxdreema.com/demo/mt4-loop-add-to-volume-on-loss - it does that on loss, but I don't know what is your "my direction".
To allow the EA to work with your manual trades, set this to 0:
I was playing with this block a little bit (locally on my own PC) and I was able to detect and remove weekdays. But it is interesting situation if for example someone wants to detect age of 1 month. 1 month sounds like 30 days, but if weekdays are removed, the actual workdays are 20 and something.
Also, if I do that for this block, I think I should do that for other blocks, for the expiration of pending orders. I mean, everywhere where there is expiration, I think I should exclude all weekdays and work only with workdays.
Bars count.... In my MT4 I actually have candles recorded for Sundays, not always. Take a look:
22 July this year is Sunday and those 3 candles (M15 timeframe) are recorder for 22 July. I wonder why I have more that 3 candles in History Center, but anyway:
I want to say, I'm not sure how accurate will be if you use bars count. And when you backtest, sometimes you have missing candles in random time periods.
Can you make some simple project for example, so I can see what are you doing, because I don't really understand what you want to explain here
You can also create MQL5 project, which can be the same. You can copy block between projects.
Here the question is how to calculate at which candle that cross happened. Here is some idea: https://fxdreema.com/shared/eHWR6SX5d
But what do you mean by "price crosses the ma21" - it matters. Because in the history of prices you have 4 prices for each candle and these values.
The idea in this example is that I have one variable that I set with value 0 before the calculation, then I check whether the Condition is true for candle 0, and if it's not, I increment its value and run Condition with the updated value... as a result Condition runs one or more times, until it passes. After that the value of the variable will have some value - the number of times that Condition passed minus 1, which is the same as the last CandleID used in Condition.
I also don't really know how to use iMAOnArray(). I will suggest to search for some indicator that does that
I don't know. I mean, I can check what logic I used when text ID is used, but it doesn't matter, because I can change it eventually. Lower numbers run first, but when the ID is a text... which should run first? Everyone will have different opinion. But block 362 passes every time, so you can just place it before or after first_set_only
I think you can use the difference between TP and SL, because that difference represents 200% and half of it is 100%. Any % value can be easily calculated and Open Price is not used. But when you move SL, there will be new difference between TP and SL, so to prevent second SL move, you can place "once per trade/order".
Here is some idea: https://fxdreema.com/shared/wtuY2RjC
I load the last fibonacci object on the chart (because "Not more than..." in block 1 is set to 1). Then I make sure that the color of that object is not White. Then I put the pending order. Then I modify the color to White, to mark that object as used. The idea is to not create a new pending order over the same object in case the EA is restarted.
Interesting question. I don't know any way to get that "low of the first 4h candle" value in fxDreema, so I made this example with some calculations in it:
https://fxdreema.com/shared/qKEtPnO4e
I have a "double" (floating number) Variable called CandleCloseOnMonday4H, which I modify in block 3. As you can see, there are few calculations over there, and the result should be Low of that first 4h candle on the previous Monday. It doesn't work properly for the first 4 hours of Monday and that's why I put this Weekday filter block. Then I create 1 new pending order on every day of the week. Each pending order expires in 1 minute, so the chart can be clear. This is only to test how accurate the value is, here I don't care about the pending orders.
To shift the open price of the orders, use some value in the "Price offset" option in "Buy pending order".
I hope you can get an idea what I do in the formula. 86400 is the number of seconds in 1 day and I add .0 to this value when I want to use it as a "double" value, it's where I use this "/" operator. I think it can work without .0, but just in case...
FourOclockOnMonday - this is the time that is at 04:00 on the past Monday. After that I'm trying to calculate how many candles can fit in that time period between now (TimeCurrent()) and FourOclockOnMonday. Everything will be fine if on the chart you have all candles present. But if there is a missing candle for some reason, the result will be kinda fake. There is no chack for whether some candle is missing or not, it's pure math.
3600 is the number of seconds in 1 hour.
TimeDayOfWeek() returns value from 0 to 6, where 0 is Sunday, 1 is Monday and so on...
MathFloor() returns integer numeric value closest from below
MathCeil() returns integer numeric value closest from above
iLow() returns Low of particular candle
In MT there is some Trailing Stop option that you can set manually:
I actually never tested this option and I don't know how good it works In the EA... the EA is controlled by MetaTrader and when you remove the EA from the chart, it doesn't work anymore. But I guess you can make another EA that only does trailing stop.
Which of your projects is that?
I don't know how can you do that. "Once per bar" is made so that the EA can be backtested quickly, and MetaTrader "feeds" the EA with ticks - 1 per candle - but in H8 there is no candle at that time, and I don't know how can you tell MetaTrader to produce extra tick at 22:00. But why don't you try with another timeframe, maybe this can work somehow?
I don't really understand your question
I don't think that the type of one variable can change anything. After all, the EA that is generated contains many many variables with different types. It's true that the generated EA contains 100s and 1000s rows of code, while you could manually code the same strategy with so much less amount of code.
Not only that, but I know that sometimes the MQL code itself is slow for reasons that I don't know. I noticed many times before that the amount of code in a function can make it slow, even if 99% of that code never runs. I guess that when the code is compiled, it is not optimized very good and it's like the code in a function is parsed every time the function runs. I don't know if this is true, but it feels this way.
So again, the type of 2-3 variables will not make a change. And todays computers have so much RAM. Even with the 1000s rows of code that fxDreema produces, I think that there are not RAM problems. I personally have 32GB of RAM, only because of the amount of browsers that I use. MetaTrader is nothing compared to Chrome or Firefox in my opinion
There is a block that can send such notifications, "Phone Notification". Isn't this what you want?
It is different, you have something like "Formula results" in "Condition", and also in other blocks where you can use those options in "Condition".
In the web version I changed it a little bit, and "Formula" saves the result into a Variable, that needs to be created manually.
Interesting question. I might take a look at this problem, to exclude Sat and Sun somehow.
This probably comes from the demo account that I use for these examples. I have this extra account and I probably added this indicator somewhere in the past, so it appears there. But I never use "My Indicators" in the examples, simply because I don't expect people to have the indicators. I also can't add Renko, because this is also some extra EA or Indicator. And by the way, when you are making an EA for Renko, you simply put it over the offline chart and it should work. Your Renko EA or Indicator is something outside the EA.
I think that this example works fine for me: 
Blocks 6 and 16 doesn't work, but this is because you have to set Group to 1 for them as well, because you have it at 1 in the other blocks.