MetaEditor does that if there are no errors. If there are errors - .log file is created. If you want to learn MQL, go to "Dictionary" in MetaEditor or www.mql4.com and start trying. It requires at least a month to start doing things a little bit better.
Yes, I posted two sample files above. It's ok to write all the parameters, name the file as the name of the indicator and upload it to fxDreema. Also you have to put the number of buffers and optionally give them names. This is not so different as if there is an option to manually create list of parameters directly in fxDreema.
So what is it? Sorry, but "ea does not work" and "ea also doesn't work in backtest" does not really help.
You may wonder if fxDreema introduce this limit, but it's not. There is nowhere in the code something that tells "don't place stops if the requested pips are lower than X pips". You can always try some simple EA found in Internet, and similar EA made by fxDreema. Then, if you can put that SL/TP with the first EA and can't put it with fxDreema's EA, show me both, please.
By the way, we are talking for error 130, yes?
Well, yes, but with so much input parameters I really recommend to create a file and upload it 
There is no "minimum trailing stop" parameter from the broker. There is a broker parameter called "Stops level", but this parameter basically does not matter. My "Stops level" is shown as 0, but I can't put SL/TP closer than 0.0001 to the open price. In other words - there is no parameter that tells you how close you can put SL/TP, or if there is some - it can be not true.
EAs created by fxDreema uses MQL's OrderSend() function at the end, so if this native MQL function gives error... how can I help? Try virtual stops if you want.
string Se_Ex="----Indicator settings";
int SmallWave=5;
...
...
bool StrictWaves=false;
...
color BearWave=Tomato;
...
string SoundFile="alert.wav";
...
...
and so on...
"ab" are "string", and use " (double quotes) before and after the text.
"123" are "int" or "double" (if it is a float number).
the green icons are "bool" - true or false.
and colors are "color" and the name of the color is written as is.
What Windows do you use?
Windows UAC enabled? I can suggest to disable it. At least I don't have this problem on Windows 7 
There is a difference between pips and points. But nevermind, it's not important how many digits the broker use. If the point format set in fxDreema is 0.0001, then 5 pips are 0.00050, and if it is 0.00001, then 5 pips are 0.00005.
It's funny how 5-digit brokers advertise their spreads. They say "Our spread for EURUSD is 1 pip!", which does not mean that the spread is 0.00001 wide.
But you should have that spread meter on the lower left angle. For example, if it shows something like 2, use 5 pips, or if it shows 20 - use 50 pips.
When uploading an indicator to fxDreema, the .mq4 file is uploaded and then the information needed is read from it - external parameters, number of buffers, and in some case the names of those buffers. This information is stored to the database, and the .mq4 file is no longer needed. When used in a project, iCustom() is used.
Older .ex4 files actually contain external parameters names in clear text format. Now I just compiled some indicator with the newest MetaEditor, and there is no plain-text data inside the .ex4 file. In other words, .ex4 cannot be used to read this data from it, or at least I don't know how to crack this file.
And let's say that I can add an option to manually enter the input parameters. Can you do that? To choose the correct datatype for every input parameter?
Check the attachments. These are simple files containing only what is needed, and they can be uploaded. One of them contains also the name of the buffers, but this is optional because it can be edited in fxDreema.
I have it on the first tick. Even if I put the visual mode to pause (">>") a buy trade appears.
Right-click over the "Condition" block and hit "On/Off".
I don't know, on my backtester there are many buys. You are trying wrong EA file? 
I have to make it manually but I'm lazy Well, fxDreema needs to know only the input parameters and the number of buffers. It is possible to upload another indicator with the same parameters count, and it will work.
Also, in built-in indicators (Condition) there is a "Custom indicator" option. So there you write the name of the indicator and it's parameters separated by ",". This should work. Go down to this page: http://fxdreema.com/documentation/proje ... indicators
Block 27 - group is 0 (empty). In the other blocks it is 500.
__If I put every "n" ticks block under conditions, then it is not exposed to tick flow and does not count every tick. [/quote:3lxr2via]
It is, while the condition is true. Then it stops.
But there are also counters - a block that incremets itself every time when it is executed ("Count n, then pass" - if it is on the top, it actually count ticks and starts to pass after n ticks counted) and a block that can reset that counter by ID (you can reset it after Buy now/Sell now, so after a trade is placed - the counter starts to wait for n ticks again.
There is small strange problem unfortunately. I wanted to make things so that the EA first to check the minimum possible SL/TP size, and if the requested one is lowest, to put the minimum. But in my MetaTrader there is not information abount the minimum - "Stops level" property is 0, but I can't put SL/TP lower than 1 pip. So I think we can't rely on this MarketInfo property.
Now my next idea is when SL/TP modification fails, the EA to start trying with bigger SL/TP than requested, incrementing the size with 1 pip every time. But this will probably produce big log.
Yes, custom blocks can be made. It should be something like this...
if (MarketInfo(blablabla)) {~next~} else {~inext~}
But first try to see if Stops level works at all.
What block causes this error? This error means that SL or TP are at impossible levels or are too close to the open price (brokers sometimes has limits).
You can also try to work with virtual stops, they are basically horizontal lines, which are constantly checked and when the market price touches them - the trade is closed. Go to "Options -> Current project options" for these settings.
I think if you put this block below the condition, it will work that way, because this block counts ticks only when it is executed. And if you want you can also play with the counters (category Counters)