AutoEMC

Automatic, accurate EMC assignment for ProjectE — built for modpacks, not just vanilla.

AutoEMC scans your loaded mods and automatically fills in ProjectE EMC values for items that don't have one, using a layered pricing system designed to make smart, sensible guesses instead of flat defaults. No more diamond-tier ores worth the same as dirt.

✨ Why AutoEMC?

Out of the box, ProjectE only knows values for items it's been explicitly told about. In a big modpack, that leaves hundreds — sometimes thousands — of items with no EMC at all. Most auto-fillers solve this by falling back to a flat, undifferentiated guess (rarity, stack size, durability), which means a modded raw diamond and a modded raw dirt clump end up worth exactly the same.

AutoEMC fixes that with a priority chain that checks the best available signal first:

Priority	Source	What it means
1	ProjectE's own value	Never overridden — hand-set and mod-provided values always win
2	Recipe-derived cost	Solved from crafting recipes, using ingredients that already have EMC
3	ProjectE Integration baselines	Curated values imported from the ProjectE Integration compat mod's own datapacks
4	Configured tier overrides	Your pack's own hand-tuned high-tier materials (Allthemodium, Vibranium, Draconic, etc.)
5	Forge tag fallback	Reads standard tags like `forge:gems/diamond` or `forge:ingots/copper` to rank material quality
6	Reverse-recipe floor	If a raw material smelts into something with a known value, it can't be priced below that
7	Rarity / stack size / durability	Last resort, only used when nothing else applies

This means an unlabeled, unconfigured modded gem will still correctly outrank an unlabeled dust or filler block — without you ever having to name the mod it came from.

🔧 Core Features

Smart fallback pricing

Reads Forge tags (forge:ores/tin, forge:storage_blocks/osmium, forge:raw_materials/...) against a configurable material/form table, so material quality (gem > ingot > storage block > dust/nugget > ore > raw) is respected automatically — no per-mod hardcoding required.

ProjectE Integration baseline import

Pulls curated values.before conversion data straight from the ProjectE Integration compat mod's own datapacks, across multiple MC versions, and uses it as a trusted baseline layer ahead of generic guessing.

Reverse-recipe value floor

If ProjectE knows a smelted/processed output is worth 800 EMC, the raw input material can no longer be left at a token value like 8 — closing a common EMC duplication path (cheap raw ore → expensive ingot → sell for profit).

Respectful item ownership

AutoEMC tracks which items it generated a value for. If another mod later provides its own real EMC value for that same item, AutoEMC detects the change and automatically yields — releasing the item and removing its own stale entry instead of fighting for control forever.

Adaptive batch sizing

Scan batch size adjusts based on actual server tick time (MSPT) instead of a fixed number, so large modpacks don't cause tick-time spikes during a scan.

Manual rescan command

/autoemc rescan

Forces a fresh scan without a server restart — handy for iterating on tag/tier tuning.

Safe by design

Never overwrites a value another mod or the server owner has explicitly set.
Bad/unusual recipes are skipped with a clear debug log line instead of silently disappearing or crashing the scan.
Config changes that affect pricing automatically trigger a rescan.

⚙️ Configuration Highlights

All of the following are configurable, no recompile required:

Material families — copper, tin, zinc, osmium, lead, silver, nickel, uranium, platinum, iridium, and more, including compatibility for mods like Mystical Agriculture and Draconium.
Form multipliers — ore / raw material / gem / ingot / dust / nugget / storage block / plate / gear / rod / wire / coin.
ProjectE Integration baselines — toggle on/off, or edit the imported id/tag table directly.
Tier overrides — your pack's own high-end progression materials (Allthemodium, Vibranium, Draconic, Unobtainium, Chaos, Infinity, etc.).
Adaptive batching — enable/disable and tune sensitivity to server tick time.

🧠 How Pricing Actually Works (Quick Version)

Does ProjectE already know this item's value? → Use it, done.
Can it be crafted from items that already have EMC? → Solve the recipe cost.
Does ProjectE Integration have a curated value for this item or its tag? → Use that.
Is it in your pack's configured high-tier list? → Use the configured value.
Does it carry a recognizable Forge tag (gem, ingot, ore, etc.)? → Estimate from material/form tier.
Does it smelt/process into something with a known value? → Floor it at that value.
Nothing else worked → Fall back to rarity, stack size, and durability.

Every step above only runs if the previous ones came up empty — so hand-set and mod-provided values are always respected first.

📋 Requirements

Minecraft Forge
ProjectE
ProjectE Integration (optional, enables curated baseline values)

💬 Feedback

Found an item that's still priced oddly? Use /autoemc rescan after adjusting the tag/tier config, and check the mod's debug log for skipped-recipe diagnostics if something seems to be missing entirely.