A new Dragon Ball: Sparking! ZERO update is available for PlayStation 5, Xbox Series X|S and PC. Bandai Namco identifies it as version 3022.021.003.012.015. The patch changes CPU behaviour, restores trophies that could fail to appear after players met certain conditions in Jiren’s Episode Battle, and improves overall stability. The publisher does not list new characters, stages or balance values in this update.
Table of Contents
The patch is narrow and should be described that way
The official notes contain three lines of functional change. They do not announce a new downloadable fighter, a larger story chapter or a ranked-season reset. Calling the update a major content expansion would therefore create the wrong expectation. Its value is practical: computer-controlled opponents should behave differently, an Episode Battle reward should register more reliably, and the game receives stability work. Players who want to know whether a favourite character’s damage changed will not find that answer here. They should keep the current balance data until a later note lists a specific numerical adjustment.
CPU behaviour needs testing in the mode where the problem appeared
Bandai Namco says CPU behaviour was adjusted but does not identify every decision that changed. The responsible way to test it is to repeat a known offline situation with the same difficulty, arena and characters. One match is not enough because positioning and attack choice can vary naturally. Players can look for repeated improvements or new errors across several rounds, especially around recovery, pursuit and defensive reactions. A different result does not prove that the entire difficulty system was rebuilt. It only shows how the updated opponent handled that particular set of conditions.
| Area | Patch action |
|---|---|
| Platforms | PlayStation 5, Xbox Series X|S and PC |
| CPU | Behaviour adjusted |
| Jiren Episode Battle | Missing trophy display issue fixed |
| Stability | General improvements applied |
The Jiren fix concerns recognition after a requirement is met
The Episode Battle correction applies to certain trophies that were not displayed after their conditions had been completed. It does not lower those conditions or automatically promise every trophy to every save. After installing the update, a player should open the relevant Jiren episode and check the platform trophy list. If the reward remains absent, completing the final required step again may trigger a fresh check. Before repeating a long sequence, confirm that the game version matches the number in the notes and that the console or PC account is online enough to synchronize its achievement data.
Save backups still matter before repeating story content
A stability patch reduces known problems but cannot protect a save from power loss, interrupted synchronization or a damaged local file. Players returning to Episode Battle should allow cloud synchronization to finish before launching and avoid closing the game while a result is being stored. On PC, it is also sensible to verify that security software has not quarantined a changed file after the update. These checks are not evidence that the patch is unsafe. They are ordinary precautions when a player is revisiting progress that previously failed to register correctly.
The long version number helps support identify the exact build
Version 3022.021.003.012.015 is more useful than saying only that the latest patch is installed. Storefronts can release data at slightly different times, and a suspended console may not begin a download until it reconnects. When reporting an issue, players should include the full version, platform, game mode and sequence that produced the problem. A short video can help when CPU behaviour is involved, because it shows distance and timing that a written message may miss. Reports that identify the build are easier to separate from cases created under an older version.
Online opponents are not the same as the adjusted CPU
The wording about CPU behaviour applies to computer-controlled characters. It should not be presented as a change to matchmaking, network delay or the decisions of human players. A difficult online round after the patch does not demonstrate that the CPU change failed. Likewise, a smoother offline battle does not prove that connection quality improved. Players can isolate the systems by testing Episode Battle or another offline fight first, then checking online performance separately.
This simple division prevents unrelated experiences from being folded into one claim about the update.
