⚡ AutoEMC

Automatic EMC generation for ProjectE • Forge 1.16.5

🧠 AutoEMC scans your modpack and assigns EMC to items that ProjectE does not already know.
It calculates values from recipes first, uses fallback values only when needed, and writes the results into ProjectE's custom EMC file.

   

✨ What AutoEMC Does

AutoEMC is made for large Forge 1.16.5 modpacks with lots of modded materials, machines, tools, armor, upgrades, ores, and endgame items.

Instead of giving every missing item a random value immediately, AutoEMC follows a recipe-first approach:

🟦 Existing ProjectE EMC
        ↓
🟨 Calculate EMC from loaded recipes
        ↓
🟩 Seed only true raw/source materials
        ↓
🟪 Recalculate recipe chains
        ↓
🟧 Assign fallback EMC only to unresolved items
        ↓
🔵 Improve downstream fallback recipe outputs
        ↓
✅ Write AutoEMC values to ProjectE

Example recipe chain

Raw Gem
  ↓
Gem Block
  ↓
Machine Part
  ↓
Advanced Machine Part
  ↓
Armor / Tool / Upgrade

AutoEMC repeats recipe solving because a later item may depend on an earlier item that only received EMC during the previous pass.

🛡️ Safe by Default

AutoEMC is designed to avoid destroying normal ProjectE mappings.

Important: Keep generated_entries.json. It tells AutoEMC which old entries belong to AutoEMC and can safely be recalculated.

🧩 Supported Recipe Types

AutoEMC reads standard loaded Forge/Minecraft recipe types, including:

• 🛠️ Crafting Table recipes
• 🧺 Shapeless crafting recipes
• 🔥 Smelting recipes
• 💥 Blasting recipes
• 🍖 Smoking recipes
• 🔥 Campfire cooking recipes
• ✂️ Stonecutting recipes
• ⚒️ Smithing Table recipes
• 🧩 Compatible mod recipes that expose normal Forge IRecipe data

⚒️ Smithing Table Support

For a standard Smithing Table upgrade, AutoEMC reads both required inputs:

Base armor/tool
+ Upgrade material
= Upgraded armor/tool

Example:

Netherite Chestplate
+ Upgraded Netherite Ingot
= Upgraded Netherite Chestplate

🟡 Some mods use unusual or custom Smithing Table behavior. Check autoemc-debug.log when an upgraded item does not have the expected EMC.

🧮 How EMC Is Calculated

Normal crafting recipe

8 Chroma Shards = 1 Chroma Block

When one Chroma Shard is worth 64 EMC:

8 × 64 EMC = 512 EMC

The Chroma Block should receive 512 EMC.

Smithing recipe

Base Item EMC
+ Addition Material EMC
= Upgraded Item EMC

Deep recipe chains

Raw Material
→ Component
→ Machine
→ Upgrade
→ Armor
→ Weapon

AutoEMC performs multiple recipe passes so earlier components can feed into later recipes.

🌱 Source Material Seeding

Some items are not crafted. They are source materials.

Examples include:

• ⛏️ Ores
• 💎 Raw gems
• 🧪 Dusts
• ✨ Crystals
• 🧩 Shards
• 🐉 Boss drops
• 🔩 Modded ingots
• 📦 Special components

AutoEMC gives these source items fallback EMC once, then uses that value to calculate crafted items downstream.

Raw Gem gets fallback EMC once
      ↓
Gem Block gets recipe EMC
      ↓
Machine Part gets recipe EMC
      ↓
Armor gets recipe EMC

🚫 A crafted machine part should not normally be seeded. It should get EMC from its recipe whenever possible.

🧯 Final Fallback EMC

Some items cannot be calculated from readable recipes.

This can happen when:

• ❌ The item has no recipe
• ❌ The recipe is hidden or malformed
• ❌ A required ingredient has no EMC
• ❌ A mod uses a custom machine recipe
• ❌ The recipe does not expose ingredients through Forge
• ❌ The item is loot-only, quest-only, or reward-only
• ❌ The item depends on special NBT, fluids, energy, or multiblock processing

AutoEMC gives those items a final fallback EMC value so they are not left blank.

After fallback values are created, AutoEMC safely checks recipe chains again:

Fallback Machine Part
        ↓
Advanced Machine Part
        ↓
Armor
        ↓
Weapon

