Project — X Love Potion Disaster 35 Save 325 Fix Exclusive

Project X: Love Potion Disaster – How to Fix the Save 325 Error in Version 3.5

If you are reading this post, you are likely one of the many fans of the cult classic indie game Project X: Love Potion Disaster. You’ve fought through waves of enemies, enjoyed the unique blend of Sonic the Hedgehog aesthetics and beat-em-up gameplay, and finally decided to update to Version 3.5.

But then, disaster struck—ironically enough.

You tried to load your old save file, only to be met with a crash, a black screen, or the infamous "Save 325" error. It is one of the most frustrating experiences for a player: losing hours of progress because a patch doesn't recognize old data. project x love potion disaster 35 save 325 fix

Don't panic! While the game is known for being a bit unstable on older hardware, this specific save file issue is usually fixable. In this guide, we will walk you through why this error happens and, more importantly, how to fix it so you can get back to the action.

Step 3 – Break the 35-Loop Manually (If the Hex Fix Isn’t Enough)

Some users report that the save loads but the dialogue loop persists. If so, after loading save 325: Project X: Love Potion Disaster – How to

1. Immediately pause the game (do not let the festival cutscene play).
2. Open the developer console (Ctrl + ` ).
3. Type: global.set_flag("LOVE_POTION_DISASTER_35", false)
4. Then type: global.set_flag("SAGE_BETRAYAL_ACKNOWLEDGED", true)
5. Finally: scene.jump_to("MOONFALL_POST_FIX")

This skips the corrupted cutscene entirely and lands you at a hidden recovery scene (“The Morning After Regret”) where you can apologize to Sage without potion mechanics active.

What You’ll Need:

• MC Command Center (for mass relationship edits)
• Sims 4 Studio (to batch-fix the broken moodlet)
• A backup (you made one, right? Right??)

Why This Fix Works for Exactly 325 Save Files

You might wonder: why is the fix so specific to save 325? Why not 324 or 326? Step 3 – Break the 35-Loop Manually (If

Because Project X’s auto-save system writes to slot 325 only when the following three conditions are met:

1. You are inside the Moonfall Festival map.
2. You have a rank 3 or higher Amorous Infusion in your inventory.
3. The internal RNG seed (calculated from system time) ends in 325 modulo 1000.

The disaster corrupts future saves but also freezes slot 325’s segment of the hard drive, preventing overwrites. It’s a bug that behaves like a protective quarantine. The developers never patched it officially, but the community’s hex fix essentially unlocks the quarantine.