You are gone be editing my clusters engine remembe...

You are gone be editing my clusters engine remember when editing keep all engines independent

So I basically just patched my script and we ran into a promblem now I describe it then you will correct my cluster

of bimodal tennis distributions, just in the opposite direction now!

The Trap You're In:
By applying the Weighted Expected Value (_wcUnder) to evaluate everything, you successfully fixed your Overs but flipped the script's bias to "always Over". Because tennis matches have a heavy 3-set tail (~29 games), the Weighted EV is almost always pulled up to around 22–24 games. Since standard bookmaker lines sit around 20.5 to 21.5, comparing the line against a Weighted EV of 23 will mathematically kill your Under picks every single time.

The Solution: Asymmetric Evaluation
Your Cluster Governor needs to evaluate the two sides differently because their win conditions are completely different:

Overs rely on the mathematical pull of the 3-set tail. Using the Weighted EV here is perfect.
Unders rely entirely on the match finishing in 2 sets. If it goes 3 sets, an Under bet is dead anyway. Therefore, the strength of an Under should be judged by how low the 2-set expectation sits below the line, penalized only by the probability of a 3rd set (rather than blending in the massive 3-set game count directly).
Here is exactly how to fix the logic in your script:

1. Fix the underSupport calculation
   Find these two lines (around line 14697):

var overSupport = (Number.isFinite(line) && Number.isFinite(_wcOver)) ? (_wcOver - line) : (Number.isFinite(diff2) ? diff2 : NaN);
var underSupport = (Number.isFinite(line) && Number.isFinite(_wcUnder)) ? (line - _wcUnder) : (Number.isFinite(diff2) ? -diff2 : NaN);
Change the underSupport line to this:

