Skip to content

1.32.0: Log Analysis for Fury Warrior; SimC's rotation beside every result - #43

Merged
Roburmaster merged 1 commit into
mainfrom
log-analysis-rotation
Oct 2, 2026
Merged

Roburmaster merged 1 commit into
mainfrom
log-analysis-rotation

Conversation

@Roburmaster

Copy link
Copy Markdown
Owner

Log Analysis: streamed combat log reading (1.3 GB in ~15 s), boss encounters and per-player activity stretches, and a Fury Warrior analysis (Enrage/Recklessness uptime, rage over the cap, unused Sudden Death, Whirlwind buff on several targets, time without a cast, cooldowns together, potion timing) with casts per minute beside a finished simulation of the same character and a cast timeline.

Rotation view: each run saves the action list SimC followed; results show SimC casts per minute, the first minute of its sample sequence, and the APL.

Tested on the 2 Oct Silvermoon log and a 1.3 GB raid log; npm test 220/220, test:ci 205/205.

🤖 Generated with Claude Code

…esult

Log Analysis reads WoW combat logs from the WoW folder (streamed, so a 1.3 GB
raid log scans in about 15 s), finds boss encounters and stretches of activity
per player, and analyses one player's fight. Fury Warrior is the first
specialization: Enrage and Recklessness uptime, rage lost to the cap, unused
Sudden Death procs, single-target attacks on several targets without the
Whirlwind buff, time without a cast, cooldowns used together, potion timing,
and casts per minute beside a finished simulation of the same character, with
a cast timeline. Stretches start 6 s before the first hit so the opener counts.

Every main run saves the action list SimC followed (save_actions), and each
result has a Rotation view: SimC's casts per minute, the first minute of its
sample sequence with rage and key buffs, and the action priority list.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
@Roburmaster
Roburmaster merged commit 38bcc6b into main Oct 2, 2026
5 checks passed
@Roburmaster
Roburmaster deleted the log-analysis-rotation branch October 2, 2026 08:33
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant