Save file

Basics Menus Game Creation Gameplay Pawns Plants Resources Gear Mods Basics Menu Controls User Interface Save File Modding Version history

---

Save files are the files that store a player's progress in RimWorld. The game can be saved in two ways: the player saving a game manually, or the game saving automatically - being an autosave. When saving the game manually, the player can choose a custom name for the save. When the game autosaves, the save names are automatically labeled as "Autosave-#", with the number incrementing by one for every autosave stored.

Saving manually also allows the choice of overwriting other saves. To the very left of each save's "load" button, three pieces of information are stored: the corresponding date, time and version. If a save's version is different from the game's current version, that info will be displayed in yellow, rather than the standard grey (as seen in the image).

Clicking the red "X" to the right of the save's load button will delete the save, though the game will ask the player if they want to continue with their deletion every time an X is clicked.

Save file contents

RimWorld's save files are written in XML and contain all the information about the state of the game. They are stored with the file extension .rws, and can be read with any XML reader or Notepad. The contents of a save are heavily dependent on the version of the game that was running at the very moment of the save, this means that even though saves of a different version may still work, some gameplay issues may occur.

DLC and mods are also integrated into save files, meaning that problems can occur when loading a save without the same content enabled as was originally part of that save. If there is any difference between what is enabled and what's contained in a save file, the game will notify the player of this.

World data is saved into the map file, to allow multiple saves on the same world without confusion.

Notable sections

• Resources - Contains information about each of the available resources in the game.
• ProjectList - Contains the state of each of the research projects available in the game. The research completes when Progress is more than (or equal) to TotalCost.
• ThingReservation - Details what a Pawn (person/animal) is doing/going to do.
• Thing - information about a person/animal.

Important elements

<li>

You will notice that "li" appears a lot in the save file. As in HTML, this simply stands for a "list item". It can have many different meanings depending on what the element surrounding it is.

<def>

"def" contains a single string that refers to some item or property. For example, an element needs > li.Need_Food > def (in CSS selector syntax) has the value "Food", explaining that the data is about need for food.

A donkey, on the other hand, starts with a def containing "Donkey" in the section that describes pawns.

<id>

This contains a string of the unique identifier of a thing. It might be referred to several times in the file. Be sure to change it if you duplicate a thing.

<ID> and <UniqueID> serve the same purpose, but they are numbers.

The names are generally quite descriptive, so it shouldn't be hard to figure out the purpose of things and how to change them. The class attribute should be familiar to those who know HTML. As with always, it is harder to figure out how to create things from thin air than to change existing things.

Overall structure

Each section is book-ended by an opening tag <tag> and closing tag </tag> respectively. For brevity's sake, only the opening tag is shown and closing tags are omitted with the exception of </savegame>.

Note: This structure was taken from 1.2 save files.

<?xml version="1.0" encoding="utf-8" ?>
<savegame>
   <meta>
      <gameVersion>
      <modIds>
      <modNames>
   <game>
      <currentMapIndex>
      <info>
      <rules>
      <scenario>
      <tickManager>
      <playSettings>
      <storyWatcher>
      <gameEnder />
      <letterStack>
      <researchManager>
      <storyteller>
      <history>
      <taleManager>
      <playLog>
      <battleLog>
      <outfitDatabase>
      <drugPolicyDatabase>
      <foodRestrictionDatabase>
      <tutor>
      <dataNotifier>
      <questManager>
      <components>
      <world>
      <maps>
      <cameraMap>
</savegame>

The vast majority of the data in a save file is contained within the <world> and <maps> sections. Within the <maps> section, each colony is stored as a list item <li> if multiple colonies were present at any point during the save. In turn, within each colony, the <things> section stores items, chunks, filth, plants, buildings and pawns. Each and every instance of any type is stored as an individual <thing> with its own respective class.

<savegame>
   <meta>
   <game>
      <world>
         <info>
         <grid>
         <factionManager>
         <worldPawns>
         <worldObjects>
         <gameConditionManager>
         <storyState>
         <features>
         <components>
      <maps>
         <li>
            <uniqueID>
            <mapInfo>
            <weatherManager>
            <reservationManager>
            <physicalInteractionReservationManager>
            <designationManager>
            <pawnDestinationReservationManager>
            <lordManager>
            <visitorManager>
            <gameConditionManager>
            <fogGrid>
            <roofGrid>
            <terrainGrid>
            <zoneManager>
            <temperatureCache>
            <snowGrid>
            <areaManager>
            <lordsStarter>
            <attackTargetReservationManager>
            <deepResourceGrid>
            <weatherDecider>
            <damageWatcher>
            <rememberedCameraPos>
            <mineStrikeManager>
            <retainedCaravanData>
            <storyState>
            <wildPlantSpawner>
            <temporaryThingDrawer>
            <components>
            <compressedThingMapDeflate>
            <things>
