feat: add catalog weapon throughput baseline
This commit is contained in:
+10
-6
@@ -25,12 +25,16 @@ The team builds the project in vertical slices.
|
||||
Server code checks authorization for each mutation. UI visibility has no effect
|
||||
on server authorization.
|
||||
|
||||
Builder and shared Build pages currently expose only deterministic totals from
|
||||
the equipped items, selected rolls, fixed bonuses, inherited profiles, augments,
|
||||
and active set bonuses. Conditional Talent outcomes, weapon and Skill DPS,
|
||||
encounter assumptions, activation profiles, rotations, and simulation remain
|
||||
planned. Explicit `COMING SOON` panels identify those player-facing
|
||||
capabilities.
|
||||
Builder and shared Build pages expose deterministic totals from the equipped
|
||||
items, selected rolls, fixed bonuses, inherited profiles, augments, and active
|
||||
set bonuses. Builder additionally shows an experimental catalog baseline for
|
||||
each selected weapon: body-hit throughput from selected weapon damage and
|
||||
catalog RPM, magazine, and reload values only. It is not expected or encounter
|
||||
DPS, does not infer or substitute missing values, reports blocked metrics with
|
||||
their source fields, and does not change shared Build behavior. Conditional
|
||||
Talent outcomes, full weapon and Skill DPS, encounter assumptions, activation
|
||||
profiles, rotations, and simulation remain planned. Explicit `COMING SOON`
|
||||
panels identify those player-facing capabilities.
|
||||
|
||||
Weapon and gear range calculations must preserve decimal endpoints and follow
|
||||
the tested progression rules in
|
||||
|
||||
Reference in New Issue
Block a user