Fixing Food and Hunger Conflicts Between Mods That Use AppleCore

When several mods touch hunger, you can get weird results: food restoring the wrong amount, the hunger bar jumping, or saturation behaving inconsistently. AppleCore exists to reduce these conflicts, but it cannot fix every combination.

Identify the Conflicting Mods

Check your mod list for anything that changes food, hunger, or saturation. Common culprits are food-expansion mods, hunger overhaul mods, and HUD mods. Note which ones declare AppleCore as a dependency, since those are the ones sharing AppleCore's systems.

Isolate the Problem

Make a test world and eat a single known food, like bread or cooked meat. Watch how much the hunger bar and saturation change. Then disable one hunger-related mod at a time and repeat. When the behavior becomes consistent, the last mod you disabled is likely the source of the conflict.

Reduce Overlap

If two mods both overhaul hunger, keep only one. AppleCore can bridge mods that use its API, but two full overhauls will still fight. Prefer the mod that other mods in your pack already depend on, so AppleCore can mediate between them.

Check Load Order and Dependencies

Make sure every mod that needs AppleCore actually has it installed. A missing dependency can cause hunger values to fall back to vanilla in odd ways.