Recommended Posts

Ret Pallys have been literally raping DPS since the patch, and do need to get hit by the nerf stick IMHO. Hopefully Ret Pallys aren't nerfed to their spot pre-patch which did have laughable dps.
which is more or less what i said so needless to say i agree with you.

the big thing is all the new instant attacks with low cooldowns. instant attacks + 2 handers = rape. i hope what ends up happening is that they just adjust the numbers so theres not as much burst damage and spread it out over time more. i think that should help.

it can't go back to the way it was before..it just can't. it was really bad before. there has to be happy median and I hope they find it

Best case: in 3 months I'll be having as much fun as I was last week.

And for the rest of the millions of normal humans that don't treat this game like a job, probably much longer.

Sorry, but you "uber" raiding guilds partially create the problems yourselves.

which is more or less what i said so needless to say i agree with you.

the big thing is all the new instant attacks with low cooldowns. instant attacks + 2 handers = rape. i hope what ends up happening is that they just adjust the numbers so theres not as much burst damage and spread it out over time more. i think that should help.

That's what they plan to do:

Divine Storm -- the damage was changed from Holy to Physical. As you know, Holy damage is almost never mitigated and this talent could pack a lot into a very short time. This is a nerf to the ability's damage. This change is now active on Live.

Repentance -- this ability now lasts for only 6 seconds in PvP (down from 10). Obviously this is also a nerf. This change is also active on Live.

Art of War -- now affects all damage done by Judgements, Crusader Strike and Divine Storm (instead of critical strike damage). Net dps should be about the same but less bursty. This change will be made before Nov 13.

Righteous Vengeance -- now applies a dot affect similar to Deep Wounds (instead of critical strike damage). This ends up being a significant buff to the ability to make up for the damage lost to Divine Storm, but is also less bursty. This change will be made before Nov 13. EDIT: The dot will NOT break Repentance.

Glyph of Crusader Strike -- now reduces mana cost (instead of increased damage on stunned targets.) We thought paladins could stack too much damage vs. stunned targets. This change will be made before Nov 13.

We also fixed a bug with Seal and Judgement of Light that could sometimes result in too much healing.

In our tests, Retribution dps remains the same over longer periods of time, but they can't do quite so much damage in the initial few seconds of a PvP encounter.

I dunno, I'll be happy with these changes. Love the ret pally now. :p

They also said a bit about buffing Holy's damage as it seems to be low.

And for the rest of the millions of normal humans that don't treat this game like a job, probably much longer.

Would you describe people who play a round of golf on Saturday and Sunday as "working a second job"? How about taking a trip to the ski hill every other weekend or too the race track every Wednesday and Friday night?

Why is it that when one person plays and has fun it's okay, when somebody else does and has more to show for it: it isn't?

Also, why wouldn't the millions of non-?ber players not start having fun in Naxx shortly after turning level 80 or becoming competitive in Arena? For me it'll be a rehash of content I did years ago but now with training wheels turned on, for them it could be new & interesting mechanics with a pile of story line to go with it.

Sorry, but you "uber" raiding guilds partially create the problems yourselves.

Blizzard took away Sunwell: the only way I could have avoided this would be to start playing poorly, join a much less/slower progressing guild and wait for this patch. As for their being nothing challenging at 80: that's Blizzards fault. The encounters are now under tuned the same way Kara/gruul/mag were over tuned for introductory raids. Likewise Heroic 5-man content under tuned.

If you found Naxx-80 10-man as easy to clear as Karazhan after 3.0 would you find it a rewarding experience? Many people in this thread have stated that killing new bosses at any level of ?kael, illidan, <anything in sunwell>?didn't really have a sense of accomplishment. That's what everyone will be running in to if the level 80 content ships under-tuned.

The relevant abilities are:
  • Blast Nova: 60 sec CD, about 2,500 damage every 2 seconds for 10 seconds to every player in the lair
    When the channel breaks, the player receives the 90 sec Mind Exhaustion debuff

If you can find alternate information for them, I'd love to see them but neither wowwiki nor wowhead have longer durations for mind exhaustion or shorter cooldowns for blast nova.

He was first killed by Nihlium on Feb 25: a video of that encounter shows Awake click the cubes twice in 2 minutes. That demonstrates that more than 2 cube groups has never been a requirement for a kill.

You had me doubting myself then as i couldnt find it anywhere on google lol.. but found it on a nihilum column in the end:

