Почему mcedit выдает ошибку

I just downloaded MCEdit, yet whenever I tried to a world, It crashes. Does anyone knows how to fix it?

Here is the error details:

MCEdit version: 2.0.0-beta14
Python version: 2.7.15 (v2.7.15:ca079a3ea3, Apr 30 2018, 16:30:26) [MSC v.1500 64 bit (AMD64)]
Platform: win32
System version: Windows-10-10.0.18362
Processor: Intel64 Family 6 Model 158 Stepping 10, GenuineIntel

Obtained a GL context with this format:
Valid: True
Version: 4.6
Hardware Accelerated: True
Depth buffer: True, 24
Double buffer: True
Rendering profile: PySide.QtOpenGL.QGLFormat.OpenGLContextProfile.CompatibilityProfile

Driver info:
GL_VERSION: 4.6.0 NVIDIA 441.45 (4, 6)
GL_VENDOR: 'NVIDIA Corporation'
GL_RENDERER: 'GeForce GTX 1650/PCIe/SSE2'

------

Unhandled Exception

Traceback (most recent call last):
  File "mcedit2editorsession.py", line 1643, in viewOffsetChanged (self is a EditorTab)
  File "mcedit2worldviewminimap.py", line 187, in currentViewMatrixChanged (self is a MinimapWorldView)
  File "mcedit2utilraycast.py", line 30, in rayCastInBounds  
  File "mcedit2utilprofiler.py", line 73, in _wrapper (self is a Profiler)
  File "mcedit2utilraycast.py", line 77, in rayCast  
  File "mcedit2utilraycast.py", line 215, in advanceToChunk  
  File "mceditlibworldeditor.py", line 831, in getChunk (self is a WorldEditorDimension)
  File "mceditlibworldeditor.py", line 499, in getChunk (self is a WorldEditor)
  File "mceditlibcachefunc.py", line 77, in __call__  
  File "mceditlibworldeditor.py", line 477, in _getChunkDataRaw (self is a WorldEditor)
  File "mceditlibanviladapter.py", line 922, in readChunk (self is a AnvilWorldAdapter)
AnvilChunkFormatError: [Errno Error loading chunk: KeyError('Key Blocks not found.',)] None: <traceback object at 0x000002833D94BB48>

I just downloaded MCEdit, yet whenever I tried to a world, It crashes. Does anyone knows how to fix it?

Here is the error details:

MCEdit version: 2.0.0-beta14
Python version: 2.7.15 (v2.7.15:ca079a3ea3, Apr 30 2018, 16:30:26) [MSC v.1500 64 bit (AMD64)]
Platform: win32
System version: Windows-10-10.0.18362
Processor: Intel64 Family 6 Model 158 Stepping 10, GenuineIntel

Obtained a GL context with this format:
Valid: True
Version: 4.6
Hardware Accelerated: True
Depth buffer: True, 24
Double buffer: True
Rendering profile: PySide.QtOpenGL.QGLFormat.OpenGLContextProfile.CompatibilityProfile

Driver info:
GL_VERSION: 4.6.0 NVIDIA 441.45 (4, 6)
GL_VENDOR: 'NVIDIA Corporation'
GL_RENDERER: 'GeForce GTX 1650/PCIe/SSE2'

------

Unhandled Exception

Traceback (most recent call last):
  File "mcedit2editorsession.py", line 1643, in viewOffsetChanged (self is a EditorTab)
  File "mcedit2worldviewminimap.py", line 187, in currentViewMatrixChanged (self is a MinimapWorldView)
  File "mcedit2utilraycast.py", line 30, in rayCastInBounds  
  File "mcedit2utilprofiler.py", line 73, in _wrapper (self is a Profiler)
  File "mcedit2utilraycast.py", line 77, in rayCast  
  File "mcedit2utilraycast.py", line 215, in advanceToChunk  
  File "mceditlibworldeditor.py", line 831, in getChunk (self is a WorldEditorDimension)
  File "mceditlibworldeditor.py", line 499, in getChunk (self is a WorldEditor)
  File "mceditlibcachefunc.py", line 77, in __call__  
  File "mceditlibworldeditor.py", line 477, in _getChunkDataRaw (self is a WorldEditor)
  File "mceditlibanviladapter.py", line 922, in readChunk (self is a AnvilWorldAdapter)
AnvilChunkFormatError: [Errno Error loading chunk: KeyError('Key Blocks not found.',)] None: <traceback object at 0x000002833D94BB48>

Hi, I am 34486 not a buddy of mine 34486SCI heh.

I have noticed this with 2 worlds and get the exact same error EACH TIME! Its getting annoying.

An error occurred while opening D:/Servers/HHSDepleted/world/level.dat

‘utf8’ codec can’t decode byte 0xc0 in position 0: invalid start byte

Traceback (most recent call last):

File «mcedit2editorapp.py», line 781, in loadFile (self is a MCEditApp)

File «mcedit2editorsession.py», line 186, in __init__ (self is a EditorSession)

File «mceditlibworldeditor.py», line 233, in __init__ (self is a WorldEditor)

File «mceditlibfindadapter.py», line 62, in findAdapter

File «mceditlibanviladapter.py», line 463, in __init__ (self is a AnvilWorldAdapter)

