Tribonacci_RF攻略#1: Wait to shoot "three conditions" (pullback/backtest aiming EA explanation)
Hello, this is a black cat.
Last time, I organized the idea of the Tribonacci ratio (5 lines) from the perspective of formalizing pullbacks/retracements as rules.
This time, as a sequel, I will summarize the "three conditions" that Tribonacci_RF (EA) uses to decide when to enter—waiting to strike.
To state the conclusion first, this EA does not enter immediately when it touches a line;
it is designed to enter only when all three conditions are met, which helps reduce noise entries.
1) First premise: this EA waits for pullbacks/retracements
This EA automatically creates the Tribonacci retracement (5 lines) from recent price action,
and makes visible the “candidate zones” for pullbacks/bounce backs, then waits for the conditions to align.
Recommended time frame: 15-minute chart (M15)
Reference: last 120 bars
Ratios: 16.0% / 29.5% / 54.3% / 73.6% / 83.9%
2) Waiting to strike: the “three conditions”
This is the main part. The three conditions are as follows.
Condition 1: touch of the major line
Condition 2: distance (in pips) from 0–50% is above a certain threshold (check potential)
Condition 3: Stochastic condition (buy ≤ 30% / sell ≥ 70%)
3) Condition 1: line touch (which line is being watched)
The entry candidate is the Tribonacci 5 lines (16.0/29.5/54.3/73.6/83.9).
This EA checks whether the “front foot touched” to avoid jumping in on momentum alone.
（※ one aspect of the “wait design”）
4) Condition 2: divergence check (check potential for 0–50% distance)
In markets where the 0%–50% distance is small, there is little room for movement,
and pullbacks/retracements tend to become “tiny noise.”
Therefore, this EA only considers there is room to move when the 0–50% distance exceeds a certain number of pips,
and so it judges that there is potential for movement.
（This filter helps reduce wasted entries）
5) Condition 3: Stochastic (confirm overbought/oversold)
Finally, with Stochastic,
Buy: ≤ 30%
Sell: ≥ 70%
Only when these conditions are met does an entry candidate become valid.
Not just lines and distance,
the timing (oscillator) must also align—waiting for that is key.
6) Exit is trailing-led (preserve gains)
Tribonacci_RF does not rely solely on fixed take profits; it aims to capture further gains with trailing.
（e.g., start at 8 pips / follow in 1-pip steps, etc.）
※This part will be explained in detail in the next issue (#3), including the idea behind settings.
7) Caution (essential read)
Accounts with stop levels are not recommended (because 1-pip trailing may cause order modifications to be rejected)
When spreads widen sharply at release times, use MaxSpreadPips to mitigate
Most reasons for “not functioning / choppy” lie here, so it’s safest to check this first.
Summary
This EA does not enter immediately upon line touch
Entry occurs only when line touch, divergence check, and stochastic three conditions are all met
Thus it is designed to “wait to strike,” helping suppress noise
Product page
Next time
Next time (#2) will summarize the trailing take profit concept and the spread/stop level/verification conditions that tend to differ before operation.
× ![]()
