IMPORTANT NOTICE:
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.
In Full:
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.
OreSpawn
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.
API
Adding OreSpawn support to your mod is not hard. You can look here for an example.
IMPORTANT:
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":
features-default.json replacements-default.json
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" ]
And after:
[ "modernmetals", "baseminerals", "endmetals", "basemetals", "nethermetals" ]
Or, if you have no custom configuration happening with OreSpawn at all, just delete the "config/orespawn3" directory entirely.
1.16.3???
i cant find the items
In reply to killer_speeder1975:
This is NOT any form of the mod found at http://www.orespawn.com - as the text that starts the description of this mod says, this mod SPAWNS ORES for other mods. That is why this is named "MMD ORESPAWN" - the whole "MMD" bit is part of the name that functionally describes what the mod does. If this somehow offends you, well, go on and be offended, but know that nobody actually has to listen to any ranting on your part about it.
you are very adamant that this IS NOT the orespawn that is poorly named
Hehe, couldn't find anything from "Ore Spawn" xD
(jk)
So what's the situation with 1.15+?
In reply to BurnN8or101:
Currently? Not enough time - I'm responsible for porting and maintaining somewhere close to a dozen mods and have a lot of RL duties to also handle.
In reply to dshadowwolf:
In that case, I'm going to take a crack at making a version for 1.15+ with the source. If that's ok.
In reply to BurnN8or101:
Of course it is. Just don't blame me if my sometimes convoluted code causes you to lose SAN
In reply to dshadowwolf:
OF course
Could I remove ores with this or just add ores to the generation?
In reply to krassy02:
You could set it to cancel vanilla generation and remove the config files that tell it what to do (as long as you leave ``config/OreSpawn3/sysconf``` alone you should be able to remove other JSON files and have it stop any ore spawns in the world (note that this will also stop all granite, andesite and diorite from spawning and also remove all subsurface dirt and gravel deposits. (That is the reason we have them in the example config that comes with MMD OreSpawn 3)
Hello, i having a crash when i use with dense metals. I use the version 3.3.0 and above and also having the crash. Because this i lost a entire map. I sad but i still trying fix. Can somebody help me?
This is the message of crash
The game crashed whilst there was a severe problem during mod loading that has caused the game to fail
Error: net.minecraftforge.fml.common.LoaderExceptionModCrash: Caught exception from OreSpawn (orespawn)
Edit: I reinstalled the forge, the two mods (orespawn and dense metals) and THE MINECRAFT. Nothing...
I'm Braziliam sorry about my english. :(
In reply to letisgoll:
That is not the full crash log which we'd need to assist you, please don't just pick the bits you think are relevent.
ps: we prefer support requests to be made on our github, not curseforge comment or DM.
I'm hoping for help. Here's my orespawn.json. I left the other config files at default. I'm trying to add this to an existing world using the modpack Hekxit 3, which is 1.12.2-based and in Technic. I'm sure part of my problem is mod/block names. I can't seem to find the relevant log for help.The jar was added to the server and the clients and, according to latest.log, seems to be loading ok. There appears to be no change in any ores, including the vanilla Minecraft ones. Thanks!
Edit - Reading through all the comments I may have figured something out. Since it is an existing world, do I need to change this to true?: Do we have Retrogen active and generating anything different from the last run in already existing chunks ? [default: false]
If so, do I then set it back to false once I've restarted and the new ores have been generated?
In reply to hekylnjekyl:
in orespawn.cfg and in the JSON you'll want to flip the "retrogen" flag - though if you use the "force" form of it you'll want to turn it off again later on, the standard form records some data in the world to say what it had configured (to a point) at the time of generation and if it doesn't roughly match current, it'll re-run in that chunk.
1.15??
In reply to carriecakex:
Every time someone makes this kind of comment I put off working on the code for another month. It's already looking like this won't be out until 1.18 territory now :)
In reply to dshadowwolf:
Well then I guess there is no point in waiting, rip
In reply to dshadowwolf:
Man. I hate those comments as much as the next guy, but I've never seen a developer be this much of an asshole.