@frank-2
you cant check if there is no trade
and the next check is once per trade if there is no trade
there needs to be a trade first to limit the action to once per trade afterwards
@frank-2
you cant check if there is no trade
and the next check is once per trade if there is no trade
there needs to be a trade first to limit the action to once per trade afterwards
this might be not balanced once h1 and once current timeframe

@drewliedadeuce
you could also grab the average spread which is calculated by the ea
it has some logical issues:
first you check market properties it would be better if you use the low of x candle instead of giving a range which is x of x
second you cant expect a cross to happen if you let the block run just once a bar
you would say is below not crosses below but that isnt the exact crossing price can be way further away.
this would be quick fix ignoring the low of the candle thing:

you need to change the loop for each trade, otherwise it cant close open positions
and then in the condition you simply switch volume for profit
or make 2 conditions 1 profit and the 1 volume
find a good strategy, test and then make the ea, easy!
@jstap
wouldn't it be better to store the incoming ticks or last candle high/low since the last trade was closed?
from what i saw it would reduce the workload a lot and takes worries out, but i dont understant the whole concept sry...
@iagnew
if you want just 1 trade and there shouldnt be another
set the trade check to equal 0, if you want to allow a certain number of trades later on
use the no trade block if you only want 1 trade at the same time
not forget to re/set the sl before each loop so you set the correct sl
a please would be an act of kindness, if you want someones help!

Think about it in the future!
make a calculation in a custom block combined with an if block, gives the same effect!
string. lvl_indi_name. = sample_indicator_name;
string indicator_handle_01 = iCustom(NULL,0,lvl_indi_name) ;
ChartIndicatorAdd( 0 , 0 ,indicator_handle_01 ) ;
in a custom mql block
@uriel-0
yes. the problem was the handle back then. once i saw it, it was done quickly
the first custom block loop through all open orders and counts them. so you dont need to run extra loops.
at this stage you could sum all swaps as well. and then dont need the other blocks anymore.
yes you are right!
he could offer an extra support channel where specialists are available 12/5. However who is going to cover the cost of this 240 hours a month (12x5x4) Lets assume you find a specialist that works for 50$/€ per hour (which would be on the lower end) you can see quickly that nobody is willing to cover that cost. Or lets say you need to find at least 100 people who are willing to pay 100$/€ extra per month at least.
@stantham
you would need to understand the logic of each line and translate it into a block in fxdreema if you want to modify it there
@mantadiver
each group can be in full 100s
so group 1: 100-199
so group 2: 200-299 etc
so you see instantly which belonds to which
you could simply define a global variable with the name indicator_value = EMPTY_VALUE;
at bool alterted you make another line with indicator_value = EMPTY_VALUE;
in the do alert buy you make a set globalvariable indicator_value = 10
in the do alert sell you make a set globalvariable indicator_value = -10
simply idea you can try
@akulus said in MT5 tries to open 250 lots position when it shoudn't:
SPX500
are you trading indices on icmarkets?
If yes i would suggest you to make the lot/trade size calculation by your own ( in seperate step by a formula) on fx pairs you shouldnt see such issues.