Minecraft Forums

Hello!

Thanks for the honest words. It doesn't sound rude at all and you are right. To tell you the truth, I keep updating regionfixer because has became pretty important in the community and it feels the right thing, but since I played minecraft and coded for fun a lot of time has passed and a lot of things have changed.

I have little free time, and when I have it I prefer to use it to unwind. I have tried to update the windows exe but the library I used has been deprecated since then, the same goes for the GUI. You are right about the wiki, english is not my mother language and, again, I choose not to spend my time in that. If you are finally successful, feel free to create a proper tutorial and I will link to it, or add it to the wiki.

That said, I have no idea what is going on, and I'm really sorry to not be able to help you. As you say that change in ouput from regionfixer seems promising. What triggered that change? What did you do? That seems like a good path to investigate. Please report with any information you have and I will try to help.

To fix this issue, stop the server than try deleting all the files other than obviously server.jar, world or what ever the name of your world is, server.properties and the eula text file than restart the server and you should be able to break stuff and no longer have the issue.

I assume it's usercache.json causing the issue but to be sure deleting and letting it recreate the files is a cleaner answer to make sure.

I've another problem. I have a previously corrupted world(which I fixed already), but then when I loaded in again, I found 1 corrupted chunk. When I first use the--processes command, It shows there is 1 wrongly located chunk, therefore I tried to use the --delete-wrong-located yet it doesn't work. I chose to use --processes again, and this time, It says there isn't any chunk problem, but when I revisits the world, the corrupted chunk is still there. What should I do?

Here's the scan result:

Welcome to Region Fixer!
(version: 0.3.2)

############################################################
#####  Scanning world: Corrupted_World_And_Chunk_Test  #####
############################################################

World info:
There are 26 region files, 1 player files and 15 data files in the world directory.

-------------------- Checking level.dat --------------------
'level.dat' is readable

---------------- Scanning UUID player files ----------------
1 of 1|##########################################################|Time: 0:00:00

------------- Scanning old format player files -------------
Info: No files to scan.

---------- Scanning structures and map data files ----------
15 of 15|########################################################|Time: 0:00:00

------------------ Scanning region files -------------------
26 of 26|########################################################|Time: 0:00:05


############################################################
##### Scan results for: Corrupted_World_And_Chunk_Test #####
############################################################


Unreadable player files:
No problems found.

Unreadable data files:
idcounts.dat

Chunk problems:
No problems found.


Region problems:
No problems found.

Hello!

Well, I'm sorry to say that you have to fix that chunk yourself.

That chunk that you show me in the screenshot is not a corrupted chunk because it can be opened.

That chunk might look wrong-located (I would is it out of place) but it's not wrong located in the regionfixer sense. For a chunk to be wrong located the coordinates from the chunk file and the region file should disagree. And in that case they don't disagree. So, you have to fix that with a world editor.

Don't hesitate to ask if you need anything else.

A new release is out!

Bugs fixed and new features. Region Fixer can now scan region poi files. See:

https://github.com/Fenixin/Minecraft-Region-Fixer/releases/tag/v0.3.3

thank you!

I made an account just to help someone out who was stuck like me:


Great tool but takes some modifying for certain W10 users. I'm using W10 64-bit with latest updates as of today.

Initially on file scan it refused to detect my path to my world folder. To mitigate this I had toclone my world folder off my dedicated server and place in a temp storage on one of my SSDs:

K:\HORCRUX\Minecraft-Region-Fixer-master>python regionfixer.py "K:\HORCRUX\Villages\world"

It would then detect and start its scan, only to be stopped around 30% on the region file scan due to:

------------------ Scanning region files -------------------
214 of 353|################################                      |ETA:  0:01:28

Ops! Something went really wrong and regionfixer crashed.


Bug report:

