Crashes when populating a chunk with empty (void) columns
Minecraft crashes when populating a chunk which has empty columns ("void columns"), i.e. colums with just air blocks, no bedrock, such as can for instance be generated by creating a Superflat world with preset
2;0;1;decoration
I have attached the crash report. I don't have access to the Minecraft source code, but using the Minecraft Coder Pack for Minecraft 1.7.2 I've traced it to the following code in BiomeDecorator.java (method func_150513_a(BiomeGenBase), lines 160-166):
for(var3 = 0; var3 < this.grassPerChunk; ++var3) { var4 = this.chunk_X + this.randomGenerator.nextInt(16) + 8; var5 = this.chunk_Z + this.randomGenerator.nextInt(16) + 8; var6 = this.randomGenerator.nextInt(this.currentWorld.getHeightValue(var4, var5) * 2); WorldGenerator var10 = p_150513_1_.getRandomWorldGenForGrass(this.randomGenerator); var10.generate(this.currentWorld, this.randomGenerator, var4, var6, var5); }
It takes the height at a particular x,z coordinate and feeds the result (times two) to Random.nextInt(int). Unfortunately that method throws an exception when passed a value of zero.
One way to fix this would be to change those lines to something like:
for(var3 = 0; var3 < this.grassPerChunk; ++var3) { var4 = this.chunk_X + this.randomGenerator.nextInt(16) + 8; var5 = this.chunk_Z + this.randomGenerator.nextInt(16) + 8; int height = this.currentWorld.getHeightValue(var4, var5); if (height > 0) { var6 = this.randomGenerator.nextInt(height * 2); WorldGenerator var10 = p_150513_1_.getRandomWorldGenForGrass(this.randomGenerator); var10.generate(this.currentWorld, this.randomGenerator, var4, var6, var5); } }
The same would have to be done for the other loops in that method.
Environment
Ubuntu 13.04 64-bit
java version "1.7.0_51"
Java(TM) SE Runtime Environment (build 1.7.0_51-b13)
Java HotSpot(TM) 64-Bit Server VM (build 24.51-b03, mixed mode)
Linked Issues
is duplicated by10
MC-52015Game Crashes When Loading Adventure MapDuplicateMC-54341Crashing from chunk pop.DuplicateMC-55761Can't load worldDuplicateMC-56829Random crash at spawn chunksDuplicateMC-58667Server constantly crashing when specific user joinsDuplicateMC-63622More and More CrashesDuplicateMC-64629Crash For No ReasonDuplicateMC-67543Exception Ticking WorldDuplicateMC-69285"n must be positive"DuplicateMC-69472Can't open any SP worldDuplicateAttachments9
Created Issue:
Crashes when populating a chunk with empty (void) columns
Minecraft crashes when populating a chunk which has empty columns ("void columns"), i.e. colums with just air blocks, no bedrock, such as can for instance be generated by WorldPainter (by using a Void border or the Void layer).
I have attached the crash report. I don't have access to the Minecraft source code, but using the Minecraft Coder Pack for Minecraft 1.7.2 I've traced it to the following code in BiomeDecorator.java (method func_150513_a(BiomeGenBase), lines 160-166):
for(var3 = 0; var3 < this.grassPerChunk; ++var3)
{ var4 = this.chunk_X + this.randomGenerator.nextInt(16) + 8; var5 = this.chunk_Z + this.randomGenerator.nextInt(16) + 8; var6 = this.randomGenerator.nextInt(this.currentWorld.getHeightValue(var4, var5) * 2); WorldGenerator var10 = p_150513_1_.getRandomWorldGenForGrass(this.randomGenerator); var10.generate(this.currentWorld, this.randomGenerator, var4, var6, var5); }It takes the height at a particular x,z coordinate and feeds the result (times two) to Random.nextInt(int). Unfortunately that method throws an exception when passed a value of zero.
One way to fix this would be to change those lines to something like:
for(var3 = 0; var3 < this.grassPerChunk; ++var3) {
{ var6 = this.randomGenerator.nextInt(height * 2); WorldGenerator var10 = p_150513_1_.getRandomWorldGenForGrass(this.randomGenerator); var10.generate(this.currentWorld, this.randomGenerator, var4, var6, var5); }
var4 = this.chunk_X + this.randomGenerator.nextInt(16) + 8;
var5 = this.chunk_Z + this.randomGenerator.nextInt(16) + 8;
int height = this.currentWorld.getHeightValue(var4, var5);
if (height > 0)}
The same would have to be done for the other loops in that method.
Environment
Ubuntu 13.04 64-bit
java version "1.7.0_51"
Java(TM) SE Runtime Environment (build 1.7.0_51-b13)
Java HotSpot(TM) 64-Bit Server VM (build 24.51-b03, mixed mode)
Attachments1
Minecraft crashes when populating a chunk which has empty columns ("void columns"), i.e. colums with just air blocks, no bedrock, such as can for instance be generated by WorldPainter (by using a Void border or the Void layer).
I have attached the crash report. I don't have access to the Minecraft source code, but using the Minecraft Coder Pack for Minecraft 1.7.2 I've traced it to the following code in BiomeDecorator.java (method func_150513_a(BiomeGenBase), lines 160-166):
for(var3 = 0; var3 < this.grassPerChunk; ++var3)
{ var4 = this.chunk_X + this.randomGenerator.nextInt(16) + 8; var5 = this.chunk_Z + this.randomGenerator.nextInt(16) + 8; var6 = this.randomGenerator.nextInt(this.currentWorld.getHeightValue(var4, var5) * 2); WorldGenerator var10 = p_150513_1_.getRandomWorldGenForGrass(this.randomGenerator); var10.generate(this.currentWorld, this.randomGenerator, var4, var6, var5); }It takes the height at a particular x,z coordinate and feeds the result (times two) to Random.nextInt(int). Unfortunately that method throws an exception when passed a value of zero.
One way to fix this would be to change those lines to something like:for(var3 = 0; var3 < this.grassPerChunk; ++var3) {
{ var6 = this.randomGenerator.nextInt(height * 2); WorldGenerator var10 = p_150513_1_.getRandomWorldGenForGrass(this.randomGenerator); var10.generate(this.currentWorld, this.randomGenerator, var4, var6, var5); }
var4 = this.chunk_X + this.randomGenerator.nextInt(16) + 8;
var5 = this.chunk_Z + this.randomGenerator.nextInt(16) + 8;
int height = this.currentWorld.getHeightValue(var4, var5);
if (height > 0)}
The same would have to be done for the other loops in that method.
Minecraft crashes when populating a chunk which has empty columns ("void columns"), i.e. colums with just air blocks, no bedrock, such as can for instance be generated by WorldPainter (by using a Void border or the Void layer).
I have attached the crash report. I don't have access to the Minecraft source code, but using the Minecraft Coder Pack for Minecraft 1.7.2 I've traced it to the following code in BiomeDecorator.java (method func_150513_a(BiomeGenBase), lines 160-166):
for(var3 = 0; var3 < this.grassPerChunk; ++var3) { var4 = this.chunk_X + this.randomGenerator.nextInt(16) + 8; var5 = this.chunk_Z + this.randomGenerator.nextInt(16) + 8; var6 = this.randomGenerator.nextInt(this.currentWorld.getHeightValue(var4, var5) * 2); WorldGenerator var10 = p_150513_1_.getRandomWorldGenForGrass(this.randomGenerator); var10.generate(this.currentWorld, this.randomGenerator, var4, var6, var5); }It takes the height at a particular x,z coordinate and feeds the result (times two) to Random.nextInt(int). Unfortunately that method throws an exception when passed a value of zero.
One way to fix this would be to change those lines to something like:
for(var3 = 0; var3 < this.grassPerChunk; ++var3) { var4 = this.chunk_X + this.randomGenerator.nextInt(16) + 8; var5 = this.chunk_Z + this.randomGenerator.nextInt(16) + 8; int height = this.currentWorld.getHeightValue(var4, var5); if (height > 0) { var6 = this.randomGenerator.nextInt(height * 2); WorldGenerator var10 = p_150513_1_.getRandomWorldGenForGrass(this.randomGenerator); var10.generate(this.currentWorld, this.randomGenerator, var4, var6, var5); } }The same would have to be done for the other loops in that method.
Crash report with default biomes.
Minecraft crashes when populating a chunk which has empty columns ("void columns"), i.e. colums with just air blocks, no bedrock, such as can for instance be generated by
WorldPainter (by using a Void border or the Void layer).I have attached the crash report. I don't have access to the Minecraft source code, but using the Minecraft Coder Pack for Minecraft 1.7.2 I've traced it to the following code in BiomeDecorator.java (method func_150513_a(BiomeGenBase), lines 160-166):
for(var3 = 0; var3 < this.grassPerChunk; ++var3) { var4 = this.chunk_X + this.randomGenerator.nextInt(16) + 8; var5 = this.chunk_Z + this.randomGenerator.nextInt(16) + 8; var6 = this.randomGenerator.nextInt(this.currentWorld.getHeightValue(var4, var5) * 2); WorldGenerator var10 = p_150513_1_.getRandomWorldGenForGrass(this.randomGenerator); var10.generate(this.currentWorld, this.randomGenerator, var4, var6, var5); }It takes the height at a particular x,z coordinate and feeds the result (times two) to Random.nextInt(int). Unfortunately that method throws an exception when passed a value of zero.
One way to fix this would be to change those lines to something like:
for(var3 = 0; var3 < this.grassPerChunk; ++var3) { var4 = this.chunk_X + this.randomGenerator.nextInt(16) + 8; var5 = this.chunk_Z + this.randomGenerator.nextInt(16) + 8; int height = this.currentWorld.getHeightValue(var4, var5); if (height > 0) { var6 = this.randomGenerator.nextInt(height * 2); WorldGenerator var10 = p_150513_1_.getRandomWorldGenForGrass(this.randomGenerator); var10.generate(this.currentWorld, this.randomGenerator, var4, var6, var5); } }The same would have to be done for the other loops in that method.
Minecraft crashes when populating a chunk which has empty columns ("void columns"), i.e. colums with just air blocks, no bedrock, such as can for instance be generated by creating a Superflat world with preset "2;0;1;decoration".
I have attached the crash report. I don't have access to the Minecraft source code, but using the Minecraft Coder Pack for Minecraft 1.7.2 I've traced it to the following code in BiomeDecorator.java (method func_150513_a(BiomeGenBase), lines 160-166):
for(var3 = 0; var3 < this.grassPerChunk; ++var3) { var4 = this.chunk_X + this.randomGenerator.nextInt(16) + 8; var5 = this.chunk_Z + this.randomGenerator.nextInt(16) + 8; var6 = this.randomGenerator.nextInt(this.currentWorld.getHeightValue(var4, var5) * 2); WorldGenerator var10 = p_150513_1_.getRandomWorldGenForGrass(this.randomGenerator); var10.generate(this.currentWorld, this.randomGenerator, var4, var6, var5); }It takes the height at a particular x,z coordinate and feeds the result (times two) to Random.nextInt(int). Unfortunately that method throws an exception when passed a value of zero.
One way to fix this would be to change those lines to something like:
for(var3 = 0; var3 < this.grassPerChunk; ++var3) { var4 = this.chunk_X + this.randomGenerator.nextInt(16) + 8; var5 = this.chunk_Z + this.randomGenerator.nextInt(16) + 8; int height = this.currentWorld.getHeightValue(var4, var5); if (height > 0) { var6 = this.randomGenerator.nextInt(height * 2); WorldGenerator var10 = p_150513_1_.getRandomWorldGenForGrass(this.randomGenerator); var10.generate(this.currentWorld, this.randomGenerator, var4, var6, var5); } }The same would have to be done for the other loops in that method.
![[Mod] Ezekiel (ezfe)](../../../data/assets/gravatar/ezekielelin.jpeg){kind=small}
Minecraft crashes when populating a chunk which has empty columns ("void columns"), i.e. colums with just air blocks, no bedrock, such as can for instance be generated by creating a Superflat world with preset
"2;0;1;decoration".I have attached the crash report. I don't have access to the Minecraft source code, but using the Minecraft Coder Pack for Minecraft 1.7.2 I've traced it to the following code in BiomeDecorator.java (method func_150513_a(BiomeGenBase), lines 160-166):
for(var3 = 0; var3 < this.grassPerChunk; ++var3) { var4 = this.chunk_X + this.randomGenerator.nextInt(16) + 8; var5 = this.chunk_Z + this.randomGenerator.nextInt(16) + 8; var6 = this.randomGenerator.nextInt(this.currentWorld.getHeightValue(var4, var5) * 2); WorldGenerator var10 = p_150513_1_.getRandomWorldGenForGrass(this.randomGenerator); var10.generate(this.currentWorld, this.randomGenerator, var4, var6, var5); }It takes the height at a particular x,z coordinate and feeds the result (times two) to Random.nextInt(int). Unfortunately that method throws an exception when passed a value of zero.
One way to fix this would be to change those lines to something like:
for(var3 = 0; var3 < this.grassPerChunk; ++var3) { var4 = this.chunk_X + this.randomGenerator.nextInt(16) + 8; var5 = this.chunk_Z + this.randomGenerator.nextInt(16) + 8; int height = this.currentWorld.getHeightValue(var4, var5); if (height > 0) { var6 = this.randomGenerator.nextInt(height * 2); WorldGenerator var10 = p_150513_1_.getRandomWorldGenForGrass(this.randomGenerator); var10.generate(this.currentWorld, this.randomGenerator, var4, var6, var5); } }The same would have to be done for the other loops in that method.
Minecraft crashes when populating a chunk which has empty columns ("void columns"), i.e. colums with just air blocks, no bedrock, such as can for instance be generated by creating a Superflat world with preset
2;0;1;decorationI have attached the crash report. I don't have access to the Minecraft source code, but using the Minecraft Coder Pack for Minecraft 1.7.2 I've traced it to the following code in BiomeDecorator.java (method func_150513_a(BiomeGenBase), lines 160-166):
for(var3 = 0; var3 < this.grassPerChunk; ++var3) { var4 = this.chunk_X + this.randomGenerator.nextInt(16) + 8; var5 = this.chunk_Z + this.randomGenerator.nextInt(16) + 8; var6 = this.randomGenerator.nextInt(this.currentWorld.getHeightValue(var4, var5) * 2); WorldGenerator var10 = p_150513_1_.getRandomWorldGenForGrass(this.randomGenerator); var10.generate(this.currentWorld, this.randomGenerator, var4, var6, var5); }It takes the height at a particular x,z coordinate and feeds the result (times two) to Random.nextInt(int). Unfortunately that method throws an exception when passed a value of zero.
One way to fix this would be to change those lines to something like:
for(var3 = 0; var3 < this.grassPerChunk; ++var3) { var4 = this.chunk_X + this.randomGenerator.nextInt(16) + 8; var5 = this.chunk_Z + this.randomGenerator.nextInt(16) + 8; int height = this.currentWorld.getHeightValue(var4, var5); if (height > 0) { var6 = this.randomGenerator.nextInt(height * 2); WorldGenerator var10 = p_150513_1_.getRandomWorldGenForGrass(this.randomGenerator); var10.generate(this.currentWorld, this.randomGenerator, var4, var6, var5); } }The same would have to be done for the other loops in that method.
is duplicated by
is duplicated by
is duplicated by
is duplicated by
is duplicated by
is duplicated by
Here is the annoying crash that has now interrupted my progress on my custom map I was making. I would appreciate a fix.
This bug still occurs in snapshot 14w29a. I attached the crash log.
is duplicated by
![[Mod] CubeTheThird](../../../data/assets/gravatar/cubethethird.jpeg){kind=small}
is duplicated by
is duplicated by
is duplicated by
Mog (Ryan Holtz)is duplicated by
relates to
From Linux. Demonstrates the issue with a Minecraft generated world map using the steps outlined in bug report MC-46082.
Duplicate of MC-46082 - If you have not, please use the search function in the future, to see if your bug has already been submitted. If you could not find the original report, please comment with the keywords you searched for.
Dupe of MC-46082
I can provide a test map if desired.
You are using large biomes! Say it in the description!
Thanks for the tip. I tested it, and it also happens with default biomes. I'll attach another crash report.
Reproduction steps?
To reproduce, unzip this map (created with WorldPainter) to the saves folder and try to load it in Minecraft. It will hang, but the log will show the exception.
And how would one reproduce it without using any third party tools?
This ticket is invalid as it relates to a modified or 3rd party client, server, or launcher.
Please post here if you can reproduce it in fully Vanilla Minecraft.
I wonder if you might reconsider:
Would it be possible for someone from Mojang to at least take a look at it?
I'm the one who initially reported this to bukkit and I am pretty sure that it can be reproduced in VANILLA Minecraft. Mojang should look at this issue.
Here are instructions for reproducing this problem with vanilla Minecraft:
I respectfully request that this bug be reopened, given that it is reproducible in vanilla Minecraft without using any external programs.
I can confirm that the above steps will produce a situation which causes Vanilla Minecraft to hang (running on Minecraft Linux):
Full log file attached.
How can this issue be "Resolved" when in fact it happens (per above) in Vanilla unmodified Minecraft using a Minecraft generated world map?!
Encouraging us to report bugs and then responding unintelligently really is counter productive, Mojang.
And here is MY bug report following the steps outlined above using preset "2;0;1;decoration" (without the quotes) on a Windows 7 64-bit PC:
From Linux. Demonstrates the issue with a Minecraft generated world map using the steps outlined in bug report
MC-46082.Here's an idea: Reopen this issue and don't mention worldpainter, just show the vanilla way to do it. That might get them to respond.
Reopened and marked as confirmed, since https://bugs.mojang.com/browse/MC-46082?focusedCommentId=142437&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-142437 will reproduce the crash.
This happens in any map reguardless if the map was made with worldpainter, mods that add void maps or just vanilla minecraft. One of my old custom maps has islands overhanging the void using a void map superflat preset, that map has now become unplayable as it just hangs there. Even one of Sethblings maps did it when I was flying around exploring how he did things.
I wont bother posting my bug reports from all the maps that I've tried playing thats caused this issue as it's just the same as the two posted already.
It's a mess, and needs to be fixed.
@Krystal - the requirement is that it be reproducible somehow, any how, in vanilla. If the issue cannot be shown without involving an external tool or mod then it should be reported to them, not Mojang. Once vanilla reproduction steps are provided the bug can be confirmed, accepted, and added to the list. We as mods rely on users details and so rely on vanilla steps being provided. Note this ticket was reopened and confirmed once they were provided, so this one is good on that front.
It is done in vanilla. Just as I said, it don't matter if the map was made by a 3rd party program, or made by vanilla minecraft. If there is void, and minecraft is trying to populate said chunk, ie even a super flat preset for void, it will crash same as everyone else is reporting.
One of my custom maps, that was MADE IN VANILLA of islands over the void, was first started being made when we first were able to do super flat worlds. I used a void preset.
I've worked on it on and off building it out block by block. It's my own personal little project.
Yet as of 1.7.4, all new 'void' chunks CRASH the game, giving the same error message. So I can't continue expanding the map as I go anywhere near the edge that would cause new void chunks to generate, minecraft will hang, display the same error as everyone else has posted.. and crash.
So yes, this is effecting new maps, and old maps, rather made IN VANILLA or made with a 3rd party program. If it's a void chunk trying to be populated, it causes the crash.
Krystal Ewing: We are aware it happens in vanilla, which was why fienxjox has told you that the ticket has been reopened. We are not disputing the fact it occurs in vanilla. Fienxjox was telling you our reason for the original resolution. Please re-check the ticket carefully - it is not closed and has been marked Confirmed.
I've verified that this still happens in version 1.7.5.
I'm gratified that the bug has been reopened. Would it be possible to actually get it fixed? I appreciate that there are a lot of open bugs (with many more votes), but relatively little work would be involved in fixing this one, since the bug is easy to reproduce (and therefore test) and I have already done the work of finding the bug and proposing a fix, and in addition the number of votes is not representative of the number of people affected, which is substantial.
Also, it's a very severe bug, entirely crashing Minecraft and preventing play.
You might be able to run 14w03a and later, and then use the /fill command to do "/fill <x1> < y1> <z1> <x2> < y2> <z2> minecraft:air" to cause this problem, help fix it, but I haven't tried that yet
Sam, there's already an easy way to reproduce the issue: just create a Superflat world with preset "2;0;1;decoration". Instant crash (it hangs, but on the console you can see it actually crashed).
While searching the web, I finally found this bug report and it appears to be what I'm seeing:
Description: Exception ticking world
java.lang.IllegalArgumentException: n must be positive
...
I encountered this error when playing a custom map (Vechs' Sunburn Island Super Hostile) and have downloaded other custom maps (Vechs, Sethbling, etc) and had them all crash with the above error when nearing the map's border with what seems to be all 1.7.x clients, including 1.7.10. I was able to approach the map borders under the 1.6.4 client without crashing.
I know this is not the best bug report, but the OP appears to already have a handle on the cause and reproduction of this bug. Seeing the low "votes" on this issue and what appears to be no hurry to fix it, I wanted to let you guys know the kind of impact this has. I know that technically a custom map is no longer "vanilla" Minecraft, but using this excuse to dismiss the coding bug also dismisses most of the custom map maker community.
[Minecraft] Custom Map Makers have always done the the same thing by customizing a normal map/seed and clearing an area where they build their custom map and then making a border that usually involves removing blocks and/or replacing them with something like bedrock. This bug affects users trying to play these custom maps with a 1.7.x version and I had to search pretty hard to find this bug, but found several hits of flustered users crashing all types of custom maps when approaching the map's borders and most of them sounded like typical end users who wouldn't even know what an issue tracker is, let alone how to search or submit to one.
Custom maps are vanilla minecraft. I don't know who told you otherwise. Not all custom maps are made with map editors.
Good thing 1.8 won't have any custom maps. Oh wait...oh...uh...maybe this bug should be fixed before the "custom map update" known as 1.8 comes out. This would seem to be the #1 bug for 1.8.
@Tokes:
I was reading other bug reports that have been closed as duplicate of this one and some of those bugs referenced using 3rd party tools and were flagged as "not vanilla" because of that.
It appears to boil down to the error:
...
Description: Ticking memory connection
java.lang.IllegalArgumentException: n must be positive
...
Which is something in the 1.7.x code (and in the 1.8 snapshots) that tries to divide by zero when it loads a chunk containing modifications the way some map makers make an impenetrable border to their custom map "sandboxes."
The point of my post is that this bug probably has a much bigger impact on the Minecraft community than any of the previous posts indicate. I can only speculate that users crash when approaching the border of some custom maps and blame the map maker as a bad designer without trying to get at the root cause or providing a useable bug report to Mojang. Basically the typical game playing end user will at most post something like these:
http://bugs.mojang.com/browse/MC-55498
http://www.minecraftforum.net/topic/191908-ctmcollection-vechs-super-hostile-series/page__st__60620
http://www.minecraftforum.net/topic/1818607-puzelementsco-op174/
http://www.planetminecraft.com/forums/ticking-memory-connection-t402397.html
http://www.minecraftforum.net/topic/2770100-help-me/
http://www.minecraftforum.net/topic/2281720-ticking-memory-connection-crash/#entry27796384
@Tokes They should fix this before the update that I'm referring to as "The mapmakers' dream, the modmakers' nightmare. Mojang sure seems to be supporting that when they say that a "map editor is not vanilla"
I have also been having this issue creating a custom map of mine. I create a void area by creating a super flat world with the generation settings 2;0;1. I then changed the world type of the single player world using no 3rd party software, and the "n must be positive" crash occurs every time I join the world. It has halted my progress on the map, making this update a pretty unsuccessful "map maker" update. A fix would be very appreciated.
The short term fix is to use the preset "0:0" instead of the bugged one.
This bug still occurs in snapshot 14w29a. I attached the crash log.
...and 14w29b. Crash log attached.
@ShadowofElements unless this is fixed, it should apply to every version, since this bug can't really be resolved by fixing other bugs.
@Samg_is_a_Ninja I understand that it will apply until it is fixed, but I am trying to keep this bug updated as it is very important to certain custom maps (including the one I am trying to create).
@ShadowofElements Is this why they added the /worldborder command? I'm making a custom map and I'm just going to make superflat bedrock world, and use WorldPainter or MCEdit or some (apparently not vanilla!) map editor to copy and paste the map in it, then just use the /worldborder command. The only problem is the map has to be square.
@Samg_is_a_Ninja I don't believe that is the reason. The problem occurs in the map that I made when a player gets close enough to an air chunk to try and populate it, which means to add the decorations and such. Because I have air chunks in a normal world, this crash occurs when the game tries to populate them. I tried pre-generating the chunks, but to no avail.
Crash log for 14w30b attached.
/worldborder is a great [new] tool, but it will not fix maps already in existence that fall prey to this bug.
If the cause is the code noted by the OP, it should be possible to either not drop into the loop or bug out of it under divide by 0 conditions or even go back and see how it's done in 1.6.x and earlier versions that don't crash.
I'm starting to get frustrated with Mojang at this point. All they have to do is copy, paste, and test the suggested lines above. If you guys do that and it doesn't work, let me know. But I doubt that. So basically its back to everyone waiting on Mojang.
I REALLY hope that this bug gets released in a map maker update. This will cause a lot of frustration, and @Samg_is_a_Ninja, you are right. This bug wouldn't take barely any effort at all to fix. Please Mojang, help us!
Fixed in 1.8! Cool, thank you very much Mojang!
Does this mean the fix will be in the next weekly build as well?
1.8 is already prereleased, but 1.8-pre2 is expected today.
Thank you so much Mojang! I am glad this bug was fixed,, now the map that it made in 1.6, people can download and use 1.8.
Thanks Mojang!
Unfortunately it seems that the bug has only been fixed for Superflat mode.
Is there any chance of getting it fixed for all world types, to fix the use case where people want Minecraft to populate the world with trees, etc. but want it to contain void as well?
Can you post a preset which includes empty columns? (or some other way to reproduce)