Big Dragon Ball FighterZ Fix Likely Coming in April

The developers of Dragon Ball FighterZ have stated a big fix will be coming to the game to address the issues introduced with its new rollback netcode. Near the end of February, a new update for Dragon Ball FighterZ added rollback netcode to almost all versions of the game, with the Switch version being the only exception. Dragon Ball FighterZ's PS5 and Xbox Series X/S versions were released the same day as this update. While the rollback netcode was meant to improve the online environment of Dragon Ball FighterZ, fans have found the update has broken the game instead.

Shortly after the update went live for Dragon Ball FighterZ, clips of game-breaking glitches were posted by fans and streamers alike on social media. These glitches ranged from a character T-posing while the cinematic animations continued to play on-screen, or a bizarre character bug that had them being cloned during a match. The community was both frustrated and fascinated by the amount of glitches that the rollback netcode introduced. The developers of FighterZ are aware of these issues and are looking to implement a fix next month.

According to the official Dragon Ball Games Twitter account, the team is aware of the issues introduced with Dragon Ball FighterZ's rollback update. The account also states the team is working to address these problems within April, promising an official release date of this patch once a release date has been confirmed. An apology was also given out to fans who were encountering issues with the rollback update and thanked fans for being patient as the developers addressed the issues.

A possible reason behind the game's broken rollback netcode is due to a rumored split between Dragon Ball FighterZ developer Arc System Works and publisher Bandai Namco. Due to the split, the rollback update and new versions were possibly taken on by an internal Bandai Namco team or its development was outsourced to a third party without involvement from Arc System Works. This detail, however,