Starym

Old Dev Blog on Encounter Tuning and Exploits

Sign in to follow this  

4 posts in this topic

55cKxHT.jpg

 

Watcher shared this old developer blog on his twitter, related to the recent discussions around exploits and bugs and how that related to encounter design. The blog itself is from the Mists of Pandaria era, so the examples may be outdated, but as the man himself says, still accurate.

Blizzard LogoWatcher, 2013

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 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.

Q3GTU4P439QW1348241610432.jpg

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 10 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.

OQ5ZIPW2Z9JJ1348241610383.jpg

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.

3ME67TIPAK5D1348241610286.jpg

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.

 

Share this post


Link to post
Share on other sites
36 minutes ago, Migol said:

...I'd like to hear his justification on Vanilla's C'thun...


/bitter old player.

Haha, dont think he was working there at the time, but yea that was one of the worst things ever. From unkillable to instadead first try, BALANCE!

Share this post


Link to post
Share on other sites
6 hours ago, Starym said:

From unkillable to instadead first try, BALANCE!

That sounds like the motto the PvP team must have on their wall in the Blizzard HQ!

Share this post


Link to post
Share on other sites

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
Sign in to follow this  

  • Recently Browsing   0 members

    No registered users viewing this page.

  • Similar Content

    • By Stan
      Today's roundup of blue posts covers Allied Race boosting through Recruit-a-Friend, the Azerite system, Flight Master's Whistle working in Legion zones & more.
      Allied Race Recruit-a-Friend Boost
      If your play an Allied Race and your friend grants you levels through RaF, you will be ineligible to receive Heritage Armor.
      Blizzard (Source)
      Receiving granted levels from Recruit A Friend would make the character ineligible for the heritage armor set.
      If your friend grants levels to one of your Allied Race characters, it makes your character ineligible to receive the Heritage Armor.

      If you grant levels to one of your friend's characters, that won't effect your eligibility for the armor.

      But only the recruited player accumulates levels that can be granted, so that would be your friend. If they were to grant any of those levels onto your Void Elf, that would make your Void Elf ineligible for the armor.
      Azerite System Underwhelming
      It's too early to consider the Azerite system underwhelming. Quest gear only contains generic traits and Azerite Armor from raids has better traits.
      Blizzard (Source)
      Surely im not the only one who feels this way? The azerite gear is essentially the netherlight crucible. Most traits are passive and boring. Does it get better as the xpac goes on or..?
      Some of the default Azerite items from questing don't have a lot of variety because you're still leveling up. Once you're at 120 and getting them from vendors, WQs, and dungeons you start seeing a lot more variety and some pretty neat stuff. 

      Like there's one for Ret that reduces the cooldown of Divine Steed and it gives a speed buff to your entire raid when you use it. Which I thought was pretty rad.

      It's definitely early, but I'm eager to see how it plays out and how this system shapes up as well as what else we might do with it. It has potential, and I'm pretty excited about that alone as a player.
      Unintended Conquest Cap
      A bug in the Battle for Azeroth pre-patch caused players to receive Conquest from certain PvP activities, but that was never intended outside of Seasons.
      Blizzard (Source)
      With the Battle for Azeroth Pre-Patch, we incurred a bug that caused some PvP activities to reward Conquest. Conquest was never intended to be accessible while the season is not active, and while Conquest did appear for some players on their Character Currency tab, it wasn’t useable. There aren’t any items that can be exchanged for it in-game right now.

      We’ll be deploying a hotfix soon that will change any activities that are currently awarding Conquest to award Honor instead.

      When BFA Season 1 begins, players will start earning Conquest as planned. At the same time, we’ll convert any unintended Conquest that players earned during the post-season to Honor or gold.

      Additionally, new one-time PvP quests will get reset when BFA Season 1 begins. We want to make sure you can complete those quests to earn Conquest from them as intended. These quests are located in the same place where you turn in Conquest quests, so they should be easy to spot.

      We apologize for any confusion this may have caused, and we’re working to make the fixes and conversions as seamless as possible.

      We look forward to everyone engaging with the new Conquest System upcoming in Season 1 of Battle for Azeroth! Click here to learn more.

      Thank you! Flight Master's Whistle
      Flight Master's Whistle will be upgraded to work in BfA zones when you unlock world quests. If you didn't play Legion or destroyed your whistle, you'll receive a new one that will work in Legion zones as well.
      Blizzard (Source)
      When you unlock Battle for Azeroth world quests, your Flight Master's Whistle gains the ability to work in the new lands. if you didn’t play Legion or destroyed your whistle, you will receive a Flight Master's Whistle that works in Legion and Battle for Azeroth zones.
    • By Starym
      The hotfixes continue as we hit a 3-day streak, and we have the previously announced big Arms Warrior changes, dungeon fixes including XP issues with mixed groups of level 120 and lower, and the now standard massive amount of profession and quest fixes.
      August 16 (source)
      Azerite Gear
      Fixed an issue where Ruinous Bolt would sometimes damage enemies that the player was not in combat with.  
      Classes
      Warrior Arms 1 point of Mastery now increases Mastery: Deep Wounds damage by 10% (was 1%). Damage of all Arms abilities decreased by 14%. This excludes Arms Azerite Traits. Creatures and NPCs
      Da White Shark has turned a new leaf and has fully renounced the fighting tactic of beating someone with another person's body. Players should now always be able to see the reward treasure chest after defeating Da White Shark in the Grand Bazaar. Slickspill in Stormsong should now be much easier to loot. John J. Keeshan has decided to once again wield his old bow instead of the bow of a certain warchief. Dungeons
      Fixed a bug where a group of players below level 110, when partied with a level 110 player in a Legion dungeon, would receive heavily reduced experience. Fixed an issue that caused Alliance players who had completed The Pride of Kul Tiras to be unable to access Siege of Boralus. Fixed an issue that caused Horde players who hadn’t completed Zandalar Forever to be able to access Kings’ Rest. Clarified the error messages shown when attempting to zone in to Kings’ Rest or Siege of Boralus without meeting the requirements.  
      Items
      Salty Dog Crackers are now consumed on use. The Stormsteel Saber now has a level requirement of 120. Player versus Player
      Steel Strongboxes now drop Dread Aspirant gear for all valid armor slots during the offseason. Factionally-aligned guards should no longer attack you for attacking members of the opposite faction. Call to Arms: Vol'dun will now correctly count Horde players slain while in Vol'Dun. Professions
      The Forgotten Techniques of Kul Tiras/Zandalar items now properly restore recipes that were learned and subsequently unlearned. Fixed a bug preventing some Draenor profession books from properly teaching all introductory recipes. Archaeology Digsites in the Port of Zem’lan are no longer partially obscured from view. Cooking Crafting  Swamp Fish 'n Chips should now give credit towards the achievements "The Zandalari Menu" and "The Kul Tiran Menu". Fishing Akan now teaches Battle for Azeroth Fishing. Quests
      Fixed a bug that caused a few Tortollan quests in Stormsong Valley from awarding Tortollan reputation as intended. Completing "All Laid Out For Us" now awards its part of the Stormsong and Dance achievement. Upon accepting “Back to the Lab”, Raimond Mildehnall will no longer attempt to fight every enemy he sees while returning to the basement. Fixed an issue where the Lightforged Warframe used during "Dawn of Justice" was weaker than intended. Felecia Gladstone will now offer the remainder of her quests in Warfang Hold only once all her tasks for the Saltstone Mine have been completed. When unlocking World Quests in Zandalar and Kul’Tiras, Halford Wyrmbane or Nathanos Blightcaller will now give you a fresh Flight Master's Whistle if you left yours in the bank. Players are no longer stuck after abandoning “Into the Dunes” mid-flight. Scout Mckellis is now available at the turn-in location for "Powder to the People" and "One Man Against the Horde". "WANTED: Anchorface" should now be available to Alliance players before they unlock World Quests. "Wiccaphobia" should now proceed as expected for players who group up with other players on the quest. Players may now complete "Spell Bound" after first completing "So Long, Sister". Lucille Waycrest should no longer disappear for some players on "Of Myth and Fable”. Eligible party members now receive Azerite along with “Azerite Mining” quest credit when a member of the party interacts with an Azerite node. World
      Fixed a bug preventing some Inns from granting rested experience to characters in War Mode. The Royal Treasury in Dazar’Alor is now flagged as a rested area. The second floor of the Snug Harbor Inn is now flagged as a rested area. The Flight Master's Whistle can now be used on the non-dungeon island of Tol Dagor. Previous Patch 8.0.1 Hotfixes
      August 15 August 14 August 10
    • By Babblet
      Location: Horde, US Connected Realms: Aegwynn, Bonechewer, Daggerspine, Gurubashi, Hakkar. 
      Raiding Times: Mon/Tue 8:00 PM EST - 12:00 PM EST
       
      About us:
      We are former nolife raiders who now enjoy spending time outside our basements in the real world. Our total play time has decreased slightly but we still strive to meaningfully progress our characters through end game raiding. Currently we are recruiting new members to help us progress in the upcoming expansion. Join us and lets slay Dragons together!
      Apply if you are:
      interested in end game content; M+ Dungeons and Heroic/Mythic Raiding capable of critical thought and willing to contribute when discussing strategy a self-starter who plays to improve and keeps up to date with latest theorycraft always on time and reliable  
      Recruitment Status: currently recruiting Ranged DPS.
       
      Contacts/Battle Tags:
      Shig#1825 (Guild Master)
      Silvadine#1273 (Officer)
      Discord:
      Shig#8835
      Silvadine#1277
    • By Starym
      After he took down the full VoD and clips of his leveling experience due to racist remarks that popped up on screen from donors, Gingi has compiled a video with just the highlights from his World First run to level 120, that took him 4 hours and 17 minutes. Warning: there's a LOT of sped up footage in there so beware!
    • By Starym
      Update: Gingi has removed the VoD of the leveling experience due to some problematic content in the video, but will be posting an edited version of the entire leveling experience to youtube soon. Here's his tweet on the subject and you can still watch the whole experience through Deepshades',and Meeres' PoVs.
      ________________________________________________________________
      Well, this was quite insane. It seems Method's Gingi decided to one-up his fellow teammate Fragnance, who got the WF level 110 in Legion in 5 and a half hours. Well, it took Gingi, or rather Luigingi, 4 hours and 17 or so minutes to finish up Battle for Azeroth's leveling, in a team of three, along with Method's Meeres and Deepshades, using his boomkin:

       
       
      If you want to see how exactly he did it, you can check out his full leveling video, but it seems they just went for really REALLY fast questing (obviously tested on beta) with no special shenanigans involved (at least that I could find at first glance):
       

      Method's Gingi dinged 120 in 4 hours 17 minutes!

      Obviously, Deepshades and Meeres dinged very quickly after Gingi, and here are their full streams of the leveling process as well, linked to the final minute - Deepshades, Meeres.
      And some thanks from the WF Gingi himself: