I think you are right. In the code I was counting the number of exceptions that happened, and only when their number is as specified (11) it passed. But it should be the opposite - to count the difference between 12 and 11 and wait for only 1 positive condition.
Try it now.
I think I fixed it, but better save the values of this one. The problem was... well, hard to explain, let's say that there was no default value set, it only looked that "Any color" was selected because it's the first in the list.
Hey, I think there is some bug, but I will look at this tomorrow because now I reanny need to go to sleep [sleepy]
It does not wait for 11 candles, it loops in the oldest candles that currently exists. But I think you want to find that minimum value which is located somewhere in between the current value and the same value found somewhere in the past. For this task I think that I have no block, but if I think more about it and find some good name for this functionality, I can probably make some block.
The normal way is to calculate the next lot size by using lot sizes of existing trades. Or closed trades, but by "existing" I mean such that exists in the database of MT and also on the server. This is how for example Martingale works - it reads the lot size of the previous trade and doubles it, but it does not use variables to store the last lot size that was taken.
I tried your project and I don't have the indicators that you have, which means that I got many errors for missing indicators, but otherwise it does something. Maybe the problem is in some indicator? What else is written in the error log, line of code?
Well, in any case having less blocks is better, but I have seen projects with much more than 200 blocks and everything works.
This problem normally happens when a block is connected with itself
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.
Something like Cookies in browsers, I guess 
Maybe... MT does not have this by itself. It only have some Terminal Variables, but they are global for the all EAs, but it can write files otherwise.
For what are your variables used?
It doesn't look correct to me. You have this reset even before the counter. But what "market revrses" mean? And what should happen then with those Buy trades? Ok, it "resets for the opposite trades", but I don't see "Sell now" here or the opposite condition. But I don't think that counters are needed, they are very rarely needed.
This value was requested from another member before. It means that for X candles, the value is allowed to be out of the range. This value should be lower than the period or most often 0.
Ако не друго, то поне е по-шарено
The only block who can probably do that is this one: Indicator moves within limits http://prntscr.com/8e7qt4
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.
The Average... thing in the calculations should the mathematical average, which is the sum of all divided by their count. I don't know for iExposure, maybe it calculates some weighted values that depend on the type and the lotsize?
I don't have idea to make this thing possible, it just doesn't sound like something important to me. I think that this is something complex that will never be actually used (nobody asked for this before). It's more important for you to find why this EA is giving you too good results. This happens sometimes, but in these cases the EA is most probably exploiting some defect of the Tester
Here is it: https://fxdreema.com/shared/sHdT7r4Id
And the function is pretty simple and can be used everywhere, as you probably know - OrderComment(). But also you must have the correct trade loaded, which is done here in "For each Trade". After this block you can use OrderComment() somewhere if you want and if it's easier for you.