Call of Duty: Black Ops 6 was released on October 25 as the twenty-first installment of the Call of Duty series and the seventh main entry in the Black Ops sub-series. As is usually the case with any newly released video game, the Black Ops 6 also brings in some initial bugs that are troubling gamers. As per some reports, some Black Ops 6 players are having trouble saving the attachments on Blueprint weapons.
For those unaware, Blueprint weapons are pre-designed versions of the guns that players often acquire through events in-game purchases, or progression rewards. Players can also customize these weapons as per their requirements. However, a bug isn’t letting players modify attachments on Blueprint weapons.
Black Ops 6 attachments not saving on Blueprint weapons
While gamers can customize their attachment, the changes don’t stay. Players report that their customizations don’t show up in the game even though they have saved it. The old configurations remain unchanged or revert once they start the game.
Moreover, removing or changing attachments or completely resetting the loadouts doesn’t fix this bug. Some players even reported that modifying attachments causes certain slots to become empty, leaving the weapon partially unequipped. According to reports, this issue appears to be affecting players on multiple platforms including Xbox and PC. Furthermore, this bug also affects players who purchased the Vault Edition Blueprints.
Is it a bug or an intended thing?
Many players who are unable to save attachments on blueprint weapons are wondering if this is an intended change by Treyarch or a bug. Well, this is something we can’t answer as the developers of the game have not cleared it up. However, if it’s a bug then, we expect it to be resolved in one of the upcoming game updates.
In any case, weapon attachment customization is a critical feature in COD games that allows players to adapt their playstyle. However, this bug completely limits players’ ability to personalize the gameplay. Unfortunately, there aren’t any workarounds that would help you fix this problem. Also, this bug remains unacknowledged as of yet. That said, we will let you know as and when this bug is resolved.
For more such content, bookmark ASSEMBLEDEBUG.