**********
*** Exception while scanning:
*** r.0.8.mca
**********
*** Printing the child's traceback:
*** Exception:<class 'UnicodeDecodeError'>'utf-8' codec can't decode byte 0xed in position 3: invalid continuation byte
**********
*** File K:\HORCRUX\Minecraft-Region-Fixer-master\regionfixer_core\scan.py, line 809, in scan_region_file
***   entity_limit)**********
*** File K:\HORCRUX\Minecraft-Region-Fixer-master\regionfixer_core\scan.py, line 908, in scan_chunk
***   chunk = region_file.get_chunk(*coords)**********
*** File K:\HORCRUX\Minecraft-Region-Fixer-master\nbt\region.py, line 599, in get_chunk
***   return self.get_nbt(x, z)**********
*** File K:\HORCRUX\Minecraft-Region-Fixer-master\nbt\region.py, line 578, in get_nbt
***   nbt = NBTFile(buffer=data)**********
*** File K:\HORCRUX\Minecraft-Region-Fixer-master\nbt\nbt.py, line 628, in __init__
***   self.parse_file()**********
*** File K:\HORCRUX\Minecraft-Region-Fixer-master\nbt\nbt.py, line 655, in parse_file
***   self._parse_buffer(self.file)**********
*** File K:\HORCRUX\Minecraft-Region-Fixer-master\nbt\nbt.py, line 493, in _parse_buffer
***   tag._parse_buffer(buffer)**********
*** File K:\HORCRUX\Minecraft-Region-Fixer-master\nbt\nbt.py, line 493, in _parse_buffer
***   tag._parse_buffer(buffer)**********
*** File K:\HORCRUX\Minecraft-Region-Fixer-master\nbt\nbt.py, line 404, in _parse_buffer
***   self.tags.append(TAGLIST[self.tagID](buffer=buffer))**********
*** File K:\HORCRUX\Minecraft-Region-Fixer-master\nbt\nbt.py, line 476, in __init__
***   self._parse_buffer(buffer)**********
*** File K:\HORCRUX\Minecraft-Region-Fixer-master\nbt\nbt.py, line 493, in _parse_buffer
***   tag._parse_buffer(buffer)**********
*** File K:\HORCRUX\Minecraft-Region-Fixer-master\nbt\nbt.py, line 404, in _parse_buffer
***   self.tags.append(TAGLIST[self.tagID](buffer=buffer))**********
*** File K:\HORCRUX\Minecraft-Region-Fixer-master\nbt\nbt.py, line 476, in __init__
***   self._parse_buffer(buffer)**********
*** File K:\HORCRUX\Minecraft-Region-Fixer-master\nbt\nbt.py, line 493, in _parse_buffer
***   tag._parse_buffer(buffer)**********
*** File K:\HORCRUX\Minecraft-Region-Fixer-master\nbt\nbt.py, line 493, in _parse_buffer
***   tag._parse_buffer(buffer)**********
*** File K:\HORCRUX\Minecraft-Region-Fixer-master\nbt\nbt.py, line 493, in _parse_buffer
***   tag._parse_buffer(buffer)**********
*** File K:\HORCRUX\Minecraft-Region-Fixer-master\nbt\nbt.py, line 353, in _parse_buffer
***   self.value = read.decode("utf-8")
**********

After much digging and very long tldr, the encoding/decoding needs to be tweaked in the 'nbt.py' file from 'utf-8' to 'latin-1'. Don't ask me why, I just know it does for me. Lines 347-359 in 'nbt.py' should now look like this:

 # Parsers and Generators
 def _parse_buffer(self, buffer):
 length = TAG_Short(buffer=buffer)
 read = buffer.read(length.value)
 if len(read) != length.value:
 raise StructError()
 self.value = read.decode("latin-1")

 def _render_buffer(self, buffer):
 save_val = self.value.encode("latin-1")
 length = TAG_Short(len(save_val))
 length._render_buffer(buffer)
 buffer.write(save_val)

Returning to the scan it now completes with no issues:

############################################################
################# Scan results for: world ##################
############################################################


Unreadable player files:
No problems found.

Unreadable data files:
No problems found.

Chunk problems:
----------------------------------------------
| Problem | Corrupted  Wrong located  Total  |
----------------------------------------------
|  Count  |    23          8146       122000 |
----------------------------------------------

Region problems:
No problems found.

Thanks for the time for making this plug dev, good luck to others!

Thank you very much for your comment

Quote from DAMCServer»

