The Three Steps That Prevent Most Problems
Each of these three steps addresses a specific failure mode. Testing in a new save protects your existing worlds from untested mod behaviour. Removing conflicting mods eliminates the most common source of runtime crashes. Matching the Minecraft version closes the compatibility gap that causes silent errors during world loading.
Mod Compatibility at a Glance
Not all mods conflict with Jenny Mod . The table below shows which companion mod types are safe and which carry risk, helping you build a stable mod profile before your first session.
| Mod Type | Risk Level | Recommendation |
|---|---|---|
| Other NPC / relationship mods | High Risk | Remove before running Jenny Mod |
| World generation overhauls | Caution | Test separately in a new world first |
| Entity AI replacements | High Risk | Disable — entity conflicts crash on load |
| OptiFine (matching version) | Safe | Compatible with most Jenny Mod builds |
| Inventory / UI mods | Safe | Cosmetic mods rarely cause conflicts |
| Performance optimisers | Safe | Generally compatible — test once to confirm |
What to Do After a Crash
Even with proper preparation, unexpected crashes can occur. Acting correctly in the minutes after a crash determines whether your world recovers cleanly.
Opening a corrupted save a second time can compound the damage. Read the crash log in .minecraft/crash-reports before doing anything else.
Recovery Steps
Open the crash log and identify the failing mod or class. If the world fails to load, restore from your most recent backup. Remove the identified mod, test in a clean world, then gradually restore your setup one mod at a time.
Copy your .minecraft/saves folder before every session. A dated backup folder takes two minutes to create and makes full recovery possible after any crash.