Complete running EA? Well here's my 500 best ones, that I have decided to save: 
I understand the admin, too, he probably wants something else for his life than just giving 24/7 technical support for years.
In my opinion, if you really need your projects pre-chewed and spoon-fed for you, you lack the skill and passion required to succeed in the first place. I'm sorry.
Use variables to store any information, with the "modify variables" block.
Although you need some logic to reset the data and restrict its process, you probably dont want replace the data on every bar?
@sidmcfarland yeah, maybe that is the bug inside the cross operator: it forgets to check the = case, just like I did
https://fxdreema.com/shared/ZCoTSeTDb
The plan is to count seconds in the On Timer tab. You must set the onTimer period to 1 second from the options -> project options.
Now that we have the seconds counting, when bull candle appears, set the count to 0 -> now the variable can increase to 10, and we have our 10 seconds delay -> buy!
https://fxdreema.com/help/working-with/constants-and-variables
Here's some info about constants and variables.
You can create your variables to the variable list, which is on the left in builder, above the search box.
Just create some system with "modify variables" block, test it around, you will (eventually) see how they work 
You can replace nearly any value with a variable or constant, by right-clicking the number
https://fxdreema.com/shared/dCBq6vAYc
As a test, here's an EA which draws 3 vertical lines to candles 1, 2 and 3.
However, due to using an array to name the objects (I think), the lines and names dont match, something goes wrong..
@fxDreema would you please look at this, or explain where I made an error
I revisited this project today, and noticed there were some stupid logical mistakes in the data manipulation..
Made a better one! In this dataset on EURUSD 2009-2019 M1 OHLC candles,
every 2nd one-minute candle is flipped upside down. All gaps are removed. As a result, the weekly chart starts quickly deviating from real EURUSD. Backtest reports 98% accuracy.
Because significant m1 candle moves don't occur in binary fashion (0,1,0,1...), the resulting price movement is pseudorandom.
Why use this? If my EA works well in both real EURUSD and this modified one, it is a bad signal - my EA probably just exploits some flaw in the backtester.
Import M1 OHLC bars: https://drive.google.com/open?id=1SuxvO2sjLPu0dVnwyVfauG2azC7r0cV8
@tantan thats the way to resolve things
@cpxiom I have the same methodology - money management shouldn't be the critical part, trading logic comes first!
set different group numbers for them, and then use "pending order exist" separately for each number
-> then you can close the other one.
or simplier, check if theres less than 2 pending orders -> delete pending orders
When viewing the generated code, the OnInit() function always contains the code shown below.
What is the purpose of it? It seems the code stops the initializing process if the init reason is a change of symbol or change of timeframe.
Well that seems appropriate for most cases, but why the else statement? Now the init is stopped in any case, right?
The problem: Lets say a project contains some graphical objects on the OnInit() tab, and some boolean constant input determines if those objects should be drawn or not.
If the user changes this boolean while the EA is running, the changes will not take effect because the OnInit() is stopped before those blocks are executed.
I often delete that else statement manually to make those objects inputs work properly, but I'd rather have this code changed for good.
Example: https://fxdreema.com/shared/pd9JF900c
Yes, the advertising might paint a bit too rosey picture, and yes there could be more extensive help material and tutorials. The tutorials-section is a great place to share knowledge, but unfortunately it seems to be flooded with help requests, which is not a place for them. Couple of moderators would be great for the forum.
Most of the questions are very basic stuff made by novices that have used the demo builder for 10 minutes. It is simply not worth it to provide costly support for such. It's a sad reality of a niche business like this. Hiring some support staff would potentially result in higher sales, but it is a huge risk as well.
Fxdreema projects, even fairly advanced ones, do not require coding knowledge. They do require a very high degree of logical thinking and patience. Making success in the world's most competitive markets can never be easy and everyone can't be winners, no matter how good the support is. That's just my opinion.
https://fxdreema.com/shared/bhDHS63Qc
Here's the principle
Maybe some buttons accidentally use the same name?
Why this happens: the strategy tester doesnt use accurate data. It will slightly overstate the probability of a TP hit. The effect is bigger when making more and quicker trades. There's nothing interesting here..
Going forward, I recommend building your strategy with "once per bar" block at the top, so the tester is more true to life.
So the signals happen at different price?
You need another variable, and store the price to that variable.
After the looping process, that variable should contain the last signal and you can continue with that
Slightly off topic: if you have more than 1000 blocks, I'm smelling some kind of repetition - you could probably decrease your project size by using arrays, loops and other higher level stuff
@seb-0 They are smooth because so many trades. In reality, trading costs would be so big that it's not even reasonable to expect such smoothness. Boils down to the sharpe ratio: profit/volatility. A curve like this is more reasonable:
