Treyarch accidentally added legacy tokens to Call of Duty: Black Ops 6, took them away, and then promised to restore them after realising they can't put the toothpaste back in the tube

pcgamer.com:

There was a pleasant surprise waiting for players when Call of Duty: Black Ops 6 went live. XP tokens from previous Call of Duty games were there sat in everyone's inventory, making it easier to face the grind and level up characters or weapons. Usually, players can get these by completing limited time events, finishing the battle pass, or sometimes via collaborations.

Legacy XP tokens aren't unheard of. Call of Duty: Modern Warfare 2 and Modern Warfare 3 both let players use previously purchased or unlocked items and cosmetics as well as double XP tokens from various Call of Duty games.

Unfortunately, this time it didn't seem like the feature was intentional. One of the latest Call of Duty: Black Ops 6 updates erased legacy tokens, or as Activision put it: «Fixed an issue that incorrectly allowed legacy XP tokens to be activated in the Black Ops 6 UI.» We just can't have nice things.

This sudden change was matched by Black Ops 6 players who did a complete 180, going from praising Treyarch for providing them with this helping hand to condemning the devs for patching out something that everyone wanted. Players were calling the move «greedy» and «a joke», with one arguing that legacy tokens were disabled «to artificially inflate [Treyarch’s] retention metrics.» But the story didn't stop there. Over the weekend players carried on telling Treyarch just how upset they were about this change, and it actually ended up leading to something.

«With the start of Season 01, a UI bug allowed players to activate legacy XP tokens in Black Ops 6,» Treyarch says. «Unfortunately, it also introduced some potential risk to game stability, which is why it was patched yesterday.

»We realize how much players appreciate being able to redeem legacy XP tokens in both BO6 and Warzone, so we are currently testing a way to implement this change correctly in a future update. This allows us time to ensure stability is maintained before we reintroduce this feature."

I’m not qualified to comment on