Ore Control

Description

Description

A small mod to control ore generation, chunk population and biome decoration. In the config file you can individually set which ores or terrain features are not allowed to generate in the world.

For ores, this includes Dirt and Gravel pocket generation inside stone, and Emerald ore and Silverfish blocks in Extreme Hills biomes. Additionally, in 1.8+ you can also individually disable the new stone types (Andesite, Diorite and Granite). For decoration stuff, you can disable all the things like tall grass, trees, mushrooms, flowers etc.

The decoration and population control was added in version 0.4.0. In the same version, support was also added for per-dimension configs.

To use per-dimension configs:

• All the config files are in the config/orecontrol/ directory
• Enable the B:enablePerDimensionConfigs config option in the main orecontrol.cfg file
• Then copy the main config file or create a new empty file named orecontrol_dim1.cfg (for dimension 1) etc. for each dimension you want
• Start the game or load a world so the per-dimension configs get populated with all the options

The per-dimension configs always override the main config for that dimension, if they exist.

Note: Emerald Ore and Monster Egg (= Silverfish block) generation are not part of the regular ore generation. The OreGenEvent.GenerateMinable event was added for them in Forge 11.15.0.1618 for MC 1.8.8. Ore Control 0.3.1 is the first version which uses those events for disabling Emeralds and Silverfish blocks. In older versions of the mod they get handled separately, by replacing any Emerald Ore and Monster Egg blocks in the world with Stone in the PopulateChunkEvent.Post event, aka. after the chunks get populated during world generation.

Mod packs/permissions

• Re-hosting the mod file is not cool, mmkay?
• Mod packs: go ahead!
• Basically follow Wheaton's Law (= Don't be a dick.).

What means Verified?

• Compatibility: The mod should be compatible with the latest version of Minecraft and be clearly labeled with its supported versions.
• Functionality: The mod should work as advertised and not cause any game-breaking bugs or crashes.
• Security: The mod should not contain any malicious code or attempts to steal personal information.
• Performance: The mod should not cause a significant decrease in the game's performance, such as by causing lag or reducing frame rates.
• Originality: The mod should be original and not a copy of someone else's work.
• Up-to-date: The mod should be regularly updated to fix bugs, improve performance, and maintain compatibility with the latest version of Minecraft.
• Support: The mod should have an active developer who provides support and troubleshooting assistance to users.
• License: The mod should be released under a clear and open source license that allows others to use, modify, and redistribute the code.
• Documentation: The mod should come with clear and detailed documentation on how to install and use it.

How to Install