I am a D2 player that really got into the game this year and I am inquiring on behalf of my friend who is the owner of this account making the post.
I got him to install Destiny 2 for the first time via PS5 to play cross-platform with me on PC. But during the cross-platform onboarding of making a Bungie account through PlayStation for the first time, he seemed to have accidentally skipped the name selection aspect. He got assigned a generic Guardian name of Guardian1152. We have been trying to use his one-time name change to set it to his preferred gamertag of ATK_Anton which is used on PSN and all other platforms we play together on. However, we have not been able to as we keep getting the message, along the lines of "account name can only be changed once" even though the name never changed, and it is a brand-new account created today (Less than 8 hours old as of posting). At first, we thought maybe the issue was his phone bugging out, but after trying it on my computer using his login credentials it seems like it is an account-level issue rather than a particular device. We do get the option of using a suggested name which Bungie recommends his PSN name stated above. But when we try to save it, it does not work.
He has been enjoying it so far and was planning on getting the DLCs on Sale to run through the stories as well as Revenant. But this issue is a bit of a problem big for us as it caused a lot of confusion during our run of the New Light Cosmodrome missions. Since there were a few others with generic Guardian names.
Is there anything we can do about it to fix this issue, is he going to be forever stuck like that?
-
I got the same issue. Hope somebody could fix that soon.
-
[quote]Bungie Names cannot be changed. We hope to fix this as quickly as possible.[/quote] https://help.bungie.net/hc/en-us/articles/27062192032404-Destiny-2-Year-7-Known-Issues-and-Vital-Information [quote] along the lines of "account name can only be changed once"[/quote] Outdated text that simply means the account has available name changes, but given the issue above you cannot currently use them.