Not Enough God Damn Ores

Description

This mod is simply TooManyGodDamnOres ported for MinecraftForge 1.9.4 NOW WITH FEATURES FROM TooManyDanyOres!

If TooManyDanyOres is ported to 1.9.4, please use it instead.

MODPACKS: Leave post down in comments saying you will include the mod in the pack, with the name of the pack.

Description:

This mod does not disable world gen of ores, but simply adds in methods to change the ores after harvesting them.

It's all based off configuration and is very easy to use.

To configure a replacement, simply add the ore dictionary name, followed by the modid for the replacement block.

Take the below configuration as an example:

# Configuration file

exclusions {
        S:oreCopper <
                TConstruct:GravelOre
        >
        S:oreTin <
                TConstruct:GravelOre
        >
}

exclusions {
}


notenoughgoddamnores {
 # Try increasing in case of lag [range: 1 ~ 1200, default: 100]
 I:"Merge Items Every X Ticks"=100
}


replacements {
 S:ingotBronze=techreborn
 S:ingotCopper=techreborn
 S:ingotLead=techreborn
 S:ingotSilver=techreborn
 S:ingotTin=techreborn
 S:oreCopper=techreborn
 S:oreLead=techreborn
 S:oreSilver=techreborn
 S:oreTin=techreborn
}

With this config, when a block is harvested, and said block is in the config for OreDictionary translation, the block will be changed to the TechReborn version. Also, if you have any of the ores or items mentioned in the config in your inventory, every 100 ticks they will be translated.

This works with silk touch, and aims to not interfere with any other mods that use the HarvestDropsEvent.

In the case of mods like TinkersConstruct, you'll want to exclude certain blocks from being replaced or being used to replace others. In the example above you'll see us excluding the gravel ore blocks. New versions of TinkersConstruct do not need this, but you may need to use an exclusion for something else.

This mod is aimed for people putting together their own modpacks, and do not want to mess with ore generation.

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