Patch Notes Playbook

Example inputs

Paste the patch notes you want analyzed: Fictional game Emberfall, patch 1.4 (test fixture). Shield Bash cooldown: 12 seconds -> 15 seconds. Guard duration: 4 seconds -> 5 seconds. Shield Bash damage is unchanged. A bug that could trigger two cooldown resets from one parry is fixed. No release date supplied.

Your role, build or usual strategy: Support shield build in co-op. I used the occasional double reset for burst and usually need protection during ally revives.

What can you change?: No new unlocks; preserve support role. 30 minutes available. I have no recorded pre-patch test data.

Generated example

Emberfall Patch 1.4 — Support Shield Build Briefing

What changed for you

| Change | Source excerpt | Interpretation | Confidence |
|---|---|---|---|
| Shield Bash cooldown 12s→15s | "Shield Bash cooldown: 12 seconds -> 15 seconds" | Sustained cast rate falls: 12/15 − 1 = **−20%** casts over time in steady-state (excludes resets/encounter effects). Damage unchanged per hit, but with fewer casts, DIRECT: total DPS from this ability drops in sustained use, even though per-hit damage is flat. | High |
| Guard duration 4s→5s | "Guard duration: 4 seconds -> 5 seconds" | (5−4)/4 = **+25%** uptime per activation. INFERRED: more forgiving window for covering ally revives, your stated priority. | High |
| Double cooldown-reset bug fixed | "bug that could trigger two cooldown resets from one parry is fixed" | DIRECT: your occasional double-reset burst option is removed. INFERRED: this does not confirm single resets are now guaranteed or more consistent — reset frequency per parry is unknown. | Medium |
| Shield Bash damage unchanged | "Shield Bash damage is unchanged" | Per-hit number is flat; do not treat this as unchanged DPS given the cooldown increase above. | High |

*(No unlocks, release date, or other changes were supplied — none invented.)*

Keep, change, test

• Keep: Guard as your revive-protection tool. The +25% duration directly supports your stated need to shield allies during revives; no comparison needed since this is a straightforward duration buff on your existing habit.
• Change: Stop planning around double-reset bursts. That path is patched out; do not substitute an assumed single-reset burst rhythm since reset reliability per parry is not stated.
• Test, don't assume: Whether to time Shield Bash on cooldown vs. hold it for parry-triggered resets is unresolved — these two approaches haven't been compared, so neither is the established safer default yet.

Next-session test

Time budget: one 30-minute block (no retroactive pre-patch comparison possible; no baseline data recorded).

• Constant: Same co-op content/encounter type, same build, same 30-minute session.
• Variable: Split the block into two back-to-back segments (e.g., 15 min each) — Segment A: cast Shield Bash on cooldown only; Segment B: hold for parry opportunities.
• Record: number of Shield Bash casts, number of parries landed, number of resets observed, number of ally revives shielded successfully by Guard.
• Decision trigger: if Segment B yields meaningfully more casts or successful revive-covers than A, favor parry-holding next session; if similar or fewer, favor on-cooldown use. One session is not statistical proof — treat as directional only.
• Optional future work: repeat across multiple sessions before treating either approach as confirmed.

What the notes cannot tell us

• Reset frequency per parry: not stated whether resets are guaranteed, chance-based, or conditional — cannot plan burst timing around this.
• Revive duration: exact ally revive time isn't supplied, so we can't confirm Guard's 5s fully covers a revive window.
• Net build strength: with no pre-patch benchmark and unknown reset rate, overall support-build power (better/worse/neutral) is undetermined — do not infer from cooldown/duration numbers alone.