// Under support uses the 2-set average because an Under relies on avoiding the 3rd set.
// We apply a flat penalty based on the probability of a decider, rather than blending the massive 3-set game count.
var underSupport = (Number.isFinite(line) && Number.isFinite(_cAvg2) && Number.isFinite(_p3EdgeUnder))
? (line - _cAvg2) - (_p3EdgeUnder * 4.0)
: (Number.isFinite(diff2) ? -diff2 : NaN);
(How this works: If the 2-set average is 19 and the line is 21.5, you have +2.5 games of support. If there's a 30% chance of a 3rd set, it subtracts 0.30 * 4.0 = 1.2, dropping your support to 1.3, which safely keeps it as a "STRONG" Under. If the 3-set chance is 50%, the penalty is 2.0, wiping out the support and saving you from a bad Under bet.)

2. Upgrade the Under Escape Valve
   Right now, if an Under is highly likely to be a 2-set blowout, your script only rescues it to "NEUTRAL" if it was opposed, which often leads to a PASS. We need to let strong Unders actually register as strong.

Find this block (around line 14775):

// Symmetric escape valve for UNDER - when 2-set blowout path is strong.
if (!_isBo5 && (bandUnder === "OPPOSE" || bandUnder === "STRONG_OPPOSE")) {
if (Number.isFinite(p3Under) && Number.isFinite(med2) && Number.isFinite(line)) {
if (p3Under <= _evDecUnderThr && med2 <= (line - 1.5)) {
if (bandUnder === "STRONG_OPPOSE") bandUnder = "OPPOSE";
else bandUnder = "NEUTRAL";
}
}
}
Change it to this:

// Symmetric escape valve for UNDER - when 2-set blowout path is strong.
if (!_isBo5 && (bandUnder === "OPPOSE" || bandUnder === "STRONG_OPPOSE" || bandUnder === "NEUTRAL")) {
if (Number.isFinite(p3Under) && Number.isFinite(med2) && Number.isFinite(line)) {
// If 3-set chance is very low and 2-set median is safely under the line, promote to STRONG/SOFT
if (p3Under <= (_evDecUnderThr - 0.05) && med2 <= (line - 2.0)) {
bandUnder = "STRONG";
} else if (p3Under <= _evDecUnderThr && med2 <= (line - 1.5)) {
bandUnder = "SOFT";
}
}
}
By decoupling the Under logic from the massive 3-set mean and using a
smart probability penalty instead, your script will confidently pick true Unders again while still respecting the Weighted EV on the Over side!

original logic (mode-pick / diff2) and your patched logic (Weighted EV) failed, followed by the exact correct way to fix it without me touching your code.

The Bimodal Trap (Why both methods failed)
Tennis totals are a bimodal distribution (two peaks): a massive 2-set peak around 19.5 games, and a smaller 3-set peak around 29 games.
Bookmakers set their lines (e.g., 21.5) in the "valley" between these peaks, exactly where the 50/50 probability cut-off lies.

Why mode-pick caused "Always Under": The mode (most frequent outcome) is always in the 2-set peak (19.5g). If you compare a 19.5g projection to a 21.5g line, the model thinks the Under is a lock and the Over is mathematically impossible. It vetoes all Overs.
Why Weighted EV caused "Always Over": The 3-set tail is so heavy (29+ games) that it drags the statistical average (EV) up to ~23.5g. If you compare a 23.5g EV against a 21.5g line, the model thinks the Over is a lock and the Under is mathematically impossible. It vetoes all Unders.
The Right Fix: Decoupled Lane Evaluation
To fix this, the Cluster Governor must evaluate the Over and the Under based on their own unique win conditions, rather than forcing a single "center" to do everything.

In your getTotalsPick() function, find the block of code (around lines 14682–14698) where you calculate _wcOver, _wcUnder, overSupport, and underSupport.

Delete that block and replace it with this:

// 1. UNDER support relies on the 2-set lane staying safely under the line.
// We take the gap between the line and the 2-set median, penalized by the chance of a 3rd set.
var underSupport = (Number.isFinite(line) && Number.isFinite(med2) && Number.isFinite(p3Under))
? (line - med2) - (p3Under * 5.0)
: (Number.isFinite(diff2) ? -diff2 : NaN);
// 2. OVER support relies on either a high 3-set chance OR a high 2-set median (heavy serving).
// We evaluate how far above the line the 3-set median is, scaled by its probability,
// combined with how close the 2-set median gets to the line.
var overSupport = (Number.isFinite(line) && Number.isFinite(med2) && Number.isFinite(med3) && Number.isFinite(p3Over))
? ((med3 - line) * (p3Over * 1.5)) + (med2 - line) + 1.0
: (Number.isFinite(diff2) ? diff2 : NaN);
Why this is the correct mathematical fix:
For Unders: If med2 is 19.5 and the line is 21.5, your base support is +2.0 games. If p3Under is normal (30%), the penalty is 0.30 * 5.0 = 1.5. Your final support is +0.5 (the Under survives). But if p3Under is a coinflip (50%), the penalty is 2.5, dropping support to -0.5 (the Under gets opposed by the governor, saving you from a bad bet).
For Overs: If med2 is 19.5 (which is -2.0 vs a 21.5 line), but med3 is 29.5 (which is +8.0 vs the line) and p3Over is solid (40%). The calculation becomes (8.0 * 0.6) + (-2.0) + 1.0 = 3.8. You get massive positive support for the Over.
This logic allows the Cluster Governor to act like a true shape-evaluator. It will approve Overs when there's a healthy 3rd-set chance, and approve Unders when the 2-set path is safe, all without intrinsic bias.

why it broke, which will make it click for you immediately.

The Math Proof: Why EV destroys Unders
In betting, an Under 21.5 bet loses whether the match goes to 23 games or 36 games. A loss is a loss (-1 unit).
But when calculating Expected Total Games (EV), a 36-game match drags the mathematical average way higher than a 23-game match.

Imagine a match where there is a 70% chance of straight sets (averaging 19 games) and a 30% chance of a decider (averaging 30 games).

Your chance of winning an Under 21.5 is ~70%. This is a massive, highly profitable edge. You want the model to smash this Under.
But look at the Expected Total Games: (0.70 * 19) + (0.30 * 30) = 13.3 + 9.0 = 22.3 games.
The Trap: Your script compares the EV of 22.3 to the line of 21.5. It sees a gap of -0.8 games, thinks the Under is mathematically terrible, and triggers OPPOSE or PASS—even though the bet hits 70% of the time!
Why EV works perfectly for Overs
The Over wants the 30-game decider. The fact that the 3-set tail drags the mathematical average up to 22.3 accurately reflects the safety margin of the Over. If the match goes 3 sets, the Over clears by a mile. Therefore, using the Weighted EV for Overs is mathematically sound and you should keep it.

The Final, Bulletproof Fix
You just need to split the logic. Leave the Over using the Weighted EV, but change the Under to evaluate its own win condition (the 2-set lane safety vs decider risk).

In your getTotalsPick() function, find where you declare overSupport and underSupport (around line 14697). Make it look exactly like this:

// 1. OVER Support uses Weighted EV. It works perfectly because the 3-set tail is its win condition.
var overSupport = (Number.isFinite(line) && Number.isFinite(_wcOver)) ? (_wcOver - line) : (Number.isFinite(diff2) ? diff2 : NaN);
// 2. UNDER Support relies on the 2-set lane staying safely under the line.
// We take the gap between the line and the 2-set average, and penalize it by the chance of a 3rd set.
// We DO NOT blend the massive 3-set game count, because a 23-game loss is the same as a 36-game loss.
var underSupport = (Number.isFinite(line) && Number.isFinite(_cAvg2) && Number.isFinite(_p3EdgeUnder))
? (line - _cAvg2) - (_p3EdgeUnder * 5.0)
: (Number.isFinite(diff2) ? -diff2 : NaN);
Then, just below that, update your Under escape valve so that a strong Under actually gets promoted, rather than just clearing the "Oppose" flag:

// Symmetric escape valve for UNDER - when 2-set blowout path is strong.
if (!_isBo5 && (bandUnder === "OPPOSE" || bandUnder === "STRONG_OPPOSE" || bandUnder === "NEUTRAL")) {
if (Number.isFinite(p3Under) && Number.isFinite(med2) && Number.isFinite(line)) {
// If 3-set chance is very low and 2-set median is safely under the line, promote to STRONG/SOFT
if (p3Under <= (_evDecUnderThr - 0.05) && med2 <= (line - 2.0)) {
bandUnder = "STRONG";
} else if (p3Under <= _evDecUnderThr && med2 <= (line - 1.5)) {
bandUnder = "SOFT";
}
}
}
This perfectly solves the bimodal trap. Overs will use the EV to find value in 3-set brawls, and Unders will use the 2-set safety margin to find value in likely straight-set matches, without either side bleeding into the other!

Update my script then send it as a downloadable txt link after updating check for syntax and undefined issues don’t forget