[MC-315] Chunks do not delete properly remaining in a newly created world if the same world name is reused Created: 25/Oct/12  Updated: 14/Aug/20  Resolved: 02/Jul/20

Status: Resolved
Project: Minecraft: Java Edition
Component/s: None
Affects Version/s: Minecraft 1.4.1, Minecraft 1.4.4, Minecraft 1.4.6, Minecraft 1.4.7, Snapshot 13w05b, Snapshot 13w07a, Snapshot 13w09a, Snapshot 13w09b, Snapshot 13w09c, Snapshot 13w10b, Minecraft 1.5, Snapshot 13w11a, Minecraft 1.5.1, Snapshot 13w16b, Minecraft 1.5.2, Snapshot 13w17a, Snapshot 13w22a, Snapshot 13w24a, Snapshot 13w24b, Snapshot 13w25a, Snapshot 13w25b, Snapshot 13w25c, Minecraft 1.6.1, Minecraft 1.6.2, Minecraft 13w36b, Minecraft 13w37a, Minecraft 13w39b, Minecraft 1.7.1, Minecraft 1.7.2, Minecraft 1.7.3, Minecraft 1.7.4, Minecraft 14w02c, Minecraft 14w03b, Minecraft 14w04a, Minecraft 14w04b, Minecraft 14w05a, Minecraft 14w05b, Minecraft 14w06b, Minecraft 14w07a, Minecraft 14w08a, Minecraft 1.7.5, Minecraft 14w11b, Minecraft 1.7.8, Minecraft 1.7.9, Minecraft 14w18b, Minecraft 14w19a, Minecraft 14w29b, Minecraft 14w30c, Minecraft 1.8, Minecraft 1.8.1-pre3, Minecraft 1.8.3, Minecraft 1.8.8, Minecraft 15w33a, Minecraft 15w33b, Minecraft 15w35b, Minecraft 1.8.9, Minecraft 1.9 Pre-Release 4, Minecraft 1.9, Minecraft 1.10.2, Minecraft 16w38a, Minecraft 16w40a, Minecraft 1.11, Minecraft 16w50a, Minecraft 1.11.2, Minecraft 1.12.2, Minecraft 18w11a, Minecraft 18w16a, Minecraft 18w19b, Minecraft 18w20c, Minecraft 18w21b, Minecraft 18w22b, Minecraft 18w22c, Minecraft 1.13-pre1, Minecraft 1.13-pre2, Minecraft 1.13-pre3, Minecraft 1.13-pre4, Minecraft 1.13-pre5, Minecraft 1.13-pre6, Minecraft 1.13, Minecraft 18w30a, Minecraft 18w30b, Minecraft 1.13.1-pre1, Minecraft 1.13.1, Minecraft 1.13.2-pre1, Minecraft 1.13.2, Minecraft 18w43a, Minecraft 18w43b, Minecraft 18w43c, Minecraft 19w07a, Minecraft 19w08b, Minecraft 19w12b, Minecraft 19w13a, Minecraft 1.14 Pre-Release 2, Minecraft 1.14 Pre-Release 3, Minecraft 1.14 Pre-Release 4, Minecraft 1.14 Pre-Release 5, Minecraft 1.14.2, Minecraft 1.14.3 Pre-Release 3, 1.14.4, 19w40a, 1.15.2, 20w08a, 20w10a
Fix Version/s: Minecraft 13w38a

Type: Bug
Reporter: Greg Milson Assignee: Unassigned
Resolution: Cannot Reproduce Votes: 92
Labels: chunk, mojang_internal_1, rendering, superflat-world, world-generation, world-name

