Posted tagged ‘log browser’

World of Logs Log Browser meet Player. Player, meet Log Browser

July 8, 2013

Protip: You can scroll to the bottom of this post (and click on the “Read the rest…” link if viewing from the main page) for an example WITH PICTURES using Eternal Flame and Holy Power.

Megaera’s stupid Diffusion has been keeping me up at night. (Which, I suppose, isn’t necessarily a bad thing. It does means there’s nothing more pressing in my life to ruin my sleep.) But, as a kid, when something bothered me, I was always encouraged to write about it. (With nice handwriting and proper spelling and grammar.) So write about it, I shall. Some day.

It occurred to me first, that I’ve never really written about World of Log’s Log Browser. Since my ripping my hair out probably isn’t the best scenario to cover the basics on (and narrowing in on one mechanic from one fight makes it hard to keep the post up to date), I figured I’d do a little formal introduction to World of Logs’ Log Browser.

Finding the Log Browser.

Finding the Log Browser.

The Log Browser: Why Would I Use It?

The Log Browser is a search tool for the Combat Log.

See, (if it’s still mystery to you,) how World of Logs works is that someone in your raid is saving their Combat Log to a document-type file on their computer. They then upload that file into World of Logs. World of Logs reads it and translates it into those meters, tables and graphs that we love so much.

But! Should you need information that isn’t provided by those meters, graphs and tables, the original Combat Log is still available on World of Logs, through, *drumroll*…. The Log Browser!

Generally I’ll use it for:

Timestamps: When was a spell cast, when did someone take damage, how often does an event occur in an encounter, etc.
Dispels: Who dispelled who, what and when. (Also applies to Interrupts)
Spell Behaviour: If I’m studying a spell and want to know what it did each time instead of the average provided by the spell breakdown page.

And…I’m sure there are other uses, but those are the ones that come to mind. Timestamps tend to be the bulk of my Log Browser usage – it’s the best way to find those extra details about a fight that the basic strat guides don’t tell you.

As for how to get started, use it as you would the “Damage Done“, “Damage Taken“, “Healing Done“, etc. features. Pick a fight (or a boss). In the image above, I’ve got a Heroic Megaera fight selected because blogging has forced my WoW life to now revolve around Heroic Mageara. Then select “Log Browser” from the correct drop down box.

The Log Browser: Think of it as a fancy Google search bar

The Log Browser was probably the last WoL feature I started using because I found it rather intimidating. (I still don’t use the Expression Editor…every time I think “oh the Expression Editor might be useful to answer this question!”, I’m quickly and brutally reminded that I have no basic understanding at all of the language spoken by that Editor.)

Once you get familiar with it, though, using the Log Browser is as easy as Googling yourself.

Your first view of the Log Browser.

Your first view of the Log Browser. I did not censor anything. Please do not stalk my guildies.

The first thing you want to do, before anything, anything at all, is hit “Remove” where is says “Queries Show all events (remove, copy)“.

Reason for that being, until you remove this “Show everything” command, the Browser will constantly just show you everything, ignoring anything you ask of it. This will make you cry (or at least, very, very sad). I have much experience.

As for those buttons along the bottom, here’s a quick translation of what they mean, in Google terms:

1- “Add Query” means “Search bar will pop up”
2- “Run” means “Google Search”, or “Enter”
3- “Copy Query set” and “Paste” are, well, copy and paste options that you’ll find useful if you expect to redo the same search in the future.

So after removing the “Show Everything“, hit “Add Query” to get the action started.

Next step is don’t panic! The form looks a lot worse than it really is.

Using the “Add Query” Form

It looks all tough but it isn't.

It looks all tough but it isn’t.

1- Event Type: This is to either widen your search (example: search for all Summons), or narrow it (example: search through a mage’s casts and only show misses). You can check as many or as few boxes as you want, depending on what you’re looking for.

2- Actor: You would put a character’s name (either a player or an NPC) here if you want to search through all the lines of the Combat Log where that character is mentioned, regardless of whether they were on the casting or the receiving end (example: if I want to look at all heals I cast as well as all heals that were cast on me, I would put my name in the “Actor” field). You’ll probably leave this field blank most of the time.

3- Source: This is where you’d put the name of the character doing the thing you’re interested in (example: if we were to look at all the heals I cast, we would put my name in the “Source” field).

4- Target: You’d put the name of the character on the receiving end of the event you want to study (example: if we want to see all the times I took a fireball to the face, we’d type in my name in the target field)

5- Spell: Enter the name of the spell you want to observe. The field seems to be case-sensitive so you have to type them exactly as they’d be written in your Combat Log (or Wowhead) (example: if we’re interested in Light of Dawn, we’d type in “Light of Dawn” with L and D capitalized).

