Jupisoft
- Jupisoft
- jupisoft
- Europe/Stockholm
- Yes
- No
MC-111845![[Mojang] Georgii Gavrichev](../../../data/avatars/users/22428.png){kind=small}
I'm not sure if I should start this new issue since my previous was a bit different, but this time I'm 100 % it happens on vanilla without mods or resource packs.
In my slime farm, I have 3 rails with 4 turns around the corners of a slime chunk, and one of the minecarts suddenly and randomly stops, always in a corner (for now in 3 different corners).
It always takes between 5 or 10 minutes to me to get that error happening.
Also I suspect that in a corner the minecarts might skip it's own track in a corner and end up in another track, but for now I haven't seen that in vanilla yet. But having seen that minecarts also stops without hitting anything in corners, kind of proves also that.
If you need to see my map, please tell me and I'll upload it to mediafire (it's over 100 MB, started in version 1.11 a few days ago, and it's seed it's -2013069384034621868).
Thank you very much for all your attention, and have a nice day
[Seed -488963417782474398 from MC 1_6_4] [Map Ores 2D Overworld] [XZ -1024 to 1023] [MC 1_13].png
![[Mod] redstonehelper](../../../data/avatars/users/10122.svg){kind=small}
@Jupisoft: so this is a 1.6.4-generated world, at least the parts where chunks were deleted?
Hello, I've just discovered this serious bug and since I'm also the creator for some tools for Minecraft 1.13, I can confirm that it occurs as soon as the world is optimized using the new 1.13 function inside the Edit menu, even without loading the world.
I don't really wanna make publicity to myself, but that I know this is the only map generator that almost fully supports 1.13, so if you need a tool to generate a map of the damaged zone, maybe it might help you:
https://www.minecraftforum.net/forums/minecraft-java-edition/recent-updates-and-snapshots/2894808-minecraft-1-13-new-chunk-format-fully-decoded-read
Several dozens of chunks (at least) get fully deleted (even it's biome infos) creating some weird circular pattern which I thought it had to do with the rendering distance, but now I'm sure it's not that. Also I made my map on 1.6.4, then ported it on 1.12.2, but only leaving 4 regions around 0, 0: from -1024, -1024 to 1024, 1024, the rest were deleted on purpose. I had no bug even on 1.12.2. All were fully generated and the proof is the original map made from the 1.12.2 version.
Clearly this is a 1.13 bug, and when the player goes to the deleted chunks, new ones in the 1.13 format appears, and I know that because it generated icebergs on some of them. Even a village appeared on the east side over a jungle, but only in the missing chunks, so the houses were split in half.
Here is a double world download with the original from 1.12.2 and the damaged from 1.13 and several maps to help in the comparison of even underground structures or biomes, also attached:
http://www.mediafire.com/file/891tastibymzayi/Jupisoft_-_Seed_-488963417782474398.zip/file
Please update it as soon as possible or at least warn the rest of users or they might loose their worlds forever. Thanks a lot for your attention and have a nice day.
I cannot attach a crash report because the game was working fine. The bug was on the conversion that changed the places the items had on the chest.
I'm really sorry about that. Then should I delete this ticket, or correct it's information and leave it?
Sorry, I'm kinda new to adding posts here and I get confused very easily. But thanks a lot for all your help!
Ok, thanks a lot for all your help and please forgive me because I'm a noob at posting here although I wanna make it without mistakes. But thanks again and have a nice day!
Yes, at least a chunk that I've looked that on 1.13 is missing has that value on "0" or off, but I've never edited my world with any tool. I created it in 1.6.4 and teleported myself on creative and waited up to 5 minutes to load every zone. It took me 2 days of work and teleporting to generate a map of 2048 x 2048 blocks, but I made sure to teleport even further away of those chunks.
Then I converted the world to 1.12.2 and deleted the regions outside of -1024 or +1024. And there all the chunks were existing without problems. But now are gone and I don't understand why they have that value turned off. And specially if there are lots of chunks further away, and outside of my attached map the explored and loaded terrain was going at least more than 256 blocks away in every direction, so I really don't understand why is happening because I really took my time to be sure all of the chunks were fully loaded when first creating the world.
Also their value TerrainPopulated is 1 or true, so that shouldn't make the game to save those chunks, or if they haven't their light updated, even if they have their terrain built are gonna be deleted anyway, because I understand why was programmed like this, but I believe that at least in this case something is out of place, but I'm not even sure why they have the light turned off if I was on those chunks and they generated correctly on 1.6.4, or maybe there was a bug on that version, because at least the terrain always looked good?
If I change theLightPopulated value on every of those chunks it will work fine in theory and won't be deleted, because it should take several hours to do it, if so is there a quick way of doing it?
Thanks again for your attention.
Then it only should mean that I've had some sort of bug where the values of the chunks changed even before 1.13. Maybe it was when converting the 1.6.4 to 1.12.2, which are the only versions I have used. If possible please look at the attached pictures (the 4 at the bottom, and note how the map continues without any cut, but in reality it kept going even for other 256 blocks on any other direction before that world border of unexplored chunks, so I can't understand it) to see the kind of circular pattern of black squares where the chunks are missing as it might help to spot what happened, since I'm not really sure, only that on 1.12.2 the LightPopulated is false on several chunks, although there they aren't deleted and work fine, which even confuses me more. But thanks in any case for the help.
Hello again, sorry for the delay in my answer. Yes the deleted chunks were generated originally in 1.6.4, then updated to 1.12.2 and finally to 1.13.
I've been updating my tool with 3 new world maps that show the values of LightPopulated, TerrainPopulated and Status (only in 1.13), and it showed the first 2 values in green when it's value is true (1), red when it's false (0) or yellow when it doesn't exist (null). And I can confirm that all the deleted chunks had the LightPopulated set to zero, maybe because at 1.6.4 that value didn't existed yet, and although it was successfully updated to 1.12.2 the existing (but never loaded before, at least on 1.12.2) chunks were shown yellow, so during the update the version 1.12.2 didn't check for existing chunks and also didn't add to them the LightPopulated either on true (1) or false (0).
And that meant that when I played on that world only the chunks that were loaded on 1.12.2 had the LightPopulated added with 1 (or 0 at the world border), working perfectly as you said, but in this case ignoring the other chunks that were existing from 1.6.4 that weren't loaded on 1.12.2, thus creating a world border that deleted chunks between both sides of pre-existing ones.
And also as you said if you simply load the world on 1.12.2 and make sure to load or visit all those pre-existing chunks and save the world, they'll have the LightPopulated set to 1 and will be successfully converted to 1.13 (but the LightPopulated value gets deleted on 1.13 after you load any previous chunk, and I wonder, that should happen?, aside from that it seems to work fine). The only minor problem might be to be sure if one has finished visiting or loading all those pre-existing chunks.
But luckily for all those interested in being sure I've just finished a new update of my "Minecraft Tools" application that now includes full world maps generation and can show which chunks will be missing after the conversion to solve it before it's actually a problem or loss. And don't worry about my program because it only loads the regions and chunks as read-only (it doesn't include any saving or so for now), so it's 100 % sure that no files will be touched or modified (only make sure to have Minecraft closed while loading the world, just to be sure it doesn't interfere with it).
Here is the free link to my latest update, which has full support for 1.13 worlds also
:
http://www.mediafire.com/file/iy5pdair5u0t7na/Jupisoft_-_Minecraft_Tools_EXE_%252828-07-2018%2529.zip/file
Instructions to generate a full world map of the LightPopulated value of all the chunks:
Download the above link, extract the zip file somewhere, start the file "Minecraft Tools.exe" (it doesn't require any installation and it doesn't contain viruses or malware, but feel free to check it out by yourself), then in the started application open the "Tools" menu, select "Realistic world viewer in 2D..." (or press F5), then on the tool window combobox after "3D map" select "Light populated", then right click on the gray background to open the context menu, and at it's bottom click on the "Draw the full world at once..." (or Control + W), and finally in the "Minecraft worlds" combobox select your desired world (or if it's not there drag and drop it's folder on the window, and it also supports modded worlds!). After several minutes (depends on how big is your world), you'll see on it's title bar "Done". After this click "Control + S" or save from it's context menu to export a PNG image with the full chunk map by colors, which will be auto-opened (and saved to "My pictures\Jupisoft\Minecraft Tools\Realistic World Viewer in 2D", or press F4 to open that folder). The red zones in the map will be deleted when converting to 1.13 so be careful if you see any red color. You can also do this without checking the full world on it's menu and by changing the X and Z coordinates navigate through your world and check "little zones" instead of exporting a full map which is slower (but at once you'll see eveything which should be better at least for this problem).
I really hope that this information could be useful to someone else, because it really was to myself. And of course thanks a lot to Georgii Gavrichev and all the other kind people that helped me a lot with this issue
.
I can confirm that on 1.13 by shift-clicking on a stack of rockets of flight duration 3, the one that goes to the enchanting table will loose all it's NBT data and won't be able to stack again with the other rockets. I haven't tested other items yet.