Condition (indicator > 0) => Close Trades
Indicator is visible => Close Trades
Any of these shoud work. But first make sure that you use the indicator with correct settings. "Indicator tester" can help. Normally you need to set Candle ID to 1 (or more) for arrow-based indicators
"on Trade" is an event that fires when something happens with some trade or order - open, close, modify. I think you just want to put blocks 8 and 7 under "on Tick". And you probably need something more, because MA10 can be > than MA20 and on the very next tick it can be the opposite, so you will end up with a trade closed immediately. "Once per bar" or something else can help, it depends. And it's totally different when Sell is used as well.
Well, this thing appears to work on backtest. Maybe the EA didn't worked at that time, I don't know, there are many reasons 
It looks that when Show_Filling is set to false, it's buffers are empty. Maybe their data comes from the filling material
Stochastic has totally different nature, it's values vary between 0 and 100. How can you compare the value from Candle Low, which is something like 1.2345, to other value that is somewhere between 0 and 100 
And you have 25 candles in these blocks. Note that the comparison between Candle Low and BB is for each candle individually. It's not like comparing a single Candle Low value with 25 values of BB. So you probably don't see Stochastic because the first block didn't passed, at least I can't see 25 lows below BB's low.
"Round numbers detector" is only looking at the price, it is not linked to any trade. I think I can add an option to never come back, once I understand it's messy code 
Or you want to do similar thing, but starting from the open price of some running trade and only while the trade is still running?
Well, in some sence BE locks the profit. What it does is to put SL somewhere once. Similar to Trailing stop, but it changes SL once. Because there is a setting to put SL at some distance from the Open Price (BEP offset mode), I think you can put SL at 50pips (from the open price) once when the trade is on profit bugger than 50pips. Just make sure that the offset value is smaller than the profit value.
Wide time filter -> Conditions -> Narrow time filter
Do you really need the first time filter? Why not like this: Time filter (~17:30) -> conditions and so on...
When you keep data in variables, also keep in mind that when you restart the EA it will be gone.
If stops are hard, then the broker is responsible to work with them correctly. I think that it's better this way. Otherwise... you know, errors happen out of nothing.
Which one of your projects is this?
Try this: https://fxdreema.com/shared/6f02Qbxie
24:00 does not look very good anyway. I can suggest to use "Relative to Start time" mode.
I found that I have this indicator already and it produces normal values other than 0 for me, even for the current candle 
http://prntscr.com/7o5ymr
This error is not included in the loops that I am thinking about. Can you give me an EA that produces this error?
Only indicators can create such a window, at least this is what I know. Indicators builder... I don't know when, I'm not even thinking about it and I don't know why, I guess I'm not a big fan of indicators and such thing will only add to the things I must support 
https://fxdreema.com/shared/bNXmeUAX
http://prntscr.com/7o5mis
Candle Low < Bollinger Low for ID's 1, 2, 3, 4 and 5
Well, this error comes frm the broker and I believe that it's description tells the reason. Where are some limits and when you are too close, modification can't happen. The EA will try to do it for few times anyway and it should quit trying after a while. If someone thinks that it's better to just skip this error or don't even try to do the modification, I can program it like this.
There is a block called "Once per bar", it does basically the same thing as in your example.
When you are not sure whether an indicator works or not, just put it in "Indicator tester" to see what it's buffers provide. If there are values different than 24XXXXXXXX, then it can be used. Otherwise you should try something else, for example changing Candle ID. Many indicators just work in some older candle and provide nothing for the current one.
Well, I made a plugin for Firefox and Chrome that opened access from the browser to the local filesystem and the whole procedure was basically the same as in the local version. I did it this way personally and I work on the local version only to check if things are working after I build it.
Because this plugin used an old technology called NPAPI, which was considered not too secure, they dumped it and now these plugins that I have created stopped working. But some days ago I wrote another plugin for Chrome that now uses 100% of the API provided by Chrome,here it is: https://chrome.google.com/webstore/deta ... mkdhjdgdkp
The only block that do something similar to this is "Indicator moves within limits". It check whether the buffer of the selected indicator is > and/or < from some other value, and it does that for N number of candles.