Tested with: KSA Version 2026.10.19.5638
This replaced the old way. Vehicles used to be defined as
<Vehicle>blocks insideAstronomicals.xml, with the part tree, mass, orbit and everything else in one element. That is gone. If you are following a guide that has you writing<Vehicle Id="..."><RootPart .../><Mass Kg="..."/></Vehicle>, it is out of date and the game will ignore almost all of it.
A vehicle now comes from three places:
| What | Where |
|---|---|
| The part tree, meaning what the craft is built from | Content\Core\defaultvehicles\<Name>\vehicle.xml |
| Its name and metadata | Content\Core\defaultvehicles\<Name>\meta.toml |
| Where it starts, in orbit or on a launch pad | a <Situation> in an assets file, referenced from the system file |
Vehicles live in Content\Core\defaultvehicles\. This path is hardcoded and it is not per-mod, so a vehicle folder inside your own mod directory will not be picked up. Drop your folder in alongside the stock ones.
Content\Core\defaultvehicles\
├── Gemini7\
│ ├── meta.toml
│ └── vehicle.xml
└── MyRocket\
├── meta.toml
└── vehicle.xml
name = "MyRocket"
created = 2026-08-07T12:00:00.0000000
updated = 2026-08-07T12:00:00.0000000
version = "v2026.8.5.5168"
systems = [ "Sol", ]
nameis the id everything else refers to, not the folder name. They happen to match in stock content, and you should keep them matching, but the game readsname.
created, updated and version are stamped by the editor when you save a craft and are only used for the columns in the load dialog. systems is filled in with whatever system you were in at the time; nothing reads it back except a debug console listing, so it does not restrict where the craft can be used. Copy the stock pattern and do not worry about it.
No
meta.tomlmeans no vehicle. If the file is missing or unparseable the whole folder is skipped without an error message. This is the first thing to check when a vehicle does not appear.
The root element is <VehicleSaveData>, the same format the game writes when you save a craft from the editor. That means the easiest way to make one is to build it in the VAB and save it, then copy the folder out of Documents\My Games\Kitten Space Agency\vehicles\ into defaultvehicles\.
Here is Banjo, the stock EVA kitten, in full. It is about as small as a vehicle gets:
<?xml version="1.0" encoding="utf-8"?>
<VehicleSaveData Id="Banjo" Character="BanjoKitten">
<RootPartRef InstanceOf="KittenBackPackPart" LocalInstanceId="0">
<Transform>
<Position X="0" Y="0" Z="0" />
<Rotation X="0" Y="0" Z="0" />
<Scale X="1" Y="1" Z="1" />
</Transform>
<SubPartRef InstanceOf="KittenBackPackSubPart" LocalInstanceId="1">
<TankData InstanceOf="PropellantTank">
<Mole SubstancePhaseId="MMH(l)">
<Mass Kg="37.4446" />
</Mole>
<Mole SubstancePhaseId="N2O4(l)">
<Mass Kg="59.9113" />
</Mole>
</TankData>
</SubPartRef>
</RootPartRef>
</VehicleSaveData>
On <VehicleSaveData>:
| Attribute | Meaning |
|---|---|
Id |
The craft name. |
Character |
Optional. Set this to a <Character> id to make it a kitten instead of a rocket. Stock values are BanjoKitten, PolarisKitten, HunterKitten. |
ActiveSequence |
Optional. Which staging sequence is armed. |
Child elements: <RootPartRef>, plus optional <SequenceEnvironment>, <FuelLink> and <LaunchGameTime>.
On <RootPartRef> and <PartRef> / <SubPartRef>:
| Attribute | Meaning |
|---|---|
InstanceOf |
The Id of a <Part> or <SubPart> defined in an assets file. |
LocalInstanceId |
A number unique within this craft. Every part and subpart needs one. |
Stage, Sequence, SequenceGroup, SequenceOrder |
Staging. |
Parts nest: a <RootPartRef> contains <PartRef> children for parts attached to it, and <SubPartRef> children for its own subparts. Each can carry <Transform>, <PartConnectorRef>, <SymmetryRef> and <Gimbal>.
Module data (<TankData>, <BatteryData>, <ControlData>, <DecouplerData>, <DockingData>, <EngineController>, <IVASeatData>, <KeyframeAnimationData>, <PowerConsumerData>, <SolidGrainSegmentData>, <SolidMotorData>, <ThrusterController>) goes inside the <SubPartRef> it belongs to.
Mass, propellant mass and moments of inertia are not written anywhere. The game works them out from the parts, their mass geometry templates and what is actually in the tanks. There is nothing to fill in.
Orbits moved out of the vehicle definition into their own reusable element. Put this in any file listed under assets in your mod.toml. Core keeps them all in Content\Core\Situations.xml:
<?xml version="1.0" encoding="utf-8"?>
<Assets>
<Situation Id="MyRocketStartingSituation">
<Orbit DefinitionFrame="Ecliptic">
<SemiMajorAxis Km="6713" />
<Inclination Degrees="28.87" />
<Eccentricity Value="0.0077" />
<LongitudeOfAscendingNode Degrees="60.48" />
<ArgumentOfPeriapsis Degrees="30.0015" />
<TimeAtPeriapsis Minutes="-20" />
</Orbit>
</Situation>
</Assets>
<Situation> also accepts <CelestialId> and <LocationId> for placing a craft at a named surface location instead of in orbit.
Valid <Orbit> children are SemiMajorAxis, Periapsis, Eccentricity, Inclination, LongitudeOfAscendingNode, ArgumentOfPeriapsis and TimeAtPeriapsis, plus the DefinitionFrame attribute. See Coordinates and Units for units.
In your system file, use LoadVehicleFromLibrary:
<LoadVehicleFromLibrary Id="MyRocket" Parent="Earth">
<SituationRef InstanceOf="MyRocketStartingSituation"/>
<Body2Cce X="1.815" Y="0.0091" Z="1.9134" />
<BodyRates X="0" Y="0.0011657209075534262" Z="0" />
</LoadVehicleFromLibrary>
Id must match name in the vehicle's meta.toml.Parent is the body it orbits.<SituationRef InstanceOf="..."/> points at the <Situation> from step 2.<Body2Cce> is the craft's starting orientation, <BodyRates> its starting roll/pitch/yaw rate. Both optional.<WindSound SoundId="..."/> is also accepted.Those four elements plus Parent are genuinely all LoadVehicleFromLibrary reads. Anything else you put in there is silently dropped, including <Color> and <SoundEvent>, which still appear in stock EarthOnly.xml as leftovers and do nothing.
Not
LoadFromLibrary, and notLoadFromVehicleLibrary.LoadFromLibraryis for celestial bodies only; a vehicle added with it never appears.LoadFromVehicleLibraryis not a real element name at all.
There is no <KittenEva> element. A kitten is an ordinary vehicle whose vehicle.xml sets Character="BanjoKitten" and whose root part is KittenBackPackPart. Stock Banjo, Hunter and Polaris are all in defaultvehicles\ next to Gemini7 and Rocket, and all five are loaded the same way.
Work down this list in order:
Could not find default vehicle save 'X' in the log. The Id on your LoadVehicleFromLibrary does not match any name in a defaultvehicles\*\meta.toml. Check for a typo or a missing meta.toml.systems in mod.toml.InstanceOf in vehicle.xml names a part id that does not exist. Check the assets file defining it is listed under assets, and listed before anything that references it.SituationRef id does not resolve, so the orbit block never applied.The log is Documents\My Games\Kitten Space Agency\logs\KittenSpaceAgency.log.