Best posts made by miro1360

try something from this:
https://fxdreema.com/forum/topic/4208/tutorial-06-my-indicators-in-fxdreema/2?page=1
...
find:
2.) Import without mq file, with ex file:

they are little messy, but something can be used

yes, as you told ... fxdreema importer is working that way, it only store these parameters (it is not storing whole indicator), also in EA code is used only reference for indicator as external file (its name)

use it with Symbol() ... but note, that admin can change it anytime

I am very satisfied with contabo.com VPS with SSD performance, exactly this one:
https://contabo.com/?show=configurator&vserver_id=185
huge RAM, six cores and speed of SSD, unbeatable
... they have reasonable prices + licensed windows (you need check box while order), speed of VPS was really really fast, I never get problems and it past it has runned >15 metatraders with EAs at once and still have resources without problems (I am with them > 2 years) ... previous I tried a lot of VPS and all was slow, maximal 2-3 metatraders and resources of VPS was on 100% ... amazon is not cheap ... and is slow for that price ..
I am talking about VPS up to 20USD/month ...

not directly, but maybe with files reading/writing ... or using database:
https://www.mql5.com/en/articles/932
... I have not tried

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 ...

it is ... but wait for next value (the first logically can not be read if is not located on candle ID 0 imediatelly after EA is placed on the chart)

The block Indicator appear is not the right block for working with zigzag.

The block "Indicator is visible" could be theoretically used, but it will not work right.
It will not work because H0 or L0 is always present on the chart (and in this block it is not related to the Candle ID) and because of that the condition "Indicator is visible" will be always true. It can be used only for the current leg, which is related to the candle ID in the block.

Few notes, because zigzag is a bit complicated:

• current leg (0) differs from other legs (1,2, - these are static), because this current leg can be repainted (and often is repainted/updated)

• zigzag leg ID is not the same as zigzag on the candle ID, but they are related (zigzag leg ID have its own candle ID and this is changed/moved with each new candle .... moreover the change of zigzag leg IDs changes whole relation)

• for identifying the presence of zigzag leg on the specific candle you must use custom code, whereby you check if zigzag leg is present on the past candles (and save such presence - save candle ID on which the zigzag leg is present)
  (I am doing this in my tutorial, where am I looking if the most present zigzag leg is high - H0 or zigzag leg low - L0)

I am not sure, if I remember these things about zigzag right, because it was long ago when I was working with zigzag, and it needed a lot of debugging, because not everything worked as expected

they used custom indicators named:
CoronaCyclePeriod
CoronaDFT_v1
Homodyne
Goertzel_Cycle_v1
Instant Trendline Filter
Moving Average (weighted mode, period 4)
another MA with dynamic period
bolliger bands
RSI
MACD
CCI
Stochastic

each indicator has own parameters,
so much combinations can contains at least the one combination of parameters, where on the specific timeframe for specific pair exist one specific profitable strategy - but that is the history where each one is general, it is gone ....

what happens if you run that EA from 2015?
martingale is good when it has the limit, lets say after 3 multiplies it will reset ... if no and rather continuation is taken, one must count with bankruptcy

you have to add a reset of variables before loop:

problem with not opening trades is not in the loop, it is in other conditions before AND block, trades are not opened:

here are trades opened:

but this is not good, because each loop cycle where condition is true will open a trade ...
you have to create few logic changes:

this is testable in tester:
https://fxdreema.com/shared/o0zAtdend

yes it is implemented
https://fxdreema.com/shared/5rvzn7pN

https://fxdreema.com/shared/vyN1rZPZb

It should have similiar result ..
But these pink blocks needs additional filtering ...
And for checking only a last trade change the parameter "Not more than "n" history trades" to 1:

Go through all my posts, try them as examples and that way you can learn a lot

This is admin:
https://fxdreema.com/about

I can assure you he is a fair man.
He works alone, like one man team, therefore there may be a time gap.
Try to contact him by email, be patient.

for 0.1 format, do this:
TP1 = NormalizeDouble(TP1, 1);

https://docs.mql4.com/constants/environment_state/marketinfoconstants
create new variable lot_step, and use this custom code function:
lot_step = MarketInfo(Symbol(), MODE_LOTSTEP);

there are other lot values which can be achieved:
lot_min = MarketInfo(Symbol(), MODE_MINLOT);
lot_max = MarketInfo(Symbol(), MODE_MAXLOT);

you can get them all and create some custom math for your purposes