Transferring Common Stack:
MA Stack single timeframe, multi-timeframe and multi-currency variations for MT4 (Metatrader 4)
Very helpful for locating present and better timeframe tendencies. Greatest suited to long run development based mostly buying and selling.
For fast scalping use fewer shifting averages. And never appropriate throughout low volatility. Solely use throughout excessive volatility and regular trending markets.
Use this to reinforce your current Development based mostly methods to seek out greatest tendencies. As a substitute of utilizing as a standalone indicator.
You will get any of those variations relying in your wants:
MA Stack for Particular person Charts:
Video Tutorial:
Primary MA Stack Indicator:
It is a single timeframe & single forex indicator. It seems at MAs and present 3 attainable states on chart:
- When all MA Align Upwards: Stack Up
- When all MA Align Downwards: Stack Down
- If MAs not aligned: Stack None
You may place the small block in your chart. And get present standing of the Stack:
You should utilize this template to get the above chart.
It’s simplistic and really eash to make use of and might information you to seek out good tendencies in your methods.
Purchase Stack:
When quickest above, medium MA in center and slowest beneath. So the stack ought to seem like screenshot above: 8 (above) > 21 > 34 > 55 > 89 (lowest)
Promote Stack:
When quickest beneath, medium MA in center and slowest above. 8
MA Stack MTF:
It is a Multi-timeframe and Single Forex Scanner. You may specify the Pair title and timeframes checklist (comma-separated).
It is extremely helpful when buying and selling methods which depend upon completely different timeframe tendencies. If it is advisable place a number of MTF indicators on chart, be sure you use a singular prefix for all.
And alter the YDistance. And likewise YSpacing should you want it to be extra compact.
Min Distance will be outlined individually for every timeframe. It’s a minimal distance in factors.
It’s checked for the gap between all MA individually.
Suppose M5=10,M15=20
Then for M5, it would examine that each one MAs are aligned.
And the first and 2nd MA are at the least 10 factors away from one another, 2nd and third additionally, third and 4th.. and so forth. Identical for M15 however with 20 factors.
Min Distance will keep away from alerts like this. When MAs are aligned, however nonetheless too shut collectively and value is clearly nonetheless ranging:
If false use identical “Shift” for all timeframes. Or else convert bar’s time based mostly on present timeframe.
You may see in Consultants log which bar is used for which timeframe after conversion:
Suppose our present timeframe is M30 and Shift is 1. That shift bar’s timings will really replicate completely different bar’s on completely different timeframes.
Bar 1 on M30 remains to be ongoing as bar 0 on greater timeframes. And it has already occurred on decrease timeframes a number of bar’s again.
However should you want Shift as 1 on all timeframes, hold “Convert Timeframes” to false.
Full Scanner Dashboard:
Multi-Forex & Multi-Timeframe Full Scanner Dashboard.
This exhibits:
- MA Stack Up/Down
- And what number of bars again the Stack occurred (in brackets)
That is very helpful to seek out which timeframes are at present in alignment.
If MA Stack aligned was greater than MaxPastBars in the past, then you will notice (..)
Present Revenue Factors: true/false
If true, it would present how a lot Revenue/Loss has occurred in Factors. For the reason that MAs had been stacked.
This setting is helpful, as a result of even after MAs stacking occurs, value can typically get caught in a variety. So, the factors are useful in figuring out when the MA Stack occurred and the way far the worth has are available what number of bars.
Word that, if the stack occurs, and if it stops even for just a few bars, after which occurs once more. The Factors shall be calculated from the Candle Shut of the latest Stack’s beginning bar to the present bar’s closing value.
Use this information to see Widespread Scanner Settings:
https://www.mql5.com/en/blogs/submit/747456
