Oblivion's Edge set from Vaults of Madness completely ignored by new set collection mechanism

caelianb16_ESO
When going through my backlog of "gear i can now finally salvage" i noticed an item from the Oblivion's Edge set was still showing for me as not having been "collected" yet .... so i went for the context menu to bind it only to discover the item is already bound.

When looking at the Set Collection UI all the sets from Vaults of Madness seem to have been "collected" properly with "Oblivion's Edge" being the sole exception. That entire set remains "not collected" even though i have items from that set bound and in my inventory while actively logged in.

When i asked a guildmate to check his set collections, he also noticed "Oblivion's Edge" was suspiciously void of any collected entries.
  • baratron
    baratron
    ✭✭✭✭✭
    I can confirm that the set adds if you decon it. Which doesn't help if you want to use it, of course.

    GJIEO.png
    Guildmaster of the UESP Guild on the North American PC/Mac Server 2350+ CP & also found on the European PC/Mac Server 1700+ CP

    These characters are on both servers:
    Alix de Feu - Breton Templar Healer level 50
    Brings-His-Own-Forest - Argonian Warden Healer level 50
    Hrodulf Bearpaw - Nord Warden Bear Friend & identical twin of Bjornolfr level 50
    Jadisa al-Belkarth - Redguard Arcanist Damage Dealer level 50

    NA-only characters:
    Martin Draconis - Imperial Sorceror Healer (Aldmeri Dominion) level 50
    Arzhela Petit - Breton Dragonknight Healer (Daggerfall Covenant) level 50
    Bjornolfr Steel-Shaper - Nord Dragonknight Crafter (Ebonheart Pact) level 50 EAGERLY AWAITING HIS BEAR
    Verandis Bloodraven - Altmer Nightblade Healer & clone of Count Verandis Ravenwatch (Aldmeri Dominion) level 50
    Gethin Oakrun - Bosmer Nightblade Thief (Ebonheart Pact) level 50
  • caelianb16_ESO
    Good to know that at least works as a workaround if you just want it added to your collection.

    But I still believe the fact it doesn't add otherwise is a bug, and could point to some sort of internal database/code inconsistency that should probably be looked at a bit more closely.
    Oblivion's Edge so far is the only set for which I have encountered this problem, but that doesn't mean there are not potentially more sets out there affected similarly.
Sign In or Register to comment.