giftbasket.blogg.se

Wow classic logs
Wow classic logs








wow classic logs wow classic logs
  1. #Wow classic logs how to
  2. #Wow classic logs update
  3. #Wow classic logs full
  4. #Wow classic logs code

That's just how the game is now for classic. I don't play classic but it seems like the meta slavery/toxic parse culture is even worse on classic, is that not against the spirit of the game back then? Remove Living Constellation (ID: 33052) and Dark Matter (ID: 33089) from damage doneĪs always, thank you for reading and participating! We would love to hear your feedback or if you have any questions, please reach out on Discord!.Only count the damage done to the first 8 Guardians of Yogg-Saron (ID: 33136) OR IF NOT POSSIBLE: remove P1 and remove the damage done to leftover Guardians of Yogg-Saron (ID: 33136) OR exclude damage done to Guardians of Yogg-Saron (ID: 33136).Hard Mode only: count damage done to Saronite Animus (ID: 33524) OR remove the boss from all rankings.

#Wow classic logs full

  • Remove damage done to her until the last time she healed to full hp.
  • ? remove damage done to Feral Defender (ID: 34035) ?.
  • Normalize damage done (divided by 2) while under the influence of Overwhelming Power (ID: 61888).
  • Remove damage done to boss mobs before they heal up when one of the other boss mobs dies.
  • Remove P1 (ends when first interaction with Razorscale happens - like Gothik) and remove the damage done to leftover P1 adds (IDs: 33388, 33846, 33453) OR remove the damage done to adds (IDs: 33388, 33846, 33453).
  • This would be to prevent snapshotting of the Slag Pot debuff to be required to parse as a DK.
  • Invalidate parses if Death Knights use "Summon Gargoyle" (ID: 49206) or "Army of the Dead" (ID: 42650) or "Raise Dead" (ID: 46584) while they have the buff "Slag Pot" (ID: 62717) OR (worse option) invalidate parses of all Death Knights who get the buff "Slag Pot" (ID: 62717).
  • Only count the killing blow on Iron Construct (ID: 33121) from damage done OR (worse option) remove the damage done to Iron Construct (ID: 33121).
  • Fight removed for DPS/HPS - likely staying for Speed.
  • #Wow classic logs code

    Please keep in mind that this is a community drafted proposal, and changes are likely depending on combat log and code restrictions. All the current buff restrictions will apply to parsing in Ulduar. The first proposal of adds excluded and various other rules are on Discord. Parsing RulesĪs seen in the Naxxramas Parsing Rules article, there are a number of boss changes and items/buffs, etc banned. The simplest solution here is just to give full credit for the highest hard mode level and to add a 5 minute penalty if you do not do the hardest mode of a boss. Our current thinking is that we will apply time penalties for any boss that has a Hard Mode but isn't killed on that Hard Mode. Starting on the death would require completely new code, and we are not sure if we will have the time to implement this. The starting point will likely be Flame Leviathan pull, potentially death. Ignis, Razorscale, and Auriya are optional bosses, and those have historically not been included. There are a couple of main questions for Speedruns in Ulduar below.

  • 4 Lightning Charged Iron Dwarf (ID: 34199).
  • The optional bosses are Ignis, Razorscale, and Auriaya, they are not required, as optional bosses have never been required for progress previously. See below for what each boss and difficulty awards. The current plan is to have a point system to track progress.

    #Wow classic logs how to

    ProgressĪs Ulduar is the last raid before Blizzard implements a difficulty selector, we have to figure out how to deal properly with Hard Modes. You will not be able to sort by hard mode difficulties on PTR logs. PTR logs from Ulduar testing can be found here, or at the bottom of the front page, once raid testing is live. Feedback is appreciated, so please join us on Discord to discuss. Please keep in mind this is all work in progress. Please check out the #wrath-raid-discussion channel for the Ulduar specific posts. We are currently using Forum Channels on Discord to make it easier to navigate and get updated on the relevant discussions. Ulduar Support / FeedbackĪs always, please join us early in discussing the upcoming raid, both for progression and individual boss rules. Hopefully, this post will clarify our perspectives and what to expect going into the next WotLK raid. Our team is currently incredibly busy dealing with Dragonflight release and Christmas, but discussions are in progress regarding Ulduar and how that will be handled.

    #Wow classic logs update

    We are back with another update for those who don't keep up with Discord and the discussions between phase launches.










    Wow classic logs