F1: power supply multiplies the resolved stat, it does not interpolate
PerformanceStat.Evaluate folded PowerSupply into the same Min/Max lerp factor as Heat/Durability/Quality, so zero supply bottomed out at Min instead of 0 (measured: a radiator at zero power still pumped 19-25% of full; three of Cut 7's eight authored terms had Min == Max and were completely inert, since lerp(x, x, anything) == x). PowerSupply terms are now accumulated into their own multiplier and applied to the fully-interpolated, fully-modified value instead of to the interpolation factor. The term still lives in PerformanceStat.Terms -- it is still authored per stat and still censused/validated the same way -- it is just no longer blended into `factor`. Corrected the comments that stated the old premise (Radiator.cs, Entity.cs, ItemData.cs's IStatContext.PowerSupplyFactor doc). Pinned in tests/Aetheria.Shared.Tests/PowerCurveTests.cs: APowerSupplyTermedStatWithNonzeroMinResolvesToExactlyZeroAtZeroSupply and AMinEqualsMaxStatStillRespondsToItsPowerSupplyTerm -- both fail under the reverted (lerp-based) mutation. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
This commit is contained in:
parent
e6609c45f3
commit
da5a710030
4 changed files with 72 additions and 10 deletions
|
|
@ -1371,9 +1371,11 @@ public class EquippedItem : IStatContext
|
|||
public float HeatFactor(float exponent) => pow(ThermalPerformance, ThermalExponent * exponent);
|
||||
public float DurabilityFactor(float exponent) => pow(DurabilityPerformance, DurabilityExponent * exponent);
|
||||
public float ConsumableProgressFactor(float exponent) => 1f;
|
||||
// Cut 6 (docs/stats-and-power-cut.md): the brownout curve. A stat with a PowerSupply term degrades as this
|
||||
// tick's grant falls below 1 and is exactly unchanged at full supply (pow(1, exponent) == 1 regardless of
|
||||
// exponent) -- the operator's "a continuous consumer that degrades instead of stopping." PowerBus writes
|
||||
// Cut 6 (docs/stats-and-power-cut.md), applied per F1 (operator ruling 2026-09-19): PerformanceStat.Evaluate
|
||||
// multiplies this straight onto the resolved value rather than blending it into the Min/Max interpolation, so
|
||||
// a stat with a PowerSupply term is exactly unchanged at full supply (pow(1, exponent) == 1 regardless of
|
||||
// exponent) and exactly zero at zero supply (pow(0, exponent) == 0 for any exponent > 0), no matter what Min
|
||||
// is -- "a continuous consumer that degrades instead of stopping" down to genuinely nothing. PowerBus writes
|
||||
// PowerSupply below; the resolver invalidates this source once per tick from the same write (PowerBus.cs
|
||||
// AllocateTiers), so this read is always this tick's own grant, never a stale one.
|
||||
public float PowerSupplyFactor(float exponent) => pow(PowerSupply, exponent);
|
||||
|
|
|
|||
Loading…
Reference in a new issue