![]() It manages to churn out data for a long time, becoming ever increasingly corrupt, before finally failing outright. It actually reads okay about halfway through, gets to the "Bloody Cobbler (Cobblestone?) tag, and then the compressor starts going off the rails. Well bad news, the file is actually pretty well toast, at the GZip level. This could be a text encoding issue (unicode perhaps?), so maybe odds of a recovery are even better. Inside level.dat make sure you are editing level.dat/Data/Player/Pos and not level.dat/Data/Spawn.The subItem in question is "Bloody Cobbler" with what appears to be a couple invalid characters in the name. 2 Answers Sorted by: 3 In NBTExplorer make sure you are editing the level.dat file, not a playername.dat file as singleplayer worlds read from the level.dat, not one of the playername.dat files in the saves/savename/players/ folder. It's a list of over 3000 tags, of which it's failing about halfway through. I'd say that's a tag you really don't want to be corrupt. What I know so far is that there is malformed data in /FML/ModItemData. A partial recovery may be possible, and it would be nice to put that functionality into the program if it is. I'll have to look a little deeper tomorrow. The good news is that the file is not truncated or otherwise corrupted at the GZIP level. It does say something is wrong at byte 14 or whatever and here is the file:Īnd this file was an Level.dat out of a Modded world just to mention Presumably associated with this error message: Click File on the left top of the Task Manager interface. Message: An entry with the same key already exists.Īt `2.Add(TKey key, TValue value)Īt ()Īt _0.MoveNext()Īt (ExecutionContext executionContext, ContextCallback callback, Object state, Boolean preserveSyncCtx)Īt (ExecutionContext executionContext, ContextCallback callback, Object state, Boolean preserveSyncCtx)Īt (ExecutionContext executionContext, ContextCallback callback, Object state)Īt ()Īlso crashes repeatedly when trying to search for specific values. Then, the File Explorer will be restarted, and see if the File Explorer would just hang again. NBTExplorer encountered the following exception while trying to run: ArgumentException
0 Comments
Leave a Reply. |