I thought you have that ticket number and logically you replace value 1 with that unique ticket number 
block For each Trade is basically loop which is loading ticket number for one trade and with other blocks connected in this loop you can filter and working with that trade, you can save values into variables (or array), from one trade, from filtered trades or all trades, and than working with that .... these pink blocks are very powerful ..
@didble-trader said in Error code=4806:
Error code=4806
is not that something related to custom indicator?
not with bucket, you can do it with For each Trade
yes you can do it, but it is complicated .... you end up with a lot of blocks or with loop through arrays with less blocks ...
look into my examples with looping and modify that for your purposes ... in forum are many examples ...
or modify this one for your purposes:
https://fxdreema.com/forum/topic/4510/tutorial-loop-advanced-find-and-save-specific-value-from-indicator-history
something you can do with block "Indicator moves within limits" but limits are not looped in this block ...
they are recreated from online charts (which are normal charts) ... offline is only name for different charts
this recreation is done with different conditions or math
... there is a lot of things on which are they created, well known are renko charts - they very depends on ticks, in history you have not detailed information about ticks and therefore you are not able to recreate true renko offline charts from history -- and it is why a lot of people failed on their renko strategies (tester/history was working great but the reality not)
it is not possible in any builder, you must create custom indicator which is doing this job and than import it into My Indicators in fxDreema and than working with that custom indicator ...
I showed few examples how to do these custom indicators, there exist function ibandsonarray() which can be used for this job on your request:
https://docs.mql4.com/indicators/ibandsonarray
this is one of examplex where is used imaonarray (moving average on that separate window), you can replace and modify it with bolligerbands (ibandsonarray)
https://fxdreema.com/forum/topic/5806/baby-steps/19
use Bucket of Trades
https://fxdreema.com/examples#Bucket-of...
there is such option for TP (average)
there should be added several blocks for these indicators, which would work with history candles, by example:
next can be added special block for creating advanced comments with rectangle background ...
for MT5 it is more complicated but it can be created ... indicators are simple
next, you should avoid checking these input parameters ... you should give there parameter Constants ... for more blocks the same constants ...
https://fxdreema.com/tutorial/builder/constants-and-variables
if you want speed up tester, set value in barsLimit to about 200 or 300 or more and try with that values ... it should speed up tester (it should avoid calculation of whole history bars, maybe ... ) ...
as next step you can place block "once per bar" before this calculation and under "More settings" in blocks give 1 for Candle ID (original is 0) ... it will take value from first candle (not the current one, and it should be faster) ..
try something like this:
https://fxdreema.com/shared/nKUwgnv9c
there can be bug, maybe you must add more control logic (possibility of false detection or fail) ... it is something what needs intensively testing and debugging ..
note: this example is only for buy and only if price crosses trendlines up (trendlines are placed manually, renamed as TL1 and TL2) .... after trade is entered, EA should delete these trendlines (I have not did it, you can) ...
admin recently added this option under project settings:
"Display Indicators After Test" set to "No" and it should working 
because when period is changed, this situation tester understand as a new indicator ...
try to place this into on Deinit section:
with arrays it is possible, but avoid it if possible and use one EA for one Pair...
... for few reasons, in MT4 opening multipairs can not be tested in tester, only in MT5 ... and only blocks in onTick section .... on Timer section is not working in tester
... in MT4 you can test reading data from other pairs, but not opening multipair trades
if it is not possible to avoid, than create it
... if you create it in onTick section, all your pairs depends on ticks from pair (from chart) where EA is placed (good or bad? it depends on your strategy)
... if possible, create and test your strategy in forward demo with blocks placed in onTimer section ... set timer interval for some reasonable value, like 10s (here again, it depends on your strategy)
... in overall, if you create multipair EA, and your strategy is lossable in lets say 5 pairs, in other pairs is most probably lossable too, ... when you sum that, you end up logically in the loss
... my hint is, focus for only few pairs (filter them too, because some pairs are more trendy (gbpjpy) and other pairs are more side (eurchf)
... create profitable EA for one pair (you can read data from other pairs) but with EA open only 1 pair based on that data ... read these data with multicurrency custom indicator if possible, if not possible you can do it in EA ...
working with multipair (or multicurrency) EAs is possible, be aware because it is big challenge and you can easily fail, your EA can fail and when you ended up with 28*x opened trades, you will easily lose yourself and probably a lot of money too (because closing 28 trades may not be cheap ) ...
@miro1360 said in Daisy-Chaining Indicators:
sure, check this:
https://fxdreema.com/shared/BkhCaSnW
here are 2 moving averages, one is static (yellow) with period 200 and the second (purple) is with dynamic period controlled by RSI indicator
note, there can be problem with cross detection
note2: rsi is not good example
and this is EA from tester, not indicator ...
now I probably know what are you trying to do ....you are trying to generate indicator from fxdreema - it is not working this way, fxdreema can not generate indicators, only experts, and experts can not be used as indicators (in indicators folder, but they can work as some indicator - as experts)
