Custom Raw Ores

Custom Raw Ores

简体中文 | English

/ffd_rawore helps modpack makers generate raw-ore JSON definitions for other mods' ores instead of writing every definition by hand.

It checks the currently loaded ore dictionary, ore drops, and processing outputs. It does not search the world for ore veins or give items to your inventory.

Usage

Requires command permission level 2.

Command	Action
/ffd_rawore scan	Preview the default scope, primarily ores with ingot outputs; writes no files
/ffd_rawore scan all	Preview an expanded scope that also includes gems, dusts, crystals, and nuggets; writes no files
/ffd_rawore generate	Rescan the default scope and write definitions, review drafts, and a report
/ffd_rawore generate all	Rescan the expanded scope and write the corresponding files

all expands the output categories. It does not disable drop checks, force generation, or support every possible processing chain. Default mode also checks eligible Tinkers' Construct paths where an ore melts into a fluid that can be cast directly into an ingot using an ingot cast. Its detection path is therefore not identical to all.

Recommended workflow

1. Back up your configuration and preferably work in a test copy of your modpack.
2. Run /ffd_rawore scan and read the candidate counts and skip reasons.
3. If the scope looks right, run /ffd_rawore generate.
4. If you also want gems, dusts, or the other supported output categories, review scan all before using generate all.
5. Check the generated definitions, drafts, and report. The generator is an aid, not a substitute for reviewing ores with special mechanics.
6. Fully restart the game or server, then check the new raw ores, storage blocks, mining drops, and processing results.

You can run generate without first running scan. Every generation run performs a fresh scan.

Where are the files saved?

Path	Contents
config/farmers_future_delight/custom_raw_ores/	Active JSON definitions; valid entries are registered on restart
config/farmers_future_delight/custom_raw_ores/_example.json	An automatically created format example; it is not loaded as an active definition
config/farmers_future_delight/raw_ore_generation/drafts/	Drafts requiring review, usually named _<material>.json
config/farmers_future_delight/raw_ore_generation/reports/	Reports showing generated entries, existing definitions, review candidates, and skipped content

Only sufficiently clear matches are written to the active directory. Candidates with a plausible output but incomplete information may receive a draft. Ambiguous or unsuitable candidates are recorded in the report without an active definition.

Drafts do not activate automatically. After reviewing and correcting one, move it into the active directory and give it a .json filename that does not begin with an underscore. Removing the underscore while leaving the file in drafts/ is not enough.

The command does not overwrite existing active definitions or drafts. To change an existing definition, back it up and edit it manually.

Why were some ores skipped?

Common reasons include:

• No recognizable ore... ore-dictionary entry, or no valid ore block associated with it.
• The material is already supported by the mod or has a custom definition.
• Another mod already provides a raw_<material> item, so a duplicate is avoided.
• Normal mining drops are unstable, have multiple possible outputs, or require additional processing.
• Different sources for the same material lead to different processing outputs and cannot be safely combined.
• Default mode found a non-ingot output; check whether scan all is appropriate.
• The ore belongs to the excluded ancient-debris/netherite-scrap chain.

Detection uses data registered by the mods, not just names that look like ores or metals. Read the report rather than enabling every draft blindly.

No new items after generation?

Check that you fully restarted, the files are in the active directory, their names do not start with an underscore, and the JSON is valid. Disabling raw ores globally or disabling the particular material also prevents that content from being enabled.

This command does not generate custom deepslate-ore JSON.

---

Back to Command Overview