Great tool but takes some modifying for certain W10 users. I'm using W10 64-bit with latest updates as of today.

Initially on file scan it refused to detect my path to my world folder. To mitigate this I had toclone my world folder off my dedicated server and place in a temp storage on one of my SSDs:

That is something new. I Do most of my coding, if not all, in a W10 machine. There must be something strange with your paths. I have a small collection of corrupted world and they are in a different hard drives than regionfixer is. Anyway, I'm glad it worked that way.

Quote from DAMCServer»

It would then detect and start its scan, only to be stopped around 30% on the region file scan due to:

------------------ Scanning region files -------------------
214 of 353|################################                      |ETA:  0:01:28

Ops! Something went really wrong and regionfixer crashed.


Bug report:

**********
*** Exception while scanning:
*** r.0.8.mca
**********
*** Printing the child's traceback:
*** Exception:<class 'UnicodeDecodeError'>'utf-8' codec can't decode byte 0xed in position 3: invalid continuation byte
**********
*** File K:\HORCRUX\Minecraft-Region-Fixer-master\regionfixer_core\scan.py, line 809, in scan_region_file
***   entity_limit)**********
*** File K:\HORCRUX\Minecraft-Region-Fixer-master\regionfixer_core\scan.py, line 908, in scan_chunk
***   chunk = region_file.get_chunk(*coords)**********
*** File K:\HORCRUX\Minecraft-Region-Fixer-master\nbt\region.py, line 599, in get_chunk
***   return self.get_nbt(x, z)**********
*** File K:\HORCRUX\Minecraft-Region-Fixer-master\nbt\region.py, line 578, in get_nbt
***   nbt = NBTFile(buffer=data)**********
*** File K:\HORCRUX\Minecraft-Region-Fixer-master\nbt\nbt.py, line 628, in __init__
***   self.parse_file()**********
*** File K:\HORCRUX\Minecraft-Region-Fixer-master\nbt\nbt.py, line 655, in parse_file
***   self._parse_buffer(self.file)**********
*** File K:\HORCRUX\Minecraft-Region-Fixer-master\nbt\nbt.py, line 493, in _parse_buffer
***   tag._parse_buffer(buffer)**********
*** File K:\HORCRUX\Minecraft-Region-Fixer-master\nbt\nbt.py, line 493, in _parse_buffer
***   tag._parse_buffer(buffer)**********
*** File K:\HORCRUX\Minecraft-Region-Fixer-master\nbt\nbt.py, line 404, in _parse_buffer
***   self.tags.append(TAGLIST[self.tagID](buffer=buffer))**********
*** File K:\HORCRUX\Minecraft-Region-Fixer-master\nbt\nbt.py, line 476, in __init__
***   self._parse_buffer(buffer)**********
*** File K:\HORCRUX\Minecraft-Region-Fixer-master\nbt\nbt.py, line 493, in _parse_buffer
***   tag._parse_buffer(buffer)**********
*** File K:\HORCRUX\Minecraft-Region-Fixer-master\nbt\nbt.py, line 404, in _parse_buffer
***   self.tags.append(TAGLIST[self.tagID](buffer=buffer))**********
*** File K:\HORCRUX\Minecraft-Region-Fixer-master\nbt\nbt.py, line 476, in __init__
***   self._parse_buffer(buffer)**********
*** File K:\HORCRUX\Minecraft-Region-Fixer-master\nbt\nbt.py, line 493, in _parse_buffer
***   tag._parse_buffer(buffer)**********
*** File K:\HORCRUX\Minecraft-Region-Fixer-master\nbt\nbt.py, line 493, in _parse_buffer
***   tag._parse_buffer(buffer)**********
*** File K:\HORCRUX\Minecraft-Region-Fixer-master\nbt\nbt.py, line 493, in _parse_buffer
***   tag._parse_buffer(buffer)**********
*** File K:\HORCRUX\Minecraft-Region-Fixer-master\nbt\nbt.py, line 353, in _parse_buffer
***   self.value = read.decode("utf-8")
**********