6- Spell ID: If you aren’t having luck with a spell name (it happens sometimes), you can use the spell ID number. You can find that number on Wowhead in that spell’s URL (example: for Diffusion, use Spell ID 139993).

You can enter more than one name in each field, as long as you separate them with a comma and no space (example: if I wanted to look at Holy Shock and Eternal Flame, in the spell field I’d write “Holy Shock,Eternal Flame).

You can also leave fields empty if they won’t help you narrow your search to the data you want.

Log Browser: The Limits

The Log Browser is awesome, but there are a few limits to what it can do. (The gaps in the Log Browser functions are probably filled by the Expression Editor, but the Expression Editor is beyond my humble abilities.)

– It can only show a certain number of lines, starting at the beginning of a fight/time selection. So unless you’re looking for something that happened very early on, you have to be specific in your searches.
– You can’t automatically search for specific Timestamps. There is no way to see all and only the events that happened between 1min30 and 1min36.
– The Timestamps don’t line up exactly with the times shown in the graphs elsewhere in your parses. The graphs are more like approximations, so expect some discrepancies when comparing log timestamps to graphs.

You can, however, somewhat bypass the first two limits by going to a graph page (Damage Done, Healing Done, etc), selecting a period of the fight you’re interested, right clicking on the highlighted zone and hitting “Set page to selection”. From then on, WoL (including the Log Browser) will look at that selection instead of the whole fight. (Huuuuuge thanks to Kurn for teaching me that. I owe you one!)

And the rest is just practice and creativity!

For visual types (like me), there’s a fun (by my standards) example after the cut.

(more…)

Preparing a Fight with World of Logs

January 28, 2013

When I want to really prepare for a fight, I don’t watch dozens of videos, I don’t compare various guides. Nope. When I want to go above and beyond to prepare for a fight, I go to World of Logs.

It can be more time consuming, but the depth of information is priceless. Plus, for those of us who need to apply knowledge in order to learn (if you were the kid who taught themselves math in high school by doing the exercises before reading the theory, WoL fight preparation is for you!), I find it’s the only way to get a solid idea of the fight before the pull.

Since I’ve been studying WoL a lot lately (and spamming posting my findings on my guild forums), I figured I’d share my approach, in case some of you would like to give this method a try.

Note that my strategy for tackling logs varies a bit from fight to fight depending on whether I want to observe general damage patterns, tank healing strategy or boss mechanics. It also depends on how much I already of the fight (learning the heroic version vs a completely new fight).

Together, you and I are going to prepare for Heroic Imperial Vizier Zor’lok.

1- Decide what we’re looking for

If you don’t know what you’re looking for, you won’t find it!

Let’s figure out our needs:

1) We (I) already know this fight on normal so we’re not too concerned about mechanics.
2) We know that this is a “heal through Force and Verve and don’t get hit by disks” fight so we’re not too interested in general healing strategies.
3) We do, however, want to get an idea of the overall damage patterns so we can choose our glyphs, talents and plan our cooldowns.

Now that we’ve figured out what we’re looking for, we’ll know not to waste time on individual healer spell breakdowns or incoming tank damage logs.

Instead, we’ll probably spend a lot of time looking at the “Total Damage Taken” graph and matching the spikes with the boss abilities from the Log Browser. We’ll probably also look at the “Deaths Overview” page to see what attacks tend to kill players. We might also want to compare a tank and a non-tank’s Damage Taken graphs with the Total Damage Taken graph.

If this is gibberish to you, don’t worry, I’ll explain it all in time.

2- Collect some background information

It does help to review a strat guide to get an idea of spell names (and general mechanics if this is a completely new fight) before perusing the logs. Even if you can’t understand general strat guides (I usually don’t), keep them opened in tabs for references.

Let’s open the Icy Veins strat and Pardeux’ strat.

3- Find some Logs

findinglogs

To find logs, select the fight (1), the size/difficulty (2) then the link to the kills (3).

To get a decent idea of what you’ll be facing, you’ll want to pick the logs of:

1) A recent kill (patches and hotfixes constantly change fights).
2) A kill in your language (it’s a lot of extra work to decode a foreign spell names).
3) A kill from a guild with comparable dps/healing strength.

findingguild

There are 106 pages of Vizier kills and I know my guild struggles a bit with dps performance, so I’m going straight to my URL bar (1) and to enter page 101 (if you’re not sure of the URL, go to the very bottom of the page and click on the “next” link on the far left. That will bring you to page 2. Then go back to your URL and replace “2” with “101”.)

The “US Guild!” logs seem perfect – fairly recent, in my language and probably in my guild’s dps range.

