Didn't find what you were looking for?

New post
Bungie Answered

Missing Vandal Skin After Completing Compiler

Hello Bungie Support, I completed the Compiler encounter tonight and received the achievement confirming completion. However, I did not receive my Vandal skin. I personally dealt damage to the Compiler and successfully extracted after defeating it, so I believe I met all the requirements. Could you please look into this and help me receive my missing reward? Thank you, Alex
0

Comments

3 comments
  • Official comment

    Hi there,

    Thank you for reaching out and for reporting this.

    Please provide the following details to add to your report:

    • Your Platform
    • The approximate date and time of when this happened
    • Did your crew start the Compiler encounter?
    • Was this a fight involving multiple crews or just yours?
    • Do you have video or screenshots showing those hits?
    • Did your friends get the skin/Codex from the same run? If so, what are their Bungie IDs?
    • Was the missing reward just the skin, or also Codex progress?

    If you have a video or clip from the encounter, you can upload the footage to a public video hosting site, like YouTube, then post the link here and we’ll be glad to take a look.

  • I’m on Xbox. I posted about the issue within an hour of it happening.

    Our crew started the Compiler encounter, and it involved multiple crews. Unfortunately, I don’t have any screenshots or video of the hits.

    My crew members were:

    * JadeTheGiant#9308 — did not have the skin beforehand and received it from that run.
    * Trev_Bozlee#8963 — already had the skin before the encounter.

    I also did not have the skin before the encounter, but unlike JadeTheGiant#9308, I did not receive it after completing the encounter.

    I did receive the Codex progress/reward from completing the Compiler encounter. The only reward I’m missing is the Vandal skin.

    0
  • Hi again,

    Thank you for sharing these additional details.

    Please know this issue has been flagged to the team for investigation. We apologize for the significant inconvenience caused.

    0

Please sign in to leave a comment.