TL;DR: If the fact that this mod "Spawns Ores" and is not related to the mod "Ore Spawn"in any way offends you, just go away. Otherwise know that, as stated, this mod SPAWNS ORES and that is all it does - the name is descriptive and not meant to, in any form, be confusing, hence the continual inclusion of the "MMD" prefix. At the last time things were checked (June 7, 2019) the mod "OreSpawn" that adds new enemies, girlfriends and such has not been ported off 1.7.10.
This mod has no relation to the "OreSpawn" mod from 1.7.10 that had trees that would replicate ores and gave you "Dragon Girlfriends" and special mobs. Do not bother us with "Mobs are spawning" or "Not finding anything from the mod" - this mod - MMD OreSpawn - exists to provide ore-spawning (and, hopefully, other world-gen features, in the future) to other mods. It does not add mobs or any content.
If the fact that this mod has a name that describes exactly what it does and that it is not related in any way, shape or form to The Badly Named Mod "OreSpawn" - just go away. Do not think you are free to heap your own stupidity, hatred and vitriol on us.
Minecraft library mod that provides better control over the spawning of ores in Minecraft.
Talk to the devs on Discord: here
How it works
Ore Spawn parses all of the .json files found in config/orespawn3 and adds ore generators to the game based on those files.See more in the JSON documentation.
Adding OreSpawn support to your mod is not hard. You can look here for an example.
MMD OreSpawn 3.3.0 has changed several parts of how it operates, internally, and has also changed the format of one of the configuration files. Because of this, while there are no major differences in the rest of the configuration files, when upgrading from the MMD OreSpawn 3.2 series, you can either delete the entirety of the "config/orespawn3" directory and allow it to regenerate with the defaults or you can follow the following steps:
1) Delete the following files, found in "config/orespawn3/sysconf":
2) Back up any and all customization that has been made to the configurations, specifically the "orespawn.json" file in "config/orespawn3"
3) Edit "config/orespawn3/sysconf/known-configs.json" and remove the line that has "orespawn" as the contents. The file should appear similar to the following, prior to the edit
[ "modernmetals", "orespawn", "baseminerals", "endmetals", "basemetals", "nethermetals" ]
[ "modernmetals", "baseminerals", "endmetals", "basemetals", "nethermetals" ]
Or, if you have no custom configuration happening with OreSpawn at all, just delete the "config/orespawn3" directory entirely.