My Account. Remember Me? Need an account? Register Now. Recent Blue Posts 8 hours ago. Recent Forum Posts AM.

Thread: How do I parse high and use this Warcraft Logs thing? How do I parse high and use this Warcraft Logs thing? Exactly the title. Reply With Quote. Shoot the pixels Dumb questions get dumb answers. Nothing of me is original. I am the combined effort of everybody I've ever known. Parsing high is all about using whatever you can to whore out that last little bit of dps and the the 1 factor in a high parse is rng. I had a 58k tectus wipe, next lull was the kill with only 45k.

The big difference is how lucky you can get with mechanics and uptimes, pretty much whore on everything you can and pray to rngesus. Yeah, first factor is rng, sure. If there's more than 2 targets, you Multi-Shot a lot. Doesn't matter if the targets matter. If you can multidot something, do it and don't kill it for more dual-SS uptime.

Originally Posted by Azortharion. Well, knowing how to play pretty good is sort of the obvious unmentioned one, and RNG is out of your control so it's fairly stupid to mention it. The rest you can do is basically beyond your control, such as how quickly your guild kills shit, how high you bother stacking Favor, etc. Depends on the fight. Some you can't really go bigdick beyond the usual at all Butcherothers you can completely fuck fight mechanics and achieve ranks Imperator.

If you're really pro you can disguise your rankwhoring by still being good in places where it matters, such as whoring the fuck out of Imperator phase 4 adds while still somehow managing high damage on Cho'gall. I'm ranked 2 for Mythic and I am a mix. Have your tank keep them pretty close and focus-dump with Multi-Shot on them.My Account. Remember Me? Need an account? Register Now. Recent Blue Posts 8 hours ago. Recent Forum Posts AM. But I have recently been uploading logs for my chars and my friends in our little guild to Warcraftlogs to see how we compare and such.

Mainly is being higher there a better thing? Reply With Quote. Bracket is percentile in your item level bracket. In the example Item Level. So out of people under you got 92nd percentile.

While overall any ilvl it's 80th percentile. Not so many people log LFR though. Last edited by zethh; at PM.

how to read warcraft logs

It's used as an overall ranking of all parses within your spec regardless of item level. There were total parses, and you ranked out of Every 14 levels for Highmaul, and every 7 for BRF. Once you get to item level, you will be in the bracket. Brackets are flawed because there is a huge difference in 14 levels of gear, as you can possibly compete with someone with item level, while you are It's a bit less flawed in BRF as it's only 7 item levels, but they can still make a large difference.

Would be nice to see how many parses there are within what bracket you are in. Last edited by mmocadb88f; at PM. Last edited by Nelle; at PM. Never interrupt your enemy when he is making a mistake. Originally Posted by Nelle. People making logs from LFR reminds me of the quote: "In the land of the blind, the one-eyed man is king! The issue is that it wouldn't be very informative. For the brackets, I allow the same player to have best scores in each bracket, which means that there are still a lot of parses to compare against in a lower bracket even after that person graduates to the higher bracket.By ZagamJanuary 16, in General Discussion.

Zagam here with what I hope to be a long, detailed explanation of an incredible tool to be used in World of Warcraft to analyze, diagnose, correct, and observe anything imaginable. This tool is Warcraftlogs. So, you're interested in getting a better understanding of combat logs? You've come to the right place. First, head on over to www. Follow the instructions to activate your account. Once you do that, log in and click on the button that says "Upload a Log" near the search bar. This will bring you to this screen:.

Once you do that, log into World of Warcraft. You'll want to turn on Advanced Logging which can be found by going into your main settings by hitting Escape. Select System and then Network. There should be an option that is unchecked called "Advanced Logging. When you've closed the logging process or exited WoW, go to upload the log using the Warcraft Logs Uploader. Use the Browse feature to locate the text file. Now it's time to analyze!

When you successfully load your log, you will be brought to a screen that looks like this:. There is a lot info here including the date of the log, duration of the entire combat log file, whether or not this log is private or public and when the file expires.

When rankings are included with Warcraftlogs, they will be found on this screen as well. The default display when you load your log will be that of the last pull you had of the raid. Here, you can see that pull for us is a kill of 12 man Flex Garrosh. Let's take a look at some of the other features in more detail. Notice how incredibly easy it is to see all of the members of your raid without having to hover over their abilities to see what their role was.

