WoWCenter.pl
wikass zabił Mythrax the Unraveler (Normal Uldir) po raz 2.     
kuturin zdobył 7th Legionnaire's Cuffs.     
Nikandra spełnił kryterium Loot 200,000 gold osiągnięcia Got My Mind On My Money.     
Tooly zdobył Fairweather Helm.     
Muattin zdobył osiągnięcie The Dirty Five.     
Yoozku zdobył Parrotfeather Cloak.     
Mlody89 zdobył Royal Apothecary Drape.     
Weakness zabił Dazar, The First King (Mythic King's Rest) po raz 6.     
liq spełnił kryterium osiągnięcia Saving for a Rainy Day.     
Osiol spełnił kryterium osiągnięcia Saving for a Rainy Day.     
Wuntu zabił Zek'voz, Herald of N'zoth (Heroic Uldir) po raz 1.     
Olsa zabił Vectis (Heroic Uldir) po raz 6.     
Sarenus spełnił kryterium osiągnięcia Saving for a Rainy Day.     
kajtasus zdobył osiągnięcie Come Sail Away.     
ossir spełnił kryterium osiągnięcia Saving for a Rainy Day.     
mcpablo spełnił kryterium Alliance players slain. osiągnięcia Frontline Slayer.     
Emmm zabił Taloc (Heroic Uldir) po raz 17.     
AsaGorth spełnił kryterium Big-Mouth Clam osiągnięcia The Oceanographer.     

PSA: Creatures now scale with item level

blizz -> wysłany:
What the hell.

I discovered this while creating an undocumented changes thread on reddit. Me, and 3 other people with vastly different item levels all see different health values for normal creatures, rares and elites.

This is the one thing that Blizzard said they wouldn't do. This removes all sense of power progression in the open world.

You can confirm this yourself - Target a mob at 110 and remove a piece of gear. Its health will immediately drop.

I've linked to this thread in a Tweet to Blizzard, so hopefully we can get some information on this.

Edit:

The values seem to be like this:

110 15589k ilvl 749
110 15589k ilvl 821
110 15589k ilvl 850
110 16461k ilvl 857

It starts increasing faster and harder after 850.
blizz -> wysłany:
Apologies for the delay in getting information out on this - our initial focus was on putting out other patch-day fires.

Yes, this reflects a deliberate change, but it's also not working exactly as we intended. The scaling may be too steep, and the fact that unequipping a piece of gear can ever be helpful is a bug in the system. We'll be looking into making changes to correct this in the very near future.

Power progression is an essential part of the WoW endgame, and the last thing we want is to undermine that. We stressed the importance of that progression when discussing how the level-scaling system worked in Legion around the time of the expansion's launch, and explained why we then had no plans to scale foes' power based on gear. But as we've watched Legion unfold, we've come to observe some side-effects of our endgame content plan and the associated rewards structure that made us reconsider.

We've never had the initial outdoor world content stay relevant for this long in an expansion before. By the end of Mists of Pandaria, for example, the mantid of Dread Wastes that had once been reasonable foes were completely trivial. They'd basically evaporate if a raid-geared player looked in their general direction. But there wasn't much reason besides achievements or completionism to revisit the Klaxxi dailies once Isle of Thunder was out or, later on, Timeless Isle. And the enemies in those later zones could be tuned to a proportionally more challenging baseline difficulty.

But in Legion, while the new content in Broken Shore is the focus of 7.2, and we've made sure that the core outdoor rewards (both dropped and from Nethershards) are superior to the rep-related rewards from the original factions, the intent is not for the Broken Shore to completely replace the rest of the game. You'll still go back to the other Broken Isles zones for emissaries, Legion Assaults (coming next week!), Order campaign quests, improved world quest rewards, and more. And as 7.1 and 7.1.5 progressed, we could see that even with Nighthold gear the pacing of combat was getting a bit silly - what would happen once new content made that level of gear more common, and once the Tomb raid pushed limits even higher?

To reiterate, power progression is an essential part of the WoW endgame. We absolutely want you to feel overpowered as you return to steamroll content that once was challenging. But there's a threshold beyond which the game's core mechanics start to break down. When someone trying to wind up a 2.5sec cast can't get a nuke off against a quest target before another player charges in and one-shots it, that feels broken. And even for the Mythic-geared bringer of death and destruction, when everything dies nearly instantly, you spend more time looting corpses than you do making them. You spend an order of magnitude longer traveling to a quest location than you do killing the quest target. You stop using your core class abilities and instead focus on spamming instants to tap mobs as quickly as possible before they die.

Our goal is basically to safeguard against that degenerate extreme. We tune outdoor combat for a fresh 110 around a 12-15sec duration against a standard non-elite, non-boss enemy. It's great for gear, over the course of an expansion to cut that time in half, or even by two-thirds. But once you get down to a duration of one or two global cooldowns, the game just wasn't built to support that as the norm. (Note that this is an current-content endgame concern; running legacy content for completion/transmog/etc. purposes is a totally different story.)

The intent of our change in 7.2 was to smooth out that progression curve a bit, not flatten it out, and certainly never to invert it. If you get a great set of item upgrades that make you 5% stronger, maybe the world gets 1-2% tougher. Perhaps instead of getting 400% stronger over the course of the expansion relative to the outdoor world, you only get 250% stronger. But you should always be getting more powerful in relative terms, and upgrades should always matter. From some reactions so far, it sounds like we may be off on that tuning. And as noted above, the fact that unequipping items can ever be helpful is a bug that we'll be investigating and fixing.

Finally, there's the natural question of why we didn't patch-note this. It was not to be deceptive; we know it's impossible to hide a change from millions of players. But the system was meant to feel largely transparent and subtle, just like level-scaling does if you don't stop and really think about it, and so we did want players to first experience the change organically. Your feedback and reactions and first impressions of the system are more useful in this particular case when they are not skewed by the experience of logging in and actively trying to spot the differences. Thank you for that, and I look forward to continued discussion.
blizz -> wysłany:
Thanks for the feedback on this issue. It’s clear that we need to make some changes here, so here are our current plans:

  • We’re removing the increase to damage dealt by creatures in the world. Our overall goal with this change is to keep the amount of time it takes to kill a creature from getting ridiculously short, and increasing the damage they deal is unnecessary for that goal. Instead, this was making you feel like they were becoming more dangerous, which was not our intent.
  • We’re significantly reducing the rate at which creature health scales with your item level. Again, all we’re trying to do here is prevent cases where monsters die too quickly for players to react to their presence, particularly around World Quests. Our initial tuning was far more aggressive than it needed to be, which could make it feel like your upgrades weren't actually helping. This change will make it very clear that you are still becoming noticeably stronger than your enemies as your gear improves.
  • Those two changes are already live, and you should be seeing them in-game now.
  • Later today, we’ll be correcting a separate issue that’s causing unequipping an item to drastically alter the power of enemies you’re facing. The above changes make it so that’s never the right thing to do anyway, but this is still a strange/buggy interaction that needs to be fixed.

It should also be noted that this change was on the Patch 7.2 PTR (and has been since January). We didn’t communicate anything about it initially because we wanted to get testers’ raw and honest feedback about it when they encountered it themselves, rather than attempting to pre-empt or otherwise influence their opinions ahead of time. When that feedback never came, we assumed that meant it was an acceptable change – i.e., those who hadn’t noticed it weren’t bothered by it, and those who had noticed it thought it was fine. Clearly that was a false assumption, and we should have drawn attention to it later in the PTR cycle, so that we could have caught these issues before Patch 7.2 went live.