originally posted in:BungieNetPlatform
Turns out that if you access this username via the bungie users endpoint it works, but not with the destiny user endpoint.
Does anyone know why 2 accounts on https://www.bungie.net/ of type 1 (XboxLive) are allowed to have the same username?
https://www.bungie.net/en/Profile/1/4611686018446746696
https://www.bungie.net/en/Profile/1/4611686018433349139
Both are 'Ziyco'. This has huge implications for the reliability of username based searches for Destiny websites and apps.
Both have associated Xbox live accounts but the lvl 8 Warlock seems to be a bug, either a Bungie test account with the same name or an old sample from the players account.
Really can't figure this one out.
English
-
Edited by Seraphsys: 3/12/2015 8:26:43 AMAny help?
-
Edited by Korvinstine: 3/14/2015 4:40:56 PMmaybe one is xbox 360, one is xbox one.
-
Unlikely since bother would still be part of the xbox live network. If the xbox live networks are separate and allow 2 players with the same username then should not the destiny api have separate system types for xbox360 and xboxone. I could be that you are correct. In which case we will need a new system type to differentiate the 2 networks. Any input from a Bingie API perspective?
-
Edited by TTL Goose: 4/22/2015 8:55:30 PMBumped into this problem today. I have a user who played Destiny on Xbox 360 w/ a Gamertag named "Apples" for example. When hey got an Xbox One, he renamed his old Xbox360 gamertag "Oranges" and made a new gamertag on Xbox One "Apples". Now he has two accounts on Destiny and both point to the same gamertag. One account points to the Guardians made on the account while played on their 360, and the other points to the Guardians made while playing on their Xbox One. Did you find a solution for this? -- Nevermind, saw the post above.