Attachments: PNG File 2012-10-19_15.00.05.png     PNG File 2012-10-19_15.00.20.png     PNG File 2012-10-19_15.00.37.png     PNG File 2012-10-19_15.01.29.png     PNG File 2012-10-19_15.01.41.png     PNG File 2013-06-23_12.50.21.png     PNG File 2014-06-13_18.08.57.png     PNG File 2016-02-03_20.27.56.png     PNG File 2018-10-22_19.04.22.png     PNG File 2018-10-22_19.05.19.png     PNG File farlands.png     Text File latest.log    
Issue Links:
Duplicate
is duplicated by MC-6714 random areas un flat areas in the set... Resolved
is duplicated by MC-7216 'Cut-off'ed World Generation Resolved
is duplicated by MC-7327 Chunk error where ocean chunks spawn ... Resolved
is duplicated by MC-8033 Normal world chunks in SuperFlat worlds Resolved
is duplicated by MC-8935 Creating a superflat world is glitchy Resolved
is duplicated by MC-9222 World Generation Resolved
is duplicated by MC-9270 Minecraft world generating system broken Resolved
is duplicated by MC-9398 Minecraft:Got more lagger! and more b... Resolved
is duplicated by MC-9758 Strange Extreme Hills Generation in 1... Resolved
is duplicated by MC-9893 I thought this was superflat! Resolved
is duplicated by MC-10550 FlatGrass loads both flat and normal Resolved
is duplicated by MC-10660 Odd world generation Resolved
is duplicated by MC-10861 This is not your average world genera... Resolved
is duplicated by MC-10909 half houses Resolved
is duplicated by MC-11074 Superflat and Default world merging! Resolved
is duplicated by MC-11724 Ice Plains biome spawned in my super ... Resolved
is duplicated by MC-12141 Epic Land Corruption Resolved
is duplicated by MC-12302 Random chunks in a particular area ar... Resolved
is duplicated by MC-12605 Superflat giant stone tower Resolved
is duplicated by MC-13160 Superflat chunks appearing in Normal ... Resolved
is duplicated by MC-13242 Parts of Super-Flat World Not Flat Resolved
is duplicated by MC-13558 Missing chunks Resolved
is duplicated by MC-14110 random chunk generation Resolved
is duplicated by MC-14641 Strange terrain generation in 13w17a Resolved
is duplicated by MC-14643 Land generation errors Resolved
is duplicated by MC-14651 Strange terrain bug - Random desert c... Resolved
is duplicated by MC-14723 I have found generation bug in the la... Resolved
is duplicated by MC-15294 Random Castle Generation Resolved
is duplicated by MC-15905 Biome Intergration Resolved
is duplicated by MC-16536 Flat World Chunk Loading Bug Resolved
is duplicated by MC-16550 Normal world parts in superflat Resolved
is duplicated by MC-16598 Superflat terrain glitch Resolved
is duplicated by MC-16768 Major Chunk Errors Resolved
is duplicated by MC-16936 Chunks from default world loading in ... Resolved
is duplicated by MC-17002 Random chinks of differnt terrain are... Resolved
is duplicated by MC-17218 I found a random "block of land" in s... Resolved
is duplicated by MC-17275 Random chunk generated in middle of o... Resolved
is duplicated by MC-17331 Chunk of world in superflat Resolved
is duplicated by MC-17404 Minecraft world re-create Resolved
is duplicated by MC-17475 World-Generator generate strange stru... Resolved
is duplicated by MC-17572 antvenom seed generation error Resolved
is duplicated by MC-17989 Chunk generator generates random biom... Resolved
is duplicated by MC-19109 Buggy Chunk Loading in 1.6 Pre-Release Resolved
is duplicated by MC-19196 Biomes are spawning in random chunks Resolved
is duplicated by MC-19686 World generation bug Resolved
is duplicated by MC-21439 Flatland Glitch Resolved
is duplicated by MC-21632 Superflat error. Resolved
is duplicated by MC-21753 World generation buggy!! Resolved
is duplicated by MC-22292 Worl generation Error - Unmatching ch... Resolved
is duplicated by MC-22493 Missing Chunks Resolved
is duplicated by MC-22718 Weird World Generation Bug Resolved
is duplicated by MC-22795 Problems with terrain generator and m... Resolved
is duplicated by MC-24523 Strange chunk rendering in 1.6.2 sing... Resolved
is duplicated by MC-24615 World generation issue Resolved
is duplicated by MC-25946 Terrain Drops with a straight border ... Resolved
is duplicated by MC-26832 Complete world recreation in hardcore Resolved
is duplicated by MC-26907 Strange world bug Resolved
is duplicated by MC-27422 2 bugs spawn point and weird earth cu... Resolved
is duplicated by MC-28265 Chunk Error in SuperFlat Resolved
is duplicated by MC-28358 Really Funny And Strange CHUCNK ERROR Resolved
is duplicated by MC-28934 Odd generation error Resolved
is duplicated by MC-29121 um... WAT?! Resolved
is duplicated by MC-29470 Chunk Loading Errors Resolved
is duplicated by MC-29524 Lots of chunck errors up with the 1.... Resolved
is duplicated by MC-30521 Amplified world option stops... ampli... Resolved
is duplicated by MC-30599 Odd box like sections of map raised i... Resolved
is duplicated by MC-30657 World generation total failure Resolved
is duplicated by MC-30715 World generation errors Resolved
is duplicated by MC-30717 Inappropriate biomes formation and ad... Resolved
is duplicated by MC-30809 Rerrain generation Resolved
is duplicated by MC-30970 Large biomes, biomes not mixing. Resolved
is duplicated by MC-31052 Multiple bonus chests appear Resolved
is duplicated by MC-31200 The Generator For Superflat Didnt work Resolved
is duplicated by MC-31954 Chunk Generating Error Resolved
is duplicated by MC-32066 Chunk generation error Resolved
is duplicated by MC-32340 Default chunks loading in superflat w... Resolved
is duplicated by MC-33042 Chunk Errors generating Resolved
is duplicated by MC-33076 Generation of the world. Resolved
is duplicated by MC-33431 World Generation Glitch Resolved
is duplicated by MC-33858 world creation bug Resolved
is duplicated by MC-34303 Square Oceans/Chunk Generation Errors Resolved
is duplicated by MC-36196 Flat world and Normal World Generatin... Resolved
is duplicated by MC-36409 when I create a superflat world the s... Resolved
is duplicated by MC-36585 misplaced chunks while loading the world Resolved
is duplicated by MC-36770 Map displays normal world on superflat. Resolved
is duplicated by MC-37017 World Generate Resolved
is duplicated by MC-37535 Open Resolved
is duplicated by MC-37656 Cut of land Resolved
is duplicated by MC-38060 Random Raised Chunk Resolved
is duplicated by MC-38724 Chunk errors in 1.7 Resolved
is duplicated by MC-40170 Superflat world is partially normal w... Resolved
is duplicated by MC-40304 when i want villages and flat land it... Resolved
is duplicated by MC-40776 Some chunks end abruptly Resolved
is duplicated by MC-41311 Huge Superflat World Error Resolved
is duplicated by MC-41558 Biomes didn't blend - pure 1.7.2 Resolved
is duplicated by MC-42058 Weird new world after defeating the e... Resolved
is duplicated by MC-42124 Flat walls appear INSIDE NEWLY GENERA... Resolved
is duplicated by MC-42139 World generation Resolved
is duplicated by MC-42285 World deletion fails Resolved
is duplicated by MC-42491 random single chunks of extreme hills... Resolved
is duplicated by MC-42666 Biomes not generating correctly Resolved
is duplicated by MC-44150 MAJOR chunk error Resolved
is duplicated by MC-44184 RANDOM GENERATION OF THE DEEP OCEAN ... Resolved
is duplicated by MC-44221 Superflat Generation Resolved
is duplicated by MC-44275 Chunk Errors Resolved
is duplicated by MC-45435 Mundo mal generado - Bad generated world Resolved
is duplicated by MC-45693 What? Resolved
is duplicated by MC-46173 Error generate chunks in superflat world Resolved
is duplicated by MC-46189 Bonus chest break superflat Resolved
is duplicated by MC-46483 Major Chunk Errors Resolved
is duplicated by MC-46849 world dissapiers make a new world wit... Resolved
is duplicated by MC-47187 Huge Chunk Error Resolved
is duplicated by MC-47309 Bad world gen with a random seed (14w... Resolved
is duplicated by MC-47334 Preset bug Resolved
is duplicated by MC-47384 Flatland Bug Resolved
is duplicated by MC-48473 Bug generation chunk Resolved
is duplicated by MC-48803 When I go and make new world delete b... Resolved
is duplicated by MC-48873 Glitched SuperFlat World Generation Resolved
is duplicated by MC-48887 BAD superflat biomes glitch Resolved
is duplicated by MC-49192 Abnromal terrain generation after cre... Resolved
is duplicated by MC-49887 Deleting a world while it is still 'g... Resolved
is duplicated by MC-50796 world gen messed up Resolved
is duplicated by MC-51102 Server Lagg on Singleplayer Resolved
is duplicated by MC-51287 Custom Superflat World Generator Error Resolved
is duplicated by MC-51635 I have encountered a chunk loading bug. Resolved
is duplicated by MC-51959 Chunk Loading Error Resolved
is duplicated by MC-52275 Incorrect Chunk Resolved
is duplicated by MC-52596 classic superflat preset starts loadi... Resolved
is duplicated by MC-52686 seed bug Resolved
is duplicated by MC-52708 Minecraft terrain makes superflat wor... Resolved
is duplicated by MC-52865 Flatworld Generation Bug Resolved
is duplicated by MC-53047 New world generation bug Resolved
is duplicated by MC-53057 Major world generation bug in super f... Resolved
is duplicated by MC-53137 Odd world generation Resolved
is duplicated by MC-53531 (Custom Worlds) Chunk Generation Resolved
is duplicated by MC-54540 14w18b customized world terrain errors Resolved
is duplicated by MC-54816 Chunck generating error Redstone Read... Resolved
is duplicated by MC-54866 Superflat worlds still generate a non... Resolved
is duplicated by MC-54876 Superflat Worlds Are Broken Resolved
is duplicated by MC-54976 I came back to my normal superflat, a... Resolved
is duplicated by MC-55132 Generation error with grass on Superf... Resolved
is duplicated by MC-55387 Trees leaves not spawning on one side... Resolved
is duplicated by MC-55804 Extreme Hills (Corruption?) Chunk Resolved
is duplicated by MC-56242 World doesn't generate properly in so... Resolved
is duplicated by MC-56774 I was playing minecraft PC, and these... Resolved
is duplicated by MC-57349 Chunck generating can fail if moving ... Resolved
is duplicated by MC-57722 Same Name Old Copy Resolved
is duplicated by MC-57768 World not generating correctly Resolved
is duplicated by MC-59271 Debug mode mis generation Resolved
is duplicated by MC-59297 Biomes No Longer Blend Properly Into ... Resolved
is duplicated by MC-59443 Chunk Generation on a "Redstone Ready... Resolved
is duplicated by MC-59739 Superflat bug? Resolved
is duplicated by MC-59794 huge bug Resolved
is duplicated by MC-59863 Newly spawned worlds in 14w27a have s... Resolved
is duplicated by MC-60630 Weird custom Biome layouts Resolved
is duplicated by MC-60805 Chunk loading error Resolved
is duplicated by MC-61102 Chunk errors in new world (bad altitude) Resolved
is duplicated by MC-61514 Lava Chunks Resolved
is duplicated by MC-61705 Unnatural Chunk Loading Resolved
is duplicated by MC-61874 Superflat still generates regular chu... Resolved
is duplicated by MC-61952 Customized worlds sometimes generate ... Resolved
is duplicated by MC-62544 World Generation Issue 19w29b Resolved
is duplicated by MC-62627 AMPLIFIED terrain generating in Defau... Resolved
is duplicated by MC-62884 Superflat Generation Error Resolved
is duplicated by MC-62959 The World Regeneration Is glitchy Resolved
is duplicated by MC-63338 Deep ocean Biome cut off Resolved
is duplicated by MC-63658 Chunks loaded incorrectly Resolved
is duplicated by MC-63839 Terrain Generation bugs Resolved
is duplicated by MC-63863 Terrain generation bug (forest + plai... Resolved
is duplicated by MC-63864 Unlit blocks bug Resolved
is duplicated by MC-64092 Bug creating the world Resolved
is duplicated by MC-64104 World terrain becomes weird Resolved
is duplicated by MC-64112 Failed terrain generation Resolved
is duplicated by MC-64228 Deleting save impossible Resolved
is duplicated by MC-64388 Creating a world with the same name a... Resolved
is duplicated by MC-64636 Flatworld chunks generating normal wo... Resolved
is duplicated by MC-64657 Strange generation and transfer betwe... Resolved
is duplicated by MC-65758 Worlds created with same name clash t... Resolved
is duplicated by MC-66266 Water Skyscraper world chunks? Resolved
is duplicated by MC-66385 Chunk of old world erred Resolved
is duplicated by MC-67366 Generating Fail Resolved
is duplicated by MC-67747 New creative world replaced by survival? Resolved
is duplicated by MC-68224 Giant hole Resolved
is duplicated by MC-69533 Huge World Generation Gliches with se... Resolved
is duplicated by MC-71302 Chunks appear to be scrambled Resolved
is duplicated by MC-71322 Bug in minecraft Resolved
is duplicated by MC-72261 New map glitch Resolved
is duplicated by MC-72853 Hole generated in a new world Resolved
is duplicated by MC-73506 Biome/chunk glitch Resolved
is duplicated by MC-73862 There are sharp wall edges on a minec... Resolved
is duplicated by MC-74412 World Mixtures Resolved
is duplicated by MC-75047 whole parts of worls have dissapeared... Resolved
is duplicated by MC-75141 Map Generating Glitch Resolved
is duplicated by MC-75509 Swapping Chunks Resolved
is duplicated by MC-76052 Chunks switching biome generation in ... Resolved
is duplicated by MC-76505 Deep Ocean Customized World Generatio... Resolved
is duplicated by MC-77268 1.8.1 "Chunk Glitch" in a single-play... Resolved
is duplicated by MC-78282 World generation glitch? Normal world... Resolved
is duplicated by MC-79179 Chunks raised from the ground Resolved
is duplicated by MC-80653 Superflat world with a piece of norma... Resolved
is duplicated by MC-80654 normal chunks genning on super flat Resolved
is duplicated by MC-80849 bad creation world Resolved
is duplicated by MC-87332 Flatland not generating corectly Resolved
is duplicated by MC-89075 The Void Make Some Lands Far Away Resolved
is duplicated by MC-91356 Village Bug Resolved
is duplicated by MC-91839 error in map's generation Resolved
is duplicated by MC-92876 Normal world gen in a superflat world Resolved
is duplicated by MC-94291 Chunk Glitch Resolved
is duplicated by MC-94668 Chunks Being Weird (Not The Normal Ch... Resolved
is duplicated by MC-95062 World was set to FLAT LAND and all of... Resolved
is duplicated by MC-96152 I'm very concerned about what has hap... Resolved
is duplicated by MC-97210 World granting Resolved
is duplicated by MC-98215 World Generator Bug Resolved
is duplicated by MC-98277 Worlds are sometimes created with dis... Resolved
is duplicated by MC-99996 Biome Wall Resolved
is duplicated by MC-102089 Bad Generation Resolved
is duplicated by MC-102105 Chunk bug Resolved
is duplicated by MC-104825 Random Mountain Spawning Resolved
is duplicated by MC-105222 Chunk Improperly Loaded, Filled with ... Resolved
is duplicated by MC-105341 I logged in to my new server and I st... Resolved
is duplicated by MC-106255 bug chunk Resolved
is duplicated by MC-106606 Giant Dirt Pillars in Superflat world?! Resolved
is duplicated by MC-107335 wrong chunks Resolved
is duplicated by MC-107873 Chunk error Resolved
is duplicated by MC-109416 World chunks are glitching... Resolved
is duplicated by MC-111457 RANDOM OCEAN LIKE GLITCH WITHIN SNAPS... Resolved
is duplicated by MC-113219 Pls fix asap Resolved
is duplicated by MC-114788 Incorrectly generated chunks Resolved
is duplicated by MC-118869 Weird Terrain Bug When Doing This Resolved
is duplicated by MC-123245 WORLD GENERATING BUG! Resolved
is duplicated by MC-124393 Minecraft Glitch --------------------... Resolved
is duplicated by MC-124648 PODX world glitch Resolved
is duplicated by MC-125602 World generation problem Resolved
is duplicated by MC-126047 Various glitches when creating a void... Resolved
is duplicated by MC-126826 Really weird chunk errors Resolved
is duplicated by MC-127497 terrain generation error Resolved
is duplicated by MC-127523 Erronous Chunk Resolved
is duplicated by MC-128322 Terrain generation issue Resolved
is duplicated by MC-128705 Random chunks from a deleted world us... Resolved
is duplicated by MC-129043 weird block changes Resolved
is duplicated by MC-129102 Harcore Mode Seems to be Broken in Sn... Resolved
is duplicated by MC-129530 World Buffet bug Resolved
is duplicated by MC-129602 Seemingly random world generation cra... Resolved
is duplicated by MC-129982 Chunks being generated in the wrong p... Resolved
is duplicated by MC-132914 Chunk Errors happen in worlds created... Resolved
is duplicated by MC-132964 Weird world generation Resolved
is duplicated by MC-135891 super flat worl link to unflat Resolved
is duplicated by MC-136203 Terrain generation bug in flat world Resolved
is duplicated by MC-136906 Creating a world that isn't super fla... Resolved
is duplicated by MC-137684 Incorrect chunk generation Resolved
is duplicated by MC-137703 generation chunk bug Resolved
is duplicated by MC-137735 World generations Hard lines between ... Resolved
is duplicated by MC-137807 Odd Terrain/Chunk Generation Resolved
is duplicated by MC-137811 Buffet worlds generate multiple biomes Resolved
is duplicated by MC-138076 Farlands Resolved
is duplicated by MC-138542 Chunks bugs Resolved
is duplicated by MC-138826 IN my super flat world there was chun... Resolved
is duplicated by MC-142542 Superflat world generation gone weird... Resolved
is duplicated by MC-143253 World Generating issues Resolved
is duplicated by MC-143316 "Default" world chunks generates in "... Resolved
is duplicated by MC-143991 Strange Chunk Generation Resolved
is duplicated by MC-144431 Hardcore death, created NEW WORLD an... Resolved
is duplicated by MC-144742 creating an amplified world corrupts ... Resolved
is duplicated by MC-146772 Flat world generation bug Resolved
is duplicated by MC-152189 Worlds dissapearing but still in file... Resolved
is duplicated by MC-190338 Chunk error while loading a Superflat... Resolved
is duplicated by MC-204 Error - Superflat Resolved
is duplicated by MC-227 Some random terrain was made on a new... Resolved
is duplicated by MC-353 failed chunck Resolved
is duplicated by MC-639 World copy paste? Resolved
is duplicated by MC-699 World generation Resolved
is duplicated by MC-762 Hardcore World Not Completely Deleted Resolved
is duplicated by MC-1091 World generatig bug Resolved
is duplicated by MC-1152 Beta terrain generation in a superfla... Resolved
is duplicated by MC-1154 random elevated and depressed chunks ... Resolved
is duplicated by MC-1234 Chopped Mountains Resolved
is duplicated by MC-1376 biome bug Resolved
is duplicated by MC-1395 An Ocean biome chunk cutting into oth... Resolved
is duplicated by MC-2278 Worlds are not fully removed when del... Resolved
is duplicated by MC-2721 Just named worlds can be mixed into each Resolved
is duplicated by MC-2735 Chunk regeneration Resolved
is duplicated by MC-2822 Map bug Resolved
is duplicated by MC-2856 Hills/lakes/rivers are cutted off by ... Resolved
is duplicated by MC-3218 Strange Chunk Placement Resolved
is duplicated by MC-4521 Chunks of Redstone Ready is mixed Resolved
is duplicated by MC-5001 1.4.6 Prerelease World Gen Error Resolved
is duplicated by MC-5039 Superflat Generating Issues Resolved
Relates
relates to MC-526 Worlds will not delete Resolved
relates to MC-2548 A chunk with previously generated dat... Resolved
CHK:
Confirmation Status: Confirmed
Category:
Chunk loading
Mojang Priority: Normal

 Description   

The bug

I made a superflat world when i noticed a huge structure in the fog. So i closed up on it and it was a chunk from the default world.

How to reproduce

It seems to be kinda random and very rare but I've been able to do it only 4 times

  1. Make a superflat world(default)
  2. Travel around a bit and if you're lucky you'll find one. (I once even spawned in one)


 Comments   
Comment by [Mod] violine1101 [ 03/Jul/20 ]

Policies can change.

If we just pick any random version as fix version, it's a false statement as well. Nevertheless, this is not the place to discuss that.

Comment by Fabian Röling [ 03/Jul/20 ]

It has always been the normal thing to just pick any reasonable version then. "Cannot reproduce" is simply false. It also suggests that people are supposed to try to reproduce it, which would just waste time in this case.

Comment by [Mod] CubeTheThird [ 02/Jul/20 ]

If you are able to provide the game version upon which this was fixed, I can try to update accordingly.

Comment by Markku [ 02/Jul/20 ]

I would think the correct resolution is "fixed", since it was reproduced plenty of times before. "Cannot reproduce" resolution (at least in the meaning I've seen it used usually) basically would mean the issue could not be confirmed by testing at any point (thus not valid issue) , which obviously isn't the case here.  Yeah, yeah, I'm nitpicking, while happy it has been fixed. Finally.

Comment by Numeritos [ 02/Jul/20 ]

Unable to reproduce in 1.16.1 and 20w27a

Video: https://youtu.be/LMtDccVBYfo

Comment by Markku [ 24/Jun/20 ]

I can confirm the fix. Game now detects existing folders (that do not have complete saved world), and add a counter ( (1), (2), ...) in the end of the directory name when creating a new world with the same old name.

Funny detail: if naming the new world like "name (1)" (i.e. includes the counter in the name) and there is already such directory, game will add another counter, saving to "name (1) (1)".

Even if the bug isn't fixed, per se, as the garbage save data is still left there, the solution fulfills the overall goal of not getting wrong chunks in a new world. I thus consider this issue as good as fixed.

Comment by Numeritos [ 24/Jun/20 ]

Unable to reproduce with the steps @bugi74 has provided, Minecraft always creates a (1) folder instead of using the older with the old files, tested on 1.16

Comment by Markku [ 15/Feb/20 ]

Do read the comments; the reproduction is not deterministic if using only Minecraft (one would need really tight timing and luck), and the reproduction steps in the description are woefully inadequate.

From my memory, from years back, so might not work as is, but... a better process could be:

  1. create world with specific name
  2. exit game
  3. delete certain world save files (enough to make the game think the world is not there), but leave some chunk data files. This manual step simulates effects of world deletion being incomplete (for reason or other, e.g. MC-526).
  4. start game again
  5. create a new world (random or explicitly different seed) with that same specific name
  6. move around to notice chunk issues

Note also the relate issues MC-526 and its comments.

Comment by [Helper] Misode [ 15/Feb/20 ]

I'm unable to replicate this either with the steps that Nathan provided. gregmilson are you sure this is still happening? If so please edit the description and specifically the steps to reproduce.

Comment by Galaxy_2Alex [ 23/Apr/19 ]

I am unable to reproduce this in any way. Please add the console log, as well as concrete steps on how to reproduce this issue, as the current provided steps are not sufficient.

Comment by Fabian Röling [ 06/Jan/19 ]

Oh, you meant it the other way around. Yes, you're right.

Comment by Fabian Röling [ 06/Jan/19 ]

No, they are exactly the same.

Comment by Nixinova [ 26/Oct/18 ]

Replace superflat with buffet and this happens as well

Comment by PoolloverNathan [ 15/Jul/18 ]

I do not play Java, but it sounds like the instructions are different.
Maybe they are:

  1. Make a normal world and write down what you named it (you need it later)
  2. Delete the world
  3. Quickly create a world with the name you wrote down, but make it Superflat this time
  4. Move around quite a bit and you should find chunks from the normal world
Comment by [Mod] Michael Wobst [ 29/May/18 ]

gregmilson, ticket is yours now

Comment by Greg Milson [ 29/May/18 ]

Affects 18w21b

Comment by Shawn Baird [ 19/Jan/18 ]

So I've seen this happen a decent number of times. I regularly play hardcore and just use New World to get a random seed. I always delete my old hardcore game when I die, but currently that means telling it once when I die, but that doesn't really delete it, so an additional time selecting it from my game list and then deleting it and confirming the deletion.

If the window between my deleting the old world and the new one is too small I'll often see this bug. Is there really a reason that the delete operation can't just block until it is truly deleted?

Comment by Joseph Fowler [ 28/Nov/16 ]

Still present in 1.11

Comment by [Helper] gaspoweredpick [ 12/Oct/16 ]

I was playing survival mode on singleplayer, and i went caving in extreme hills, then i got out and all the sudden i saw a huge tower of extreme hills generated in the plains that wasn't there before. there was no lag or relog, it just appeared.

Comment by [Mod] CubeTheThird [ 30/Aug/16 ]

Please avoid re-editing your comments. Every time you do, an email is sent to those watching this report, which now makes for many emails. I also recommend you set your name to something that isn't blank.

Comment by ouroya [ 30/Aug/16 ]

1.10,
1. create default world 00000
2. re-create it
3. delete level.dat and level.dat_old from files
4. create superflat world Copy of 00000
5. remakes the original, but only the loaded section. around it is superflat
NOTE: this breaks potions

Comment by ouroya [ 30/Aug/16 ]

1.10, creating a superflat world, then deleting and creating a non-superflat world can "force" villages into weird generations.

Comment by CyanEmber [ 29/Aug/16 ]

You can delete the level.dat and level.dat_old of a world folder and recreate a new world under the same name, and then you will get this bug. It's kind of awesome, though, because you can use it to make survival island maps easily. Try making a world using the seed "Flame", with the name "Broken Chunks", exiting, deleting the level.dat and level.dat_old files, and then making the world Flame again, but on a Customized world type where the only biome is Ocean. It's pretty awesome.

Comment by Markku [ 24/Jun/16 ]

MC-63 is sort of similar to MC-526, not to this. At least the way these two issues are split now (and should stay split). MC-526 is about the failure of deleting after doing that delete-action; this is about failing to clean up the possible left-overs when doing create-action. Possible crashes during creating a new world are much easier to handle, even when there might be something to clean up first.

This issue is more important to fix (and easier, too), because it is indeed pretty much impossible to ensure 100% certain deletion (crashes etc.) Put more simply; fix only this easy one and MC-526 (and other causes) will not matter as much (and won't be seen in the game, only in the filesystem), but if only MC-526 is fixed, there will still be issues caused by other reasons (thus not as often).

(There are still ways to handle the MC-63 sort of properly, i.e. either everything gets saved (pure success) or nothing gets saved-and-later-loaded (pure crash), but it gets quite deep in the coding (somewhat common exercise in business critical systems, though), more than suitable to paste here, should someone even get the motivation to try and do such fixes.)

Comment by Fabian Röling [ 24/Jun/16 ]

I think this is similar to MC-63: The game has to do things after each other and the calculation speed is limited. So if it crashes halfway through saving or deleting, that can't be fixed in all instances. In this case it could delete the folder before creating something or forbid saving in an existing folder, but e.g. in MC-63 there has to be one thing before the other: If it saves the inventory first and then the entites, you can make it crash in between and duplicate items. If it does it the other way around, people who have a crash in between can lose items. One of those two will always happen.
In this case: If you don't allow the process javaw.exe to be killed while deleting a world, you could cause other problems if the world deletion goes into an infinite loop for some reason and the program doesn't want to get quit so that the whole computer lags or whatever.
In short: If a program gets closed from the outside (crash, task manager, ...), it's often impossible to prevent some errors.
(And yes, I've understood now how to reproduce.)

Comment by Markku [ 24/Jun/16 ]

Read both this and MC-526 through (comments, too), that should clarify things a little.

You asked for a reliably reproducible test for this issue; putting the files there manually is an easy and reproducible test to check if this issue is fixed or not. (Manually putting the files is like simulating the effect of issue MC-526, which is the typical, but not the only reason for hitting this issue later on.) NOTE: not all the files of an old world, just such a subset that makes the game think the world is not there, yet old wrong chunks gets rendered after new world gets created on top of the remains.

When creating a new world, its files are supposed to go into a very specific (and a new) directory. The directory is not supposed to be there, and if it is, there is supposed to be no files in it. Otherwise the world creation should not be allowed to happen to the name used in the first place. (In fact, one could argue that allowing to name the world in a way that leads to issues is already a bug, but such claim is in the territory that can cause heated discussion among developers about bugs, priorities, right and wrong ways to solve things etc. Lets not continue to there.) But since the world creation is allowed to happen with that name, it is, imho, perfectly fine to assume that if there are any files in the way, they are leftovers of a failed removal, or that they are put there manually by a user, and if a user is putting files in such a place where user's manipulation is not welcome (taking backup needs only copying the whole directory, not individual files inside it), it can be assumed he knows what he is doing and is thus responsible for the fate of those files - the game does not need to account for that kind of messing with its operation.

A really fancy fix for this issue would actually check what kinds of files are there, and only remove the ones that are related to this game, and leave other files as is. I have no idea what other kinds of files users could possibly want to put in there, though... perhaps some sort of README-file or such (though such would likely be needed only when dropping in a full world for playing, and thus world creation is not needed or wanted). But in any case, that kind of fancy change would be way beyond just a bugfix, and belongs to wherever they want the feature requests to be put and forgotten.

Comment by Fabian Röling [ 24/Jun/16 ]

If you put these files in the folder manually, why should they get deleted? I don't see why you should do that except if you want these files there.

Comment by Markku [ 24/Jun/16 ]

Fabian:
Since this issue is about deleting random left-overs before creating new world into existing directory, it is easy to simulate a situation where the previous world deletion has failed: simply backup random files from a test world before deleting it, delete it, create the directory again if necessary, then copy those backed up random files back into that directory. Create a new world with the same name and compare results, i.e. are the wrong files still in the save directory.

For continued testing, simply store the collection of random files and their world-directory into a zip-file and re-plant them over the deleted world and re-create...

(I didn't test the sequence above, making it up from my memory, but it should give the idea close enough.)

The related MC-526 is much more difficult to test, but luckily this is the more important issue to be fixed and can be tested easily. 3.5 years gone now, plenty of duplicates (more than votes in this issue), nearly trivial to fix and an (somewhat bad) example code given... sigh...

Comment by Fabian Röling [ 24/Jun/16 ]

Does anyone have tips how to reproduce this a bit reliably?

Comment by Markku [ 11/May/16 ]

Lawrence G. you could have read some comments before adding yours, it is quite often useful. E.g. the one just two comments before yours. Or the 8th from the start... Basically, the reasons have been known for years, we're just waiting for the fix.

Comment by Alawnely [ 11/May/16 ]

I think I know the bug: When you create a world and delete it, Minecraft may not be able to delete some chunk files so when you create a new world with same world name and directory name (in saves folder), it will load the chunks in the folder of the world in the saves folder.

I suggest Minecraft developers that if you create a world, it will have different directory name in the saves folder (like in Pocket Edition).

Comment by Jonathan Haas [ 30/Mar/16 ]

@Deano: This bug is bad, but it's not awful and it doesn't plague us for 4 years or something like that. There is a very simple workaround: Just don't reuse world names, if you create a new world, use a name you didn't used before (append a digit or whatever). Then you should be fine.

Comment by Markku [ 30/Mar/16 ]

Michael Connel, this issue is quite easily fixable, just see my comment made 3 years ago. Granted it is quite awful piece of code, but it was just an example. (I do not expect mojang to solve the issue with that code, it just proves it can be fixed with code.)

The way how some operating systems/file systems delete files has nothing to do with this issue. It has more to do with how minecraft does the deletion, server vs. client architecture, and in some cases too quick exit. Note well the related issue MC-526.

Comment by Michael Connel [ 30/Mar/16 ]

I'm not sure this is fixable from a developers' standpoint.

The but occurs by deleting a world and making a new one that is named the same thing (as the desc says).

It has to do with the way computers delete things. When a file is deleted, it isn't actually deleted, it's just allowed to be overwritten. So if you create a new world right AFTER deleting one of this same name, it will create the world in the same place on the hard drive, and thus it will pull some chunks from the deleted world.

So that's why it isn't fixable- at least for the developers.

There are workarounds (like 'permanent' deletion), but they are complicated.

Comment by JON [ 28/Mar/16 ]

This is awkward... I thought this was removed...

Comment by Nick Eumo [ 25/Mar/16 ]

Confirmed in 1.9. Either this or a related bug. Random chunks relocated upon reloading an existing world.

Comment by Ari Staggs [ 04/Feb/16 ]

I got a screenshot of it.

Comment by Ari Staggs [ 04/Feb/16 ]

Confirmed in 1.8.9. I generated a new superflat world with the dirt preset changed to 50, so it can be deeper. I teleported to 0 62 0, the center of the world, set my spawn, and started building. However, I soon saw a large structure in the distance, and I realized that it was a chunk. I saw a bunch of them, and it was really scary. I deleted that world. The thing is, I had created a world before this, but I forgot to set it to superflat and creative mode. It was normal and was in survival. I suppose that the chunks didn't unload, causing them to load into the superflat world with the exact same name. There was a lake in one of the chunks, and in the superflat world it didn't flow over the edge, so I suppose the chunks just didn't unload when deleting and recreating the world in superflat.

Comment by Samuel Finch [ 12/Aug/15 ]

I can confirm it for 15w32c

Comment by Marcono1234 [ 16/May/15 ]

gerottinho probably because this report here contained the cause for this bug. It happens sometimes that Mods close older reports because they contained less information

Comment by Gerottinho [ 16/May/15 ]

I love how my report on MC-204 is older than this one but still got closed for the reason "duplicated". I'm actually quite surprised I accessed randomly MC-204 and saw I was the reporter, too.

Comment by KingSupernova [ 24/Oct/14 ]

Confirmed in 1.8.1-pre3

Comment by Noproct [ 30/Aug/14 ]

I have one chunk in my main SSP world, next to my guardian farm in a deep oceanthat does not belong there. It seems that the biome info is overwritten because the chunk is clearly a forrest but every block on it is a deep ocean biome.

Comment by Thomas Bruce [ 27/Jul/14 ]

Confirmed 14w30c

Comment by yarrmateys [ 23/Jul/14 ]

one way to circumvent it until fixed would be to rename the newly created world on creation if previous wasn't deleted completely and its folder/files still exist.

say, you make world called "new world", then delete it (but deletion fails) and make a new one called the same. instead of calling its folder "new world" too and causing the bug, just auto rename it to "new world_1" or involve a date+time, like "new world_20140723151905" to prevent multiple attempts to create the same name.

that way even if the world fails to delete, new one won't be able to overwrite its remains, taking some of its chunks in since it'll go to a different folder.

the remaining one could be scheduled to be deleted on next minecraft launch, and if it still fails then, reschedule for next and keep doing it until successful. one pc reset later the folder will be finally freed and will delete normally.

Comment by Markku [ 22/Jul/14 ]

Blah, Andrew and Bruce, and Sonic:
Read my comments in both this issue and MC-526.

  • Both are fixable, and can be quite easily at least improved so much that we wouldn't get 180 duplicates... (And Searge's comment in MC-62627 in no way claims that these are not fixable, he merely states the reason for that issue to be this bug.)
  • The issue is both failing to delete a world properly at the time of deletion, and failing to delete the remains at the time of creating a new one. (The first is obviously good to have, the latter is a must.)
  • "Don't do that then" is a joke, not a valid solution for these issues. These issues are not user errors, but coding bugs.

There are, in a way, two issues caused by one failure. However, both issues should be fixed as the MC-526's "worlds will not delete" can not be 100% ensured in e.g. crash situations (power outages etc.). The world deletion can be made more robust (I've even provided some suggestions of tested fixes). The lingering worlds can be deleted (100%) properly before taking them into new use (I've even provided some tested, though ugly code fixes).

These issues have now been, and has been for last 1.5 years, only waiting for Mojang dev's to adapt those fixes to their code (or make even better fixes if they want).

Comment by Kumasasa [ 22/Jul/14 ]

@duckofduckness: It's the server still saving the world files while the client tries to delete the files:

[00:19:42] [Server thread/INFO]: Saving chunks for level 'Flatworld6'/Overworld
[00:19:42] [Client thread/INFO]: Deleting level Flatworld6
[00:19:42] [Client thread/INFO]: Attempt 1...
[00:19:42] [Client thread/WARN]: Couldn't delete file C:\Users\User\AppData\Roaming\.minecraft\saves\Flatworld6\region\r.-1.0.mca
[00:19:42] [Client thread/WARN]: Couldn't delete directory C:\Users\User\AppData\Roaming\.minecraft\saves\Flatworld6\region
[00:19:42] [Client thread/WARN]: Unsuccessful in deleting contents.
[00:19:42] [Server thread/INFO]: Saving chunks for level 'Flatworld6'/Nether
[00:19:42] [Server thread/INFO]: Saving chunks for level 'Flatworld6'/The End
[00:19:43] [Client thread/INFO]: Attempt 2...
[00:19:43] [Client thread/WARN]: Couldn't delete file C:\Users\User\AppData\Roaming\.minecraft\saves\Flatworld6\region\r.-1.0.mca
[00:19:43] [Client thread/WARN]: Couldn't delete directory C:\Users\User\AppData\Roaming\.minecraft\saves\Flatworld6\region
[00:19:43] [Client thread/WARN]: Unsuccessful in deleting contents.
[00:19:43] [Client thread/INFO]: Attempt 3...
[00:19:43] [Client thread/WARN]: Couldn't delete file C:\Users\User\AppData\Roaming\.minecraft\saves\Flatworld6\region\r.-1.0.mca
[00:19:43] [Client thread/WARN]: Couldn't delete directory C:\Users\User\AppData\Roaming\.minecraft\saves\Flatworld6\region
[00:19:43] [Client thread/WARN]: Unsuccessful in deleting contents.
[00:19:44] [Client thread/INFO]: Attempt 4...
[00:19:44] [Client thread/WARN]: Couldn't delete file C:\Users\User\AppData\Roaming\.minecraft\saves\Flatworld6\region\r.-1.0.mca
[00:19:44] [Client thread/WARN]: Couldn't delete directory C:\Users\User\AppData\Roaming\.minecraft\saves\Flatworld6\region
[00:19:44] [Client thread/WARN]: Unsuccessful in deleting contents.
[00:19:44] [Client thread/INFO]: Attempt 5...
[00:19:44] [Client thread/WARN]: Couldn't delete file C:\Users\User\AppData\Roaming\.minecraft\saves\Flatworld6\region\r.-1.0.mca
[00:19:44] [Client thread/WARN]: Couldn't delete directory C:\Users\User\AppData\Roaming\.minecraft\saves\Flatworld6\region
[00:19:44] [Client thread/WARN]: Unsuccessful in deleting contents.
[00:19:57] [Server thread/INFO]: Starting integrated minecraft server version 14w29b
Comment by Bruce Preston [ 21/Jul/14 ]

Andrew, look at the log on my comment. The error being reported is:

[20:24:11] [Server thread/ERROR]: Couldn't save chunk; already in use by another instance of Minecraft?

Basically, old chunks from one world can't be overwritten by worldgen in the next.

Blah, I'd accept "Don't do that then" as a bugfix...

Comment by Andrew McCluskey [ 21/Jul/14 ]

So the problem is actually with the world/chunk generation and not old files not being deleted properly?

Comment by Dlawso the Really Lucky Rabbit [ 21/Jul/14 ]

Unfixable. Searge's comment from MC-62627:

Leaving a world, then immediately deleting it and creating a new one with the same name can, in some cases, cause issues with chunk generation.

Comment by claire [ 11/May/14 ]

happened to me 2, but when i first spawned it was nt there.. 2 weeks later its like random walls grew. And now my dirt is retextured to look like its glowing.

Comment by Markku [ 02/Feb/14 ]

Note, the sequence used by Bruce also indicates that MC-526 affects 14w05b (couple more versions than the latest reported). The delete and recreate -sequence, when causing issues, automatically confirms both issues (as both the deletion fails at the time of deletion, and no attempt to clear the old dir is made at the time of creation).

Comment by Bruce Preston [ 02/Feb/14 ]

Confirmed in 14w05b (OSX 10.8.5, log attached).

Just accidentally created a checkerboard of two different worlds due to the deletion of the previous world failing to complete before a new world (with the same name) was created.

I meant to create a new Creative world but created a Survival world by mistake (as "New World"). I quit out to the menu, deleted the Survival world and created a Creative one instead (also "New World"). Creative world has a mixture of chunks from the deleted world and the world that actually goes with the seed given by /seed.

Edit: Actually, this may be an instance of MC-526 instead.

Comment by Kumasasa [ 25/Jan/14 ]

Logfile in https://bugs.mojang.com/browse/MC-526?focusedCommentId=134792&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-134792

Comment by Deleted account [ 24/Jan/14 ]

kumasasa: Can't get it to work right now, I'll try again tomorrow.

Comment by Kumasasa [ 24/Jan/14 ]

Jar_: Please attach the development console when having this issue.

Comment by Deleted account [ 23/Jan/14 ]

This is still an issue in Minecraft version 14w03b.

Comment by Kumasasa [ 08/Oct/13 ]

Markku, you are absolutely right.

Comment by Markku [ 08/Oct/13 ]

Actually, it does justify reopening this issue, but not the related MC-526. This issue is now profiled more about deleting any garbage at the time of taking a possible old folder to be reused - whatever the reason for having that garbage there.

My crude fix shown in a previous comment does just that; even if some ancient stuff is around, they are cleared out first. That action is also necessary even if the deletion process is fixed, as there could still be events which interrupt deletion, like crash or power-down etc. and those can not be avoided or handled at deletion time. They must be handled later, at the time of creating a new world. (A fancy fix might occasionally try to check and cleanup folders that are obviously no longer in use but have some garbage...)

The MC-526 is purely about the deletion itself, when the action is started by the player, but fails to complete (for reasons that can be fixed and avoided). No need to even try to create another world by the same name. This MC-315 is just the most common consequence of the MC-526. But not the only consequence for it, and there are other reasons for MC-315 than having MC-526 first. (Thus, the need to have these separate issues for them.)

Comment by Kumasasa [ 08/Oct/13 ]

MC-34303 does not necessarily justify a reopening of this ticket, if there are still old region files laying around on the harddisk (by this bug in older versions), then creating the world with the old name in 13w39b will of course show this effect too.

Comment by [Mod] CubeTheThird [ 08/Oct/13 ]

Reopening due to MC-34303

Comment by EvilSeph (Warren Loo) [ 19/Sep/13 ]

Potentially fixed this issue. I'm not able to reproduce it so I'm not 100% sure. Please test and let me know, thanks

Comment by Galen Dolkas [ 16/Aug/13 ]

Im having a similar problem with jungle biomes.

Comment by Michael Connel [ 09/Jul/13 ]

Please add that it affects Mac OSX.

Comment by Markku [ 06/Jul/13 ]

@crazyman: those steps (as described) are not always enough, as timing is part of the problem. Better description for reproduction in the comments of the related MC-526. (The crucial thing is to do the step from leave world -> delete world quickly; on my machine (SSD drive etc) I have to even exercise a bit (e.g. to know to move mouse cursor to proper spot even before I can see the button to be pressed) in order to be quick enough.)

Apart from the user error part, Steelcrow's comment was otherwise correct, and was one of the comments that allowed me to find the problem code quicker.

As another note, there are more duplicates than votes for this issue. Sigh.

Comment by crazyman [ 06/Jul/13 ]

@SteelCrow we are not looking for user error.
Steps to reproduce:
1. Make a world
2. Leave world
3. Delete world (singleplayer ==> select world ==> press delete world ==> Are you sure? YES)
4. Create new world with exactly same world and directory name.
5. Old chunks remains in new world.
This is not user error, this is error in the game code. I'm waiting that someone from mojang fixes this.
In mean time, let's just cuddle :3

Comment by crazyman [ 06/Jul/13 ]

Confirmed on 1.1 (superflat introduced) - prerelease 1.6.2
this bug ANNOYS ME!

Comment by Brendan Chow [ 24/Jun/13 ]

Confirmed in 13w25c

Comment by Brendan Chow [ 06/Jun/13 ]

it did it to me in 13w22a

Comment by John Distler [ 05/Jun/13 ]

Confirmed in 13w22a

Comment by Thomas Pye [ 26/May/13 ]

I got this with an extreme hills (which for some reason had jungle trees on it...!?) in 1.5.2

Comment by AgentM [ 17/May/13 ]

I had this once but than th other way around with the superflat in the middle and default around it...
looked like 'the end of the flatlands'

Comment by RowanSkie [ 17/Apr/13 ]

Guys, My brother found it he has the one who said me to post it. Sorry!

Comment by Markku [ 17/Feb/13 ]

Crude fix
MCP naming...

Minecraft.launchIntegratedServer()
    ...
    ISaveHandler var4 = this.saveLoader.getSaveLoader(dirName, false);
    WorldInfo var5 = var4.loadWorldInfo();

    if (var5 == null && par3WorldSettings != null) {
        // A new world, ensure deletion of possible old junk and reinitialize var4:
        this.saveLoader.deleteWorldDirectory(dirName);         // ADDED
        var4 = this.saveLoader.getSaveLoader(dirName, false);  // ADDED
            
        this.statFileWriter.readStat(StatList.createWorldStat, 1);
        var5 = new WorldInfo(par3WorldSettings, dirName);
        var4.saveWorldInfo(var5);
    }
    ...

It is kinda bad coding, but I am trying to keep using existing methods. The ugliness comes from that method handling both new and existing worlds, and it needs to init and use both var4 and var5 in order to know if the world is new. But by that time those calls have already created the world directory and a file, which the deletion then immediately remove. Thus it needs to redo the var4 stuff.

The proper fix would be add a new method that specifically checks the existence of world save left-overs and then cleans them up, and use that method from those places which create new worlds (and only create, not open existing ones).

Tested on 1.4.7, works wonders. My messed up results from testing MC-526 and sheep color testing, and even manually "broken" world save directories were all handled correctly. That is, the world creation first wiped the remains of the old directory (confirmed by watching the console and checking that marker files disappeared) before generating the new world with the same directory name.

Comment by yarrmateys [ 06/Feb/13 ]

one way to fix it could be probably to force minecraft to check for any world files/region folder/DIM* folders present when creating a new world, before world generation and delete them before being allowed to generate new ones. in case any files are inaccessible/read only show an error and return to world creation menu.

unless that's already happening and didn't help.

Comment by Anorma [ 26/Jan/13 ]

It is still in 13w04, I can comfirm it.

Comment by Kumasasa [ 13/Jan/13 ]

This issue is a follow up of MC-526

Comment by RowanSkie [ 16/Dec/12 ]

I had it on 1.2.5.

Comment by George Warner [ 03/Nov/12 ]

Ive Seen This Aswell Exept The Biome Was Desert And There Were Jungle Trees and It Was Snowing!!??

Comment by SteelCrow [ 29/Oct/12 ]

Commonly seem when the world name is reused. Old world didn't have time to delete and new one used the same folder name as the old which contained undeleted chunks. We're looking at user error.

Comment by James Dolan [ 25/Oct/12 ]

Have you tried deleting these incorrectly generated chunks via some third-party program such as MCedit. From the results of this test you could determine whether this is a slight flaw with flatland generation or the game neglecting to read the NBT tags of the save before generating these chunks and therefore generating them as it would with a normal world. This also seams to be the same issue as MC-204.

Generated at Sun Jan 12 11:50:37 UTC 2025 using Jira 9.12.2#9120002-sha1:301bf498dd45d800842af0b84230f1bb58606c13.