Combat & survival
Match the blocking symptom to your game version
Check your version before following an old roll/block explanation. The October 16 shared-action design was replaced by separated actions in 1.04 on October 21. A different two-short-sword stuck-pose issue was fixed in 1.05 on October 25. Neither historical report proves the same bug is present in your current build.
On this page
Which report matches what you see?
| Source period | Symptom or rule | How to use it now |
|---|---|---|
| October 15–19, before 1.04 | Roll/block shared an action; shield users reported rolling instead of blocking. | Historical explanation only. Do not force an old shared binding onto a newer build. |
| 1.04, October 21 | Roll and block separated; sword blocks absorb 50% of incoming damage; shield-equipped rolling added. | Consult the current controls and expect a sword block to reduce damage, not guarantee immunity. |
| October 22 report | Two short swords could leave the character stuck in a block pose while still taking hits. | Distinct animation issue, subsequently listed as fixed in 1.05. |
| 1.06 announcement | Stamina added; gamepad interface navigation improved. | No detailed stamina/block cost or universal controller-fix rule is established. |
Check the current setup
- Note the displayed version and whether this is the Demo or full game. Steam’s date alone does not prove which build you are running.
- Check a supported weapon pair, then ensure the intended weapons are actually held.
- Read the block and roll bindings shown by your current build. The historical posts contain conflicting layouts across dates and devices; they are not a current default-key table.
- Observe whether the character rolls, enters a block pose, becomes stuck, or blocks while still losing some health. Those are different outcomes.
Taking damage does not by itself mean a block failed
The 1.04 announcement specifies 50% absorption for sword blocking. In an October 24 reply, the developer says shields have a higher protection value shown in each shield’s stats. Read your actual shield rather than applying the sword percentage to it. These are partial-protection statements, not a promise of immunity; the sources do not provide every attack type, current stamina cost or a complete timing window.
What the historical success reports prove
On October 21 the original player replied that blocking worked after the separation update; another player thanked the developer on October 25. The 1.05 note separately lists the two-sword pose fix. These support the dated fixes. They do not prove every input device and every later build is free of blocking issues.
If blocking still fails in a newer build
Document version, input device, exact pair, active set and the observed action. Include whether a block pose persists after you release the input. Compare with the developer thread and report your current case if necessary. No evidence here supports deleting saves or promising a reinstall will resolve it; the original report includes unsuccessful reinstall and new-game attempts.
Your diagnosis is useful when…
You can describe the actual action and its version, rather than treating all damage or all rolling as one bug. A working sword block can still allow damage; a frozen pose needs a different report.
Sources & version
Source-based explanation; no independent gameplay or file-transfer test. Original source dates retain their scope. Later notes establish the changes they explicitly describe; silence is not proof that every mechanic stayed identical.
- blocking? · original report and dated replies, October 15–26
- blocking? · update and success replies #17–24
- Short sword dual-wielding block bug · October 22 report
- Suggestion: Slow it down! · developer on shield stats, October 24
- Update 1.04 · October 21
- Update 1.05 · October 25
- Update 1.06 · November 3 UTC announcement