For the sharedstashsave tho, you can pick the most recent saved file before the corrupted ( last played) character. It might have been 2 min ago, or 2 days ago if your unlucky. Your only option is to recover the most recent saved of this character in this backup folder. This saved is corrupted for whatever reasons. You'll notice it wont work and maybe the character will not even appear. Try to copy paste the Sharedstashsave and character from this save. Your last log out before the bug happens is where it happened. So now, you deleted your bugged shardstashsave in Diablo II and you explored the Backup file. Keep in mind those back up are actually made everytime u save and exit. In this backup file, sort by MODIFIED LAST and you will have alot of Saved files and each one have a saved sharedstashsave as it was when u exited the game at that time. IN RECENTS PLUGY UPDATE, they added a BACKUP file in this diablo II folder. If you can log after deleting your respective gameplay sharedstashsave ( Theres 2, 1 normal and 1 HC ), then you know your sharedstash is bugged. Then 1 by 1, delete file ( try shared stash file 1st ) and see if your able to log on any character. Here, save everything in a new folder on your computer. In SP saved files which are under Windows(x) / user / name / saved games / diablo II, you have access to all your saved characters. ( YOUR CHARACTER LAST USED MIGHT BE DELETED, KEEP READING UNTIL THE END) The error was caused by the shared stash, i dont know why but it was that. This is what i did (Plugy SP with up to date version and 1.14d patch). So i just had a scary moment : Cannot connect - bad header error when logging in and after looking online i didnot find anything to help.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |