{"id":33009,"date":"2025-01-28T15:38:19","date_gmt":"2025-01-28T15:38:19","guid":{"rendered":"https:\/\/dejan.au\/index.php\/2025\/01\/28\/warzone-players-blast-l-update-as-devs-disable-champions-quest-feature-dexerto\/"},"modified":"2025-01-28T15:38:19","modified_gmt":"2025-01-28T15:38:19","slug":"warzone-players-blast-l-update-as-devs-disable-champions-quest-feature-dexerto","status":"publish","type":"post","link":"https:\/\/dejan.au\/index.php\/2025\/01\/28\/warzone-players-blast-l-update-as-devs-disable-champions-quest-feature-dexerto\/","title":{"rendered":"Warzone players blast \u2018L update\u2019 as devs disable Champion\u2019s Quest feature &#8211; Dexerto"},"content":{"rendered":"<p>Warzone players blast \u2018L update\u2019 as devs disable Champion\u2019s Quest feature Activision BlizzardIssues with Warzone\u2019s Season 1 Reloaded patch have forced developers to disable the Champion\u2019s Quest nuke feature \u2013 players aren\u2019t happy. The Season 1 Reloaded patch for Call of Duty: Warzone went live on January 17. Of course, the update featured the customary bug fixes, weapon balancing adjustments, and all the rest. It also brought Champion\u2019s Quest to the Urzikstan map for the first time, allowing players to navigate their way through a series of tasks to activate a nuke. Not everything\u2019s sunshine and rainbows where the new update is concerned, though. Since the patch went live, users have encountered numerous gameplay bugs, including a few that break the game. And now developers have no choice but to temporarily deactivate one of the affected features. Raven Software disables Warzone\u2019s Champion\u2019s Quest A social media post from Raven Software confirms that the studio has removed the recently added nuke quest from Warzone. While the feature\u2019s deactivation is temporary, it\u2019s not clear when Champion\u2019s Quest will return. Raven said the decision spawned from the realization that Season 1 Reloaded\u2019s patch does not meet its internal quality standards. The message reads in part: \u201cAt the moment, the current state of the update does not meet our standards for quality and gameplay, and we are committed to addressing the issues promptly to ensure that all players can enjoy Warzone to the fullest extent possible. Our goal is always to provide a smooth and seamless experience.\u201d Suffice it to say, Warzone players aren\u2019t happy about the quick switch with Champion\u2019s Quest. Twitch streamer Poboy responded to the tweet saying: \u201cTest your game before you roll a mid-season update out? Thoughts?\u201d Another content creator went as far as to call this patch the worst Raven\u2019s deployed to date \u201cThis has got to be the worst update you guys have ever dropped and that\u2019s saying something,\u201d commented Zyro. Reads a response from another disgruntled Call of Duty user, \u201cYet again another \u2018L\u2019 update. Do you guys have a \u2018test environment\u2019 where these updates are tested\u2026\u201d Some people are especially upset because they were on a winning streak when the Champion\u2019s Quest announcement went live. As such, their shot at the nuke was abruptly hindered without warning. Again, there\u2019s currently no word on when Champion\u2019s Quest will return to Warzone. But, hopefully, its future reinstatement won\u2019t be plagued by bugs.<\/p>\n","protected":false},"excerpt":{"rendered":"<p>Warzone players blast \u2018L update\u2019 as devs disable Champion\u2019s Quest feature Activision BlizzardIssues with Warzone\u2019s Season 1 Reloaded patch have forced developers to disable the Champion\u2019s Quest nuke feature \u2013 players aren\u2019t happy. The Season 1 Reloaded patch for Call of Duty: Warzone went live on January 17. Of course, the update featured the customary [&hellip;]<\/p>\n","protected":false},"author":2,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[1],"tags":[],"class_list":["post-33009","post","type-post","status-publish","format-standard","hentry","category-uncategorized"],"_links":{"self":[{"href":"https:\/\/dejan.au\/index.php\/wp-json\/wp\/v2\/posts\/33009","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/dejan.au\/index.php\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/dejan.au\/index.php\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/dejan.au\/index.php\/wp-json\/wp\/v2\/users\/2"}],"replies":[{"embeddable":true,"href":"https:\/\/dejan.au\/index.php\/wp-json\/wp\/v2\/comments?post=33009"}],"version-history":[{"count":0,"href":"https:\/\/dejan.au\/index.php\/wp-json\/wp\/v2\/posts\/33009\/revisions"}],"wp:attachment":[{"href":"https:\/\/dejan.au\/index.php\/wp-json\/wp\/v2\/media?parent=33009"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/dejan.au\/index.php\/wp-json\/wp\/v2\/categories?post=33009"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/dejan.au\/index.php\/wp-json\/wp\/v2\/tags?post=33009"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}