Confirmed pocket bug list

[Khroki]

Downloaded the Windows 10 edition of Minecraft, and here are the bugs I have confirmed. This thread is so we can see what all needs to be done. If you have another bug please open a new issue, I'll add it to here once confirmed.

• Light handling issue causing darkness near edited areas. Tall grass in dark areas reporting different values than in unaffected areas. Does not always occur directly over edits. Torches light up areas, but removing them restores the darkness, underground lava not affected so almost certainly a bug with how we handle sky lighting in pocket.
• Seed, world name, and some world variables such as always day being lost on save
• Chest editor does not support pocket at this time, new items are in string format which can cause corruption if saved to a pocket chest. Editing existing items should be safe.
• NBT too short error on save on certain worlds (asked for 4 only got 0)
• Missing some blocks
• Player handling does not properly support pocket; sometimes resets positions and the player menu does not handle pocket formatted ids correctly.
• No dimension support
• Waypoint system disabled when loaded into a pocket world.
• Piston head entities not being saved properly

I have heard about MCEdit supposedly not loading some chunks, but I haven't been able to reproduce even with some large worlds, if someone could provide a world with this bug and tell me where chunks are missing (a screenshot), that would help.

[LaChal]

I agree with @neonerz .

Please, open a new issue(s) here to talk about subjects which are not MCEdit PE known bugs. A good idea may be to transfer the messages not related to this thread to new one(s), even by copying/pasting. (This will let me do a sort of clean-up of this thread.)

BTW, I could not test yet the filter you created, neonerz, but I look at, and I guess the logic is good. It needs some enhancement, but, anyway nice stuff :smile:

[neonerz]

yea, sorry about that @LaChal. A bit later I'll go through and delete the non-relevant posts and move posts related to actual bugs (not mentioned in the OP post) into a new issue.

edit // removed most of my off topic posts

[ghost]

@LaChal Please send me your LevelDB-MCPE.dll for 1.0+ worlds. It doesn’t compile for me. No z.lib. I am Win10 x64

[LaChal]

@NFGamerMC The .dll is already in this repository (in the pymclevel folder). Personally, I don't compile it. I'm running on a non Windows OS.

To compile it on Windows, you'll have to install Visual Studio, and the Windwos SDKs on you system, then get the sources from there: https://github.com/jocopa3/leveldb-mcpe. Pay attention to the zlib @ 4a090ad. It's the link to Zlib sources. You'll need them to compile.

[ghost]

Thanks, also @LaChal How do I run MCEDIT from this repo on Windows?

[LaChal]

You'll need to install Python 2.7 and the dependencies as stated in the readme. Just adapt the command for Windows :)

[neonerz]

I'm not sure if you are aware @LaChal there seems to be an issue in windows. I'm not sure if it's the DLL that's packaged with it or something else, but if you save a world in windows, it clears the seed and resets the world name (among other things)

[LaChal]

Right, it has been reported in #801.

I tried to compile it on my side, but no chance (yet).

All right. I could finally compile something for 64 bit systems (using VS 2017 community edition): LevelDB-MCPE.dll.zip

Editing a PE 1.1 world: Loaded, saved unmodified, closed, reloaded: level name and seed unchanged. Loaded, saved modified (added a sign), closed, reloaded: level name and seed unchanged. Closed MCEdit and reloaded the modified world: level name and seed unchanged.

All the same with PE 1.0 worlds.

These tests has been done in MCEdit.

[neonerz]

I just tested using commit b735277 (the latest commit from @Podshot is spitting a TON of errors to the console, though works otherwise) and your DLL. I'm still having the issue.

Inside MCEdit it looks fine, but when I load the world in PE, Minecraft reports it with no name, seed 0, game mode reverted back to survival, and world type reverts back to Infinite.

Here's an example world I simply opened, and saved. In MCEdit "World Info" looks right, but if you open it in MCPE, it's different. brewing-stand.zip

[Podshot]

@neonerz Yeah, I completely broke some parts of the code, could you give me pastes of the errors to make sure I fix all of them?

[neonerz]

@Podshot I went to reproduce the errors I was seeing, but it seems you must have fixed it in the 6/30 commits. I'm not getting the console spam anymore.

[neonerz]

@LaChal - I found a slight work around for the Windows issue. If you do all your work in Windows, save the world, then open it back up in Linux, and save it again. When you open the world in MCPE, the world info reflects the correct info.

With that in mind, it seems like Windows can't save to level.dat in the new format, and is only saving to level.dat_old (I assume this because if I use a NBT editor on level.dat_old on a world I edited in Windows, I actually see the changes).

[LaChal]

Hmmm...

No error in the console? No mention of corrupted, unreadable or unwritable level.dat in the log file?

[neonerz]

Nothing in either. Here's a mcedit.log of me opening a PE world in windows, changing the name, and then saving it. mcedit.log.txt

Also, here's a gif demonstrating it.

[LaChal]

Hmmm...

MCEdit explicitely writes to level.dat, on any platform. level.dat_old will be loaded if level.dat is corrupted...

After some investigation on your 'brewing-stand', it looks like it's the same issue than the #810 one. The byte sequence '0a0d' is the Windows line ending/start. I guess something is replacing every '0a' byte with '0a0d' pair...

@neonerz It shall be fixed now.