Hey, I have a weird bug that has screwed up my character. I clicked on a ring in my inventory to move it and the game crashed. When I logged back in, the ring was in the middle of my screen and it wouldn't move. I can move the cursor around (the pointy hand) but I can't click on anything or move or use any abilities. I can't even use the menu because I can't click. All the while, this stupid ring is just sitting there stuck in the middle of my screen. I logged out and logged in 24 hours later but the problem persists.

However I can still play properly and without any issue on my other characters.

Anyone experienced this before? Any fix tips?
Thanks!

Turn your h4x off ez fix XD

The immediate solution to your problem is a bannable offence. Ladder reset might fix it.

The ring seeks his owner.. it must be destroyed in the fires of mount doom

you're the ring bearer now, mister frodo

Sounds like a problem another user had on D2LoD -EU


(EXAMPLE) Semi - Bricked

#1- https://forums.d2jsp.org/topic.php?t=92936712&f=21&o=0 (most famous case)

#2- https://forums.d2jsp.org/topic.php?t=83494851&f=21

#3- https://forums.d2jsp.org/topic.php?t=81775326&f=21

#4- https://forums.d2jsp.org/topic.php?t=84629931&f=21

AFAIK, even blizzard support cant help / refuses to rollback character.
They Officially investigate this issue (a post from "Eaty") they came to the conclusion that is a game breaking bug.

He uploaded s/s from official" blizzard support" on a different topic.
if i remember correctly, he has made like 3-4? Of topics about this issue

i tried to help eaty by dumping his inv/stash/cube item datas and then using every packet method i could think of to 'drop' or move the item(s). if i recall i was able to open the stash and/or cube but not able to clear the cursor. doubtful even blizzard has any other method(s) available to fix this state once its locked in. i had some theory about how it happened based on item data and where the open space in inventory was but i dont remember anymore

tl;dr char fkd sry m8

I remember hearing about this bug myself when it first came around.
Kind of shocked it still exists and there isn't a fix (that is known to fix it).