The answer first
Attacks do not consume stamina in The Relic: First Guardian; defensive actions and dodging do, while skills use cooldowns instead of a separate resource. Patch 6 widened the parry timing window, and Patch 7 changed lock-on dodging to follow the camera view. The official notes do not publish exact timing values or confirm identical behavior on every platform.
Last updated: 2026-08-08 · The PlayStation developer systems article plus official Patch 6 and Patch 7 announcements. Exact timing values and hands-on combat testing are not claimed.
Which combat actions use stamina?
| Action | Current verified rule | Evidence |
|---|---|---|
| Attacking | Does not consume stamina | RFG-COMBAT-001 |
| Blocking, dodging and parrying | Consume stamina | RFG-COMBAT-001 |
| Skills | Use cooldowns rather than a separate resource | RFG-COMBAT-002 |
These rules explain resource use, not the exact recovery speed, cost per action or result of reaching zero stamina. Those values are not established by the approved source set.
What changed for parrying and lock-on dodging?
| Version | System | Official status |
|---|---|---|
| Patch 6 · Aug. 6 | Parry timing | The parry timing window was extended; no exact value was published. |
| Patch 7 · Aug. 7 | Lock-on dodge direction | Dodging while locked on now follows the camera view. |
The individual patch bullets do not state a separate PC or PS5 scope, so this page does not claim identical behavior on every platform or save.
What should I check when defense feels inconsistent?
- Confirm that the installed game version includes the latest available patch.
- Separate stamina use from skill cooldowns when diagnosing why an action is unavailable.
- For parry timing, note that Patch 6 widened the window but did not publish an exact number.
- For lock-on dodge direction, compare the result with the camera-facing behavior described in Patch 7.
- Record the platform, installed version, enemy, action and repeatable steps if the issue continues.
What is verified
- Attacks do not consume stamina; defensive actions and dodging do (RFG-COMBAT-001).
- Skills operate on cooldowns rather than a separate resource (RFG-COMBAT-002).
- Patch 6 extended the parry timing window (RFG-COMBAT-004).
- Patch 7 changed lock-on dodging to follow the camera view (RFG-COMBAT-003).
What needs more evidence
- Exact stamina capacity, recovery rates and per-action costs are not verified.
- The exact size of the Patch 6 parry window is not published.
- The patch bullets do not establish separate behavior for each platform.
- No universal combat rotation, boss-specific response or optimal setup is verified here.
Should I play more aggressively after learning this?
The verified rule only says normal attacks do not spend stamina. Keep enough stamina for the defensive actions you actually use, and adjust from your own repeatable encounters rather than treating unlimited attacks as proof that constant pressure is safe.
Related Guides
Frequently Asked Questions
Does attacking drain stamina?
No. The registered developer source says attacks do not consume stamina.
Which actions use stamina?
Blocking, dodging and parrying consume stamina in the registered system description.
Do skills use stamina?
The registered source says skills use cooldowns instead of a separate resource.
Was parrying made easier?
Patch 6 says the parry timing window was extended, but it does not publish an exact value.
How does lock-on dodging choose direction?
Patch 7 says dodging while locked on follows the camera view.
Source scope and verification
The PlayStation developer systems article plus official Patch 6 and Patch 7 announcements. Exact timing values and hands-on combat testing are not claimed.
Source IDs: RFG-S02, RFG-S06, RFG-S08
Author: independent site editor · Reviewer: Codex evidence review · Corrections require the page URL, platform, installed version, and a current official or reproducible source. No external game image is used on this page.
What changed on August 8, 2026?
Removed pre-release wording, added Patch 6 parry and Patch 7 lock-on dodge status, and retained the same canonical URL.