@kbt I doubt the purpose of this post is to specifically talk about Iran. The fact is that the average person in country a has more purchase power than the average person in country b (and fxdreema or any other business cant do much about this inequality).
Anyway 30% of Iranian households live in poverty, so it is not very outrageous to call it a poor country in general, in my opinion.
It seems MT5 got a resolution selection in the latest update. I suppose this helps with objects
I can't test the .ex5 right now, got an optimization running..
Please use the windows snipping tool to put a picture, or share a copy of the project:
@MMBInvest DoubleToString() always works, I dont know what else to say. Here is an example you can actually reproduce, maybe it helps.
testtt.mq4
@spicynote
This will need some fixing. Remember that the ea algorithm runs on every new tick (as we are "on Tick").
Now it checks every tick if the candle is above MA 60, and if that is TRUE, then it buys.
It will not open new buys (even if price is above MA) before we wait 2 bars, that's what the "every n bars" does.
You shouldn't put any closing conditions after the opening condition - that means that you want to close the trade on the same second you open it.
I'll make a working example in a minute
Looking at the source, the time model seems to use TimeLocal() and TimeGMT() but then immediately remove the difference to server time - I wonder what's up with that @fxDreema 
Also a good thing to remember:
@spicynote
Here: https://fxdreema.com/shared/Y3lUXgVrb
Moving backwards in time is best done with the candle ID.
ID 0 = current, updating candle
ID 1 = latest completed candle
ID 2 = 2nd completed candle
etc.
Connecting blocks vertically means "AND".
I connected 2 blocks with condition: "candle close is above 60 MA", with different candle IDs, so the combination reads as "latest candle is above 60 MA, AND the one before it is also above 60 MA"
@PhiLykia does the custom indicator have variable names such as "c" or "v"? Those may create the bug. You could try renaming the variables of your indicator.
I do agree these kinds of bugs should be fixed rather than finding such workarounds.
Use the block "modify variables" and from there select candle -> candle total pips
@l-andorrĂ fractal indicator has a value for every candle, even if there is no arrow visible. That value will be 0, and naturally 0 is always below candle high.
This is why the correct way to use fractal is simply with condition:
fractal up/down != 0
@jennifer
You can put custom code pretty much everywhere in fxdreema, like this for example
@gsmtricks Just replace it to the function:
MathFloor(Rate * 100) / 100
Hope it works!
@moon
We update the PreviousBalance variable at the point when there is no trades.
When there are some trades, compare the current equity to the previous balance. If it is 100 units bigger, close trades
How to troubleshoot an error like this:
Hmm, inp43 = problem is block 43, left operand, something about timeframes...
Lets check the block in fxdreema:
Hmm, maybe I should untick the timeframe box:
voilĂ , no error anymore! To the next error ->
This error can be more confusing, as the stop-loss doesnt seem to use any timeframe:
But it is hiding in the drop-down menu, "Custom (pips)". Uncheck that timeframe box. No error!
@l-andorrĂ I wish I was a real programmer lol. I don't even know the basics of mql.
I just copy from mql4 articles, try and fail and try again until I get my result.
Thats the beauty of this program, you can teach yourself
@zackry It is to filter how far your trade is from the break even point.
If you set 0, the break even will always be set if your trade is on profit.
If you set 10, the SL will move to break even only if youre 10 (or more) pips on profit
@zackry ok, just set it to 0, so the amount of profit will not matter.
You can't set a breakeven on a losing trade