(edited by Outlaw.3421)
Bug Fixed: Collections and sPvP
Were you in Heart of the Mists when you did this?
Were you in Heart of the Mists when you did this?
Yes, I believe I was, but I can’t remember for sure. I know some items in the Mists won’t even let you open them until you leave. I can’t remember if the Glove Box was setup that way. I did get another glove box though and chose the light gloves outside the Heart of the Mists, but the result was the same. No collectible unlock. I did not think that the Heart of the Mists would affect the item in that way.
The only thing I can think of is buying it on an alt character just for testing purposes, but other than that – nothing I can do until it is patched.
(edited by Outlaw.3421)
Just wanted to provide an update that I did buy another glove box on an alt character, but still have the same issue where it will not unlock in the collection. In case anyone else tries, now you know.
Could you post two screenshots with your wardrobe and the collection?
[RUC] Riverside United Corps! For Riverside!
For the moment, I am avoiding trying to unlock anything while in the Heart of the Mists. I don’t imagine that everything there is bugged, but it’s not worth taking the chance since it’s just as easy to unlock in PvE.
Could you post two screenshots with your wardrobe and the collection?
I have attached the image you requested. It has my inventory in the top left with the Carapace Gloves showing “Skin Unlocked” (I selected the Carrion stats), the Wardrobe in the top right confirming it is there, and at the bottom, the missing collection for the gloves.
So this issue seems to be linked to another thread updated today: https://forum-en.gw2archive.eu/forum/support/bugs/HotW-Collection-Bugged/first#post4719620
This apparently is an issue with collections and unlocking skins in sPvP (Heart of the Mists), and not the Luminescent Gloves collection specifically.
(edited by Outlaw.3421)
Just wanted to update that the issue is still present as of the patch on 1/27
I want to confirm that the issue has been fixed with the 2/24 patch!