#43 Shared Stash won't open

[Tom]

I can no longer open my shared stash (hardcore) - it's 'disconnected'. Currently on version 5.9. I noticed it after auto-updating from 5.8, but it could have happened before (it was working the last time I opened GoMule).

I started a new softcore character and put an item in the shared stash, which GoMule can open. I also deleted all GoMule files, and then redownlaoded it, but that didn't fix it. I attached a copy of my HC shared stash if that helps.

[Tom]

I found the culprit. I had an eth Plague Bearer on page 3. Once I transferred that to a character in-game, I could open my shared stash again (and then the test char was listed as 'disconnected'). Hope this helps, thanks for the awesome tool.

[Silospen]

This is a fascinating example

• Before you identify an item, it contains some information on when and who dropped the item so that it can be stored in the chronicle as soon as you identify it
• Once you identify it, that information is removed from the item
• This item is very strange in that it is identified but it still has the chronicle information on it
• You can fix it by moving it out of the stash, on to a character, then save and exit, the item should now be 'correct'

Was there anything weird about the way you unidentified this item or the way you obtained it?

[Tom]

I don't remember where this dropped, and my Chronicle keeps getting reset (I assume Hell Meph, b/c all I really farmed was him and LK chests - so it could have dropped from a rack).

I have been unable to fix it by moving it to another character. Attached is the 'test' character I moved it onto (can't open him in GoMule unless first opening him in-game and then moving the Plague Bearer off him).

Also possibly interesting, I have several 'bugged' rack drops (pretty sure there's an unid Earth Keeper in that first test file attached). GoMule reads and saves it correctly, but if I ID it in game, it will reset the Chronicle.

[Silospen]

Very weird, well I guess we're fixing Blizz's bugs too - thanks for the report, should be working correctly in 5.10 :)