mega12345mega / NBT-Editor

Edit items, blocks, and entities in-game.
MIT License
31 stars 9 forks source link

Weird crash report when opening up client chest thingy #92

Closed Fnige closed 3 weeks ago

Fnige commented 3 months ago

Log: https://gist.github.com/Fnige/bfc863549284cdf953d5575b7fe2e30c

Basically all I had to do is open up the client chest and it seemed to crash. There was also errors about files not existing too which you can see here so maybe thats related to the issue?

mega12345mega commented 3 months ago

It seems like the mod is failing to create the page_names.json file, which is where the names for the client chest pages are stored. I don't know why this would happen - is your hard drive full, or does the game directory have write access restrictions? You could try manually creating the file in <game directory>/nbteditor/client_chest/page_names.json with the contents {}. (If this fixes it, I imagine setting pages names would cause an error when trying to write to it again.)

Fnige commented 3 months ago

Interestingly enough adding the file seems to have fixed all of the issues which is weird. Idk if this could happen with someone else so you can close the issue if you want

mega12345mega commented 3 months ago

Just in case, I'll add some code to explicitly create the file, since it might be some weird operating system thing or something that causes the current code to be ambiguous.

mega12345mega commented 1 month ago

I believe a dev build with a fix for this has been available for a while now, I just had forgotten to label the issue. Looking at what I changed, it seems like the problem may have been that the client_chest folder was missing, so it was unable to create the page_names.json file inside of it. If you happen to still remember, can you confirm that when you created the file you also had to create the client_chest folder?

Fnige commented 1 month ago

My memory is nonexistant so sadly I do not remember but maybe?

Fnige commented 1 month ago

image Aha I did have to make the folder when fixing that issue

mega12345mega commented 3 weeks ago

I've now fixed this in v2.0.0!