🚀 AFStar Indicator MetaTrader 4/5 – 2026 [Developer Update] - [TradingFinder]

Product reviewed

AFStar / “EFAR” Indicator for MetaTrader 4 & 5 (Developer Update, 2026) — an indicator that generates buy and sell signals using internal calculations based on multiple moving averages and Williams %R (Williams percent range) indicators.

Key features / how it works

Signal colors

• Buy signals: blue
• Sell signals: orange

Core calculation components

• Uses fast and slow moving averages (multiple MA elements)
• Uses Williams %R indicators as part of the calculations
• Mentions “footprint volume profile” and “fastest gap” as part of the indicator approach (as described in the subtitles)

Configurable MA ranges (fast + slow)

For each moving average type (fast and slow), the indicator accepts:

• Start factor and end factor (range)
• Step / increment (how the factor moves within the range)

Notes:

• The numbers are described as factors used to compute MA periods (not the period directly).
• Effect of widening upward the range / using higher factors:
  • Leads to higher-period moving averages
  • Results in fewer signals (explicitly stated)
• Includes a step change concept for the MA factor progression

Configurable Williams %R parameters

Also uses:

• Start factor and end factor (range)
• Step / increment

Guidance given:

• Values should be chosen based on the trading symbol and timeframe to better match market conditions.

MT5 vs MT4

• Settings are the same between MT5 and MT4.
• MT4 includes one extra input:
  • Number of past candles used for calculations

Pros (mentioned)

• Provides clear visual buy/sell signals (blue/orange).
• Highly parameterized:
  • Tune fast/slow MA factor ranges and Williams %R factor ranges.
• Tuning guidance:
  • Adjusting MA factor ranges can reduce signal frequency (by using higher-period MAs).

Cons / limitations (mentioned or implied)

• The subtitles don’t list explicit drawbacks, but tuning complexity is implied:
  • Multiple ranges + step sizes likely require more setup/experimentation.
• Signal frequency and behavior depend heavily on user-chosen factors:
  • Higher factors likely reduce signals, meaning you may have fewer opportunities if set too conservatively.

User experience / testing (from subtitles)

• A “live test” is referenced for both:
  • MetaTrader 5
  • MetaTrader 4
• No performance metrics are provided in the subtitles (e.g., win rate, backtest results, ratings). The discussion focuses on workflow and settings.

Comparisons made

• No direct comparison to other indicators is mentioned.
• Only a platform comparison appears:
  • MT5 vs MT4, with MT4 differing by an additional “past candles” input.

Unique points mentioned (complete list)

1. Indicator provides buy (blue) and sell (orange) signals.
2. Uses moving averages (fast + slow).
3. Uses Williams %R in internal calculations.
4. Mentions additional concepts: “footprint volume profile” and “fastest gap.”
5. MA settings include fast MA range (start/end factor).
6. MA range uses a factor, not the direct MA period.
7. Larger/highward factor ranges lead to higher-period moving averages.
8. Higher-period MAs produce fewer signals.
9. MA settings include step/increment behavior.
10. Williams %R settings also use start/end factors and step/increment.
11. Williams %R values should be chosen based on symbol and timeframe.
12. MT5 and MT4 share the same settings.
13. MT4 adds an extra setting: number of past candles used for calculations.
14. Live tests were shown on MT5 and MT4.
15. Viewer is invited to leave comments/criticisms/suggestions.

Speakers / contributors

• Single speaker throughout (no multiple viewpoints indicated).

Concise verdict / recommendation

Recommended for traders who want a customizable, signal-based MT4/MT5 indicator (blue/orange buy/sell) built around tunable fast/slow moving-average factors and Williams %R ranges. Expect fewer signals if you raise the MA factor ranges to higher-period settings, and note that MT4 requires an additional “past candles” parameter. No objective performance ratings are provided in the subtitles, so evaluation should be done via your own testing/backtesting.