"At number 4: Magtheridon. This old ruler of Outland is supposed to be an entry level raid encounter in TBC, but he certainly wasn't tuned like that. Raids with fresh 70s that had just geared up through Karazhan and heroics were confronted with an insanely overtuned encounter, wiping any raid that even dared to enter the lair. It started with the trash, packs of 3 caster mobs doing AoE fears, 3k AoE shadow bolts and hitting like a truck; with today's standard they should have dropped T6 items. If you managed to kill these packs and reach Magtheridon, you were confronted with no less then 5 of these mobs guarding him. Attacking these guards would start the encounter and Magtheridon would join the fight in a few minutes. To make it a bit harder, these 5 guards also spawned elementals on a regular basis, as they had to be stronger then the normal trash, of course. If you managed to deal with the 5 adds before Magtheridon joined in, then the real encounter could start, the oh-so-feared cube clicking. That part of the encounter is basically the same as today, except that the debuff the player received after clicking a cube was 4 times longer than today, and each cube needed a 4 player rotation on it to stop Magtheridon from doing his AoE. As an extra bonus, Magtheridon would aggro all the trash in his liar, which was on a 1h respawn timer - nothing beats hordes of trash jumping you - while you are fighting a boss of course. Again an encounter that was designed quite ok, but the tuning was just horrible."

Source: http://nihilum.mousesports.com/en/article/...e_money_fails_/

Magtheridon was like that until SSC attunements were dropped, months into the game.. So Casual 25man raiders couldnt do anything as there was abolutly no learning curve.

Given how different our experiences for Magtheridon are, I'm not willing to argue this one out in detail (because so much of it is opinion). But if you go back and read the Gruul thread from elitist jerks (Titled "Dealing with Shatter" or something like that) you'll see a large portion of the raid community arguing that the fight is a consumable extravaganza and little else.

While luck certainly played some roll in the encounter (bad punts) dealing with shatter damage was the key mechanic: if you got lucky, great! but that wasn't the way you were expected to win.

Dont have to go find a source for this, as its the same as the previous one.

Luck was the only way to win on release version of gruul, as you always got to the point where Gruul could oneshot your tank regardless and just had to prey. That still isnt the point i was trying to make about learning curve's.. if the hardcore Vanilla WoW players were struggling to meet the enrage pushing all DPS to the maxiumum on the 2nd boss into the PvE content? wtf was the casual raiders meant to do.. just sit and wait.

At the start of TBC, content was just about banging your head on the wall until Blizzard nerfed it until it was properly. The only problem is that Blizzard realised they was screwing up and under tuned MH/BT when they were instances which could of got away with being overtuned.

Would you describe people who play a round of golf on Saturday and Sunday as "working a second job"? How about taking a trip to the ski hill every other weekend or too the race track every Wednesday and Friday night?

Why is it that when one person plays and has fun it's okay, when somebody else does and has more to show for it: it isn't?

Also, why wouldn't the millions of non-?ber players not start having fun in Naxx shortly after turning level 80 or becoming competitive in Arena? For me it'll be a rehash of content I did years ago but now with training wheels turned on, for them it could be new & interesting mechanics with a pile of story line to go with it.

Blizzard took away Sunwell: the only way I could have avoided this would be to start playing poorly, join a much less/slower progressing guild and wait for this patch. As for their being nothing challenging at 80: that's Blizzards fault. The encounters are now under tuned the same way Kara/gruul/mag were over tuned for introductory raids. Likewise Heroic 5-man content under tuned.

If you found Naxx-80 10-man as easy to clear as Karazhan after 3.0 would you find it a rewarding experience? Many people in this thread have stated that killing new bosses at any level of ?kael, illidan, <anything in sunwell>?didn't really have a sense of accomplishment. That's what everyone will be running in to if the level 80 content ships under-tuned.

What's funny is you act like WoW was hardd. It's a fun game,difficultt it has never been. Ever. Whatever though, may you find happiness in whatever endeavor entertains you.

What's funny is you act like WoW was ever hard. It's a fun game, but difficult it has never been. Ever. Whatever though, may you find happiness in whatever endeavor entertains you.

Clearly there is some difficulty or the 99%+ raid guilds that cleared Karazhan would also have cleared Sunwell.

What's funny is you act like WoW was ever hard. It's a fun game, but difficult it has never been. Ever. Whatever though, may you find happiness in whatever endeavor entertains you.

