I don't know, maybe you have negative value for the input parameter?
I tried this: https://fxdreema.com/shared/gc1FxAv8e
And here is the result: http://prntscr.com/9y04wq
As you can see, both of my trades were modified (at 25 pips, because its shorter for testing) and their SL set to 10 pips positive, and then they were closed by that SL, so their profit was 10 dollars.
Break even - this moves SL only once. Trailing stop - this moves SL many times.
Break even is like stripped version of Trailing stop and you can actually emulate break even behaviour with the Trailing stop block.
There are many options in Trailing stop. Maybe you want to just put some kind of delay and start trailing SL after few pips of profit are gained. For this, look at the "Start" option.
The wev version is just what it is, always the latest revision. There are no versions for it, it's just a website page that looks like desktop application. The desktop version has some build numbers, but my idea is that everyone should work with the latest thing available. I have only 1 head and I just can't think and support old versions.
When I do changes, I have some scripts that will automatically update the project you are loading to the latest state, if necessary. When I decide to remove some block, I only hide it and it still works, but a warning message appears for that project.
I can't find this block in any of your projects, so I can't tell what is wrong
Of course I know that Molanis exists and I was playing for a while with it before I started fxDreema, but I don't know its special features and I have no idea how they evolved in the last few years 
if the first trade needs to be special, you can easily make it special by giving it "Group" number. Then with "No trade" check if there is no trade with that Group number, which means that it was closed (or never created, but anyway), and after that do whatever you want.
Probably, but I would not recommend this. These days people are asking me more about multi-currency and multi-timeframe stuff and while there are two blocks that are somehow able to do something about it, I don't think it's a good idea to build EA that just does tons of calculations. The idea behind these blocks (named "Set .... for next blocks") is to reuse few other blocks (those connected after them) for few other currencies/timeframes, but it was never in my mind to make them ready for tons of calculations and I don't even know how fast they can do something like this.
I actually experimented with this long time ago. But this means that the size of the blocks will be sometimes huge and each one will be different in size. And probably one single block will resize if you change some settings. I always prefer to have all important information directly visible, but in this case... I don't know Maybe if we can select which parameter to set as visible. But another problem appears - very often the name of the parameter is very long even in the list of parameters.
Pending orders in grid - the idea here is to place multiple pending orders at once. You can set the distance between them, lot sizes and other things.
Bucket of... - this block does not create orders, it selects them, so then you can calculate few things out of the selected group of orders. Things like min, max or average lot size, sl, tp, profit...
I don't know FXChoice But I only ever had real accounts in 2 local brokers, so I can't tell if any other broker is good or bad.
Just extend that Tester window. It's there, but it's invisible at the moment.
The desktop version is old, this is from the web version and you should see it.
"Condition" does not give single signals!!! It only compares two values and depending on that comparison one of the outputs is active. And if this block runs on every tick, then that output will be active once on every tick while the comparison between both values is true.
There is a whole category of blocks designed to work with indicators. They are in the category called "Indicators". Look at them. Or put "Once per bar" after (or before, it depends) "Condition".
I have build 950 and it's ok for me. I don't know, check the symbol, history data, profile. You are the first one asking me why MetaTrader features are disabled
There are expiration settings. But note that for trades these work because of the EA - those trades will only be closed if the EA works, it's not like how it happens for pending orders.
The other way is of course to check the age of trades and close them, but this is what happens with the expiration settings.
And I decided that you have problems with this.
Not long time ago, someone asked me something for such type of broker here in the forum, but I think the problem was something else. I expect that "Close trades" will close the exsting trade, but if this doesn't work I will fix it.
https://fxdreema.com/shared/NderHfNib
"For each Trade" should be also used, but in this particular case I think we can live without it.
I don't like hedging strategies and I don't even want to think about them, so you can play with the rest. You can catch TP events in "on Trade" or in "on Tick" to check for the count of trades/orders and reach when the count is something meaningful. Let's say that 0 trades and 1 (or more) pending orders means that the orders must be deleted.
No. Such thing would require arrays for remembering the state for each frame, but in "Once per bar" there is only 1 memory value that works in general. It's not impossible for "Once per bar" to be modified, but as a result it will start to work slower and this is something I don't like. Unfortunately in MQL4/MQL5 there are no associative arrays to make things simpler and I don't know how to easily work in scenarios where associative arrays would work fine.
There is "Adjust" field to add "n" pips to some indicator in "Condition", but I'm not sure that it will work as expected when checking for crossover, because for crossover there are 2 checks and if you add 20 pips, 20 pips will also be added to the value of the indicator for the previous candle. But maybe this is what you want.
I have many stops modifications, it appears that Trailing stop is working fine for me: http://prntscr.com/9wgqlb