I received this item as a reward from an overseer's crate. It looks to be part of a collection but is not tagged as one. \aITEM -622625187 282421539:Ropscion's Acidic Slough\/a
I have an item like that stuck in guild collection depot (for a while now). I don't know how I got it but same, I can't use it (it's level 90): \aITEM 1511062270 -2079126350 0 0 0:[Fire Shard]\/a
Reported here a fair while back: https://forums.daybreakgames.com/eq...d-ropsicon-mindseyes-relic-collection.592914/ Upvoted and now pushed back to page 5.. The Devs must be aware of it, as they removed the result that inspecting it opened the collection window without any patch message. It still shows on broker as a collection item and it would seem a lot have sold for a lot of plat...I am sure to the disappointment of the buyer as it will not add to collection. Give the change, and that a lot of people have got it as a rare reward from overseers, and that it is an actual tradable version of the no trade heroic shiny from the set, I assume the silence with the change is that they consider it an exploit to win it in overseer.
My issue is older, I discovered it on Test on Nov 20, 2019 @ 2:05:54 pm Checking on EQ2U, there are 2 items called Fire shard: \aITEM 1511062270 -2079126350:Fire Shard\/a https://u.eq2wire.com/item/index/1511062270 discovered in 2018 and up (I guess I got mine from the guild NPC that trades loot for shinies) \aITEM 1535360963 -1525168942:Fire Shard\/a (NOT THE SAME item ID) \aITEM 1535360963 -1525168942:Fire Shard\/a which is a collectible from Tears of Veeshan discovered in 2013 The problem is the same with your item, aka Ropscion's Acidic Slough: \aITEM -622625187 282421539:Ropscion's Acidic Slough\/a https://u.eq2wire.com/item/index/3672342109 discovered on January 15th \aITEM -94917609 282421539:Ropscion's Acidic Slough\/a https://u.eq2wire.com/item/index/4200049687 no-trade collection bit from AC heroic instances discovered on December 18th. In both cases, the problem is the same: a NPC/other mean of getting the collection gives a duplicate Item that doesn't have the same ID and, obviously, doesn't work. Fix should be to merge the not-working one with the working one. (and I'll go copy that in the old thread)