Well, for those of us in US, this last weekend was Memorial Day! Despite the holiday weekend, we still filled Sunday night's raid. We had quite a busy weekend- some folks working on achievements, some old world content, and 10 man Ulduar as well. We finished up Nax, and got some of our casual raiders into the mix. There were some nice gear upgrades for some folks, and some nice offspec pieces to be had as well. We even rounded out recruitment, with just one position open- a mage slot. With the next upcoming month, I suspect we'll be seeing great progress in Ulduar, but at least for now, if nothing else we are consistent.
Tuesday, May 26, 2009
A Great Holiday Weekend!
Sunday, May 24, 2009
Off Night Fiascos
remember when if you pulled 3 core packs it was sudden death?... and then wrapped that up with Rag's defeat.. which I might add still looks as epic as ever!
This followed an adventure into BWL.. but first we had to attune a few people.. so while a small group ran UBERs,, (remember that?!) We had a dance party!
We crafted a few cloaks.. and away we went to BWL...
Wednesday, May 20, 2009
WWS != meters
Originally posted on our forums: Posted: 02 Apr 2009 08:52 pm RECAP: Interpreting WoWWebStats
Here's a write up I found about Wowwebstats that may explain more about this tool to everyone and how to read it.
You can link either the anonymous version of the report (which will use fake names and not link Armory profiles) or the 'private' version to the forums. IMO, more information is better, so unless you are doing this without the consent of the guild leaders, there isn't a really good reason to hide specs and gear. Allowing people to see specs and gear will eliminate the uncertainty when judging actions, otherwise we can't criticize a player for using a skill they didn't put points into.
WWS records DPS during DPS time, which will result in a different number than recount or Swstats which will record DPS over the time of the boss fight. As a result, there are two other numbers which become important for WWS, presence and DPS time. Presence is how much of the fight the player spent alive. DPS time is how much of THAT time the player spent DPSing. This will vary from class to class and fight to fight, but it should not vary too much between players of the same class doing the same job.
Non-damaging debuffs are not necessarily recorded as attached to a specific player, so if a warlock doesn't show a curse active, it may be because he kept up a non-damaging curse. In order to check to see if non-damaging debuffs have been put up, click on the "Raid and Mobs" section, then lick on the boss, and scroll to debuffs.
Healing meters may not show the full story, if you want to check healing assignments, click on the "Who Heals Whom" page. You will end up on a spreadsheet with healers on the columns and healing targets (including those healers) on the rows. Their "focus" is listed as well. The focus is a measure of how "focused" (for lack of a better word) a healer is on a single target. If you assigned a MT healer and that healers focus isn't the MT, talk to him.
Reading WWS
Clicking on a single player's name in WWS will result in a breakdown of their damage done, heals, buffs and debuffs. Let's look at a specific character
We can see percentages of damage done, crits, and misses. When WWS records a 'miss' and generates a miss rate for a spell or a physical attack, it is just counting your misses (which will be shown on the combat log as full resists if you are a spellcaster) and dividing by the total attempts. The miss rate should approach your theoretical miss rate (so 1% if you are hit capped), but does not need to be close.
If you click on an ability, you will find a breakdown of partial resists, blocked attacks, parries, dodges, and so forth. This also works for incoming damaging attacks to see how many crushing blows a tank took during a fight or what their avoidance was on average. Scrolling down, we find that we can see how many time a player clicked an 'on use' trinket, assuming we know the name of the effect the trinket causes. We can also find out how many potions, healthstones, mana gems, or other abilities the player used. Remember, WWS uses the names that the combat log uses, which may or may not match the names we use for them in conversation.
You can read DoT uptime from counting the DoT ticks and multiplying by the period of the dot (how often it ticks). This is NOT an optimal solution, because if dots are refreshed early or dispelled by the boss, you may have different values for estimated and actual uptime. If anyone knows a better way to figure DoT uptime, let me know.
What you CAN'T read from WWS
You can't tell, directly, the group makeup from WWS. This is why it is important for you to post what the raid groups were in your request for help. You can guess at who was with whom by seeing who received certain groupwide buffs (FI, Battleshout, Heroism/Bloodlust, etc.) and auras, but this is wasting time that is better spent looking for other things.
WWS handles buff uptime poorly because the combat log handles it poorly. If you refresh Battleshout before it expires every time, then it is entirely possible that WWS will show "Battleshout: 1" under the buff category. Similar problems exist with recording debuffs on a boss that are procced by abilities but meant to be maintained the whole fight, like Scorch. The debuff for Scorch shows up as "Fire Vulnerability (Stacksize)" (Where the relevant number is inserted for stack size. For a fight like Netherspite, having Scorch up 3 times may mean that the fight went through three portal phases—in this case, looking at the combat log, that is true. For other fights, a large number of scorch debuffs recorded may mean that the raid isn't keeping it up, this is very fight dependent.
WWS cannot tell you max health, minimum health or max/min mana. You can not tell strictly from the charts if an arcane mage is potting/gemming correctly or only when he is OOM. You cannot tell if a tank was kept full or barely above 75% for the duration of the fight. Assuming that the players from the raid logged in their buffs and in their raid gear, you can extrapolate some of this information, but it isn't worth it for most of the cases.
WWS does not record latency, so you can only tell from DPS time and combat logging if players are using macroes/stopcasting/etc. If you look at percentages, you may be able to tell the player's specific rotations, or area for improvement in rotations. This is merely another tool to allow players to improve their overall performance.
Things to add.. DejaWoW, World of Logs, and WoWMeterOnline also break things down differently.
There's a raid analysis section. From reading WWS, I can see what buffs were had, what people died from, or if they killed themselves.. i.e. tapping when too low on health.
By looking closely, I see about what rotation you are. Some sites are incredible analytic for spec and rotation that should be kept up, even coming close to providing %. This will tell you alot about playstyle. For example, compare my healing with Spans. I guarantee he spams CH alot more (Chain heal for you non healing types) where as I use Riptide alot in pinches and I believe I keep ES (Earth shield) up.
We have vastly different playstyles. Everybody does. Rotations are something that can be consistent- more for dps, but also, healing can change up alot depending on the fight. You can look at specific fights and see decursing etc, who heals whom, etc.
These are not just METERs, they are far more than meters, they are tools. If someone is better, (and there's always someone better), you can learn, if not from them then at least from their meters.
It's not a competition. It's about working as a team- if the goal is to live, the massive amount of DPS you did in the 10 sec you were alive DOES NOT MATTER. DPS and HPS do not matter. What it boils down to, is this is a tool that you use to learn from your mistakes.
This site does a great job of explaining how to interpret raid analysis tools.
http://www.worldofraids.com/forums/showthread.php?t=22022
An easier way to navigate the WWS meters.. there are two links in the above link that explain this far better than I can.
Being Prepared
Well, it's been a bit since I've posted here and I'm working on cleaning out old topics on our forums. I'm going to archive some of those topics on our guild blog. Here's a good one, amended to reflect current changes. Original Post Posted: 23 Feb 2009 09:48 am
Being prepared is not just about flasks.. or food, it is also a certain level that you must commit to, in a much similar fashion that one does when he/she has a job. You have a certain time that you have to be to work. You better show up properly attired, and you better keep gas in your vehicle, or money to buy gas to get to work or your job may be at risk.
The same is true in correlation for raiding. Of course, if you read through our policies, you find that we EXPECT to make the first pull at 6:30. The expectation is that you are online and ready to raid 15 minutes prior.
The policy also states that we expect you to be at the instance- admittedly this one has been hard as of late, due to the fact our schedule has been bouncing around on what we are raiding. That schedule is something else I'm updating. Composition and attendance provided, we will focusing on Ulduar
Bonus EP and Penalties are about to be changed. The full impacts of those changes have not been fully decided upon. Attendance has become flighty. We always seem to end or be close to a full raid by the end of the night. What we have to allocate is simple- a full group. The On Time Bonus is going to be re-defined.
In our current policy, we state to be prepared and ready. Let me clarify exactly what is meant by this. This guild raids 4 nights a week, for a total of 13 hours. This is less than a part time job, if you want to look at raiding in that perspective. You're in this guild because you want to be, because you want to raid, and to do so competently. That means you have agreed to our raiding terms:
• Be online 15 minutes prior to the raid start time
• Be available – this means don't say, hey, hold up- I'm doing OS 10 really quick or Vault, or finish up a BG. This is rude behavior to the other 24 people waiting on you. It isn't just your time if you have committed to be in the raid and available for it.
• Be fully repaired-
This one is common sense. If you go to a raid, you show up fully repaired- that's 100% durability. No one is here to babysit. This will be checked at the beginning of every raid- and if you aren't repaired, it will be noted.
• Bring your food buff/flask/elixirs/bandages/potions.
Do I expect you to pop it on a Nax run? Flasks- no, but this goes with raiding. You should have these items ready for any raid. Several guild members assist me with helping to supply the raid with fish feasts, but you should still keep a stack of food for buff in the event you die and the raid doesn't. Our raid nights are pretty much set- so you should always have flasks/food available at that time.
• You should - at a minimum - be in Dalaran, if you are unsure of where we are going, if not outside the raid instance. Do not expect a summons. If you are going to be late or close on time, get prepared, and log out by the instance.
• The Cost of Epix/Purplez – The cost of getting gear and raiding is time and gold. Why did I say time? Because it takes time to farm mats, ply your trade to make money, or doing dailies so that you have gold. Why did I say gold? Gold is needed to be able to enchant items (the guild bank offers some high prices items at ½ going AH rate), get the consumables you need if you aren't farming them, and have money to repair. This is a guild that consists of mature members, 99% adults, and with jobs/real lives/ significant others. We all have other obligations/duties. This aspect of the game also goes along as the cost of raiding. There is NO valid excuse not to have these items covered. Gold is easier to come by now than it has ever been. The AH is another avenue to make money. If you need pointers, please make a post.