JavaScript is required to use Bungie.net

Destiny

Discuss all things Destiny.
2/14/2017 6:02:22 PM
1860

Hungering Blade Clarification for Hotfix 2.5.0.2 Patch Notes

We just launched [b]Hotfix 2.5.0.2[/b] which contains a Sandbox tuning pass and changes to the Crucible. If you want an in-depth exploration into some of these changes you can watch our [url=https://www.twitch.tv/videos/120721482]live fire demonstration here[/url]. For those interested in the bullet points we have the full [url=https://www.bungie.net/en/News/Article/45661]Patch Notes[/url] up as well. In the interest of full transparency, we do need to clarify something in this update. Our test team discovered that the changes to the Blade Dancer Perk Hungering Blade were being applied to several other Health Regen Perks. Here is a quote from Sandbox designer Josh Hamrick. [quote]Over the last couple of days, as we continued to test the patch, it came to our attention that the changes we made to Hungering Blade were unintentionally shared among a number of additional elements (list below). While we considered delaying the hotfix to remove the shared change, we ultimately decided to live with the patch we’d made and tested. We believe that Hotfix 2.5.0.2 is an important step forward to maintain the health of the game and that getting it out to you ASAP is in everyone's best interest. And besides, no one wants to show up empty handed on Valentine’s day. List of affected elements: • Hungering Blade (Arc Hunter) • Transfusion (Striker Titan) • Cauterize (Sunbreaker Titan) • Lifesteal (Voidwalker Warlock) • Red Death perk • Suros Legacy Perk (Suros Regime) • No Backup Plans • Ward of Dawn cast • The Ram • Apotheosis Veil • Embrace the Void (Voidwalker Warlock) Over the next couple of weeks, we will be diligently watching and listening to what you have to say about these changes. While we will be unsurprised if additional tweaks need to be made, we are honestly super interested to see how these changes, intended or not, play out. We will be relying on you to give us your feedback as you grow accustomed to the feel of the game over the next couple of weeks. We will also be with you ingame, playing along and making our own notes… Apparently, I have to redeem myself for my stream performance anyway. Now if you’ll excuse me, I have a 1st date with a potential Skorri fix… [/quote]
English
#Destiny

Posting in language:

 

Play nice. Take a minute to review our Code of Conduct before submitting your post. Cancel Edit Create Fireteam Post

View Entire Topic
  • Edited by Highs_In_Berg: 2/14/2017 11:06:29 PM
    I don't often join in on the post-patch Bungie-bash sessions, but I can't hold my tongue. I watched part of the Twitch stream in which Bungie discussed the sandbox changes and the rationale for implementing said changes. During the stream, one of the sandbox developers (I don't remember the gentleman's name) stated that the choice to change Hungering Blade was based upon his own personal experiences, rather than being based upon input from the player base. I remember watching and thinking, "That sounds like a bad idea to nerf an aspect of a subclass based upon one tester's experiences." Fast forward to today. I read the description in the patch notes and was extremely surprised to find that 1) implementation of this nerf inadvertently caused negative effects to several other weapons and subclasses, 2) this fact had been recognized by Bungie, and that 3) Bungie decided to release the patch anyway! So the decision to nerf Hungering Blade appears to have been based on a single person's experiences. And by implementing this unnecessary nerf, many other aspects of the game have been negatively effected. Bungie recognized that this would happen, and pushed the patch anyway, and even remarked that they were interested to see how this mistake would play out! Guys...I don't even know how to articulate myself other than to say, WTF?

    Posting in language:

     

    Play nice. Take a minute to review our Code of Conduct before submitting your post. Cancel Edit Create Fireteam Post

    6 Replies
    1 2
    You are not allowed to view this content.
    ;
    preload icon
    preload icon
    preload icon