@xyon126 Creo que me cuesta más entenderlo por culpa de la edad, ja, ja. Veamos, cuando dices velas amarillas quieres decir bajistas, y las azules son alcistas. ¿Es correcto?
En cuanto a contar las velas, necesitarás crear una variable numérica que añada +1 a su valor a medida que se van creando velas nuevas.
@darrow Ok. This is more clear now. So if I understand it corectly you need to modify both buy stop and SL levels every tiem a new candle is complete. Right?
About limiting how many changes are accepted, you will have to create a counter variable and add plus 1 to it every time a modification is done. I guess you are not using variables often. Rught? 
@len-1 Both mean the same. If that crossing ot new top happen at any moment within that candle period, the condition will be true. Beware, however, that the condition can be tru more than one within the period. I mean that there can be more than one corssing or more than one new top and the consition block will not distinguish how many times it happened.
@osamaababneh You need to import your custom indocator to your fxDreema account first. I strongly recommend you to read these threads:
https://fxdreema.com/forum/topic/4208/tutorial-06-my-indicators-in-fxdreema
https://fxdreema.com/forum/topic/9105/tutorial-working-with-ex4-ex5-indicator-file
@len-1 As I said you then, working with negative shift values is tricky in fxDreema. I'm afraid I do not understand what you mean by 'using the shift as the leading moving average'.
@yoloyacht Can you please share your project?
@floridabrazil That EA cannot work because theare no trades anywhere. The 'on trade' tab works obkly if there is at least one open trade.
@doctorninja Well, I always recommend to use custom indicators doing as much work as possible. That allows you to focus on the strategy itself. I cannot recommend you a specific one right now doing what you need.
On the other hand the best way to share a project is by doing this:
@len-1 Yes, because it is a Constant, not a variable.
@ramimoujaes Your take profut is too short. I'm not dure your broker will accept it.
@jay_c Can you please upload an image showing that?
@an1dres Weird. Can you please upload a screenshot of the error?
@aleeee You'll never be able to get the exact value of an intersection. A trader can see it on screen but from a programming point of view they are non existent. The closes you can get is the previous and the later MA's candle value for each of them.
@jay_c I guess it is possible, but I'm afraid this is my weakest point in fxDreema. Do you mean a 'moving' rectangle as new candles are formed?
@ontrade Ok. Are you using a custom indocator to get that value? If so, can you please share it here?
@xyon126 Entonces, si lo entoendo correctamente, cierras la operación cuando las velas ID1, ID 2, ID 3 e ID 4 tienen su máximo (high) por debajo del nivel del bid. No importa entonces dónde está el máximo de la ID 0. ¿Es correcto?
@darrow The first problem I see is that MA crossing will never be really confirmed until a new candle is created. That means your Buy stop and Stop Loss proces will not be available until an additional candle is closed. Is that what you want?
@axmed69 The problem is those blocks turning on and off other block BELOW them. Try not to do that unless strictly necessary. Just move them away from their current positions and let the condition blocks to connect to each other.
@ramimoujaes You can select any value fo any of those parameters by creating a Constant and then inserting it into the appropriate place. Now on you questions:
For question 1:
There you can set the time at which the trade bill be automatically closed.
For question 2:
There you can set the amount of lots required to increase every new trade as your balance moves up or down.
For question 3:
I hope this helps.
@kriordan Interesting. Could you please shw a screenshot of that configuration?