Core Keeper Mod Conflict Triage

#Direct Answer

When a Core Keeper modded save feels wrong, do not assume every guide is broken. First isolate what changed. A mod conflict is only useful to diagnose when you can name the rule, system, or behavior that changed.

Use this order:

1. back up the save
2. write down the mod list or changed setting
3. compare the problem against the vanilla expectation
4. test one changed variable
5. decide whether the normal guide still applies

If you cannot name the changed rule, use the Core Keeper Mods Baseline Guide first.

#Separate Mod Problems From Normal Problems

Many modded-save issues are still ordinary guide issues.

The mod is not always the cause. Sometimes it only makes a normal weakness easier to notice.

#What counts as a real conflict

A mod conflict usually shows up when:

• one mechanic changes in a repeatable way after the mod is enabled
• the same save behaves differently on vanilla and modded runs
• the issue disappears when the mod is removed
• the mod changes a rule the normal guide depends on

If the problem stays the same in both states, the issue is probably not the mod. It may be the route, build, or patch timing.

#Test One Variable

Do not change gear, food, mods, route, and difficulty at the same time. That creates a result you cannot read.

A clean test looks like this:

1. keep the same route
2. keep the same build
3. change one mod or setting
4. run one short repeatable test
5. write down the result

If the result changes, the mod may matter. If it does not, the issue probably belongs to a normal guide page.

#Record the change

When a mod test does change the result, write down:

1. the mod name or setting
2. the exact behavior that changed
3. whether vanilla still matches the normal guide
4. which page should carry the mod note

That record matters more than the first failed run. It keeps the next review from becoming another guess.

#When A Mod Note Belongs On A Guide

A mod note is useful when it changes the page's main advice.

Add or look for a mod note when the mod changes:

• damage numbers
• enemy pressure
• drop rates
• biome access
• crafting requirements
• movement or inventory comfort
• progression order

If the mod only changes convenience, the normal page often still works. You may need a comfort adjustment, not a new route.

Concrete examples:

• a mod that changes ore density can change which mining route is worth the trip
• a mod that changes stack size can change how safe a money run feels
• a cosmetic mod usually should not change the main advice at all
• a difficulty mod can move the boss, food, and build pages at the same time

#Use Updates Separately

Patch changes and mod conflicts can overlap, but they are not the same problem.

If the save changed after a game update, open Updates or the Update Recheck tool first. If the save only changed after adding or removing a mod, stay on the mods baseline path.

#Common mistakes

1. Blaming the mod before testing vanilla.
2. Retesting with too many variables changed at once.
3. Writing a mod note that does not change the page's advice.
4. Treating a convenience mod like a combat or route mod.
5. Leaving the conflict unresolved and hoping the next patch hides it.

#Next Step

Open the Mods Baseline Guide when the changed rule is unclear. Open Update Recheck if the problem started after a patch. Open the relevant build page only after the mod or update question is separated from ordinary setup weakness.