Activision pushed a small Black Ops 7 update across all platforms on the evening of September 11. Most of it is Zombies housekeeping. The multiplayer line is the one worth reading twice: scorestreak selections would sometimes fall back to their default selections, despite players selecting custom configurations. In plain terms, the game was quietly ignoring the streaks you set.
Confirmed. This comes straight from the official Call of Duty Updates account, the channel Activision uses for patch notes and live issues, and we read the post directly. What it does not tell you is how long the bug ran, whether the fix is complete, or whether the same loadout persistence problem exists anywhere else.
What the update changes
- Multiplayer. Scorestreak selections no longer fall back to their default selections when a player has set a custom configuration.
- Zombies. Quest items could fail to appear in the inventory when joining a match in progress on Rex Infernus. Fixed.
- Zombies. Players took unintended damage over time inside one room on Rex Infernus. Fixed.
- Scope. Described as a small update rolling out on all platforms. No download size, no downtime window, no other multiplayer changes listed.
Why Hardcore SnD cares
Competitive ranked Search runs without scorestreaks, so on paper this is a pub lobby problem. In practice, pub lobbies are where most hardcore Search actually gets played, and where new players get evaluated. In hardcore the minimap is off, so a UAV is not a bonus. It is the only information in the round that is not earned by sound or by a body.
- A call you cannot cash. You tell three teammates you have a UAV coming at the next plant. The game has quietly given you something else. That is a lost round, and it looks like a lost round on you.
- It poisons your own data. If you are tuning what streaks actually earn their score cost in hardcore Search, a silent revert means you were never testing the setup you thought you were.
- Check it before you blame yourself. Weeks of players insisting their streaks would not stick turned out to be a real bug. If something in your class has felt wrong, open the menu and look rather than assuming it is you.
- It is a persistence bug, not a balance one. The category matters. A game that does not reliably run the configuration you selected is the same class of problem as settings that do not save, and that is worth watching into launch.
A loadout you cannot trust is worse than a bad loadout. At least you can plan around a bad one.
What is not confirmed
Activision did not say how long the bug was live, what caused it, how many players it hit, or whether every path that caused a revert is now closed. The post says addressed, which is the word Activision uses whether a fix is total or partial. It also says nothing about whether other loadout choices, such as perks or attachments, ever reverted the same way.
What would verify it
The simplest check is your own: set a custom streak configuration, back out, join a match, and see what you actually spawn with. If the community reports stop after this build, the fix held. If the Season 06 patch notes on September 17 revisit scorestreaks or loadout persistence again, it did not, and that becomes the story.