Fenixin/Minecraft-Region-Fixer

Cannot start regionfixer..

Closed this issue · 8 comments

Hello i cant start regionfixer anymore.. when i type the command and hit enter nothing will happen and if i try to use RegionFixer on Ubuntu it says this:

Traceback (most recent call last): File "regionfixer.py", line 29, in <module> from regionfixer_core import world File "/home/******/Minecraft/Java/Vanilla/RF/Minecraft-Region-Fixer/regionfixer_core/world.py", line 26, in <module> from .util import table File "/home/******/Minecraft/Java/Vanilla/RF/Minecraft-Region-Fixer/regionfixer_core/util.py", line 27, in <module> from . import world ImportError: cannot import name world

I have the same issue. Ubuntu 18.04:

Traceback (most recent call last):
  File "regionfixer.py", line 29, in <module>
    from regionfixer_core import world
  File "/home/server/Skyblock/regionfixer/0.3.1/Minecraft-Region-Fixer-0.3.1/regionfixer_core/world.py", line 26, in <module>
    from .util import table
  File "/home/server/Skyblock/regionfixer/0.3.1/Minecraft-Region-Fixer-0.3.1/regionfixer_core/util.py", line 27, in <module>
    from . import world
ImportError: cannot import name world

It only started to happen with 0.3.1 version.

Hello!

This looks like you are using python2 instead of the mandatory python3. Regionfixer will only work with python3.

Please, try to use it with python3 and report back.

image
@Fenixin I don't think that's the problem.

From your screenshot I see that you are scanning a region directory, could you please try to scan the world folder or add *.mca at the end of the command prompt? I will try to reproduce this.

@Scheshi, In your last image you are using python when invoking regionfixer.py but python3 when calling for version. In my ubutu system if I use python python 2 is ran, and if I use python3 the version 3 is ran. Like this:

$ python --version
Python 2.7.17
$ python3 --version
Python 3.6.9

Could you please test regionfixer with python3 instead of python?

Yes, it working with python3. Thank you for help!

I'm going to close this, the issue seems to be python version.