Two things a gate could not have found and one look at a screen did.

They were far too small. 22 was chosen against the loot captions at 20,
and both of those are read while standing still; this is read out of the
corner of an eye in the second before it goes, over a mob, while you are
pressing something. 36 now, and the range runs to 72.

Two shrinkings were compounding under it. A number ended its life at 0.72
of its start, and an ordinary hit late in a fight was weighted to 0.78 of
that against the fight's biggest, so a plain hit finished at 12 pixels of
a setting that said 22. The envelope ends at 0.85 and the weight band is
0.88 to 1.18. The band exists to say which of two numbers was the bigger
hit, and the setting says how big numbers are; the band was doing both.
A critical starts at 1.45 rather than 1.3 with it.

And the client is no longer drawing the same hit underneath. Four CVars,
read off Blizzard_SettingsDefinitions_Frame on the 2.5.6 source rather
than typed: damage on the target, periodic spells and pet melee under it,
and healing beside them. The `_v2` on three of those is why they were
read rather than remembered, because the names without it are the retail
spelling and resolve to nothing here, which fails the way a CVar always
fails, silently and looking like it worked.

Not enableFloatingCombatText, which looks like the switch and is the
wrong one. On this client it gates the text beside your character: the
dodges and parries, aura gains and fades, combat state, combo points,
energy, honour and reputation. Blizzard_CombatText registers eight events
behind it and not one is a damage event, so taking it would delete a
dozen readouts to stop one duplicate.

What was there is remembered per character before the first write and put
back when the part goes off, which is the shape Charge/SoftTarget.lua
already uses and for its reason: a part that leaves a CVar wherever it
landed quietly edits your client config. `/wk hits quiet off` leaves the
client alone for anyone who wants both.

The section asserts all four go down, that the master does not, that the
prior values come back rather than the defaults, and that quiet off takes
nothing at all.

@@ -283,0 +289,4 @@
+	check(row and row["RightButton"] and row["MiddleButton"],
+		"the gear row keeps the camera's buttons, so a right drag on a row does not turn the camera")
+	check(head.button:GetWidth() < head:GetWidth(),
+		("the secure button is %s wide on a row of %s, so the action is the whole row again")

@@ -555,3 +645,2 @@
 local function Portrait(parent)
-	local panel = UI.Box(parent, C.sunken, C.edge)
-	local level = (panel:GetFrameLevel() or 0) + 5
+	local panel = CreateFrame("Frame", nil, parent)

@@ -0,0 +170,4 @@
+end
+
+-- How many of the four are down, for the harness.
+function Blizzard.Quiet()