Seeing the specialization of each DPS helps get a sense of what a raid group used to down a particular boss. Imbedded into each of the graphs of Warcraftlogs is a tracing feature with your mouse. You can use your mouse to highlight over any portion of the fight for specific details.

You can also see things such as the time Bloodlust was cast, such as in this picture:. Also within the graph's functionality, there is the ability to portion out a part of the fight simply by dragging your mouse from a start point to a finish point or vice versa.

From the previous picture, I've selected only the Bloodlust portion seen here:. You can see in that picture that the DPS of each player below modifies to include the portion of the combat log that falls within this time frame. This is a great opportunity to see who is doing what during Bloodlust such as checking to see if your raid members are using the potions! On the right hand bottom corner of the graph, you will notice a small options bar. It looks like this:. By default, this selects the Bloodlust option which marks a blue portion on your graph which we previously highlighted.

Other options here include battle resurrections, player deaths, boss deaths, and other mob deaths.By PandachoNovember 26, in General Discussion. Compares one full raid report all fights to another. Very useful when you have players of the same spec that are not performing equally. A great option that actually shows you how other players of your ilvl were performing in the same fight difficulty, fight length, amount of raiders.

You can even check whether these players were using the same talents, legendaries, trinkets, etc. This option is much-much better than just picking from random parses or, even worse, comparing to the top For example on this screenshot we can see an enhancement shaman with a very good Legendary.

This is easy enough - take your fight length in seconds and divide it on the amount of ability casts. Let's look at an example in Nythendra Mythic kill log of some resto shaman that were worried about their healing numbers. Fight length sec :. Some players just cast slow. They don't make mistakes in rotation but rather have some kind of a delay between casts while thinking about their next step or trying to change their positioning too frequently.

You can check whether a player was playing 'right' in ' Damage Done ' tab, choosing ' Done to Enemy ' from the dropdown menu. Hovering your mouse above the enemy name will show who dps'ed it. In this case, hovering above every player's name or clicking it you'd be able to see how they split their dps between targets. Very useful for the healers to check their mana management during fights choose 'Mana' from the dropdown menu.

Shows mana spent and mana gained from different sources like trinkets and potions. You should always click on the questioned player name and check the last 30 sec before the death: whether they used personal damage mitigation abilities, healing potions, did they received enough direct healing, etc. You can post now and register later. If you have an account, sign in now to post with your account. Note: Your post will require moderator approval before it will be visible.

Paste as plain text instead. Only 75 emoji are allowed. Display as a link instead. Clear editor. Upload or insert images from URL.

how to read warcraft logs

General Discussion. Recommended Posts. Report post. Posted November 26, There are 3 options of comparison in WCL: 1.Welcome to Warcraft Logs!

This page will help you get familiarized with the Web site and all of its features. You will need an account to upload logs to the site, so if you plan on uploading logs, first create an account. You do need a valid e-mail address, since we verify it via an activation e-mail. After you have signed up for Warcraft Logs, you can integrate your account with Battle.

This gives WCL access to your characters and guilds. You can go to your user settings to integrate with Battle. A combat log is a file created by the game that contains a series of events.

These events contain information such as what abilities your team used, what damage they did and to whom, and what healing was received. The idea behind combat logging is pretty simple: record what happened so that it can be sent to Web site for analysis.

Before doing any logging in World of Warcraft, you need to make sure that Advanced Combat Logging is enabled. This is required in order for logs to be accepted on the site. Go to the Network pane of System preferences in-game. That's all you have to do! Now everything you and the players and enemies around you do will be written to a file called WoWCombatLog.

This file can be found in the Logs subdirectory of your WoW installation.

Getting Started With Warcraft Logs

Outside of raids, the combat log file is only written to when a certain number of events have been generated. This means it can be very slow to update if you are just doing solo content out in the world.

Robot to have logging turn on automatically in raids and turn off when you leave. It is very important when using Warcraft Logs that you log the entire raid though. DBM's auto logging feature, for example, only logs bosses, and this will cause it to not log pet summons. This can lead to problems where pets won't be connected with owners. If possible we always recommend that you log the entire raid night. Do not leave trash and events that occur outside of the combat out of the log. In order to upload logs to the Web site, you use a client application.

