RimWorld: Best ModConfig.xml for 500+ Mod Load Orders

The primary goal for mega-modded RimWorld is TPS (Ticks Per Second) Preservation. In a 500+ mod environment, every “Tick” requires the game to check thousands of lines of code—from pawn pathfinding to complex temperature simulations. This configuration focuses on stripping away “active” mod behaviors that scan the map unnecessarily, while using specific startup flags to speed up the 20-minute loading times typical of high mod counts.

Hardware Compatibility & Expectations

  • The Single-Core King: RimWorld is almost entirely single-threaded. Your CPU’s Single-Core Clock Speed and L3 Cache (like the AMD X3D series) are far more important than having 16 or 32 cores.
  • RAM Management: For 500+ mods, 32GB of RAM is the comfortable minimum. 16GB will lead to “Out of Memory” crashes during the “Late Game” when the map is full of items.
  • GPU Role: Your GPU is secondary unless you use “HD Texture” mods. RimWorld’s sprites are rendered via the CPU, so don’t expect a GPU upgrade to fix late-game lag.

File Location

The mod configuration file that stores your active list and order is located in: %USERPROFILE%\AppData\LocalLow\Ludeon Studios\RimWorld by Ludeon Studios\Config\ModConfig.xml

Best ModConfig.xml Structure for Stability

While you can edit the XML manually, for 500+ mods, you must use RimPy or RimSort (external tools) to manage the logic. However, the internal “Ordering” logic in your XML should follow the “Performance First” hierarchy:

<ModConfigData>
  <version>1.5.XXXX</version>
  <activeMods>
    <li>brrainz.harmony</li>             <li>ludeon.rimworld</li>             <li>ludeon.rimworld.ideology</li>    <li>ludeon.rimworld.biotech</li>
    <li>unlimitedhugs.hugslib</li>       <li>krkr.rocketman</li>               </activeMods>
</ModConfigData>

Pro Tip: RocketMan should always be the absolute last mod in your ModConfig.xml. It rewrites the way the engine handles “Ticking” for pawns that are not currently on screen, effectively doubling your TPS in late-game colonies.

The “Performance Trinity” (Essential Mods)

To make a 500+ mod list playable, these three mods are non-negotiable and affect how your config is handled:

Mod NameRoleImpact
Performance FishEngine OptimizerFixes inefficient code in the base game’s C# logic. (Found on GitHub).
RocketManTick ManagerThrottle AI checks for distant pawns. Increases TPS significantly.
Dubs Performance AnalyzerDiagnosticHelps you find exactly which mod is “eating” your frames in real-time.

Strategy for Managing “Tick-Hogs”

Large mod lists fail because of “Active Scanners.” To keep your colony smooth:

  • Avoid “Social” Mods: Mods that add complex “Chat” or “Relationship” logic for every pawn on the map are the #1 cause of lag.
  • Limit Map Size: Stick to 250×250. Larger maps (325+) significantly increase the pathfinding distance, which scales exponentially with the number of mods that add “New Terrains” or “Hazards.”
  • Clean the World: Periodically use the “RuntimeGC” or “RocketMan” cleanup tools to delete “World Pawns” (dead raiders/family members) that the game is still simulating in the background.

Troubleshooting & Common Fixes

  • The “Pink Square” Bug: This means you have run out of VRAM or have a mod conflict. Use “Graphics Settings+” mod to optimize texture memory.
  • Infinite Loading Screen: This is usually a “Def” error. Check Player.log in the same folder as your config. Search for the word “Error” to find the mod causing the loop.
  • Stuttering Every Second: This is often the “JobGiver” failing. A pawn is trying to do a task they can’t reach. Check your “Work” tab and unassign the pawn from that task.

Frequently Asked Questions (FAQ)

Can I add mods mid-save with a 500+ list?

It is highly dangerous. Adding “Scripted” mods (those that change AI or UI) often corrupts the save. Small “Content” mods (new furniture/clothes) are usually safe, but always backup your ModConfig.xml first.

Why use RimPy instead of the in-game manager?

The in-game manager loads the game before you change the mods. RimPy allows you to sort and fix the ModConfig.xml without opening the game, saving you hours of “Crash -> Restart” loops.

Does the “Automatic Sorting” in RimPy work?

Yes, it uses a community-driven database of 20,000+ mods to determine the safest load order. It is far more reliable than sorting manually at this scale.

Conclusion and Expected Results

By manually structuring your ModConfig.xml with Harmony at the top and RocketMan at the bottom, and by culling “Tick-Hog” mods, you are preparing your colony for long-term survival. You can expect the total removal of “Job-search” stuttering, faster startup times through optimized XML parsing, and a stable 360-900 TPS, even with 20+ colonists and dozens of animals.

Leave a Comment