Furia Memory

Furia Memory 1.2.0 (NeoForge) – Compatibility Update

🔧 Compatibility

• Better compatibility with other optimization mods and large modpacks. Furia Memory adapts to what is installed: when another mod already covers a module's job, that module turns itself off automatically, so nothing is duplicated. Set autoYield = false under [compat] to disable this (restart required).
• Failsafe. If a module ever hits an error, it switches itself off for the session, the game keeps running, and /furiamemory report shows [ERROR] with the reason.
• Safer startup. If something Furia Memory hooks into does not match what it expects (another Minecraft version, or another mod changed it), that part is skipped with a message in the log instead of stopping the game from launching.

✅ Improvements

• Fixed bugs after using the /furiamemory clean commands. Cleaning no longer revives modules that you turned off or that another mod already covers, and the numbers it reports are now accurate.
• More accurate auto-off. Statistics and hit-rate checks now count correctly, so a module that doesn't pay off switches itself off when it should.
• maxInternedStringLength now applies to every pool, and options read very early at startup follow your config from the first launch.
• /furiamemory report shows clearer states for every module ([ACTIVE], [AUTO-OFF], [PARTNER], [OFF], [N/A], [ERROR]), plus JVM and heap information.

💡 Recommended JVM arguments (optional)

For the G1 collector (Java's default), these let the JVM hand unused memory back to your system while the game is idle:

-XX:G1PeriodicGCInterval=60000 -XX:MaxHeapFreeRatio=50

• Add them to your launcher's Java arguments (on a server, user_jvm_args.txt).
• Do not set -Xms equal to -Xmx, or the heap cannot shrink.
• They do not reduce the data Minecraft keeps in memory, and they do nothing while you play.

📝 Notes

• Furia Memory never cleans anything on its own: cleanup is manual, with the /furiamemory clean commands.
• Real RAM savings depend on your modpack.