This helps downstream items improve from the value of their actual components.

👑 Endgame EMC Tiers

AutoEMC supports material tiers for powerful late-game content.

Priority order:

Overpowered
   ↓
Very Strong
   ↓
Strong
   ↓
Normal fallback

⚠️ Powerful materials can create very large EMC values because their recipe cost can travel through long machine and upgrade chains. This is expected.

🔁 Recipe Loop Protection

Some modpacks have reversible conversion recipes:

Item A → Item B
Item B → Item A

Without protection, those loops could increase EMC forever.

AutoEMC protects against this by:

• ✅ Only allowing generated values to increase when appropriate
• ✅ Using snapshot-based recipe passes
• ✅ Stopping when a complete pass makes no improvements
• ✅ Respecting the configured maximum recipe-pass limit
• ✅ Blocking cyclic fallback chains from feeding each other forever

🎨 Colored In-Game Progress Messages

AutoEMC shows clear phase-based chat messages while it works.

[AutoEMC] START ▶ Starting AutoEMC scan...

[AutoEMC] 1/6 CHECK » Checking existing ProjectE EMC
[AutoEMC] 2/6 RECIPES » Reading loaded recipes
[AutoEMC] 3/6 SOURCES » Finding source materials
[AutoEMC] 4/6 CHAIN » Solving recipes using source materials
[AutoEMC] 5/6 FALLBACK » Assigning final fallback EMC
[AutoEMC] 6/6 UPGRADE » Improving fallback recipe outputs

[AutoEMC] DONE ✓ Scan completed

📋 Dedicated AutoEMC Debug Log

Minecraft's latest.log can be extremely crowded. AutoEMC writes its own clean debug log.

config/autoemc/autoemc-debug.log

The previous AutoEMC session is saved here:

config/autoemc/autoemc-debug.previous.log

The dedicated log contains only AutoEMC information:

• 📌 Scan start reason
• 📊 Scan progress
• 🧾 Recipe pass results
• 🌱 Source material seeding
• 🧯 Fallback assignment
• 🔁 Post-fallback recipe upgrades
• ⚠️ Warnings
• ❌ Errors with full stack traces
• ⚒️ Smithing Table recipe details
• 💰 Smithing Table calculated values

Smithing debug example

[SMITHING-RECIPE]
output=examplemod:upgraded_chestplate
inputs=[minecraft:netherite_chestplate] + [examplemod:upgrade_ingot]

[SMITHING-SOLVED]
stage=recipe solve
output=examplemod:upgraded_chestplate
emc=180288

📤 When reporting an AutoEMC problem, upload config/autoemc/autoemc-debug.log instead of the full Minecraft latest.log.

📁 Important Files

🚀 Installation

1. Install required mods

Your modpack needs:

Minecraft Forge 1.16.5
ProjectE
AutoEMC

Place the compiled AutoEMC .jar in your instance's mods folder.

CurseForge\minecraft\Instances\Your Modpack\mods\

2. Start Minecraft

Launch the modpack normally.

AutoEMC scans once the server/world is available. Watch the colored chat messages or open:

config/autoemc/autoemc-debug.log

Wait until you see:

[AutoEMC] DONE ✓

⏳ Do not close Minecraft during the first large scan.

3. Restart Minecraft

After values are written, restart Minecraft.

Close Minecraft
   ↓
Start Minecraft again
   ↓
Check EMC in JEI or ProjectE

A restart is preferred because ProjectE loads EMC mappings during startup.

🔄 When AutoEMC Rescans

When nothing relevant changed, AutoEMC skips the long scan:

[AutoEMC] SKIP — item registry and AutoEMC settings are unchanged; prior scan is complete.

That is normal.

AutoEMC rescans when important changes happen:

• ➕ You add a mod
• ➖ You remove a mod
• ⚙️ You change AutoEMC settings
• 🆕 You update the solver version
• 🧩 Registered items change
• 📜 Loaded recipes change
• 🗑️ You delete the saved scan state

Removing a mod can change many recipe paths:

Removed Mod Ingredient
        ↓
Changed Component Recipe
        ↓
Changed Machine Recipe
        ↓
Changed Armor / Tool Recipe

A full rescan prevents stale EMC values from remaining after the recipe graph changes.

🔧 How to Force a New Scan

Delete only this file:

config/autoemc/recipe_solve_state.json

Then restart Minecraft.