I’m going to choose logs from another guild in the same range as well for comparison purposes. I’m also going to pull up logs of a recent kill by a top notch guild (in the first 10 pages of the kills list) so I can see how the fight looks when executed perfectly.

4- Note the Length of the Fight

Our “comparable” fights:

fightlength1
fightlength2

And our “top notch” fight:

fightlength3

Building our strat: Knowing the fight varies between 7 and 10.5 minutes is important for cooldown planning. Because the fights are long, we know we can use our “long” cooldowns like Guardian of Ancient Kings twice, and our “medium” cooldowns like Avenging Wrath or Divine Favor at least twice, preferably 3 times.

5- Look at Damage Taken

findingdmgtaken

If you choose Damage Taken from the dropdown bar, you’ll get a graph with a lot of lines. Scroll down to the list below the graphs and uncheck every box. You’ll end up with graphs like this:

dmgtaken1
dmgtaken2
dmgtaken3

The first two are our comparable guilds, the last is the top notch guild.

These graphs make me giddy because they are very much alike. Which means the damage patterns will look like this: spiky at first, then a lull with possible minor spikes, then several intense spikes for the last ~1/3 of the fight.

See the 5 buttons on the top right corner, just under “Total”? You can play with those to check who died to what and when, verify when adds die (not shown in the images I posted, but there are 2 adds in the fight) and show/hide heroism (heroism is shown in the images as the large blue bar).

Building our strat: This fits perfectly with our cooldowns! We’ll pop Guardian of the Ancient Kings and another cooldown for the first major spike. We can use other cooldowns if there are spikes during the “lull” phase, and all cooldowns should be ready for use by the time the final spiky phase comes along. As well, spikes mean we’ll probably want to spec into Holy Avenger for the yummy burst healing.

6- Match up Damage Spikes to Boss Abilities

findinglogbrowser

Open the log browser.

logquery

Once you’re in the log browser, remove the current query (1) (I’m not sure why “Show all events” comes up by default. It did take me a long time to figure out how to use the log browser because of that.) then hit “Add Query” (2). Once you’ve entered your query, hit “Run” (3).

addquery

When you hit “Add Query”, the “Add Query” window pops up. The log browser only shows a limited number of lines so you have to be specific in what you’re looking for. It does take a little practice to become good at finding what you’re looking for but once you figure it out, it’s simple.

For this analysis, I want to look at spells cast (1) by the Source Imperial Vizier Zor’lok (2) (note: spelling is important when using the log browser). Then I hit save.

zorlokcasts

After running the query, the log shows all of Zor’lok’s casts.

The rest is just matching up the spells to the Damage Taken graph. Note that there is often a 5-15 second difference between the timestamps on the log browser and the timestamps on the graph, which can be frustrating and confusing.

We can conclude that all the first minor spike is probably Pheromones of Zeal damage (I would guess comparable guild #2 started the fight on the first platform, hence why they only have one spike at the beginning while the other guilds have 2 spikes), the second is Force and Verve, small spikes in between are people getting hit during Attenuation, medium spikes are likely Converts and the major spikes at the end are Force and Verve during the final phase.

Building our strat: Force and Verve is going to hurt a lot, so we should be ready with our cooldowns as soon as he starts casting it. We also know that Force and Verve and Attenuation are physical damage so Devotion Aura will be useless against them (Devo Aura might be helpful would be during the transition between platforms or MAYBE during Convert, since those are the only times any Magic damage will be going out). Hand of Protection, however, might be nice making Clemency an interesting talent choice. We should glyph Divine Protection, and we could combine it with Unbreakable Spirit instead of choosing Clemency as well. Because Force and Verve is AoE damage while we’re grouped up, Light’s Hammer is a good talent choice too. Holy Prism may also be an option, though I’m feeling more Light’s Hammer.

7- Peak at the Deaths Overview

deathsoverview

The deathlog is probably my favorite part of logs because it shows you who dies to what and when. During post-raid analysis it quickly tells you who’s dying to avoidable damage. In a pre-raid analysis, it tells you which abilities to be ready for, and helps you differentiate deadly abilities from abilities that just hurt a lot.

In this kill, 10 players died to Attenuation, 10 died to Force and Verve and one tank died to normal melee damage.

Building our strat: This just re-enforces what we already know: Force and Verve is going to hurt (so all CDs, talents and Glyphs toward burst healing and reducing physical damage), and we should concentrate extra hard during Attenuation.

Conclusion!

There you have it! We’re set for Imperial Vizier Zor’lok!

And for your enjoyment, attached is a copy of what I posted on our guild forums. (more…)


Follow

Get every new post delivered to your Inbox.

Join 1,970 other followers