How should I read block, parry and stamina numbers?

The 0.1× value applies when the hit is registered by the parry hitbox. It does not apply to every hit while holding a defensive item, and it does not replace body-area armour. Record whether the test was an ordinary hit, a block or a confirmed parry before comparing damage.

A shield or weapon can also list block and parry stamina properties. Those values describe resource costs or modifiers, not another flat armour percentage. Open the specific equipment record instead of applying one generic shield rule.

At the unmodified baseline, 200 divided by 7.5 is about 26.7 seconds of configured sprint cost, and the same arithmetic applies to recovering 200 at 7.5 per second. This is a reference, not a live stopwatch promise.

Attacks, blocking, dodging, delay, equipment and encumbrance share or modify the same practical budget. Do not spend the last stamina on one extra attack if the plan still requires disengaging, turning a corner or reaching an exit marker.

Use the same enemy attack, armour state and equipment condition when comparing a shield, weapon or skill. If several variables change together, a lower health loss does not prove which one caused it.

Use the listed base values to plan, then judge timing, recovery, remaining stamina and whether the parry actually connected in the game. If several things changed at once, repeat the test before replacing your whole setup.

A useful comparison starts from a repeatable failure: the same named attack breaks the guard, a sprint leaves no stamina for defence, or a parry is consistently late. Record that event, change one equipment or timing decision, and test again. This produces a practical answer without pretending that a static number can reproduce every combat frame.