MC-54331Custom Map Generation Randomized Min. v Max. Ore Generation Bug
On the Custom Map Generation, page 2 of the options menu, the ores menu, hitting the randomization button will not keep in mind the fact that the minimum spawn level must be less than the maximum spawn level and it occasionally makes the minimum larger than the maximum, thus making the world impossible to load.
What I expected to happen was that the randomizing button would automatically make sure the minimum was lower than the maximum.
What actually happened was the minimum was somewhere around 100 and the maximum was around 70 or 50.
I'm not sure how often it happens, but I noticed this because my world wouldn't load after many long periods of multiple attempts.
Environment
Windows 8
Attachments1
Created Issue:
Custom Map Generation Randomized Min. v Max. Ore Generation Bug
On the Custom Map Generation, page 2 of the options menu, the ores menu, hitting the randomization button will not keep in mind the fact that the minimum spawn level must be less than the maximum spawn level and it occasionally makes the minimum larger than the maximum, thus making the world impossible to load.
What I expected to happen was that the randomizing button would automatically make sure the minimum was lower than the maximum.
What actually happened was the minimum was somewhere around 100 and the maximum was around 70 or 50.
I'm not sure how often it happens, but I noticed this because my world wouldn't load after many long periods of multiple attempts.
Environment
Windows 8
Can confirm this in 14w19a
Duplicate of
MC-53469Yes this issue still occurs in 14w31a
Both iron and diamond have been assigned a min height higher than the max height: snapshot 14w31a
Is this still a concern in the current Minecraft version? If so, please update the affected versions in order to best aid Mojang ensuring bugs are still valid in the latest releases/pre-releases. If this has been done, we can reopen the issue.
Keep in mind that the "Resolved"-Status on this ticket just means "Answered", and that we are waiting for further information on whether this issue still exists or not. We will reopen it as soon as the requested information has been delivered.
Ticket resolved as incomplete, because no answer in a reasonable amount of time (1+ year), if it still happens, please update the ticket.