This brief uses information visible on the official Steam listing as of July 15, 2026. Exact inputs, timings, stats, item names, and encounter outcomes stay unpublished until they can be tested after the July 23, 2026 release.
What Steam confirms
The official Dinoblade description explicitly tells players to time dodges, rolls, and parries while chaining combos and using skills. That confirms the three defensive actions exist. It does not confirm that they share a resource, cancel attacks, grant invulnerability, or work against every strike.
| Action | Confirmed before launch | Launch verification |
|---|---|---|
| Parry | Named as a timed combat action | Input, window, valid attacks, result, recovery |
| Dodge | Named as a defensive movement action | Direction, distance, resource cost, cancel behavior |
| Roll | Named separately from dodge | Input, distance, recovery, practical use cases |
A safe practice order
- Confirm the bindings. Read the final control menu and tutorial. Do not assume dodge and roll share an input.
- Test distance without an enemy. Use a visible landmark to compare displacement and recovery for each available movement action.
- Observe one enemy attack. Watch its start, travel, and recovery before trying to defend.
- Try one response repeatedly. Change timing gradually and record success, failure, damage, and position.
- Repeat with a different attack. A result against one move does not establish a universal rule.
How to document timing without fake precision
A useful guide should distinguish visual cues from measured timing. Before frame-by-frame capture is available, describe the cue that starts the test and the visible result. Do not publish a frame count from a trailer, compressed clip, or inconsistent performance.
- Record the enemy animation or effect used as the timing reference.
- Note whether the game was running consistently and which input device was used.
- Repeat the same test enough times to separate a pattern from chance.
- Recheck after patches that mention combat, animation, input, or performance.
Exact parry windows, invulnerability frames, and stamina costs remain unverified until hands-on testing of the release build.
Launch-day verification sheet
| Test | Evidence to capture | Publish only after |
|---|---|---|
| Parry timing | Repeated attempts against the same clearly identified attack | Consistent result across multiple trials |
| Dodge safety | Damage and position before and after contact | Different directions and enemy attacks are compared |
| Roll function | Distance, recovery, and resource display | Behavior is distinct from dodge in the final build |