After much digging and very long tldr, the encoding/decoding needs to be tweaked in the 'nbt.py' file from 'utf-8' to 'latin-1'. Don't ask me why, I just know it does for me. Lines 347-359 in 'nbt.py' should now look like this:

 # Parsers and Generators
 def _parse_buffer(self, buffer):
 length = TAG_Short(buffer=buffer)
 read = buffer.read(length.value)
 if len(read) != length.value:
 raise StructError()
 self.value = read.decode("latin-1")

 def _render_buffer(self, buffer):
 save_val = self.value.encode("latin-1")
 length = TAG_Short(len(save_val))
 length._render_buffer(buffer)
 buffer.write(save_val)

Returning to the scan it now completes with no issues:

############################################################
################# Scan results for: world ##################
############################################################


Unreadable player files:
No problems found.

Unreadable data files:
No problems found.

Chunk problems:
----------------------------------------------
| Problem | Corrupted Wrong located Total |
----------------------------------------------
| Count | 23 8146 122000 |
----------------------------------------------

Region problems:
No problems found.

Thanks for the time for making this plug dev, good luck to others!

This can be very useful. Could you provide a region file that thows this error? Do you mind If I open a issue with your comment for future reference? I have seen this problem before and I thought it was solved.

Thank you for your comment.

Several notes after testing today:

If you are updating an older server version (in my case 1.12.2) to the latest (1.16.1 at this time) you must use this process:

1. Make a backup of everything, if you're like me you're going to run into issues

2. Stop your server and edit your start script to include '--forceUpgrade' in the startup flags

3. If going from 1.12 you'll need to update to 1.13 first. Download the latest jar for 1.13 and replace

4. Start server and let it check/update your chunks. Once complete stop your server

5. Edit your start script and remove the forceUpgrade flag

6. Replace the server jar with the latest 1.16.1 (or whatever at your time of reading) jar

7. Start server - it should load no issues

8. Enjoy

The corrupted chunk issues I had originally were almost all cleared up doing the process above.

Region fixer is still a very useful tool if your map contains corrupted chunks somewhere and inadvertently crashing your server.

Is it possible to fix an unreadable idcounts.dat file ?

Quote from BlueEnni»

Is it possible to fix an unreadable idcounts.dat file ?

This file only stores the number of the last map created, so you can easily recreate it by copying the file from another world and editing it with NBTExplorer to set the "Data\map" tag to the number of the map data file with the highest number (e.g. if you see map_100.dat set it to 100. Higher values shouldn't cause issues but lower will cause newly created maps to overwrite old ones, so it is necessary for this file to exist with the correct count).

Quote from TheMasterCaver»

This file only stores the number of the last map created, so you can easily recreate it by copying the file from another world and editing it with NBTExplorer to set the "Data\map" tag to the number of the map data file with the highest number (e.g. if you see map_100.dat set it to 100. Higher values shouldn't cause issues but lower will cause newly created maps to overwrite old ones, so it is necessary for this file to exist with the correct count).

Thank you for your answer. I completely forgot to answer BlueEnni's question. Also, I didn't know that, and it's a very useful information!

New version out. This new version is mostly thanks to contributors. POIs can be scanned now and it should fix a few issues. Get from github cloning master branch or from the releases page:

https://github.com/Fenixin/Minecraft-Region-Fixer/releases/tag/v0.3.4

New version out! Contributors have updated regionfixer to work with 1.18.1 worlds. Get from github cloning master branch or from the releases page:

https://github.com/Fenixin/Minecraft-Region-Fixer/releases/tag/v0.3.5

hello

I am trying to fix a 1.18.31 version of a World with Minecraft-Region-Fixer, but I get the following error message.

(Is 1.18.31 not yet supported?)

Warning: The folder /home/-/minecraft/backups/K.World doesn't look like a minecraft world. I'll skip it.

What could be the reason? How can I fix it?
Version 0.3.5 of Minecraft-Region-Fixer is used.

The contents of the folder are

4096 Jun 8 20:59 db
2539 Jun 8 21:00 level.dat
2539 Jun 8 20:59 level.dat_old
8 Jun 8 21:00 levelname.txt

This World is generated and used in bedrock Server.