Tested with: KSA Version 2026.10.19.5638
There are two directories that matter: where the game is installed, and where it keeps your stuff.
There is no fixed path. The installer asks where to put the game, so it depends on what was chosen at install time. Paths you will see quoted around the place include:
C:\Program Files\Kitten Space Agency\C:\Users\<You>\AppData\Local\Programs\Kitten Space Agency\C:\Users\<You>\Documents\Kitten Space Agency\All three are real, none of them is the path, and guides that state one as fact will send somebody to the wrong folder. If you are not sure which you have, the RGA launcher shows it, or you can right click your shortcut and open the file location.
Never hardcode the install path in a mod. For anything under the game's own folder, work relative to the assembly. For player data, use
KSA.Constants.DocumentsFolderPath. See Game Documents Directory.
Kitten Space Agency\
├── KSA.exe
├── KSA.dll the game code
├── Brutal.*.dll the engine, split across ~30 assemblies
├── Planet.Core.dll
├── Planet.Render.Core.dll
└── Content\
├── manifest.toml which mods ship enabled by default
├── Core\ all of the game's actual content
├── Shaders\
├── Fonts\
├── Sample\
├── ThermoToolkit\
└── Versions\ one JSON per build ever released
KSA.dll is the one you decompile and the one you reference from a code mod. Brutal.ImGui.Abstractions.dll is the one you need for GUI work.
This is where all the game data lives. It has grown a lot, to around forty XML files plus several subdirectories.
Systems
| File | What |
|---|---|
SolSystem.xml |
The full solar system |
SolSystemDense.xml |
Solar system with more bodies |
EarthSystem.xml |
Earth and its neighbourhood |
EarthOnly.xml |
Just Earth. The smallest and best file to read first |
SolSystemInterstellar.xml |
The solar system plus the nearby stars, at their real distances |
EarthOnlyInterstellar.xml |
Earth plus the nearby stars. The smallest multi-star example |
Celestial and world data
| File | What |
|---|---|
Astronomicals.xml |
Every celestial body: orbits, terrain, atmospheres, oceans, clouds |
InterstellarAstronomicals.xml |
Nearby stars, barycenters and their planets. See Multiple Star Systems |
Situations.xml |
Starting orbits and locations, referenced by vehicles |
MeshCollections\ |
Planet LOD mesh definitions |
TextureCollections\ |
Random heightmap collections |
GroundClutter\ |
Grass, rocks and trees scattered on terrain |
Parts. Parts are no longer in one file. Each pack has an *Assets.xml (meshes, materials, models) and an *GameData.xml (the functional side: tanks, engines, connectors):
PartAssets.xml PartGameData.xml
CoreCommandAAssets.xml CoreCommandAGameData.xml
CoreCouplingAAssets.xml CoreCouplingAGameData.xml
CoreElectricalAAssets.xml CoreElectricalAGameData.xml
CoreFairingAAssets.xml CoreFairingAGameData.xml
CoreFuelTankAAssets.xml CoreFuelTankAGameData.xml
CoreFuelTankBAssets.xml CoreFuelTankBGameData.xml
CoreIVAPropAAssets.xml CoreIVASpaceAGameData.xml
CoreIVASpaceAAssets.xml CoreLandingAGameData.xml
CoreLandingAAssets.xml CorePassageAGameData.xml
CorePassageAAssets.xml CorePropulsionAGameData.xml
CorePropulsionAAssets.xml CorePropulsionBGameData.xml
CorePropulsionBAssets.xml CorePropulsionCGameData.xml
CorePropulsionCAssets.xml CoreServiceModuleAGameData.xml
CoreServiceModuleAAssets.xml CoreStructuralAGameData.xml
CoreStructuralAAssets.xml CoreUtilityAGameData.xml
CoreUtilityAAssets.xml CoreFuelPortGameData.xml
CoreEditorTagsGameData.xml
Physics and chemistry
| File | What |
|---|---|
Reactions.xml |
Combustion reactions engines refer to (Hydrolox, MMH_NTO, ...) |
Volatiles.xml |
Substance definitions |
SolidPropellants.xml |
Solid motor propellants |
GrainGeometries.xml |
Solid motor grain shapes |
Materials.xml |
Structural materials |
Presentation
| File | What |
|---|---|
DefaultAssets.xml |
Shaders, shared textures, meshes |
Sounds.xml |
All sound and music definitions |
Gauges.xml |
Cockpit gauge canvases |
CharacterAssets.xml |
Kitten models, fur, animations |
ExhaustAssets.xml, PlumeTrailAssets.xml, ParticleEmitterAssets.xml, DistantGlintAssets.xml |
VFX |
Languages.xml |
Localisation |
Everything else
| Path | What |
|---|---|
Meshes\ |
GLB models, now shipped as one *_MeshAtlas.glb per part pack |
Textures\ |
KTX2 textures |
Sounds\, Music\ |
Audio files |
Characters\, Animations\ |
Kitten assets |
defaultvehicles\ |
Stock craft, one folder each |
*.bin |
Star field binaries |
mod.toml |
Core's own mod manifest, the best worked example there is |
C:\Users\<You>\Documents\My Games\Kitten Space Agency\
On Linux the same folder sits under your home directory rather than Documents, following whatever your desktop reports as the personal folder. Ask the game rather than guessing, using the properties in the table below.
This is where everything you generate lives. Mods read and write here, and it is the path to use for anything player-specific.
| Path | What | Get it in code from |
|---|---|---|
logs\ |
KittenSpaceAgency.log |
Constants.LogsFolderPath |
crashdumps\ |
Crash dumps | Constants.CrashDumpFolderPath |
saves\ |
Save games, one folder each | GameSaves.SaveFolderPath |
vehicles\ |
Craft saved from the editor | VehicleSaves.SaveFolderPath |
HUDLayouts\ |
Saved HUD arrangements | LayoutSaves.SaveFolderPath |
mods\ |
Installed mods, one folder each | ModLibrary.LocalModsFolderPath |
manifest.toml |
Which mods are enabled | ModLibrary.LocalManifestPath |
settings.toml |
Game settings | private |
imports\, exports\ |
Import/export staging | private |
A mod manager can point the game at a different documents folder to create an isolated instance. That is why you should always ask the game where these are rather than building the path yourself. See Game Documents Directory.
Note the casing: logs, saves, crashdumps are lowercase; HUDLayouts is not. It does not matter on Windows but it will on Linux.