Majestic Terrain

v0.0.0-beta.5 — Majestic Core is now a listed dependency

Same world generation as beta.4, with the packaging and the status command made honest.

Added

• Majestic Core is a listed dependency again. It could not be while its CurseForge project was unapproved — CurseForge rejects the whole upload with an invalid slug. It has since been approved, so the launcher will install it for you and the page will link to it. It was always a hard requirement in the mod metadata; without this, a missing Majestic Core meant a crash instead of an automatic install.

Changed

• /majestic_terrain status now reads the running world instead of the config file, and says plainly whether our biomes are in the Overworld's biome source or not. A mod whose entire product is invisible worldgen should be able to say so.
• It also reports each biome as present in that world's biome list, or not. That is the difference between "the config asked for it" and "it is actually there".
• /majestic_terrain status now states that the custom relief switch does nothing yet. It has shipped as a no-op since beta.3 and saying so beats leaving a toggle that promises something and quietly does not.

Notes

• A world created with beta.3 or beta.4 stays broken. Its chunks were generated before the grove existed there. Make a new one.
• beta.3 has been left on this page rather than deleted, so the history is visible: it is the version where the grove never appeared anywhere, and it has 6 downloads from people who were right to be suspicious.
• Verify the grove is really in your world with /majestic_terrain probe before hunting for it. The answer should be a few hundred samples, not zero.