This application can be obtained here. If you have any issues getting the application to launch or install, we encourage you to go to the forums for assistance, since it's likely someone else has encountered the same issue and can help. There are two ways you can choose to log.

The first is to upload the entire log file after your raid is over. The second way is to do what we call live logging. In this model, the client monitors the log file and whenever it sees new events tacked on to the end of the file, it sends those events up to the Web site. The live logging mode is great for when you want to study wipes right after they happened to see what went wrong.

You have two choices for where to upload your logs. Every user on Warcraft Logs gets a personal log space just for them, so you can always upload your logs there without ever joining a guild.By KrazyitoFebruary 10, in General Discussion.

If you want information on how to interpret or use the log websites please visit Zagams comprehensive guides Warcraft Logs Comprehensive guide by Zagam First, I will explain how to capture your log data to begin with. The most basic and easy way is to use the command or even macro it. This command will toggle combat logging.

You can use this command before you enter a raid and it should log for the whole night. Each time you log out I think it turns it off and you need to turn it back on. My preferred method is with the use of an add-on. Specifically Loggerhead. This addon will display a pop-up box when you first enter an instance asking you if you would like to log that specific instance. After that it will remember your choice and continue to log or not log when you enter that instance. Next you may want to consider enabling "Advanced Combat Logging" Advanced logging will use more memory and space, but its a really useful feature in Warcraft logs specifically where you can actually "replay" your encounter to see peoples positioning.

Do yourself a favor and turn it on. Robot and DBM also have options for automactic logging. You'll first need to sign up for a Warcraft logs account.

Click it to begin. Simply sign up for an account and verify your e-mail. Of course, this is completely optional, although highly recommended.

After you integrate with Battle. Here is an example of mine. Now that you can log-in you need to download the 'client' this is a program that you install on to your computer which will interpret and upload the logs for you. Simply download and install this program.Today I want to talk about the basics of how to read raid logs. Although the nerdy part is certainly true in my case, anyone can read and benefit from raid logs.

how to read warcraft logs

First you need to record some combat logs. While it is active, it will be saving all combat log data to a file. The combat log will be saved as WoWCombatLog.

1. Getting Started

If you forget to turn on and off logging very easily like I do, I recommend getting the addon LoggerHeadwhich can be set to automatically start logging when you enter specific raids on specific difficulties and automatically stop logging when you leave. Navigate to the the WoWCombatLog. Once it finishes, click to view the log, which will make it open up in your browser. Make sure the log uploaded correctly and has all the fights it is suppose to.

The uploader has a convenient button to do so. If you want to look at it too, you can see the logs here. I can easily see where my DPS was coming from. That says it hit 43 times. The fight lasted for 4 minutes and 37 seconds or seconds. If I divide by 43 I get 6. Since 43 was the number of kill command casts, and was the total time, this tells me that there was an average time of 6.

Since it has a 6 second cooldown, that was pretty good. Now, looking a bit farther down the list I can see my serpent sting. Go over to the debuffs tab, and below where it says my name, change it from friendlies to enemies, like this.

Scroll up to where you can see the new graph created by the pin, and look along the top bar until you see where it says Graph: Seperate. Click on this twice. Once will change it to Graph: Off and the second click will change it to Graph: Main.

Raid Logging Basics

If you have done all of that correctly, it should look like this. Leave that pin alone for now and change it back from enemies to friendlies, and select Elendi from the drop down menu above. Then go over to the casts tab. On the graph on this tab, there should be a long list of different abilities that I casted. Make sure they are all off, except for serpent sting. It should look like this now.

how to read warcraft logs

Now we have this very cool graph here. Each little bar shows a time I cast serpent sting.

The slightly transparent grey areas on the graph show the time that serpent sting was active. You can pretty clearly see exactly when I let it fall off, and how long it took me to reapply it. The first time I let it fall off, it was off for a full 13 seconds. In my next post on this topic I will explore many more ways you can check your performance, beyond checking DoT uptime and time between casts. As always, please contact me if you have any questions.

I am very happy to answer them.