@l-andorrĂ in your example there is no time window for resetting those variables. Even if you specify 10 minutes time window, it is not guaranteed that the EA receives a tick and the blocks are updated.
I would make a structure that makes sure the variables are actually reset every day, with 100% certainty.
@Remco-Rich sorry, I thought the lines are only 1 candle apart.
Compare MAs on candle IDs 1 and 6 then.
@Remco-Rich you get that result by comparing ID 1 and ID 2.
ID 1 crosses below ID 2
Technically you can use -5 shift in MA, but such an indicator doesnt have a current value. It has only history values.
@morad-dezhfard I would just start building, putting random blocks together and see what happens.
But there is also some documentation, youtube channels... @l-andorrĂ might also help you
@fxDreema I understand, both of your points.
I have just seen some "EA builders" offered by brokers, and they are always miles, light years behind fxdreema. This is the iPhone of EA industry lol
@fxDreema just go ahead with version 2, and finance it with some nice fat partnership contract with some major forex broker 
swing for the fences lol
The cock favicon probably would have to go though
With the current system, there is just no way for any input changes to take effect immediately. But its ok, I can live with that.
Some event tabs have those specific filters, maybe the OnInit could have similar blocks too...
@Qairos if you want to create some kind of time sequence, you should work with candle IDs rather than "once per bar" block.
Candle ID 0 means the current bar, 1 means last bar, 2 is the bar before that and so on
@l-andorrĂ can you isolate the problem into 2-3 blocks without any unnecessary parts in the example? Its difficult to follow the Spanish variables
All I can say that your EA seems to work during higher daily volatility. But volatility cannot be really forecasted, so I cant give any answers there.
@speedsk8r when you create a variable, usually it gets a default value of 0 unless you specify something else. The default value doesnt matter, the system will replace it anyway.
@speedsk8r well that depends on your project, what you are trying to accomplish...
But in general, you should connect everything on one chain so the proper order is ensured; you should first update your variable and then use it, not try to use a variable before it has a value.
The value will be stored in that variable so you can use it later.
@speedsk8r that is probably not the right block for you. The block gives you a yes/no answer, not a price level.
Its probably better for you to use modify variables block and then select highest/lowest price from market properties.
@speedsk8r if you want to take some chart value and store that value, a variable is always the way to go.
Maybe this helps
https://fxdreema.com/tutorial/builder/constants-and-variables
You change constants, computer changes variables.
Constants are constant from the computer's viewpoint
@gooseman time filter needs to come before once per bar.
