Some blocks are designed to check something by looking at the existing trades. For example "No trade is running". This process is basically searching and filtering data, so these blocks also have filters to specify wich trades to work with (and skip others that you don't care). "Origin of trades" is just that place where you specify the group/market filters for this type of blocks.
Yes, because of group numbers. No trade exists now checks trades with group = 0, then you create a trade with different group number, and No trade exists just don't care about that.
Well, if you can separate trades by type (Buy, Sell), do it by type. Note that all pink blocks are universal, they work for buys and sells (whateve For each Trade is loading above).
Look at "Not more than N trades" option in "For each Trade". it depends, but I think you should set it to 1... maybe. And also take a look at the "once per trade/order" block, I think you have to put this one after the "pips away".
The comment for the Byt trade should be something like "Long trade" or whatever that is for a Buy trade. Well, this is optional.
I looks ok, but I can't be sure. Check it to see. Again, use "Draw arrow" to see where a block passes, use "Comment on chart" to print some data, or "Indicator tester" to print the history of some value. Use "Delay" to pause the EA (there are options also for backtesting, these require dll import) - you can pause when a new trade is created, so you can observe the situation at that moment very closely.
I think I don't understand this now. Otherwise for screenshots I use a program named Lightshot.
Now I have a mistake, I found one problem now and fixed it, but even with that it does not show difference. There is a difference if you use Candle ID = 1 for the indicator as well. Why? I think it's because of the way that indicator works. Here is a screenshot at the moment when a Sell position is placed, it looks that the condition passes when the buffer becomes some big value (aka EMPTY_VALUE constant):
http://prntscr.com/3d4hid
At this exact moment these conditions are right: Low[1] < Indicator[0] and Low[2] > Indicator[1]
Low[1] and Low[2] are almost the same. Indicator[0] becomes that big value, which makes it invisible, but mathematically it's a big value, much bigger than Low[1]. Low[2] is obviously above Indicator[1].
So, you can set Candle ID to 1 also for the indicator. Or use 2 conditions to detect that crossover. I think this crossover which is built in fxDreema is not very good and accurate, especially when Low or High is used.
https://fxdreema.com/shared/EBsIfwFVd
http://prntscr.com/3cx4zm
What this block do is to wait for the price to travel at some distance (let's say 0.0010) from the last round price, then it passes once and from that point it's all again - it waits for +0.0010 or -0.0010. But it does not pass at the exact round price! The chance to hit exact price is not big. So this block works with conditions like > and <. If for some reason the block missed some quites, it can give you a signal some pips away from the round price. If you run it on every tick it will be as accurate as possible.
I'm searching for someone who wants to build itself as a programmer, this is not a job offer 
Well, there are not many programmers here actually, but at least I can try.
The problem is, I wasn't updated fxDreema lately, especially the MQL4/MQL5 part, which is now pretty old and in my opinion - not really good and optimal. I mean, it can be better.
It's not only this, fxDreema has also a PHP/JS body that is not obvious, and this also needs care. I also want to build some other website (not related to Forex and trading), so I'm focused in PHP and web development now. I started to build my own PHP framework which then I can use in every website I have... or at least I will have more experience and hopefully I will make future things better, now I'm so tired of fixing same things again and again and working with bad written code.
Who said that programming is easy?
I still answer to all of the questions here, but I feel guilty of not moving fxDreema forward in last few months. So I wonder is there is someone who wants to take care of the MQL4/MQL5 code, functions, blocks, that kind of stuff?
Well, I can't offer a job, this website earns relly fine for the amount of active users that it have, but not even the half of a normal salary in a developed country. So I'm searching for some young enthusiast who wants to learn MQL4/MQL5 better and also wants to make his own EAs better. I can guarantee that it's a big advantage if you know how things work in a deeper level, and doing stuff for a framework like fxDreema is a very good exercise.
james, I think you have something wrong in block 2. OrdersTotal() returns the total number of trades and pending orders at the moment, nothing about lots. In the same time
Otherwise yes, "add to volume" can be used. But I will suggest to use some limits in "For each Trade", maybe using value 1 for "Not more than N trades". Then in "add to volume" there is an option "% of current trade volume", which I guess will be better than calculating it before using variables.
Don't look at the fxDreema/Data subfolder, these are only database files, not output files. .mq4 files are generated with .mq4 button, or .xml files from Projects menu. Well, I can also read the .fxdb file, but this does not matter, I can see the general problem, whish is the one I pointed above.
Again, no block waits until it passes. Your blocks 11, 18, 14 and 15 are executed rarely. Just break those connections from 8 and 10 and they will start working. In short, your closing rule does not work. Check the example again: https://fxdreema.com/demo/mt4-wrong-closing-rule
About the opening rule... I'm a little bit lazy to check it on MT4, but I can suggest what you can do in this situation. here we want to execute Buy now or Sell now, right? So you want to know if these blocks are executed at all. Just put "Draw arrow" block after 3, after 4, after 7... to understant if these blocks are working correctly and whether it's possible Buy now to be executed at all. If Buy now is executed but you have no trade on the chart, then look at the error messages, it's probably something wrong with SL or TP.
To know about indicators or any other numeric levels, use "indicator tester" block. It's one of my favorites
One way is to create multiple pending orders at some distance from each other. They are also executed on the server, which is a good bonus, and they also support expiration. "Buy pending orders in grid" or "Sell pending orders in grid" is to do that.
Otherwise you have to spy the last trade. Something like this: https://fxdreema.com/shared/HdVlWXpKc
There is a block named "Round numbers detector" which passes **once ** when it reach new level. The orange output on upper level and the yellow output on lower level. This is suitable for trades.
Otherwise in theory this can be done with pending orders, but I still didn't make it able to calculate exaxt round numbers But for grid which is starting from the current price check those blocks for pending orders in grid.
Damn these shared projects are broken again 
Nevermind...
Just downloaded the EA from your profile and tried it, I got bunch of errors like...
2014.04.24 01:52:13.773 2014.02.12 00:00:06 Error: Invalid SL requested (179769313486231570000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000.00000 for Ask price 1.36387)
I don't know there are so many 0, but this number is most probably from a buffer which is not active (visible) at the moment. Which probably means that the wrong buffer is selected.
Then I saw blocks parameters and I found something weird: http://prntscr.com/3ctma9
Parameters of Buy now and Sell now are exactly the same, even that "Short position" at the end. And because I'm seeing this for the first time, do you think it's a bug and parameters somehow copied from one block to another, or you manually did that?
Well, all the data from (on trade) is about that particular trade/order that caused that event. There is nowhere in blocks something to calculate group lots or group anything and give the result as a value. But the example I posted above does that... with 2 blocks and 2 variables
I was thinking before how to do something like this many times actually. One way is to add option in Condition to select group of trades, to filter them out and return... bunch of things. The other way is to have block like "Select group of trades" and then in Condition to have same options with, but not selecting and filtering trades there.
There is another issue - I prefer to keep projects with same blocks for MT4 and MT5, and functions like this are MT4 only.
The way I posted above (calculating everything in a loop) is the most universal and it's actually faster than what will be if this was inside Condition. Well, it requires some additional variables
By the way in this example you are missing something maybe important - to filter the event.
Well, Longs count is the count of Buy trades - how many Buy trades are there - 1, 2, 3, 4... This is not Lot size
You can monitor the profit/loss if you want, these blue blocks are for that. If you want to monitor the global account profit/loss, better use Condition -> Account -> Profit.
Trade statistics are probably fine, but when you use them they make the EA slow (when backtest) because some function that tracks statistics on every tick is enabled. In MetaTrader everything is fine to be used in live, but when it comes for backtesting... there is no room for much fancy things here, unfortunately
Anyway, I think you have to read this: viewtopic.php?p=5868#p5868
It's interesting how most of the people expect the EA structure to be. Now I'm starting to wonder if this way can actually work
It's all in the Projects menu. Load some .mq4 or .xml file previously generated with fxDreema.
Here is a way to get the sum of lots: https://fxdreema.com/shared/RFQWrZdjd
I user 2 variables for that. Notice how I used them in both pink blocks. "Modify Variables" or "Custom MQL4 code" can be used as well, but they take some space. You will see OrderLots(), this is the native MQL4 function that gets the lot size of the currently loaded trade.
So, block 1 loads each trade one after another, goes to block 2 as many times as many trades there are, and then at the end it goes to it's yellow output.
Ok, there is something you are missing here. I described it in this example: https://fxdreema.com/demo/mt4-wrong-closing-rule
In short, no block stuck and wait unlimited amount of time waiting for the right conditions to pass. Many people thing this is the way an EA should be build and they connect everything from the beginning to the end in that fashion, like "No trade => Condition to buy => Buy => Condition to close => Close". This is not the case here, check the link above
Break connections after Buy now and Sell now. "Once per tick" is not needed.
This worked before, but now with 600+ there was some changes with arrays. Fixed for the web version
You want to add/remove 30 pips to the ZigZag value? Then do this: http://prntscr.com/3clru0