</savegame>

Save file locations

Windows version

The Save files are stored in users AppData folders: %USERPROFILE%\Appdata\LocalLow\Ludeon Studios\RimWorld by Ludeon Studios\Saves

Shortcut:

1. Windows+R -> the Run dialog will appear.
2. Type appdata and press enter.
3. Go to LocalLow/Ludeon Studios.

Note:

• As of at least Alpha 16, the directory Steam Cloud will create is %USERPROFILE%\Appdata\LocalLow\Ludeon Studios\RimWorld which is not detected by the game. Unknown if this a bug at this point.
• By default, %USERPROFILE% is the same as C:\Users\[username]. It is possible to be moved.

---

Linux version

The Save files are stored in: ~/.config/unity3d/Ludeon Studios/RimWorld by Ludeon Studios/Saves/

At least as of Alpha 17b, Steam Cloud synchronization is working as intended on Linux, meaning that save files are automatically updated across different Steam installations on multiple devices.

---

macOS version

Your Rimworld settings folder is ~/Library/Application Support/RimWorld

To see your save games with Finder, open a new shell and enter:

open "~/Library/Application Support/RimWorld/Saves/" (may also be in cache)

This also applies to Alpha 12d.

As of at least Alpha 16, Steam Cloud uses the directory ~/Library/Application Support/RimWorld By Ludeon Studios/Saves, whereas the game uses open ~/Library/Application Support/RimWorld/Saves/, therefore meaning the save game sync is currently not working.

• 

  Save file for Mac using EasyFind

• 

  Save file for Mac using EasyFind reveal in Finder

Editing saves

See also: Permadeath save conversion guide, Dev mode renabling, and Fluid ideoligion save conversion guide

Save editing can be a useful way to tweak the current game state. It can be used to do various things such as adding or remove currently active events, pawn traits and passions, and modifying skills and statistics.

Note: Incorrectly editing the save might can have unwanted consequences that might be irreversible if the original file is lost, up to and including the total loss of the save. It is highly recommended that you make a copy of your save file before editing it or save the new one as a different save file.

Stopping an event

Example of removing the Toxic Fallout event from the game: open the save file with Wordpad, press Ctrl+F, or ⌘+F on macOS and search for 'toxicfallout'. You will see a list of <li>events</li>. See where in the list 'ToxicFallout' is. Below that list is a list of <li>numbers</li>. Change the number to '0' between <li></li> which is in the same position in the list as 'ToxicFallout' was in the previous list (bottom one for me). It will now never occur again.

Also if currently, you would be experiencing this Toxic Fallout and would want to remove it not only for the future but also immediately, do the following: Ctrl+F in the save file and search for 'activeconditions'. You will find: <activeConditions><li>some text regarding the Toxic Fallout</li></activeConditions>. Change this to only 1 line with just this: <activeConditions />. So you would have this.

Modifying a pawn

Pawn editing is another useful ability of editing save files. This can be used for a range of ways, from small modifications to existing pawns, recreating specific characters, or simply creating godlike pawns. To do this, open the save file, and move about 1/3 down the text file. Click on a line, and then use the Ctrl+F function to find the name of the pawn you wish to edit. Keep going down until you find the pawn save location, which will have three lines: one for last name, one for nickname, and one for first name.

From here, scroll down to find the part you wish to edit. You can remove health conditions by editing the hediffs for injuries (i.e. deleting permanent wounds) or add skills and passions.

Moving/Removing a steam geyser

A steam geyser can usually be removed using the Destroy function in Dev Mode, but in older versions or modded saves this might not be possible. Instead, the geyser can be manually deleted from the save file.

To edit a geyser: open the save file with Wordpad/Notepad, press Ctrl+F, or ⌘+F on macOS and search for 'geyser'. The geyser should be represented as a <thing Class="Building_SteamGeyser">. To move the geyser to a new location, edit the coordinates stored in the <pos> line. To remove the geyser entirely, select the lines from <thing> to </thing>.