JavaScript is required to use Bungie.net

Help

Help us help you.
Edited by BNGHelp4: 10/19/2017 5:32:05 PM
1043

[BUNGIE] Raid keys erroneously removed from Character Inventory [UPDATE: 10/19/17]

[b][u]UPDATE 10/19[/u]:[/b] As of Destiny 2 [url=https://www.bungie.net/en/Explore/Detail/Update/46410]Hotfix 1.0.5[/url], raid keys should no longer be erroneously removed when players create a new character, or when players log in to alternate characters for the first time after the weekly reset. Additionally, raid keys are no longer removed at the weekly reset, in general. [b]Prior Message[/b] [spoiler] Through our investigations with internal teams, we have identified two instances where Leviathan raid keys are erroneously removed from character inventory. [quote][b]Signing in with alternate characters will remove raid keys if the character had not been signed in since the weekly reset. If a player earns Raid keys and creates a new character, raid keys are removed from inventory.[/b][/quote] To prevent this issue, we advise players sign in with all characters or inspect all characters on the Destiny Companion App prior to completing checkpoints within the Leviathan raid after the weekly reset. Please note: Leviathan raid progress, including key rewards, are reset each week. We are looking to address issues where keys are removed erroneously with a future update. Stay tuned to @BungieHelp for future announcements. [/spoiler]
English
#Help

Posting in language:

 

Cancel Edit Create Fireteam Post Play nice. Take a minute to review our Code of Conduct before submitting your post.

View Entire Topic
  • Also has the issue lost 3 keys. 42 pages since September and no mention of reimbursement. That is a damn travesty. Bungie you're quickly committing suicide here. There are so many things wrong with D2 at the moment. I'm sure if you'd delayed it for 3 months to fix stuff OR you did a better with a longer window, better community interaction during, and not so close to release date, then you might have been ok... I think your senior management needs to take a look at themselves and ask how this was allowed to go so wrong

    Posting in language:

     

    Cancel Edit Create Fireteam Post Play nice. Take a minute to review our Code of Conduct before submitting your post.

    1 Reply
    1 2
    You are not allowed to view this content.
    ;
    preload icon
    preload icon
    preload icon