We don't need to go through this again...the further you progress in the game, the harder it gets. If arena was "easy" I would have an amazing team/personal rating...I don't. If raiding was at all easy past Kara my guild would have cleared Mount Hyjal last night...we didn't.

Maybe for the people who stall out in Kara, it's a cake walk. Maybe for those who stall out in BGs they can pwn face. But if you keep pushing and progressing, you will find new and harder content.

What's funny is you act like WoW was ever hard. It's a fun game, but difficult it has never been. Ever. Whatever though, may you find happiness in whatever endeavor entertains you.

Congratulations on never being in a progressing guild and rather be in one that has everything on farm mode and never having to experience PVP or PUGs. Of course nothing is going to be difficult when everything is basically handed to you on a silver platter...

That's what they plan to do:

I dunno, I'll be happy with these changes. Love the ret pally now. :p

They also said a bit about buffing Holy's damage as it seems to be low.

thanks for posting that! yea those changes would be fine by me too. i'm happy that what they're doing is exactly what i hoped they do - reduce the burst damage and take that reduction and spread it out over time. same dps, just in a longer period. sounds like pvp'ers should be happy by this so they don't owned in 3 seconds.

Hahah yep.

What's funny about it is that I'm only 4/5 in MH and wiped enough times getting there that I'm exalted with Scale of the Sands.

It was a total cake walk, both Vashj and Kael.

I was doing 3k+ DPS with 3k+ Atkpwr at 31% crit rating

Volley is HUGE for AoE'ing as a hunter now. I saw another hunter in raid doing 5k+ but he was 4/8 t6.

grats

Hand of A'dal!

While the official ruling is that you can't get the title any more, if you are on certain stages of the quest chain it's still possible.

Example: If you'd completed the BT attunement chain, but hadn't completed the Hyjal attunement you can still get the title provided you had the quest in your log already. They way no-title-for-you was implemented was by adding duplicate quests with identical rewards/text/etc. that all the NPCs now give out. They won't give out the old ones, but there is some speculation that if you have somebody share them you can still sneak your way into a title.

All the same: grats.

While the official ruling is that you can't get the title any more, if you are on certain stages of the quest chain it's still possible.

Example: If you'd completed the BT attunement chain, but hadn't completed the Hyjal attunement you can still get the title provided you had the quest in your log already. They way no-title-for-you was implemented was by adding duplicate quests with identical rewards/text/etc. that all the NPCs now give out. They won't give out the old ones, but there is some speculation that if you have somebody share them you can still sneak your way into a title.

All the same: grats.

