Posts made by jstap

@amadablam MarketInfo(0,MODE_STOPLEVEL); This code in a modify variables block should give you the minimum stop loss, before placing an order check the SL distance is far enough away, otherwise use this number for the stoploss.

@musa-5 said in VARYING DATA SETS ON ONE EA BUILD:

shared/Bsni6mlXb

If you are running this on back test it is unlikely to run on any TF above 15m, on live or demo it should.

@chattahooche You can use a condition to switch trail or something on/off. If you put a shared link here it's easier to see how a block is connected and what's inside.

@jstap Thinking about it you probably want something like this: https://fxdreema.com/shared/y5G5430G

@stantham The best way is probably to use a once per bar block, this will limit trade to once per candle.

@stantham No worries, your welcome.

@william-1 Put a shared link on here so problems can be assessed.

@stantham https://fxdreema.com/shared/ZMehNl49d

@william-1 The stop is how far behind price to trail, this distance doesn't change unless you use start or a separate condition to start/stop. If you put a shared link things can be looked at, I would set up a simple buy/sell EA, then set up a simple trail to see on back test how it works.

@jstap said in Pair name:

@des-3 Not sure if names are same as market watch it should work.

@des-3 Not sure if names are same as market watch it should work.

@bluekangaroo14 When signal appears, set a variable or flag, count candles using a formula block reset when enough candles have passed.

@stantham https://fxdreema.com/shared/rPtHfNY4c This gets the buy/sell text into a variable, the buffers just contain numbers (probably MA price values). You can use a standard condition block in your buy/sell trees, with text = indicator text to create a buy/sell order.

@alphaomega Pretty much everything works for mt5, every time people asked a question I would use this file to add an example so it isn't necessarily all needed to work together, I also have other ideas that aren't in here.

71-72 will likely be in there somewhere but unsure and they're unnecessary for area 20.

@ladydolares I would do it like this: https://fxdreema.com/shared/62Ef2EIXb

@alphaomega 71-78 will count the candles starting at 0 from the point of MA cross, can be used for most things like candle<>, indicator <> 0 etc.

78+79 is to put in tree so whenever the loop count is above a set number the tree will pass.

81-88 is how to turn a bool constant/variable true false depending on condition.

89+90 is how to read if a bool condition is true/false, if true the block passes.

@ladydolares You can set conditions to start/stop EA, if removed the only way to attach to chart is to do it manually.

@william-1 Stop is how much profit before stop moves, step is how far to move once stop is reached, start is how to wait before starting trail, the trail won't stop until price retraces and hits.

@yyaanniicckk Groups get added to the magic no, if group is 3, magic number is 1111, magic number becomes 1114, as long as group and magic numbers match all trades on same platform should work together.

@thedisliked This makes no sense to me as there is 8 condition blocks in area 20, the loop at the top will start at 0 then count candles from the cross, the condition blocks go in your tree, you only need 2, logic being check amount of candles the fast ma > slow ma.