{"id":80310,"date":"2025-01-28T22:35:27","date_gmt":"2025-01-28T22:35:27","guid":{"rendered":"https:\/\/dejan.au\/index.php\/2025\/01\/28\/dragon-ball-fighterz-ruined-by-disastrous-rollback-netcode-update-dexerto\/"},"modified":"2025-01-28T22:35:27","modified_gmt":"2025-01-28T22:35:27","slug":"dragon-ball-fighterz-ruined-by-disastrous-rollback-netcode-update-dexerto","status":"publish","type":"post","link":"https:\/\/dejan.au\/index.php\/2025\/01\/28\/dragon-ball-fighterz-ruined-by-disastrous-rollback-netcode-update-dexerto\/","title":{"rendered":"Dragon Ball FighterZ \u201cruined\u201d by disastrous rollback netcode update &#8211; Dexerto"},"content":{"rendered":"<p>Dragon Ball FighterZ \u201cruined\u201d by disastrous rollback netcode update TyrantUKDragon Ball FighterZ players have been asking for rollback netcode for years, which was finally confirmed in 2022. However, it appears that rollback wasn\u2019t worth the wait for DBFZ fans. At one point, Dragon Ball FighterZ\u2018s rollback netcode was nothing more than a meme. Players gave up hope that it\u2019d ever happen in the years following the game\u2019s release, only for rollback to be revealed at EVO 2022. Its projected release date wasn\u2019t locked in at the time, and release dates that came after that announcement were continually pushed back until fans finally got rollback almost 2 years after the initial announcement \u2013 and more than six whole years after DBFZ\u2019s initial release. After all that time, however, rollback netcode appears to be completely breaking the game despite how long it took to develop. Dragon Ball FighterZ rollback update kills spectator mode To clarify, the actual gameplay for either fighter in the rollback netcode update appears to be fine. The problem lies in the game\u2019s spectator mode. When a player users a super move, it freezes their player model on the screen in a fixed pose. And this can be replicated over and over again to plaster the screen with player models. And, while that may not seem to be a huge issue on the surface considering it\u2019s just spectator mode, a large part of the reason why the community wanted this update so badly was to keep the competitive scene alive. Now, running online tournaments for this game requires you to either force players to play with a worse connection, or to not spectate the tournament at all. At least players are having fun with just how many ways you can mess with the way characters freeze and t-pose on the screen, but it makes the game impossible to watch. It isn\u2019t like this bug where characters stick around a bit longer than intended is a difficult to replicate bug, either. This happens every time someone uses a super move. \u201cWhat have they done? They\u2019ve ruined it.\u201d streamer Tyrant lamented. What\u2019s more, people playing the rollback netcode update have claimed that their DLC characters didn\u2019t carry over on their account when upgrading from the PS4\/Xbox One version to the PS5\/Xbox Series version with the new update. There are several claims of this, ranging from people missing one character to people missing all of their DLC. For just the character DLC alone, all of the fighters are worth $80 USD total. Having to buy all of that again is something long time players understandably don\u2019t want to do. Between these two widespread issues, Dragon Ball FighterZ players are livid at how what could be the game\u2019s last big update was handled.<\/p>\n","protected":false},"excerpt":{"rendered":"<p>Dragon Ball FighterZ \u201cruined\u201d by disastrous rollback netcode update TyrantUKDragon Ball FighterZ players have been asking for rollback netcode for years, which was finally confirmed in 2022. However, it appears that rollback wasn\u2019t worth the wait for DBFZ fans. At one point, Dragon Ball FighterZ\u2018s rollback netcode was nothing more than a meme. Players gave [&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-80310","post","type-post","status-publish","format-standard","hentry","category-uncategorized"],"_links":{"self":[{"href":"https:\/\/dejan.au\/index.php\/wp-json\/wp\/v2\/posts\/80310","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=80310"}],"version-history":[{"count":0,"href":"https:\/\/dejan.au\/index.php\/wp-json\/wp\/v2\/posts\/80310\/revisions"}],"wp:attachment":[{"href":"https:\/\/dejan.au\/index.php\/wp-json\/wp\/v2\/media?parent=80310"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/dejan.au\/index.php\/wp-json\/wp\/v2\/categories?post=80310"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/dejan.au\/index.php\/wp-json\/wp\/v2\/tags?post=80310"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}