Eric Veilleux
- DementedCreation
- dementedcreation
- America/New_York
- Yes
- No
MC-128297![[Mojang] slicedlime](../../../data/assets/gravatar/slicedlime.jpeg){kind=small}
In the Overworld, mobs won't spawn. Play several hours, built a platform 30 blocks out for mobs to spawn. Neither hostile nor passive mobs spawn naturally. (Btw it's a void world - friends and I wanted to play a world called Vanilla SkyBlock on CurseForge.) Played for hours now. For some reason, mobs in the Nether will spawn. Went to the Nether roof, tried to spawn the Wither in, didn't spawn. Brought it to an open area, still didn't spawn. ("And I said: WHY-e-i-ei-ooo")
EDIT: After more testing, I think I know why. Even during the night, both the Client Light and Server Light, for the sky, is 15 during both the day and night. Since mobs in the Overworld spawn in low light levels, they won't spawn. However, since mobs in the Nether don't take light levels into account, they do spawn. The sky light level can be changed if you block the sky with a series of blocks.
"Aternos.org" Vanilla Server
Amethyst Geodes won't generate in superflat worlds, plain and simple. Of course, it would be weird if they generated in void worlds, by why wouldn't the option be there? More importantly, they don't generate when using the 'Tunnelers' Dream' preset, while other ores like coal do generate.
There should be an option to forcefully turn on or off the generation of Amethyst Geodes, for any world type. There should probably be an option in the experimental world generation settings.
I've attached a screenshot that shows
be using the Tunnerlers' Dream superflat preset, and how underground water & lava lakes generate but there are no Amethyst Geodes.Amethyst Geodes won't generate in superflat worlds, plain and simple. Of course, it would be weird if they generated in void worlds, by why wouldn't the option be there? More importantly, they don't generate when using the 'Tunnelers' Dream' preset, while other ores like coal do generate.
There should be an option to forcefully turn on or off the generation of Amethyst Geodes, for any world type. There should probably be an option in the experimental world generation settings.
I've attached a screenshot that shows me using the Tunnelers' Dream superflat preset, and how underground water & lava lakes generate but there are no Amethyst Geodes.
No option forAmethyst Geodes generationAmethyst Geodes generation not working as expected
I'm trying to generate a void world with the default overworld biomes using a data pack (attached). I've managed to strip the world of most detail, but when it comes to doing this:
{ "Name": "minecraft:air" }
"default_block":The world generates with stone blocks water lakes. It should probably be noted that, when generating the world for the first time, I change nothing in-game. I simply rename the world, select the data pack, and hit generate.
There are other problems, like the fact that there shouldn't be any lakes at all, and the fact that a bedrock floor generates when it shouldn't, but I believe those belong in separate bug reports.
I'm trying to generate a void world with the default overworld biomes using a data pack (attached). I've managed to strip the world of most detail, but when it comes to doing this: "default_block": { "Name": "minecraft:air" } (in data/minecraft/worldgen/noisesettings/overworld.json)
The world generates with stone blocks water lakes. It should probably be noted that, when generating the world for the first time, I change nothing in-game. I simply rename the world, select the data pack, and hit generate.
There are other problems, like the fact that there shouldn't be any lakes at all, and the fact that a bedrock floor generates when it shouldn't, but I believe those belong in separate bug reports.
When using the attached datapack with some custom world generation settings, generating the world is incredibly slow. Normally, my computer can generate a new world fairly quickly. However, something about this makes it stay at 0% for actual minutes. This may be a problem with what I've done in the datapack, but I'm also fairly sure that it's a weird custom world generation bug.
Looking through the log, there were no errors.When using the attached datapack with some custom world generation settings, generating the world is incredibly slow. Normally, my computer can generate a new world fairly quickly. However, something about this makes it stay at 0% for actual minutes. This may be a problem with what I've done in the datapack, but I'm also fairly sure that it's a weird custom world generation bug.
After letting it run for 10-ish minutes, it crashed with an IllegalArgumentException. I've also attached the crash report.
When using the attached datapack with some custom world generation settings, generating the world is incredibly slow. Normally, my computer can generate a new world fairly quickly. However, something about this makes it stay at 0% for actual minutes. This may be a problem with what I've done in the datapack, but I'm also fairly sure that it's a weird custom world generation bug.
After letting it run for 10-ish minutes, it crashed with an IllegalArgumentException. I've also attached the crash report.
When using the attached datapack with some custom world generation settings, generating the world is incredibly slow. Normally, my computer can generate a new world fairly quickly. However, something about this makes it stay at 0% for actual minutes. This may be a problem with what I've done in the datapack, but I'm also fairly sure that it's a weird custom world generation bug.
After letting it run for 10-ish minutes, it crashed with an IllegalArgumentException. I've also attached the crash report.
EDIT: Added updated pack for 1.18.2 - world still doesn't load, though.
When using the attached datapack with some custom world generation settings, generating the world is incredibly slow. Normally, my computer can generate a new world fairly quickly. However, something about this makes it stay at 0% for actual minutes. This may be a problem with what I've done in the datapack, but I'm also fairly sure that it's a weird custom world generation bug.
After letting it run for 10-ish minutes, it crashed with an IllegalArgumentException. I've also attached the crash report.
EDIT: Added an updated pack for 1.18.2 - the world still doesn't load, though.
EDIT 2: Added another updated pack for 1.19 snapshots - the world still doesn't load too.
World gen is very slow withcustom settingsWorld gen is very slow with negative sea level
When using the attached datapack with some custom world generation settings, generating the world is incredibly slow. Normally, my computer can generate a new world fairly quickly. However, something about this makes it stay at 0% for actual minutes. This may be a problem with what I've done in the datapack, but I'm also fairly sure that it's a weird custom world generation bug.
After letting it run for 10-ish minutes, it crashed with an IllegalArgumentException. I've also attached the crash report.
EDIT: Added an updated pack for 1.18.2 - the world still doesn't load, though.
EDIT 2: Added another updated pack for 1.19 snapshots - the world still doesn't load too.
UPDATE: After some testing, it's the negative sea level that's throwing Minecraft off.
Can confirm for MC 1.14, 1.14 Pre-Release 1, and 1.14 Pre-Release 2. Can't spawn the Wither, and no mobs spawn in the overworld. NONE.
Done, added screenshots - the same resource pack is active in both. Left is 19w45b, right is 1.14.4. You can tell the pack is active by the transparent hotbar
This will be awful for combat... I thought you guys learn your lesson form 1.9
Amethyst Geodes aren't structures, so I don't think this relates to that
This isn't the place for feature requests. This is a BUG TRACKER. Please head over to the feature requests page -> https://feedback.minecraft.net/hc/en-us
Also, Mojang have already stated that they won't be adding dynamic lighting anytime soon.
Working as intentional. Leather armor only slows the freezes process, it doesn't stop it.
This bug only happens with there are no structures in the "structures" field. I closed this issue because I figured that out.