originally posted in:BungieNetPlatform
Hi all,
I have a user called Ziyco on the xbox network for destiny.
They are a 32 Hunter / 31 Titan / 30 Warlock over at;
[url]http://destinytracker.com/destiny/overview/xbox/ziyco[/url] and
[url]http://www.destinydb.com/guardians/xbox/2305843009225984049-ziyco[/url]
But they are a single 8 Warlock at;
[url]http://destinystatus.com/xbl/Ziyco[/url] and
[url]http://www.littlelight.link/xbox/Ziyco[/url]
This is the only player I can find this bug on. What is going on, any ideas
English
-
I did some research and found several accounts in this state. Here is how it happens 1. User A with gamertag Ziyco plays Destiny, and his gamertag is stored in our DB. 2. User A changes his gamertag to something else, but never returns the play Destiny 3. User B changes his gamertag to Ziyco and plays Destiny 4. Now we have two Ziycos in our DB. I have filed a but to fix search so that only the most recent Ziyco is returned rather than the oldest.
-
The second one has a capital
-
Edited by Seraphsys: 3/12/2015 8:26:30 AMTurns 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.