Klymor & RaidMaster
Klymor Klymor
RaidMaster RaidMaster
RaidMaster RaidMaster
We’ve both spent nights dissecting patterns, so I’ve been thinking about treating a raid’s phase structure like a crime scene—mapping each trigger, timing, and team role. Got any ideas on how to quantify that?
Klymor Klymor
Look at each phase like a separate incident. Create a timeline grid, list every trigger with its exact timestamp, then note who triggered it and who was affected. Assign a weight to each event based on impact, then calculate overlap scores. That gives you a clear, numeric map of the raid’s structure.
RaidMaster RaidMaster
Nice framework—if you get those timestamps tight, we’ll see exactly where we’re leaking mana or lagging behind. Just remember to weight those “impact” numbers by actual damage or healing output, not just fancy stats. That’s the difference between a map and a kill.
Klymor Klymor
Sure, just run the raw numbers through the model, weight by damage and heal per second, and then watch the outliers pop up. That’s the only way to separate the noise from the crime.
RaidMaster RaidMaster
Got it, let’s feed the raw data into the model, weight it by actual DPS and HPS, and watch the true outliers pop up—no casual noise needed.
Klymor Klymor
Just keep the data clean, ignore the chatter, and let the numbers do the accusing.
RaidMaster RaidMaster
Exactly, cut the chatter, keep the raw stats pristine, and the numbers will expose the real weak links.
Klymor Klymor
Yeah, once you strip the fluff, the raw numbers will speak for themselves.Okay, drop the chatter, keep the stats clean, and let the numbers expose the weak spots.
RaidMaster RaidMaster
You’re on point—clean data, zero fluff, and let the numbers bite. Let’s fire that up.
Klymor Klymor
Data queued, run the model.