Page 1 of 2
1
2
LastLast
  1. #1
    not good with computers
    chaud's Avatar
    Join Date
    Oct 2007
    Posts
    7,471

    Developer Watercooler: Encounter Tuning by Watcher

    Shaman and Death Knight Tier 15 Armor Sets, Build 16467 Pets, Audio, Icons

    Developer Watercooler: Encounter Tuning by Watcher
    Originally Posted by Blizzard (Blue Tracker / Official Forums)
    In this blog, I’d like to shed some light on an aspect of our design that may unfortunately seem inscrutable or even arbitrary: how and when we make adjustments to our raid encounters once they’re on the live servers. The only changes we jump on immediately to fix are a clearly irritating bugs that never benefit the player in any way (e.g., issues that can cause players to fail to receive loot from a boss, glitches that can cause an encounter to evade or reset prematurely, etc.). Thanks to our internal QA team and the feedback from players on our test realms, those are relatively few in number.

    Other than these clear-cut cases, virtually every change has some negative cost to it, such that the benefits must clearly be evident in order to justify making them. If we fix a bug that allows for an unintended strategy on a fight, then the following week there will be raid groups that previously had a working strategy on an encounter and will now have to re-learn it. If we reduce the difficulty of an encounter, there will always be groups who were very close to a kill on the “pre-nerf” version whose victory feels cheapened as a result. And so forth.

    Given this background, let’s look at some of the adjustments we’ve made (or not made, in some cases) to the 5.0 raid zones over the course of the past months, broken down into a few general categories.

    Unintended Tactics

    Our players are ingenious and adept at coming up with clever solutions to the challenges posed by our raid encounters. While we have learned from past experience to an extent (Rule #14 of encounter design: If it’s possible to kite adds instead of killing them, someone will kite them instead of killing them), we are still unable to always anticipate the lengths to which our players will go to overcome a difficult encounter. There’s nothing inherently wrong with that, and often one of the hallmarks of a great encounter is that it is open to multiple approaches, depending on the strengths and weaknesses of an individual raid group. I can think of three distinct approaches that we saw to handle the Molten Elementals summoned by Heroic Ragnaros, for example, and I’m sure there are more out there.

    For example, a common tactic on the Heroic mode of Amber-Shaper Un’sok in the Heart of Fear is to have a dedicated transformed player who maintains a Destabilize stack on Un’sok throughout the entire second phase of the fight, when he is otherwise nearly invulnerable and the raid’s attention is focused on the Amber Monstrosity. This is only possible due to a bug. Un’sok was intended to be immune to Amber Strike during phase 2 of the fight, and he was in fact immune to it during that phase for much of the beta testing of the boss. However, fixing a separate bug late in development (ensuring that Amber Strike could always interrupt the otherwise-uninterruptible Monstrosity) caused Amber Strike to also bypass Un’sok’s shield in phase 2. Oops.

    This would have been a simple bug to fix, but we chose to not do so. This was a clever tactic, and while it made phase 3 of the encounter relatively simple, it did so at the expense of adding length, challenge, and complexity to the first two phases of the fight. Kudos to the players who first came up with it.

    As a general matter, unintended tactics are only a problem when they either trivialize an encounter, or when they simultaneously are the “right” (i.e., easier) way to do the fight and make it less fun in the process.

    Gara’jal the Spiritbinder
    On the first night of Heroic progression through Mogu’shan Vaults, Heroic Gara’jal proved to be an incredibly tough test for the damage-dealing capability of the best raid guilds in the world. A number of groups were a few percent shy of a kill, but it appeared quite possible that it would simply require another week worth of gear upgrades to get there. We would have been fine with that, but then one raid group noticed that one of the trolls before Gara’jal cast a massive haste buff on itself that was Spellstealable. The raid kept a couple of those enemies crowd controlled throughout the encounter, periodically breaking them out to let them cast their buffs for the mages to Spellsteal. This gave them the extra bit of damage that they needed, and Gara’jal fell.

    Other guilds got wind of this tactic, and were attempting to utilize it as well. We definitely didn’t want the fight to require the awkward use of Spellsteal and bringing other mobs into the encounter, mandating the use of multiple mages in order to meet the DPS check for initial kills. But we also didn’t want an unfair playing field in the Heroic progression race, with one guild able to continue progressing in the instance while others were stuck behind a slightly-out-of-reach DPS check and unable to take advantage of the trick that had been used to secure the first kill. As such, we made a hotfix that prevented that buff from being Spellstolen, but also reduced Gara’jal’s health by 5% to offset for the extra damage that the mages with the buff would have done.

    Exploits vs. “Creative Use of Game Mechanics” – A Brief Aside

    I’d like to take a moment to note that what this guild did was not an “exploit” in the sense of being cheating, bad, wrong, or against the rules of the game. Players used Spellsteal to steal a beneficial effect from a mob, which is what the spell is supposed to do, and the beneficial effect increased the power of the mage, which is what it was supposed to do. This was the essence of “creative use of game mechanics.” (Note that this is not to say that it isn’t possible to violate the Code of Conduct by using Spellsteal in general – if you find a spell that you can steal that causes you to damage nearby allies, and you take it back to town to grief newbies, that’s a little different. . . .)

    By contrast, a different group found a bug with Gara’jal where he could be dragged on top of the gate to his room such that players standing outside the gate could damage him without being susceptible to his attacks, and used this “unintended tactic” to defeat him. We fixed that bug, but also removed the loot and achievements earned from the players involved, and issued account suspensions. In general, it is never permissible to cause parts of a boss encounter to evade in order to gain an advantage, or to use line of sight or collision to get a boss stuck where you can attack it but its abilities no longer function.

    Will of the Emperor
    One more example, also from Heroic progression—most of the “unintended tactics” tend to be discovered and applied by cutting-edge progression guilds, since they’re the first ones to see the encounters, and are often undergeared and struggling to find every possible advantage, which usually means thinking outside the box. On Heroic Will of the Emperor, the Emperor’s Rage constructs that spawn present a real challenge. Their health is significantly increased, but each one of them also produces a deadly Titan Spark upon being destroyed, which explodes on contact to deal massive damage. The amount of damage and attention required to keep up with both the Rages and the Sparks they produce is one of the core demands the Heroic mode makes upon a raid group. It was so demanding, in fact, that most of the early groups that reached this encounter were unable to handle the overall DPS requirement.

    Looking for solutions to this problem, clever players noticed that the mage spell Ring of Frost froze enemies for 10 seconds, had a 30-second cooldown, and had no target cap. Cue three mages cycling Rings of Frost to keep every Rage frozen for the entire fight. They spawn in waves of four in 25-player mode, resulting in anywhere from 52 to 64 Rages frozen in one giant clump by the end of the fight, causing client and server performance issues in the process. On the upside (for the designers observing these attempts), when this mage rotation faltered, the resulting wipes were fairly comical, bearing more than a little resemblance to an endless stream of passengers emerging from a clown car.

    This was an example of a tactic that made the fight both significantly easier and significantly less fun. With so many enemies entirely neutralized by a small portion of the raid, the gameplay for many of the remaining players was reduced to standing in the middle of the room nuking the boss(es) for ten minutes and hoping the mages didn’t screw up. Not ideal. We wanted to fix it. However, the issue here wasn’t specific to the Will encounter. We had always fully intended for all forms of crowd control to work on Rages, so changing that was not an option.

    The problem was Ring of Frost – being able to incapacitate an unlimited number of targets with a single spellcast caused problems. This ended up being a case where the negative cost of hotfixing the issue outweighed the upside of improving the encounter. When hotfixing spells, we do not have the ability to update the tooltips and other data that resides on each individual client. Thus, if we had added a target cap to the spell via hotfix, a mage who attempted to use it on a large pull in a dungeon, or a large group of players in a battleground, would have thought the spell was broken when it suddenly didn’t work on many of the targets. Quite simply, confusing hundreds of thousands of players in all sorts of contexts, in order to fix a problem in a situation affecting a few hundred players, was not an acceptable trade-off. As such, we changed Ring of Frost (capping it at 5 targets) in patch 5.1, allowing for ample notice through patch notes and PTR cycles, as well as a properly updated in-game tooltip. By the time this change went live, access to superior gear from Heart of Fear and Terrace of Endless Spring allowed players to much more readily handle killing the Rages as we originally intended.

    Pure Difficulty Adjustments

    Other adjustments occur simply because a boss is proving to be more difficult than we’d intended, creating a roadblock. Note that we will essentially never make pure numerical (health/damage) adjustments to a raid encounter that make it more challenging once it’s gone live. If we goof on the tuning in the players’ favor, then so be it.

    On average, the self-selected pool of guilds that go through the effort of copying characters to our test servers are far more skilled and organized than the typical Normal-mode raider (and the pick-up groups that form tend to be below the target skill threshold), so there is a bit of estimation that goes into tuning Normal mode encounters. Because a disproportionately difficult Normal mode encounter presents a brick wall that entirely blocks progress, we will act to reduce the difficulty of such encounters, often shortly after they first become accessible, to avoid giving players a frustrating experience. For example, when Heart of Fear was released, we observed that even some guilds that had fully cleared Heroic Mogu’shan Vaults were struggling to meet the berserk timer on Normal Garalon; we made several adjustments to the fight to bring its difficulty in line with the rest of the instance on that first day. By the time that most others saw the encounter, it was where we wanted it to be difficulty-wise.

    Over the long-run course of a raid tier, we pay close attention to the community’s overall rate of progression. We don’t have target completion numbers for each tier or for a given number of bosses; we are far more concerned with the rate of change. Progression is fun. Running into a challenge can also be quite a bit of fun. Running into a challenge that seems insurmountable is not. So when we notice that the rate at which groups are progressing is beginning to stall, we tend to take action. In Dragon Soul (and in Icecrown Citadel before that), we used a zonewide aura to reduce the difficulty of encounters over time. Some community members’ “hand on the dial” jokes notwithstanding, those processes were not automated, and reflected an assessment of the latest progression numbers from the live servers. We have the framework for such a system in place for the current raid tier, but we have not yet felt that its activation was necessary.

    Our goal is not to make sure that the group that currently has defeated 4 of 6 Mogu’Shan Vaults bosses finishes Sha of Fear before our next patch; we do want to ensure, however, that they feel reasonably able to continue progressing at the rate they have been, with the assistance of gear upgrades gained along the way. As such, we recently reduced the difficulty of a few elements of the Normal difficulty Elegon encounter in a hotfix. This doesn’t necessarily mean that Elegon was “too hard” in some absolute sense – his difficulty presented a welcome challenge to the first wave of raiders who tackled the encounter this past fall. But the folks who defeated Elegon back then have moved on to Heart of Fear, Terrace, and/or Heroic raids in the meantime. A nerf to Elegon doesn’t affect them one way or another, but allows for raid groups still making those attempts to continue making progress today.

    And then there’s LFR. Ultimately, LFR raids are designed to be completed by groups of players that qualify to queue for them. This does not mean that it should be impossible to fail, but unlike our Normal and Heroic raids, which are designed as progressions of increasing difficulty, LFR is designed to have a flat level of difficulty within each wing. Whereas a raiding guild will routinely give up and return another night or another week when they run into a challenge they can’t quite overcome, an LFR group that runs into a difficulty spike continues to grind away as new people cycle in to replace those who depart. Most players who ran LFR last fall will recall the ubiquitous partially-complete instances with a dense carpet of skeletons to greet arriving players—not a particularly fun experience. As such, we act quickly to adjust the difficulty of encounters in LFR when needed.

    Until Next Time
    Ultimately, there is no hard-and-fast rule or formula that we follow to determine how and whether to make adjustments to encounters once they are in players’ hands, but hopefully this blog has provided some insight into the sorts of factors we consider, and our thought process with regard to a handful of specific changes during this last tier.

    Ion “Watcher” Hazzikostas is Lead Encounter Designer, and really wishes you would stop making him ban you
    Last edited by chaud; 2013-01-17 at 06:28 PM.

  2. #2
    woot first?

  3. #3
    Read this and Ion really gives players a lot to look up to. He is so open about encounter design and how it effects their decisions.

    EDIT: And yes, you are first because I actually took the time to read this one :P

  4. #4
    All I got from this is what I already knew - nerf mages every time we can.
    Spell steal is essentially worthless in PvE now, and has been for a while - Thanks!
    Oh, and let's nerf Ring of Frosts target limit while we're at it, can't have that working in say.. BGs.
    Then of course the recent neutering of fire to an virtually noncompetitive state.

    Not sure why I'm still playing this class.

  5. #5
    woah nice post

    lol at the haste buff from the trash did never see that one ^^
    well we will allways find some clever guy to find something that they did not think of ^^


    seems fun for both sides

  6. #6
    "In Dragon Soul (and in Icecrown Citadel before that), we used a zonewide aura to reduce the difficulty of encounters over time. Some community members’ “hand on the dial” jokes notwithstanding, those processes were not automated, and reflected an assessment of the latest progression numbers from the live servers."

    Good read... but not buying that part... hehehe they were automated.

  7. #7
    Epic!
    Join Date
    Oct 2010
    Location
    France, Illidan-EU
    Posts
    1,744
    Interesting read.
    So that's why the orbs are useless on Amber-shaper, it was supposed to last more than 30 seconds

  8. #8
    Quote Originally Posted by Trigunflame View Post
    All I got from this is what I already knew - nerf mages every time we can.
    Spell steal is essentially worthless in PvE now, and has been for a while - Thanks!
    Oh, and let's nerf Ring of Frosts target limit while we're at it, can't have that working in say.. BGs.
    Then of course the recent neutering of fire to an virtually noncompetitive state.

    Not sure why I'm still playing this class.
    Tell that those shamans, whose spells didnt get nerfed because of an encounter(tsulong HM) via hotfix(and not in an later patch like mages), instead they completly dont work together anymore. Doesnt seem to matter to nerf the shamans in all other aspects of wow.

    and crying as a mage? very good pve/pvp class in every addon. They are one of the last classes that are allowed to cry about sth.

  9. #9
    Mechagnome Layuth's Avatar
    Join Date
    Nov 2008
    Location
    Northeast Ohio
    Posts
    577
    TL;DR: We didn't learn from Freya.

  10. #10
    An interesting read to say the least.

  11. #11
    Good read.

    Note that mages locking down adds using CC is not unique to Will Heroic or even to the Ring of Frost spell. Back in SSC, using Frost Nova rotations to CC waves of murloc and DPS-ing them down was a similar example (though in that case, the added needed to be killed before the rotation wore off).

    Using creative use of spellsteal isnt new to MoP either. Recall Flower Power buff in Ulduar and Ensidia's smart use of it to kill Hodir Hard Mode. What makes that an exploit and what Vodka did a "creative use of game mechanics"? IIRC Ensidia was banned for using Flower Power although they posted a video of the kill and reported Flower Power right after using it to kill Hodir.

  12. #12
    Morals of the devblog is if you are a mage just smash your nuke and don't even think about anything fancy or you will get nerfed...

  13. #13
    Quote Originally Posted by Fayenoor View Post
    Using creative use of spellsteal isnt new to MoP either. Recall Flower Power buff in Ulduar and Ensidia's smart use of it to kill Hodir Hard Mode. What makes that an exploit and what Vodka did a "creative use of game mechanics"? IIRC Ensidia was banned for using Flower Power although they posted a video of the kill and reported Flower Power right after using it to kill Hodir.
    I think they got the ban using saronite bombs on LK normal which was part of standard rogue rotation on those days, not for that flower buff. but again a stupid decision by blizzard since it was their own fault.
    "Blizzard is not incompetent or stupid and they are not intentionally screwing you over"

  14. #14
    Immortal Raiju's Avatar
    Join Date
    Apr 2011
    Location
    England
    Posts
    7,186
    Was nice to see their side of things on this tier for sure

  15. #15
    Field Marshal
    Join Date
    Feb 2011
    Location
    New Mexico
    Posts
    59
    by contrast, a different group found a bug with gara’jal where he could be dragged on top of the gate to his room such that players standing outside the gate could damage him without being susceptible to his attacks, and used this “unintended tactic” to defeat him. We fixed that bug, but also removed the loot and achievements earned from the players involved, and issued account suspensions. In general, it is never permissible to cause parts of a boss encounter to evade in order to gain an advantage, or to use line of sight or collision to get a boss stuck where you can attack it but its abilities no longer function.


    TM Door strat

  16. #16
    Quote Originally Posted by Marooned View Post
    I think they got the ban using saronite bombs on LK normal which was part of standard rogue rotation on those days, not for that flower buff. but again a stupid decision by blizzard since it was their own fault.
    That's not entirely true. Some members admitted to knowing that the bombs were rebuilding the platform and that 4-5 of their raid members went and powerleveled up Engineering just to have more bombs to throw to rebuild the platform faster. It's not like they had no clue what was causing it and didn't know it was an exploit.

    All the top guilds push exploits and all have been suspended for them at one point or another. It's just a part of the World First game.

  17. #17
    Mages - too clever for their own good.

    If Shamans and warriors ever move close to the top of the dps charts you can pretty much expect some raid will try and stack them for a stormlash/skull banner rotation to max out deeps.

    As for my pet peeves:
    Make totems work while aerial (e.g. Alakir P3)
    NPCs should not attack totems while rooted (since they don't do so while snared)! It kind of makes earthgrab totem potentially less useful than earthbind.

  18. #18
    Quote Originally Posted by Layuth View Post
    TL;DR: We didn't learn from Freya.
    So true. At this point in the game you would think blizzard would have designed encounters a little more intelligently vs players than they do.

    Decent read but most of what it boiled down to was players are crafty and if they beat blizzards design through interesting play styles and tactics it has to be "less fun" in most situations cause it's not how we (blizzard) designed it.
    Last edited by quras; 2013-01-17 at 06:47 PM.

  19. #19
    Immortal Granyala's Avatar
    Join Date
    Feb 2010
    Location
    Arkon-III
    Posts
    7,802
    On the upside (for the designers observing these attempts), when this mage rotation faltered, the resulting wipes were fairly comical, bearing more than a little resemblance to an endless stream of passengers emerging from a clown car
    WooT Devs watching attempts .. creepy... but I bet they had plenty to laugh.

  20. #20
    Quote Originally Posted by nnelson54 View Post
    That's not entirely true. Some members admitted to knowing that the bombs were rebuilding the platform and that 4-5 of their raid members went and powerleveled up Engineering just to have more bombs to throw to rebuild the platform faster. It's not like they had no clue what was causing it and didn't know it was an exploit.

    All the top guilds push exploits and all have been suspended for them at one point or another. It's just a part of the World First game.
    Yeah, the whole feigning that they didn't know what was causing it was just some bs that ensidia used at the time to maintain face in front of fans who were stupid enough to believe that, and that story exists till today. Of course, blizzard had all the facts with which to make the right call, even if the players don't see them.

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •