Dr Disrespect claims Warzone needs \u201ctotal rebuild\u201d to save battle royale Raven Software \/ YouTube: Dr DisrespectDr Disrespect claims Warzone needs to pull off a \u201ctotal engine rebuild\u201d if the popular Call of Duty battle royale wants to keep duking it out with rivals Fortnite and Apex Legends \u2014 especially in terms of live events \u2014 long into the future. To call Dr Disrespect\u2019s relationship with Warzone \u2018hot and cold\u2019 over the last few months would probably be an understatement. The streamer \u2014 who himself was a renowned Call of Duty map designer in a past life \u2014 clearly loves the battle royale; the YouTuber hosted a $20k tourney just last month. In true Doc fashion, however, he\u2019s also publicly dubbed the popular title \u201cdisappointing,\u201d downright \u201cunplayable\u201d at times, and even dramatically quit the game for a week in early May. Now he\u2019s back plotting ways to keep the game going strong. The two-time got thinking about Warzone\u2019s long-term future during a recent May 20 stream, and in particular the battle royale\u2019s \u201cpretty terrible\u201d Season 2 finale. All the game\u2019s issues, Dr Disrespect suggested, have stemmed from a bigger problem simmering under the surface. It\u2019s one that doesn\u2019t have a \u201cclear solution,\u201d at least in his eyes \u2014 how \u201cpoor\u201d the title\u2019s \u2018IW 8.0\u2019 game engine is. \u201cEverything bad in Warzone, everything that [went wrong] in season one, two, three, the whole narrative and buildup, the live event, it\u2019s all got something to do with how limiting the engine is\u2026 what it can\u2019t do,\u201d the two-time proclaimed. \u201cThe Call of Duty franchise is one of the biggest gaming IPs in the world,\u201d he continued. \u201cHow limiting this Warzone engine is has to be addressed.\u201d \u201cThere\u2019s a lot they can\u2019t do with it. How to fix it\u2026 I\u2019m not sure.\u201d The Doc pointed to rivals like Apex Legends (run on Valve\u2019s iconic Source engine) as well as PUBG and Fortnite (both built on the 23-year-old Unreal Engine) as high watermarks for battle royales that Raven Software should \u201cemulate.\u201d \u201cThe other engines out there, how they\u2019re designed, how efficient they are, there\u2019s so many benefits. They make the whole process \u2014 matches, live events, lobbies \u2014 much easier, much more streamlined,\u201d he explained. \u201cMaybe they\u2019re already addressing it. They started in Blackout, then built Warzone. Could they go back to that? They did a really good job on [Blackout].\u201d Blackout ran on the \u201cBlack Ops 4\u201d engine during its 2018 heyday. Standard battle royale lobbies in the Treyarch-led title hosted 100 players at a time. There were rumors back in March that Raven Software was eyeing a Warzone engine swap that would have shifted the battle royale onto Black Ops Cold War\u2019s engine \u2014 a unique software build \u2014 but were soon shot down. Whether Doc is right that \u2018IW 8.0\u2019 is at the heart of Warzone\u2019s issues remains to be seen. It\u2019s unlikely, however, that Raven ditches the software any time soon.<\/p>\n","protected":false},"excerpt":{"rendered":"
Dr Disrespect claims Warzone needs \u201ctotal rebuild\u201d to save battle royale Raven Software \/ YouTube: Dr DisrespectDr Disrespect claims Warzone needs to pull off a \u201ctotal engine rebuild\u201d if the popular Call of Duty battle royale wants to keep duking it out with rivals Fortnite and Apex Legends \u2014 especially in terms of live events […]<\/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-25948","post","type-post","status-publish","format-standard","hentry","category-uncategorized"],"_links":{"self":[{"href":"https:\/\/dejan.au\/index.php\/wp-json\/wp\/v2\/posts\/25948","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=25948"}],"version-history":[{"count":0,"href":"https:\/\/dejan.au\/index.php\/wp-json\/wp\/v2\/posts\/25948\/revisions"}],"wp:attachment":[{"href":"https:\/\/dejan.au\/index.php\/wp-json\/wp\/v2\/media?parent=25948"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/dejan.au\/index.php\/wp-json\/wp\/v2\/categories?post=25948"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/dejan.au\/index.php\/wp-json\/wp\/v2\/tags?post=25948"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}