Imagine how mad you would be if you ID'ed a Tyrael's inside before the fix

Don't trust randoms on the internet. ID the rare items proper.

This post was edited by Hell Knight on Apr 3 2026 07:06am

Someone that frequents this subforum had exactly that happen to them.
He even made it his signature lol.

Also, how do you know it was fixed? Got a blue post?

Also, I believe it was more complicated than just IDing in your cube. It was having the item on your cursor as you picked it up for the first time that triggered it.

This post was edited by Emiliaaa on Apr 3 2026 06:43am

theres gotta be more to the bug, ive been iding from cube since rotw release and never had this happen.

This post was edited by C4NTWO on Apr 3 2026 06:41am

when was it broken? i id all items from cube and haven’t run into this issue.

In that case, don't trust me. I have had the problem once with a trivial item and now it worked for me, no bluepost.

Skill issue, if you are not playing sweaty enough to find edge case bugs, are you even playing hard enough?

It's a pretty rare bug, but has happened enough times to people in this subforum. It appears to only happen extremely rarely and only if you pickup the item onto your cursor before placing it into your inventory to identify it.

If you're playing on controller and putting directly in your cube or just picking the item up into your inventory, you won't ever run into this bug.

nah, those people would attempt to place in cube. cube was full, so they’d drop the item and make room. then it would break the chronicle id.

or that clown with the tyrael post who looted to cube, then moved to shared stash, then left and went to a new game before identifying.

I thought it was the "pickup on cursor, cube full, drop item" at first as well, but that doesn't seem to be the case. It really is just as simple as having it on your cursor the first time you pick it up, but as for why it's rare, there must be another unknown step that triggers it.

I told people the same thing as you, but it seems that's not the case in every single time it's been triggered.