π Iris
Overviewβ
Iris includes first-class Oraxen integration. Once both plugins are installed, Oraxen registers itself as an external data provider, so Iris can resolve your custom blocks directly inside pack configs.
No extra bridge, addon, or manual registration is required. Install both plugins and use the oraxen:block_id format in Iris configs.
Block Formatβ
Use the Oraxen namespace followed by your block ID.
oraxen:your_block_id
Exampleβ
This example assumes you already created an Oraxen ore block, such as amethyst_ore.
Open your dimension configβ
Go to plugins/Iris/packs/YOUR_PACK_NAME/dimensions/YOUR_DIMENSION_NAME.json.
For the default overworld pack, this is usually plugins/Iris/packs/overworld/dimensions/overworld.json.
Find the ore deposit sectionβ
Locate the deposits list inside the dimension config.
"deposits": [
{
"minHeight": 19,
"maxPerChunk": 4,
"maxHeight": 150,
"minPerChunk": 1,
"minSize": 25,
"maxSize": 25,
"palette": [{ "block": "granite" }],
"varience": 2
}
]
Add your Oraxen oreβ
Create a new deposit entry and point the palette block to your Oraxen ID.
{
"minHeight": 2,
"maxPerChunk": 2,
"maxHeight": 30,
"minPerChunk": 0,
"minSize": 3,
"maxSize": 6,
"palette": [{ "block": "oraxen:amethyst_ore" }],
"varience": 5
}
Regenerate the worldβ
Save the file, then generate fresh chunks or create a new world so Iris can place the new ore deposits.
Notesβ
World-generation changes only apply to newly generated chunks. Existing terrain will not retroactively gain your custom ores.
Iris pack paths can differ if you use a custom pack or dimension name, but the oraxen:block_id format stays the same.