✅ This is the safest way to force another calculation pass.

⚠️ How to Completely Reset AutoEMC

Use this only when you want AutoEMC to rebuild all generated values from scratch.

Step 1 — Back up your files

Back up:

config/ProjectE/custom_emc.json
config/autoemc/generated_entries.json

Step 2 — Remove AutoEMC state files

config/ProjectE/custom_emc.json
config/autoemc/generated_entries.json
config/autoemc/recipe_solve_state.json
config/autoemc/known_items.json

Step 3 — Launch Minecraft

Start the game and wait for the full scan to finish.

🚨 Warning: Do not delete custom_emc.json without a backup if it contains manual EMC values you want to preserve.

❓ Troubleshooting

<details> <summary>Why is AutoEMC scanning again?</summary>

AutoEMC detected a registry, recipe, mod, setting, or version change.

Check the first lines of:

config/autoemc/autoemc-debug.log

They explain why the scan started.

</details>

<details> <summary>Why does recipe progress restart on every pass?</summary>

The progress counter tracks recipes in the current pass, not missing items across the whole modpack.

Pass 1: Raw Gem → Gem Block
Pass 2: Gem Block → Machine Part
Pass 3: Machine Part → Armor

Each pass needs to review the recipe list again because more ingredients become usable over time.

</details>

<details> <summary>Why did an item receive fallback EMC?</summary>

The item could not be calculated from a supported readable recipe.

Common causes:

• No recipe
• Hidden or broken recipe
• Custom machine recipe
• Unknown ingredient EMC
• Recipe data unavailable through Forge
• Loot-only or quest-only item

Check the dedicated debug log.

</details>

<details> <summary>Why did my upgraded armor or tool not get the expected value?</summary>

Check for these lines in autoemc-debug.log:

[SMITHING-RECIPE]
[SMITHING-SOLVED]
[SMITHING-FALLBACK]

A normal Smithing Table upgrade should follow:

Base Item EMC + Addition Material EMC = Upgraded Item EMC

Custom modded Smithing recipes may need manual verification.

</details>

<details> <summary>Why is an EMC value extremely high?</summary>

High-tier materials and long recipe chains can produce very large values.

This is common for:

• Draconic Evolution items
• Allthemodium / Vibranium / Unobtainium items
• Chaos / Infinity / Creative-tier items
• Large machine chains
• Late-game storage and upgrade components

</details>

<details> <summary>Why did AutoEMC not change an item?</summary>

AutoEMC protects normal ProjectE values and manual custom EMC values.

It normally updates only entries it previously created and recorded in:

config/autoemc/generated_entries.json

</details>

⚠️ Known Limitations

AutoEMC cannot always calculate every modded item perfectly.

Examples:

• Custom machine recipes that do not use Forge IRecipe
• Dynamic runtime recipes
• Hidden recipes with unreadable ingredients
• Malformed recipe data
• Loot-table-only items
• Quest reward items
• NBT-dependent crafting costs
• Fluid, energy, multiblock, or custom processing costs
• Non-standard Smithing Table recipes

Those items can receive fallback EMC and may need manual balancing in a highly customized modpack.

🧪 Recommended Modpack Author Workflow

1. Install ProjectE + AutoEMC
        ↓
2. Back up custom_emc.json
        ↓
3. Launch the modpack
        ↓
4. Wait for AutoEMC DONE ✓
        ↓
5. Restart Minecraft
        ↓
6. Test key progression items
        ↓
7. Check autoemc-debug.log for warnings
        ↓
8. Add manual EMC only where special balancing is needed
        ↓
9. Keep generated_entries.json for future automatic updates

Test at least:

• ⛏️ Ores and raw materials
• 🧱 Ingots and blocks
• ⚙️ Components and machines
• 🛡️ Armor and tools
• ⚒️ Smithing upgrades
• 🐉 Endgame items
• 💎 High-tier materials

🐛 Reporting a Bug

Include:

Minecraft version:
Forge version:
ProjectE version:
AutoEMC version:

Wrong item ID:
Expected EMC behavior:
Actual EMC value:

Attached file:
config/autoemc/autoemc-debug.log

For a Smithing problem, also include:

Base item:
Upgrade material:
Upgraded output:
JEI recipe screenshot or exact recipe:

### ⚡ AutoEMC — Recipe-first EMC generation for large ProjectE modpacks