This mod adds new ore variants (both normal and dense–optionally) for andesite, diorite, and granite, and is largely customizable. Most settings are vanilla by default, but can be customized or, in many cases, completely disabled. Otherwise, these blocks function exactly like their vanilla counterparts, complete with redstone ore effects, recipes, and all.
The mod also allows users to add ore variants for almost any background block, provided it can find the model. This means Nether and End variants can be added with only a couple of words. Moreover, users can modify almost any property of all existing ores, as well as add support for others and even create entirely new ores, using a builtin mod-type system. See documentation below.
Without that, the following mods are automatically supported in 1.12:
Suggestions and bug reports can be sent to GitHub. However, I welcome any feedback and am usually willing to discuss potential changes or additions to the mod on Discord. I’m also willing to help you get things setup exactly how you like them, so feel free to join us there! Here’s a link.
Full range of transparency:
Which implies automatic CTM support for background layers:
World Generation Features:
Most world-gen settings emulate vanilla as closely as possibly by default, but I’ll admit, I don’t prefer this. See configuration (below).
Example configuration file (UTD : Sept. 26, 2018)
Edit: The exact names of these values are not the same since 5.0, but most of them have analogues. They have simply been flattened into fewer categories and use fewer “negative” descriptors, which should make them easier to reason about.
Configuration settings and details (not fully UTD — See the example file.):
Variant Drop Settings:
“Variants Drop” and
“Variants Still Drop with Silk Touch”
By default, the new variants do not drop unless silk touch is used. This is to avoid inventory clutter. If you like the variants and would prefer to obtain them more easily, you can set “Variants Drop” to true in order to obtain iron and gold ore without silk touch. If you’re still turned off by the thought of inventory clutter and would like to never get these variants, you can set “Variants Still Drop with Silk Touch” to false and, of course, they will not drop even when using silk touch.
World Generation Settings:
“Replace Vanilla Ore and Stone Generation”
In order to stop normal ore variants from generating in all types of stone, I had to replace their spawn algorithm. You can set “Replace Vanilla Ore and Stone Generation” to false to disable this, which I recommend if you’re also using a mod such as Open Terrain Generator or any other mod which spawns underground ore patches (including stone, dirt, etc.) on its own. In effect, this setting simply disables most vanilla WorldGenMinable events.
These settings simply change the vein size of any given WorldGenMinable feature. Negative values decrease the vein size, where -2 is completely disabled and -1 is half size (15); 0 is vanilla size (33); and positive values increase size, where 1 is larger (44), and 2 is even larger (52).
“Stone Variant Count”
This setting changes the frequency of andesite, diorite, and granite clusters. A negative value means fewer clusters per chunk, where -1 is half frequency (5); 0 is vanilla frequency (10); and positive values increase them, where 1 is double frequency (20), and 2 is quadruple frequency (40).
“Generate Stone Variants in Layers” and
“Generate Stone Variants in Layers” setting changes the stone variants to only spawn at the given y coordinate range. Setting x_layer to 1 will spawn that type of stone from layers 0 to 20, whereas 2 will spawn it from layers 25 to 45, and 3 will do layers 40 to 80.
This setting toggles whether certain ores should only spawn in specific biomes. For example, emerald ore typically only spawns in mountain biomes, but setting this to false means it can also spawn in other biomes.
“Spawn Default Quartz Variants”
This setting adds quartz variants to the overworld. No need for adding the line under “Variant Adder”
Dimensions are whitelisted inside of an array contained within the config file, located under “world generation settings” > “dimensions” > “Dimension Whitelist.” You can see dimensions -1, 0, and 1 are listed by default. If you would like for ores to spawn in any modded dimensions, simply add their numbers here. This setting is for performance purposes. Many users would probably prefer better performance in said dimensions when nothing is supposed to happen, anyway. In that case, they would need to either remove the number of whichever dimension is listed by default, or not add the IDs of any new dimensions.
“Overlays are Shaded / are not Highlighted”
This setting changes whether the overlay textures are shaded. What this means is that certain overlays may become more or less visible depending on their backgrounds or opacity levels. I’ve set it to false by default because, specifically, the vanilla granite texture makes makes most of the included overlays difficult to see, but it does unfortunately mean that some textures are especially shiny-looking. I recommend setting it to true if you’re using a resource pack. In particular, any resource pack for which the overlay textures are at all transparent will probably look better when this is set to false.
You can enter the names of any ores that should be shaded opposite of the global setting. Any ore that is difficult for you to see based on your setup can be added to this list and it may look better.
Overlays are Shaded = false
Overlays are Shaded = true
This setting has been marked as experimental for some time, as I’m still not sure how effective it really is. It should theoretically make all blocks render in the “CUTOUT_MIPPED” render layer instead of transparent, but I’ve neglected to do much testing with it.
“Use Built-in Blended Textures”
Certain ores include translucent overlay textures, which allows them to blend into their background blocks more smoothly and also to retain stylistic consistency with the original sprites as closely as possible. Setting this to false swaps the textures to an entirely different set of textures which don’t have this. The option is currently provided in case some users prefer one setting vs. the other. This should not affect resource packs, as the file name is the same in both cases.
Bonus: Future builds will also include both 16x and 32x textures by default for better support with some specific mods. 😉 That’s one of the percs of running a relatively small mod thanks to the way block models are handled / almost don’t exist.
Dense Ore Settings
In order to maintain vanilla functionality as closely as possible, dense ores are disabled by default, but they can be enabled under “dense ore variants” > “general dense ore settings” > “Enable Dense Variants.” More information about dense ores can be found below.
This mod allows users to add new stone variants for almost any ore type. Literally. See below, as well as the documentation inside of ore_stone_variants.cfg for more information.
These settings allow the user to disable automatic creation of ore variants relative to each mod name, vanilla included.
“mod generation hax”
These settings are hacky and will result in other configurations’ comments being deleted, for now. On the other hand, if you don’t feel like disabling the ore generation from other mods for better compatibility, you can set these to true per-mod to do so. It doesn’t actually prevent the mod from doing anything in-code, just takes advantage of their config files. For this reason, you’ll need to restart your game twice for everything to take effect.
To be updated / missing information (Sept 26, 2018):
New Stone Types From Quark:
New Stone Types from Mineralogy
i r someday take photo. so complicated.
New Stone Types from Underground Biomes
For all mods supported in OSV, if the same mod is not supported by Underground Biomes, support will automatically be added using their stone types.
faux toe go here
All Ores from SimpleOres
These blocks function exactly like their counterparts, including support for all advancements added by SimpleOres. All settings are currently based on the mod’s default settings. However, future builds may provide the option to either read from or (if possible) circumvent SimpleOres’ configuration file.
Overworld Ores from Ice and Fire
All Ores from Base Metals
All Ores from Biomes O’ Plenty
All Ores from Glass Hearts
All Ores from Thermal Foundation
dev sux geta life
pix r so hard
I may not even write the next one …yet.
Dense Ore Variants
As of 2.0, users can now optionally enable dense ore variants in the config file. These variants function mostly like normal ores, but instead drop between 1 and 3 times as much as they normally would. Their textures are procedurally generated and placed inside of “resources.zip,” located under /config/ore_stone_variants_mods/, which is a resource pack that does not need to be moved or applied.
Large Cluster Mode
Background Block Imitation
Ore variants imitate their background blocks, taking on many of their properties.
Ore Dictionary Support
All ores are automatically registered with ore dictionary support, dynamic and manually added ores included.
Since 5.0, this process is entirely automated. Original Ore Dict values are retrieved for each ore type and applied automatically to their new variants.
In its current state, the mod uses multiple different texture paths for the same textures, depending on the user’s setup. This may complicate things for resource pack makers, so I’ve included a workaround.
Create a file inside of assets/ore_stone_variants/ called “osv.cfg” Inside, you can add a line that reads “force_single_texture_location = true” which will tell the mod to only retrieve the basic textures for any use. Since you’ll be replacing them anyway, it shouldn’t matter. You can look inside of config/ore_stone_variants_mods/resources.zip (a resource pack) for an example. Just change false to true.
There may be other options for resource pack developers in the future. Let me know if you have any ideas and I’ll consider adding them.
Because some people just want to watch the world burn; and others just want coal in a log.
This mod allows users to add ore variants to any block whatsoever using its dynamic model system. All you need to do is open the config file, look for “Add Blocks Here,” and enter the ore type followed by the block name to register new blocks, following the model in the config file. There is no need to provide a texture, blockstate file, block model, or item model. The block will function exactly like its parent ore type, inheriting the background block model of the chosen background block, and overlaying the appropriate ore texture on top.
Users can also enter a given mod’s namespace in place of “x_ore” and the mod will automatically create variants for all of that mod’s ores. For example, “”Add Blocks Here”=simpleores, stained_hardened_clay:3” will create a new variant for adamantium, copper, mythril, and tin, inside of stained_hardened_clay:3.
These blocks also function exactly like their counterparts, with world generation (whichever dimension is applicable), ore dictionary support, advancement support (if applicable), and even redstone ore effects. They can be configured just like any other block using the configuration settings mentioned above.
Because there are so few blocks in other vanilla dimensions, this does mean that you can add all ores to the Nether by typing this line under “Variant Adder” :
Likewise, you can add all ores to the End by typing
Note: I can’t guarantee it will work with any block (because of the way background block models are found), but I have tested quite a few mods with no issues.
Dynamic Ore Types
As of 5.0, the preset system is vastly simplified. Each ore has its own preset stored in
which can be edited to alter its properties, including block properties, texture settings, item drops, recipes, and world generation variables. See
for more information on which fields are supported.
As of 5.0, stone variants are spawned using new stone presets. These presets are stored in
and simply contain data about the original blockstate and its world generation variables. See
for more information.
As of 5.1, OSV now supports a new command:
For now, this command can be used to generate entirely new presets from new blocks and edit some other mods’ config files to disable their ore spawning.