I killed Vashj/Kael after patch. I did the BT attunment chain up to the part where you needed to talk to the guy in SSC. I just got my Medallion of Karabor, and got the title, Hand of A'dal. :)

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
  • Posts

    • Waymo recalls self-driving software after cars enter closed freeway work zones by Paul Hill Waymo, the self-driving car maker owned by Alphabet – the parent company of Google –, has recalled some of its fifth-generation Automated Driving Systems (ADS). It did so after some of its cars drove through closed construction zones. According to the National Highway Traffic Safety Administration (NHTSA), the affected vehicles were capable of driving through a closed freeway construction zone and continuing to drive at speed. The listing on the NHTSA website says that Waymo is currently developing a solution to fix this issue, but in the meantime, freeway driving is being restricted. Waymo will update its ADS software so that vehicles can detect when they can avoid entering construction zones. According to the Safety Recall Report, on April 20, 2026, Waymo’s Field Safety Committee began meetings reviewing an event from April 11, 2026, and five events from April 19, 2026, where Waymo’s autonomous vehicles didn’t recognize and drove past ramp closure signs into the pre-planned freeway construction zones. This took place in Phoenix, Arizona. Separately, on May 18, 2026, seven Waymo vehicles entered freeway lanes with active construction in the San Francisco Bay Area by driving between cones that were placed to show the lane was closed. On the back of both of these events, Waymo restricted freeway driving until it could address the issue. In June, Waymo’s Safety Board reviewed the issue and additional information related to ADS performances around construction zones; then, as a result, it decided to conduct a recall. This development is not good for Waymo as it adds to a growing list of technical hiccups its cars have experienced. Ultimately, it will lead to more scrutiny from lawmakers around the world who will be more cautious about letting autonomous vehicles on their roads without tighter regulation. For readers in areas where Waymo operates, does this news make you more wary about stepping into one of these vehicles?
    • I'm still on Windows 10 22H2 because I didn't want to deal with all the issues in Windows 11, so I waited almost a week before installing the latest Patch Tuesday update (KB5094127), I went ahead and did it, and it was a huge mistake—ever since then, my File Explorer has seen a performance drop of about 30% when transferring large files... Once again, Microsoft has outdone itself! This update cannot be uninstalled, either through the Control Panel (via Settings) or by accessing Advanced Startup Options. The only possible alternative would be to use system restore points, but I’d have to reinstall all app and driver updates (and there’s no guarantee it would work). Or there’s the “nuclear option” of a in-place repair without losing files or apps, but even then, all my customizations would be lost! Microsoft just can’t help but mess everything up! Way to go, Microsoft! But I still don’t want your c****y Windows 11!
    • Microsoft: Windows 11 could finally solve a major issue across AMD, Nvidia, and Intel GPUs by Sayan Sen While Microsoft has been trying to improve it, Windows 11 is definitely not flawless, as even today some issues are taking a year to publicly acknowledge. However, one area of trouble that may finally see much better results soon is graphics driver crashes. Work on graphics driver timeouts, also called Timeout and Detection Recovery (TDR), is not new as the latest WDDM 3.2 also has specific improvements regarding it. Windows Display Driver Model (WDDM) version 3.2 is supported on Windows 11 24H2 and 25H2. However, with the upcoming version 26H2, TDR crash diagnosis could go to the next level as Microsoft is introducing a new DirectX 12 API feature called "DirectX Dump Files". Similar to how system memory dump files work when a system crashes or freezes or encounters any such major issue, DirectX Dump Files (DDF) will essentially record a snapshot of the GPU execution right at the moment a graphics-related crash or hang or freeze occurs, so that developers can better understand and diagnoze these TDR and timeout detection errors. The dump will be available as a .dxdmp file for analysis and it will be a comprehensive dump file generated with detailed insights about the hardware, drivers, Windows, as well as the affected application. This should be another welcome change in this department. Earlier at GDC 2026, when the technology was first debuted, Microsoft had shared more details regarding it. The company had explained how DDF is designed to gather data from every layer of the graphics stack into a single file, eliminating the need for developers to manually correlate logs from multiple tools. As mentioned above, the dump can contain a lot of useful details like GPU hardware state information such as register values, shader program counters, page fault virtual addresses, shader memory data, and command buffers. Alongside that, it also captures DirectX runtime and kernel information, including D3D objects, pipeline state objects, device error data, adapter details, and CPU call stacks. Microsoft says the feature has been built around two primary use cases: retail device removals and local device removals. The former allows developers to collect crash information from end users' systems in the field, while the latter helps QA teams and developers investigate issues on test machines. Developers will also be able to include up to 2 MB of custom application data through new D3D12 APIs, providing additional context for troubleshooting. In addition, Microsoft is introducing three dump collection modes ranging from zero-overhead capture, which has no runtime performance impact on supported hardware, to higher-detail modes that collect more vendor-specific debugging data. On compatible Tier 2 hardware, zero-overhead dumps will be enabled by default, meaning developers may begin receiving useful crash diagnostics without making any code changes. The table below explains the three tiers: Tier Description NO_OVERHEAD Enables crash capture with no runtime cost and is suitable for broad deployment MEDIUM_OVERHEAD Provides a balance, capturing additional diagnostic data with moderate impact HIGH_OVERHEAD Collects the most detailed GPU and driver state available, enabling deeper investigation at the cost of higher runtime overhead In terms of availability, the company expects broader release to be around the fall of 2026, which should be right around the time when Windows 11 version 26H2 lands. Right now, DirectX Dump Files are available as a preview and currently, only AMD has the compatible AgilitySDK Developer Preview driver version 26.10.07.02. You can find the official announcement post here on Microsoft's website.
    • And with SO much better perf than the laggy mess that is Files.
  • Recent Achievements

    • One Month Later
      Sharbel earned a badge
      One Month Later
    • First Post
      BizSAR earned a badge
      First Post
    • Week One Done
      Jordan Smith earned a badge
      Week One Done
    • Reacting Well
      BizSAR earned a badge
      Reacting Well
    • First Post
      AndreaB earned a badge
      First Post
  • Popular Contributors

    1. 1
      +primortal
      598
    2. 2
      +Edouard
      190
    3. 3
      PsYcHoKiLLa
      79
    4. 4
      Michael Scrip
      76
    5. 5
      Steven P.
      70
  • Tell a friend

    Love Neowin? Tell a friend!