Patch Note Parser: NW.100.20180709g.21 or RIP Siege Farm

Neverwinter Uncensored’s patch note parser runs through any bigger patch notes and offers additional context to the changes that were made to the game. Today we are taking a closer look into version “NW.100.20180709g.21“.

Hag’s Rags Brought in Line with Fured Kiuno

[su_quote]The buff on Hag’s Rags now stacks with Eyestalk Wrappers.[/su_quote]

First change we’d like to highlight is a change to Hag’s Rags, which do now stack with its M13 counterpart Eyestalk Wrappers. This instantly catapults both items into most loadouts of ranged toons like Hunter Rangers, Control Wizards, or Scourge Warlocks, which probably already featured one of the items. Check closely however whether Jawripper’s Gloves might do more for you. This is in line with how Heels of Fury and Fured Kiuno of the Bear work now.

Players Are Now Able to Complete the “Ghost Stories” Achievement

[su_quote]Castle Ravenloft: For the achievement, Ghost Stories, all three ghosts now spawn per dungeon run, rather than just “randomly” choosing the same one each time.[/su_quote]

The next change is a nice one for all you achievement hunters. We’ve been getting a lot of question where to find the ghosts that are supposed to spawn in Castle Ravenloft. Answer: You weren’t, at least not consistently. So be one the lookout for more ghosts on your next run!

RIP Siege Farm

[su_quote]Stronghold Siege: The “Storming the Castle” weekly quest no longer incorrectly completes under certain circumstances.[/su_quote]

Here comes the pain! You probably knew that the “Storming the Castle” weekly could be completed quickly in small queue groups. Well, that is no longer as the quest now requires the Siege to be completed as full 20v20 match (or even outside the private queue, we’re not sure here). Either way, it’s going to be much more difficult to complete Siege, especially on several toons. We think this will effectively kill the Siege farm. You can however reason that the quest wasn’t designed to work this way in the first place. So whether or not it’s a nerf or a bugfix is up for discussion.

It also seems like the devs fixed at least one way to peek into random queues. Some players report it’s still possible though.


What’s your take on this topic? Share your thoughts and experience on our social channels, in the comments below, or visit our message board!

Neverwinter UN:Blogged is always looking for writers to contribute to the blog. If you are an active player and search for a way to spread your opinions, analysis, diaries or reviews to more than 75,000 regular visitors, then don’t hesitate and get in touch with us on our contact page or message board! We are currently especially looking for console and PVP content, but that’s not exclusive. There is no frequency requirement, you post how often you want.

NWO_Unblogged

We are always looking for people that contribute to this blog. For more information contact us via blog@nwo-uncensored.com or check the forum.

11 thoughts on “Patch Note Parser: NW.100.20180709g.21 or RIP Siege Farm

  • October 8, 2018 at 7:46 am
    Permalink

    So, let’s nerf a bunch of classes so PVP is balanced, and then destroy the ”’intro to PVP” quest.

    Fannnnnnntastic.

    • October 8, 2018 at 9:56 am
      Permalink

      they didnt fix pvp, they broke it even futher

  • October 8, 2018 at 7:57 am
    Permalink

    Did a 20v20 public queue full on PvP battle organized in one of the channels and still no quest completion. I reckon its completely FUBAR now.

  • October 8, 2018 at 8:20 am
    Permalink

    “Fixing” siege was so damned petty…all the bugs still in the game, but they just had to keep us from getting a bit of ad and a ruby once a week!??!

  • October 8, 2018 at 11:24 am
    Permalink

    Since I was suspended for apparently misusing a bug(I guess Im clueless) I no longer have faith in the developers and will spend no $$ on neverwinter

  • October 8, 2018 at 3:22 pm
    Permalink

    They “fixed” siege by breaking it. Initial feedback on arc is only 1 of 40 players getting the quest completion in public que. I see it as a kneejerk reaction to show proactiveness from programmers to upper management. I didnt use glitch hunts or have ad taken from my account, however i am going on an extended hiatus after this latest “fix”. Private siege was a nice quick once a week deal for me but im not going to spend 30 minutes+ waiting for a bugged que that wont complete.
    I might be back for masquerade and winter fest, but at this point i just dont know.
    I hope WOTC is taking note. Maybe the next FR/D+D title will be entrusted to a more able company.

  • October 8, 2018 at 4:05 pm
    Permalink

    Everyone knew siege would get fixed eventually. I’ll miss the campaign progression on my crappy alts more than the AD. Am I happy about it, no. Is it expected, yes

    • October 9, 2018 at 4:02 pm
      Permalink

      The fix was what allowed people to use the private queue to storming the castle. The quest was broken last year around this time and no queue could be used to complete it. The storming the castle quest got fixed during “Rocktober,” by a dev adding “extra redundancies” to the quest. These redundancies made it so that the quest could be competed in both public and private queues.

  • October 8, 2018 at 11:33 pm
    Permalink

    banned all who makes small group siege 🙂

  • October 9, 2018 at 12:18 pm
    Permalink

    There’s been a ton of testing:
    To complete the weekly siege quest you must now:
    1) Complete a 20v20 Siege in the Public queue
    2) Be on the winning team
    3) Personally score at least 300 points.

    The losing team no longer gets credit and the limit to be counted as a participant at all has been raised from the original 80.

    • October 9, 2018 at 3:55 pm
      Permalink

      I was part of a 20 vs 20 run where just about everyone got over 300 points and no one got a completion credit.

Comments are closed.