File «mceditlibanviladapter.py», line 530, in loadMetadata (self is a AnvilWorldAdapter)

File «srcmceditlibnbt.pyx», line 590, in mceditlib.nbt.load

File «srcmceditlibnbt.pyx», line 683, in mceditlib.nbt.load_compound

File «srcmceditlibnbt.pyx», line 690, in mceditlib.nbt.load_named

File «srcmceditlibnbt.pyx», line 807, in mceditlib.nbt.load_tag

File «srcmceditlibnbt.pyx», line 683, in mceditlib.nbt.load_compound

File «srcmceditlibnbt.pyx», line 690, in mceditlib.nbt.load_named

File «srcmceditlibnbt.pyx», line 807, in mceditlib.nbt.load_tag

File «srcmceditlibnbt.pyx», line 683, in mceditlib.nbt.load_compound

File «srcmceditlibnbt.pyx», line 689, in mceditlib.nbt.load_named

File «srcmceditlibnbt.pyx», line 733, in mceditlib.nbt.load_name

UnicodeDecodeError: ‘utf8’ codec can’t decode byte 0xc0 in position 0: invalid start byte

64bit Mcedit2 2.0.0-beta7 I have tried another version, I forget which one and gave me the same error! What could this be from? I was able to load a factions world, but not my vanilla or depleted world? Whats the deal with this? I hope I get emails about this because I might forget of my issue…

Thanks!

Click here follow the steps to fix Mcedit Error During Function Confirm At and related errors.

Instructions

Note:
This article was updated on 2023-01-24 and previously published under WIKI_Q210794

What is Mcedit Error During Function Confirm At error?

The Mcedit Error During Function Confirm At error is the Hexadecimal format of the error caused. This is common error code format used by windows and other windows compatible software and driver vendors.

This code is used by the vendor to identify the error caused. This Mcedit Error During Function Confirm At error code has a numeric error number and a technical description. In some cases the error may have more parameters in Mcedit Error During Function Confirm At format .This additional hexadecimal code are the address of the memory locations where the instruction(s) was loaded at the time of the error.

What causes Mcedit Error During Function Confirm At error?

The Mcedit Error During Function Confirm At error may be caused by windows system files damage. The corrupted system files entries can be a real threat to the well being of your computer.

There can be many events which may have resulted in the system files errors. An incomplete installation, an incomplete uninstall, improper deletion of applications or hardware. It can also be caused if your computer is recovered from a virus or adware/spyware
attack or by an improper shutdown of the computer. All the above actives
may result in the deletion or corruption of the entries in the windows
system files. This corrupted system file will lead to the missing and wrongly
linked information and files needed for the proper working of the
application.

How to easily fix Mcedit Error During Function Confirm At error?

There are two (2) ways to fix Mcedit Error During Function Confirm At Error:

Advanced Computer User Solution (manual update):

1) Start your computer and log on as an administrator.

2) Click the Start button then select All Programs, Accessories, System Tools, and then click System Restore.

3) In the new window, select «Restore my computer to an earlier time» option and then click Next.

4) Select the most recent system restore point from the «On this list, click a restore point» list, and then click Next.

5) Click Next on the confirmation window.

6) Restarts the computer when the restoration is finished.

Novice Computer User Solution (completely automated):

1) Download (Mcedit Error During Function Confirm At) repair utility.

2) Install program and click Scan button.

3) Click the Fix Errors button when scan is completed.

4) Restart your computer.

How does it work?

This tool will scan and diagnose, then repairs, your PC with patent
pending technology that fix your windows operating system registry
structure.
basic features: (repairs system freezing and rebooting issues , start-up customization , browser helper object management , program removal management , live updates , windows structure repair.)

Here you will find some information for troubleshooting information. These examples were mostly taken form the issue tracker.

There is not much here yet, but feel free to expand it!

Crashes

First, you should try development builds. Those are less stable, but they sometimes fix known crash errors. This was the case in Issue #193 and #198

Mac OSX

Missing X server

MCEdit is an X application. As such it needs an X server to function properly. Apple has its own version called XQuartz (AKA X11.app). This one is taken form Issue #192.

Other (running from source, typically Linux)

Missing pymclevel

When you run MCEdit from the source, you must get pymclevel too (in the git, it is a submodule). If you were following the instructions in README.md, you should not have this problem. However, if you have blindly cloned the repository, then you will have to run

git submodule init
git submodule update

This was the case in Issue 167

Wrong python version

MCEdit only works with Python 2.7. If you have any other version, it will fail. You should probably get Python 2.7 and run MCEdit as python2.7 mcedit.py
This was the case in Issue #168

Glitches

Windows, panels, interface items not showing up

This is a known issue. The interfaces are still usable, and this is a purely graphical glitch. Updating your graphics driver may (Issue #169), or may not (#191) solve your problem.

Common pitfalls

Clone, Fill & Replace and Filter buttons disabled

You have probably not selected an area, or maybe you have used the chunk tool instead of the select tool. If you want to operate on whole chunks, use the select chunks button in the panel of the select tool.
This was the case in Issue #196

Reporting an issue

If you haven’t found the solution for your problem here, you should report an issue. Before doing so, please read the related article (Reporting Issues) and search in the issue tracker to make sure not to make a duplicate. Thank you!