Tested with: KSA Version 2026.10.19.5638
A system file defines a star system that shows up in the picker when you start the game. One file per system, .xml, named after the system.
Put the file in your mod folder and list it under systems in your mod.toml:
systems = [ "MySystem.xml" ]
Miss that line out and your system will not appear, no matter how correct the XML is. This is the single most common reason a custom system does not show up.
<?xml version="1.0" encoding="utf-8"?>
<System Id="KerbolOnly">
<DisplayName Value="KSP System - Kerbin+Mun+Minmus Only"/>
<GalacticPlane>
<RightAscension Degrees="192.86" />
<Declination Degrees="27.13" />
</GalacticPlane>
<!-- generated and cached using 'textures summarize' in game, used for VRAM estimates -->
<VesselTextures Size="184 MB">
<Texture Width="4096" Height="4096" Count="12" Size="181 MB"/>
<Texture Width="512" Height="512" Count="3" Size="3 MB"/>
</VesselTextures>
<TerrainTextures Size="0.6 GB">
<Texture Width="16384" Height="8192" Count="2" Size="171 MB"/>
<Texture Width="8192" Height="4096" Count="2" Size="256 MB"/>
</TerrainTextures>
<UnscaledTextures Size="8 MB">
<Texture Width="1024" Height="1024" Count="1" Size="4 MB"/>
</UnscaledTextures>
<LoadFromLibrary Id="Kerbol"/>
<LoadFromLibrary Id="Kerbin" Parent="Kerbol" HomeBody="true"/>
<LoadFromLibrary Id="Mun" Parent="Kerbin"/>
<LoadFromLibrary Id="Minmus" Parent="Kerbin"/>
<LoadVehicleFromLibrary Id="Rocket" Parent="Kerbin">
<SituationRef InstanceOf="RocketStartingSituation"/>
</LoadVehicleFromLibrary>
</System>
Id attribute<System Id="KerbolOnly"> is the internal name. It does not appear in the system list, but it is what the loading screen shows ("Loading KerbolOnly") and what a vehicle's meta.toml refers to under systems.
If two systems share an Id, the game loads whichever file name comes first alphabetically, regardless of which one you picked.
<DisplayName><DisplayName Value="Earth Only" />
The text shown in the system picker. Anything goes, and duplicates are fine. This is purely cosmetic.
If you want two bodies to have the same visible name, adding a trailing space to one works. Custom fonts could in principle give you invisible or lookalike characters, but nobody has documented how yet.
<GalacticPlane>Orients the background star field relative to your system.
<GalacticPlane>
<RightAscension Degrees="192.86" />
<Declination Degrees="27.13" />
</GalacticPlane>
Optional. Leave it out and you get the default orientation. The values above are the real galactic north pole, which is what stock uses.
<VesselTextures>, <TerrainTextures> and <UnscaledTextures> are cached VRAM estimates, used to warn players before they pick a system their card cannot hold.
<TerrainTextures Size="0.6 GB">
<Texture Width="16384" Height="8192" Count="2" Size="171 MB" />
</TerrainTextures>
You do not write these by hand. Run the textures summarize command in the in-game console once your system loads and paste the result. They only affect the estimate shown to the player, so a rough or missing block will not stop anything working. It will just mis-report.
<LoadFromLibrary Id="Sol"/>
<LoadFromLibrary Id="Earth" Parent="Sol" HomeBody="true"/>
<LoadFromLibrary Id="Luna" Parent="Earth"/>
Each one pulls a body defined in an <Assets> file into this system.
Parent. The first <StellarBody> listed becomes the system's primary star.Parent, except other roots: extra stars and barycenters placed at a fixed <Position> also have no Parent. See Multiple Star Systems.Parent. The hierarchy here wins, even if the body's own definition says otherwise. That is deliberate: it lets you reuse the same body definition across systems with different arrangements.HomeBody="true" marks the body the game treats as home. Set it on one body. If you set it on none, the game picks the first body that is not a star or barycenter and logs "HomeBody not Defined".Bodies can also be written inline instead of referenced, using the same syntax as in <Assets>: <StellarBody>, <AtmosphericBody>, <PlanetaryBody>, <TerrestrialBody>, <MinorBody>, <Asteroid>, <Comet>, <PeriodicComet>, <InterstellarComet>, <Barycenter>. Definitions written inline are local to this system and other files cannot reference them.
<LoadVehicleFromLibrary Id="Gemini7" Parent="Earth">
<SituationRef InstanceOf="Gemini7StartingSituation"/>
<Body2Cce X="1.815" Y="0.0091" Z="1.9134" />
<BodyRates X="0" Y="0.0011657209075534262" Z="0" />
</LoadVehicleFromLibrary>
The element is
LoadVehicleFromLibrary. NotLoadFromVehicleLibrary, which does not exist, and notLoadFromLibrary, which only handles celestial bodies and will silently drop a vehicle.
Id matches the name in the vehicle's meta.toml under Content\Core\defaultvehicles\. Full walkthrough on Adding a vehicle.
LoadVesselFromLibraryThere is a second, near-identical element name, and it does a different job.
The game reads every system file twice. The first pass builds the system-picker entry and collects a list of what the system needs; the second pass actually builds the system when you select it.
LoadVehicleFromLibrary is read by the second pass. It places the vehicle. This is the one you write.LoadVesselFromLibrary is read by the first pass. It is a whitelist saying "this system needs that vehicle".The whitelist only matters if you declare a <Vehicle> inside an <Assets> file. When a system is selected, any celestial or vehicle template in an assets file that the chosen system does not list is skipped rather than registered, which is how the game avoids loading Jupiter's textures for an Earth-only start.
Stock content declares no <Vehicle> elements in assets files at all, which is why no stock system file contains a LoadVesselFromLibrary. If you go the assets-file route for a vehicle, you need both elements. If you follow Adding a vehicle and use defaultvehicles\, you only need LoadVehicleFromLibrary.