RimWorld Wiki - User contributions [en]

Modding Tutorials/Pawn Generation Process

2026-07-31T18:27:37Z

Aelanna: Added two missing steps.

{{DISPLAYTITLE:Pawn Generation Process}}
{{BackToTutorials}}

{{:Modding_Tutorials/Under_Review}}

Last updated for: <code>1.6.4871 rev591</code>

This guide explains the pawn generation process of RimWorld and its individual steps.

== WARNING ==

This guide is intended to be used to reference the order in which sections of pawn data is generated in order to diagnose issues with mod code running too early or too late. '''You should avoid Harmony patching these methods if there are existing mechanisms for affecting that particular aspect,''' as pawn generation is a very performance-sensitive system in RimWorld. If you have any questions regarding pawn generation mechanisms, please make use of online resources such as the '''#mod-development''' channel on [https://discord.gg/rimworld the RimWorld Discord].

== Entry Point ==

The root method that services pawn generation requests is <code>Verse.PawnGenerator.GeneratePawn(PawnGenerationRequest)</code>, which is called from dozens of external methods.

This then calls <code>Verse.PawnGenerator.GenerateOrRedressPawnInternal(PawnGenerationRequest)</code> after validating the request conditions, which will then call <code>RedressPawn(Pawn, PawnGenerationRequest)</code> if it decides to redress (recycle) an existing pawn or <code>GenerateNewPawnInternal(ref PawnGenerationRequest)</code> if it decides to generate a fresh pawn.

== Existing Pawn Redressing ==

(Placeholder)

== New Pawn Generation ==

New pawn generation begins in <code>Verse.PawnGenerator.GenerateNewPawnInternal(ref PawnGenerationRequest)</code>. This method's primary purpose is to call <code>TryGenerateNewPawnInternal(ref PawnGenerationRequest, out string, bool, bool)</code> and retry if the attempt fails. After 70 failed attempts the pawn generator will log an error and begin ignoring scenario requirements. After 100 attempts the pawn generator will begin ignoring validators. After 120 failed attempts the pawn generator will give up and return null.

<div class="TutorialTableWrapper">
{| class="TutorialCodeTable"
! # !! Description || Called Method(s)
|-
| class="TutorialCodeTable-description" | '''1'''
| class="TutorialCodeTable-description" | '''Create the Pawn object'''
| <source lang="xml">
Verse.ThingMaker.MakeThing(ThingDef)
</source>
|-
| class="TutorialCodeTable-description" | '''2'''
| class="TutorialCodeTable-description" | '''Set the new pawn's faction'''
| <source lang="xml">
Verse.Pawn.SetFactionDirect(Faction)
</source>
|-
| class="TutorialCodeTable-description" | '''3'''
| class="TutorialCodeTable-description" | '''Initialize the pawn's internal components and trackers'''
| <source lang="xml">
Rimworld.PawnComponentsUtility.CreateInitialComponents(Pawn);
</source>
|-
| class="TutorialCodeTable-description" | '''4'''
| class="TutorialCodeTable-description" | {{AnomalyIcon}} '''Validate that Anomaly is enabled and the request allows creepjoiners if the pawn is currently considered a creepjoiner'''
| <source lang="xml">
(inline)
</source>
|-
| class="TutorialCodeTable-description" | '''5'''
| class="TutorialCodeTable-description" | '''Set gender''' (PawnGenerationRequest > PawnKindDef > random roll)
| <source lang="xml">
(inline)
</source>
|-
| class="TutorialCodeTable-description" | '''6'''
| class="TutorialCodeTable-description" | '''Set age'''
| <source lang="xml">
Verse.PawnGenerator.GenerateRandomAge(Pawn, PawnGenerationRequest)
</source>
|-
| class="TutorialCodeTable-description" | '''7'''
| class="TutorialCodeTable-description" | '''Set initial needs levels'''
| <source lang="xml">
pawn.needs.SetInitialLevels()
</source>
|-
| class="TutorialCodeTable-description" | '''8'''
| class="TutorialCodeTable-description" | '''Adjust food and rest need levels if the pawn is a newborn'''
| <source lang="xml">
(inline)
</source>
|-
| class="TutorialCodeTable-description" | '''9'''
| class="TutorialCodeTable-description" | '''Apply humanlike pawn overrides'''
| <source lang="xml">
(inline)
</source>
|-
| class="TutorialCodeTable-description" |
| class="TutorialCodeTable-description" | a. Apply randomized faction if none was specified in the request
| <source lang="xml">
(inline)
</source>
|-
| class="TutorialCodeTable-description" |
| class="TutorialCodeTable-description" | b. Apply request skin color override if applicable
| <source lang="xml">
(inline)
</source>
|-
| class="TutorialCodeTable-description" |
| class="TutorialCodeTable-description" | c. Select head type - can be randomized or one forced by pawn genes
| <source lang="xml">
pawn.story.TryGetRandomHeadFromSet(IEnumerable<HeadTypeDef>)
</source>
|-
| class="TutorialCodeTable-description" |
| class="TutorialCodeTable-description" | d. {{IdeologyIcon}} Assign favorite color from the request or a randomly chosen ColorDef
| <source lang="xml">
(inline)
</source>
|-
| class="TutorialCodeTable-description" |
| class="TutorialCodeTable-description" | e. {{BiotechIcon}} Assign a [[xenotype]] based on request and faction, if applicable. Note that this only applies the xenotype label; genes are not applied until step 9i
| <source lang="xml">
GetXenotypeForGeneratedPawn(PawnGenerationRequest)
AdjustXenotypeForFactionlessPawn(Pawn, ref PawnGenerationRequest, ref XenotypeDef)
</source>
|-
| class="TutorialCodeTable-description" |
| class="TutorialCodeTable-description" | f. Pick a [[List_of_Player-created_Pawns|solid]] or random bio (name and backstories)
| <source lang="xml">
RimWorld.PawnBioAndNameGenerator.GiveAppropriateBioAndNameTo(Pawn, FactionDef, PawnGenerationRequest, XenotypeDef)
</source>
|-
| class="TutorialCodeTable-description" |
| class="TutorialCodeTable-description" | g. Override name from request if applicable (such as for children)
| <source lang="xml">
(inline)
</source>
|-
| class="TutorialCodeTable-description" |
| class="TutorialCodeTable-description" | h. Apply traits
| <source lang="xml">
GenerateTraits(Pawn, PawnGenerationRequest)
</source>
|-
| class="TutorialCodeTable-description" |
| class="TutorialCodeTable-description" | i. Apply body type
| <source lang="xml">
GenerateBodyType(Pawn, PawnGenerationRequest)
</source>
|-
| class="TutorialCodeTable-description" |
| class="TutorialCodeTable-description" | j. Generate genes
| <source lang="xml">
GenerateGenes(Pawn, XenotypeDef, PawnGenerationRequest)
</source>
|-
| class="TutorialCodeTable-description" |
| class="TutorialCodeTable-description" | k. Generate skill passions and levels
| <source lang="xml">
GenerateSkills(Pawn, PawnGenerationRequest)
</source>
|-
| class="TutorialCodeTable-description" | '''10'''
| class="TutorialCodeTable-description" | '''Generate random pawn relations if pawn is not a newborn'''
| <source lang="xml">
GeneratePawnRelations(Pawn, ref PawnGenerationRequest)
</source>
|-
| class="TutorialCodeTable-description" | '''11'''
| class="TutorialCodeTable-description" | '''If the pawn is a player animal, make it tamed and enable Tameness training'''
| <source lang="xml">
(inline)
</source>
|-
| class="TutorialCodeTable-description" | '''12'''
| class="TutorialCodeTable-description" | '''Generate an appropriate RoyalTitleDef for the pawn, if applicable''' - Note that RoyalTitleDefs are not locked to {{RoyaltyIcon}}Royalty. Also includes permits, favor, and psycaster levels
| <source lang="xml">
(inline)
</source>
|-
| class="TutorialCodeTable-description" | '''13'''
| class="TutorialCodeTable-description" | {{RoyaltyIcon}} '''Enable bedroom and apparel demands if applicable to PawnKindDef'''
| <source lang="xml">
(inline)
</source>
|-
| class="TutorialCodeTable-description" | '''14'''
| class="TutorialCodeTable-description" | {{IdeologyIcon}} '''Randomize join status''' - "join as colonist" vs. "join as slave"
| <source lang="xml">
pawn.guest.RandomizeJoinStatus()
</source>
|-
| class="TutorialCodeTable-description" | '''15'''
| class="TutorialCodeTable-description" | '''Initialize work assignments for player-controlled pawns with a work settings tracker'''
| <source lang="xml">
pawn.workSettings.EnableAndInitialize()
</source>
|-
| class="TutorialCodeTable-description" | '''16'''
| class="TutorialCodeTable-description" | '''Generate an appropriate name for faction-controlled animals and mechs''' - Only applicable to mechs if {{BiotechIcon}} Biotech is enabled
| <source lang="xml">
pawn.GenerateNecessaryName()
</source>
|-
| class="TutorialCodeTable-description" | '''17'''
| class="TutorialCodeTable-description" | {{IdeologyIcon}} '''Set Ideo if applicable''' - Based on request, only for non-babies
| <source lang="xml">
(inline)
</source>
|-
| class="TutorialCodeTable-description" | '''18'''
| class="TutorialCodeTable-description" | {{IdeologyIcon}} '''If the pawn has a MindStateTracker and it craves human meat, set an initial value for when it last ate human meat''' - In order to prevent cannibals from being immediately unhappy
| <source lang="xml">
pawn.mindState.SetupLastHumanMeatTick()
</source>
|-
| class="TutorialCodeTable-description" | '''19'''
| class="TutorialCodeTable-description" | '''If the pawn has a SurroundingsTracker, clear its state'''
| <source lang="xml">
pawn.surroundings.Clear()
</source>
|-
| class="TutorialCodeTable-description" | '''20'''
| class="TutorialCodeTable-description" | '''Generate initial hediffs'''
| <source lang="xml">
GenerateInitialHediffs(Pawn, PawnGenerationRequest)
</source>
|-
| class="TutorialCodeTable-description" | '''21'''
| class="TutorialCodeTable-description" | '''If the request asked for a dead pawn and the pawn is not dead, kill it'''
| <source lang="xml">
pawn.Kill()
</source>
|-
| class="TutorialCodeTable-description" | '''22'''
| class="TutorialCodeTable-description" | '''Humanlike style item setup'''
| <source lang="xml">
(inline)
</source>
|-
| class="TutorialCodeTable-description" |
| class="TutorialCodeTable-description" | a. Choose a random hair style
| <source lang="xml">
PawnStyleItemChooser.RandomHairFor(Pawn)
</source>
|-
| class="TutorialCodeTable-description" |
| class="TutorialCodeTable-description" | b. Choose a random beard style
| <source lang="xml">
PawnStyleItemChooser.RandomBeardFor(Pawn)
</source>
|-
| class="TutorialCodeTable-description" |
| class="TutorialCodeTable-description" | c. {{IdeologyIcon}} Choose a random tattoo style - forces to NoTattoo for babies or if Ideology is disabled
| <source lang="xml">
PawnStyleItemChooser.RandomTattooFor(Pawn) - for both face and body
</source>
|-
| class="TutorialCodeTable-description" | '''23'''
| class="TutorialCodeTable-description" | '''Apply all AbilityDefs specified in the PawnKindDef if provided'''
| <source lang="xml">
(inline)
</source>
|-
| class="TutorialCodeTable-description" | '''24'''
| class="TutorialCodeTable-description" | '''Notify all Scenario parts that a new pawn has been generated''' - This is where forced traits and hediffs from the scenario are applied
| <source lang="xml">
Find.Scenario.Notify_NewPawnGenerating(Pawn, PawnGenerationContext)
</source>
|-
| class="TutorialCodeTable-description" | '''25'''
| class="TutorialCodeTable-description" | '''Run validation checks for the generated pawn and discard if any fail''' - Any failures will immediately return a null from this attempt
| <source lang="xml">
(inline)
</source>
|-
| class="TutorialCodeTable-description" |
| class="TutorialCodeTable-description" | a. If the pawn is dead and the request did not allow for dead pawns, discard it
| <source lang="xml">
(inline)
</source>
|-
| class="TutorialCodeTable-description" |
| class="TutorialCodeTable-description" | b. If the request does not allow dead or downed pawns and the pawn is downed, discard it
| <source lang="xml">
(inline)
</source>
|-
| class="TutorialCodeTable-description" |
| class="TutorialCodeTable-description" | c. If the request requires the capability for violence and the pawn is incapable, discard it
| <source lang="xml">
(inline)
</source>
|-
| class="TutorialCodeTable-description" |
| class="TutorialCodeTable-description" | d. If the PawnKind requires capability in specific skills and this pawn is incapable, discard it
| <source lang="xml">
(inline)
</source>
|-
| class="TutorialCodeTable-description" |
| class="TutorialCodeTable-description" | e. If the PawnKind requires any minimum skill levels and this pawn does not meet those requirements, discard it
| <source lang="xml">
(inline)
</source>
|-
| class="TutorialCodeTable-description" |
| class="TutorialCodeTable-description" | f. If the PawnKind requires a mimimum combined skill level and the pawn does not meet that requirement, discard it
| <source lang="xml">
(inline)
</source>
|-
| class="TutorialCodeTable-description" |
| class="TutorialCodeTable-description" | g. If the request is for a player starting pawn, the pawn does not meet the scenario requirements, and the pawn generator has not hit the threshold for ignoring scenario requirements, discard it
| <source lang="xml">
(inline)
</source>
|-
| class="TutorialCodeTable-description" |
| class="TutorialCodeTable-description" | h. If the request provided a special pre-gear validator, the pawn does not pass the validator, and the pawn generator has not hit the threshold for ignoring the validator, discard it
| <source lang="xml">
(inline)
</source>
|-
| class="TutorialCodeTable-description" | '''26'''
| class="TutorialCodeTable-description" | '''Generate pawn gear''' - Does not apply for newborns, mechanoids, or if the request forces no gear (naked brutality)
| <source lang="xml">
GenerateGearFor(Pawn, PawnGenerationRequest)
</source>
|-
| class="TutorialCodeTable-description" |
| class="TutorialCodeTable-description" | a. Generate starting apparel
| <source lang="xml">
PawnApparelGenerator.GenerateStartingApparelFor(Pawn, PawnGenerationRequest)
</source>
|-
| class="TutorialCodeTable-description" |
| class="TutorialCodeTable-description" | b. Generate inventory items
| <source lang="xml">
PawnInventoryGenerator.GenerateInventoryFor(Pawn, PawnGenerationRequest)
</source>
|-
| class="TutorialCodeTable-description" |
| class="TutorialCodeTable-description" | c. Generate equipped weapon (can be disabled by request)
| <source lang="xml">
PawnWeaponGenerator.TryGenerateWeaponFor(Pawn, PawnGenerationRequest)
</source>
|-
| class="TutorialCodeTable-description" | '''27'''
| class="TutorialCodeTable-description" | '''If pawn is dead, notify PawnApparelTracker that the pawn died''' - This is what causes clothing to be tainted
| <source lang="xml">
pawn.apparel.Notify_PawnKilled()
</source>
|-
| class="TutorialCodeTable-description" | '''28'''
| class="TutorialCodeTable-description" | '''Run post-gear pawn validator, if provided''' - As with pre-gear validator, if the pawn does not pass this validator and the pawn generator has not reached the threshold for ignoring validators then the pawn will be discarded
| <source lang="xml">
(inline)
</source>
|-
| class="TutorialCodeTable-description" | '''29'''
| class="TutorialCodeTable-description" | {{AnomalyIcon}} '''Apply a MutantDef if one is specified by the request or PawnKindDef'''
| <source lang="xml">
MutantUtility.SetFreshPawnAsMutant(Pawn, MutantDef)
</source>
|-
| class="TutorialCodeTable-description" | '''30'''
| class="TutorialCodeTable-description" | '''Add the pawn to the static list of pawns being generated'''
| <source lang="xml">
(inline)
</source>
|-
| class="TutorialCodeTable-description" | '''31'''
| class="TutorialCodeTable-description" | '''If the pawn has a faction, notify the faction of a new member joining'''
| <source lang="xml">
pawn.Faction.Notify_PawnJoined(Pawn);
</source>
|-
| class="TutorialCodeTable-description" | '''32'''
| class="TutorialCodeTable-description" | '''Apply <code>existingDamage</code> entries from PawnKindDef''' - Used by {{AnomalyIcon}} Anomaly for pawns with surgical scars and other similar pre-existing injuries
| <source lang="xml">
ApplyMiscDamage(Pawn, PawnKindDef)
</source>
|-
| class="TutorialCodeTable-description" | '''33'''
| class="TutorialCodeTable-description" | '''Flag pawn's renderer as dirty''' - Forces a regeneration of its render tree
| <source lang="xml">
pawn.Drawer?.renderer?.SetAllGraphicsDirty()
</source>
|-
| class="TutorialCodeTable-description" | '''34'''
| class="TutorialCodeTable-description" | '''Remove the pawn from the static list of pawns being generated''' - Run in a <code>finally</code> block, even if an above step returns early or causes an error
| <source lang="xml">
(inline)
</source>
|-
|}
</div>

[[Category:Modding tutorials]]

Modding Tutorials/Pawn Generation Process

2026-07-31T18:06:05Z

Aelanna: /* New Pawn Generation */

{{DISPLAYTITLE:Pawn Generation Process}}
{{BackToTutorials}}

{{:Modding_Tutorials/Under_Review}}

Last updated for: <code>1.6.4871 rev591</code>

This guide explains the pawn generation process of RimWorld and its individual steps.

== WARNING ==

This guide is intended to be used to reference the order in which sections of pawn data is generated in order to diagnose issues with mod code running too early or too late. '''You should avoid Harmony patching these methods if there are existing mechanisms for affecting that particular aspect,''' as pawn generation is a very performance-sensitive system in RimWorld. If you have any questions regarding pawn generation mechanisms, please make use of online resources such as the '''#mod-development''' channel on [https://discord.gg/rimworld the RimWorld Discord].

== Entry Point ==

The root method that services pawn generation requests is <code>Verse.PawnGenerator.GeneratePawn(PawnGenerationRequest)</code>, which is called from dozens of external methods.

This then calls <code>Verse.PawnGenerator.GenerateOrRedressPawnInternal(PawnGenerationRequest)</code> after validating the request conditions, which will then call <code>RedressPawn(Pawn, PawnGenerationRequest)</code> if it decides to redress (recycle) an existing pawn or <code>GenerateNewPawnInternal(ref PawnGenerationRequest)</code> if it decides to generate a fresh pawn.

== Existing Pawn Redressing ==

(Placeholder)

== New Pawn Generation ==

New pawn generation begins in <code>Verse.PawnGenerator.GenerateNewPawnInternal(ref PawnGenerationRequest)</code>. This method's primary purpose is to call <code>TryGenerateNewPawnInternal(ref PawnGenerationRequest, out string, bool, bool)</code> and retry if the attempt fails. After 70 failed attempts the pawn generator will log an error and begin ignoring scenario requirements. After 100 attempts the pawn generator will begin ignoring validators. After 120 failed attempts the pawn generator will give up and return null.

<div class="TutorialTableWrapper">
{| class="TutorialCodeTable"
! # !! Description || Called Method(s)
|-
| class="TutorialCodeTable-description" | '''1'''
| class="TutorialCodeTable-description" | '''Create the Pawn object'''
| <source lang="xml">
Verse.ThingMaker.MakeThing(ThingDef)
</source>
|-
| class="TutorialCodeTable-description" | '''2'''
| class="TutorialCodeTable-description" | '''Set the new pawn's faction'''
| <source lang="xml">
Verse.Pawn.SetFactionDirect(Faction)
</source>
|-
| class="TutorialCodeTable-description" | '''3'''
| class="TutorialCodeTable-description" | '''Initialize the pawn's internal components and trackers'''
| <source lang="xml">
Rimworld.PawnComponentsUtility.CreateInitialComponents(Pawn);
</source>
|-
| class="TutorialCodeTable-description" | '''4'''
| class="TutorialCodeTable-description" | {{AnomalyIcon}} '''Validate that Anomaly is enabled and the request allows creepjoiners if the pawn is currently considered a creepjoiner'''
| <source lang="xml">
(inline)
</source>
|-
| class="TutorialCodeTable-description" | '''5'''
| class="TutorialCodeTable-description" | '''Set gender''' (PawnGenerationRequest > PawnKindDef > random roll)
| <source lang="xml">
(inline)
</source>
|-
| class="TutorialCodeTable-description" | '''6'''
| class="TutorialCodeTable-description" | '''Set age'''
| <source lang="xml">
Verse.PawnGenerator.GenerateRandomAge(Pawn, PawnGenerationRequest)
</source>
|-
| class="TutorialCodeTable-description" | '''7'''
| class="TutorialCodeTable-description" | '''Set initial needs levels'''
| <source lang="xml">
pawn.needs.SetInitialLevels()
</source>
|-
| class="TutorialCodeTable-description" | '''8'''
| class="TutorialCodeTable-description" | '''Adjust food and rest need levels if the pawn is a newborn'''
| <source lang="xml">
(inline)
</source>
|-
| class="TutorialCodeTable-description" | '''9'''
| class="TutorialCodeTable-description" | '''Apply humanlike pawn overrides'''
| <source lang="xml">
(inline)
</source>
|-
| class="TutorialCodeTable-description" |
| class="TutorialCodeTable-description" | a. Apply randomized faction if none was specified in the request
| <source lang="xml">
(inline)
</source>
|-
| class="TutorialCodeTable-description" |
| class="TutorialCodeTable-description" | b. Apply request skin color override if applicable
| <source lang="xml">
(inline)
</source>
|-
| class="TutorialCodeTable-description" |
| class="TutorialCodeTable-description" | c. Select head type - can be randomized or one forced by pawn genes
| <source lang="xml">
pawn.story.TryGetRandomHeadFromSet(IEnumerable<HeadTypeDef>)
</source>
|-
| class="TutorialCodeTable-description" |
| class="TutorialCodeTable-description" | d. {{IdeologyIcon}} Assign favorite color from the request or a randomly chosen ColorDef
| <source lang="xml">
(inline)
</source>
|-
| class="TutorialCodeTable-description" |
| class="TutorialCodeTable-description" | e. {{BiotechIcon}} Assign a [[xenotype]] based on request and faction, if applicable. Note that this only applies the xenotype label; genes are not applied until step 9i
| <source lang="xml">
GetXenotypeForGeneratedPawn(PawnGenerationRequest)
AdjustXenotypeForFactionlessPawn(Pawn, ref PawnGenerationRequest, ref XenotypeDef)
</source>
|-
| class="TutorialCodeTable-description" |
| class="TutorialCodeTable-description" | f. Pick a [[List_of_Player-created_Pawns|solid]] or random bio (name and backstories)
| <source lang="xml">
RimWorld.PawnBioAndNameGenerator.GiveAppropriateBioAndNameTo(Pawn, FactionDef, PawnGenerationRequest, XenotypeDef)
</source>
|-
| class="TutorialCodeTable-description" |
| class="TutorialCodeTable-description" | g. Override name from request if applicable (such as for children)
| <source lang="xml">
(inline)
</source>
|-
| class="TutorialCodeTable-description" |
| class="TutorialCodeTable-description" | h. Apply traits
| <source lang="xml">
GenerateTraits(Pawn, PawnGenerationRequest)
</source>
|-
| class="TutorialCodeTable-description" |
| class="TutorialCodeTable-description" | i. Apply body type
| <source lang="xml">
GenerateBodyType(Pawn, PawnGenerationRequest)
</source>
|-
| class="TutorialCodeTable-description" |
| class="TutorialCodeTable-description" | j. Generate genes
| <source lang="xml">
GenerateGenes(Pawn, XenotypeDef, PawnGenerationRequest)
</source>
|-
| class="TutorialCodeTable-description" |
| class="TutorialCodeTable-description" | k. Generate skill passions and levels
| <source lang="xml">
GenerateSkills(Pawn, PawnGenerationRequest)
</source>
|-
| class="TutorialCodeTable-description" | '''10'''
| class="TutorialCodeTable-description" | '''Generate random pawn relations if pawn is not a newborn'''
| <source lang="xml">
GeneratePawnRelations(Pawn, ref PawnGenerationRequest)
</source>
|-
| class="TutorialCodeTable-description" | '''11'''
| class="TutorialCodeTable-description" | '''If the pawn is a player animal, make it tamed and enable Tameness training'''
| <source lang="xml">
(inline)
</source>
|-
| class="TutorialCodeTable-description" | '''12'''
| class="TutorialCodeTable-description" | '''Generate an appropriate RoyalTitleDef for the pawn, if applicable''' - Note that RoyalTitleDefs are not locked to {{RoyaltyIcon}}Royalty. Also includes permits, favor, and psycaster levels
| <source lang="xml">
(inline)
</source>
|-
| class="TutorialCodeTable-description" | '''13'''
| class="TutorialCodeTable-description" | {{RoyaltyIcon}} '''Enable bedroom and apparel demands if applicable to PawnKindDef'''
| <source lang="xml">
(inline)
</source>
|-
| class="TutorialCodeTable-description" | '''14'''
| class="TutorialCodeTable-description" | {{IdeologyIcon}} '''Randomize join status''' - "join as colonist" vs. "join as slave"
| <source lang="xml">
pawn.guest.RandomizeJoinStatus()
</source>
|-
| class="TutorialCodeTable-description" | '''15'''
| class="TutorialCodeTable-description" | '''Initialize work assignments for player-controlled pawns with a work settings tracker'''
| <source lang="xml">
pawn.workSettings.EnableAndInitialize()
</source>
|-
| class="TutorialCodeTable-description" | '''16'''
| class="TutorialCodeTable-description" | '''Generate an appropriate name for faction-controlled animals and mechs''' - Only applicable to mechs if {{BiotechIcon}} Biotech is enabled
| <source lang="xml">
pawn.GenerateNecessaryName()
</source>
|-
| class="TutorialCodeTable-description" | '''17'''
| class="TutorialCodeTable-description" | {{IdeologyIcon}} '''Set Ideo if applicable''' - Based on request, only for non-babies
| <source lang="xml">
(inline)
</source>
|-
| class="TutorialCodeTable-description" | '''18'''
| class="TutorialCodeTable-description" | {{IdeologyIcon}} '''If the pawn has a MindStateTracker and it craves human meat, set an initial value for when it last ate human meat''' - In order to prevent cannibals from being immediately unhappy
| <source lang="xml">
pawn.mindState.SetupLastHumanMeatTick()
</source>
|-
| class="TutorialCodeTable-description" | '''19'''
| class="TutorialCodeTable-description" | '''If the pawn has a SurroundingsTracker, clear its state'''
| <source lang="xml">
pawn.surroundings.Clear()
</source>
|-
| class="TutorialCodeTable-description" | '''20'''
| class="TutorialCodeTable-description" | '''Generate initial hediffs'''
| <source lang="xml">
GenerateInitialHediffs(Pawn, PawnGenerationRequest)
</source>
|-
| class="TutorialCodeTable-description" | '''21'''
| class="TutorialCodeTable-description" | '''If the request asked for a dead pawn and the pawn is not dead, kill it'''
| <source lang="xml">
pawn.Kill()
</source>
|-
| class="TutorialCodeTable-description" | '''22'''
| class="TutorialCodeTable-description" | '''Humanlike style item setup'''
| <source lang="xml">
(inline)
</source>
|-
| class="TutorialCodeTable-description" |
| class="TutorialCodeTable-description" | a. Choose a random hair style
| <source lang="xml">
PawnStyleItemChooser.RandomHairFor(Pawn)
</source>
|-
| class="TutorialCodeTable-description" |
| class="TutorialCodeTable-description" | b. Choose a random beard style
| <source lang="xml">
PawnStyleItemChooser.RandomBeardFor(Pawn)
</source>
|-
| class="TutorialCodeTable-description" |
| class="TutorialCodeTable-description" | c. {{IdeologyIcon}} Choose a random tattoo style - forces to NoTattoo for babies or if Ideology is disabled
| <source lang="xml">
PawnStyleItemChooser.RandomTattooFor(Pawn) - for both face and body
</source>
|-
| class="TutorialCodeTable-description" | '''23'''
| class="TutorialCodeTable-description" | '''Apply all AbilityDefs specified in the PawnKindDef if provided'''
| <source lang="xml">
(inline)
</source>
|-
| class="TutorialCodeTable-description" | '''24'''
| class="TutorialCodeTable-description" | '''Notify all Scenario parts that a new pawn has been generated''' - This is where forced traits and hediffs from the scenario are applied
| <source lang="xml">
Find.Scenario.Notify_NewPawnGenerating(Pawn, PawnGenerationContext)
</source>
|-
| class="TutorialCodeTable-description" | '''25'''
| class="TutorialCodeTable-description" | '''Run validation checks for the generated pawn and discard if any fail''' - Any failures will immediately return a null from this attempt
| <source lang="xml">
(inline)
</source>
|-
| class="TutorialCodeTable-description" |
| class="TutorialCodeTable-description" | a. If the pawn is dead and the request did not allow for dead pawns, discard it
| <source lang="xml">
(inline)
</source>
|-
| class="TutorialCodeTable-description" |
| class="TutorialCodeTable-description" | b. If the request does not allow dead or downed pawns and the pawn is downed, discard it
| <source lang="xml">
(inline)
</source>
|-
| class="TutorialCodeTable-description" |
| class="TutorialCodeTable-description" | c. If the request requires the capability for violence and the pawn is incapable, discard it
| <source lang="xml">
(inline)
</source>
|-
| class="TutorialCodeTable-description" |
| class="TutorialCodeTable-description" | d. If the PawnKind requires capability in specific skills and this pawn is incapable, discard it
| <source lang="xml">
(inline)
</source>
|-
| class="TutorialCodeTable-description" |
| class="TutorialCodeTable-description" | e. If the PawnKind requires any minimum skill levels and this pawn does not meet those requirements, discard it
| <source lang="xml">
(inline)
</source>
|-
| class="TutorialCodeTable-description" |
| class="TutorialCodeTable-description" | f. If the PawnKind requires a mimimum combined skill level and the pawn does not meet that requirement, discard it
| <source lang="xml">
(inline)
</source>
|-
| class="TutorialCodeTable-description" |
| class="TutorialCodeTable-description" | g. If the request is for a player starting pawn, the pawn does not meet the scenario requirements, and the pawn generator has not hit the threshold for ignoring scenario requirements, discard it
| <source lang="xml">
(inline)
</source>
|-
| class="TutorialCodeTable-description" |
| class="TutorialCodeTable-description" | h. If the request provided a special validator, the pawn does not pass the validator, and the pawn generator has not hit the threshold for ignoring the validator, discard it
| <source lang="xml">
(inline)
</source>
|-
| class="TutorialCodeTable-description" | '''26'''
| class="TutorialCodeTable-description" | '''Generate pawn gear''' - Does not apply for newborns, mechanoids, or if the request forces no gear (naked brutality)
| <source lang="xml">
GenerateGearFor(Pawn, PawnGenerationRequest)
</source>
|-
| class="TutorialCodeTable-description" |
| class="TutorialCodeTable-description" | a. Generate starting apparel
| <source lang="xml">
PawnApparelGenerator.GenerateStartingApparelFor(Pawn, PawnGenerationRequest)
</source>
|-
| class="TutorialCodeTable-description" |
| class="TutorialCodeTable-description" | b. Generate inventory items
| <source lang="xml">
PawnInventoryGenerator.GenerateInventoryFor(Pawn, PawnGenerationRequest)
</source>
|-
| class="TutorialCodeTable-description" |
| class="TutorialCodeTable-description" | c. Generate equipped weapon (can be disabled by request)
| <source lang="xml">
PawnWeaponGenerator.TryGenerateWeaponFor(Pawn, PawnGenerationRequest)
</source>
|-
| class="TutorialCodeTable-description" | '''27'''
| class="TutorialCodeTable-description" | {{AnomalyIcon}} '''Apply a MutantDef if one is specified by the request or PawnKindDef'''
| <source lang="xml">
MutantUtility.SetFreshPawnAsMutant(Pawn, MutantDef)
</source>
|-
| class="TutorialCodeTable-description" | '''28'''
| class="TutorialCodeTable-description" | '''Add the pawn to the static list of pawns being generated'''
| <source lang="xml">
(inline)
</source>
|-
| class="TutorialCodeTable-description" | '''29'''
| class="TutorialCodeTable-description" | '''If the pawn has a faction, notify the faction of a new member joining'''
| <source lang="xml">
pawn.Faction.Notify_PawnJoined(Pawn);
</source>
|-
| class="TutorialCodeTable-description" | '''30'''
| class="TutorialCodeTable-description" | '''Apply <code>existingDamage</code> entries from PawnKindDef''' - Used by {{AnomalyIcon}} Anomaly for pawns with surgical scars and other similar pre-existing injuries
| <source lang="xml">
ApplyMiscDamage(Pawn, PawnKindDef)
</source>
|-
| class="TutorialCodeTable-description" | '''31'''
| class="TutorialCodeTable-description" | '''Flag pawn's renderer as dirty''' - Forces a regeneration of its render tree
| <source lang="xml">
pawn.Drawer?.renderer?.SetAllGraphicsDirty()
</source>
|-
| class="TutorialCodeTable-description" | '''32'''
| class="TutorialCodeTable-description" | '''Remove the pawn from the static list of pawns being generated''' - Run in a <code>finally</code> block, even if an above step returns early or causes an error
| <source lang="xml">
(inline)
</source>
|-
|}
</div>

[[Category:Modding tutorials]]

Modding Tutorials/Overhaul workspace

2026-07-31T17:03:52Z

Aelanna:

{{DISPLAYTITLE:Overhaul Workspace}}

{{BackToTutorials}}

{{:Modding_Tutorials/Under_Review}}

'''NOTE''': This is a workspace for the ongoing overhaul of the RimWorld Wiki's modding tutorials and references. If you managed to find your way here, please check out the main [[Modding_Tutorials|modding tutorials index page]] instead.

This overhaul is being overseen by the '''#mod-development''' channel on the [https://discord.gg/rimworld RimWorld Discord], please contact us before changing anything.

== Modding Basics ==

<div class="TwoColumnCollapsibleLayout">
<div class="TwoColumnCollapsibleLayout-section">
<div class="TwoColumnCollapsibleLayout-subtitle">Modding Basics</div>
<div class="TwoColumnCollapsibleLayout-text">
* Getting Started
* [[Modding_Tutorials/Recommended software|Recommended Software]]
* [[Modding_Tutorials/Mod_Folder_Structure|Mod Folder Structure]]
* [[Modding_Tutorials/About.xml|About.xml]]
* [[Modding_Tutorials/Textures|Textures]]
* [[Modding_Tutorials/Sounds|Sounds]]
* [[Modding_Tutorials/Localization|Localization]]
</div>
</div>
<div class="TwoColumnCollapsibleLayout-section">
<div class="TwoColumnCollapsibleLayout-subtitle">XML</div>
<div class="TwoColumnCollapsibleLayout-text">
* Defs
* ThingDef
* [[Modding Tutorials/MayRequire|MayRequire]]
* [[Modding Tutorials/PatchOperations|PatchOperations]]
* [[Modding Tutorials/Research Projects|Research Projects]]
</div>
</div>
<div class="TwoColumnCollapsibleLayout-section">
<div class="TwoColumnCollapsibleLayout-subtitle">C#</div>
<div class="TwoColumnCollapsibleLayout-text">
* C# Basics
* [[Modding_Tutorials/Decompiling source code|Decompiling Source Code]] - Reading compiled code from the base game as well as DLCs and other mods.
* [[Modding_Tutorials/Setting up a solution|Setting up]] - (Needs cleanup)
* Harmony Primer
</div>
</div>
<div class="TwoColumnCollapsibleLayout-section">
<div class="TwoColumnCollapsibleLayout-subtitle">Code References</div>
<div class="TwoColumnCollapsibleLayout-text">
* [[Modding_Tutorials/Infrastructure_Overview|Infrastructure Overview]]
* [[Modding_Tutorials/Application_Startup|Application Startup]]
* [[Modding_Tutorials/Pawn_Generation_Process|Pawn Generation]]
* [[Modding_Tutorials/Simulation_Lifecycle|Simulation Lifecycle]]
* [[Modding_Tutorials/Rendering_Lifecycle|Rendering Lifecycle]]
* [[Modding_Tutorials/Buildings|Buildings]]
* [[Modding_Tutorials/Pawns|Pawns]]
* [[Modding_Tutorials/Audio|Audio]]
</div>
</div>
</div>

== Tutorials ==
This will be a curated subset of tutorials that will be vetted, reviewed, and maintained by the overhaul team. These are meant to be a cohesive set of tutorials that guides the reader from the simplest single-Def items such as weapons to building a full custom faction.

=== Basic Tutorials (XML) ===
* [[Modding_Tutorials/Basic_Melee_Weapon|Creating a custom melee weapon]]
* [[Modding_Tutorials/Basic_Ranged_Weapon|Creating a custom ranged weapon]]
* [[Modding_Tutorials/Basic_Plant|Creating a custom plant]]
* [[Modding_Tutorials/Basic_Animal|Creating a custom animal]]
* [[Modding_Tutorials/Basic_Building|Creating a simple building]]
* [[Modding_Tutorials/Basic_Workbench|Creating a custom workbench]]
* [[Modding_Tutorials/Basic_Drug|Creating a custom drug]]

=== Advanced Tutorials (XML) ===
* [[Modding_Tutorials/Advanced_Faction|Creating a custom faction]]
* [[Modding_Tutorials/Advanced_Culture|Creating a custom culture]]
* [[Modding_Tutorials/Advanced_Trader|Creating a custom trader type]]

=== Basic Tutorials (C#) ===
* [[Modding_Tutorials/Basic_Consumable|Creating a custom consumable]]

=== Advanced Tutorials (C#) ===
* [[Modding_Tutorials/Advanced_Texture_Overlays|Creating custom texture overlays]]

[[Category:Modding tutorials]]

== Banner Templates ==

{{:Modding_Tutorials/Under_Review}}
<nowiki>{{:Modding_Tutorials/Under_Review}}</nowiki>

{{:Modding_Tutorials/Marked_for_Deletion}}
<nowiki>{{:Modding_Tutorials/Marked_for_Deletion}}</nowiki>

{{:Modding_Tutorials/Obsolete}}
<nowiki>{{:Modding_Tutorials/Obsolete}}</nowiki>

{{:Modding_Tutorials/Outdated}}
<nowiki>{{:Modding_Tutorials/Outdated}}</nowiki>

Modding Tutorials/Pawn Generation Process

2026-07-31T17:01:07Z

Aelanna: Created page with "{{DISPLAYTITLE:Pawn Generation Process}} {{BackToTutorials}} {{:Modding_Tutorials/Under_Review}} Last updated for: <code>1.6.4871 rev591</code> This guide explains the pawn..."

{{DISPLAYTITLE:Pawn Generation Process}}
{{BackToTutorials}}

{{:Modding_Tutorials/Under_Review}}

Last updated for: <code>1.6.4871 rev591</code>

This guide explains the pawn generation process of RimWorld and its individual steps.

== WARNING ==

This guide is intended to be used to reference the order in which sections of pawn data is generated in order to diagnose issues with mod code running too early or too late. '''You should avoid Harmony patching these methods if there are existing mechanisms for affecting that particular aspect,''' as pawn generation is a very performance-sensitive system in RimWorld. If you have any questions regarding pawn generation mechanisms, please make use of online resources such as the '''#mod-development''' channel on [https://discord.gg/rimworld the RimWorld Discord].

== Entry Point ==

The root method that services pawn generation requests is <code>Verse.PawnGenerator.GeneratePawn(PawnGenerationRequest)</code>, which is called from dozens of external methods.

This then calls <code>Verse.PawnGenerator.GenerateOrRedressPawnInternal(PawnGenerationRequest)</code> after validating the request conditions, which will then call <code>RedressPawn(Pawn, PawnGenerationRequest)</code> if it decides to redress (recycle) an existing pawn or <code>GenerateNewPawnInternal(ref PawnGenerationRequest)</code> if it decides to generate a fresh pawn.

== Existing Pawn Redressing ==

(Placeholder)

== New Pawn Generation ==

New pawn generation begins in <code>Verse.PawnGenerator.GenerateNewPawnInternal(ref PawnGenerationRequest)</code>. This method's primary purpose is to call <code>TryGenerateNewPawnInternal(ref PawnGenerationRequest, out string, bool, bool)</code> and retry if the attempt fails. After 70 failed attempts the pawn generator will log an error and begin ignoring scenario requirements. After 100 attempts the pawn generator will begin ignoring validators. After 120 failed attempts the pawn generator will give up and return null.

<div class="TutorialTableWrapper">
{| class="TutorialCodeTable"
! # !! Description || Called Method(s)
|-
| class="TutorialCodeTable-description" | '''1'''
| class="TutorialCodeTable-description" | '''Create the Pawn object'''
| <source lang="xml">
Verse.ThingMaker.MakeThing(ThingDef)
</source>
|-
| class="TutorialCodeTable-description" | '''2'''
| class="TutorialCodeTable-description" | '''Set the new pawn's faction'''
| <source lang="xml">
Verse.Pawn.SetFactionDirect(Faction)
</source>
|-
| class="TutorialCodeTable-description" | '''3'''
| class="TutorialCodeTable-description" | '''Initialize the pawn's internal components and trackers'''
| <source lang="xml">
Rimworld.PawnComponentsUtility.CreateInitialComponents(Pawn);
</source>
|-
| class="TutorialCodeTable-description" | '''4'''
| class="TutorialCodeTable-description" | {{AnomalyIcon}} '''Validate that Anomaly is enabled and the request allows creepjoiners if the pawn is currently considered a creepjoiner'''
| <source lang="xml">
(inline)
</source>
|-
| class="TutorialCodeTable-description" | '''5'''
| class="TutorialCodeTable-description" | '''Set gender''' (PawnGenerationRequest > PawnKindDef > random roll)
| <source lang="xml">
(inline)
</source>
|-
| class="TutorialCodeTable-description" | '''6'''
| class="TutorialCodeTable-description" | '''Set age'''
| <source lang="xml">
Verse.PawnGenerator.GenerateRandomAge(Pawn, PawnGenerationRequest)
</source>
|-
| class="TutorialCodeTable-description" | '''7'''
| class="TutorialCodeTable-description" | '''Set initial needs levels'''
| <source lang="xml">
pawn.needs.SetInitialLevels()
</source>
|-
| class="TutorialCodeTable-description" | '''8'''
| class="TutorialCodeTable-description" | '''Adjust food and rest need levels if the pawn is a newborn'''
| <source lang="xml">
(inline)
</source>
|-
| class="TutorialCodeTable-description" | '''9'''
| class="TutorialCodeTable-description" | '''Apply humanlike pawn overrides'''
| <source lang="xml">
(inline)
</source>
|-
| class="TutorialCodeTable-description" |
| class="TutorialCodeTable-description" | a. Apply randomized faction if none was specified in the request
| <source lang="xml">
(inline)
</source>
|-
| class="TutorialCodeTable-description" |
| class="TutorialCodeTable-description" | b. Apply request skin color override if applicable
| <source lang="xml">
(inline)
</source>
|-
| class="TutorialCodeTable-description" |
| class="TutorialCodeTable-description" | c. Select random head type
| <source lang="xml">
pawn.story.TryGetRandomHeadFromSet(IEnumerable<HeadTypeDef>)
</source>
|-
| class="TutorialCodeTable-description" |
| class="TutorialCodeTable-description" | d. {{IdeologyIcon}} Assign favorite color from the request or a randomly chosen ColorDef
| <source lang="xml">
(inline)
</source>
|-
| class="TutorialCodeTable-description" |
| class="TutorialCodeTable-description" | e. {{BiotechIcon}} Assign a [[xenotype]] based on request and faction, if applicable. Note that this only applies the xenotype label; genes are not applied until step 9i
| <source lang="xml">
GetXenotypeForGeneratedPawn(PawnGenerationRequest)
AdjustXenotypeForFactionlessPawn(Pawn, ref PawnGenerationRequest, ref XenotypeDef)
</source>
|-
| class="TutorialCodeTable-description" |
| class="TutorialCodeTable-description" | f. Pick a [[list of player-created Pawns|solid]] or random bio (name and backstories)
| <source lang="xml">
RimWorld.PawnBioAndNameGenerator.GiveAppropriateBioAndNameTo(Pawn, FactionDef, PawnGenerationRequest, XenotypeDef)
</source>
|-
| class="TutorialCodeTable-description" |
| class="TutorialCodeTable-description" | g. Override name from request if applicable (such as for children)
| <source lang="xml">
(inline)
</source>
|-
| class="TutorialCodeTable-description" |
| class="TutorialCodeTable-description" | h. Apply traits
| <source lang="xml">
GenerateTraits(Pawn, PawnGenerationRequest)
</source>
|-
| class="TutorialCodeTable-description" |
| class="TutorialCodeTable-description" | i. Apply body type
| <source lang="xml">
GenerateBodyType(Pawn, PawnGenerationRequest)
</source>
|-
| class="TutorialCodeTable-description" |
| class="TutorialCodeTable-description" | j. Generate genes
| <source lang="xml">
GenerateGenes(Pawn, XenotypeDef, PawnGenerationRequest)
</source>
|-
| class="TutorialCodeTable-description" |
| class="TutorialCodeTable-description" | k. Generate skill passions and levels
| <source lang="xml">
GenerateSkills(Pawn, PawnGenerationRequest)
</source>
|-
| class="TutorialCodeTable-description" | '''10'''
| class="TutorialCodeTable-description" | '''Generate random pawn relations if pawn is not a newborn'''
| <source lang="xml">
GeneratePawnRelations(Pawn, ref PawnGenerationRequest)
</source>
|-
| class="TutorialCodeTable-description" | '''11'''
| class="TutorialCodeTable-description" | '''If the pawn is a player animal, make it tamed and enable Tameness training'''
| <source lang="xml">
(inline)
</source>
|-
| class="TutorialCodeTable-description" | '''12'''
| class="TutorialCodeTable-description" | '''Generate an appropriate RoyalTitleDef for the pawn, if applicable''' - Note that RoyalTitleDefs are not locked to {{RoyaltyIcon}}Royalty. Also includes permits, favor, and psycaster levels
| <source lang="xml">
(inline)
</source>
|-
| class="TutorialCodeTable-description" | '''13'''
| class="TutorialCodeTable-description" | {{RoyaltyIcon}} '''Enable bedroom and apparel demands if applicable to PawnKindDef'''
| <source lang="xml">
(inline)
</source>
|-
| class="TutorialCodeTable-description" | '''14'''
| class="TutorialCodeTable-description" | {{IdeologyIcon}} '''Randomize join status''' - "join as colonist" vs. "join as slave"
| <source lang="xml">
pawn.guest.RandomizeJoinStatus()
</source>
|-
| class="TutorialCodeTable-description" | '''15'''
| class="TutorialCodeTable-description" | '''Initialize work assignments for player-controlled pawns with a work settings tracker'''
| <source lang="xml">
pawn.workSettings.EnableAndInitialize()
</source>
|-
| class="TutorialCodeTable-description" | '''16'''
| class="TutorialCodeTable-description" | '''Generate an appropriate name for faction-controlled animals and mechs''' - Only applicable to mechs if {{BiotechIcon}} Biotech is enabled
| <source lang="xml">
pawn.GenerateNecessaryName()
</source>
|-
| class="TutorialCodeTable-description" | '''17'''
| class="TutorialCodeTable-description" | {{IdeologyIcon}} '''Set Ideo if applicable''' - Based on request, only for non-babies
| <source lang="xml">
(inline)
</source>
|-
| class="TutorialCodeTable-description" | '''18'''
| class="TutorialCodeTable-description" | {{IdeologyIcon}} '''If the pawn has a MindStateTracker and it craves human meat, set an initial value for when it last ate human meat''' - In order to prevent cannibals from being immediately unhappy
| <source lang="xml">
pawn.mindState.SetupLastHumanMeatTick()
</source>
|-
| class="TutorialCodeTable-description" | '''19'''
| class="TutorialCodeTable-description" | '''If the pawn has a SurroundingsTracker, clear its state'''
| <source lang="xml">
pawn.surroundings.Clear()
</source>
|-
| class="TutorialCodeTable-description" | '''20'''
| class="TutorialCodeTable-description" | '''Generate initial hediffs'''
| <source lang="xml">
GenerateInitialHediffs(Pawn, PawnGenerationRequest)
</source>
|-
| class="TutorialCodeTable-description" | '''21'''
| class="TutorialCodeTable-description" | '''If the request asked for a dead pawn and the pawn is not dead, kill it'''
| <source lang="xml">
pawn.Kill()
</source>
|-
| class="TutorialCodeTable-description" | '''22'''
| class="TutorialCodeTable-description" | '''Humanlike style item setup'''
| <source lang="xml">
(inline)
</source>
|-
| class="TutorialCodeTable-description" |
| class="TutorialCodeTable-description" | a. Choose a random hair style
| <source lang="xml">
PawnStyleItemChooser.RandomHairFor(Pawn)
</source>
|-
| class="TutorialCodeTable-description" |
| class="TutorialCodeTable-description" | b. Choose a random beard style
| <source lang="xml">
PawnStyleItemChooser.RandomBeardFor(Pawn)
</source>
|-
| class="TutorialCodeTable-description" |
| class="TutorialCodeTable-description" | c. {{IdeologyIcon}} Choose a random tattoo style - forces to NoTattoo for babies or if Ideology is disabled
| <source lang="xml">
PawnStyleItemChooser.RandomTattooFor(Pawn) - for both face and body
</source>
|-
| class="TutorialCodeTable-description" | '''23'''
| class="TutorialCodeTable-description" | '''Apply all AbilityDefs specified in the PawnKindDef if provided'''
| <source lang="xml">
(inline)
</source>
|-
| class="TutorialCodeTable-description" | '''24'''
| class="TutorialCodeTable-description" | '''Notify all Scenario parts that a new pawn has been generated''' - This is where forced traits and hediffs from the scenario are applied
| <source lang="xml">
Find.Scenario.Notify_NewPawnGenerating(Pawn, PawnGenerationContext)
</source>
|-
| class="TutorialCodeTable-description" | '''25'''
| class="TutorialCodeTable-description" | '''Run validation checks for the generated pawn and discard if any fail''' - Any failures will immediately return a null from this attempt
| <source lang="xml">
(inline)
</source>
|-
| class="TutorialCodeTable-description" |
| class="TutorialCodeTable-description" | a. If the pawn is dead and the request did not allow for dead pawns, discard it
| <source lang="xml">
(inline)
</source>
|-
| class="TutorialCodeTable-description" |
| class="TutorialCodeTable-description" | b. If the request does not allow dead or downed pawns and the pawn is downed, discard it
| <source lang="xml">
(inline)
</source>
|-
| class="TutorialCodeTable-description" |
| class="TutorialCodeTable-description" | c. If the request requires the capability for violence and the pawn is incapable, discard it
| <source lang="xml">
(inline)
</source>
|-
| class="TutorialCodeTable-description" |
| class="TutorialCodeTable-description" | d. If the PawnKind requires capability in specific skills and this pawn is incapable, discard it
| <source lang="xml">
(inline)
</source>
|-
| class="TutorialCodeTable-description" |
| class="TutorialCodeTable-description" | e. If the PawnKind requires any minimum skill levels and this pawn does not meet those requirements, discard it
| <source lang="xml">
(inline)
</source>
|-
| class="TutorialCodeTable-description" |
| class="TutorialCodeTable-description" | f. If the PawnKind requires a mimimum combined skill level and the pawn does not meet that requirement, discard it
| <source lang="xml">
(inline)
</source>
|-
| class="TutorialCodeTable-description" |
| class="TutorialCodeTable-description" | g. If the request is for a player starting pawn, the pawn does not meet the scenario requirements, and the pawn generator has not hit the threshold for ignoring scenario requirements, discard it
| <source lang="xml">
(inline)
</source>
|-
| class="TutorialCodeTable-description" |
| class="TutorialCodeTable-description" | h. If the request provided a special validator, the pawn does not pass the validator, and the pawn generator has not hit the threshold for ignoring the validator, discard it
| <source lang="xml">
(inline)
</source>
|-
| class="TutorialCodeTable-description" | '''26'''
| class="TutorialCodeTable-description" | '''Generate pawn gear''' - Does not apply for newborns, mechanoids, or if the request forces no gear (naked brutality)
| <source lang="xml">
GenerateGearFor(Pawn, PawnGenerationRequest)
</source>
|-
| class="TutorialCodeTable-description" |
| class="TutorialCodeTable-description" | a. Generate starting apparel
| <source lang="xml">
PawnApparelGenerator.GenerateStartingApparelFor(Pawn, PawnGenerationRequest)
</source>
|-
| class="TutorialCodeTable-description" |
| class="TutorialCodeTable-description" | b. Generate inventory items
| <source lang="xml">
PawnInventoryGenerator.GenerateInventoryFor(Pawn, PawnGenerationRequest)
</source>
|-
| class="TutorialCodeTable-description" |
| class="TutorialCodeTable-description" | c. Generate equipped weapon (can be disabled by request)
| <source lang="xml">
PawnWeaponGenerator.TryGenerateWeaponFor(Pawn, PawnGenerationRequest)
</source>
|-
| class="TutorialCodeTable-description" | '''27'''
| class="TutorialCodeTable-description" | {{AnomalyIcon}} '''Apply a MutantDef if one is specified by the request or PawnKindDef'''
| <source lang="xml">
MutantUtility.SetFreshPawnAsMutant(Pawn, MutantDef)
</source>
|-
| class="TutorialCodeTable-description" | '''28'''
| class="TutorialCodeTable-description" | '''Add the pawn to the static list of pawns being generated'''
| <source lang="xml">
(inline)
</source>
|-
| class="TutorialCodeTable-description" | '''29'''
| class="TutorialCodeTable-description" | '''If the pawn has a faction, notify the faction of a new member joining'''
| <source lang="xml">
pawn.Faction.Notify_PawnJoined(Pawn);
</source>
|-
| class="TutorialCodeTable-description" | '''30'''
| class="TutorialCodeTable-description" | '''Apply <code>existingDamage</code> entries from PawnKindDef''' - Used by {{AnomalyIcon}} Anomaly for pawns with surgical scars and other similar pre-existing injuries
| <source lang="xml">
ApplyMiscDamage(Pawn, PawnKindDef)
</source>
|-
| class="TutorialCodeTable-description" | '''31'''
| class="TutorialCodeTable-description" | '''Flag pawn's renderer as dirty''' - Forces a regeneration of its render tree
| <source lang="xml">
pawn.Drawer?.renderer?.SetAllGraphicsDirty()
</source>
|-
| class="TutorialCodeTable-description" | '''32'''
| class="TutorialCodeTable-description" | '''Remove the pawn from the static list of pawns being generated''' - Run in a <code>finally</code> block, even if an above step returns early or causes an error
| <source lang="xml">
(inline)
</source>
|-
|}
</div>

[[Category:Modding tutorials]]

Modding Tutorials

2026-07-31T16:56:08Z

Aelanna: Added link to pawn gen guide

{| align=center
| {{Mods_Nav}}
|}
<hr>

This is the hub page for tutorials, guides, and reference materials for creating mods for RimWorld. If you are looking for instructions on how to use RimWorld, please check out the general [[Modding]] hub.

As RimWorld does not have a formal modding API, nearly all of the information here has been gathered and maintained by the modding community.

'''NEW: [[Modding_Tutorials/RimWorld_1.6_Mod_Updates|RimWorld 1.6 Mod Updates]]''' - A work-in-progress list of changes datamined by the modding community in the current unstable version of RimWorld 1.6. '''THERE MAY BE ODYSSEY DLC SPOILERS, YOU HAVE BEEN WARNED.'''

-----

==About RimWorld==
RimWorld is a multi-platform game written on Unity 2022.3.35. However, the Unity Editor is not used for creating mods unless you are creating new shaders or building optional asset bundles.

* [[Modding_Tutorials/Recommended_software|Recommended Software]] - Editors and other useful software for mod development
* [[Modding_Tutorials/Mod_Folder_Structure|Mod Folder Structure]] - Explore the basic folder structure of a mod
** [[Modding_Tutorials/About.xml|About.xml]] - About.xml identifies and describes your mod to RimWorld so that it can be loaded properly

===Game Systems Guides===

* [[Modding_Tutorials/Defs|Defs]] - XML Definitions are used to define and configure content in a way that does not require compiling code
** [[Modding_Tutorials/MayRequire|MayRequire]] - MayRequire and MayRequireAnyOf are used to conditionally load Defs and list entries based on whether a DLC or other mod is loaded
* [[Modding_Tutorials/Localization|Localization]] - Define text strings used for translations and word lists used in name and text generation
* [[Modding_Tutorials/PatchOperations|PatchOperations]] - PatchOperations are used to modify XML Defs without overwriting them completely
* [[Modding_Tutorials/Sounds|Sounds]] - (Needs Rewriting) Adding sound files for mods
* [[Modding_Tutorials/Textures|Textures]] - How to create and add textures to mods
* [[Modding Tutorials/Plant Rendering|Plant Rendering]] - An explanation of how plant textures are rendered
* [[Modding_Tutorials/Research_Projects|Research Projects]] - How to create and use research projects.

===XML Tutorials===

The following are step-by-step tutorials for creating basic content mods.

Basic Tutorials:
* [[Modding_Tutorials/Basic_Melee_Weapon|Basic Melee Weapon]] - How to create a basic melee weapon with a texture mask
* [[Modding_Tutorials/Basic_Ranged_Weapon|Basic Ranged Weapon]] - How to create a basic ranged weapon with custom sound effects
* [[Modding_Tutorials/Basic_Plant|Basic Plant]] - How to create a custom plant with both a cultivated and wild variant
* Custom Animal (Upcoming)
* Simple Building (Upcoming)
* Custom Workbench (Upcoming)
* [[Modding_Tutorials/Custom Drug|Custom Drug]] - How to create a new drug.

Advanced Tutorials:
* Custom Faction (Upcoming)
* Custom Culture (Upcoming)
* Custom Trader Type (Upcoming)

===C# Guides===

C# is used to create and define custom game behaviors

* [[Modding_Tutorials/Decompiling source code|Decompiling Source Code]] - How to set up and use a decompiler to read vanilla game code
* [[Modding_Tutorials/Setting up a solution|Setting up a Solution]] - How to set up a solution for compiling a custom mod assembly
* [[Modding_Tutorials/Application_Startup|Application Startup]] - Describes the application startup process and the order in which game data is loaded
* [[Modding_Tutorials/Pawn_Generation_Process|Pawn Generation Process]] - Describes the steps and relevant code for pawn generation
* Custom Consumable (Upcoming)
* Custom Overlays (Upcoming)
* [[Modding_Tutorials/Code_FloatMenuOptionProvider|FloatMenuOptionProvider]] - How to use <code>FloatMenuOptionProvider</code> to add right click context menu options to arbitrary targets.
* [[Modding_Tutorials/Code_MendingJob|Example Mending Job]] - How to use a <code>FloatMenuOptionProvider</code> in conjunction with a <code>JobDef</code> and <code>JobDriver</code> in order to create a simple mending function for weapons and apparel.

===Updates and Migrations===

* [[Modding_Tutorials/RimWorld_1.5_Mod_Updates|RimWorld 1.5 Mod Updates]] - (WARNING: Anomaly Spoilers) Community notes for updating mods from 1.4 to 1.5.
* [[Modding_Tutorials/RimWorld_1.6_Mod_Updates|RimWorld 1.6 Mod Updates]] - (WARNING: Odyssey Spoilers) Community notes for updating mods from 1.5 to 1.6.

===Testing and Troubleshooting===

* [[Modding Tutorials/Testing mods|Testing Mods]] - Tips and tricks for testing mod content

===Performance and Optimization===

* [[Modding_Tutorials/Asset_Bundles|Asset Bundles]] - How to create Unity asset bundles for assets and shaders.

===Slightly Outdated===

* [[Modding_Tutorials/Plague_Gun|Plague Gun]] - This tutorial was created for RimWorld 1.0 but updated for 1.4. While the exact content is obsolete as you can now accomplish the same result with purely vanilla XML, it is still useful as a crash course for end-to-end mod creation and is here until newer tutorials can replace it.

===Uploading to Steam Workshop===
* You can upload your mod to Steam Workshop by enabling Development Mode from your game Options and then using the Upload option under the Advanced button in the vanilla mod manager.
* Note that in order to upload to Steam Workshop, you must own the game on Steam Workshop. Owning RimWorld on GOG or Epic will not work.
* Your Preview.png should be a 640x360 or 1280x720 PNG and '''must''' be under 1MB. If it is too large, then your upload will be rejected with <code>Error : Limit Exceeded</code>
* If you get a <code>OnItemSubmitted Fail</code> error, make sure you close any programs that are targeting items in your mods folder. This can also mean that Steam Workshop is having some technical issues at the moment. If it keeps occurring, then the only thing to do is to wait a few hours for it to clear up.
* Steam mod descriptions don't use markdown, they use a variant of BBCode. Please check out the [https://steamcommunity.com/comment/Guide/formattinghelp Steam text formatting guide].

-----

'''Note:''' All of the above tutorials have been cleaned up and reviewed by the #mod-development team on the [https://discord.gg/rimworld RimWorld Discord] in cooperation with RimWorld Wiki staff editors. Please let us know before creating, adding, or making any major edits to the vetted tutorials and guides section!

==Outdated / Under Review==

The following tutorials are either out of date or in need of a rewrite. The information in them might be useful but may not be up to standard; please be aware of any potential inaccuracies until they can be addressed.

* [[Modding Tutorials/First Steps|First Steps and Some Links]]
* [[Modding Tutorials/Essence| Essence of Modding]]
* [[Modding Troubleshooting Tips and Guides]]
* [[Modding Tutorials/Sounds|Adding and Testing Sounds]]
* [[Modding Tutorials/Assets|Decompiling Texture/Sound Assets]]
* [[Modding Tutorials/Compatibility|Compatibility]]
* [[Modding_Tutorials/Distribution|Distribution]]
* [[Modding_Tutorials/Modifying defs|Modifying Defs]]
* [[Modding_Tutorials/Troubleshooting|Troubleshooting mods]]
* [[Modding Tutorials/Rituals]]

===XML tutorials===

* [[Modding Tutorials/XML file structure|XML File Structure]]
* [[Modding Tutorials/XML Defs|Introduction to XML Defs]]
** [[Modding Tutorials/Compatibility with defs|XML Def Compatibility]]
** [[Modding Tutorials/ThingDef|ThingDef explained]]
** [[Modding Tutorials/Weapons Guns|Weapons_Guns.xml explained]]. Slightly dated.
* [[Modding Tutorials/Xenotype template]] originally by Ryflamer

===C# tutorials===
* [[Modding_Tutorials/Hello World|Hello World]]
* [[Modding_Tutorials/Writing custom code|Writing Custom Code]]
* [[Modding Tutorials/Linking XML and C#|Linking XML and C#]]
* [[Modding_Tutorials/Harmony|Alter Code at Runtime with Harmony]] - this is a best practice for modifying game code, replacing C# code injection to reduce Mod Conflicts
* [[Modding_Tutorials/Modifying classes|Adding fields and methods to classes]]
* [[Modding Tutorials/ModSettings|Mod settings]] - Add settings to your mod
* [[Modding Tutorials/DefModExtension|Def mod extensions]] - Add (custom) fields to Defs
* [[Modding Tutorials/Custom Comp Classes|Custom Comp Classes]] - A quick overview of what types of Comps there are, and what they're suited for.
* [[Modding_Tutorials/ThingComp|ThingComp]] - Learn all there is to know about ThingComps.
* [[Modding Tutorials/GameComponent|Components]] - GameComponents, WorldComponents, and MapComponents
* [[Modding_Tutorials/Def classes|Introduction to Def Classes]]
* [[Modding_Tutorials/Compatibility_with_DLLs|Using Harmony to optionally patch other mods for the sake of compatibility]]
* [[Modding Tutorials/TweakValue|TweakValues]] - Change values on the fly (handy for quick iteration!)
* [[Modding Tutorials/ExposeData|ExposeData]] - Save stuff
* [[Modding Tutorials/BigAssListOfUsefulClasses|The big ass list of useful classes]] - A non-exhaustive list of classes you'll use most
* [[Modding Tutorials/GrammarResolver|Grammar Resolver]] - PAWN_objective, PAWN_possessive? Find out what it all means here.
* [https://github.com/Mehni/ExampleJob/wiki ExampleJob] - Mehni's top to bottom breakdown of Jobs.
* [[Modding_Tutorials/ConfigErrors|Config Errors]] - Provide configuration issues to the user on startup.
* [[Modding Tutorials/DebugActions|Debug Actions]] - Call methods from the debug menu
* [https://www.arp242.net/rimworld-mod-linux.html Getting started with RimWorld modding on Linux]

===Art Tutorials===
* [https://spdskatr.github.io/RWModdingResources/artstyle Artstyle] - Officially unofficial guide to RimWorld's Artstyle
* Ekksu's animal texture guides: [https://imgur.com/a/how-to-make-rimworld-sprites-its-basically-x-with-y-edition-wS3Pt 1] [https://imgur.com/a/how-to-make-rimworld-sprites-theres-nothing-that-looks-like-this-animal-edition-xdDzg 2]
* [https://steamcommunity.com/sharedfiles/filedetails/?id=1114369188 ChickenPlucker's guide to creating apparel]
* [https://github.com/seraphile/rimshare/wiki/Colouring-in-Images Seraphile's guide to masks]

===Under Construction===

These are currently unfinished and need to be cleaned up or removed

* [[Modding Tutorials/Quests]]
* [[Modding Tutorials/Troubleshooting/Finding Exceptions]]

==External Links==
* [https://github.com/roxxploxx/RimWorldModGuide/wiki Roxxploxx's set of modding tutorials]
* [https://spdskatr.github.io/RWModdingResources/ RimWorld Modding Resources - A hub for guides, modders, practical tips]

[[Category:Modding]]
[[Category:Modding tutorials]]

Template:Apparel Table Row

2026-07-29T15:19:59Z

Aelanna: Added missing pain shock threshold value for ritual mask

<includeonly>
! style='text-align: left !important;'| {{Icon Small|{{{?Name}}}|32}}
! style='text-align: left !important;'| {{DLC Icons|{{{?Name}}} }}
| {{#ifeq: {{#var:TypeColumn}} | true | {{{?Type2}}} {{!!}} }} data-sort-value="{{#if: {{{Sharp}}} | {{{Sharp}}} | {{#if: {{{Sharp2}}} | {{#expr:{{{Sharp2}}}-999}} }} }}" | {{#if: {{{Sharp}}} | ×{{%|{{{Sharp}}} }} | {{#if: {{{Sharp2}}} | {{{Sharp2}}}% | – }} }}
| data-sort-value="{{#if: {{{Blunt}}} | {{{Blunt}}} | {{#if: {{{Blunt2}}} | {{#expr:{{{Blunt2}}}-999}} }} }}" | {{#if: {{{Blunt}}} | ×{{%|{{{Blunt}}} }} | {{#if: {{{Blunt2}}} | {{{Blunt2}}}% | – }} }}
| data-sort-value="{{#if: {{{HeatA}}} | {{{HeatA}}} | {{#if: {{{HeatA2}}} | {{#expr:{{{HeatA2}}}-999}} }} }}" | {{#if: {{{HeatA}}} | ×{{%|{{{HeatA}}} }} | {{#if: {{{HeatA2}}} | {{{HeatA2}}}% | – }} }}
| {{#ifeq: {{{?Type2}}}|Body Parts| data-sort-value="99999"{{!}} – |{{#if: {{{HP}}} | {{{HP}}} | – }}}}
| {{#if: {{{Coverage}}} | {{{Coverage}}} | – }}
| data-sort-value="{{#if: {{{Cold}}} | {{{Cold}}} | {{#if: {{{Cold2}}} | {{#expr:{{{Cold2}}}-999}} }} }}" | {{#if: {{{Cold}}} | {{%|{{{Cold}}} }} | {{#if: {{{Cold2}}} | -{{Temperature|{{{Cold2}}}||delta}} | – }} }}
| data-sort-value="{{#if: {{{HeatI}}} | {{{HeatI}}} | {{#if: {{{HeatI2}}} | {{#expr:{{{HeatI2}}}-999}} }} }}" | {{#if: {{{HeatI}}} | {{%|{{{HeatI}}} }} | {{#if: {{{HeatI2}}} | +{{Temperature|{{{HeatI2}}}||delta}} | – }} }}
| {{#switch: {{{?Name}}}
| #default = –
| Cowboy hat | Beret = {{+|10%}} [[Social impact]]
| Bowler hat | Tribal headdress = {{+|15%}} [[Social impact]]
| Coronet | Crown | Hood | Ladies hat | Stellic crown | Top hat = {{+|20%}} [[Social impact]]
| Torture crown = {{++|5%}} [[Pain]]
| Veil = {{+|5%}} [[Pain shock threshold]]
| War mask = {{+|10%}} [[Pain shock threshold]]
| Ritual mask = {{+|15%}} [[Pain shock threshold]]
| Psychic foil helmet = '''−90%''' [[Psychic sensitivity]]
| Blindfold = {{Bad|max 20%}} [[Sight]]
| Eltex helmet = Quality dependent increase to [[Psychic sensitivity]],<br/>{{+|0.066}} <abbr title="heat per second">h/s</abbr> [[Neural heat recovery rate]]
| Eltex skullcap = Quality dependent increase to [[Psychic sensitivity]],<br/>{{+|0.091}} <abbr title="heat per second">h/s</abbr> [[Neural heat recovery rate]]
| Eltex robe = Quality dependent increase to [[Psychic sensitivity]],<br/>{{+|0.091}} <abbr title="heat per second">h/s</abbr> [[Neural heat recovery rate]]
| Eltex vest = Quality dependent increase to [[Psychic sensitivity]],<br/>{{+|0.05}} <abbr title="heat per second">h/s</abbr> [[Neural heat recovery rate]]
| Eltex shirt = Quality dependent increase to [[Psychic sensitivity]],<br/>{{+|0.033}} <abbr title="heat per second">h/s</abbr> [[Neural heat recovery rate]]
| Authority cap = {{+|10%}} [[Suppression|Slave suppression offset]]
| Slave collar | Slave body strap = {{+|15%}} [[Suppression|Slave suppression offset]]
| Burka = {{--|0.4}} {{CS}} [[Move speed]]
| Flak jacket | Flak pants | Flak vest = {{--|0.12}} {{CS}} [[Move speed]]
| Marine armor = {{--|0.25}} {{CS}} [[Move speed]]
| Grenadier armor = {{--|0.25}} {{CS}} [[Move speed]],<br/>built-in '''frag grenade launcher'''
| Prestige marine armor = {{--|0.4}} {{CS}} [[Move speed]],<br/>'''+5%''' [[Psychic sensitivity]],<br/>{{+|0.033}} <abbr title="heat per second">h/s</abbr> [[Neural heat recovery rate]]
| Plate armor = {{--|0.8}} {{CS}} [[Move speed]]
| Cataphract armor = {{--|0.5}} {{CS}} [[Move speed]]
| Locust armor = built-in '''burst rocket'''
| Prestige recon armor | Prestige marine helmet | Prestige recon helmet | Prestige cataphract helmet = '''+5%''' [[Psychic sensitivity]],<br/>{{+|0.033}} <abbr title="heat per second">h/s</abbr> [[Neural heat recovery rate]]
| Phoenix armor = {{--|0.5}} {{CS}} [[Move speed]],<br/>{{---|68%}} [[Flammability]],<br/>built-in '''flamebolt launcher'''
| Prestige cataphract armor = {{--|0.5}} {{CS}} [[Move speed]],<br/>'''+5%''' [[Psychic sensitivity]],<br/>{{+|0.033}} <abbr title="heat per second">h/s</abbr> [[Neural heat recovery rate]]
| Airwire headset = {{+|3}} [[Bandwidth]]
| Array headset = {{+|6}} [[Bandwidth]]
| Integrator headset = {{+|9}} [[Bandwidth]]
| Mechcommander helmet = {{+|6}} [[Bandwidth]]
| Mechlord helmet = {{+|12}} [[Bandwidth]]<br/>{{--|5}} [[Shooting accuracy]]<br/>{{--|0.5}} [[Melee hit chance]]
| Mechlord suit = {{+|12}} [[Bandwidth]]<br/>{{--|5}} [[Shooting accuracy]]<br/>{{--|0.5}} [[Melee hit chance]]
| Face mask = {{+|50%}} [[Toxic environment resistance]]
| Gas mask = {{+|80%}} [[Toxic environment resistance]]
| Lab coat = {{+|5%}} [[Research Speed]]<br/>{{+|10%}} [[Entity Study Rate]]
| Heavy bandolier = {{---|20%}} [[Ranged cooldown multiplier]]
| Gunlink = {{+|3}} [[Shooting accuracy]]
| Vacsuit = {{--|1.25}} {{CS}} [[Move speed]],<br/>{{+|32%}} [[Vacuum resistance]]
| Vacsuit helmet = {{+|69%}} [[Vacuum resistance]],<br/>{{+|80%}} [[Toxic environment resistance]]
| Armorskin gland = {{Bad|x90%}} [[Moving]],<br/>{{--|1}} [[Beauty]]
| Stoneskin gland = {{Bad|x85%}} [[Moving]],<br/>{{--|2}} [[Beauty]]
| Toughskin gland = {{Bad|x95%}} [[Moving]]
}}
| {{#if: {{{Research}}} | [[Research#{{{Research}}}|{{{Research}}}]] | – }}
| data-sort-value="{{formatnum:{{{Work}}}|R}}" | {{#if: {{{Work}}} | {{Ticks|{{{Work}}} }} | – }}
| data-sort-value="{{{R1a}}}" | {{#if: {{{R1}}} | {{Required Resources|{{{?Name}}}|simple=1}} | – }}
| data-sort-value="{{#vardefineecho:value | {{#if: {{{Value}}} | {{formatnum:{{{Value}}}|R}} | {{#if: {{Market Value Calculator|{{{?Name}}}|wood}} | {{Market Value Calculator|{{{?Name}}}|wood}} }} }} }}" | {{#if: {{#var:value}} | {{Icon Small|Silver}} {{#var:value}} | – }}
| {{#if: {{{Work}}} | {{#ifexpr: {{formatnum:{{{Work}}}|R}} > 0 | {{#if: {{#var:value}} | {{#expr: {{#var:value}} / {{formatnum:{{{Work}}}|R}} round 3}} | – }} | – }} | – }}
| {{#if: {{#var:value}} | {{#if: {{{R1a}}} | {{#expr: {{#var:value}} / {{{R1a}}} round 2}} | – }} | – }}
|-
</includeonly><noinclude>{{Recode|reason=Missing most of Vacuum resistance values}}{{Documentation}}
</noinclude>

Modding Troubleshooting Tips and Guides

2026-07-28T00:15:13Z

Aelanna:

{| align=center
| {{Basics_Nav}}
|}
----

{{TOCright}}
== Basic Troubleshooting Things You Should Do ==

"My game broke/crashed/the UI is gone/froze, what do I do?"

'''''You should:'''''

- Verify with Steam (if you use it to run Rimworld).

- Clear your configs (instructions below).

- Check your mod order (instructions also below).

- Remove any mods that are out of date to the base game version. No I do not care if Steam comments say it works fine. Remove it anyway.

- Remove any mods that have been "vibe coded" or rather coded by an automatic generator, LLM, AI slopbot, or other lack of intelligence. These suck and break things constantly, and no modlist that contains these mods will have their errors taken seriously.

- Restart after all this has been done.

- If these do not fix it (and you actually did them), proceed to the section on reporting errors to mod devs.

-----------------

=== Basic Load Order Rules: ===

-Mods actually care what order they are loaded in when it comes to Rimworld. If you came from something like modded Minecraft this is probably exceptionally weird to you. The order in which mods need to be loaded is entirely dependant on the mods themselves and what they're doing, and gets complex very fast. The in-game mod sorter, like the base game log, *exists*, but is not great.
Luckily, people have made an auto-sorter program specifically to combat this issue. It's called Rimsort, and is a fork of Rimpy which does the same thing but may not have been updated in a while. This is an external program you have to download and sadly may not work on all OSs.
If that is the case for you, or you just don't want to download stuff outside the Steam ecosystem, there is an older guide that may at least be somewhat helpful.
Other guides exist (though I cannot personally vouch for them one way or the other). Your mileage may vary for any or all of these methods.

=+=

RimSort is a useful tool that works outside the game, to make it easier to sort your mods. It also has it's own auto-sort function if you want to see if that will help your issue:

https://github.com/RimSort/RimSort

There are also a few mod managers out there, both as mods and as external programs.

Another option for sorting your mods is to follow this guide here:

https://rwom.fandom.com/wiki/Mod_Order_Guide

=+=

The basic idea behind mod load order is below:

-Mods must be loaded beneath any and all dependencies.
eg: Most mods depend on Core to function and must load below it.

-Mods should not/cannot be loaded with other incompatible mods.

-How do we know which mods are incompatible? Reading mod descriptions, asking people who know things, and trial/error.

-In the instance of multiple mods that change the same thing, whichever is loaded last will take precedence.
There are some "ifs" and "buts" in this statement, but it's largely true.

=== Local Mods: ===

Windows:
C:\Program Files (x86)\Steam\steamapps\common\RimWorld\Mods

or
C:\Program Files (x86)\RimWorld\Mods

Mac OS X:
Right-click the RimWorld application and show package contents
cd Library/Application\ Support/Steam/steamapps/common/RimWorld

Linux:
~/.steam/steam/steamapps/common/Rimworld/Mods;

=== Config Files: ===
-Clear your config files. This is done because they are not automatically removed if you remove a mod, or updated if you change versions. This lack of cleanup can cause weird unusual issues if not dealt with.

> RimWorld configuration files and most mod settings are kept in this folder, and removing them will reset all settings to default.

> "Clearing configs" refers to deletion of old/all configs and config files in the aforementioned folder

> Save the "ModsConfig.xml" as this is your mod load order, and if you remove it you will lose your modded load order.

> The Windows location is here, check the wiki for other OSs locations: %appdata%\..\LocalLow\Ludeon Studios\RimWorld by Ludeon Studios\Config

=== Steam Default Install Location (Windows): ===
C:\Program Files (x86)\Steam\steamapps\common

=== Steam Default Mod Install Folder (Windows): ===
C:\Program Files (x86)\Steam\steamapps\workshop\content\294100

=== Verify Game Files with Steam: ===

> Steam Library

> Right Click RimWorld

> Properties

> Local Files

> "Verify integrity of game files". Wait until Steam tells you the files have been checked, and has fixed any issues it encountered.

=== Change Game Version with Steam: ===

> Steam Library

> Right Click RimWorld

> Properties

> Betas

> "Select the beta you would like to opt into:"

=== Hugslog Instructions ===

> Go to Game Options

> Turn on Dev mode

> Click the white button at the top of the screen that opens the logging function (they keep changing where this button is in the row, don't @ me). Otherwise press CTRL + F12

> A console log window should have now appeared. If you have Hugslib, there should be a green "Share Logs" button at the bottom of this window. Press it

> Post the resulting link to share your Hugslog

--------------------------

=== So you want to report a mod error to a mod dev... ===

-First, you need to understand that Rimworld's logging *exists*, but is not great. There is a REASON why there are multiple mods that have popped up over the games lifetime that try to make it better. Part of this is that the devs of the base game cannot reasonably have planned for everything mods might do that would need to show up in a log.
...But also the logs are still kinda bad so-

-Currently, as previously stated, there are a few mods that try to make this better, spread out across various versions of the base game. These include Hugslib, Rocketman and CAI 9000, Achtung, etc. These mods sometimes run messages about what they find and label it with their own name at the start to show what is *finding* the error. This does not mean that the logging mod is *causing* the error, they're adding their name for record keeping purposes.
-DO NOT RUN MODS THAT ARE FOR A PREVIOUS VERSION OF THE GAME, you will be yeeted into the sun if you do, you have been warned. Do your due diligence and check what version a mod is for.

-Hugslib has been fairly consistent across the versions, and is the default recommendation for getting logs you can read and post elsewhere. There is a separate Hugslib Log Publisher if that's your jam. Both are on Steam.

--------------------------

=== How do you determine if an error needs to be reported to begin with? ===

-There is a checklist of things you need to do before you go to report an error to a mod dev. Do not skip steps on this list, because devs and troubleshooters will likely refuse to help you until you complete them.
That checklist is at the top of this page.
If the checklist does not solve the problem, and you actually went through it and did everything on it, proceed to the next section.

--------------------------

=== Now then, we need to figure out if an error needs to be reported to a specific dev. ===

-Sadly, there is no simple way to do this. As previously mentioned, some loggers will add their names into the error report, which has caused headaches for those devs over the years because people see that name, and assume it's that mods fault.

-Stacktraces, which are a list of mods potentially involved in an error and what they were doing, will give you a few more options. However Just because a mod is in a stacktrace it still doesn't mean that the mod is CAUSING the error, it just means something that mod is doing was also affecting the bugged *thing* at the time. Stacktraces are not there to diagnose the problem, they're there to let you see all the code-bumper-cars running around so you can maybe figure out why a ten car pileup just happened. They're a snapshot, basically.

-Devs will occasionally be able to read an error and go "oh, that method I was using to affect the pawn's eating habits is breaking because I forgot a parenthesis on line 432, fixed". This is exceedingly rare, and usually it's more of a hunt for a needle in a straw bale, but logging can at least tell you which part of the bale you should be looking in.

-Rimworld (with Hugslib) logs start with a list of loaded mods, then a list of "methods" that are all the major things mods are doing. If an error mentions one of these methods, that can be but is NOT GUARANTEED to be an indicator of what is causing a problem. Many errors are the result of multiple mods interacting in weird arcane ways the mod devs did not foresee, and the one being named is not necessarily the culprit, though you should probably inform that dev of the error anyway.

-Sometimes something breaks and there is no log for it whatsoever, or the error message is unreadable or decidedly not helpful. This sucks and can happen for a variety of reasons. The best you can do here is basic mod maintenance, which was discussed before, and once that is done (assuming that didn't fix it) you can ask around to see if anyone else has encountered the issue.

--------------------------

=== How do you report an error to a dev, in a manner that won't cause them to yeet you into the sun anyway? ===

-Do the checklist. Gee I wonder why this is constantly posted throughout this guide, it can't possibly be because people skip it thinking that it couldn't possibly solve their problem, until it does when they're forced to by a troubleshooter or mod dev five minutes later. How could that ever be the case.

-Give a DETAILED explanation of your error, what kind of state your game is currently in (just landed, early game, late game, travelling to the location ending, etc.), and provide a Hugslog. You will not be taken seriously if you do not provide a log, and lack of detail will mean you have to sit there for days or weeks while the mod dev finds the time to quiz you about the details. Over Steam comments. Assuming they even pay attention to those comments because Steam comment sections suck.
Instructions for the Hugslog are above.

-For that matter, check the description of the mod to see if the dev has a discord server or github. They usually do, and with a large notable exception they do in fact take bug reports there. They work far better than Steam comments do, so use them.

--------------------------

''
'''An explanation of how this works code wise;'''

"Keep in mind that not all mod conflicts will be solved by shuffling load order around. Sometimes mods are just incompatible until the mod authors put in effort to fix their mods.

Sometimes mods will just be incompatible.

As with most things, the truth is a bit more fine-grained. It's true that "Core, Mod 1, Mod 2, Mod 3" is the load order, and the last mod "wins", but the actual load order is a bit different.

- XML

- xpath

- C#

The game first loads all XML (defs, mostly) from Core, Mod 1, Mod 2, Mod 3

Then it applies all xpath patches from Mod 1, Mod 2, Mod 3

Then it loads the C# from Mod 1, Mod 2, Mod 3

Core doesn't use xpath or load any C#, so they're not in that list. The C# for RimWorld is already loaded by that point, roughly speaking.

So if Mod 3 overwrites something in XML, but Mod 2 overwrites it in xpath and Mod 1 overwrites it in C#, it's Mod 1 that wins -- even though Mod 3 and Mod 2 come after it in the load order.

There are a few things that matter with load order:

- Does the mod require a different mod? Examples of that are mods that require HugsLib, Proper Shotguns, Turret Extensions, Alien Races, JecsTools, whatever. If you are missing a dependency, you'll notice: You get a nice red error saying something like
Could not find type named TurretExtensions.CompProperties_Upgradable from node <A lot of XML> and missing a dependency like that will put the entire game in a corrupted and unplayable state.

And then there is another insidious thing some XML mods do: overwrite (abstract) bases. For that, I refer you to https://github.com/RimWorld-CCL-Reborn/AllYourBase. This is something that's still unfortunately very frequently done, and it can cause havoc.

The C# summary slightly diverts from the truth. It even depends on how they instantiate the mod; there are two or three possible hooks and they happen at different times. Most mods that mess about with Defs will all have to do it in the second or third hook.

There's inherit from mod, which happens before Defs are loaded. Generally mods can't screw around with Defs in there.

There's the staticconstructoronstartup annotation which happens after Defs are loaded. This is where mods would screw around with Defs, for the most part.

Finally there's Hugslibs' ondefsloaded, which is exactly like a staticconstructoronstartup, but it runs after the staticconstructoronstartup utility is done.

and fwiw: that's just the Defs side of the equation

I won't even mention the harmony conflicts (which are way harder to detect) or runtime conflicts (which sometimes get logged, but not nearly always)

take the world edit mod: I can't remember which page it was, but basically if you click next somewhere and from there on you get redirected to world edit's version of whatever the next screen would've been.

There's like.. almost zero chance of detecting that programmatically"''

--------------------------

''

=== Common things people do that they should be doing differently ===

-Do not run out of date mods. This means mods that are for a different version of the game than you are running. The only exception is Allyourbase at this time.

-If asked to add and use Allyourbase, do NOT turn on Verbose Logging till you are asked to do so.

-Do not run two copies of the same mod. This causes things to break horribly.

-Do not use modpacks. They are almost always partially out of date, almost always partially broken, and you will be told to make your own list if you present them to a troubleshooter.
Also Samuel Streamer needs to either stop editing around all the dev commands they use, or they need to stop giving people the packs without FIXING them first.

-Do not come into a troubleshooting area with "Can someone help?" and nothing else. Do not even come into such an area with that and a log. Come with a description of your problem, AND a log, so that troubleshooters do not have to spend multiple minutes asking for a description of your problem.

-If a troubleshooter asks you to do something that does not ACTUALLY BREAK LAWS OR PUT YOU IN HARMS WAY, do it. Even if you did it already. You're not being asked as a delaying tactic, or as a power trip; you are being asked to do that thing so that they can help you fix your game.

-If you come from modding Skyrim or Fallout and you are used to the LOOT filter: Guess what, Rimpy exists, it hasn't had enough time to get to where LOOT is (though the devs are working on it). Use it.

-Always provide a Hugslog if possible. Yes, even if it has to come from the main menu. Yes, even if it has to come from a restart before the error occurs. It will STILL be useful. (Hugslogs are acquired by adding the Hugslib mod, and then either pressing Ctrl+F12 while in game, or navigating to the dev mode console window and hitting the green "Share Logs" button.)

-It's (almost always) not Achtung or Rocketman.
~Both of these mods check what other mods are doing to try to make bugs easier to notice and fix. They are probably not the cause of whatever they catch.

=== YOU NEED HARMONY ===
Harmony is a library critical to the function of many complex mods. If you remove it, any mods that require it will explosively break!

== Further Help ==

Every mod list is different and sometimes general rules aren't enough to solve a particularly unique issue. If you are still having issues after following these guidelines, consider checking out the #troubleshooting channel on the [https://discordapp.com/invite/UTaMDWc RimWorld Discord server] and follow the posted instructions to get direct help from a volunteer troubleshooter!

[[Category:Modding]]

Modding Tutorials

2026-07-22T19:28:18Z

Aelanna: /* XML Tutorials */

{| align=center
| {{Mods_Nav}}
|}
<hr>

This is the hub page for tutorials, guides, and reference materials for creating mods for RimWorld. If you are looking for instructions on how to use RimWorld, please check out the general [[Modding]] hub.

As RimWorld does not have a formal modding API, nearly all of the information here has been gathered and maintained by the modding community.

'''NEW: [[Modding_Tutorials/RimWorld_1.6_Mod_Updates|RimWorld 1.6 Mod Updates]]''' - A work-in-progress list of changes datamined by the modding community in the current unstable version of RimWorld 1.6. '''THERE MAY BE ODYSSEY DLC SPOILERS, YOU HAVE BEEN WARNED.'''

-----

==About RimWorld==
RimWorld is a multi-platform game written on Unity 2022.3.35. However, the Unity Editor is not used for creating mods unless you are creating new shaders or building optional asset bundles.

* [[Modding_Tutorials/Recommended_software|Recommended Software]] - Editors and other useful software for mod development
* [[Modding_Tutorials/Mod_Folder_Structure|Mod Folder Structure]] - Explore the basic folder structure of a mod
** [[Modding_Tutorials/About.xml|About.xml]] - About.xml identifies and describes your mod to RimWorld so that it can be loaded properly

===Game Systems Guides===

* [[Modding_Tutorials/Defs|Defs]] - XML Definitions are used to define and configure content in a way that does not require compiling code
** [[Modding_Tutorials/MayRequire|MayRequire]] - MayRequire and MayRequireAnyOf are used to conditionally load Defs and list entries based on whether a DLC or other mod is loaded
* [[Modding_Tutorials/Localization|Localization]] - Define text strings used for translations and word lists used in name and text generation
* [[Modding_Tutorials/PatchOperations|PatchOperations]] - PatchOperations are used to modify XML Defs without overwriting them completely
* [[Modding_Tutorials/Sounds|Sounds]] - (Needs Rewriting) Adding sound files for mods
* [[Modding_Tutorials/Textures|Textures]] - How to create and add textures to mods
* [[Modding Tutorials/Plant Rendering|Plant Rendering]] - An explanation of how plant textures are rendered
* [[Modding_Tutorials/Research_Projects|Research Projects]] - How to create and use research projects.

===XML Tutorials===

The following are step-by-step tutorials for creating basic content mods.

Basic Tutorials:
* [[Modding_Tutorials/Basic_Melee_Weapon|Basic Melee Weapon]] - How to create a basic melee weapon with a texture mask
* [[Modding_Tutorials/Basic_Ranged_Weapon|Basic Ranged Weapon]] - How to create a basic ranged weapon with custom sound effects
* [[Modding_Tutorials/Basic_Plant|Basic Plant]] - How to create a custom plant with both a cultivated and wild variant
* Custom Animal (Upcoming)
* Simple Building (Upcoming)
* Custom Workbench (Upcoming)
* [[Modding_Tutorials/Custom Drug|Custom Drug]] - How to create a new drug.

Advanced Tutorials:
* Custom Faction (Upcoming)
* Custom Culture (Upcoming)
* Custom Trader Type (Upcoming)

===C# Guides===

C# is used to create and define custom game behaviors

* [[Modding_Tutorials/Decompiling source code|Decompiling Source Code]] - How to set up and use a decompiler to read vanilla game code
* [[Modding_Tutorials/Setting up a solution|Setting up a Solution]] - How to set up a solution for compiling a custom mod assembly
* [[Modding_Tutorials/Application_Startup|Application Startup]] - Describes the application startup process and the order in which game data is loaded
* Custom Consumable (Upcoming)
* Custom Overlays (Upcoming)
* [[Modding_Tutorials/Code_FloatMenuOptionProvider|FloatMenuOptionProvider]] - How to use <code>FloatMenuOptionProvider</code> to add right click context menu options to arbitrary targets.
* [[Modding_Tutorials/Code_MendingJob|Example Mending Job]] - How to use a <code>FloatMenuOptionProvider</code> in conjunction with a <code>JobDef</code> and <code>JobDriver</code> in order to create a simple mending function for weapons and apparel.

===Updates and Migrations===

* [[Modding_Tutorials/RimWorld_1.5_Mod_Updates|RimWorld 1.5 Mod Updates]] - (WARNING: Anomaly Spoilers) Community notes for updating mods from 1.4 to 1.5.
* [[Modding_Tutorials/RimWorld_1.6_Mod_Updates|RimWorld 1.6 Mod Updates]] - (WARNING: Odyssey Spoilers) Community notes for updating mods from 1.5 to 1.6.

===Testing and Troubleshooting===

* [[Modding Tutorials/Testing mods|Testing Mods]] - Tips and tricks for testing mod content

===Performance and Optimization===

* [[Modding_Tutorials/Asset_Bundles|Asset Bundles]] - How to create Unity asset bundles for assets and shaders.

===Slightly Outdated===

* [[Modding_Tutorials/Plague_Gun|Plague Gun]] - This tutorial was created for RimWorld 1.0 but updated for 1.4. While the exact content is obsolete as you can now accomplish the same result with purely vanilla XML, it is still useful as a crash course for end-to-end mod creation and is here until newer tutorials can replace it.

===Uploading to Steam Workshop===
* You can upload your mod to Steam Workshop by enabling Development Mode from your game Options and then using the Upload option under the Advanced button in the vanilla mod manager.
* Note that in order to upload to Steam Workshop, you must own the game on Steam Workshop. Owning RimWorld on GOG or Epic will not work.
* Your Preview.png should be a 640x360 or 1280x720 PNG and '''must''' be under 1MB. If it is too large, then your upload will be rejected with <code>Error : Limit Exceeded</code>
* If you get a <code>OnItemSubmitted Fail</code> error, make sure you close any programs that are targeting items in your mods folder. This can also mean that Steam Workshop is having some technical issues at the moment. If it keeps occurring, then the only thing to do is to wait a few hours for it to clear up.
* Steam mod descriptions don't use markdown, they use a variant of BBCode. Please check out the [https://steamcommunity.com/comment/Guide/formattinghelp Steam text formatting guide].

-----

'''Note:''' All of the above tutorials have been cleaned up and reviewed by the #mod-development team on the [https://discord.gg/rimworld RimWorld Discord] in cooperation with RimWorld Wiki staff editors. Please let us know before creating, adding, or making any major edits to the vetted tutorials and guides section!

==Outdated / Under Review==

The following tutorials are either out of date or in need of a rewrite. The information in them might be useful but may not be up to standard; please be aware of any potential inaccuracies until they can be addressed.

* [[Modding Tutorials/First Steps|First Steps and Some Links]]
* [[Modding Tutorials/Essence| Essence of Modding]]
* [[Modding Troubleshooting Tips and Guides]]
* [[Modding Tutorials/Sounds|Adding and Testing Sounds]]
* [[Modding Tutorials/Assets|Decompiling Texture/Sound Assets]]
* [[Modding Tutorials/Compatibility|Compatibility]]
* [[Modding_Tutorials/Distribution|Distribution]]
* [[Modding_Tutorials/Modifying defs|Modifying Defs]]
* [[Modding_Tutorials/Troubleshooting|Troubleshooting mods]]
* [[Modding Tutorials/Rituals]]

===XML tutorials===

* [[Modding Tutorials/XML file structure|XML File Structure]]
* [[Modding Tutorials/XML Defs|Introduction to XML Defs]]
** [[Modding Tutorials/Compatibility with defs|XML Def Compatibility]]
** [[Modding Tutorials/ThingDef|ThingDef explained]]
** [[Modding Tutorials/Weapons Guns|Weapons_Guns.xml explained]]. Slightly dated.
* [[Modding Tutorials/Xenotype template]] originally by Ryflamer

===C# tutorials===
* [[Modding_Tutorials/Hello World|Hello World]]
* [[Modding_Tutorials/Writing custom code|Writing Custom Code]]
* [[Modding Tutorials/Linking XML and C#|Linking XML and C#]]
* [[Modding_Tutorials/Harmony|Alter Code at Runtime with Harmony]] - this is a best practice for modifying game code, replacing C# code injection to reduce Mod Conflicts
* [[Modding_Tutorials/Modifying classes|Adding fields and methods to classes]]
* [[Modding Tutorials/ModSettings|Mod settings]] - Add settings to your mod
* [[Modding Tutorials/DefModExtension|Def mod extensions]] - Add (custom) fields to Defs
* [[Modding Tutorials/Custom Comp Classes|Custom Comp Classes]] - A quick overview of what types of Comps there are, and what they're suited for.
* [[Modding_Tutorials/ThingComp|ThingComp]] - Learn all there is to know about ThingComps.
* [[Modding Tutorials/GameComponent|Components]] - GameComponents, WorldComponents, and MapComponents
* [[Modding_Tutorials/Def classes|Introduction to Def Classes]]
* [[Modding_Tutorials/Compatibility_with_DLLs|Using Harmony to optionally patch other mods for the sake of compatibility]]
* [[Modding Tutorials/TweakValue|TweakValues]] - Change values on the fly (handy for quick iteration!)
* [[Modding Tutorials/ExposeData|ExposeData]] - Save stuff
* [[Modding Tutorials/BigAssListOfUsefulClasses|The big ass list of useful classes]] - A non-exhaustive list of classes you'll use most
* [[Modding Tutorials/GrammarResolver|Grammar Resolver]] - PAWN_objective, PAWN_possessive? Find out what it all means here.
* [https://github.com/Mehni/ExampleJob/wiki ExampleJob] - Mehni's top to bottom breakdown of Jobs.
* [[Modding_Tutorials/ConfigErrors|Config Errors]] - Provide configuration issues to the user on startup.
* [[Modding Tutorials/DebugActions|Debug Actions]] - Call methods from the debug menu
* [https://www.arp242.net/rimworld-mod-linux.html Getting started with RimWorld modding on Linux]

===Art Tutorials===
* [https://spdskatr.github.io/RWModdingResources/artstyle Artstyle] - Officially unofficial guide to RimWorld's Artstyle
* Ekksu's animal texture guides: [https://imgur.com/a/how-to-make-rimworld-sprites-its-basically-x-with-y-edition-wS3Pt 1] [https://imgur.com/a/how-to-make-rimworld-sprites-theres-nothing-that-looks-like-this-animal-edition-xdDzg 2]
* [https://steamcommunity.com/sharedfiles/filedetails/?id=1114369188 ChickenPlucker's guide to creating apparel]
* [https://github.com/seraphile/rimshare/wiki/Colouring-in-Images Seraphile's guide to masks]

===Under Construction===

These are currently unfinished and need to be cleaned up or removed

* [[Modding Tutorials/Quests]]
* [[Modding Tutorials/Troubleshooting/Finding Exceptions]]

==External Links==
* [https://github.com/roxxploxx/RimWorldModGuide/wiki Roxxploxx's set of modding tutorials]
* [https://spdskatr.github.io/RWModdingResources/ RimWorld Modding Resources - A hub for guides, modders, practical tips]

[[Category:Modding]]
[[Category:Modding tutorials]]

Modding Tutorials/Custom Drug

2026-07-22T19:27:17Z

Aelanna: Adding review banner

{{DISPLAYTITLE:Custom Drug}}
{{BackToTutorials}}

{{:Modding_Tutorials/Under_Review}}

In this simple RimWorld tutorial, we will create a custom drug, complete with its own hediff and sprite.

== Goals ==
In this tutorial you will:

* Create [[Modding_Tutorials/ThingDef|ThingDef]]s for a '''new drug''': xylin, a potent yet addictive painkiller.
* Assign '''custom stackable textures''' to your new drug
* Create a new [[Modding_Tutorials/RecipeDef|RecipeDef]] to '''craft xylin''', yielding this new drug

== Folder Setup ==
First, you will want to set up your mod folder in this order:

<source>
Mods
└ MyModFolder
├ About
│ └ About.xml
├ Defs
│ └ ThingDefs_Items
│ └ ExampleItem_Xylin.xml
└ Textures
└ ExampleMod
└ Xylin
├ Xylin_a.png
└ Xylin_b.png
</source>

=== About.xml ===
The <code>about.xml</code> is used to register the mod with RimWorld; the template below should act as a baseline.
<source>
<?xml version="1.0" encoding="UTF-8"?>
<ModMetaData>
<name>CustomDrug</name>
<author>YourName</author>

<packageId>YourName.CustomDrug</packageId>

<description>ExampleDescription</description>
<supportedVersions>

<li>1.6</li>
</supportedVersions>
</ModMetaData>
</source>

=== Sample Assets ===
You can use these as the example textures:
<div class="TwoColumnCollapsibleLayout">
<div class="TwoColumnCollapsibleLayout-section">
<div class="TwoColumnCollapsibleLayout-subtitle">Single graphic</div>
<div class="TwoColumnCollapsibleLayout-text">
[[File:CustomDrug_Xylin_a.png|none]]
</div>
</div>
<div class="TwoColumnCollapsibleLayout-section">
<div class="TwoColumnCollapsibleLayout-subtitle">Full stack graphic</div>
<div class="TwoColumnCollapsibleLayout-text">
[[File:CustomDrug_Xylin_b.png|none]]
</div>
</div>

== Instructions ==
=== 1. Create drug ThingDefs ===
Internally, the addiction system is relatively consistent across all drugs, so we will be using the def block of [[Smokeleaf]] as a template. The XML for [[Smokeleaf]] can be found in <code>Data/Core/Defs/Drugs/Smokeleaf.xml</code>

After copying the def, we'll alter it to look like this:
<source>
<?xml version="1.0" encoding="utf-8" ?>
<Defs>
<ThingDef ParentName="MakeableDrugBase">
<defName>XylinDrug</defName>
<label>xylin</label>
<description>Description goes here.</description>
<possessionCount>5</possessionCount>
<descriptionHyperlinks>
<HediffDef>XylinHigh</HediffDef>
</descriptionHyperlinks>
<graphicData>

<texPath>ExampleMod/Xylin</texPath>
<graphicClass>Graphic_StackCount</graphicClass>
</graphicData>
<rotatable>false</rotatable>
<statBases>
<WorkToMake>450</WorkToMake>

<MarketValue>16</MarketValue>
<Mass>0.05</Mass>
<DeteriorationRate>6</DeteriorationRate>
<Flammability>1.3</Flammability>
</statBases>
<techLevel>Industrial</techLevel>
<ingestible>
<foodType>Plant, Fluid</foodType>

<baseIngestTicks>80</baseIngestTicks>
<nurseable>true</nurseable>

<drugCategory>Medical</drugCategory>
<ingestSound>Ingest_Inject</ingestSound>
<ingestEffectEat>EatVegetarian</ingestEffectEat>
<ingestHoldOffsetStanding>
<northDefault>
<offset>(0.18,0,0)</offset>
</northDefault>
</ingestHoldOffsetStanding>

<ingestHoldUsesTable>false</ingestHoldUsesTable>
<ingestCommandString>Inject {0}</ingestCommandString>
<ingestReportString>Injecting {0}.</ingestReportString>
<ingestReportStringEat>Consuming {0}.</ingestReportStringEat>

<useEatingSpeedStat>false</useEatingSpeedStat>
<outcomeDoers>
<li Class="IngestionOutcomeDoer_GiveHediff">
<hediffDef>XylinHigh</hediffDef>

<severity>1.0</severity>
</li>

</outcomeDoers>
</ingestible>

<recipeMaker>
<recipeUsers>

<li>DrugLab</li>
</recipeUsers>
<workSpeedStat>DrugCookingSpeed</workSpeedStat>
<workSkill>Cooking</workSkill>

<displayPriority>2000</displayPriority>
</recipeMaker>
<costList>

<Chemfuel>4</Chemfuel>
</costList>
<comps>
<li Class="CompProperties_Drug">

<listOrder>20</listOrder>
</li>
</comps>
<allowedArchonexusCount>50</allowedArchonexusCount>
</ThingDef>
<HediffDef>
<defName>XylinHigh</defName>
<label>high on xylin</label>
<labelNoun>a xylin high</labelNoun>
<description>Xylin's active chemical in the bloodstream. Dulls pain.</description>
<hediffClass>Hediff_High</hediffClass>
<defaultLabelColor>(1,0,0.5)</defaultLabelColor>
<scenarioCanAdd>true</scenarioCanAdd>
<maxSeverity>1.0</maxSeverity>
<isBad>false</isBad>
<comps>
<li Class="HediffCompProperties_SeverityPerDay">

<severityPerDay>-0.5</severityPerDay>
<showHoursToRecover>true</showHoursToRecover>
</li>
</comps>
<stages>
<li>

<painOffset>-0.9</painOffset>
<capMods>
<li>

<capacity>Consciousness</capacity>
<offset>-0.1</offset>
</li>
</capMods>
</li>
</stages>
</HediffDef>
</Defs>
</source>

Topic:Zi3ul6dvrya2yyis

2026-07-21T03:55:46Z

Aelanna (talk | contribs) commented on "Modding tutorial submission" (Hi! This is Aelanna from the wiki staff, could get you to join the RimWorld Discord server so we can discuss the tutorial you submitted?...)

Topic:Zhedqjaz7e59i69w

2026-07-09T17:32:26Z

Aelanna (talk | contribs) commented on "Just a heads up" (Heya, just letting you know that I am rejecting your change to the Damage Types page, not necessarily because it's inaccurate but because...)

Revenant flesh chunk

2026-07-03T05:32:46Z

Aelanna: Grammar.

{{Anomaly}}
{{Stub|reason=details of analysis}}

{{Infobox main|item|
| name = Revenant flesh chunk
| image = Revenant flesh chunk.png
| type = Misc
| description = A strip of leathery, desiccated flesh that sloughed off a revenant when it was harmed. The tissue oozes a dark, oily liquid.
| stack limit = 1
| mass base = 0.03
| beauty = -10
| hp = 50
| flammability = 1.6
| deterioration = 6
| defName = RevenantFleshChunk
| label = revenant flesh chunk
}}

'''Revenant flesh chunk''' is an item dropped by the [[Revenant]].

== Summary ==
Revenants will drop flesh chunks upon hypnotizing a colonist if they are damaged prior to the hypnosis completing. A colonist can be selected to analyze the item, which increases the duration that the Revenant leaves trailing filth behind, and reveals all sources that the Revenant is vulnerable to / can be used to stun them.

== Analysis ==
If a revenant is damaged when it is hunting or actively hypnotizing a pawn, it'll drop a revenant flesh chunk when hypnosis completes. Only one chunk will drop during any given hypnosis. These chunks can be analyzed by a colonist to make it easier to track the revenant:

The first analyzed flesh chunk will make the revenant's trail of smears much longer.
The second analyzed flesh chunk will provide a warning when a pawn comes within 7.9 tiles of the revenant, indicated by an exclamation mark above the pawn's head and a visible message: (i.e. "Glasses can hear the revenant shivering nearby!")
The third and final analyzed flesh chunk will reveal the revenant whenever a pawn comes within 8.9 tiles of its location.

== Version history ==
* [[Anomaly DLC]] Release - Added.

Tropical rainforest

2026-06-30T18:23:48Z

Aelanna: Rewriting summary for tone.

{{Infobox biome
| name = Tropical rainforest
| image = TropicalRainforest.png
| type = Biome
| texture = TemperateSwampTexture.png
| canbuildbase = Yes
| allowFarmingCamps = Yes
| animal density = 6.5
| plant density = 0.99
| movement difficulty = 2
| min average temperature = 15
| max average temperature = 30
| min temperature = 15
| min rainfall = 2000
| forageability = 0.75
| wild plant regrow days = 13
| disease mtb days = 35
| description = A thick, moist jungle, buzzing with animal life and infested with disease. Despite its visual beauty, this is a very dangerous biome. Choking overgrowth, aggressive animals, and constant sickness are why some explorers call this the "green hell".

| clear = 18
| fog = 1
| rain = 2
| dry thunderstorm = 0.3
| rainy thunderstorm = 1.7
| foggy rain = 1
| hard snow = 4
| soft snow = 4
| gray pall = 1
| blind fog = 1
| overcast = 2
| torrential rain = 0.5

| max fish population = 720
| freshwater_common_tilapia = Yes
| freshwater_uncommon_piranha = Yes
| saltwater_common_bluefish = Yes
| saltwater_uncommon_tuna = Yes
| saltwater_uncommon_flounder = Yes
}}
'''Tropical rainforest''' is a hot [[biome]] in RimWorld.

== Summary ==
Tropical rainforests have both strong advantages and disadvantages. The lack of winters and plentiful rich soil allow for year-round growing and both wood and animals are plentiful, however the dense foliage can make expansion difficult, hinders ranged combat, and the frequency of large predators can make fieldwork dangerous. High heat is also somewhat more difficult to deal with than low temperatures in terms of maintaining base temperature and the high disease frequency means that colonists will regularly come down with debilitating illnesses including [[sleeping sickness]], a slow-progressing and long-lasting disease exclusive to the tropics. Wild [[healroot]] also does not grow in rainforests, making medicine more difficult to come by unless you have a grower with sufficient plant skill.

In the lists below the number in brackets represents the relative commonality.

=== Flora ===
<div class="ul-column-width-200">
{{#ask: [[Type::Plant]] [[Lives In Tropical Rainforest::>>0]]
| format = template
| template = Icon List
| link = none
| sort = From DLC, Name
| default = None.
| ?Lives In Tropical Rainforest #
}}
</div>{{#set:Flora Commonality Sum | {{#expr: {{#ask: [[Type::Plant]] [[Lives In Tropical Rainforest::>>0]] | ?Lives In Tropical Rainforest = | mainlabel=- | sep=+ }} }} }}

=== Fauna ===
<div class="ul-column-width-200">
{{#ask: [[Type::Animal]] [[Lives In Tropical Rainforest::>>0]] [[Coastal Animal::false]]
| format = template
| template = Icon List
| link = none
| sort = From DLC, Name
| default = None.
| ?Lives In Tropical Rainforest
}}
</div>{{#set:Fauna Commonality Sum | {{#expr: {{#ask: [[Type::Animal]] [[Lives In Tropical Rainforest::>>0]] [[Coastal Animal::false]] | ?Lives In Tropical Rainforest = | mainlabel=- | sep=+ }} }} }}

Additionally, these animals can spawn in coastal maps:
<div class="ul-column-width-200">
{{#ask: [[Type::Animal]] [[Lives In Tropical Rainforest::>0]] [[Coastal Animal::true]]
| format = template
| template = Icon List
| link = none
| sort = From DLC, Name
| default = None.
| ?Lives In Tropical Rainforest
}}
</div>

If the map is [[polluted]],{{BiotechIcon}} then the game may choose to spawn in wild animals from this list instead:
<div class="ul-column-width-200">
{{#ask: [[Type::Animal]] [[Lives In Tropical Rainforest (Polluted)::>0]]
| format = template
| template = Icon List
| link = none
| sort = From DLC, Name
| default = None.
| ?Lives In Tropical Rainforest (Polluted)
}}
</div>

=== Diseases ===
Tropical Rainforest has a disease {{MTB}} of 35 days. The following diseases can occur in a Tropical Rainforest:
{| {{STDT|c_07 sortable}}
! Disease
! Commonality{{#set:Disease commonality sum|{{#expr:100+100+160+140+80+30+30+80+100+100+10}} }}
|-
| [[Flu]] || 100{{#set:Flu commonality|100}}
|-
| [[Plague]] || 100{{#set:Plague commonality|100}}
|-
| [[Malaria]] || 160{{#set:Malaria commonality|160}}
|-
| [[Sleeping sickness]] || 140{{#set:Sleeping sickness commonality|140}}
|-
| [[Gut worms]] || 80{{#set:Gut worms commonality|80}}
|-
| [[Fibrous mechanites]] || 30{{#set:Fibrous mechanites commonality|30}}
|-
| [[Sensory mechanites]] || 30{{#set:Sensory mechanites commonality|30}}
|-
| [[Muscle parasites]] || 80{{#set:Muscle parasites commonality|80}}
|-
| [[Flu#Animals|Animal flu]] || 100{{#set:Animal flu commonality|100}}
|-
| [[Plague#Animals|Animal plague]] || 100{{#set:Animal plague commonality|100}}
|-
| [[Organ decay]] || 10{{#set:Organ decay commonality|10}}
|}

=== Fish ===
{{Odyssey|section=1|No category}}
The table below contains the list of all of the fish that can be caught - as well as where they can be caught.
{| {{STDT|c_23 sortable}}
! Fish
! Water body
! Rarity
|-
| [[Tilapia]] || Freshwater || Common
|-
| [[Piranha]] || Freshwater || Uncommon
|-
| [[Bluefish]] || Saltwater || Common
|-
| [[Tuna]] || Saltwater || Uncommon
|-
| [[Flounder]] || Saltwater || Uncommon
|}

== Analysis ==
While food is rarely an issue, fertile land is common, and many tiles have comfortable temperatures year-round, the tropical forest is rife with disease and predation.

* '''Food and Growing: Easy''' - Growing seasons are often year-round, while it is densely populated with both animals and plant life.

* '''Disease: Difficult''' - Diseases are very common in the rainforest, with the only biome having more diseases being the [[tropical swamp]]. In addition, wild [[healroot]] does not grow in the tropical rainforest, making medicine supply an issue unless there is a grower with Plants 8+.

* '''Temperature: Moderate (regular settings) or Extreme (hot world)''' - Cooler rainforest tiles should be fairly comfortable to live in except during [[heat wave]]s. Warmer tiles can cause heatstroke during the warmer months, but [[passive cooler]]s are easy to make due to the abundance of wood. If the world's temperature setting is increased past normal, tropical rainforests can have dangerously hot temperatures year-round. They have no significant cold periods, although [[cold snap]]s can happen in cooler tiles.

* '''Fires: Difficult''' - Tropical rainforests are filled with trees and other flora, making fires near your base difficult to contain. The game's [[Weather|firewatch]] will typically contain large fires, but various conditions can disable the firewatch and significant damage can occur before it contains the fire regardless. For more information, see [[Weather]]. Surrounding your base and growing fields with firebreaks such as stone walls, two-tile-wide non-flammable flooring, or sections of roof over soil to prevent plant growth will make fires less of an issue.

* '''Predators: Moderate, but common''' - While there are no large predators like [[grizzly bear]]s, predators like [[cobra]]s and [[panther]]s are common, and will sometimes decide to hunt colonists. Colonists who venture far away are at greater risk than usual, while small animals and [[children]]{{BiotechIcon}} are especially vulnerable.

Overall difficulty is moderate. It is relatively easy in the early game due to having year-round growing periods and plenty of wood. Past the early game, when food and temperature are no longer issues, the rainforest is somewhat more difficult than most other biomes due to its disease frequency. The added diseases are annoying and will slow down production, and while rarely life-threatening, an outbreak can be a death sentence for a struggling or just-recovering colony.

== Gallery ==
<gallery>
TropicalRainforest.png|A Tropical Rainforest

TropicalRainforestTexture.png|Tropical Rainforest's texture on the world map
</gallery>

== Version history ==
* [[Version/0.7.581|0.7.581]] - Added

{{nav|biomes|wide}}
[[Category:Biomes]]
[[Category:Hot Biomes]]

Outfit stand

2026-06-30T18:06:38Z

Aelanna:

{{Stub|reason=1) Needs more images 2) More data needed}}
{{Infobox main|furniture
| name = Outfit stand
| image = Outfit_stand_south.png
| description = A small display that showcases a single outfit. Saves space and can be used to quickly change clothing.
| type = Building
| type2 = Furniture
| placeable = true
| path cost = 50
| passability = pass through only
| cover = 0.4
| minifiable = true
| size = 1 ˣ 1
| mass base = 3
| flammability = 1
| hp = 60
| sell price multiplier = 0.7
| beauty = 0.5
| terrain affordance = light
| research = Complex furniture
| work to make = 350
| stuff tags = Metallic, Woody, Stony
| resource 1 = Stuff
| resource 1 amount = 35
| has quality = false
}}
An '''outfit stand''' is a [[furniture]] item that can store a pawn's outfit for later use.

== Acquisition ==
{{Acquisition}}

== Summary ==
An outfit stand can be used to change a pawns entire outfit, rather than doing so manually. Once constructed, pawns are capable of storing [[weapons]] and [[armor]] in the outfit stand, akin to most containers or stockpiles.

When an outfit stand contains any weapons or armor, a pawn can be commanded to equip items on said armor stand, either by right clicking the armor stand with a pawn selected, or using the "Equip Outfit" gizmo and selecting a pawn.

Like pawns, outfit stands have equipment slots of their own. If a pawn is already wearing gear that takes up slots that the outfit stand is also wearing, the gear will be swapped with the outfit stand.

== Analysis ==
Outfit stands are a great way to save space with [[clothing]], especially within [[gravship]]s. Outfits for pawns can easily be swapped to suit their needs, such as swapping to a [[vacsuit]] or [[marine armor]] when entering space, or swapping to equipment that raises social impact when a pawn is trading.

== Equip Time ==
Swapping an outfit from an outfit stand takes some time. The amount of time it takes is based on the combined [[equip delay]] of each piece of gear that is being changed.

== Biotech ==
{{Biotech|No category}}
With Biotech installed, players also have the option of constructing kid outfit stands. Kid outfit stands allow for storing kid clothing, as standard outfit stands cannot store kid clothing.

{{Building Stats Table}}

== Version history ==
* [[Odyssey DLC]] Release - Added

{{Nav|furniture|wide}}
[[Category:Furniture]]

Modding Tutorials/MayRequire

2026-06-28T15:41:41Z

Aelanna: Minor rewording.

{{DISPLAYTITLE:MayRequire}}
{{BackToTutorials}}

<code>MayRequire</code> is an [[Modding_Tutorials/Introduction_to_XML|XML attribute]] introduced alongside the [[Royalty DLC]] that allows for easy conditional loading of XML content. <code>MayRequire</code> makes it easier to load content that is optionally dependent on DLCs or other mods.

== Details ==

<code>MayRequire</code> is inserted as an XML attribute in a supported XML node with a value being one or more <code>packageId</code> values separated by commas.

The <code>packageId</code> for official DLCs are:

* Royalty: <code>Ludeon.RimWorld.Royalty</code>
* Ideology: <code>Ludeon.RimWorld.Ideology</code>
* Biotech: <code>Ludeon.RimWorld.Biotech</code>
* Anomaly: <code>Ludeon.RimWorld.Anomaly</code>
* Odyssey: <code>Ludeon.RimWorld.Odyssey</code>

The <code>packageId</code> for mods can be found in their [[About.xml]] file.

=== <code>MayRequireAnyOf</code> ===

By default, <code>MayRequire</code> will only allow the use of that node if ''all'' of the DLCs or mods it designates are loaded. If you instead want to load the specified node if ''any'' of the specified DLCs or mods are loaded, you can use <code>MayRequireAnyOf</code> instead.

=== Specifying Multiple Targets ===

Both <code>MayRequire</code> and <code>MayRequireAnyOf</code> can accept a comma-delimited list of <code>packageId</code> values. For example, if you wanted to create a <code>ThingDef</code> that is only loaded if both the [[Royalty]] and [[Ideology]] DLCs are loaded, you could use the following syntax:

<source lang="xml">
<ThingDef MayRequire="Ludeon.RimWorld.Royalty,Ludeon.RimWorld.Ideology">
</source>

== List Entries ==

<code>MayRequire</code> can be on any <code>li</code> node to only load that entry if the specified DLC or mod is loaded:

<div class="TutorialTableWrapper">
{| class="TutorialCodeTable"
! XML Example !! Description
|-
| <source lang="xml">
<SurgeryOutcomeEffectDef Name="SurgeryOutcomeBase">
<defName>SurgeryOutcomeBase</defName>
<outcomes>
<li Class="SurgeryOutcomeSuccess" />



<li Class="SurgeryOutcome_FailureWithHediff" MayRequire="Ludeon.RimWorld.Biotech">
<chance>0.03</chance>
<failedHediff>Sterilized</failedHediff>
<applyToRecipes>
<li MayRequire="Ludeon.RimWorld.Biotech">ImplantIUD</li>
<li MayRequire="Ludeon.RimWorld.Biotech">RemoveIUD</li>
</applyToRecipes>
<failure>true</failure>
<totalDamage>10</totalDamage>
<applyEffectsToPart>true</applyEffectsToPart>
<letterLabel>Surgery failed on {PATIENT_labelShort}: Sterilized</letterLabel>
<letterText>{SURGEON_labelShort} has failed while operating on {PATIENT_labelShort} ({RECIPE_label}), leaving {PATIENT_objective} sterile.</letterText>
</li>



</outcomes>



</SurgeryOutcomeEffectDef>
</source>
| class="TutorialCodeTable-description" |
<code>MayRequire</code> is used in the list of possible surgery outcomes to add the possibility of accidentally sterilizing the patient as a result of a surgery failure.

Note that the use of <code>MayRequire</code> on the list nodes of the <code><applyToRecipes></code> is technically unnecessary as the entire outcome node would not have loaded without [[Biotech]] active.
|-
| <source lang="xml">
<DesignationCategoryDef>
<defName>Zone</defName>
<label>zone</label>
<order>800</order>
<specialDesignatorClasses>
<li>Designator_Cancel</li>
<li>Designator_Deconstruct</li>
<li>Designator_ZoneAddStockpile_Resources</li>
<li>Designator_ZoneAddStockpile_Dumping</li>
<li>Designator_ZoneAdd_Growing</li>
<li>Designator_ZoneDelete</li>
<li>Designator_AreaHomeExpand</li>
<li>Designator_AreaHomeClear</li>
<li>Designator_AreaAllowedExpand</li>
<li>Designator_AreaAllowedClear</li>
<li>Designator_AreaBuildRoof</li>
<li>Designator_AreaNoRoof</li>
<li>Designator_AreaIgnoreRoof</li>
<li>Designator_AreaSnowClearExpand</li>
<li>Designator_AreaSnowClearClear</li>
<li MayRequire="Ludeon.RimWorld.Biotech">Designator_AreaPollutionClearExpand</li>
<li MayRequire="Ludeon.RimWorld.Biotech">Designator_AreaPollutionClearClear</li>
</specialDesignatorClasses>
</DesignationCategoryDef>
</source>
| class="TutorialCodeTable-description" |
<code>MayRequire</code> is used in the DesignationCategoryDef for the "Zone" architect menu to add designators for pollution clearing areas.
|-
| <source lang="xml">
<AlienRace.ThingDef_AlienRace Name="ARR_RaceBase" ParentName="HumanRace" Abstract="True">



<comps>
<li Class="ARimReborn.CompProperties_ClassUser" MayRequire="Aelanna.ARimReborn.ClassesAndJobs" />
</comps>

<inspectorTabs>
<li MayRequire="Aelanna.ARimReborn.ClassesAndJobs">ARimReborn.ITab_Pawn_Classes</li>
</inspectorTabs>

</AlienRace.ThingDef_AlienRace>
</source>
| class="TutorialCodeTable-description" |
<code>MayRequire</code> can be used to omit entire code components.

In this modded example, both a ThingComp and an inspector tab are only added if a specific sub-mod is loaded.
|-
| <source lang="xml">
<Operation Class="PatchOperationSequence">
<operations>
<li Class="PatchOperationAdd" MayRequire="Ludeon.Rimworld.Biotech"> 
<xpath>Defs/ThingDef[defName="MechGestator"]/recipes<xpath>
<value>
<li>MyCustomMech</li>
</value>
</li>
<li Class="PatchOperationAdd" MayRequire="MyProject.OtherModPackageId">
<xpath>Defs/ThingDef[defName="OtherModWorkbench"]/recipes</xpath>
<value>
<li>MyCustomResource</li>
</value>
</li>
</operations>
</Operation>
</source>
| class="TutorialCodeTable-description" |
<code>MayRequire</code> can be used in lieu of PatchOperationFindMod in a PatchOperationSequence.

'''Warning''': PatchOperationSequence can obfuscate errors, so it is strongly recommended that you individually test patches first before you place them in a sequence. Please see [[Modding_Tutorials/PatchOperations|PatchOperations]] for more information.
|-
|}
</div>

== Def References ==

<code>MayRequire</code> can be used on any field that references [[Modding_Tutorials/Defs|Defs]] by their <code>defName</code>, including single fields, lists, and special parsed lists such as stat blocks and item count lists.

'''Note''': When used in direct references or in a list of direct references, Def references have a special behavior in that <code>MayRequire</code> only serves to suppress cross-resolution errors if the targeted DLC or mod is not loaded. '''If RimWorld finds the targeted Def, it will be loaded into the list regardless of whether the specified DLC or mod is loaded or not.''' This does not apply to special parsed lists (see below).

<div class="TutorialTableWrapper">
{| class="TutorialCodeTable"
! XML Example !! Description
|-
| <source lang="xml">
<LifeStageDef ParentName="HumanlikeAdolescent">
<defName>HumanlikeBaby</defName>
<label>baby</label>



<thinkTreeMainOverride MayRequire="Ludeon.RimWorld.Biotech">HumanlikeBaby</thinkTreeMainOverride>
<thinkTreeConstantOverride MayRequire="Ludeon.RimWorld.Biotech">HumanlikeBabyConstant</thinkTreeConstantOverride>



</LifeStageDef>
</source>
| class="TutorialCodeTable-description" |
<code>MayRequire</code> is used in human LifeStageDefs for Def references such as the ThinkTreeDefs for certain lifestages. These Defs only exist in the Biotech DLC, and thus must have errors suppressed if the DLC is not loaded.
|-
| <source lang="xml">
<ThingDef ParentName="BasePawn">
<defName>Human</defName>
<label>human</label>



<recipes>
<li>ExciseCarcinoma</li>
<li>AdministerMechSerumHealer</li>
<li>RemoveBodyPart</li>
<li>Euthanize</li>
<li>Anesthetize</li>
<li>CureScaria</li>
<li MayRequire="Ludeon.RimWorld.Biotech">Vasectomy</li>
<li MayRequire="Ludeon.RimWorld.Biotech">ReverseVasectomy</li>
<li MayRequire="Ludeon.RimWorld.Biotech">TubalLigation</li>
<li MayRequire="Ludeon.RimWorld.Biotech">ExtractOvum</li>
<li MayRequire="Ludeon.RimWorld.Royalty">CureBloodRot</li>
<li MayRequire="Ludeon.RimWorld.Royalty">CureAbasia</li>
<li MayRequire="Ludeon.RimWorld.Biotech">ExtractHemogenPack</li>
<li MayRequire="Ludeon.RimWorld.Biotech">BloodTransfusion</li>
<li MayRequire="Ludeon.RimWorld.Biotech">ImplantXenogerm</li>
<li MayRequire="Ludeon.RimWorld.Biotech">ImplantIUD</li>
<li MayRequire="Ludeon.RimWorld.Biotech">RemoveIUD</li>
<li MayRequire="Ludeon.RimWorld.Biotech">TerminatePregnancy</li>
</recipes>



</ThingDef>
</source>
| class="TutorialCodeTable-description" |
<code>MayRequire</code> is used in the Human [[Modding_Tutorials/ThingDef|ThingDef]] to set surgery recipes that are only relevant to specific DLCs. Without <code>MayRequire</code>, these would cause errors as the specified [[Modding_Tutorials/Defs|Defs]] only exist in their respective DLCs.
|-
| <source lang="xml">
<ThingDef Name="TorchLamp" ParentName="BuildingBase">
<defName>TorchLamp</defName>
<label>torch lamp</label>



<statBases>
<MaxHitPoints>75</MaxHitPoints>
<WorkToBuild>100</WorkToBuild>
<Flammability>0</Flammability>
<MeditationFocusStrength>0.0</MeditationFocusStrength>
<StyleDominance MayRequire="Ludeon.RimWorld.Ideology">5</StyleDominance>
</statBases>



</ThingDef>
</source>
| class="TutorialCodeTable-description" |
<code>MayRequire</code> can be used in "special parsers" such as those for <code>statBases</code>. These are usually used to create shorthand notation wherein the node name is the <code>defName</code> and the value is the stat value. The vanilla torch lamp uses the <code>StyleDominance</code> stat from [[Ideology]] to affect the room it is placed in.
|-
| <source lang="xml">
<ThingDef ParentName="ApparelMakeableBase">
<defName>Apparel_Duster</defName>



<equippedStatOffsets>
<SlaveSuppressionOffset MayRequire="Ludeon.RimWorld.Ideology">-0.05</SlaveSuppressionOffset>
</equippedStatOffsets>


</ThingDef>
</source>
| class="TutorialCodeTable-description" |
<code>equippedStatOffsets</code> is another example of a stat block. In this example, the vanilla [[Duster]] apparel has a [[Slavery|SlaveSuppressionOffset]] stat offset from [[Ideology]].
|-
| <source lang="xml">
<BiomeDef>
<defName>TemperateForest</defName>
<wildPlants>
<Plant_Grass>5.0</Plant_Grass>
<Plant_GrayGrass MayRequire="Ludeon.RimWorld.Biotech">2</Plant_GrayGrass>
<Plant_TallGrass>2.0</Plant_TallGrass>
<Plant_Brambles>1.0</Plant_Brambles>
<Plant_Ripthorn MayRequire="Ludeon.RimWorld.Biotech">0.8</Plant_Ripthorn>

</wildPlants>
<pollutionWildAnimals MayRequire="Ludeon.RimWorld.Biotech">
<Toxalope MayRequire="Ludeon.RimWorld.Biotech">0.4</Toxalope>
<WasteRat MayRequire="Ludeon.RimWorld.Biotech">0.1</WasteRat>

</pollutionWildAnimals>

</BiomeDef>
</source>
| class="TutorialCodeTable-description" |
<code>MayRequire</code> is used in <code>BiomeDef</code> entries to specify wild plants and animals that are only present in DLCs.
|-
| <source lang="xml">
<FactionDef ParentName="FactionBase">
<defName>Mechanoid</defName>
<label>mechanoid hive</label>
<pawnGroupMakers>
<li>

<kindDef>Combat</kindDef>
<commonality>100</commonality>
<options>
<Mech_Scyther>10</Mech_Scyther>
<Mech_Pikeman>10</Mech_Pikeman>
<Mech_Lancer>10</Mech_Lancer>
<Mech_CentipedeBlaster>10</Mech_CentipedeBlaster>
<Mech_Militor MayRequire="Ludeon.RimWorld.Biotech">20</Mech_Militor>
<Mech_Centurion MayRequire="Ludeon.RimWorld.Biotech">2</Mech_Centurion>
<Mech_Warqueen MayRequire="Ludeon.RimWorld.Biotech">1</Mech_Warqueen>
<Mech_Apocriton MayRequire="Ludeon.RimWorld.Biotech">1</Mech_Apocriton>
</options>
</li>

</pawnGroupMakers>

</FactionDef>
</source>
| class="TutorialCodeTable-description" |
<code>MayRequire</code> is used by official content <code>FactionDef</code> entries to specify <code>PawnKindDef</code> types that only exist in DLCs.
|-
| <source lang="xml">
<FactionDef ParentName="FactionBase" Name="OutlanderFactionBase" Abstract="True">
<disallowedMemes>
<li MayRequire="Ludeon.RimWorld.Ideology">Structure_Animist</li>
<li MayRequire="Ludeon.RimWorld.Ideology">Nudism</li>
<li MayRequire="Ludeon.RimWorld.Ideology">Blindsight</li>
</disallowedMemes>
<structureMemeWeights>
<Structure_TheistEmbodied MayRequire="Ludeon.RimWorld.Ideology">1</Structure_TheistEmbodied>
<Structure_TheistAbstract MayRequire="Ludeon.RimWorld.Ideology">2</Structure_TheistAbstract>
<Structure_Ideological MayRequire="Ludeon.RimWorld.Ideology">1</Structure_Ideological>
<Structure_Archist MayRequire="Ludeon.RimWorld.Ideology">1</Structure_Archist>
<Structure_OriginChristian MayRequire="Ludeon.RimWorld.Ideology">1</Structure_OriginChristian>
<Structure_OriginIslamic MayRequire="Ludeon.RimWorld.Ideology">1</Structure_OriginIslamic>
<Structure_OriginHindu MayRequire="Ludeon.RimWorld.Ideology">1</Structure_OriginHindu>
<Structure_OriginBuddhist MayRequire="Ludeon.RimWorld.Ideology">1</Structure_OriginBuddhist>
</structureMemeWeights>

</FactionDef>
</source>
| class="TutorialCodeTable-description" |
<code>MayRequire</code> must be used for meme and precept references in <code>FactionDef</code> entries, as they only exist if [[Ideology]] is loaded.
|-
| <source lang="xml">
<FactionDef ParentName="FactionBase" Name="OutlanderFactionBase" Abstract="True">
<xenotypeSet>
<xenotypeChances>
<Hussar MayRequire="Ludeon.RimWorld.Biotech">0.05</Hussar>
<Dirtmole MayRequire="Ludeon.RimWorld.Biotech">0.05</Dirtmole>
<Genie MayRequire="Ludeon.RimWorld.Biotech">0.025</Genie>
<Neanderthal MayRequire="Ludeon.RimWorld.Biotech">0.025</Neanderthal>
</xenotypeChances>
</xenotypeSet>

</FactionDef>
</source>
| class="TutorialCodeTable-description" |
<code>MayRequire</code> must be used for xenotype references in <code>FactionDef</code> entries, as they only exist if [[Biotech]] is loaded.
|-
|}
</div>

== Optional Defs ==

<code>MayRequire</code> can be used to conditionally load entire Defs. This is far easier to use than the prior option of using [[Modding_Tutorials/PatchOperations|PatchOperations]] to inject new Defs.

<div class="TutorialTableWrapper">
{| class="TutorialCodeTable"
! XML !! Description
|-
| <source lang="xml">
<ThingDef MayRequire="Ludeon.RimWorld.Ideology" ParentName="Brazier">
<defName>DarklightBrazier</defName>
<label>darklight brazier</label>
<description>A specially treated brazier that illuminates its surroundings with darklight and creates heat. These satisfy royal brazier requirements.</description>



</ThingDef>
</source>
| class="TutorialCodeTable-description" |
<code>MayRequire</code> is used to activate [[Royalty]]'s darklight brazier stat if [[Ideology]] is also loaded.
|-
| <source lang="xml">
<StatDef ParentName="MeditationFocusBase" MayRequireAnyOf="Ludeon.RimWorld.Royalty,Ludeon.RimWorld.Biotech">
<defName>MeditationFocusGain</defName>
<label>meditation psyfocus gain</label>



</StatDef>
</source>
| class="TutorialCodeTable-description" |
<code>MayRequireAnyOf</code> is used to activate the MeditationFocusGain stat if either [[Royalty]] or [[Biotech]] is loaded.
|-
| <source lang="xml">
<ThingDef ParentName="ApparelMakeableBase" MayRequireAnyOf="Ludeon.RimWorld.Royalty,Ludeon.RimWorld.Biotech">
<defName>Apparel_Cape</defName>
<label>cape</label>



</ThingDef>
</source>
| class="TutorialCodeTable-description" |
<code>MayRequireAnyOf</code> is used to activate the [[Cape]] apparel if either [[Royalty]] or [[Biotech]] is loaded.
|-
|}
</div>

== Miscellaneous ==

The following are specific, non-standard usages of <code>MayRequire</code> from official content XML:

<div class="TutorialTableWrapper">
{| class="TutorialCodeTable"
! XML !! Description
|-
| <source lang="xml">
<PawnKindDef Abstract="True" Name="BasePlayerPawnKind">
<race>Human</race>
<apparelIgnorePollution MayRequire="Ludeon.RimWorld.Biotech">true</apparelIgnorePollution>

</PawnKindDef>
</source>
| class="TutorialCodeTable-description" |
<code>MayRequire</code> is used by <code>PawnKindDef</code> for the <code>apparelIgnorePollution</code> node.

'''NOTE''': Analysis of game code seems to indicate that this particular use of <code>MayRequire</code> does not actually have any effect, and may have been put here merely as a flag.
|-
| <source lang="xml">
<LifeStageDef ParentName="HumanlikeAdolescent">
<defName>HumanlikeBaby</defName>
<label>baby</label>
<thinkTreeMainOverride MayRequire="Ludeon.RimWorld.Biotech">HumanlikeBaby</thinkTreeMainOverride>
<thinkTreeConstantOverride MayRequire="Ludeon.RimWorld.Biotech">HumanlikeBabyConstant</thinkTreeConstantOverride>

</LifeStageDef>
<LifeStageDef Name="LifeStageHumanlikeChild" ParentName="HumanlikeAdolescent">
<defName>HumanlikeChild</defName>
<label>child</label>
<workerClass MayRequire="Ludeon.RimWorld.Biotech">LifeStageWorker_HumanlikeChild</workerClass>

</LifeStageDef>
</source>
| class="TutorialCodeTable-description" |
<code>MayRequire</code> is used for think tree override and worker classes in <code>LifeStageDef</code> entries for functionality related to children and growth in [[Biotech]].

'''NOTE''': Analysis of game code seems to indicate that the latter use of <code>MayRequire</code> does not actually have any effect, and may have been put here merely as a flag. The WorkerClass code is itself locked to [[Biotech]].
|-
|}
</div>

=== Exceptions ===

* <code>MayRequire</code> does '''NOT''' work on top-level XML nodes that are not <code>Def</code>s. This means that <code>Operation</code> tags cannot use <code>MayRequire</code>, though as previous indicated, <code>PatchOperationSequence</code> lists can. Again, this is not recommended because <code>PatchOperationSequence</code> can obfuscate errors.
* Prior to RimWorld 1.6, MayRequire was bugged and did not ignore the <code>_steam</code> suffix appended to Steam copies of a mod when you have both a local mod and a Steam mod with the exact same packageId. This meant that if you had a local copy, then only the local copy would be recognized by MayRequire. This could be worked around by using <code>MayRequireAnyOf</code> with both packageIds, i.e. <code>MayRequireAnyOf="MyName.MyMod,MyName.MyMod_steam"</code>. This should not be necessary in 1.6 and later versions.

[[Category:Modding]]
[[Category:Modding tutorials]]

Skull

2026-06-26T03:48:00Z

Aelanna: Fixing work link.

{{Infobox main|resource
| name = Skull
| image = Skull stack full.png
| description = A human skull.
| type = Crafted resources
| type2 =
| path cost =
| stack limit = 25
| beauty =
| flammability = 1
| marketvalue = 5
| mass base = 1.5
| hp = 100
| deterioration = 1
| defName = Skull
| thingCategories = Items
| tradeTags =
| page verified for version = 1.3.3066
}}
'''Skulls''' are a resource extracted from a human corpse originally added in the [[Ideology DLC]], but now part of Core.

== Acquisition ==
[[File:Gizmo corpse extract skull.png|left|thumb|The gizmo used to designate a corpse for skull-extraction]]
Skulls can be extracted from [[human]] [[corpse]]s if the [[Ideology DLC]] is active. Only pawns with the [[Ideoligion#Skullspike|Skullspike: Desired]]{{IdeologyIcon}} precept in their [[ideoligion]] can extract skulls. A corpse can be designated for skull extraction by selecting the corpse and clicking the "extract skull" gizmo. It takes {{Ticks|180}} of Basic [[work]] to extract a skull.

Extracting the skull destroys the head of the corpse and reduces the amount of meat and leather extracted from the corpse. [[Filth#Blood|Blood]] will be created from non-skeletal corpses when extracting a skull. It is unknown whether skull extraction reduces the market value extracted from the corpse by a greater amount than is gained from the skull.{{Check Tag|Detail needed}}

Skulls are also commonly found in [[gray box]]es in the [[labyrinth]].{{AnomalyIcon}}

Skulls can also be carried by pawns with the [[psychopath]] trait as a starting possession.

== Summary ==
Skulls retain the name of the person they were extracted from. Their main purpose is for building [[skullspike]]s.{{IdeologyIcon}}

Skulls can be consumed by [[harbinger tree]]s.{{AnomalyIcon}}

{{Ingredient List|noCollapse=true}}

== Analysis ==
{{Stub|section=1|reason= Missing Analysis. general but also specifically include value vs butcher loss, skull destruction as medical process (see [[Mindscrew#Removal]]) etc}}

== Gallery ==
<gallery>
Skull.png|One skull
Skull stack partial.png|Partial stack of skulls
Skull stack full.png| Full stack of skulls
</gallery>

== Version history ==
* [[Ideology DLC]] Release - Added as Ideology-exclusive item.
* [[Version/1.3.3069|1.3.3069]] - Now stackable.
* [[Version/1.3.3072|1.3.3072]] - Pawns can no longer extract skulls from corpses that have lost their head since designation.
* [[Version/1.3.3101|1.3.3101]] - Skulls now keep track of the name of the pawn they originated from. Skull extraction blood is no longer labeled as being from the extractor. Skull extraction will no longer drop blood when corpse is already a skeleton
* [[Version/1.5.4062|1.5.4062]] - Migrated to core game files, no longer requiring Ideology. Fix: Skull has duplicate CompForbiddable.

[[Category:Crafted Resource]]

Modding Tutorials

2026-06-25T22:59:34Z

Aelanna: Moving asset bundle tutorial to new category

{| align=center
| {{Mods_Nav}}
|}
<hr>

This is the hub page for tutorials, guides, and reference materials for creating mods for RimWorld. If you are looking for instructions on how to use RimWorld, please check out the general [[Modding]] hub.

As RimWorld does not have a formal modding API, nearly all of the information here has been gathered and maintained by the modding community.

'''NEW: [[Modding_Tutorials/RimWorld_1.6_Mod_Updates|RimWorld 1.6 Mod Updates]]''' - A work-in-progress list of changes datamined by the modding community in the current unstable version of RimWorld 1.6. '''THERE MAY BE ODYSSEY DLC SPOILERS, YOU HAVE BEEN WARNED.'''

-----

==About RimWorld==
RimWorld is a multi-platform game written on Unity 2022.3.35. However, the Unity Editor is not used for creating mods unless you are creating new shaders or building optional asset bundles.

* [[Modding_Tutorials/Recommended_software|Recommended Software]] - Editors and other useful software for mod development
* [[Modding_Tutorials/Mod_Folder_Structure|Mod Folder Structure]] - Explore the basic folder structure of a mod
** [[Modding_Tutorials/About.xml|About.xml]] - About.xml identifies and describes your mod to RimWorld so that it can be loaded properly

===Game Systems Guides===

* [[Modding_Tutorials/Defs|Defs]] - XML Definitions are used to define and configure content in a way that does not require compiling code
** [[Modding_Tutorials/MayRequire|MayRequire]] - MayRequire and MayRequireAnyOf are used to conditionally load Defs and list entries based on whether a DLC or other mod is loaded
* [[Modding_Tutorials/Localization|Localization]] - Define text strings used for translations and word lists used in name and text generation
* [[Modding_Tutorials/PatchOperations|PatchOperations]] - PatchOperations are used to modify XML Defs without overwriting them completely
* [[Modding_Tutorials/Sounds|Sounds]] - (Needs Rewriting) Adding sound files for mods
* [[Modding_Tutorials/Textures|Textures]] - How to create and add textures to mods
* [[Modding Tutorials/Plant Rendering|Plant Rendering]] - An explanation of how plant textures are rendered
* [[Modding_Tutorials/Research_Projects|Research Projects]] - How to create and use research projects.

===XML Tutorials===

The following are step-by-step tutorials for creating basic content mods.

Basic Tutorials:
* [[Modding_Tutorials/Basic_Melee_Weapon|Basic Melee Weapon]] - How to create a basic melee weapon with a texture mask
* [[Modding_Tutorials/Basic_Ranged_Weapon|Basic Ranged Weapon]] - How to create a basic ranged weapon with custom sound effects
* [[Modding_Tutorials/Basic_Plant|Basic Plant]] - How to create a custom plant with both a cultivated and wild variant
* Custom Animal (Upcoming)
* Simple Building (Upcoming)
* Custom Workbench (Upcoming)
* Custom Drug (Upcoming)

Advanced Tutorials:
* Custom Faction (Upcoming)
* Custom Culture (Upcoming)
* Custom Trader Type (Upcoming)

===C# Guides===

C# is used to create and define custom game behaviors

* [[Modding_Tutorials/Decompiling source code|Decompiling Source Code]] - How to set up and use a decompiler to read vanilla game code
* [[Modding_Tutorials/Setting up a solution|Setting up a Solution]] - How to set up a solution for compiling a custom mod assembly
* [[Modding_Tutorials/Application_Startup|Application Startup]] - Describes the application startup process and the order in which game data is loaded
* Custom Consumable (Upcoming)
* Custom Overlays (Upcoming)
* [[Modding_Tutorials/Code_FloatMenuOptionProvider|FloatMenuOptionProvider]] - How to use <code>FloatMenuOptionProvider</code> to add right click context menu options to arbitrary targets.
* [[Modding_Tutorials/Code_MendingJob|Example Mending Job]] - How to use a <code>FloatMenuOptionProvider</code> in conjunction with a <code>JobDef</code> and <code>JobDriver</code> in order to create a simple mending function for weapons and apparel.

===Updates and Migrations===

* [[Modding_Tutorials/RimWorld_1.5_Mod_Updates|RimWorld 1.5 Mod Updates]] - (WARNING: Anomaly Spoilers) Community notes for updating mods from 1.4 to 1.5.
* [[Modding_Tutorials/RimWorld_1.6_Mod_Updates|RimWorld 1.6 Mod Updates]] - (WARNING: Odyssey Spoilers) Community notes for updating mods from 1.5 to 1.6.

===Testing and Troubleshooting===

* [[Modding Tutorials/Testing mods|Testing Mods]] - Tips and tricks for testing mod content

===Performance and Optimization===

* [[Modding_Tutorials/Asset_Bundles|Asset Bundles]] - How to create Unity asset bundles for assets and shaders.

===Slightly Outdated===

* [[Modding_Tutorials/Plague_Gun|Plague Gun]] - This tutorial was created for RimWorld 1.0 but updated for 1.4. While the exact content is obsolete as you can now accomplish the same result with purely vanilla XML, it is still useful as a crash course for end-to-end mod creation and is here until newer tutorials can replace it.

===Uploading to Steam Workshop===
* You can upload your mod to Steam Workshop by enabling Development Mode from your game Options and then using the Upload option under the Advanced button in the vanilla mod manager.
* Note that in order to upload to Steam Workshop, you must own the game on Steam Workshop. Owning RimWorld on GOG or Epic will not work.
* Your Preview.png should be a 640x360 or 1280x720 PNG and '''must''' be under 1MB. If it is too large, then your upload will be rejected with <code>Error : Limit Exceeded</code>
* If you get a <code>OnItemSubmitted Fail</code> error, make sure you close any programs that are targeting items in your mods folder. This can also mean that Steam Workshop is having some technical issues at the moment. If it keeps occurring, then the only thing to do is to wait a few hours for it to clear up.
* Steam mod descriptions don't use markdown, they use a variant of BBCode. Please check out the [https://steamcommunity.com/comment/Guide/formattinghelp Steam text formatting guide].

-----

'''Note:''' All of the above tutorials have been cleaned up and reviewed by the #mod-development team on the [https://discord.gg/rimworld RimWorld Discord] in cooperation with RimWorld Wiki staff editors. Please let us know before creating, adding, or making any major edits to the vetted tutorials and guides section!

==Outdated / Under Review==

The following tutorials are either out of date or in need of a rewrite. The information in them might be useful but may not be up to standard; please be aware of any potential inaccuracies until they can be addressed.

* [[Modding Tutorials/First Steps|First Steps and Some Links]]
* [[Modding Tutorials/Essence| Essence of Modding]]
* [[Modding Troubleshooting Tips and Guides]]
* [[Modding Tutorials/Sounds|Adding and Testing Sounds]]
* [[Modding Tutorials/Assets|Decompiling Texture/Sound Assets]]
* [[Modding Tutorials/Compatibility|Compatibility]]
* [[Modding_Tutorials/Distribution|Distribution]]
* [[Modding_Tutorials/Modifying defs|Modifying Defs]]
* [[Modding_Tutorials/Troubleshooting|Troubleshooting mods]]
* [[Modding Tutorials/Rituals]]

===XML tutorials===

* [[Modding Tutorials/XML file structure|XML File Structure]]
* [[Modding Tutorials/XML Defs|Introduction to XML Defs]]
** [[Modding Tutorials/Compatibility with defs|XML Def Compatibility]]
** [[Modding Tutorials/ThingDef|ThingDef explained]]
** [[Modding Tutorials/Weapons Guns|Weapons_Guns.xml explained]]. Slightly dated.
* [[Modding Tutorials/Xenotype template]] originally by Ryflamer

===C# tutorials===
* [[Modding_Tutorials/Hello World|Hello World]]
* [[Modding_Tutorials/Writing custom code|Writing Custom Code]]
* [[Modding Tutorials/Linking XML and C#|Linking XML and C#]]
* [[Modding_Tutorials/Harmony|Alter Code at Runtime with Harmony]] - this is a best practice for modifying game code, replacing C# code injection to reduce Mod Conflicts
* [[Modding_Tutorials/Modifying classes|Adding fields and methods to classes]]
* [[Modding Tutorials/ModSettings|Mod settings]] - Add settings to your mod
* [[Modding Tutorials/DefModExtension|Def mod extensions]] - Add (custom) fields to Defs
* [[Modding Tutorials/Custom Comp Classes|Custom Comp Classes]] - A quick overview of what types of Comps there are, and what they're suited for.
* [[Modding_Tutorials/ThingComp|ThingComp]] - Learn all there is to know about ThingComps.
* [[Modding Tutorials/GameComponent|Components]] - GameComponents, WorldComponents, and MapComponents
* [[Modding_Tutorials/Def classes|Introduction to Def Classes]]
* [[Modding_Tutorials/Compatibility_with_DLLs|Using Harmony to optionally patch other mods for the sake of compatibility]]
* [[Modding Tutorials/TweakValue|TweakValues]] - Change values on the fly (handy for quick iteration!)
* [[Modding Tutorials/ExposeData|ExposeData]] - Save stuff
* [[Modding Tutorials/BigAssListOfUsefulClasses|The big ass list of useful classes]] - A non-exhaustive list of classes you'll use most
* [[Modding Tutorials/GrammarResolver|Grammar Resolver]] - PAWN_objective, PAWN_possessive? Find out what it all means here.
* [https://github.com/Mehni/ExampleJob/wiki ExampleJob] - Mehni's top to bottom breakdown of Jobs.
* [[Modding_Tutorials/ConfigErrors|Config Errors]] - Provide configuration issues to the user on startup.
* [[Modding Tutorials/DebugActions|Debug Actions]] - Call methods from the debug menu
* [https://www.arp242.net/rimworld-mod-linux.html Getting started with RimWorld modding on Linux]

===Art Tutorials===
* [https://spdskatr.github.io/RWModdingResources/artstyle Artstyle] - Officially unofficial guide to RimWorld's Artstyle
* Ekksu's animal texture guides: [https://imgur.com/a/how-to-make-rimworld-sprites-its-basically-x-with-y-edition-wS3Pt 1] [https://imgur.com/a/how-to-make-rimworld-sprites-theres-nothing-that-looks-like-this-animal-edition-xdDzg 2]
* [https://steamcommunity.com/sharedfiles/filedetails/?id=1114369188 ChickenPlucker's guide to creating apparel]
* [https://github.com/seraphile/rimshare/wiki/Colouring-in-Images Seraphile's guide to masks]

===Under Construction===

These are currently unfinished and need to be cleaned up or removed

* [[Modding Tutorials/Quests]]
* [[Modding Tutorials/Troubleshooting/Finding Exceptions]]

==External Links==
* [https://github.com/roxxploxx/RimWorldModGuide/wiki Roxxploxx's set of modding tutorials]
* [https://spdskatr.github.io/RWModdingResources/ RimWorld Modding Resources - A hub for guides, modders, practical tips]

[[Category:Modding]]
[[Category:Modding tutorials]]

Modding Tutorials/Asset Bundles

2026-06-25T22:56:06Z

Aelanna:

{{DISPLAYTITLE:Asset Bundles}}

{{BackToTutorials}}

{{:Modding_Tutorials/Under_Review}}

This tutorial explains what asset bundles are, why you might want them, and how they compare to the two other ways RimWorld can load custom art: loose textures and DDS files. It starts from zero, so you do not need to know anything about Unity going in. The later sections branch into the actual build process and then into the deeper stuff: shaders, sounds, fonts, and the things that go wrong.

== What is an asset bundle? ==

An asset bundle is a single file that holds a bunch of Unity assets already packed in the format the engine wants. RimWorld runs on Unity, and Unity has its own internal way of storing textures, meshes, shaders, audio, and so on. A loose PNG sitting in your mod's <code>Textures/</code> folder is not in that format yet, so the game has to convert it before it can use it.

A bundle is that conversion done ahead of time, saved to disk, and handed to the engine in one piece. The rest of this page is mostly consequences of that.

== Why would I care? ==

Two reasons, mostly:

'''Load time.''' When you ship loose PNGs, RimWorld converts every single one while the game boots (more on this in the next section). For a small mod you will never notice. For a mod with hundreds or thousands of textures, that conversion adds up, and it is part of why a heavily-modded load screen sits there for a while. A bundle skips the conversion because the work is already done.

'''Everything that is not a texture.''' Loose files only really work for textures and sounds. If you want to ship a custom shader, a custom font, a custom mesh, or anything else Unity-shaped, a bundle is the normal way to get it into the game. There is no <code>Shaders/</code> folder you can just drop a file into.

If your mod is XML and a handful of textures, you probably do not need bundles at all. If your mod is large, or it needs a custom shader or font, you do.

As of 1.6, bundles are the encouraged path for anything beyond a small loose-texture mod. The engine grew real first-class support for them: it loads them for you, swaps the right one per operating system, and serves their contents through the same content lookup you already use. Earlier versions made you wire all of that up by hand, which is why older tutorials look more involved than this one. On 1.6+ most of the friction is gone.

== Loose textures vs DDS vs asset bundles ==

All three of these get a texture onto the screen. They differ in '''when''' the work happens and '''what''' they can carry. Mix those two questions up and the whole topic gets confusing fast.

=== Loose textures (PNG) ===

You put a <code>.png</code> in your mod's <code>Textures/</code> folder and reference it by path. Simplest possible setup, and what almost every tutorial starts with. (The [[Modding_Tutorials/Textures|Textures]] page covers the path rules and texture conventions in full; this page assumes you have that down.)

RimWorld does not render your PNG directly. On load it converts the PNG into a compressed GPU texture (the same family of formats DDS uses) and caches the result. So the PNG is a source file, not the thing the GPU actually draws. That conversion is cheap for one texture and not cheap for a thousand.

* '''Pro:''' dead simple, easy to edit, easy to diff, no tooling.
* '''Con:''' the game pays a conversion cost on load, and you cannot ship anything other than textures and sounds this way.

=== DDS textures ===

A <code>.dds</code> file is a texture that is ''already'' in a GPU-ready compressed format. If you drop a DDS next to where the PNG would go, RimWorld uses it directly and skips the conversion step entirely.

So the loose-vs-DDS question is mostly about that conversion cost, not about how the final image looks. A correctly-made DDS and the game's own PNG conversion land in roughly the same place visually. What DDS buys you is a faster load and no first-load hitch, because the expensive part already happened on your machine when you made the file.

The catch is you have to ''make'' the DDS, and if you make it wrong (wrong compression, no mipmaps, wrong color space) it can look worse than just letting the game convert the PNG. It is a real win for large texture sets, and a footgun for people who do not know what BC7 or mipmaps are.

* '''Pro:''' no runtime conversion, faster load, no first-load stutter for that texture.
* '''Con:''' you have to generate it correctly, harder to edit after the fact, much larger on disk than the source PNGs, and still textures-only.

=== Asset bundles ===

A bundle is the next step up. It is one file that can hold many textures (already in GPU format, like DDS, so same load-time win) ''plus'' meshes, shaders, fonts, and audio. Instead of hundreds of loose files converted one by one, the engine loads one bundle and everything inside is ready to go.

The trade is that a bundle is opaque. You cannot open it in an image editor and tweak a pixel. You rebuild it from your source assets, which means you keep your editable PNGs and Unity sources somewhere and treat the bundle as a build output, the same way you treat a compiled DLL.

* '''Pro:''' fastest load for large asset sets, one file instead of thousands, and it is the only option for shaders, fonts, and custom meshes.
* '''Con:''' you need a build step and the Unity tooling to produce it, and the output is not hand-editable.

=== Quick comparison ===

{| class="wikitable"
! Approach !! Load cost !! Disk size !! Can carry !! Editable after build? !! Good for
|-
| Loose PNG || Converted every load || Small || Textures, sounds || Yes || Small mods, prototyping
|-
| DDS || None (pre-converted) || Large || Textures || Painful || Large texture sets
|-
| Asset bundle || None (pre-converted) || Smallest || Textures, meshes, shaders, fonts, audio || No (rebuild from source) || Large mods, anything non-texture
|}

That disk-size column is worth some real numbers. Take one texture set of around 960 files and store it all three ways:

* As loose PNGs: about 40 MB.
* Converted to DDS: about 230 MB. The conversion skips the runtime work but blows up the size on disk.
* Packed into a single asset bundle: about 28 MB.

So DDS is the ''largest'' on disk, not the smallest. It trades space for skipping the load-time conversion. The bundle gets that same load-time win and still ends up the smallest of the three, because it is compressed into one file. (Numbers from a comparison shared in the [https://discord.com/channels/214523379766525963/632790371256238120/1405733585268375643 RimWorld modding Discord]; your exact figures will vary with the texture set and compression settings.)

== The workflow, in plain terms ==

Before any code or folder layout, here is what building a bundle actually looks like from a height:

# You keep your real, editable source assets (PNGs, Unity materials, shader files, font files) in a Unity project.
# In that Unity project you tag each asset with a bundle name, then tell Unity to build the bundles.
# Unity spits out the bundle files.
# You ship those bundle files inside your RimWorld mod.
# At game load, RimWorld finds the bundle on its own and serves its contents through the normal content lookup (1.6 does the loading for you; textures and sounds resolve by their existing path, while shaders and fonts you still fetch by name in code).

That is the loop. You edit in Unity, build, copy the output into your mod, and the game picks it up. The first time through it feels like a lot of ceremony for a texture. Once it is set up, adding a new asset is just "drop it in the Unity project, rebuild, copy."

You do not have to do every step by hand. The next section covers that before the build details, so you can go find a tool first if you would rather not set this up yourself.

== Before we get started: Do I actually have to do everything below? ==

No. Setting up the Unity project, writing the build script, and juggling per-platform bundles is fiddly enough that several modders have written tools to do it for you. They wrap the whole thing, handle the multi-platform build, and spit out ready-to-ship bundles without you babysitting the Unity editor. If that sounds like what you want, you can stop here and go find one; the rest of this page is for when you want to understand what those tools are doing or build it yourself.

This tutorial does not point at any specific one on purpose, since they come and go and get superseded. A search on Google or GitHub for RimWorld asset bundle tooling turns them up, and the modding Discord communities are usually the fastest place to find out which one people are actually using right now and which one is abandoned. Ask there before sinking an afternoon into a tool that got replaced six months ago.

== Branch: the real build steps ==

If you want the actual mechanics, here they are. First, install the right Unity editor. This matters more than anything else on this page: a bundle built on the wrong Unity version may silently fail to load. RimWorld 1.6 runs on '''Unity 2022.3.35f1''', so install exactly that version through the Unity Hub (under "Add" you can pick a specific archived version, or grab it from the Unity download archive). Build your bundles in 2022.3.35f1 and they line up with what the game expects. If RimWorld updates to a new Unity version down the line, you rebuild against the new one.

=== Folder layout ===

Inside your mod, bundles usually live somewhere like:

MyMod/
About/
Defs/
Textures/
AssetBundles/
mymod_assets_win
mymod_assets_mac
mymod_assets_linux

The bundle file itself has no extension. You name it whatever you tagged it in Unity, with the OS suffix on the end (see the deep dive for why the three files). There is no <code>.dll</code> required to use a bundle: a pure XML-and-textures mod can ship a bundle and never write a line of C#, because the game loads it and serves its contents automatically.

=== Tagging and building in Unity ===

In the Unity project, select an asset, and at the bottom of the Inspector there is an AssetBundle dropdown. Assign a bundle name there. Everything sharing that name builds into the same bundle.

Then you need a small editor script to actually trigger the build, because Unity does not expose bundle building in the default menus.

The bare version is just one <code>BuildPipeline.BuildAssetBundles</code> call. It works, but it ships your textures with whatever import settings they happened to have, which is usually uncompressed and wasteful. Controlling how each texture imports before it gets packed is what actually shrinks the disk and memory footprint, so the script below does two things: it walks your textures and sets sane import settings on each, then builds.

<pre>
using UnityEditor;
using UnityEngine;
using System.IO;

public static class BundleBuilder
{
[MenuItem("Assets/Build AssetBundles")]
static void Build()
{
// First pass: set good import settings on every texture in the project.
foreach (string guid in AssetDatabase.FindAssets("t:Texture2D"))
{
string assetPath = AssetDatabase.GUIDToAssetPath(guid);
if (AssetImporter.GetAtPath(assetPath) is not TextureImporter tex) continue;

string lower = assetPath.ToLower();
bool isTerrain = lower.Contains("/terrain/");
bool isMask = lower.Contains("_mask");
bool isNormal = lower.Contains("_normal");

// GUI type suits RimWorld's flat 2D art and avoids Unity generating sprite sub-assets.
tex.textureType = isNormal ? TextureImporterType.NormalMap : TextureImporterType.GUI;
tex.alphaIsTransparency = true;

// Mask and normal maps hold raw data, not color, so they must stay linear (sRGB off).
tex.sRGBTexture = !isMask && !isNormal;

// Terrain tiles repeat across the ground; everything else should clamp at its edges.
tex.wrapMode = isTerrain ? TextureWrapMode.Repeat : TextureWrapMode.Clamp;
tex.anisoLevel = isTerrain ? 8 : 1;

tex.filterMode = FilterMode.Trilinear;
tex.mipmapEnabled = true;

// BC7 high-quality compression: small on disk and in VRAM, good for hand-painted art.
tex.SetPlatformTextureSettings(new TextureImporterPlatformSettings
{
name = "Standalone",
overridden = true,
format = TextureImporterFormat.BC7,
maxTextureSize = 4096,
textureCompression = TextureImporterCompression.CompressedHQ
});

tex.SaveAndReimport();
}

// Second pass: build the bundles.
string output = "Assets/BuiltBundles";
Directory.CreateDirectory(output);
BuildPipeline.BuildAssetBundles(
output,
BuildAssetBundleOptions.ChunkBasedCompression, // LZ4
BuildTarget.StandaloneWindows64
);
}
}
</pre>

A few notes on what that import pass is doing:

* '''BC7 + CompressedHQ''' is the compression that gets you the small disk and VRAM footprint. Without it the texture sits in memory uncompressed.
* '''sRGB off for masks and normal maps.''' A stuff-color mask or a normal map stores data, not a picture, so it must be read as linear. Leaving sRGB on silently corrupts it. The script keys off <code>_mask</code> and <code>_normal</code> in the filename, so name your files accordingly.
* '''Terrain repeats, everything else clamps.''' Terrain tiles need <code>Repeat</code> wrap so they tile seamlessly across the ground; a regular sprite wants <code>Clamp</code> so its edges do not bleed. The script keys off a <code>/Terrain/</code> folder in the path.
* '''Mipmaps on''' so the texture does not shimmer when the camera zooms out.

This is a trimmed-down version of what dedicated bundle-building tools do; they also handle audio compression, font atlas generation, and per-bundle include/exclude rules. The texture settings above are the ones worth knowing by hand. Run the menu item, Unity reimports the textures and writes the bundles to the output folder, and you copy the ones you care about into your mod's <code>AssetBundles/</code> folder.

=== Loading the bundle in your mod ===

In 1.6 you do not load the bundle yourself at all, which catches people off guard since the older docs make it look involved. RimWorld scans every active mod's <code>AssetBundles/</code> folder on startup, loads what it finds, and keeps the loaded bundles on the mod. You do not write <code>AssetBundle.LoadFromFile</code>, you do not call <code>LoadAsset</code>, you do not run anything in a static constructor.

The game's normal content lookup also checks bundles for you. When you ask for a texture the usual way, with <code>ContentFinder<Texture2D>.Get("Things/Item/MyThing")</code>, RimWorld first looks for a loose file at that path, and if it does not find one it looks inside your loaded bundles at the matching path. Same call, same path string, whether the texture is loose or bundled. The asset just has to live at the same path inside the bundle that the loose file would have used (so an asset packed at <code>Textures/Things/Item/MyThing</code> resolves for the path above).

The practical upshot: for textures and sounds you do not change a single line of your mod's code to switch from loose to bundled. You reference them by path like you always did. You only build a bundle, drop it in the folder, and the game finds the contents.

The exception is shaders. The content lookup skips the loose-file step for shaders entirely (there is no loose-shader path), so a shader is only ever found inside a bundle. <code>ContentFinder<Shader>.Get("MyShaderName")</code> works, but only because the shader is in a bundle for it to find.

== Branch: the deep dive ==

Most of this only comes up once you are shipping a shader or a font. A small texture-only mod can skip the whole section.

=== Shaders and the cross-platform problem ===

A compiled shader is platform-specific, which is why a lot of mods end up shipping multiple bundles. A shader built for DirectX (Windows) is not the same bytes as one built for Metal (Mac) or Vulkan/OpenGL (Linux). If you build one bundle on Windows and ship it, your shader works on Windows and quietly fails on Mac and Linux, usually showing up as bright magenta where the texture should be.

The fix is to build a bundle per platform, and 1.6 makes this almost free because the game does the picking for you. Name your bundle files with the suffix the game looks for:

* <code>mymod_assets_win</code> loads on Windows
* <code>mymod_assets_mac</code> loads on Mac
* <code>mymod_assets_linux</code> loads on Linux

The game checks the running platform and loads only the matching one. A bundle with no suffix at all loads on every platform, which is fine for textures and meshes that do not care, but not safe for shaders. So you build the same assets three times in Unity with different <code>BuildTarget</code> values (<code>StandaloneWindows64</code>, <code>StandaloneOSX</code>, <code>StandaloneLinux64</code>), give each the right suffix, and ship all three. You write no platform-detection code yourself.

If you have ever installed a mod that worked fine for everyone except the Mac and Linux players who saw pink everywhere, this is almost always why.

=== Sounds ===

Audio can go in a bundle as an <code>AudioClip</code>, and for a lot of sounds it is fine and saves you the loose-file management. RimWorld can also load loose audio through its normal sound def system, so for ordinary sound effects you often do not need a bundle at all. Where bundles help is when you want the audio packed with everything else, or when you are loading clips directly from code rather than through a SoundDef.

=== Fonts ===

If you want a custom font in your UI, a bundle is the way. You import the font into Unity, build it into a bundle, load it as a <code>Font</code>, and assign it where you draw text. There is no loose-font path in RimWorld at all, so here the bundle is not a speed-up, it is the only way in.

=== Meshes ===

Same story as fonts. Custom 3D meshes (not the usual flat sprites, actual geometry) come in through a bundle as a <code>Mesh</code>. Most RimWorld mods never touch this, but if you are doing something with real geometry it is here.

=== Compression and a couple of gotchas ===

A few things worth knowing before you spend an afternoon confused:

* '''Unity version mismatch.''' A bundle built on a different Unity version than the game uses may refuse to load, often with no clear error, the asset just comes back null. Build on Unity 2022.3.35f1 for RimWorld 1.6. This is the single most common reason a bundle that worked in the editor does nothing in-game.
* '''Bundle file compression.''' This is how the bundle file is packed on disk, separate from texture compression below. Bundles can be built uncompressed, LZ4, or LZMA. LZ4 is the usual sweet spot: small enough, and it does not stall on load the way LZMA can. <code>BuildAssetBundleOptions.ChunkBasedCompression</code> gives you LZ4.
* '''In-memory texture compression and the white-outline bug.''' Loose textures are compressed in memory once loaded, and that compression is what produces the faint white halo people sometimes see around a sprite (the art program threw away color data in fully transparent pixels). A bundle lets you turn that in-memory compression off for its textures, which sidesteps the halo without the usual workaround of padding the outline. The [[Modding_Tutorials/Textures|Textures]] page documents the bug and the loose-texture fix.
* '''Shader stripping.''' Unity sometimes strips shader variants it thinks are unused during the build, and then your shader looks wrong at runtime because the variant you needed got cut. If a shader misbehaves only in the built bundle but works in the editor, this is a likely suspect.
* '''Color space.''' If your textures look washed out or too dark coming out of a bundle, check that the import settings and color space match what the game expects. This is the same class of problem that makes a hand-rolled DDS look wrong.

== Summary ==

* Loose PNG: simplest, but converted on every load and limited to textures and sounds.
* DDS: a texture pre-converted to GPU format, so it skips the load-time conversion. Same final look, faster load, but you have to make it right, and it lands much larger on disk than the source PNGs.
* Asset bundle: one pre-packed file that carries textures, meshes, shaders, fonts, and audio. The fastest option for big mods and the only option for shaders, fonts, and custom meshes.

If your mod is small, stay loose. If it is large or needs anything Unity-shaped beyond a texture, learn bundles, and on 1.6+ that is the encouraged path anyway since the engine does the loading and per-OS swapping for you. And if you are shipping a shader, build one bundle per platform with the right suffix, or your Mac and Linux players get magenta.

[[Category:Modding]]
[[Category:Modding tutorials]]

Modding Tutorials/Asset Bundles

2026-06-25T22:42:58Z

Aelanna: Added banner

{{DISPLAYTITLE:Asset Bundles}}

{{BackToTutorials}}

{{:Modding_Tutorials/Under_Review}}

This tutorial explains what asset bundles are, why you might want them, and how they compare to the two other ways RimWorld can load custom art: loose textures and DDS files. It starts from zero, so you do not need to know anything about Unity going in. The later sections branch into the actual build process and then into the deeper stuff: shaders, sounds, fonts, and the things that go wrong.

== What is an asset bundle? ==

An asset bundle is a single file that holds a bunch of Unity assets already packed in the format the engine wants. RimWorld runs on Unity, and Unity has its own internal way of storing textures, meshes, shaders, audio, and so on. A loose PNG sitting in your mod's <code>Textures/</code> folder is not in that format yet, so the game has to convert it before it can use it.

A bundle is that conversion done ahead of time, saved to disk, and handed to the engine in one piece. The rest of this page is mostly consequences of that.

== Why would I care? ==

Two reasons, mostly:

'''Load time.''' When you ship loose PNGs, RimWorld converts every single one while the game boots (more on this in the next section). For a small mod you will never notice. For a mod with hundreds or thousands of textures, that conversion adds up, and it is part of why a heavily-modded load screen sits there for a while. A bundle skips the conversion because the work is already done.

'''Everything that is not a texture.''' Loose files only really work for textures and sounds. If you want to ship a custom shader, a custom font, a custom mesh, or anything else Unity-shaped, a bundle is the normal way to get it into the game. There is no <code>Shaders/</code> folder you can just drop a file into.

If your mod is XML and a handful of textures, you probably do not need bundles at all. If your mod is large, or it needs a custom shader or font, you do.

As of 1.6, bundles are the encouraged path for anything beyond a small loose-texture mod. The engine grew real first-class support for them: it loads them for you, swaps the right one per operating system, and serves their contents through the same content lookup you already use. Earlier versions made you wire all of that up by hand, which is why older tutorials look more involved than this one. On 1.6+ most of the friction is gone.

== Loose textures vs DDS vs asset bundles ==

All three of these get a texture onto the screen. They differ in '''when''' the work happens and '''what''' they can carry. Mix those two questions up and the whole topic gets confusing fast.

=== Loose textures (PNG) ===

You put a <code>.png</code> in your mod's <code>Textures/</code> folder and reference it by path. Simplest possible setup, and what almost every tutorial starts with. (The [[Modding_Tutorials/Textures|Textures]] page covers the path rules and texture conventions in full; this page assumes you have that down.)

RimWorld does not render your PNG directly. On load it converts the PNG into a compressed GPU texture (the same family of formats DDS uses) and caches the result. So the PNG is a source file, not the thing the GPU actually draws. That conversion is cheap for one texture and not cheap for a thousand.

* '''Pro:''' dead simple, easy to edit, easy to diff, no tooling.
* '''Con:''' the game pays a conversion cost on load, and you cannot ship anything other than textures and sounds this way.

=== DDS textures ===

A <code>.dds</code> file is a texture that is ''already'' in a GPU-ready compressed format. If you drop a DDS next to where the PNG would go, RimWorld uses it directly and skips the conversion step entirely.

So the loose-vs-DDS question is mostly about that conversion cost, not about how the final image looks. A correctly-made DDS and the game's own PNG conversion land in roughly the same place visually. What DDS buys you is a faster load and no first-load hitch, because the expensive part already happened on your machine when you made the file.

The catch is you have to ''make'' the DDS, and if you make it wrong (wrong compression, no mipmaps, wrong color space) it can look worse than just letting the game convert the PNG. It is a real win for large texture sets, and a footgun for people who do not know what BC7 or mipmaps are.

* '''Pro:''' no runtime conversion, faster load, no first-load stutter for that texture.
* '''Con:''' you have to generate it correctly, harder to edit after the fact, much larger on disk than the source PNGs, and still textures-only.

=== Asset bundles ===

A bundle is the next step up. It is one file that can hold many textures (already in GPU format, like DDS, so same load-time win) ''plus'' meshes, shaders, fonts, and audio. Instead of hundreds of loose files converted one by one, the engine loads one bundle and everything inside is ready to go.

The trade is that a bundle is opaque. You cannot open it in an image editor and tweak a pixel. You rebuild it from your source assets, which means you keep your editable PNGs and Unity sources somewhere and treat the bundle as a build output, the same way you treat a compiled DLL.

* '''Pro:''' fastest load for large asset sets, one file instead of thousands, and it is the only option for shaders, fonts, and custom meshes.
* '''Con:''' you need a build step and the Unity tooling to produce it, and the output is not hand-editable.

=== Quick comparison ===

{| class="wikitable"
! Approach !! Load cost !! Disk size !! Can carry !! Editable after build? !! Good for
|-
| Loose PNG || Converted every load || Small || Textures, sounds || Yes || Small mods, prototyping
|-
| DDS || None (pre-converted) || Large || Textures || Painful || Large texture sets
|-
| Asset bundle || None (pre-converted) || Smallest || Textures, meshes, shaders, fonts, audio || No (rebuild from source) || Large mods, anything non-texture
|}

That disk-size column is worth some real numbers. Take one texture set of around 960 files and store it all three ways:

* As loose PNGs: about 40 MB.
* Converted to DDS: about 230 MB. The conversion skips the runtime work but blows up the size on disk.
* Packed into a single asset bundle: about 28 MB.

So DDS is the ''largest'' on disk, not the smallest. It trades space for skipping the load-time conversion. The bundle gets that same load-time win and still ends up the smallest of the three, because it is compressed into one file. (Numbers from a comparison shared in the [https://discord.com/channels/214523379766525963/632790371256238120/1405733585268375643 RimWorld modding Discord]; your exact figures will vary with the texture set and compression settings.)

== The workflow, in plain terms ==

Before any code or folder layout, here is what building a bundle actually looks like from a height:

# You keep your real, editable source assets (PNGs, Unity materials, shader files, font files) in a Unity project.
# In that Unity project you tag each asset with a bundle name, then tell Unity to build the bundles.
# Unity spits out the bundle files.
# You ship those bundle files inside your RimWorld mod.
# At game load, RimWorld finds the bundle on its own and serves its contents through the normal content lookup (1.6 does the loading for you; textures and sounds resolve by their existing path, while shaders and fonts you still fetch by name in code).

That is the loop. You edit in Unity, build, copy the output into your mod, and the game picks it up. The first time through it feels like a lot of ceremony for a texture. Once it is set up, adding a new asset is just "drop it in the Unity project, rebuild, copy."

You do not have to do every step by hand. The next section covers that before the build details, so you can go find a tool first if you would rather not set this up yourself.

== Before we get started: Do I actually have to do everything below? ==

No. Setting up the Unity project, writing the build script, and juggling per-platform bundles is fiddly enough that several modders have written tools to do it for you. They wrap the whole thing, handle the multi-platform build, and spit out ready-to-ship bundles without you babysitting the Unity editor. If that sounds like what you want, you can stop here and go find one; the rest of this page is for when you want to understand what those tools are doing or build it yourself.

This tutorial does not point at any specific one on purpose, since they come and go and get superseded. A search on Google or GitHub for RimWorld asset bundle tooling turns them up, and the modding Discord communities are usually the fastest place to find out which one people are actually using right now and which one is abandoned. Ask there before sinking an afternoon into a tool that got replaced six months ago.

== Branch: the real build steps ==

If you want the actual mechanics, here they are. First, install the right Unity editor. This matters more than anything else on this page: a bundle built on the wrong Unity version may silently fail to load. RimWorld 1.6 runs on '''Unity 2022.3.35f1''', so install exactly that version through the Unity Hub (under "Add" you can pick a specific archived version, or grab it from the Unity download archive). Build your bundles in 2022.3.35f1 and they line up with what the game expects. If RimWorld updates to a new Unity version down the line, you rebuild against the new one.

=== Folder layout ===

Inside your mod, bundles usually live somewhere like:

MyMod/
About/
Defs/
Textures/
AssetBundles/
mymod_assets_win
mymod_assets_mac
mymod_assets_linux

The bundle file itself has no extension. You name it whatever you tagged it in Unity, with the OS suffix on the end (see the deep dive for why the three files). There is no <code>.dll</code> required to use a bundle: a pure XML-and-textures mod can ship a bundle and never write a line of C#, because the game loads it and serves its contents automatically.

=== Tagging and building in Unity ===

In the Unity project, select an asset, and at the bottom of the Inspector there is an AssetBundle dropdown. Assign a bundle name there. Everything sharing that name builds into the same bundle.

Then you need a small editor script to actually trigger the build, because Unity does not expose bundle building in the default menus.

The bare version is just one <code>BuildPipeline.BuildAssetBundles</code> call. It works, but it ships your textures with whatever import settings they happened to have, which is usually uncompressed and wasteful. Controlling how each texture imports before it gets packed is what actually shrinks the disk and memory footprint, so the script below does two things: it walks your textures and sets sane import settings on each, then builds.

<pre>
using UnityEditor;
using UnityEngine;
using System.IO;

public static class BundleBuilder
{
[MenuItem("Assets/Build AssetBundles")]
static void Build()
{
// First pass: set good import settings on every texture in the project.
foreach (string guid in AssetDatabase.FindAssets("t:Texture2D"))
{
string assetPath = AssetDatabase.GUIDToAssetPath(guid);
if (AssetImporter.GetAtPath(assetPath) is not TextureImporter tex) continue;

string lower = assetPath.ToLower();
bool isTerrain = lower.Contains("/terrain/");
bool isMask = lower.Contains("_mask");
bool isNormal = lower.Contains("_normal");

// GUI type suits RimWorld's flat 2D art and avoids Unity generating sprite sub-assets.
tex.textureType = isNormal ? TextureImporterType.NormalMap : TextureImporterType.GUI;
tex.alphaIsTransparency = true;

// Mask and normal maps hold raw data, not color, so they must stay linear (sRGB off).
tex.sRGBTexture = !isMask && !isNormal;

// Terrain tiles repeat across the ground; everything else should clamp at its edges.
tex.wrapMode = isTerrain ? TextureWrapMode.Repeat : TextureWrapMode.Clamp;
tex.anisoLevel = isTerrain ? 8 : 1;

tex.filterMode = FilterMode.Trilinear;
tex.mipmapEnabled = true;

// BC7 high-quality compression: small on disk and in VRAM, good for hand-painted art.
tex.SetPlatformTextureSettings(new TextureImporterPlatformSettings
{
name = "Standalone",
overridden = true,
format = TextureImporterFormat.BC7,
maxTextureSize = 4096,
textureCompression = TextureImporterCompression.CompressedHQ
});

tex.SaveAndReimport();
}

// Second pass: build the bundles.
string output = "Assets/BuiltBundles";
Directory.CreateDirectory(output);
BuildPipeline.BuildAssetBundles(
output,
BuildAssetBundleOptions.ChunkBasedCompression, // LZ4
BuildTarget.StandaloneWindows64
);
}
}
</pre>

A few notes on what that import pass is doing:

* '''BC7 + CompressedHQ''' is the compression that gets you the small disk and VRAM footprint. Without it the texture sits in memory uncompressed.
* '''sRGB off for masks and normal maps.''' A stuff-color mask or a normal map stores data, not a picture, so it must be read as linear. Leaving sRGB on silently corrupts it. The script keys off <code>_mask</code> and <code>_normal</code> in the filename, so name your files accordingly.
* '''Terrain repeats, everything else clamps.''' Terrain tiles need <code>Repeat</code> wrap so they tile seamlessly across the ground; a regular sprite wants <code>Clamp</code> so its edges do not bleed. The script keys off a <code>/Terrain/</code> folder in the path.
* '''Mipmaps on''' so the texture does not shimmer when the camera zooms out.

This is a trimmed-down version of what dedicated bundle-building tools do; they also handle audio compression, font atlas generation, and per-bundle include/exclude rules. The texture settings above are the ones worth knowing by hand. Run the menu item, Unity reimports the textures and writes the bundles to the output folder, and you copy the ones you care about into your mod's <code>AssetBundles/</code> folder.

=== Loading the bundle in your mod ===

In 1.6 you do not load the bundle yourself at all, which catches people off guard since the older docs make it look involved. RimWorld scans every active mod's <code>AssetBundles/</code> folder on startup, loads what it finds, and keeps the loaded bundles on the mod. You do not write <code>AssetBundle.LoadFromFile</code>, you do not call <code>LoadAsset</code>, you do not run anything in a static constructor.

The game's normal content lookup also checks bundles for you. When you ask for a texture the usual way, with <code>ContentFinder<Texture2D>.Get("Things/Item/MyThing")</code>, RimWorld first looks for a loose file at that path, and if it does not find one it looks inside your loaded bundles at the matching path. Same call, same path string, whether the texture is loose or bundled. The asset just has to live at the same path inside the bundle that the loose file would have used (so an asset packed at <code>Textures/Things/Item/MyThing</code> resolves for the path above).

The practical upshot: for textures and sounds you do not change a single line of your mod's code to switch from loose to bundled. You reference them by path like you always did. You only build a bundle, drop it in the folder, and the game finds the contents.

The exception is shaders. The content lookup skips the loose-file step for shaders entirely (there is no loose-shader path), so a shader is only ever found inside a bundle. <code>ContentFinder<Shader>.Get("MyShaderName")</code> works, but only because the shader is in a bundle for it to find.

== Branch: the deep dive ==

Most of this only comes up once you are shipping a shader or a font. A small texture-only mod can skip the whole section.

=== Shaders and the cross-platform problem ===

A compiled shader is platform-specific, which is why a lot of mods end up shipping multiple bundles. A shader built for DirectX (Windows) is not the same bytes as one built for Metal (Mac) or Vulkan/OpenGL (Linux). If you build one bundle on Windows and ship it, your shader works on Windows and quietly fails on Mac and Linux, usually showing up as bright magenta where the texture should be.

The fix is to build a bundle per platform, and 1.6 makes this almost free because the game does the picking for you. Name your bundle files with the suffix the game looks for:

* <code>mymod_assets_win</code> loads on Windows
* <code>mymod_assets_mac</code> loads on Mac
* <code>mymod_assets_linux</code> loads on Linux

The game checks the running platform and loads only the matching one. A bundle with no suffix at all loads on every platform, which is fine for textures and meshes that do not care, but not safe for shaders. So you build the same assets three times in Unity with different <code>BuildTarget</code> values (<code>StandaloneWindows64</code>, <code>StandaloneOSX</code>, <code>StandaloneLinux64</code>), give each the right suffix, and ship all three. You write no platform-detection code yourself.

If you have ever installed a mod that worked fine for everyone except the Mac and Linux players who saw pink everywhere, this is almost always why.

=== Sounds ===

Audio can go in a bundle as an <code>AudioClip</code>, and for a lot of sounds it is fine and saves you the loose-file management. RimWorld can also load loose audio through its normal sound def system, so for ordinary sound effects you often do not need a bundle at all. Where bundles help is when you want the audio packed with everything else, or when you are loading clips directly from code rather than through a SoundDef.

=== Fonts ===

If you want a custom font in your UI, a bundle is the way. You import the font into Unity, build it into a bundle, load it as a <code>Font</code>, and assign it where you draw text. There is no loose-font path in RimWorld at all, so here the bundle is not a speed-up, it is the only way in.

=== Meshes ===

Same story as fonts. Custom 3D meshes (not the usual flat sprites, actual geometry) come in through a bundle as a <code>Mesh</code>. Most RimWorld mods never touch this, but if you are doing something with real geometry it is here.

=== Compression and a couple of gotchas ===

A few things worth knowing before you spend an afternoon confused:

* '''Unity version mismatch.''' A bundle built on a different Unity version than the game uses may refuse to load, often with no clear error, the asset just comes back null. Build on Unity 2022.3.35f1 for RimWorld 1.6. This is the single most common reason a bundle that worked in the editor does nothing in-game.
* '''Bundle file compression.''' This is how the bundle file is packed on disk, separate from texture compression below. Bundles can be built uncompressed, LZ4, or LZMA. LZ4 is the usual sweet spot: small enough, and it does not stall on load the way LZMA can. <code>BuildAssetBundleOptions.ChunkBasedCompression</code> gives you LZ4.
* '''In-memory texture compression and the white-outline bug.''' Loose textures are compressed in memory once loaded, and that compression is what produces the faint white halo people sometimes see around a sprite (the art program threw away color data in fully transparent pixels). A bundle lets you turn that in-memory compression off for its textures, which sidesteps the halo without the usual workaround of padding the outline. The [[Modding_Tutorials/Textures|Textures]] page documents the bug and the loose-texture fix.
* '''Shader stripping.''' Unity sometimes strips shader variants it thinks are unused during the build, and then your shader looks wrong at runtime because the variant you needed got cut. If a shader misbehaves only in the built bundle but works in the editor, this is a likely suspect.
* '''Color space.''' If your textures look washed out or too dark coming out of a bundle, check that the import settings and color space match what the game expects. This is the same class of problem that makes a hand-rolled DDS look wrong.

== Summary ==

* Loose PNG: simplest, but converted on every load and limited to textures and sounds.
* DDS: a texture pre-converted to GPU format, so it skips the load-time conversion. Same final look, faster load, but you have to make it right.
* Asset bundle: one pre-packed file that carries textures, meshes, shaders, fonts, and audio. The fastest option for big mods and the only option for shaders, fonts, and custom meshes.

If your mod is small, stay loose. If it is large or needs anything Unity-shaped beyond a texture, learn bundles, and on 1.6+ that is the encouraged path anyway since the engine does the loading and per-OS swapping for you. And if you are shipping a shader, build one bundle per platform with the right suffix, or your Mac and Linux players get magenta.

[[Category:Modding]]
[[Category:Modding tutorials]]

Modding Tutorials

2026-06-25T22:42:32Z

Aelanna: Added link to asset bundles guide.

{| align=center
| {{Mods_Nav}}
|}
<hr>

This is the hub page for tutorials, guides, and reference materials for creating mods for RimWorld. If you are looking for instructions on how to use RimWorld, please check out the general [[Modding]] hub.

As RimWorld does not have a formal modding API, nearly all of the information here has been gathered and maintained by the modding community.

'''NEW: [[Modding_Tutorials/RimWorld_1.6_Mod_Updates|RimWorld 1.6 Mod Updates]]''' - A work-in-progress list of changes datamined by the modding community in the current unstable version of RimWorld 1.6. '''THERE MAY BE ODYSSEY DLC SPOILERS, YOU HAVE BEEN WARNED.'''

-----

==About RimWorld==
RimWorld is a multi-platform game written on Unity 2022.3.35. However, the Unity Editor is not used for creating mods unless you are creating new shaders or building optional asset bundles.

* [[Modding_Tutorials/Recommended_software|Recommended Software]] - Editors and other useful software for mod development
* [[Modding_Tutorials/Mod_Folder_Structure|Mod Folder Structure]] - Explore the basic folder structure of a mod
** [[Modding_Tutorials/About.xml|About.xml]] - About.xml identifies and describes your mod to RimWorld so that it can be loaded properly

===Game Systems Guides===

* [[Modding_Tutorials/Defs|Defs]] - XML Definitions are used to define and configure content in a way that does not require compiling code
** [[Modding_Tutorials/MayRequire|MayRequire]] - MayRequire and MayRequireAnyOf are used to conditionally load Defs and list entries based on whether a DLC or other mod is loaded
* [[Modding_Tutorials/Localization|Localization]] - Define text strings used for translations and word lists used in name and text generation
* [[Modding_Tutorials/PatchOperations|PatchOperations]] - PatchOperations are used to modify XML Defs without overwriting them completely
* [[Modding_Tutorials/Sounds|Sounds]] - (Needs Rewriting) Adding sound files for mods
* [[Modding_Tutorials/Textures|Textures]] - How to create and add textures to mods
* [[Modding Tutorials/Plant Rendering|Plant Rendering]] - An explanation of how plant textures are rendered
* [[Modding_Tutorials/Research_Projects|Research Projects]] - How to create and use research projects.
* [[Modding_Tutorials/Asset_Bundles|Asset Bundles]] - How to create Unity asset bundles for assets and shaders.

===XML Tutorials===

The following are step-by-step tutorials for creating basic content mods.

Basic Tutorials:
* [[Modding_Tutorials/Basic_Melee_Weapon|Basic Melee Weapon]] - How to create a basic melee weapon with a texture mask
* [[Modding_Tutorials/Basic_Ranged_Weapon|Basic Ranged Weapon]] - How to create a basic ranged weapon with custom sound effects
* [[Modding_Tutorials/Basic_Plant|Basic Plant]] - How to create a custom plant with both a cultivated and wild variant
* Custom Animal (Upcoming)
* Simple Building (Upcoming)
* Custom Workbench (Upcoming)
* Custom Drug (Upcoming)

Advanced Tutorials:
* Custom Faction (Upcoming)
* Custom Culture (Upcoming)
* Custom Trader Type (Upcoming)

===C# Guides===

C# is used to create and define custom game behaviors

* [[Modding_Tutorials/Decompiling source code|Decompiling Source Code]] - How to set up and use a decompiler to read vanilla game code
* [[Modding_Tutorials/Setting up a solution|Setting up a Solution]] - How to set up a solution for compiling a custom mod assembly
* [[Modding_Tutorials/Application_Startup|Application Startup]] - Describes the application startup process and the order in which game data is loaded
* Custom Consumable (Upcoming)
* Custom Overlays (Upcoming)
* [[Modding_Tutorials/Code_FloatMenuOptionProvider|FloatMenuOptionProvider]] - How to use <code>FloatMenuOptionProvider</code> to add right click context menu options to arbitrary targets.
* [[Modding_Tutorials/Code_MendingJob|Example Mending Job]] - How to use a <code>FloatMenuOptionProvider</code> in conjunction with a <code>JobDef</code> and <code>JobDriver</code> in order to create a simple mending function for weapons and apparel.

===Updates and Migrations===

* [[Modding_Tutorials/RimWorld_1.5_Mod_Updates|RimWorld 1.5 Mod Updates]] - (WARNING: Anomaly Spoilers) Community notes for updating mods from 1.4 to 1.5.
* [[Modding_Tutorials/RimWorld_1.6_Mod_Updates|RimWorld 1.6 Mod Updates]] - (WARNING: Odyssey Spoilers) Community notes for updating mods from 1.5 to 1.6.

===Testing and Troubleshooting===

* [[Modding Tutorials/Testing mods|Testing Mods]] - Tips and tricks for testing mod content

===Slightly Outdated===

* [[Modding_Tutorials/Plague_Gun|Plague Gun]] - This tutorial was created for RimWorld 1.0 but updated for 1.4. While the exact content is obsolete as you can now accomplish the same result with purely vanilla XML, it is still useful as a crash course for end-to-end mod creation and is here until newer tutorials can replace it.

===Uploading to Steam Workshop===
* You can upload your mod to Steam Workshop by enabling Development Mode from your game Options and then using the Upload option under the Advanced button in the vanilla mod manager.
* Note that in order to upload to Steam Workshop, you must own the game on Steam Workshop. Owning RimWorld on GOG or Epic will not work.
* Your Preview.png should be a 640x360 or 1280x720 PNG and '''must''' be under 1MB. If it is too large, then your upload will be rejected with <code>Error : Limit Exceeded</code>
* If you get a <code>OnItemSubmitted Fail</code> error, make sure you close any programs that are targeting items in your mods folder. This can also mean that Steam Workshop is having some technical issues at the moment. If it keeps occurring, then the only thing to do is to wait a few hours for it to clear up.
* Steam mod descriptions don't use markdown, they use a variant of BBCode. Please check out the [https://steamcommunity.com/comment/Guide/formattinghelp Steam text formatting guide].

-----

'''Note:''' All of the above tutorials have been cleaned up and reviewed by the #mod-development team on the [https://discord.gg/rimworld RimWorld Discord] in cooperation with RimWorld Wiki staff editors. Please let us know before creating, adding, or making any major edits to the vetted tutorials and guides section!

==Outdated / Under Review==

The following tutorials are either out of date or in need of a rewrite. The information in them might be useful but may not be up to standard; please be aware of any potential inaccuracies until they can be addressed.

* [[Modding Tutorials/First Steps|First Steps and Some Links]]
* [[Modding Tutorials/Essence| Essence of Modding]]
* [[Modding Troubleshooting Tips and Guides]]
* [[Modding Tutorials/Sounds|Adding and Testing Sounds]]
* [[Modding Tutorials/Assets|Decompiling Texture/Sound Assets]]
* [[Modding Tutorials/Compatibility|Compatibility]]
* [[Modding_Tutorials/Distribution|Distribution]]
* [[Modding_Tutorials/Modifying defs|Modifying Defs]]
* [[Modding_Tutorials/Troubleshooting|Troubleshooting mods]]
* [[Modding Tutorials/Rituals]]

===XML tutorials===

* [[Modding Tutorials/XML file structure|XML File Structure]]
* [[Modding Tutorials/XML Defs|Introduction to XML Defs]]
** [[Modding Tutorials/Compatibility with defs|XML Def Compatibility]]
** [[Modding Tutorials/ThingDef|ThingDef explained]]
** [[Modding Tutorials/Weapons Guns|Weapons_Guns.xml explained]]. Slightly dated.
* [[Modding Tutorials/Xenotype template]] originally by Ryflamer

===C# tutorials===
* [[Modding_Tutorials/Hello World|Hello World]]
* [[Modding_Tutorials/Writing custom code|Writing Custom Code]]
* [[Modding Tutorials/Linking XML and C#|Linking XML and C#]]
* [[Modding_Tutorials/Harmony|Alter Code at Runtime with Harmony]] - this is a best practice for modifying game code, replacing C# code injection to reduce Mod Conflicts
* [[Modding_Tutorials/Modifying classes|Adding fields and methods to classes]]
* [[Modding Tutorials/ModSettings|Mod settings]] - Add settings to your mod
* [[Modding Tutorials/DefModExtension|Def mod extensions]] - Add (custom) fields to Defs
* [[Modding Tutorials/Custom Comp Classes|Custom Comp Classes]] - A quick overview of what types of Comps there are, and what they're suited for.
* [[Modding_Tutorials/ThingComp|ThingComp]] - Learn all there is to know about ThingComps.
* [[Modding Tutorials/GameComponent|Components]] - GameComponents, WorldComponents, and MapComponents
* [[Modding_Tutorials/Def classes|Introduction to Def Classes]]
* [[Modding_Tutorials/Compatibility_with_DLLs|Using Harmony to optionally patch other mods for the sake of compatibility]]
* [[Modding Tutorials/TweakValue|TweakValues]] - Change values on the fly (handy for quick iteration!)
* [[Modding Tutorials/ExposeData|ExposeData]] - Save stuff
* [[Modding Tutorials/BigAssListOfUsefulClasses|The big ass list of useful classes]] - A non-exhaustive list of classes you'll use most
* [[Modding Tutorials/GrammarResolver|Grammar Resolver]] - PAWN_objective, PAWN_possessive? Find out what it all means here.
* [https://github.com/Mehni/ExampleJob/wiki ExampleJob] - Mehni's top to bottom breakdown of Jobs.
* [[Modding_Tutorials/ConfigErrors|Config Errors]] - Provide configuration issues to the user on startup.
* [[Modding Tutorials/DebugActions|Debug Actions]] - Call methods from the debug menu
* [https://www.arp242.net/rimworld-mod-linux.html Getting started with RimWorld modding on Linux]

===Art Tutorials===
* [https://spdskatr.github.io/RWModdingResources/artstyle Artstyle] - Officially unofficial guide to RimWorld's Artstyle
* Ekksu's animal texture guides: [https://imgur.com/a/how-to-make-rimworld-sprites-its-basically-x-with-y-edition-wS3Pt 1] [https://imgur.com/a/how-to-make-rimworld-sprites-theres-nothing-that-looks-like-this-animal-edition-xdDzg 2]
* [https://steamcommunity.com/sharedfiles/filedetails/?id=1114369188 ChickenPlucker's guide to creating apparel]
* [https://github.com/seraphile/rimshare/wiki/Colouring-in-Images Seraphile's guide to masks]

===Under Construction===

These are currently unfinished and need to be cleaned up or removed

* [[Modding Tutorials/Quests]]
* [[Modding Tutorials/Troubleshooting/Finding Exceptions]]

==External Links==
* [https://github.com/roxxploxx/RimWorldModGuide/wiki Roxxploxx's set of modding tutorials]
* [https://spdskatr.github.io/RWModdingResources/ RimWorld Modding Resources - A hub for guides, modders, practical tips]

[[Category:Modding]]
[[Category:Modding tutorials]]

Xenogerm

2026-06-24T17:17:29Z

Aelanna: Minor rephrasing.

{{Biotech}}
{{Infobox main
| name = Xenogerm
| image = Xenogerm.png
| type = Medical Items
| type2 = Body Parts
| tech level = Industrial
| description = A self-contained biological organ containing one or more implantable xenogenes.<br/>Once implanted inside a host's body, the xenogerm modifies the host's genes, gene expression, and phenotypic development using viruses, hormones, bio-synthesized drugs, and possibly mechanites. Depending on the xenogerm, the host will develop any of a wide variety of exotic traits and abilities, transforming them into a different human xenotype.<br/>Xenogerm implantation is a traumatic process. Once implanted with a xenogerm, a person will be bedridden for days as the transformation sets in.<br/>During storage and transport, xenogerms are kept safe in sealed containers.
| production facility 1 = Gene assembler
| research = Xenogenetics
| work speed stat = Research Speed
| mass = 0.5
| marketvalue = 100
| max hit points base = 100
}}
A '''xenogerm''' is a specialized [[Biotech DLC|biotechnological]] organ used to change the [[Xenotype]] of a human pawn.

== Acquisition ==
Xenogerms are created at a [[gene assembler]] by combining the [[genes]] from [[genepack]]s stored in nearby [[gene bank]]s. The gene packs are not consumed. Creating a xenogerm is considered a form of research, and requires the [[intellectual]] skill. The actual time to create a xenogerm depends on the genetic complexity of the genes it contains. The base amount of work to assemble a xenogerm is {{Ticks|7500}}, with an additional {{Ticks|1250}} of work per level of complexity. For example, a xenogerm with a complexity of 3 would take {{Ticks|11250}} of work to assemble: <code>(7500 + (1250 * 3))</code>. These times are then scaled by the [[Assembly Speed Factor]] of the assembler and the [[{{Q|Xenogerm|Work Speed Stat}}]] of the pawn using the assembler.

Normally, xenogerms can be created for free. However, if they contain any archite genes, then the required number of [[File:Archite capsule required.png|16px|Archite Capsules]] [[archite capsules]] will need to be provided before gene recombination can begin.

== Summary ==
The purpose of a xenogerm is to change the xenotype of the pawn it is installed into. This is done through an implantation surgery. The effects of xenogermination are instant, and will change the affected pawn upon the surgery's completion. Xenogerms have a minimum metabolic efficiency of -5. Xenogerms below -5 metabolic efficiency cannot be assembled, and cannot be implanted if they would lower a pawn's metabolic efficiency to less than -5.

Xenogerms completely overwrite a pawn's ''[[xenogene]]s'', genes which are not passed down through [[reproduction]]. This will outright remove xenotypes that are defined by ''xenogenes'', such as [[genies]] or [[sanguophages]]. Xenotypes using ''germline'' genes, such as [[impids]], will not have those genes removed. However, germline genes will be suppressed if they would conflict with the xenogerm. For example, a [[fast runner]] xenogerm will completely suppress the [[slow runner]] germline gene found on a [[Dirtmole]].

Multiple xenogerms can be implanted in the same pawn, though each one overwrites the last. This includes archite genes, which effectively means that any archite capsules previously spent on the pawn will be lost.

=== Operation ===
[[File:Gizmo xenogerm order implantation.png|75px|thumb|left]]
Since each xenogerm is unique, its implantation must be ordered manually. There are three ways to do this:
* Select the xenogerm. Click on the "Order implantation" gizmo. Select the desired patient from the list.
* Select your patient. Right-click the xenogerm, then click "Order implantation".
* Select your patient. Open their health tab, then view their queued surgeries. Select "Add bill", then choose "Implant xenogerm". Choose the desired xenogerm from the list that appears.

Once the bill is ready, a doctor will need to perform the implantation surgery. The operation requires 4 medicine of [[Herbal medicine|herbal quality]] or higher, and requires {{Ticks|2000}} of work.

After implantation is complete, the patient will enter a "xenogermination coma". This lasts about 2 days, depending on the quality of the surgery, and will cause a total inability to move. See the section below on more details on how this time is calculated.

In addition, the patient's genes will need between {{Ticks/gametime/years|6000000}} and {{Ticks/gametime/years|8400000}} to regrow. Extracting their genes with a [[gene extractor]] during this time will kill them. However, it is safe to implant another xenogerm during this time.

==== Breakdown of Xenogermination Time ====
There are a number of factors and specific effects on xenogermination time, which the list below will break down.

<div><li style="display: inline-table;">
Click to <div class="mw-collapsible mw-collapsed">
<div class="mw-collapsible-content">
* The time spent in a xenogermination coma depends on the quality of the surgery, clamped within 0% and 100%
** At 0% quality, the duration will be 3 days
** At 100% quality, the duration will be 1 day
** This means that the duration in days can be found with the equation: 3 - (Quality × 2)
* The quality of the surgery depends on the following factors:
** The surgery has a base quality of 100%
** Multiplied by the [[medical surgery success chance]] of the surgeon.
** Multiplied by the [[surgery success chance factor]] of the patient's bed.
** Doubled if the doctor has an [[inspired surgery]]
** Multiplied by the [[Medical Potency]] of the medicine used, based on a <abbr title="piecewise linear">simple</abbr> curve.
*** x0.7 at 0% potency, x1 at 100% potency, x1.3 at 200% potency
*** 88% for [[herbal medicine]] (60% potency)
*** 100% for [[Medicine|industrial medicine]] (100% potency)
*** 118% for [[glitterworld medicine]] (160% potency)
** Multiplied based on the overall complexity of the xenogerm
*** Factor starts at 100% at 0 complexity
*** -2% for each point of complexity
*** Minimum factor of 60%, at 20 points of complexity
** Multiplied based on patient's age
*** 100% up to age 20
*** -1.25% for each year after 20
*** Minimum of 50% at the age of 60
</div></div></li></div>

== Avoiding Metabolic Surprises ==

When applying a xenogerm to a xenotype with [[germline gene]]s, the resulting Metabolic Efficiency (ME) may be different from the one reported by the Gene assembler. This is due to overridden genes not being accounted for. For instance, adding a xenogerm of [[great animals]] to a Waster results on a ME of {{--|5}}, rather than the {{--|3}} reported by the Gene assembler, due to the overridden [[awful animals]] gene that all baseline Waster have.

To calculate the actual ME when applied to a Xenotype, you can follow this procedure:
* Note the xenotype's baseline ME.
* Make note of all the overridden genes' ME and sum it together.
* Take the Gene assembler's reported ME, add the xenotype's baseline ME, and subtract the sum of overridden genes' ME

<div class="mw-customtoggle-Example_ME" style="display:inline-block;background:rgba(128,128,128,0.5);color:white;padding:10px;border-radius:5px;outline:none;user-select:none">Example</div>

<div id="mw-customcollapsible-Example_ME" class="mw-collapsible mw-collapsed">

Applying [[Very fast runner]] and [[Weak melee damage]] to a Neanderthal:
* Assembler's reported ME : '''assembler_ME''' = -4
* Neanderthal's baseline ME : '''xenotype_ME''' = +2
* Neanderthal's baseline Slow Runner = +3
* Neanderthal's baseline Strong Melee Damage = -2
* Total ME of overridden genes : '''overridden_ME''' = +3 + -2 = +1
* Final ME = assembler_ME + xenotype_ME - overridden_ME = -4 + 2 - (+1) = -3

Therefore, we know that applying a Xenogerm of Very Fast Runner and Weak Melee Damage to a Neanderthal will induce a ME of {{--|3}} in the pawn.
</div>

In case the actual ME is less than {{--|5}}, you will be unable to apply the Xenogerm to the pawn.

== Analysis ==
The use of a xenogerm depends on what genes are contained within it. For example, it can used to counter unfavorable genes from the germline such as [[weak melee damage]] on a [[Impid]] with a passion in melee, or as a medical tool in the event of life-threatening illness by implanting [[strong immunity]]. When making a xenotype with hybrids or children ideally it should be applied within the infancy stage as the pawn cannot work or learn regardless, and the coma will be the least impactful.

For purifying genepacks into just 1 or 2 genes, a xenogerm can be applied to a baseliner prisoner or any other undesirable pawn to kill them later with a [[Gene extractor]] and attempt to acquire a genepack with the desirable genes.

Xenogerms also satisfy [[body modder]]s and [[transhumanist]]s{{IdeologyIcon}} and conversely disgust [[body purist]]s and [[Flesh_purity|flesh purists]]{{IdeologyIcon}}. Pawns with a xenotype preferred by their ideoligion will also refuse the implantation of new genes. Purely cosmetic genes can be inserted into a Body Modder for a free {{+|4}} mood with no impact compared to other options like [[denture]]s.

The only way to completely remove xenogenes are to kill the pawn by putting them through a [[Gene extractor]] while regrowing their genes and then [[Death#Resurrection|resurrecting]] them.

Xenogermination coma can technically be healed by a healer mech serum, but the item is too rare for this to be practical. However, if a colonist with the mostly-equivalent [[unnatural healing]]{{AnomalyIcon}} ability is available (and tentacle limbs are not undesirable), there is little reason not to use it to instantly wake an important pawn.

== Version history ==
* [[Biotech DLC]] Release - Added
* [[Version/1.4.3534|1.4.3534]] - Fix: Pawns will continue to create a xenogerm until they pass out.
* [[Version/1.4.3613|1.4.3613]] - Fix: Xenogerms with different genes and name stack in trade screen.
* [[Version/1.5.4062|1.5.4062]] - Fix: Error when creating xenogerm in certain circumstances.

{{Nav|body parts|wide}}
{{Biotech navbox}}

[[Category:Medical Item]] [[Category:Body Part]] [[Category:Implant]]

Militor

2026-06-22T21:19:57Z

Aelanna: Cleaned up addition, lore doesn't really need to be mentioned here.

{{Biotech}}
{{infobox main|none|
| name = Militor
| image = MilitorAncient east.png
| description = A small combat mechanoid armed with a low-powered mini-shotgun. Roughly four feet tall, militors lack the power, range, and toughness of more senior combat mechs. However, it is cheap to gestate and maintain, and so is often used as a rear guard or swarm attacker.<br>In war, mech armies are known to send militors into urban ruins to hunt down survivors after breaking the human defenses. For this reason, they are considered by some to be the most cruel of all mechanoid patterns.
| type = Mechanoid
| combatPower = 45
| movespeed = 3.80
| flammability = 0
| marketvalue = 800
| armorblunt = 10
| armorsharp = 20
| armorheat = 200
| min comfortable temperature = -100
| max comfortable temperature = 250
| psychic sensitivity = 0.5
| toxic resistance = 1
| toxic environment resistance = 1
| bandwidth cost = 1
| bodysize = 0.7
| healthscale = 1
| lifespan = 2500
| attack1dmg = 6
| attack1type = Blunt
| attack1cool = 2.6
| attack1part = Head
| page verified for version = 1.4.3525
| weaponTags = MechanoidGunShortRange

| research = Basic mechtech
| production facility 1 = Mech gestator
| gestation cycles = 1
| resource 1 = Steel
| resource 1 amount = 50
| resource 2 = Basic subcore
| resource 2 amount = 1
}}
A '''militor''' is a [[mechanoids|mechanoid]] added by the [[Biotech DLC]].

== Acquisition ==
{{Acquisition}}

Dead, friendly {{lc:{{PAGENAME}}}}s can also be resurrected at the {{lc:{{P|Production Facility 1}}}} using the "''Resurrect light mechanoid''" bill. This requires the corpse of the friendly {{PAGENAME}}, {{Icon Small|Steel||25}} [[steel]], and 1 [[gestation cycle]] taking {{ticks|1800}} to initiate.

== Summary ==
{{Mechanoid Summary}}

Dead militors may be shredded at the [[machining table]] or [[crafting spot]] for {{Icon Small|Steel||10}} [[steel]]. However, these values are affected by [[Mechanoid Shredding Efficiency|mechanoid shredding efficiency]], as well as missing parts on the militor.

Enemy mechs do not require power, though will spawn dormant outside of a [[raid]].

=== As an enemy ===
Militors can spawn in mechanioid raids and those raids called with many of the mechanoid commanders. Due to their low combat power, they are used to defend early [[mechanitor]] corpses,. They can also spawn anywhere hostile mechanoids spawn, such as [[Crashed Ship Part#Psychic Ship|psychic ships]]. They can even form large, militor-only [[raid]]s.

=== As an ally ===
Mechs under player control require power: militors use 10% of their power per day while active. If set to dormant self-charging, they instead recharge for 1% power / day, without pollution. They recharge in a [[mech recharger]] (200W), for 50% power/day, creating 5 [[wastepack]]s whenever the recharger's waste is filled up.

=== Combat ===
Militors are always equipped with a [[mini-shotgun]], which they do not drop upon death. See the [[mini-shotgun]] page for further information.

Militors have a [[shooting accuracy]] of 96%, equivalent to a pawn with a [[Shooting]] skill of 8. They have a [[melee hit chance]] of 62%, equivalent to a pawn with a [[Melee]] skill of 4.

== Analysis ==
=== As an enemy ===
A group of lone militors can easily be kited, as they are slightly slower than a base human. As soon as a militor comes remotely close to you, start running away, then use your range to your advantage. They can be fought with neolithic weapons like [[recurve bow]]s, let alone any form of long-range firearm.

Late game militor-only raids can contain hundreds of mechs to fight. Unlike most mechanoid targets, these make ideal targets for [[doomsday rocket launcher]]s as their health scale is low enough that the primary explosion will kill dozens, despite their immunity to the secondary explosions.

They are more threatening when combined with other mechanoids, like [[pikemen]] and [[lancer]]s. The militor acts as a closer threat, making it harder to engage the stronger mechanoids. Due to their short range, militors tend to cluster together. So [[EMP grenade]]s and [[EMP launcher]]s work well, as with other mechanoids. The same kiting strategy can work in the first [[Diabolus]] fight, but becomes more difficult as stronger mechs come into play.

=== As an ally ===
Militors are both cheap to build and repair, making them quite good at luring and taking attacks. For example, they can stand in the face of an [[impids|impid]]'s fire breath without any fear. The high stopping power of their mini-shotgun makes a group of militors helpful as support units, even when you have stronger mechanoids. They are a [[mechanitor]]'s only combat option before [[Standard mechtech]], and remain good at their role for colonies of any size.

Militors have a very short range and move slower than a baseline human, which must be kept in mind in combat. If using them for their firepower, create hallways, corners, and [[killbox]]es so that ranged enemies must approach them.

Militors when set to perform work will automatically find and attack threats within the home area and their allowed area, which can include insectoid [[hive]]s. This can save you some micromanaging but may also draw attention from neutral threats.

== Health ==
=== Body parts ===
{{Animal Health Table|Mech_Light}}
=== Armor ===
{| class="wikitable"
! Armor
|-
| {{Apparel Protection Chart
| set1name= {{P|Name}} (Sharp) | set1armor1={{P|Armor - Sharp}}
| set2name= {{P|Name}} (Blunt) | set2armor1={{P|Armor - Blunt}}
| set3name= {{P|Name}} (Heat) | set3armor1={{P|Armor - Heat}}
| color= grey, blue, red
}}
|}
{{Pawn Attack Table|weapon=Mini-shotgun}}

== Trivia ==
The word "militor" roughly translated from Latin means "I am a soldier" or "war is waged by me".

== Gallery ==
<gallery>
Militor east.png| Age 0-99 Militor facing east
Militor north.png| Age 0-99 Militor facing north
Militor south.png| Age 0-99 Militor facing south
</gallery><gallery>
MilitorAncient east.png| Age 100+ Militor facing east
MilitorAncient north.png| Age 100+ Militor facing north
MilitorAncient south.png| Age 100+ Militor facing south
</gallery>

== Version history ==
* [[Biotech DLC]] Release - Added.
* [[Version/1.4.3531|1.4.3531]] - Slightly reduce damage and increase ranged cooldown for militor's mini-shotgun.
* ? (Prior to 6/Feb/2023, possibly 1.4.3531) - Militor [[raid points|combat power]] reduced, from 75 to 45.

{{nav|mechanoid|wide}}
[[Category:Mechanoids]]

Sanguophages

2026-06-19T14:12:04Z

Aelanna: Spelling.

{{Biotech}}
{{Spoiler}}
{{Infobox main|xenotype
| name = Sanguophage
| image = Sanguophage.png
| description = Sanguophages are a type of archotech-enhanced xenohuman. Powered by archites, their abilities go far beyond normal genetic enhancements. They are mentally adept and preternaturally beautiful. In combat, they can launch deadly spines and heal injured friends. They don't age or die naturally and never suffer from disease or poison. A sanguophage can make a new sanguophage by reimplanting their own xenogerm into a person.<br/>Sanguophages must regularly consume hemogen derived from human blood, and they must periodically deathrest for long periods. They're easily destroyed by fire, and slowed down by UV light.<br/>The first sanguophage appeared thousands of years ago when the lord-explorer Varan-Dur sought to control a hyperintelligent archotech and found himself transformed by it instead. Every sanguophage is descended from him. Since then, sanguophages have often been hunted because of their destabilizing power and their need for blood. Since they can pass for baseliners, many live in hiding among typical humans.<br/>Their numbers are unknown. Some think they are legends or rare irrelevancies. Some believe sanguophages secretly direct entire human civilizations. The stories speak of eternal lords ruling billions from slate-black space stations, or directing blood sacrifices at conferences in the underlayers of the deepest urbworlds.
| short description = Sanguophages are ageless, deathless super-humans powered by archotech-created archites in the bloodstream. They are beautiful and extremely intelligent. They can heal any injury, and never suffer from disease or poison. In combat, they can launch deadly spines and heal injured friends. The price is that sanguophages must consume hemogen derived from human blood to survive, and they must periodically deathrest for long periods. They're easily destroyed by fire, and slowed down by UV light.

| type = Human
| type2 = Xenotypes

| can generate as combatant = true
| generate with xenogerm replicating hediff chance = 0.5
| xenogerm replicating duration left days range = 0.1~140
| combat power factor = 2.5
| display priority = -1000
| factionless generation weight = 0
| double xenotype chances = (Pigskin, 0.02), (Impid, 0.02), (Yttakin, 0.02), (Neanderthal, 0.02), (Waster, 0.02), (Dirtmole, 0.02)
| genes = Hemogenic, Hemogen drain, Bloodfeeder, Coagulate, Gene implanter, Longjump legs, Ageless, Deathless, Deathrest, Piercing spine, Psy-sensitive, Low sleep, Attractive, Fast runner, Strong melee damage, Dark vision, TotalHealing, Perfect immunity, Non-senescent, Tox immunity, Superfast wound healing, Strong Melee, Strong Social, Strong Intellectual, Mild UV sensitivity, Tinderskin, Pyrophobia, Archite metabolism, Aggressive, Robust

| defName = Sanguophage
| label = sanguophage
| iconPath = UI/Icons/Xenotypes/Sanguophage
| soundDefOnImplant = PawnBecameSanguophage
}}
'''Sanguophages''' are an exceptionally rare and powerful [[Xenotypes|xenotype]] with a deathly intolerance to heat and sunlight. They use their superhuman powers to satiate their genetic need for [[hemogen|human blood]].

== Lore ==
{{Quote|"The first sanguophage appeared thousands of years ago when the lord-explorer Varan-Dur sought to control a hyperintelligent archotech and found himself transformed by it instead. Every sanguophage is descended from him. Since then, sanguophages have often been hunted because of their destabilizing power and their need for blood. Since they can pass for baseliners, many live in hiding among typical humans.<br/>
Their numbers are unknown. Some think they are legends or rare irrelevancies. Some believe sanguophages secretly direct entire human civilizations. The stories speak of eternal lords ruling billions from slate-black space stations, or directing blood sacrifices at conferences in the underlayers of the deepest urbworlds."|Biotech preview #4: Xenotypes, world factions, and the dark blood-drinkers}}

== Summary ==
Sanguophages are a mysterious but powerful group of xenohumans. They have no distinguishing looks from other xenohumans, so they blend in at first glance. Once selected, their differences are immediately apparent, from their hemogen and deathrest trackers at the bottom of the screen, to their unique abilities and immense genetic differences.

=== Genes ===
Sanguophages have a gene complexity of 57[[File:Complexity.png|20px|Complexity|link=Complexity]] [[complexity]] and an equivalent xenogerm contains 8[[File:Archite_capsule_required.png|20px|Archite capsule|link=Archite capsule]] [[Archite capsule|archite capsules]]. With a '''0'''[[File:Metabolism.png|20px|Metabolic efficiency|link=Metabolic efficiency]] [[metabolic efficiency]], they have a hunger rate of '''×100%'''. Note however that sanguophage genes can disable a pawn's native [[germline gene]]s (e.g. ''Fast Runner'' will negate a [[neanderthal]]'s ''Slow Runner''), which can change their metabolism.

All sanguophages have these xenogenes:

'''Archite:'''
{| class="wikitable" style="text-align: center;"
|- align="center"
| width=100px height=50px | {{Stacked image|GeneBackground ArchiteGene.png|Gene XenogermReimplanter.png|64|Gene implanter|Gene implanter}}
| width=100px height=50px | {{Stacked image|GeneBackground ArchiteGene.png|Gene Ageless.png|64|Ageless|Ageless}}
| width=100px height=50px | {{Stacked image|GeneBackground ArchiteGene.png|Gene ArchiteMetabolism.png|64|Archite metabolism|Archite metabolism}}
| width=100px height=50px | {{Stacked image|GeneBackground ArchiteGene.png|Gene Deathless.png|64|Deathless|Deathless}}
| width=100px height=50px | {{Stacked image|GeneBackground ArchiteGene.png|Gene NonSenescent.png|64|Non-senescent|Non-senescent}}
| width=100px height=50px | {{Stacked image|GeneBackground ArchiteGene.png|Gene PerfectImmunity.png|64|Perfect immunity|Perfect immunity}}
| width=100px height=50px | {{Stacked image|GeneBackground ArchiteGene.png|Gene TotalHealing.png|64| Scarless|Scarless}}
|-
| <small>[[Gene implanter]]</small>
| <small>[[Ageless]]</small>
| <small>[[Archite metabolism]]</small>
| <small>[[Deathless]]</small>
| <small>[[Non-senescent]]</small>
| <small>[[Perfect immunity]]</small>
| <small>[[Scarless]]</small>
|}

'''Hemogenic:'''
{| class="wikitable" style="text-align: center;"
|- align="center"
| width=100px height=50px | {{Stacked image|GeneBackground Xenogene.png|Gene Bloodfeeder.png|64|Bloodfeeder|Bloodfeeder}}
| width=100px height=50px | {{Stacked image|GeneBackground Xenogene.png|Gene Coagulate.png|64|Coagulate|Coagulate}}
| width=100px height=50px | {{Stacked image|GeneBackground Xenogene.png|Gene LongJumpLegs.png|64|Longjump legs|Longjump legs}}
| width=100px height=50px | {{Stacked image|GeneBackground Xenogene.png|Gene PiercingSpine.png|64|Piercing spine|Piercing spine}}
| width=100px height=50px | {{Stacked image|GeneBackground Xenogene.png|Gene Hemogenic.png|64|Hemogenic|Hemogenic}}
| width=100px height=50px | {{Stacked image|GeneBackground Xenogene.png|Gene HemogenDrain.png|64|Hemogen drain|Hemogen drain}}
| width=100px height=50px | {{Stacked image|GeneBackground Xenogene.png|Gene Deathrest.png|64|Deathrest|Deathrest (gene)}}
|-
| <small>[[Bloodfeeder]]</small>
| <small>[[Coagulate]]</small>
| <small>[[Longjump legs]]</small>
| <small>[[Piercing spine]]</small>
| <small>[[Hemogenic]]</small>
| <small>[[Hemogen drain]]</small>
| <small>[[Deathrest (gene)|Deathrest]]</small>
|}

'''Assorted:'''
{| class="wikitable" style="text-align: center;"
|- align="center"
| width=100px height=50px | {{Stacked image|GeneBackground Xenogene.png|Gene WoundHealingRateSuperfast.png|64|Superfast wound healing|Superfast wound healing}}
| width=100px height=50px | {{Stacked image|GeneBackground Xenogene.png|Gene EnhancedPsychicAbility.png|64|Psy-sensitive|Psy-sensitive}}
| width=100px height=50px | {{Stacked image|GeneBackground Xenogene.png|Gene QuickMovespeed.png|64|Fast runner|Fast runner}}
| width=100px height=50px | {{Stacked image|GeneBackground Xenogene.png|Gene TotalToxicityResistance.png|64|Tox immunity|Tox immunity}}
| width=100px height=50px | {{Stacked image|GeneBackground Xenogene.png|Gene MildUVSensitivity.png|64|Mild UV sensitivity|Mild UV sensitivity}}
| width=100px height=50px | {{Stacked image|GeneBackground Xenogene.png|Gene FireWeakness.png|64|Tinderskin|Tinderskin}}
| width=100px height=50px | {{Stacked image|GeneBackground Xenogene.png|Gene FireTerror.png|64|Pyrophobia|Pyrophobia}}
|-
| <small>[[Superfast wound healing]]</small>
| <small>[[Psy-sensitive]]</small>
| <small>[[Fast runner]]</small>
| <small>[[Tox immunity]]</small>
| <small>[[Mild UV sensitivity]]</small>
| <small>[[Tinderskin]]</small>
| <small>[[Pyrophobia]]</small>
|- align="center"
| width=100px height=50px | {{Stacked image|GeneBackground Xenogene.png|Gene Aggressive.png|64|Aggressive|Aggressive}}
| width=100px height=50px | {{Stacked image|GeneBackground Xenogene.png|Gene StrongMeleeDamage.png|64|Strong melee damage|Strong melee damage}}
| width=100px height=50px | {{Stacked image|GeneBackground Xenogene.png|Gene QuickSleeper.png|64|Low sleep|Low sleep}}
| width=100px height=50px | {{Stacked image|GeneBackground Xenogene.png|Gene Tough.png|64|Robust|Robust}}
| width=100px height=50px | {{Stacked image|GeneBackground Xenogene.png|Gene Pretty.png|64|Attractive|Attractive}}
| width=100px height=50px | {{Stacked image|GeneBackground Xenogene.png|Gene Darkvision.png|64|Dark vision|Dark vision}}
|-
| <small>[[Aggressive]]</small>
| <small>[[Strong melee damage]]</small>
| <small>[[Low sleep]]</small>
| <small>[[Robust]]</small>
| <small>[[Attractive]]</small>
| <small>[[Dark vision]]</small>
|}

'''Skills:'''
{| class="wikitable" style="text-align: center;"
|- align="center"
| width=100px height=50px | {{Stacked image|GeneBackground Xenogene.png|Gene StrongMelee.png|64|Strong melee|Strong melee}}
| width=100px height=50px | {{Stacked image|GeneBackground Xenogene.png|Gene StrongSocial.png|64|Strong social|Strong social}}
| width=100px height=50px | {{Stacked image|GeneBackground Xenogene.png|Gene StrongIntellectual.png|64|Strong intellectual|Strong intellectual}}
|-
| <small>[[Strong melee]]</small>
| <small>[[Strong social]]</small>
| <small>[[Strong intellectual]]</small>
|}

== Obtaining ==
{{stub|section=1|reason=More detail on the quests}}
Sanguophages can be found in several ways.
* [[Scenario_system#Default_Scenarios|Sanguophage scenario]]: You start the game with a Sanguophage.
* Recruitment: You capture and [[recruit]] a Sanguophage, or one [[Events#Wanderer_joins|joins as a wanderer]].{{Check Tag|Verify|108 dev moded wanderers didn't generwte a sanguo. verify it can spawn this way}}
* [[Gene implanter|Gene implant]]: You can force Sanguophages to use their gene implant ability on one of your pawns if they are captured or downed. Select the desired pawn to gain these abilities, and then right-click on the sanguophage and choose the "Absorb xenogerm" option. If the sanguophage's genes are currently regrowing, this will kill them.
* [[Quests#Bloodthirsty Parley|Quest: Bloodthirsty Parley]]: You allow 2 or more Sanguophages hold a meeting at your colony. They will start the ceremony by placing a [[blood torch]], which gives {{+|2}} mood buff to all sanguophages in its radius, and a red mist, with red eyes appearing in it, will appear for a few hours. The torch will remain once the quest is complete. One of the quest rewards will allow you to choose a pawn to be implanted with Sanguophage genes. There's also a small chance that some of those sanguophages will give you a join offer, similar to refugees.
* [[Quests#Sanguophage Transport|Quest: Sanguophage Transport]]: You get word that a sanguophage and his thralls are about to crash, and you can signal them to land at your colony (or nearby). You are advised that if you capture the sanguophage you can force them to implant a xenogerm in one of your colonists.
* [[Empire|Stellarchs]]{{RoyaltyIcon}} have a 25% chance of generating as a Sanguophage, separate from the [[xenotype]] set used by the empire itself. This means that there is the potential to order the high stellarch to implant their xenogerm into a colonist during the Royalty endgame quest.
**Knights/Dames, Praetors, Barons/Baronesses and Count/Countesses also have a 5% chance to generate as a Sanguophage, and Duke/Duchesses and Consuls have a 15% chance.

== Analysis ==
Becoming a sanguophage has a variety of pros and cons, that are generally worth the implantation.

Access to Low Sleep means that, even when considering deathrest, a sanguophage will have more hours of work every day. The archite genes provide eternal youth and health, and cure scars akin to [[luciferium]]. Fast walker and Robust are useful to just about any colonist. Finally, their hemogen abilities are all useful in their own way.

Because of their Non-Senecent and Scarless genes they also end up being the most ideal target for [[Psychic ritual]]s{{AnomalyIcon}} with very little penalty from chronophagy{{Check Tag|Philophagy?|apart from the obvious skill loss its not stated if that ritual causes brain damage on its page}} other then a {{--|18}} Psychic Ritual Target thought {{Check Tag|Thought Template}} and dark psychic shock. Psychophagy can also be used if the sanguophage's psychic sensitivity is unwanted albeit preventing any further use for future rituals.

However, being a blood drinker does come with costs - a need for [[hemogen]] and a need for [[deathrest]]. While they are not deal-breakers, you should consider them whenever playing with a sanguophage. These are detailed below.

----
=== Sanguophage needs ===
==== Hemogen ====
Sanguophages can store 100 hemogen, which can be increased by deathresting with attached [[hemopump]]s. A sanguophage consumes 10 of their stored hemogen per day, equivalent to a bloodfeed every 2 days. Hemogen reaching 0 is not fatal, but will inflict a gradually increasing penalty that eventually reaches {{Bad|x50%}} [[Consciousness]], {{++|15%}} [[pain]] and a {{--|20}} [[mood]]let. Hemogen is also required, and consumed by, the Longjump, Piercing spine, and Coagulate abilities.

As a rough measure, each regular human can meet {{#expr: (20/10) /(45/33.3)}} sanguophages' needs for blood indefinitely, assuming no hemogenic abilities are used. Extracting [[hemogen pack]]s and consuming them is exactly as efficient as blood feeding in terms of hemogen per prisoner per day. Packs require storage space and additional pawn work, but do not inflict a painful bite or a {{--|5}} moodlet, and extracting them slowly trains the [[medical]] skill. Note that the moodlet is avoided when feeding on [[masochist]]s or those with the [[Ideoligion#Bloodfeeders|Bloodfeeders: Revered]] precept.{{IdeologyIcon}}

[[Prisoner]]s are preferred as hemogen sources over colonists because the [[blood loss]] will reduce the ability to work for a short time. The mood impact of bloodfeeding is also less important on prisoners. You can give prisoners the [[Dead calm]] gene to make sure they don't escape while still remaining able to feed themselves from [[nutrient paste dispenser]]s or meals left in their prison. Alternatively, the [[Peg leg#Analysis|leg treatment]] will also prevent escapes and reduce their [[Market Value]], but they will need to be manually fed by colonists or [[paramedic]] mechanoids. You can also give them negative genes like [[Very unattractive]] to reduce food upkeep.

==== Deathrest ====
{{Main|Deathrest}}
Sanguophages need to [[deathrest]] once every ~30 days. This will last from 4 days (regular [[bed]]) to 2.5 days ([[deathrest casket]] + 2 [[deathrest accelerator]]s). During this time, the pawn will have their needs frozen. Lacking deathrest is like lacking hemogen - it isn't fatal, but comes with major Consciousness and mood penalties.

The main cost of deathrest is that your sanguophage might be stuck sleeping whenever a [[raid]] arrives. [[Cassandra Classic]] and [[Phoebe Chillax]] both have defined cooldowns between sets of raids, but [[Randy Random]] won't give you that mercy. They ''can'' wake up at will, but this results in the [[Deathrest#Summary|Interrupted deathrest]] hediff, reducing their stats for 5 days.

Note that deathrest comes with some benefit. You can connect with [[deathrest building]]s like the [[glucosoid pump]] to improve post-deathrest condition. [[Psycast]]ers{{RoyaltyIcon}} will appreciate using [[psychofluid pump]]s to improve their psychic abilities. However, deathrest building capacity is limited. It must be increased one at a time by the expensive and somewhat rare [[deathrest capacity serum]]. Further, unlike a [[Cryptosleep casket]], deathrest does not suspend [[Addiction]], and can be used to mitigate withdrawal symptoms.

==== Miscellaneous ====
Sanguophages have Pyrophobia, which can cause Fleeing Fire [[mental break]] if near [[fire]]. This makes it more difficult when fighting fire-based enemies like the [[tesseron]] and [[diabolus]]. In addition, they are damaged more by fire. A [[firefoam pop pack]] can be handy. However, Sanguophages are not completely unable to deal with fire: when drafted, they will still beat out flames adjacent to the tile they are standing on. However, given their vulnerability to fire and the risk of the mental break leading them into danger, this should only be attempted in emergencies. [[Mind-numb serum]]s{{AnomalyIcon}} prevent pyrophobia breaks and have long durations - while they remain weak to fire damage itself, keeping them under control is by far more important.

Sanguophages also have minor UV sensitivity, giving {{--|6}} [[mood]] and {{Bad|x90%}} move speed during the sunlight. Ultimately, this is a minor penalty, but one worth noting. A sanguophage is slightly slower than a base human in the day, but faster at night.

----

=== Choosing a host ===
{{Stub|section=1|reason=Discuss the germline gene xenotypes and how they combine with sanguo, ideally with list of final genes/Complexity/metabolism of each vanilla germline xenotype when combined with sanguophage so that players can see what a result will be.}}
Because each xenogerm implantation has a cooldown of 2 years, not all your colonists can become a sanguophage right away. Captured Sanguophages cannot be forced to implant the sanguophage gene into babies despite the option being available. There are 2 types of colonist that deserve special mention:

* Colonists with brain damage, or colonists with [[Ailments#Chronic|chronic conditions]] like [[frail]]. These conditions are cured by the Scarless gene, and would otherwise require [[luciferium]], [[healer mech serum]], [[biosculpter pod]],{{IdeologyIcon}} the [[Unnatural healing]] ability of some [[Creepjoiner]]s{{AnomalyIcon}}, or [[Chronophagy]]{{AnomalyIcon}} to treat. In a similar vein, older colonists are vulnerable to disease and said chronic conditions. Being a sanguophage renders full immunity to disease and aging, and will retroactively cure any existing conditions over time.

* Colonists who would appreciate access to the various genes. Melee fighters will gain access to many good vampire genes, like Strong melee (skill), Strong melee damage, Robust, and Longjump, as well as all the Archite genes. Any colonist will appreciate the powers of Deathless and Scarless.

:Their pyrophobia will negate the [[Pyromaniac]] trait. Pawns with [[Transhumanist]] ideologies{{IdeologyIcon}} can also go without mandatory age reversals.

Remember that '''Sanguophage implantation replaces ''all'' xenogenes'''. Your [[genie]]s, [[hussar]]s, and [[highmates]] will lose all of their respective genes. Any [[xenogerm]]s you've implanted will be replaced completely. In addition, '''implanting any xenogerm will erase all Sanguophage genes'''. Don't give them Great Melee thinking it'll just improve your sanguophage's melee skill, it'll also remove their archite genes and need for blood.

== Trivia ==
* The [[#Lore|Sanguophage lore]] can be partially referenced in-game in the narrative of [[Bloodfeeder]] [[Ideoligion]]s{{IdeologyIcon}} with an [[Ideoligion#Structure|ideological structure]]. They repeat the story of an adventurer attempting to take control of an archotech, but the name "Varan-Dur" appears to have been lost to time.
* As a xenogerm xenotype, sanguophages can rarely create [[Neanderthals]], [[Impids]] and [[Yttakin]] inside [[Empire]]{{RoyaltyIcon}} nobility.
** Additionally in other situations, sanguophages can generate with the same endogenic xenotypes as above, or additionally as [[Wasters]] and [[Pigskins]]

== Version history ==
* [[Version/1.4.3531|1.4.3531]] - Fix: AI sanguophages can use longjump without any remaining hemogen.
* [[Version/1.4.3534|1.4.3534]] - Fix: Error on drafting pawn with hemogenic ability gene with no hemogen gene.

{{Biotech navbox}}
[[Category:Xenotypes]]
{{#set:Image = [[File:Sanguophage.png]]}}

MediaWiki:Sidebar

2026-05-28T18:49:45Z

Aelanna: Removing link to official forums per Ludeon Community request

Modding Tutorials/About.xml

2026-05-27T14:16:37Z

Aelanna: Adding RimSort to mentions of Rimpy

{{DISPLAYTITLE:About.xml}}
{{BackToTutorials}}

<code>About.xml</code> is a required file that identifies your mod to RimWorld. This file defines the internal and viewer-facing names of your mod, contains a short description of your mod that is shown in the in-game mod manager, and defines compatibility issue such as other mods that your mod might be dependent on and load helpers that mod list auto-sorters can use to determine when to load your mod.

== Setup ==

Your <code>About.xml</code> file should be placed directly inside your <code>About</code> folder. Note that both the folder and file name are case-sensitive and must be spelled exactly this way; please see [[Modding_Tutorials/Mod_folder_structure|the mod folder structure guide]] for more information.

<source>
Mods
└ MyModFolder
└ About
└ About.xml
</source>

The contents of <code>About.xml</code> is a standard XML file with <code>ModMetaData</code> as the root tag:

<source lang="xml">
<?xml version="1.0" encoding="utf-8"?>
<ModMetaData>



</ModMetaData>
</source>

== Required Tags ==

The following tags are all required for a functioning mod. Please read the tag descriptions carefully:

<div class="TutorialTableWrapper">
{| class="TutorialCodeTable"
! XML !! Description
|-
| <source lang="xml">
<packageId>AuthorName.ModName</packageId>
</source>
| class="TutorialCodeTable-description" |
The internal identifier for your mod, used to identify your mod as a dependency, load order helper, or with [[Modding_Tutorials/MayRequire|MayRequire]] attributes. <code>packageId</code>s should be alphanumeric with at least one period separating two strings. You cannot use any other special characters and you cannot end with a period. It is usually recommended that you use <code>YourName.YourModName</code>, <code>YourProjectName.YourModName</code>, <code>YourName.YourSeriesName.YourModName</code>, or something similar.

'''<code>packageId</code> must be globally unique across all mods.''' If RimWorld encounters more than one mod with the same <code>packageId</code>, ''even if they are not in your current mod list'', then an error will be thrown and only the first mod will be usable. The only time that using the same <code>packageId</code> is recommended is if you are forking or continuing a mod and want it to act as a drop-in replacement. In such cases, players must unsubscribe from the original mod to be able to use yours.

Note: <code>packageId</code> is case-insensitive as RimWorld will internally convert all IDs to lowercase; capitalization is done for readability, but two IDs that are identical other than case will resolve as identical.
|-
| <source lang="xml">
<name>My Mod Name</name>
</source>
| class="TutorialCodeTable-description" |
The title of your mod. While the name of your mod does ''not'' need to be globally unique and most references to mods are now using <code>packageId</code>, [[Modding_Tutorials/PatchOperations#PatchOperationFindMod|PatchOperationFindMod]] still uses mod names and thus you should avoid changing the name of your mod unless absolutely necessary.
|-
| <source lang="xml">
<author>Author Name, Another Author Name, A Third Author Name</author>
</source>
<div style="text-align: center; font-style: italic;">or</div>
<source lang="xml">
<authors>
<li>Author Name</li>
<li>Another Author Name</li>
<li>A Third Author Name</li>
</authors>
</source>
| class="TutorialCodeTable-description" |
The author of this mod, usually yourself. More than one author can be specified by separating names with commas or by using list nodes.
|-
| <source lang="xml">
<description>This is the description of this mod.</description>
</source>
| class="TutorialCodeTable-description" |
The plain-text description of your mod. This is used as both the content description of your mod in mod managers (including the vanilla mod manager) as well as the initial description of your mod if uploaded to Steam Workshop. In the latter case, you can change your Workshop item description independent of the mod itself, thus it is generally recommended that you keep the description of your mod in About.xml relatively short.
|-
| <source lang="xml">
<supportedVersions>
<li>1.6</li>
</supportedVersions>
</source>
| class="TutorialCodeTable-description" |
The RimWorld versions that your mod supports. A warning will be given to the player if attempting to load the mod under a version you have not explicitly specified support for, but this does not prevent players from loading the mod if they so choose.

It is strongly recommended that you only specify support for versions that you have explicitly tested compatibility for; RimWorld has changed dramatically between versions in the past and even XML-only mods may not be guaranteed to work without version-specific changes.
|-
|}
</div>

== Optional Tags ==

The following tags are optional and should only be used if you need them:

<div class="TutorialTableWrapper">
{| class="TutorialCodeTable"
! XML !! Description
|-
| <source lang="xml">
<modVersion>1.0</modVersion>
</source>
<div class="text-align: center; text-style: italic;">or</div>
<source lang="xml">
<modVersion IgnoreIfNoMatchingField="True">1.0</modVersion>
</source>
| class="TutorialCodeTable-description" |
A version string for your own personal version tracking.

'''WARNING:''' This tag was introduced in RimWorld 1.4 and will generate errors in previous versions unless <code>IgnoreIfNoMatchingField</code> is used. If you intend to support older versions of RimWorld with your mod and you want to use this field, you must add this attribute.
|-
| <source lang="xml">
<modIconPath>Path/To/Icon</modIconPath>
</source>
<div class="text-align: center; text-style: italic;">or</div>
<source lang="xml">
<modIconPath IgnoreIfNoMatchingField="True">Path/To/Icon</modIconPath>
</source>
| class="TutorialCodeTable-description" |
Adds an icon for your mod that is shown on loading screens. '''Note that the current unstable version of RimWorld 1.5 also automatically loads About/ModIcon.png, so this field is not necessary to show a mod icon. You only need it if you want to store your mod icon in your Textures folder for some reason.''' Mod icons should be 32x32 PNG files with limited colors; Unity's image compression will make icons very crunchy if you try to add too much detail.

'''WARNING:''' This tag was introduced in RimWorld 1.5 and will generate errors in previous versions unless <code>IgnoreIfNoMatchingField</code> is used. If you intend to support older versions of RimWorld with your mod and you want to use this field, you must add this attribute.
|-
| <source lang="xml">
<url>https://steamcommunity.com/workshop/filedetails/?id=2009463077</url>
</source>
| class="TutorialCodeTable-description" |
A web link that can be displayed with your mod info. This can be any link, though most mods will link to their primary download source, such as a Steam Workshop page, GitHub repository, or Ludeon Forum link.

The example URL is the Steam Workshop page for the latest version of [[Modding_Tutorials/Using_Harmony|Harmony]].
|-
| <source lang="xml">
<descriptionsByVersion>
<v1.4>A different description.</v1.4>
</descriptionsByVersion>
</source>
| class="TutorialCodeTable-description" |
Used to specify a different mod description for specific versions of RimWorld. This is not used by Steam Workshop.
|-
| <source lang="xml">
<modDependencies>
<li>
<packageId>brrainz.harmony</packageId>
<displayName>Harmony</displayName>
<steamWorkshopUrl>steam://url/CommunityFilePage/2009463077</steamWorkshopUrl>
</li>
</modDependencies>
</source>
| class="TutorialCodeTable-description" |
Used to specify dependencies for your mod. Players will be warned if a dependency for your mod is not loaded in their mod list, though players may choose to ignore it.

Note that this is not automatically used by Steam Workshop; if you want players to be notified that they should download a dependency, you must add that via Steam Workshop's "Required Items" feature.
|-
| <source lang="xml">
<modDependencies>
<li>
<packageId>erdelf.HumanoidAlienRaces</packageId>
<displayName>Humanoid Alien Races</displayName>
<steamWorkshopUrl>steam://url/CommunityFilePage/839005762</steamWorkshopUrl>
<alternativePackageIds IgnoreIfNoMatchingField="True">
<li>erdelf.HumanoidAlienRaces.dev</li>
</alternativePackageIds>
</li>
</modDependencies>
</source>
| class="TutorialCodeTable-description" |
'''1.6+''' New in 1.6, you can specify one or more alternative packageIds that can fulfill a dependency requirement. The example here is for the development/unstable version of Humanoid Alien Races, which has a different packageId from the regular mod. As with all other newly introduced tags, if the mod in question supports versions older than 1.6, then the IgnoreIfNoMatchingField attribute should be used to prevent the game from throwing errors when loading into older versions of RimWorld.
|-
| <source lang="xml">
<modDependenciesByVersion>
<v1.4>
<li>
<packageId>brrainz.harmony</packageId>
<displayName>Harmony</displayName>
<steamWorkshopUrl>steam://url/CommunityFilePage/2009463077</steamWorkshopUrl>
</li>
</v1.4>
</modDependenciesByVersion>
</source>
| class="TutorialCodeTable-description" |
Used to specify dependencies for your mod that only apply for a specific version. See above for more details.
|-
| <source lang="xml">
<loadBefore>
<li>CETeam.CombatExtended</li>
</loadBefore>
</source>
| class="TutorialCodeTable-description" |
Used to specify mods that your mod should load before. RimWorld will warn the player if your mod is not in the correct place in their mod list.

Mods specified this way must be referenced by their <code>packageId</code>.
|-
| <source lang="xml">
<loadBeforeByVersion>
<v1.4>
<li>CETeam.CombatExtended</li>
</v1.4>
</loadBeforeByVersion>

</source>
| class="TutorialCodeTable-description" |
Same as <code>loadBefore</code>, but only for the specified RimWorld versions.
|-
| <source lang="xml">
<forceLoadBefore>
<li>CETeam.CombatExtended</li>
</forceLoadBefore>
</source>
| class="TutorialCodeTable-description" |
Same as <code>loadBefore</code>, but instead of just a warning, RimWorld will not allow your mod to be loaded after the specified mods. Note that external mod managers such as RimSort and RimPy may not respect this field.
|-
| <source lang="xml">
<loadAfter>
<li>erdelf.HumanoidAlienRaces</li>
</loadAfter>
</source>
| class="TutorialCodeTable-description" |
Used to specify mods that your mod should load after. RimWorld will warn the player if your mod is not in the correct place in their mod list.

Mods specified this way must be referenced by their <code>packageId</code>.
|-
| <source lang="xml">
<loadAfterByVersion>
<v1.4>
<li>erdelf.HumanoidAlienRaces</li>
</v1.4>
</loadAfterByVersion>

</source>
| class="TutorialCodeTable-description" |
Same as <code>loadAfter</code>, but only for the specified RimWorld versions.
|-
| <source lang="xml">
<forceLoadAfter>
<li>erdelf.HumanoidAlienRaces</li>
</forceLoadAfter>
</source>
| class="TutorialCodeTable-description" |
Same as <code>loadAfter</code>, but instead of just a warning, RimWorld will not allow your mod to be loaded before the specified mods. Note that external mod managers such as RimSort and RimPy may not respect this field.
|-
| <source lang="xml">
<incompatibleWith>
<li>CETeam.CombatExtended</li>
</incompatibleWith>
</source>
| class="TutorialCodeTable-description" |
Used to specify mods that your mod is incompatible with. Players will be warned if the specified mods are loaded at the same time that your mod is.

This should generally only be used to specify mods that are fundamentally incompatible with your mod rather than mods that simply have bugs related to your mod.
|-
| <source lang="xml">
<incompatibleWithByVersion>
<v1.4>
<li>CETeam.CombatExtended</li>
</v1.4>
</incompatibleWithByVersion>
</source>
| class="TutorialCodeTable-description" |
Same as <code>incompatibleWith</code>, but only for the specified versions.
|-
|}
</div>

== Examples ==

As <code>About.xml</code> is required for all mods, you can use existing mods as a reference if you need some examples of working <code>About.xml</code> files. The default installation folder for Steam Workshop mods is under <code>C:\Program Files (x86)\Steam\steamapps\workshop\content\294100</code>

[[Category:Modding]]
[[Category:Modding tutorials]]

Modding Tutorials

2026-05-23T23:35:48Z

Aelanna: Purged deleted tutorials.

{| align=center
| {{Mods_Nav}}
|}
<hr>

This is the hub page for tutorials, guides, and reference materials for creating mods for RimWorld. If you are looking for instructions on how to use RimWorld, please check out the general [[Modding]] hub.

As RimWorld does not have a formal modding API, nearly all of the information here has been gathered and maintained by the modding community.

'''NEW: [[Modding_Tutorials/RimWorld_1.6_Mod_Updates|RimWorld 1.6 Mod Updates]]''' - A work-in-progress list of changes datamined by the modding community in the current unstable version of RimWorld 1.6. '''THERE MAY BE ODYSSEY DLC SPOILERS, YOU HAVE BEEN WARNED.'''

-----

==About RimWorld==
RimWorld is a multi-platform game written on Unity 2022.3.35. However, the Unity Editor is not used for creating mods unless you are creating new shaders or building optional asset bundles.

* [[Modding_Tutorials/Recommended_software|Recommended Software]] - Editors and other useful software for mod development
* [[Modding_Tutorials/Mod_Folder_Structure|Mod Folder Structure]] - Explore the basic folder structure of a mod
** [[Modding_Tutorials/About.xml|About.xml]] - About.xml identifies and describes your mod to RimWorld so that it can be loaded properly

===Game Systems Guides===

* [[Modding_Tutorials/Defs|Defs]] - XML Definitions are used to define and configure content in a way that does not require compiling code
** [[Modding_Tutorials/MayRequire|MayRequire]] - MayRequire and MayRequireAnyOf are used to conditionally load Defs and list entries based on whether a DLC or other mod is loaded
* [[Modding_Tutorials/Localization|Localization]] - Define text strings used for translations and word lists used in name and text generation
* [[Modding_Tutorials/PatchOperations|PatchOperations]] - PatchOperations are used to modify XML Defs without overwriting them completely
* [[Modding_Tutorials/Sounds|Sounds]] - (Needs Rewriting) Adding sound files for mods
* [[Modding_Tutorials/Textures|Textures]] - How to create and add textures to mods
* [[Modding Tutorials/Plant Rendering|Plant Rendering]] - An explanation of how plant textures are rendered
* [[Modding_Tutorials/Research_Projects|Research Projects]] - How to create and use research projects.

===XML Tutorials===

The following are step-by-step tutorials for creating basic content mods.

Basic Tutorials:
* [[Modding_Tutorials/Basic_Melee_Weapon|Basic Melee Weapon]] - How to create a basic melee weapon with a texture mask
* [[Modding_Tutorials/Basic_Ranged_Weapon|Basic Ranged Weapon]] - How to create a basic ranged weapon with custom sound effects
* [[Modding_Tutorials/Basic_Plant|Basic Plant]] - How to create a custom plant with both a cultivated and wild variant
* Custom Animal (Upcoming)
* Simple Building (Upcoming)
* Custom Workbench (Upcoming)
* Custom Drug (Upcoming)

Advanced Tutorials:
* Custom Faction (Upcoming)
* Custom Culture (Upcoming)
* Custom Trader Type (Upcoming)

===C# Guides===

C# is used to create and define custom game behaviors

* [[Modding_Tutorials/Decompiling source code|Decompiling Source Code]] - How to set up and use a decompiler to read vanilla game code
* [[Modding_Tutorials/Setting up a solution|Setting up a Solution]] - How to set up a solution for compiling a custom mod assembly
* [[Modding_Tutorials/Application_Startup|Application Startup]] - Describes the application startup process and the order in which game data is loaded
* Custom Consumable (Upcoming)
* Custom Overlays (Upcoming)
* [[Modding_Tutorials/Code_FloatMenuOptionProvider|FloatMenuOptionProvider]] - How to use <code>FloatMenuOptionProvider</code> to add right click context menu options to arbitrary targets.
* [[Modding_Tutorials/Code_MendingJob|Example Mending Job]] - How to use a <code>FloatMenuOptionProvider</code> in conjunction with a <code>JobDef</code> and <code>JobDriver</code> in order to create a simple mending function for weapons and apparel.

===Updates and Migrations===

* [[Modding_Tutorials/RimWorld_1.5_Mod_Updates|RimWorld 1.5 Mod Updates]] - (WARNING: Anomaly Spoilers) Community notes for updating mods from 1.4 to 1.5.
* [[Modding_Tutorials/RimWorld_1.6_Mod_Updates|RimWorld 1.6 Mod Updates]] - (WARNING: Odyssey Spoilers) Community notes for updating mods from 1.5 to 1.6.

===Testing and Troubleshooting===

* [[Modding Tutorials/Testing mods|Testing Mods]] - Tips and tricks for testing mod content

===Slightly Outdated===

* [[Modding_Tutorials/Plague_Gun|Plague Gun]] - This tutorial was created for RimWorld 1.0 but updated for 1.4. While the exact content is obsolete as you can now accomplish the same result with purely vanilla XML, it is still useful as a crash course for end-to-end mod creation and is here until newer tutorials can replace it.

===Uploading to Steam Workshop===
* You can upload your mod to Steam Workshop by enabling Development Mode from your game Options and then using the Upload option under the Advanced button in the vanilla mod manager.
* Note that in order to upload to Steam Workshop, you must own the game on Steam Workshop. Owning RimWorld on GOG or Epic will not work.
* Your Preview.png should be a 640x360 or 1280x720 PNG and '''must''' be under 1MB. If it is too large, then your upload will be rejected with <code>Error : Limit Exceeded</code>
* If you get a <code>OnItemSubmitted Fail</code> error, make sure you close any programs that are targeting items in your mods folder. This can also mean that Steam Workshop is having some technical issues at the moment. If it keeps occurring, then the only thing to do is to wait a few hours for it to clear up.
* Steam mod descriptions don't use markdown, they use a variant of BBCode. Please check out the [https://steamcommunity.com/comment/Guide/formattinghelp Steam text formatting guide].

-----

'''Note:''' All of the above tutorials have been cleaned up and reviewed by the #mod-development team on the [https://discord.gg/rimworld RimWorld Discord] in cooperation with RimWorld Wiki staff editors. Please let us know before creating, adding, or making any major edits to the vetted tutorials and guides section!

==Outdated / Under Review==

The following tutorials are either out of date or in need of a rewrite. The information in them might be useful but may not be up to standard; please be aware of any potential inaccuracies until they can be addressed.

* [[Modding Tutorials/First Steps|First Steps and Some Links]]
* [[Modding Tutorials/Essence| Essence of Modding]]
* [[Modding Troubleshooting Tips and Guides]]
* [[Modding Tutorials/Sounds|Adding and Testing Sounds]]
* [[Modding Tutorials/Assets|Decompiling Texture/Sound Assets]]
* [[Modding Tutorials/Compatibility|Compatibility]]
* [[Modding_Tutorials/Distribution|Distribution]]
* [[Modding_Tutorials/Modifying defs|Modifying Defs]]
* [[Modding_Tutorials/Troubleshooting|Troubleshooting mods]]
* [[Modding Tutorials/Rituals]]

===XML tutorials===

* [[Modding Tutorials/XML file structure|XML File Structure]]
* [[Modding Tutorials/XML Defs|Introduction to XML Defs]]
** [[Modding Tutorials/Compatibility with defs|XML Def Compatibility]]
** [[Modding Tutorials/ThingDef|ThingDef explained]]
** [[Modding Tutorials/Weapons Guns|Weapons_Guns.xml explained]]. Slightly dated.
* [[Modding Tutorials/Xenotype template]] originally by Ryflamer

===C# tutorials===
* [[Modding_Tutorials/Hello World|Hello World]]
* [[Modding_Tutorials/Writing custom code|Writing Custom Code]]
* [[Modding Tutorials/Linking XML and C#|Linking XML and C#]]
* [[Modding_Tutorials/Harmony|Alter Code at Runtime with Harmony]] - this is a best practice for modifying game code, replacing C# code injection to reduce Mod Conflicts
* [[Modding_Tutorials/Modifying classes|Adding fields and methods to classes]]
* [[Modding Tutorials/ModSettings|Mod settings]] - Add settings to your mod
* [[Modding Tutorials/DefModExtension|Def mod extensions]] - Add (custom) fields to Defs
* [[Modding Tutorials/Custom Comp Classes|Custom Comp Classes]] - A quick overview of what types of Comps there are, and what they're suited for.
* [[Modding_Tutorials/ThingComp|ThingComp]] - Learn all there is to know about ThingComps.
* [[Modding Tutorials/GameComponent|Components]] - GameComponents, WorldComponents, and MapComponents
* [[Modding_Tutorials/Def classes|Introduction to Def Classes]]
* [[Modding_Tutorials/Compatibility_with_DLLs|Using Harmony to optionally patch other mods for the sake of compatibility]]
* [[Modding Tutorials/TweakValue|TweakValues]] - Change values on the fly (handy for quick iteration!)
* [[Modding Tutorials/ExposeData|ExposeData]] - Save stuff
* [[Modding Tutorials/BigAssListOfUsefulClasses|The big ass list of useful classes]] - A non-exhaustive list of classes you'll use most
* [[Modding Tutorials/GrammarResolver|Grammar Resolver]] - PAWN_objective, PAWN_possessive? Find out what it all means here.
* [https://github.com/Mehni/ExampleJob/wiki ExampleJob] - Mehni's top to bottom breakdown of Jobs.
* [[Modding_Tutorials/ConfigErrors|Config Errors]] - Provide configuration issues to the user on startup.
* [[Modding Tutorials/DebugActions|Debug Actions]] - Call methods from the debug menu
* [https://www.arp242.net/rimworld-mod-linux.html Getting started with RimWorld modding on Linux]

===Art Tutorials===
* [https://spdskatr.github.io/RWModdingResources/artstyle Artstyle] - Officially unofficial guide to RimWorld's Artstyle
* Ekksu's animal texture guides: [https://imgur.com/a/how-to-make-rimworld-sprites-its-basically-x-with-y-edition-wS3Pt 1] [https://imgur.com/a/how-to-make-rimworld-sprites-theres-nothing-that-looks-like-this-animal-edition-xdDzg 2]
* [https://steamcommunity.com/sharedfiles/filedetails/?id=1114369188 ChickenPlucker's guide to creating apparel]
* [https://github.com/seraphile/rimshare/wiki/Colouring-in-Images Seraphile's guide to masks]

===Under Construction===

These are currently unfinished and need to be cleaned up or removed

* [[Modding Tutorials/Quests]]
* [[Modding Tutorials/Troubleshooting/Finding Exceptions]]

==External Links==
* [https://github.com/roxxploxx/RimWorldModGuide/wiki Roxxploxx's set of modding tutorials]
* [https://spdskatr.github.io/RWModdingResources/ RimWorld Modding Resources - A hub for guides, modders, practical tips]

[[Category:Modding]]
[[Category:Modding tutorials]]

Modding Tutorials/Xenotypes

2026-05-23T23:34:47Z

Aelanna: Added outdated label

{{:Modding_Tutorials/Outdated}}

[[Xenotypes]] offer a wide range of possibilities for modders.

== Xenotype template ==
{{Recode|reason=1) Make collapsible 2) Sanguophage uses a bunch of special options - add these}}
The following is the template for assembling xenotypes from the [[genes]] in the game. Under each heading the existing genes are listed. Simply delete or comment out the genes you do not wish to include. This is best done by editing or viewing the source of this page and copy and pasting from there. Do not include the <nowiki><pre> and </pre> tags</nowiki>

It is accurate as of the 1st of November 2022. It is originally provided by Ryflamer but has since been modified.

<pre>
<?xml version="1.0" encoding="utf-8"?>
<Defs>
<XenotypeDef>
<defName>xenotypedefname</defName>
<label>ingame name</label>
<description>A long description goes here, where you can describe the lore and whatever</description>
<descriptionShort>A shorter description goes here</descriptionShort>
<iconPath>UI/Icons/Xenotypes/Hussar</iconPath>
<inheritable>true</inheritable> 
<nameMaker>NamerPersonDirtmole_Male</nameMaker> 
<nameMakerFemale>NamerPersonDirtmole_Female</nameMakerFemale>
<chanceToUseNameMaker>1</chanceToUseNameMaker>
<combatPowerFactor>1.5</combatPowerFactor> 
<genes>











































































































































































<



































































































</genes>
</XenotypeDef>
</Defs>
</pre>

== Adding xenotypes to generated pawns ==
{{Stub|section=1|reason=More details on how pawnkind and ideoligion generation affects xenotype selection. Information on <code>MustBeCapableOfViolence</code> flag on pawn generation request.}}
[[Factions]] have their distribution of xenotypes set in their faction def at the top level by the following:
<pre>
<xenotypeSet>
<xenotypeChances>
<Neanderthal MayRequire="Ludeon.RimWorld.Biotech">0.05</Neanderthal>
<Hussar MayRequire="Ludeon.RimWorld.Biotech">0.15</Hussar>
<Genie MayRequire="Ludeon.RimWorld.Biotech">0.10</Genie>
</xenotypeChances>
</xenotypeSet>
</pre>
<small>Note: The above is for a faction that is not defined by the [[Biotech DLC]], hence the may require. This difference is irrelevant to the interpretation method chosen.</small>
These values are then interpreted one of two ways.
First:
If the values add up to less than 1.0, then they are interpreted as percentage chances for a pawn, absent any other xenotype selections, to be that xenotype, with the remainder being the chance to be a baseliner. In the above example, as the sum of 0.05, 0.15, and 0.10 is only 0.30. As this is less than 1.0, there is a 5% chance for a pawn from that faction to be a [[neanderthal]], a 15% chance to be a [[hussar]], a 10% chance to be a genie, and a 70% chance to be baseliner.

Second:
If the values exceed 1.0, then the values are instead interpreted as a weight, where the chance is equal to the value for that xenotype divided by the sum of all the weights given. If baseliners are not included as a weight, they are excluded

For example:
<pre>
<xenotypeSet>
<xenotypeChances>
<Neanderthal>999</Neanderthal>
</xenotypeChances>
</xenotypeSet>
</pre>
<small>Note: The above is for a faction that is defined by the [[Biotech DLC]], hence the lack of may require. This difference is irrelevant to the interpretation method chosen.</small>
Neanderthals have a (999/999)*100%, or a 100% chance to be selected.

Additional xenotypeSet definitions can be made in [[memes]]{{Hover title|link=no|At the time of writing (version 1.4.3704), no memes in the official content contain xenotypeSet definitions.|<sup>[Note]</sup>}} and PawnKinds. Whenever a pawn generation request is made, the generator sums the xenotype chances from the faction, the PawnKind, and each meme of the faction's primary ideoligion. The totals are then interpreted as either probabilities or weights, as described above.

For example, suppose a pawn is generated using the faction at the top of this section and a PawnKind with the following configuration:
<pre>
<xenotypeSet>
<xenotypeChances>
<Highmate>0.25</Highmate>
<Genie>0.15</Genie>
</xenotypeChances>
</xenotypeSet>
</pre>
The chances will be added together, resulting in Neaderthal=0.05, Hussar=0.15, Genie=0.25 (from adding 0.10 and 0.15), and Highmate=0.25. The total of all of these is 0.7, leaving baseliners with a chance of 0.3.

Note that a PawnKind may have <code><useFactionXenotypes>false</useFactionXenotypes></code>, which causes the faction's xenotypeSet to be ignored.

[[Category: Modding tutorials]]

Titles

2026-05-22T14:19:08Z

Aelanna: While the change is more accurate, the actual in-game text is indeed incorrectly written specifically as "him" and thus should probably stay true to the game until it gets fixed.

{{Royalty}}
'''Titles''' are a mechanic introduced in the [[Royalty]] DLC, representing power and prestige from the [[Empire]].
{{TOCright}}
== Summary ==
Titles are obtained by spending '''Honor''', the currency of the Royalty system. Honor is offered as a [[quest]] reward, or can be purchased from Royal Tribute Collector caravans in exchange for either [[gold]] or [[prisoners]].

Titles come with demands. From the title of Acolyte onwards, the title holder will start to demand certain apparel, a proper throne room, and more prestigious bedrooms. There are also limits on [[recreation]]. Empire guests and colonists with certain [[traits]] will be ''conceited'' and have more demands. In exchange, the empire will grant increasing levels of [[Psylink]], and give you access to [[#Permits|Permits]].

Titles are retained if you become [[goodwill|hostile]] to the [[empire|empire faction]], though using permits is disabled until relations are restored. Titles can be renounced at the pawn's Bio screen.

'''Special Traits:'''
* [[Ascetic]]s do not have royal demands, overriding the clothing and bedroom needs entirely. They'll need a throne in an enclosed room, but do not care if throne requirements are unmet. However, their throne room's Impressiveness will affect their mood, positively or negatively. Note that Ascetics will need to meet throne requirements to get their title, and that the [[Psyfocus#Dignified|meditation effectiveness]] of the throne remains improved by meeting the title requirements.
* Pawns with the [[Nudist]] and [[Cannibal (Trait)|Cannibal]] traits prefer being nude or eating human meat over their title requirements.
* Pawns with the Greedy, Jealous, or Abrasive traits are [[Titles#Conceited_pawns|Conceited]] and will have greater royal demands.
* [[Slaves]]{{IdeologyIcon}} can be given Honor, and will rank up as usual, with the same clothing and room requirements. However, they are unable to use permits, and slavery overrides conceited pawns' inability to work. There is a bug where slaves in a [[caravan]] can use their permits.{{Check Tag|Check for 1.4}}

=== Conceited pawns ===
{{Stub|section=1|reason=When can they eat low-class food.}}
Pawns that are guests from, or are recruited from, the [[Empire]] faction, and those with the [[Greedy]], [[Jealous]], or [[Abrasive]] traits, are Conceited and will have greater royal demands. If [[Abrasive]] has been overridden by the [[Kind instinct]] gene{{BiotechIcon}} after they have a title they will still be conceited, but if they receive the gene before their first title then they will not be conceited even if the gene is removed later.{{Check Tag|Inc. post rank up?|Does this persist if they rank up without the gene?}}

Starting at [[Acolyte]] and getting more severe with each rank, conceited nobles will refuse to do work of certain types, and will normally only eat certain types of food.{{Check Tag|Clarification needed| Will they eat it if fed given it as a prisoner? Will they eat it if fed it as a patient?}} Conceited nobles that eat food not in their allowed list will receive {{Thought|desc=That meal was below my station. My title's formal requirements should always be respected.|label=Ate low-class food|value=-8|duration=1}}. Note that conceited pawns will only automatically eat low-class food if they are starving. Also note that [[hemogen pack]]s{{BiotechIcon}} count as food for this purpose, even when being consumed for [[hemogen]]{{BiotechIcon}} and not [[saturation]].

Conceited nobles have higher expectations then normal pawns, starting at [[Acolyte]] if their expectations would be lower they replace their regular [[Mood#Expectation moodlets|expectation moodlets]] with moderate expectations. Each additional title they get makes their minimum expectations one higher up to royal expectations at [[Archon]] and above.

The game will show a popup warning if you attempt to give a conceited pawn royal honor.

===Honor===
Honor is a direct reward for empire [[quest]]s that gives access to the empire's titles. Selling gold, prisoners, or [[slave]]s{{IdeologyIcon}} to a [[royal tribute collector]] also gives Honor. The pawn that does the selling gets the honor.
[[Skills#Social|Social]] skill or other social factors do not affect honor gain, but the pawn has to be [[Incapable|capable]] of Social in order to initiate trade.

*Selling [[prisoner]]s or slaves gives 3 honor per pawn. They must be able to walk while being sold, but no other qualities matter. This gives the regular penalties for selling humans.
**It is possible to use the [[painblock]] psycast to temporarily make a pawn mobile, then rescue the now-Empire pawn for a [[goodwill]] boost.
*[[Gold]] gives 0.015 point of Honor per gold item, rounded down. Therefore, the amount of gold per honor:
{| class="wikitable"
|-
! Gold Spent !! Honor || Equiv. Market Value
|-
! {{icon Small|gold}} 67
| 1 || {{#expr: {{Q|Gold|Market Value Base}}*67}}
|-
! {{icon Small|gold}} 134
| 2 || {{#expr: {{Q|Gold|Market Value Base}}*134}}
|-
! {{icon Small|gold}} 200
| 3 || {{#expr: {{Q|Gold|Market Value Base}}*200}}
|}

== Bestowing ceremony ==
{{see also|Quests#Noble_Ceremony{{!}}Quests}}
The lowest title, Freeholder, is automatically 'purchased' as soon as a pawn earns their first point of Honor. Any further titles must be obtained through the bestowing ceremony.

A colonist with enough honor for a new title can accept the received quest to invoke the [[Empire#Bestower|bestower]], a ceremonial priest-like figure who arrives by [[imperial shuttle]] with a retinue of guards. To accept the quest, the pawn to be bestowed must have a throne room that meets the requirements, even if they themselves do not care about it. There is no room requirement for Freeholder and Novice ranks. The bestowing ceremony will be performed in the throne room assigned to the pawn to be bestowed upon. If the throne room no longer meets requirements, or is unassigned from the pawn, then the quest will fail and the bestower will return home. If no such room is available, the bestower will instead attempt to find a [[party spot]] and failing that pick a social gathering spot.{{Check Tag|Confirm Social Spot|Party spot is right, needs more testing to verify whether they target social gathering spots}} The ceremony itself gives the psylink upgrade and title. The bestower carries 2 [[psylink neuroformer]]s; if you wish, you may [[down]], arrest, or kill the bestower to steal them. Bestowers will leave if they are exposed to dense{{Check Tag|Detail needed|Define: Dense}} [[tox gas]] or [[rot stink]].

If the quest fails for any reason except promotion to a higher rank, it will reoccur after a period of time.{{Check Tag|How long}}

If you receive enough honor to qualify for a higher title, then the lower title's bestowing ceremony will be skipped entirely. Note that this can result in lost opportunities to gain honor from the skipped ceremonies, but you will still receive all of the missed psycasts that you would have gotten if you hadn't skipped the lower titles.

The ceremony is considered a [[ritual]] and its outcome affects colonist mood. It can also grant extra honor based on ritual quality, up to a maximum of 3 honor at >90% quality. Quality is determined by participant count and room impressiveness. This is independent from the actual outcome.
{| {{STDT| c_07 text-center}}
!Ritual Quality
!0%
!30%
!60%
!90%
|-
!Honor Gained
| 0
| 1
| 2
| 3
|}

<gallery>
BestowingCeremony.jpg|A bestower granting the Archon rank to a pawn.
BestowingCeremonyDeparture.jpg|Bestower and guards leaving on shuttle after granting a title.
</gallery>

=== Inheritance ===
Titles from Acolyte onwards are able to be inherited. Heirs are automatically assigned, with additional weight towards spouses. They can be changed from a [[comms console]]; in order for heirs to actually change, you must complete a monument [[quest]]. Failure to complete the quest in time gives a [[goodwill]] penalty and causes no change.

When a noble dies, the heir will automatically gain the Freeholder title, if they didn't already have honor. They must begin a bestowing ceremony to obtain their proper rank. Should the noble be [[Resurrector mech serum|resurrected]], the title is lost, even if the bestowing ceremony hasn't begun yet.

== Titles ==
For a full list of titles and their requirements, see the [[#Table of requirements|Table of requirements]].

*'''Freeholder (1 honor):''' The Imperial title of freeholder is used by the Empire to signifies a fully-respected individual. Most Imperial citizens earn it while young through volunteer work or military service. The title is also offered to outsiders who act with honor in the eyes of the Empire.
*'''Novice (7 honor):''' The Imperial title of novice is held by those who have recently been initiated into the ranks of the psychic cult. It gives the holder the right to use low-level psychic abilities as part of their learning. This title is often held by senior soldiers, warskiff pilots, spies, advisors, diplomats, intrusion operatives, and other key individuals. Many important people spend their entire lives as novices.
*'''Acolyte (13 honor):''' The title of acolyte is the first title of senior learners in the psychic cult, and encompasses a wide range of practical positions. Some acolytes are purely students, learning to lead troops, manage societies, or use psycasts in specialized schools. Others come from wealthy families and might own city buildings or farm complexes. During wartime, an acolyte might lead a platoon of troops, captain a small frigate, or serve their liege as an advisor.
*'''Knight/Dame (21 honor):''' The title of knight is held by agents of the psychic cult who have fully passed their training, but who have not ascended to higher leadership roles. Many knights never advance further, and spend their lives as respected warriors, advisors, or commanders. In war, some knights lead troop companies and assault squadrons, while psychic-focused knights engage in espionage, sabotage, and battlefield psychic combat.
*'''Praetor (31 honor):''' The title of praetor denotes a member of the psychic cult who carries out field mission in a more senior role than a mere knight. During peacetime, a praetor will usually manage a city district, asteroid sector, or agricultural region. During war, they take authority over the smallest independent combat units - terrestrial troop cohorts, or space-borne destroyers or combat groups.
*'''Baron/Baroness (45 honor):''' The title of baron is the lowest of the psychic lords who can act as a semi-independent ruler. Most barons are subordinate to a higher lord. In the Empire, a baron will typically own a city sector, mining colony, or similar outfit. At wartime, a baron may captain a capital ship in name, or control a regiment of troops.
*'''Archon (65 honor):''' The title of archon is middle rank among the independent members of the psychic cult. In peacetime, an archon may rule to a city or colony. A successful archon might have a small personal fleet, possibly including capital ships.

===Unobtainable===

These titles cannot be obtained through honor without the use of mods, though it is possible to recruit a pawn that already has the title through arresting quest pawns or via [[Skip abduction]].

*'''Dominus:''' The Imperial title of dominus is the highest of the middle-ranked independent rulers. In the Empire, domini control provinces, mega-cities, or moons. At war, a dominus can field a division-level force, or a fleet with capital ships and dozens of support craft.
*'''Consul:''' The Imperial title of consul is a lower level of high nobility. In the Empire, consuls control planets. At war, a consul can usually field an army-sized force of multiple divisions, supported by several fleets. Some command from a super-capital ship or control space-based megastructures. (Note: Consul is only obtainable if Stellarch is converted to your colony as a colonist.)
*'''Stellarch:''' The Imperial title of stellarch represents dominion over an entire star system. In the Empire, since interstellar travel times are years long, stellarchs rule their systems with a great degree of independence. They each swear fealty to the Emperor, but since the Emperor may be many light-years away, a stellarch may go years or decades without interacting with him.
*'''Emperor/Empress:''' The Imperial title of emperor indicates sovereign dominion over the entire Empire, all its peoples, planets, and fleets. All other lords swear fealty to a high lord, while the Emperor swears fealty to no one. However, even the Emperor depends on the support of lower nobles to remain in power. (Note: The emperor is never seen in the normal game.)

== Requirements ==
For a full list of requirements per title, see [[#Table of requirements|Table of requirements]].

=== Thrones and Bedrooms ===
Titles of Acolyte and above require a throne room and separate bedrooms. Both rooms must be fully [[floor]]ed, and higher ranks will require all fine floors. As with non-titled pawns, couples can share a bedroom without penalty, regardless of either partners level of nobility. Unlike non-titled pawns however, nobles will object to sharing a room with a [[baby]].{{BiotechIcon}}

Any number of nobles can share a throne room, though they need individual thrones. Ways to remove a pawns [[sleep]] need, such as a [[Circadian half-cycler]], the [[Body mastery]] trait,{{AnomalyIcon}} or the [[Never sleep|Never sleep gene]],{{BiotechIcon}} do not negate the desire for a bedroom, though pawns won't sleep in it.

As the titles increase in honor, so does the minimum requirement. Greater titles have an increasing minimum # of floor tiles, Impressiveness, and require specific furniture.

For the purposes of the throne room requirement, they cannot have beds, workstations, ritual buildings from [[Ideology]] {{IdeologyIcon}}, or any building under the [[Biotech]] {{BiotechIcon}} or [[Anomaly]] {{AnomalyIcon}} tabs. However, they can function as Impressive recreation and dining rooms, giving your entire colony a mood buff. The [[meditation throne]] itself also functions as a chair, but the [[grand meditation throne]] can only be used for meditation and [[television]] watching.

[[Ascetic]] pawns do not have to meet bedroom requirements at all. They won't receive negative [[thought]] if their throne doesn't meet requirements, but they must have a suitable throne room to actually receive their title, and they will have reduced [[psyfocus]] from a throne if requirements aren't met.

=== Clothing requirements ===
Nobles of a rank that desire clothing will experience a {{--|4}} "''Want <TITLE>-specific apparel''" [[thought]] to their mood if any of their requirements are not met. For ranks that require a specific [[quality]], a separate stacking a {{--|4}} "''Want <TITLE>-quality apparel''" thought is applied if the items worn are not of the required quality.

Clothing requires that a noble is ''covered'' in suitable apparel, i.e. that all body parts have an associated apparel. For example, Archons (and below) can suffice with a [[cape]] and any suitable headgear, or the combination of headgear and [[formal shirt]], [[formal vest]] / [[corset]], and [[prestige robe]].

The [[Nudist]] trait and the [[Nudism]]{{ideologyIcon}} precepts override the clothing requirement, and Ascetic pawns ignore it. Any conflicting apparel requirements from simultaneously holding an [[ideoligion|ideoligious]] [[role]]{{IdeologyIcon}} are disabled, with the noble clothing requirement taking priority.

===Food requirements===
Conceited nobles will refuse to eat certain foods, with fewer items being acceptable as the ranks increase. In general, all conceited nobles can eat [[lavish meal]]s, [[milk]], and other delicacies like [[insect jelly]] and [[chocolate]]. Ranks lower than Baron can eat [[fine meal]]s normally. If a noble is starving, then they will eat the meal at a {{--|7}} mood penalty. Non-conceited nobles have no such restrictions.

Conceited [[Cannibal (Trait)|Cannibal]] nobles can eat [[human meat]] without penalty, and gain the normal positive moodlets from doing so. However, they still refuse to eat improper meals that include human meat, and when eating said meals, they will ''not'' get the benefit from the Cannibal trait. [[Sanguophages]] {{BiotechIcon}} and other Hemogenic nobles can bloodfeed, but can't consume [[hemogen pack]]s.

===Work restrictions===
Conceited nobles will refuse to do certain work types; the restriction increases with each title. Conceited pawns up to Archon will continue to do Doctor, Warden, Art, and Research work, but higher ranks can't do anything outside of combat. Non-conceited nobles have no such restrictions, as are nobles who are [[slaves|enslaved]]{{IdeologyIcon}}.

==Perks==
===Psylink===
{{Main|Psycasts}}
Every title, from Novice onward, grant an increase of 1 [[Psylink]] level. If a pawn already matches their title's respective level (from [[psylink neuroformer]]s or [[anima tree]] linking), then no new levels will be given.

The bestower will implant a [[psylink neuroformer]] during the noble's bestowing ceremony, but they come with two. It is possible to arrest the bestower for an extra level, but this makes the empire faction hostile to you. If they are [[downed]] for other reasons (like [[heatstroke]]), you will still lose [[goodwill]].

=== Permits ===
Nobles that have reached Acolyte or higher will gain access to '''Permits'''. One permit is awarded for every title from Acolyte onwards, for a maximum of five permits for Archons. Higher titles will give access to stronger permits. These can include item drops, immediate support, or even direct bombardments. Permits have a cooldown; if used during it, there is an Honor cost. A pawn can't demote themselves to use a permit again.

Once picked, permits stay with your pawn, and can't be freely changed. You can return all permits and re-assign them again; this costs 8 honor ''and'' the costs of any permit currently in cooldown. New permits won't have a cooldown, as the cost has been paid.

You can't use permits if the [[empire]] faction is hostile towards you. [[Slave|Enslaved]]{{IdeologyIcon}} nobles and guests from the [[Empire]] are also unable to use permits. If an NPC noble is captured, they will come with randomly assigned permits.

Permits are lost when titles are, such as upon revocation and death, inheritance, and resurrection.

Note that some permits do not work in [[orbit]]{{OdysseyIcon}} showing the message, "the [[Empire]] faction cannot reach this area."
{| class="wikitable sortable"
|-
! Permit Name !! Prerequisite !! Cooldown<br>(Days) !! Honor Cost<Br><small>(to ignore cooldown)</small> !! Description !! Works in<br>[[Orbit]]?{{OdysseyIcon}} !! data-sort-type=number | Equiv. Value
|- id="Call transport shuttle"
|'''Call transport shuttle'''
| data-sort-value=3|Knight/Dame
| 40
| 8
| Call a one-way [[imperial shuttle]] for your own use, which will transport colonists, items, and animals up to 70 tiles away.<br>The shuttle can hold a total of 1000kg on a loaded map, but as of 1.2.2900 it ignored this weight limit for [[caravan]]s.
| {{Check}}
| ''N/A''
|- id="Call laborer team"
|'''Call laborer team'''
| data-sort-value=2|Acolyte
| 60
| 4
| Call a group of 4 [[Empire#Laborer|laborers]] to assist you for 4 days. They are fully controllable, and their equipment can be changed freely. They are always incapable of violence, animals work, social and research; sometimes other tasks are restricted by backstories. Each laborer death nominally causes a loss of 12 goodwill but this is not actually applied as of 1.4.3704. When downed or killed, laborers deduct [[Raid_points#Adaption_factor|adaptation days]] as if they were full colonists. Useful for menial labor, but also no worse in combat than any other violence-incapable meat shield, with the added advantages of being perfectly expendable and occasionally having [[Empire#Xenotypes|robust or pain-resistant xenotypes]].
| {{Cross}}
| ''N/A''
|- id="Call laborer gang"
|'''Call laborer gang'''
| data-sort-value=6|Archon<br>[[#Call laborer team|Laborer Team]]
| 60
| 8
| As ''Call laborer team'', but twice the headcount.<br>Loses access to laborer team.
| {{Cross}}
| ''N/A''
|- id="Call aerodrone strike"
|'''Call aerodrone strike'''
| data-sort-value=3|Knight/Dame
| 45
| 6
| Call a single-impact aerodrone strike at a target position. 45 tile range, 3 tile miss radius, 8 tile explosion radius, 50 [[Damage types#Bomb|Bomb damage]], {{ticks|120}} warmup time.
| {{Cross}}
|{{icon Small|silver||{{Q|Doomsday rocket launcher|Market Value Base}}}}{{ref label|Equiv|*}}
|- id="Call aerodrone salvo"
|'''Call aerodrone salvo'''
| data-sort-value=4|Praetor <br> [[#Call aerodrone strike|Aerodrone Strike]]
| 60
| 8
| Call an extended salvo of aerodrone strikes around a target position. 45 tile range, 8 tile miss radius, 6 tile explosion radius, 50 [[Damage types#Bomb|Bomb damage]], {{ticks|120}} warmup time. 6 rounds with {{ticks|60}} between them.<br>Loses access to aerodrone strike
| {{Cross}}
| {{icon Small|silver||{{Q|Orbital bombardment targeter|Market Value Base}}}}{{ref label|Equiv2|*}}
|- id="Call trooper squad"
|'''Call trooper squad'''
| data-sort-value=2|Acolyte
| 40
| 4
| Call a group of 4 light [[Empire#Trooper|troopers]] to aid you in battle, who can't be controlled. They will refuse to attack pawns that are not enemies to the Empire.
| {{Cross}}
| ''N/A''
|- id="Call janissary squad"
|'''Call janissary squad'''
| data-sort-value=4|Praetor
| 50
| 6
| Call a group of 4 professional [[Empire#Janissary|janissaries]] to aid you in battle. As troopers otherwise.
| {{Cross}}
| ''N/A''
|- id="Call cataphract squad"
|'''Call cataphract squad'''
| data-sort-value=6|Archon<br> [[#Call Janissary Squad|Janissaries]]
| 60
| 8
| Call a group of 4 heavy [[Empire#Cataphract|cataphracts]] to aid you in battle. As troopers otherwise.<br>Loses access to janissary squad.
| {{Cross}}
| ''N/A''
|- id="Steel drop"
|'''Steel drop'''
| data-sort-value=2|Acolyte
| 45
| 4
| Call for a drop of 250 [[steel]].
| {{Check}}
| {{icon Small|silver||{{#expr:{{Q|steel|Market Value Base}}*250}}}}
|- id="Glitterworld medicine drop"
|'''Glitterworld medicine drop'''
| data-sort-value=5|Baron/Baroness
| 45
| 8
| Call for a drop of 5 [[glitterworld medicine]].
| {{Check}}
| {{icon Small|silver||{{#expr:{{Q|glitterworld medicine|Market Value Base}}*5}}}}
|- id="Silver drop"
|'''Silver drop'''
| data-sort-value=3|Knight/Dame
| 45
| 6
| Call for a drop of 500 [[silver]].
| {{Check}}
| {{icon Small|silver||500}}
|- id="Food drop"
|'''Food drop'''
| data-sort-value=2|Acolyte
| 45
| 4
| Call for a drop of 20 [[packaged survival meal]]s.
| {{Check}}
| {{icon Small|silver||{{#expr:{{Q|packaged survival meal|Market Value Base}}*20}}}}
|}
:{{note|Equiv|*}} Roughly equivalent to a [[Doomsday rocket launcher]]
:{{note|Equiv2|*}} Inferior, but most closely equivalent, to an [[Orbital bombardment targeter]]

===Leader Speeches===
{{Quote|Initiate a speech from the throne. '''<PAWN NAME>''' will go to '''<PAWN POSSESSIVE>''' throne and call all colonists to listen to a speech there. If all goes well, listeners will feel inspired, and gain respect for '''<PAWN NAME>'''. If it goes poorly, the speech will do social damage. The outcome depends on '''<PAWN NAME>''''s social abilities.|In-Game Description}}

At Praetor rank, Nobles gain the ability to give leader speeches. This ability is a [[ritual]] manually triggered by the player. These speeches have a cool down, require an assigned throne, and cannot happen while another gathering is happening. Speeches last {{ticks|10000}} or 4 in-game hours.

A speech grants attendees a [[Mood#Gatherings|moodlet]] and changes the listener's opinion of the speaker, both proportional to the success of the speech:
*A "Terrible Speech" will grant a -12 negative mood to attendees and a -30 opinion of the speaker.
*An "Uninspiring Speech" will grant a -4 negative mood to attendees and a -15 opinion of the speaker.
*An "Encouraging Speech" will grant a +4 positive mood and a +20 opinion of the speaker.
* An "Inspirational Speech" grants a +8 to mood and a massive +40 opinion of the speaker. Each listener has a 5% chance of getting an [[inspiration]].

A higher [[Social Impact]] can greatly improve success, but the exact relationship is unknown. High social skill pawns are better at giving speechs, while [[top hat]]s, [[coronet]]s, and other royal items can also increase social impact.

The cooldown between uses of the speech ability varies by rank. At Praetor rank this cooldown is {{ticks|1200000}} or 20 in-game days. At Baron rank this cooldown is {{ticks|900000}} or 15 in-game days. At Archon rank or higher, this cooldown is {{ticks|600000}} or 10 in-game days.

===Trading===
A rank of Knight/Dame is required to trade with an empire [[faction base]] or trade caravan.

A rank of Baron/Baroness or higher is required to trade with the empire's [[comms console|trade ships]].

=== Decrees ===
{{stub|section=1|reason=Needs more info. Also, link is effectively dead}}
{{Main|Decree}}
Nobles will sometimes issue a "decree" quest as part of a mental break, or at random if [[conceited]]{{Check Tag|Verify}}. Decrees demand things such as producing, harvesting, or killing some number of a certain thing, or constructing a monument. The quest gives no reward except for a positive moodlet of {{+|6}} "Decree satisfied"{{Check Tag|Thought template}} for 15 days to the noble when fulfilled. If the quest's deadline is not met, the noble who issued it gets a negative "Decree ignored" moodlet{{Check Tag|Thought template}}⁰ starting at {{--|5}} and increasing linearly to {{--|15}} over the course of 15 days. A noble can issue more decrees before the current one is fulfilled, though only the oldest "Decree ignored" applies at a time.

Dying, being kidnapped, or renouncing a title ends any current decrees as of 1.1.2579.{{Check Tag|Verify currently}} Decrees are also forgotten after 80 days if unfulfilled.

== Table of requirements ==
{| {{STDT|sortable c_19 align-right}}
|-
! Obtainable Titles !! Royal Honor Required (total) !! Psylink Level !! {{Good|Capable|noFormat=1}}/{{Bad|Incapable|noFormat=1}} of<br><sub>Only if Noble is [[Titles#Conceited_pawns|Conceited]]</sub><br><sub>(New restrictions in Bold)</sub> !! Throne Room Requirements<br><sub>(New this tier in Bold)</sub> !! Bedroom Requirement<br><sub>(New this tier in Bold)</sub> !! Food Requirements<br><sub>Only if Noble is [[Titles#Conceited_pawns|Conceited]]</sub><br><sub>(Lost next tier in ''italic'')<sub> !! Clothing Requirement<br><sub>(New this tier in Bold)</sub><br><sub>(Lost next tier in ''italic'')<sub> !! New Abilities with this Rank
|- id="Freeholder"
! Freeholder
| 1 || 0 || {{Good|'' Any ''|noFormat=1}} || ''None'' || ''None'' || ''Any'' || ''Any'' || ''None''
|- id="Yeoman"
! Novice
| 6 (7) || 1 || {{Good|'' Any ''|noFormat=1}} || ''None'' || ''None'' || ''Any'' || ''Any'' || ''None''
|- id="Acolyte"
! Acolyte
| 6 (13) || 2 || {{Bad|'''Cleaning'''|noFormat=1}} || '''Area 24, Throne, all floored, Brazier x2'''<br><sub>All braziers must be lit, Room must be [[roof]]ed</sub>
|| '''Area 16, all floored, Double bed''' || [[Fine meal]], ''[[Packaged survival meal]]'', ''[[Simple meal]]'', ''[[Pemmican]]'', [[Lavish meal]], [[insect jelly]], [[milk]], [[berries]], [[ambrosia]], [[chocolate]], [[beer]] || One of: '''[[Top hat]]/[[Ladies hat]], [[Eltex helmet]], [[Eltex skullcap]], [[Prestige armor|Prestige helmet]], [[Mechlord helmet]]'''; AND<br>One of: '''[[Formal shirt]], [[Cape]], [[Eltex shirt]], [[Eltex vest]], [[Eltex robe]], [[Prestige armor]], [[Mechlord suit]]''' || 1 Permit Point
|- id="Knight"
! id="Dame" | Knight/Dame
| 8 (21) || 3 || {{Bad|Cleaning, '''Haul'''|noFormat=1}} || '''Area 30''', '''Impressiveness 60''', Throne, all floored, Brazier x2, '''Column x2''', '''Harp''' <br><sub>Harpsichord or Piano suffice, All braziers must be lit, Room must be [[roof]]ed</sub>
|| '''Area 24''', '''Impressiveness 40''', all floored, Double bed, '''End table, Dresser''' || [[Fine meal]], [[Lavish meal]], [[insect jelly]], [[milk]], [[berries]], [[ambrosia]], [[chocolate]], [[beer]] || One of: [[Top hat]]/[[Ladies hat]], [[Eltex helmet]], [[Eltex skullcap]], [[Prestige armor|Prestige helmet]], [[Mechlord helmet]]; AND<br>One of: [[Formal shirt]], [[Cape]], [[Eltex shirt]], [[Eltex vest]], [[Eltex robe]], [[Prestige armor]], [[Mechlord suit]] || 1 Permit Point <Br> Trade with Empire Caravan/Settlements
|- id="Praetor"
! Praetor
| 10 (31) || 4 || {{Good|'' Cook, Construct, Smith, Handle, Tailor, Craft, Doctor, Warden, Hunt, Art, Research ''|noFormat=1}}<br/> {{Bad|Cleaning, Haul, '''Plant cut''', '''Grow''', '''Mining'''|noFormat=1}} || '''Area 40''', '''Impressiveness 90''', Throne, all floored, Brazier x2, '''Column x4''', Harp <br><sub>Harpsichord or Piano suffice, All braziers must be lit, Room must be [[roof]]ed</sub>
|| Area 24, '''Impressiveness 50''', all floored, Double bed, End table, Dresser || ''[[Fine meal]]'', [[Lavish meal]], [[insect jelly]], [[milk]], [[berries]], [[ambrosia]], [[chocolate]], [[beer]] || One of: ''[[Top hat]]/[[Ladies hat]]'', [[Eltex helmet]], [[Eltex skullcap]], [[Prestige armor|Prestige helmet]], [[Mechlord helmet]]; AND<br>One of: [[Formal shirt]], [[Cape]], [[Eltex shirt]], [[Eltex vest]], [[Eltex robe]], [[Prestige armor]], [[Mechlord suit]]<br><sub>'''(All apparel must be at least Normal [[quality]])'''</sub>|| 1 Permit Point <Br> Give speech once per 20 days
|- id="Baron"
! id="Baroness" | Baron/Baroness
| 14 (45) || 5 || {{Good|'' Doctor, Warden, Hunt, Art, Research ''|noFormat=1}}<br> {{Bad|Cleaning, Haul, Plant cut, Grow, Mining, '''Cook''', '''Construct''', '''Smith''', '''Handle''', '''Tailor''', '''Craft'''|noFormat=1}} || '''Area 60''', '''Impressiveness 120''', '''Grand Throne''', '''all [[fine floor|''fine'' floored]]''', Brazier x2, Column x4, '''Drape x2''', '''Harpsichord''' <br><sub>Piano suffices, All braziers must be lit, Room must be [[roof]]ed</sub>
|| '''Area 30''', '''Impressiveness 70''', all floored, '''Royal bed''', End table, Dresser, '''Drape''' || [[Lavish meal]], [[insect jelly]], [[milk]], [[berries]], [[ambrosia]], [[chocolate]], [[beer]] ||One of: '''[[Coronet]]''', [[Eltex helmet]], [[Eltex skullcap]], [[Prestige armor|Prestige helmet]], [[Mechlord helmet]]; AND EITHER<br>Two of: [[Formal shirt]], '''[[Formal vest]]/[[Corset]]'''; OR<br>One of: [[Cape]], [[Eltex shirt]], [[Eltex vest]], [[Eltex robe]], [[Prestige armor]], [[Mechlord suit]].<br><sub>(All apparel must be at least Normal [[quality]])</sub>|| 1 Permit Point <Br> Trade with Imperial orbital traders <Br> Speech cooldown reduced to 15 days <Br> Expectations replaced with Noble Expectations if Conceited
|- id="Archon"
! Archon
| 20 (65) || 6 || {{Good|'' Doctor, Warden, Hunt, Art, Research ''|noFormat=1}}<br> {{Bad|Cleaning, Haul, Plant cut, Grow, Mining, Cook, Construct, Smith, Handle, Tailor, Craft|noFormat=1}} || '''Room area 80''', '''Room impressiveness 160''', Grand throne, all [[fine floor]]ed, Brazier x2, '''Column x6''', Drape x2, '''Piano'''<br><sub>All braziers must be lit, Room must be [[roof]]ed</sub>
|| Area 30, '''Impressiveness 80''', '''All [[fine floor|''fine'' floored]]''', Royal bed, End table, Dresser, Drape || [[Lavish meal]], [[insect jelly]], [[milk]], [[berries]], [[ambrosia]], [[chocolate]], [[beer]] ||One of: ''[[Coronet]]'', [[Eltex helmet]], [[Eltex skullcap]], [[Prestige armor|Prestige helmet]], [[Mechlord helmet]]; AND EITHER<br> All of: [[Formal shirt]], [[Formal vest]]/[[Corset]], '''[[Prestige robe]]'''; OR<br>One of: ''[[Cape]]'', [[Eltex shirt]], [[Eltex vest]], [[Eltex robe]], [[Prestige armor]], [[Mechlord suit]].<br><sub>(All apparel must be at least Normal [[quality]])</sub>|| 1 Permit Point <Br> Speech cooldown reduced to 10 days<Br> Expectations replaced with Royal Expectations if Conceited
|-
|}

{| class="table c_19 align-right"
! NPC Titles !! Psylink Level !! Incapable of !! Throne Room Requirements !! Bedroom Requirements !! Food Requirements !! Clothing Requirement
|-id="Dominus"
! Dominus
| rowspan="4" style="text-align: center;" | 6
| rowspan="4" | Cleaning, Haul, Plant cut, Grow, Mining, Cook, Construct, Smith, Handle, Tailor, Craft, Art, Research, Basic, Doctor, Firefight
| rowspan="4" | Area 80, Impressiveness 160, Grand throne, all [[fine floor]]ed, Brazier x2, Column x6, Piano<br><sub>All braziers must be lit</sub><br><sub>Room must be [[roof]]ed</sub>
| rowspan="4" | Area 30, Impressiveness 80, all [[fine floor]]ed, Royal bed, End table, Dresser, Drape
| rowspan="4" | [[Lavish meal]], [[insect jelly]], [[milk]], [[berries]], [[ambrosia]], [[chocolate]], [[beer]]
| rowspan="4" | One of: '''[[Stellic crown]]''', [[Eltex helmet]], [[Eltex skullcap]], [[Prestige armor|Prestige helmet]]; AND EITHER<br> All of: [[Formal shirt]], [[Formal vest]]/[[Corset]], '''[[Prestige robe]]'''; OR<br>One of: [[Eltex shirt]], [[Eltex vest]], [[Eltex robe]], [[Prestige armor]].<br><sub>(All apparel must be at least Normal [[quality]])</sub>
|-id="Consul"
! Consul
|-id="Stellarch"
! Stellarch
|-id="Emperor"
! id="Empress" | Emperor/Empress
|}

==Trivia==
The royal favor icon is reminiscent of the head of the [[eltex staff]] carried by the [[Empire#Pawns|Bestower]]. This is fitting, since the bestower grants the received titles to the pawn.
If the map is polluted enough,{{Check Tag|How polluted?}} the bestower will come with a gas mask instead of their usual headgear.

== Gallery ==
These are only provided as easily comparable examples - they are not considered ideal or efficient.
<gallery class="center" mode="nolines">
File:Room example Acolyte Throneroom.png|'''Acolyte Example Throne Room '''
File:Room example Knight Throneroom.png|'''Knight Example Throne Room '''
File:Room example Praetor Throneroom.png|'''Praetor Example Throne Room '''
File:Room example Baron Throneroom.png|'''Baron Example Throne Room '''
File:Room example Count Throneroom.png|'''Archon Example Throne Room '''
</gallery>
<gallery class="center" mode="nolines">
File:Room example Acolyte Bedroom.png|'''Acolyte Example Bedroom '''
File:Room example Knight Bedroom.png|'''Knight Example Bedroom '''
File:Room example Praetor Bedroom.png|'''Praetor Example Bedroom '''
File:Room example Baron Bedroom.png|'''Baron Example Bedroom '''
File:Room example Count Bedroom.png|'''Archon Example Bedroom '''
</gallery>

== Version history ==
{{Stub|section=1|reason=Record old title names and flavor after 1.5.4241 change}}
* [[Royalty DLC]] Release - Added.
* [[Version/1.1.2563|1.1.2563]] - [[Resurrector mech serum]] now removes royal titles, to prevent duplicating titles.
* [[Version/1.1.2571|1.1.2571]] - Baron can now do Animals, Count can now do commoner work and instead is now only unable to do same as Baron, plus Animals.
* [[Version/1.1.2575|1.1.2575]] - Added the ability to renounce the title from the bio tab.
* [[Version/1.1.2579|1.1.2579]] - Mechanics were changed from all Nobles having hard restrictions, to only some. Dying, being kidnapped, or renouncing a title now ends decrees.
* [[Version/1.1.2654|1.1.2654]] - Rename esquire to acolyte. Adjust some title descriptions.
* [[Version/1.2.2719|1.2.2719]] - Added permits system, previous ally summon abilities subsumed into it with new abilities added. Speech duration: 5hrs -> 4hrs. Inspiring Speeches have 5% chance to inspire each attendee. Titles no longer gained instantly nor neuroformers drop podded in - both replaced with Bestower and Bestowal Ceremony. Renamed royal favor to honor. New visual effects for all orbital bombardments - you can now see and hear incoming projectiles and other details are improved. Fix: LOS calcs for purpose of royal aid don't match LOS for guns.
* [[Version/1.2.2753|1.2.2753]] - Removed full-map light up effect of all strikes. Added new permits: Steel drop, Glitterworld medicine drop, Silver drop, Food drop. Renamed Orbital Strike and Orbital Salvo permits to Aerodrone Strike and Aerodrone Salvo (for fiction coherence reasons). Increased warmup time for aerodrone permits by 1 second. Titles no longer instantly transferred to heirs upon death of noble - now triggers bestower quest for the heir. Added new noble compatible clothing: Beret, Cape, Eltex Skullcap, and Stellic Crown. Stellarch and other non-rewardable title holding pawns now get any permits. NPC nobles now purchase random permits on generation.
* [[Version/1.3.3066|1.3.3066]] - Throne speeches have been re-tooled into [[rituals]].
* Prior to 1.4 - Higher tier instruments can now be used in place of lower tier instruments to meet the requirements of lower rank nobles. E.g. a piano can be used to fulfil the need a praetor's need for a harp. Previously, the exact instrument had to be used.
* [[Version/1.3.3159|1.3.3159]] - Resurrected pawns with titles that were inherited lose all permits associated with the lost titles.
* [[Version/1.4.3523|1.4.3523]] - Fix: Permit shuttle fails when sent to a worksite.
* [[Version/1.4.3534|1.4.3534]] - [[Mechlord suit]] and [[Mechlord helmet|helmet]] now satisfies royal title requirements.
* [[Version/1.4.3580|1.4.3580]] - Bestowers will leave if they are exposed to dense tox gas or rot stink.
* [[Version/1.4.3641|1.4.3641]] - Fix: Permits not reset when royal pawn dies, has title inherited, then is resurrected
* [[Version/1.5.4241|1.5.4241]] - Re-flavor royal titles.
[[Category: Game mechanics]]
[[Category:Royalty]]

Life support unit

2026-05-22T14:14:19Z

Aelanna: Keeping it simple.

{{Odyssey}}
{{Stub|reason=Infobox, general}}
{{infobox main|building|
| name = Life support unit
| image = LifesupportUnit.png
| description = A unit connected to the orbital platform's larger life support network. It keeps rooms heated and pressurized.
| type = Building
| type2 = Ruins
| size = 1 ˣ 1
| hp = 35
| power = 3200
| heatpersecond = 30
| junk = false
}}
The '''Life support unit''' is a wall-mounted building that produces [[power]], [[heat]], and [[Vacuum|oxygen]].

== Acquisition ==
Life support units cannot be constructed or minified. They can only be found on abandoned orbital platforms, where they are typically abundant.

== Summary ==
{{Stub|section=1|reason=Need info on power generation}}

Every {{ticks|250}}, a life support unit lowers the [[vacuum]] percentage of its current [[room]]. The room must be enclosed by [[airtight]] structures and [[roof]]ed. It changes the vacuum percentage at a base rate of {{Down|-5%}} per second per 100 tiles, scaling proportionally to the number of tiles enclosed; for instance, a room with 25 tiles will reduce the vacuum percentage by {{Down|-20%}} per second, while a room with 200 tiles will drop by {{Down|-2.5%}} per second. Multiple oxygen sources may be required to pressurize especially large rooms.


Life support units will attempt to heat the room so long as the room temperature is lower than {{Temperature|20}}. As opposed to a [[heater]], the target temperature cannot be configured.

{{Wall Mount Note}}

== Analysis ==
{{Stub|section=1|reason=Analysis stub}}
Although these cannot be built or claimed, like all power buildings power can be drawn from it by connecting power conduits of any kind to it. Set up a base in an abandoned orbital platform and never worry about power, heat, or vacuum again.

== Version history ==
* [[Odyssey DLC]] Release - Added.

{{Nav/Ruins|Wide}}
[[Category: Ruins]]

Spelopede

2026-05-08T04:23:49Z

Aelanna: This needs to be fixed in the TrainingTable template, not tacked on.

{{Stub|reason=Do spelopedes (after hive destroyed) still attack colonists like megaspiders do? Add to analysis}}
{{Infobox main|animal
| page verified for version = A14C
| name = Spelopede
| image = Spelopede east.png
| description = A medium-sized bioengineered insectoid the size of a sheep. The spelopede is the middle caste of a hive, taking care of most work tasks as well as fighting with its digging claws. It's dangerous in combat, but slow on open ground.
| type = Animal
| type2 = Insectoid
| flammability = 0.7
| marketvalue = 200
| armorblunt = 18
| armorsharp = 18
| combatPower = 75
| movespeed = 3.65
| baseleatheramount = 0
| bodysize = 0.8
| body = BeetleLikeWithClaw
| healthscale = 1.7
| hungerrate = 0.25
| diet = omnivorous, animal products
| wildness = 0.3
| manhuntertame = 0
| manhunter = 0.5
| trainable = Advanced
| meatname = insect meat
| lifespan = 6
| juvenileage = 0.03
| maturityage = 0.2
| toxic resistance = 1
| toxic environment resistance = 0.8
| vacuum resistance = 1
| min comfortable temperature = -25
| max comfortable temperature = 60


| attack1label = head claw
| attack1type = Cut
| attack1dmg = 7
| attack1cool = 2
| attack1part = HeadClaw

| attack2label = head
| attack2type = Blunt
| attack2dmg = 6
| attack2cool = 2
| attack2part = HeadAttackTool
| attack2ensureLinkedBodyPartsGroupAlwaysUsable = true
| attack2chancefactor = 0.2
| isCoastal = false

| devNote = insect
| defName = Spelopede
| label = spelopede
| tradeTags = AnimalInsect
}}
'''Spelopedes''' are giant, bio-engineered, subterranean invertebrates and the middle of the three [[insectoid]] types in both size and danger.

== Acquisition ==
{{PAGENAME}}s can be found underground in [[World generation#Caves|caves]] and [[infestation]]s or inside [[ancient shrine]]s. They can be tamed by a [[Work #Handle|handler]].

== Summary ==
Spelopedes can inhabit any terrain where an [[infestation]] has spawned. They are dangerous in combat, but slow on open ground.

Their body is composed of a head, head claw, mouth, pronotum, shell, elytras (left and right), and two pairs of legs (front and back).

{{Insectoid Summary}}

== Analysis ==
Spelopedes are between [[megaspider]]s and [[megascarab]]s, with in-the-middle speed and health.

Wild {{PAGENAME}}s always generate hostile, making them difficult to tame as they will try to attack the animal handler. However, animal interactions during the process will interrupt any attacks. It may be ideal to equip your handler with armor, or to select a handler with a high melee skill for a higher melee dodge chance to reduce the risk of harm, though this is not strictly necessary.

{{PAGENAME}}s are practically impossible to tame when they first spawn from an infestation. In order to try and tame a {{PAGENAME}}, you will need to down them, then destroy all hives from the infestation. With Too Deep: Infestation event and Wastepack Infestations, there are no hives, so all you need to do is down the insect. This does not make them non-hostile, but it will prevent them from seeking out colonists like a raider would. Note that wild {{PAGENAME}}s unlike other animals cannot be operated on and thus can't be anesthetized, and they are prone to waking up and attacking the pawn treating them, Waiting for blood loss to reach extreme can prevent this.

They are rather accessible and easy to maintain haulers having the lowest wildness, being only beaten by [[Husky|Huskies]], and [[Labrador retriever]]s however for most purposes the [[megaspider]] is the better option. Megaspiders are stronger in combat, but have 40% wildness and move {{Bad|{{#expr: {{P|Move Speed Base}} - {{Q|Megaspider|Move Speed Base}} }} }} {{CS}} slower along with slightly higher hunger rate. With [[Odyssey]] Spelopedes can be taught to dig.

For [[Orbit]],{{OdysseyIcon}} Spelopedes even with vacuum immunity still struggle with space due to the -75 outdoor temperature and their poor min temp. Spelopedes can only handle a short period in space before being downed by [[Ailments#Hypothermic_slowdown|hypothermic slowdown]] which will also reduce their [[manipulation]] making them worse at mining being capable of mining roughly 3 vacstone before needing rescue, thus they are surpassed in work speed by colonists wearing [[Vacsuit]]s or [[Tunneler]]s.{{BiotechIcon}} For combat and hauling in space, Megaspiders can be out for longer with higher minimum temperature.

== Training ==
{{TrainingTable}}

== Health ==
=== Body parts ===
{{Animal Health Table|BeetleLikeWithClaw}}
=== Armor ===
{| class="wikitable"
! Armor
|-
| {{Apparel Protection Chart
| set1name= {{P|Name}} (Sharp) | set1armor1={{P|Armor - Sharp}}
| set2name= {{P|Name}} (Blunt) | set2armor1={{P|Armor - Blunt}}
| set3name= {{P|Name}} (Heat) | set3armor1={{P|Armor - Heat}}
| color= grey, blue, red
}}
|}
{{Pawn Attack Table}}

== Gallery ==
<gallery>
Spelopede east.png|Facing east
Spelopede north.png|Facing north
Spelopede south.png|Facing south
</gallery>
<gallery>
File:Dessicated spelopede east.png|Dessicated facing east
File:Dessicated Spelopede north.png|Dessicated facing north
File:Dessicated Spelopede south.png|Dessicated facing south
</gallery>
== Version history ==
* Beta 19/1.0 - All insects main attack cooldowns 2.5 -> 2.9
* 1.3 - Manhunter on tame fail decreased from 20% to 10% - manhunter on harm increased from 35% to 50% - wildness decreased from 95% to 30% - trainability changed from intermediate to advanced - gestation changed from N/A to 6
* [[Version/1.3.3200|1.3.3200]] - Fix: Remove gestation period stat, since they do not breed.
* [[Biotech DLC]] release - Now gains [[pollution stimulus]] on [[polluted]] terrain.

{{Nav|animal}}
[[Category:Animals]]
[[Category:Insectoid]]

Megavole

2026-05-08T04:18:42Z

Aelanna: Dig needs to be added to the TrainingTable template, not tacked onto the end.

{{Odyssey}}
{{Stub|reason=Inadequateanalysis, and if necessary, Summary}}
{{Infobox main|animal
| name = Megavole
| image = Megavole east.png
| description = A massive burrowing rodent, bred for its size and strength. It's almost completely blind but can be surprisingly aggressive when cornered. On some low-tech worlds, these creatures are trained to dig for valuable minerals.
| type = Animal
| movespeed = 3.2
| min comfortable temperature = -15
| max comfortable temperature = 40
| flammability = 0.7
| marketvalue = 250
| filth rate = 2
| wildness = 0.40
| toxic resistance = 0.5
| toxic environment resistance = 0.8
| combatPower = 70
| bodysize = 0.8
| healthscale = 1
| hungerrate = 0.5
| diet = omnivorous grazer
| leathername = Lightleather
| manhunter = 0.1
| manhuntertame = 0
| trainable = intermediate
| petness = 0.05
| mateMtb = 12
| gestation = 5.661
| lifespan = 8
| specialtrainables = Dig
| nuzzleMtb = 72
| juvenileage = 0.1
| maturityage = 0.2222
| tradeTags = AnimalUncommon
| offspring = 1-2
| avg offspring = 1.60
| attack1dmg = 8
| attack1type = Scratch
| attack1cool = 2
| attack1part = left claw
| attack2dmg = 8
| attack2type = Scratch
| attack2cool = 2
| attack2part = right claw
| attack3dmg = 14
| attack3type = Bite
| attack3cool = 2.6
| attack3part = Teeth
| attack3chancefactor = 0.7
| attack4dmg = 5
| attack4type = Blunt
| attack4cool = 2
| attack4part = head
| attack4chancefactor = 0.2
| isCoastal = false
| livesin_glowforest = 0.25
}}
A '''megavole''' is an [[animal]] added by the [[Odyssey DLC]].

== Acquisition ==
{{PAGENAME}}s can be found in {{Habitats}}. They can either be tamed by a [[Work #Handle|handler]] or self-tame in a random event.

{{PAGENAME}}s can be bought and sold in other [[Trade#Faction base|faction bases]] and from [[Trade#Exotic goods trader 2|exotic goods traders]]. {{PAGENAME}}s purchased from traders will be already tamed.

== Summary ==
?

== Analysis ==
Megavole can be trained to Dig marked tiles. They will mine any marked tiles they can reach in their allowed area.

They have equivalent digging skill of a pawn with 8 Mining making them less useful for maximizing ore yields.

Conversely they are unaffected by light levels, can graze on nearby plant life and will only stop mining to eat or rest.

== Training ==
{{TrainingTable}}

== Health ==
{{Animal Health Table|QuadrupedAnimalWithPaws}}
{{Pawn Attack Table}}

== Gallery ==
<gallery>
Megavole east.png|Facing east
Megavole north.png|Facing north
Megavole south.png|Facing south
</gallery>
<gallery>
File:Dessicated Megavole east.png|Desiccated facing east
File:Dessicated Megavole north.png|Desiccated facing north
File:Dessicated Megavole south.png|Desiccated facing south
</gallery>

== Version history ==
* [[Odyssey DLC]] Release - Added.

{{Nav|animal}}
[[Category:Animals]]

Hive queen

2026-05-08T04:03:24Z

Aelanna: Cleanup.

{{Odyssey}}
{{Stub|reason=Summary basically missing, analysis inadequate}}
{{Infobox main|animal
| name = Hive queen
| image = HiveQueen east.png
| description = The birth mother of an insect megahive. Under suitable conditions, several distinct insect hives will merge together and produce a hive queen. The queen quickly grows in size, becoming trapped in her own burrow.
| type = Animal
| type2 = Insectoid
| movespeed = 3.4
| armorblunt = 27
| armorsharp = 22
| vacuum resistance = 1
| min comfortable temperature = -40
| max comfortable temperature = 40
| toxic resistance = 1
| toxic environment resistance = 0.8
| flammability = 0.7
| marketvalue = 2000
| filth rate = 28
| wildness = 0.99
| combatPower = 500
| bodysize = 4.5
| healthscale = 9.8
| hungerrate =
| diet = omnivorous, animal products
| baseleatheramount = 0
| manhuntertame = 1
| manhunter = 1
| trainable = advanced
| meatname = insect meat
| mateMtb =
| lifespan = 75
| specialtrainables = EggSpew
| tradeTags = AnimalInsect
| offspring = 1
| attack1dmg = 30
| attack1type = Cut
| attack1cool = 2.6
| attack1part = head claw
| attack2dmg = 14
| attack2type = Blunt
| attack2cool = 2
| attack2part = head
| attack2chancefactor = 0.2
| isCoastal = false
}}
A '''{{PAGENAME}}''' is an [[animal]] added by the [[Odyssey DLC]].

== Acquisition ==
A {{PAGENAME}} can be found in each underground [[insect lair]] below insect megahives and some infested colony [[landmarks]].

Because the locations of hive queens are well-known, [[Animal husbandry#Taming|taming]] a hive queen is possible by travelling there when your pawn has a taming inspiration, or by receiving inspiration by consuming [[psilocap]]s on-site (Animals Skill level 14 required). But this is still exceptionally dangerous. Normal tank-taming methods for insects can't be applied because her massive single-hit damage and AP often tear off fingers and whole limbs from heavily armored tamers. Even if the queen is injured, as few as 2 hits will chop off a hand if they land in the same place.

For the safety of your pawns, it's recommended to engage the queen with large animals such as [[elephant]]s, [[megasloth]]s, [[thrumbo]]s, or sacrifice some smaller animals to absorb her attacks while you tame. Alternatively, a [[ghoul]],{{AnomalyIcon}} with [[tough]], the [[robust]] gene,{{BiotechIcon}} and [[ghoul plating]],{{AnomalyIcon}} can be used to distract her while being tamed.

If available, proximity to [[psilocap (plant)|psilocap]] plants will also reduce her damage.

With the [[Royalty DLC]] enabled, you can also use pawn with [[psycast]]s{{RoyaltyIcon}} such as [[Stun (psycast)|Stun]] to effectively make your tanker take less damage from the hive queen during the taming process.

== Summary ==
?

Hive queens do not have a [[Rest]] need and thus do not need to sleep. They also have an Egg Spew ability that spawns eggs with [[larva]]e inside. Tamed hive queens will spawn tamed larvae.

This ability has a small, easy to overlook benefit. Spewed eggs give off 50% illumination in a moderate radius and never deteriorate. A fully trained hive queen can spew 1 egg at a targeted point per hour, allowing the player quickly create a free source of light. Some plants, such as [[tinctoria]] and [[fibercorn]], only require 30% light to grow and therefore hive queen eggs can be used to illuminate underground farms to grow these crops without the need to place lamps or torches. The eggs can also be used to light up work stations so a pawn does not receive a penalty from working in the dark.

On empty ground the eggs also spawn with a splash of insect sludge around them, which greatly decreases beauty and move speed. If you use this method, it is advised to immediately after command that these floors be removed. The egg itself has a small beauty penalty, but this can be easily negated by a few beautiful tiles or placing some art nearby. Eggs can also be spawned on deep water, allowing the player to place sources of illumination on some tiles they could otherwise not reach, and would not be usable anyway (Such as in caves with underground pools of water)

== Analysis ==
Hive queens are very dangerous at melee range, yet also have surprisingly high speed due to the insect sludge in the insect lair. Kiting the queen is challenging because all nearby insect sludge, hives, and egg sacs must be cleared. Alternatively, she can be weakened with [[trap]]s, or [[Insect Lair#Cook her with fire|downed by heatstroke]].

Once tamed, the hive queen is an infinite source of [[insect meat]] with her egg spew ability. With a cooldown of 2 hours, this ability gives a theoretical yield of {{#expr:24/2*{{Q|Larva|Meat Yield}}}} insect meat/day.

=== [[Orbit]] {{OdysseyIcon}} ===
As an insectoid, hive queens have 100% [[vacuum resistance]] and go into hypothermic slowdown instead of suffering hypothermia and frostbite from cold. This means they can survive in the vacuum of space without dying.

== Training ==
{{TrainingTable}}

== Health ==
=== Body parts ===
{{Animal Health Table|BeetleLikeWithClaw}}
=== Armor ===
{| class="wikitable"
! Armor
|-
| {{Apparel Protection Chart
| set1name= {{P|Name}} (Sharp) | set1armor1={{P|Armor - Sharp}}
| set2name= {{P|Name}} (Blunt) | set2armor1={{P|Armor - Blunt}}
| set3name= {{P|Name}} (Heat) | set3armor1={{P|Armor - Heat}}
| color= grey, blue, red
}}
|}
{{Pawn Attack Table}}

== Gallery ==
<gallery>
HiveQueen east.png|Facing east
HiveQueen north.png|Facing north
HiveQueen south.png|Facing south
</gallery>
<gallery>
File:Dessicated HiveQueen east.png|Desiccated facing east
File:Dessicated HiveQueen north.png|Desiccated facing north
File:Dessicated HiveQueen south.png|Desiccated facing south
</gallery>

== Version history ==
* [[Odyssey DLC]] Release - Added.

{{Nav|animal}}
[[Category:Animals]]
[[Category:Insectoid]]

Megascarab

2026-05-08T03:54:36Z

Aelanna: /* {{OdysseyIcon}}Space */

{{Infobox main|animal
| name = Megascarab
| image = Megascarab east.png
| description = A large, genetically-engineered beetle. Once the worker caste of an artificial ecosystem of insectoids designed to fight mechanoid invasions, it is now often seen without its deadlier insectoid cousins. Still, its size and hard shell make it dangerous when it attacks. A eusocial creature, it cannot reproduce individually.

| type = Animal
| type2 = Insectoid
| flammability = 0.7
| marketvalue = 100

| armorblunt = 18
| armorsharp = 72

| combatPower = 40
| movespeed = 3.75
| healthscale = 0.4
| bodysize = 0.2
| body = BeetleLike
| diet = omnivorous, animal products
| lifespan = 10
| trainable = Intermediate
| hungerrate = 0.10
| wildness = 0.2
| manhuntertame = 0
| manhunter = 0.5
| meatname = insect meat
| juvenileage = 0.03
| maturityage = 0.4
| toxic resistance = 1
| toxic environment resistance = 0.8
| vacuum resistance = 1
| min comfortable temperature = 0
| max comfortable temperature = 60
| livesin_aridshrubland_polluted = 0.2
| livesin_desert_polluted = 1
| livesin_extremedesert_polluted = 1
| livesin_lavafield_polluted = 0.2

| baseleatheramount = 0


| attack1label = mandibles
| attack1type = Bite
| attack1dmg = 5
| attack1cool = 2
| attack1part = Mouth

| attack2label = head
| attack2type = Blunt
| attack2dmg = 4
| attack2cool = 2
| attack2part = HeadAttackTool
| attack2ensureLinkedBodyPartsGroupAlwaysUsable = true
| attack2chancefactor = 0.1

| devNote = insect
| defName = Megascarab
| label = megascarab
| tradeTags = AnimalInsect
}}
'''Megascarabs''' are a type of [[Insectoid]].

== Acquisition ==
{{PAGENAME}}s can be found in [[Biome#Desert|regular]] and [[Biome#Extreme desert|extreme deserts]], under mountains in [[World generation#Caves|caves]] or [[infestation]]s and inside [[ancient shrine]]s, including inside the [[Ancient cryptosleep casket|caskets]]. They can be tamed by a [[Work #Handle|handler]].

== Summary ==
They are ground beetles of metallic color that posses elytra, a protective shell that provides some [[armor]]. Megascarabs are hazardous to hunt, for if they are injured by a human or a mechanoid, they will turn [[manhunter]] and attack any human or mechanoid on the map they can reach. If slain, they can be butchered for insect meat. Colonists dislike eating any insect meat, but meat-eating animals have no such problem.

{{Insectoid Summary}}

== Analysis ==
=== Combat ===
{{Main|Infestation#Analysis|l1=Infestation}}
Megascarabs are the smallest and fastest of the 3 insectoid types, and will often catch up to colonists and "lock" them into melee. It may be wiser to focus on bigger targets, like [[megaspider]]s, as they are stronger in combat.

[[Melee block]] tactics work well against infestations in general. In an open field, [[kiting]] works well, as even megascarabs are slower than a healthy human.

===Taming===
Megascarabs offer no real niche as a tamed pet, however they ''can'' be tamed. Unlike the larger insects, they can generate non-hostile, and are found naturally in deserts.

=== Space {{OdysseyIcon}} ===
As an insectoid, megascarabs have 100% [[vacuum resistance]] and have go into hypothermic slowdown instead of suffering hypothermia and frostbite from cold. This means they can survive in the vacuum of space without dying.

==Training==
{{TrainingTable}}

== Health ==
=== Body parts ===
{{Animal Health Table|BeetleLike}}
=== Armor ===
{| class="wikitable"
! Armor
|-
| {{Apparel Protection Chart
| set1name= {{P|Name}} (Sharp) | set1armor1={{P|Armor - Sharp}}
| set2name= {{P|Name}} (Blunt) | set2armor1={{P|Armor - Blunt}}
| set3name= {{P|Name}} (Heat) | set3armor1={{P|Armor - Heat}}
| color= grey, blue, red
}}
|}
{{Pawn Attack Table}}

== Gallery ==
<gallery>
Megascarab east.png|Facing east
Megascarab north.png|Facing north
Megascarab south.png|Facing south
</gallery>
<gallery>
Dessicated megascarab east.png|Dessicated facing east
Dessicated Megascarab north.png|Dessicated facing north
Dessicated Megascarab south.png|Dessicated facing south
</gallery>
== Version history ==
* Beta 19/1.0 - All insects main attack cooldowns 2.5 -> 2.9
* Some time between A6 and A13 - Sprite changed.
* 1.3 - Revenge on tame fail decreased from 20% to 10% - revenge on harm increased from 35% to 50% - wildness decreased from 95% to 20%.
* [[Biotech DLC]] release - Now gains [[pollution stimulus]] on [[polluted]] terrain.

<gallery>
File:Megascarab old.png|Texture as of A6
</gallery>

{{Nav|animal}}
[[Category:Animals]]
[[Category:Insectoid]]

Megaspider

2026-05-08T03:53:55Z

Aelanna: /* {{OdysseyIcon}}Space */

{{Infobox main|animal
| name = Megaspider
| image = Megaspider east.png
| description = Not actually a spider, the megaspider is a genetically-engineered giant insectoid the size of a bear. Designed for heavy work and combat, its thick chitinous armor makes it hard to kill, while its long ripper-blades make it deadly at close quarters. It is, however, quite slow in open terrain.
| type = Animal
| type2 = Insectoid
| flammability = 0.7
| marketvalue = 500
| armorblunt = 18
| armorsharp = 27
| combatPower = 150
| movespeed = 3.6
| bodysize = 1.2
| body = BeetleLikeWithClaw
| healthscale = 2.5
| hungerrate = 0.35
| diet = omnivorous, animal products
| baseleatheramount = 0
| wildness = 0.4
| manhuntertame = 0
| manhunter = 0.5
| trainable = advanced
| meatname = insect meat
| lifespan = 6
| juvenileage = 0.03
| maturityage = 0.2
| min comfortable temperature = -40
| max comfortable temperature = 60
| toxic resistance = 1
| toxic environment resistance = 0.8
| vacuum resistance = 1


| attack1label = head claw
| attack1type = Cut
| attack1dmg = 12
| attack1cool = 2.6
| attack1part = HeadClaw

| attack2label = head
| attack2type = Blunt
| attack2dmg = 7
| attack2cool = 2
| attack2part = HeadAttackTool
| attack2ensureLinkedBodyPartsGroupAlwaysUsable = true
| attack2chancefactor = 0.2
| isCoastal = false

| devNote = insect
| defName = Megaspider
| label = megaspider
| tradeTags = AnimalInsect
}}
'''Megaspiders''' are giant, bio-engineered, subterranean invertebrates and the largest and most dangerous of the three [[insectoid]] types.

== Acquisition ==
{{PAGENAME}}s can be found underground in [[World generation#Caves|caves]] and [[infestation]]s or inside [[ancient shrine]]s. They can be tamed by a [[Work #Handle|handler]].

== Summary ==
They are hostile towards any nearby [[colonists]], have plated armor that makes them quite resistant to ranged attack, and can do lethal amounts of damage in close combat. Like all insects, megaspiders only begin spawning in events where colonists come into contact with their underground habitat: In [[World generation#Caves|caves]], when opening an [[ancient danger]], during an [[Events#Infestation|infestation]], or by [[Deep drill|deep drilling]].

{{Insectoid Summary}}

== Analysis ==
=== Combat ===
Megaspiders are slightly slower than [[spelopede]]s and [[megascarab]]s. A common feature of any insectoid swarm is for these smaller, less dangerous creatures to glove the megaspiders' approach, absorbing the fire of your colonists and bogging them down until the big hitters are in range. Fully fit humans can outrun even megascarabs, so the strongest tactic is to hit and run, continually falling back in front of the swarm. If they've infested your base, open your doors and try to lead them out into the open.

[[Melee block]] tactics are very effective, but otherwise you should avoid melee combat. Megaspiders are sturdy and can do a lot of damage very quickly. Do not underestimate how many bullets they take to go down.

=== Taming ===
Wild megaspiders always generate hostile, making them difficult to tame as they will try to attack the animal handler. However, animal interactions during the process will interrupt any attacks. It may be ideal to equip your handler with armor, or to select a handler with a high [[melee]] skill for a higher [[melee dodge chance]] to reduce the risk of harm, though this is not strictly necessary.

Alternatively, a doctor has a small chance to [[bond]] when tending to a wild megaspider, instantly taming them.

As tamed pets, megaspiders offer few advantages over [[bear]]s, [[cougar]]s/[[panther]]s, or [[elephant]]s. Although the latter are all easier to tame, Megaspiders can be tamed en-masse depending on how many were downed during an infestation, require less training because of their lower wildness, and produce less filth than comparable animals.

Colonists who go near a hostile megaspider will flee from it by default, so you may need to adjust your handler's [[hostility response]] setting, or manually order your handler to interact with it.

=== Space {{OdysseyIcon}} ===
As an insectoid, megaspiders have 100% [[vacuum resistance]] and have go into hypothermic slowdown instead of suffering hypothermia and frostbite from cold. This means that they can survive in the vacuum of space without dying.

== Training ==
{{TrainingTable}}

{{OdysseyIcon}} In addition, a {{PAGENAME}} can be trained to perform 'Attack Target': “Command the animal to attack a specific target that its master can see.” (Prerequisite needed: Attack)

== Health ==
=== Body parts ===
{{Animal Health Table|BeetleLikeWithClaw}}
=== Armor ===
{| class="wikitable"
! Armor
|-
| {{Apparel Protection Chart
| set1name= {{P|Name}} (Sharp) | set1armor1={{P|Armor - Sharp}}
| set2name= {{P|Name}} (Blunt) | set2armor1={{P|Armor - Blunt}}
| set3name= {{P|Name}} (Heat) | set3armor1={{P|Armor - Heat}}
| color= grey, blue, red
}}
|}
{{Pawn Attack Table}}

== Gallery ==
<gallery>
Megaspider east.png|Facing east
Megaspider north.png|Facing north
Megaspider south.png|Facing south
</gallery>
<gallery>
Dessicated megaspider east.png|Dessicated facing east
Dessicated Megaspider north.png|Dessicated facing north
Dessicated Megaspider south.png|Dessicated facing south
</gallery>
== Version history ==
* Beta 19/1.0 - All insects main attack cooldowns 2.5 -> 2.9
* [[Version/1.3.3066|1.3.3066]] - Wildness decreased from 0.95 to 0.40, manhunter on tame chance reduced from 40% to 0. Trainability changed from intermediate to advanced, gestation changed from N/A to 6.
* [[Version/1.3.3200|1.3.3200]] - Fix: Remove gestation period stat, since they do not breed.
* [[Biotech DLC]] release - Now gains [[pollution stimulus]] on [[polluted]] terrain.

{{Nav|animal|wide}}
[[Category:Animals]]
[[Category:Insectoid]]

Larva

2026-05-08T03:53:31Z

Aelanna: /* {{OdysseyIcon}}Space */

{{Odyssey}}
{{Stub|reason=Inadequate summary, missing analysis. needs either links to page about wgg sacs (not hive queen) or egg sac mechanics on page or both. also clarify re: description saying is the juveliw form of other insects re maturing}}
{{Infobox main|animal
| name = Larva
| image = Larva east.png
| description = The juvenile form of larger bioengineered insects. Larva maintain and expand hives using an acidic secretion. If provoked, they defend themselves by spewing sludge.
| type = Animal
| type2 = Insectoid
| movespeed = 2
| min comfortable temperature = 0
| max comfortable temperature = 40
| toxic resistance = 1
| toxic environment resistance = 0.8
| flammability = 0.7
| marketvalue = 35
| filth rate = 1
| wildness = 0.20
| combatPower = 25
| bodysize = 0.2
| healthscale = 0.25
| hungerrate = 0.1
| baseleatheramount = 0
| manhunter = 0.5
| manhuntertame = 0
| trainable = intermediate
| meatname = insect meat
| mateMtb =
| lifespan = 4
| specialtrainables = SludgeSpew
| tradeTags = AnimalInsect
| offspring = 1
| attack1dmg = 5
| attack1type = Bite
| attack1cool = 2
| attack1part = mandibles
| attack2dmg = 4
| attack2type = Blunt
| attack2cool = 2
| attack2part = head
| attack2chancefactor = 0.1
| isCoastal = false
}}
A '''larva''' (pl. '''larvae''') is a type of small, sludge-spitting [[insectoid]] added by the [[Odyssey DLC]].

== Acquisition ==
Larvae can be found in [[Landmarks#Stockpile|stockpile]]s. They can also spawn from the destruction{{Check Tag|Otherwise?|If never destroyed by damage, will they ever hatc E.g. after time, when disturbed etc.}} of egg sacs. These egg sacs can be created by the egg spew ability of [[hive queen]]s or so emerge alongside with insect hives from quests, [[infestation]], [[insect lair]] as an egg sac{{Check Tag|Quest only?}} Destroying an egg sac spawned by a tamed hive queen will spawn a tamed larva. These larvae act like tamed animals in all ways.

== Summary ==
{{Image wanted|section=1|reason=Gizmo}}
Emerges when destroying egg sacs. They have intermediate trainability, wildness of 20%, and a trainable sludge attack. The (fairly weak) sludge attack is used randomly until its ability is trained (2/2 levels), at which point it becomes a usable, clickable ability.

It has a range of 7 tiles, and deals acid damage{{Check Tag|What damage & type?}} in a 3x3 area. Leaves acid sludges that act like floors and slows anything but insectoids that walk on it {{Check Tag|By how much?}}
The acid sludge afterward can be removed by using the removing floor order

== Analysis ==
?

=== Space {{OdysseyIcon}} ===
As an insectoid, larva have 100% [[vacuum resistance]] and have go into hypothermic slowdown instead of suffering hypothermia and frostbite from cold. This means they can survive in the vacuum of space without dying.

== Training ==
{{TrainingTable}}

== Health ==
{{Recode|section=1|reason=Larva body type not supported}}
{{Animal Health Table|Larva}}
{{Pawn Attack Table}}

== Gallery ==
<gallery>
Larva east.png|Facing east
Larva north.png|Facing north
Larva south.png|Facing south
</gallery>
<gallery>
File:Dessicated Larva east.png|Desiccated facing east
File:Dessicated Larva north.png|Desiccated facing north
File:Dessicated Larva south.png|Desiccated facing south
</gallery>

== Version history ==
* [[Odyssey DLC]] Release - Added.

{{Nav|animal}}
[[Category:Animals]]
[[Category:Insectoid]]

Larva

2026-05-08T03:53:13Z

Aelanna: /* {{OdysseyIcon}}Space */

{{Odyssey}}
{{Stub|reason=Inadequate summary, missing analysis. needs either links to page about wgg sacs (not hive queen) or egg sac mechanics on page or both. also clarify re: description saying is the juveliw form of other insects re maturing}}
{{Infobox main|animal
| name = Larva
| image = Larva east.png
| description = The juvenile form of larger bioengineered insects. Larva maintain and expand hives using an acidic secretion. If provoked, they defend themselves by spewing sludge.
| type = Animal
| type2 = Insectoid
| movespeed = 2
| min comfortable temperature = 0
| max comfortable temperature = 40
| toxic resistance = 1
| toxic environment resistance = 0.8
| flammability = 0.7
| marketvalue = 35
| filth rate = 1
| wildness = 0.20
| combatPower = 25
| bodysize = 0.2
| healthscale = 0.25
| hungerrate = 0.1
| baseleatheramount = 0
| manhunter = 0.5
| manhuntertame = 0
| trainable = intermediate
| meatname = insect meat
| mateMtb =
| lifespan = 4
| specialtrainables = SludgeSpew
| tradeTags = AnimalInsect
| offspring = 1
| attack1dmg = 5
| attack1type = Bite
| attack1cool = 2
| attack1part = mandibles
| attack2dmg = 4
| attack2type = Blunt
| attack2cool = 2
| attack2part = head
| attack2chancefactor = 0.1
| isCoastal = false
}}
A '''larva''' (pl. '''larvae''') is a type of small, sludge-spitting [[insectoid]] added by the [[Odyssey DLC]].

== Acquisition ==
Larvae can be found in [[Landmarks#Stockpile|stockpile]]s. They can also spawn from the destruction{{Check Tag|Otherwise?|If never destroyed by damage, will they ever hatc E.g. after time, when disturbed etc.}} of egg sacs. These egg sacs can be created by the egg spew ability of [[hive queen]]s or so emerge alongside with insect hives from quests, [[infestation]], [[insect lair]] as an egg sac{{Check Tag|Quest only?}} Destroying an egg sac spawned by a tamed hive queen will spawn a tamed larva. These larvae act like tamed animals in all ways.

== Summary ==
{{Image wanted|section=1|reason=Gizmo}}
Emerges when destroying egg sacs. They have intermediate trainability, wildness of 20%, and a trainable sludge attack. The (fairly weak) sludge attack is used randomly until its ability is trained (2/2 levels), at which point it becomes a usable, clickable ability.

It has a range of 7 tiles, and deals acid damage{{Check Tag|What damage & type?}} in a 3x3 area. Leaves acid sludges that act like floors and slows anything but insectoids that walk on it {{Check Tag|By how much?}}
The acid sludge afterward can be removed by using the removing floor order

== Analysis ==
?

=== {{OdysseyIcon}}Space ===
As an insectoid, larva have 100% [[vacuum resistance]] and have go into hypothermic slowdown instead of suffering hypothermia and frostbite from cold. This means they can survive in the vacuum of space without dying.

== Training ==
{{TrainingTable}}

== Health ==
{{Recode|section=1|reason=Larva body type not supported}}
{{Animal Health Table|Larva}}
{{Pawn Attack Table}}

== Gallery ==
<gallery>
Larva east.png|Facing east
Larva north.png|Facing north
Larva south.png|Facing south
</gallery>
<gallery>
File:Dessicated Larva east.png|Desiccated facing east
File:Dessicated Larva north.png|Desiccated facing north
File:Dessicated Larva south.png|Desiccated facing south
</gallery>

== Version history ==
* [[Odyssey DLC]] Release - Added.

{{Nav|animal}}
[[Category:Animals]]
[[Category:Insectoid]]

Megaspider

2026-05-08T03:51:51Z

Aelanna: Cleaned up addition.

{{Infobox main|animal
| name = Megaspider
| image = Megaspider east.png
| description = Not actually a spider, the megaspider is a genetically-engineered giant insectoid the size of a bear. Designed for heavy work and combat, its thick chitinous armor makes it hard to kill, while its long ripper-blades make it deadly at close quarters. It is, however, quite slow in open terrain.
| type = Animal
| type2 = Insectoid
| flammability = 0.7
| marketvalue = 500
| armorblunt = 18
| armorsharp = 27
| combatPower = 150
| movespeed = 3.6
| bodysize = 1.2
| body = BeetleLikeWithClaw
| healthscale = 2.5
| hungerrate = 0.35
| diet = omnivorous, animal products
| baseleatheramount = 0
| wildness = 0.4
| manhuntertame = 0
| manhunter = 0.5
| trainable = advanced
| meatname = insect meat
| lifespan = 6
| juvenileage = 0.03
| maturityage = 0.2
| min comfortable temperature = -40
| max comfortable temperature = 60
| toxic resistance = 1
| toxic environment resistance = 0.8
| vacuum resistance = 1


| attack1label = head claw
| attack1type = Cut
| attack1dmg = 12
| attack1cool = 2.6
| attack1part = HeadClaw

| attack2label = head
| attack2type = Blunt
| attack2dmg = 7
| attack2cool = 2
| attack2part = HeadAttackTool
| attack2ensureLinkedBodyPartsGroupAlwaysUsable = true
| attack2chancefactor = 0.2
| isCoastal = false

| devNote = insect
| defName = Megaspider
| label = megaspider
| tradeTags = AnimalInsect
}}
'''Megaspiders''' are giant, bio-engineered, subterranean invertebrates and the largest and most dangerous of the three [[insectoid]] types.

== Acquisition ==
{{PAGENAME}}s can be found underground in [[World generation#Caves|caves]] and [[infestation]]s or inside [[ancient shrine]]s. They can be tamed by a [[Work #Handle|handler]].

== Summary ==
They are hostile towards any nearby [[colonists]], have plated armor that makes them quite resistant to ranged attack, and can do lethal amounts of damage in close combat. Like all insects, megaspiders only begin spawning in events where colonists come into contact with their underground habitat: In [[World generation#Caves|caves]], when opening an [[ancient danger]], during an [[Events#Infestation|infestation]], or by [[Deep drill|deep drilling]].

{{Insectoid Summary}}

== Analysis ==
=== Combat ===
Megaspiders are slightly slower than [[spelopede]]s and [[megascarab]]s. A common feature of any insectoid swarm is for these smaller, less dangerous creatures to glove the megaspiders' approach, absorbing the fire of your colonists and bogging them down until the big hitters are in range. Fully fit humans can outrun even megascarabs, so the strongest tactic is to hit and run, continually falling back in front of the swarm. If they've infested your base, open your doors and try to lead them out into the open.

[[Melee block]] tactics are very effective, but otherwise you should avoid melee combat. Megaspiders are sturdy and can do a lot of damage very quickly. Do not underestimate how many bullets they take to go down.

=== Taming ===
Wild megaspiders always generate hostile, making them difficult to tame as they will try to attack the animal handler. However, animal interactions during the process will interrupt any attacks. It may be ideal to equip your handler with armor, or to select a handler with a high [[melee]] skill for a higher [[melee dodge chance]] to reduce the risk of harm, though this is not strictly necessary.

Alternatively, a doctor has a small chance to [[bond]] when tending to a wild megaspider, instantly taming them.

As tamed pets, megaspiders offer few advantages over [[bear]]s, [[cougar]]s/[[panther]]s, or [[elephant]]s. Although the latter are all easier to tame, Megaspiders can be tamed en-masse depending on how many were downed during an infestation, require less training because of their lower wildness, and produce less filth than comparable animals.

Colonists who go near a hostile megaspider will flee from it by default, so you may need to adjust your handler's [[hostility response]] setting, or manually order your handler to interact with it.

=== {{OdysseyIcon}}Space ===
As an insectoid, megaspiders have 100% [[vacuum resistance]] and have go into hypothermic slowdown instead of suffering hypothermia and frostbite from cold. This means that they can survive in the vacuum of space without dying.

== Training ==
{{TrainingTable}}

{{OdysseyIcon}} In addition, a {{PAGENAME}} can be trained to perform 'Attack Target': “Command the animal to attack a specific target that its master can see.” (Prerequisite needed: Attack)

== Health ==
=== Body parts ===
{{Animal Health Table|BeetleLikeWithClaw}}
=== Armor ===
{| class="wikitable"
! Armor
|-
| {{Apparel Protection Chart
| set1name= {{P|Name}} (Sharp) | set1armor1={{P|Armor - Sharp}}
| set2name= {{P|Name}} (Blunt) | set2armor1={{P|Armor - Blunt}}
| set3name= {{P|Name}} (Heat) | set3armor1={{P|Armor - Heat}}
| color= grey, blue, red
}}
|}
{{Pawn Attack Table}}

== Gallery ==
<gallery>
Megaspider east.png|Facing east
Megaspider north.png|Facing north
Megaspider south.png|Facing south
</gallery>
<gallery>
Dessicated megaspider east.png|Dessicated facing east
Dessicated Megaspider north.png|Dessicated facing north
Dessicated Megaspider south.png|Dessicated facing south
</gallery>
== Version history ==
* Beta 19/1.0 - All insects main attack cooldowns 2.5 -> 2.9
* [[Version/1.3.3066|1.3.3066]] - Wildness decreased from 0.95 to 0.40, manhunter on tame chance reduced from 40% to 0. Trainability changed from intermediate to advanced, gestation changed from N/A to 6.
* [[Version/1.3.3200|1.3.3200]] - Fix: Remove gestation period stat, since they do not breed.
* [[Biotech DLC]] release - Now gains [[pollution stimulus]] on [[polluted]] terrain.

{{Nav|animal|wide}}
[[Category:Animals]]
[[Category:Insectoid]]

Lore

2026-05-07T14:59:23Z

Aelanna: Added note explaining where the celestial body art came from.

{{Spoiler}}
{{Stub|reason=General. Also Ideology [[Ruins]], shared info on all game-host rimworlds, generated ideology and quest descriptions, archotech, and the starting scenarios. Also Horax. Known timeline. Boomshrooms->Boomaniamls also odyssey generally, military info on power armor and xenotypes, datacards on tvs}}
The '''Lore''' of RimWorld is limited and is mostly interpreted from information provided in game. However several documents have been published outlining the lore for new players. Keep in mind that the lore is being updated and that later releases retcon old ones. Old lore is only presented here as a matter of interest.

<div style="margin-bottom: .5em; float: none; width: auto;" class="toclimit-3"}}>__TOC__</div>

== Assorted Lore ==
This section includes lore from assorted sources, including [[backstories]], that is not included in the Revival Briefing.
=== Named Places ===
{{Recode|section=1|reason=Add a toggle to hide all the places that are just "Blah - exists" or "Blah = this planet type" - alternatively reformatting such that they don't get their own row without being more interesting}}
==== Worlds ====
{| {{STDT|sortable}}
|-
! Name !! Planet Type !! Description
|- id="Ticonderoga"
! Ticonderoga
| Unknown
| A planet populated with tribals and mountains.<ref name="Jon">Backstory of [[List of Player-created Pawns#Jonathan Craig|Jonathan 'Jon' Craig]]</ref>
|- id="Aracena VI"
! Aracena VI
| Feudalworld<ref name="Book descriptions">RulePacks_Book_Descriptions.xml - World names book description generation strings</ref>
| A planet with the Novo Mosteiro dos Jerónimos monastery on it, at least 2 continents and alcohol prohibition leading to the rise of bootleggers.<ref name="Oahnip">Backstory of [[List of Player-created Pawns#Vitor Pinhao|Vitor 'Oahnip' Pinhao]]</ref>
|- id="Rural Pen’The"
! Rural Pen’The
| Unknown
| A lucrative spice mining colony.<ref>Backstory of [[List of Player-created Pawns#Benn Tannen|Benn 'Ben' Tannen]]</ref>
----
'''''Out of Universe:''' This is likely a reference to Rura Penthe, the penal colony from 1954 Disney film "20,000 Leagues Under the Sea" or the Klingon penal planetoid named after it in the Star Trek universe.''
|- id="Khalderia"
! Khalderia
| [[#Midworld|Midworld]]<ref name="Book descriptions"/>
| A world with towering forests and fern farmers. The seedy underworld of racing, illegal speeder racing, zipping in and out of the massive canopies and gorgeous vistas of the world occurred here.<ref>Backstory of [[List of Player-created Pawns#Russell Shackleford|Russell 'Rusty' Shackleford]]</ref>
|- id="Earth"
! Earth
| [[#Ruinworld|Ruinworld]]<ref name="Book descriptions"/>
| A planet, from which all known naturally evolved life originated. Humanity's diaspora from Earth occurred 3400 years before the Cryptosleep Debriefing, or in the year 2100 CE assuming the Debriefing is contemporaneous with the beginning of the game in 5500.<ref name="Cryptosleep Revival Briefing">[[#Cryptosleep Revival Briefing|Cryptosleep Revival Briefing]]</ref>
|- id="Euterpe"
! Euterpe
| [[#Urbworld|Urbworld]]<ref name="Book descriptions"/>
| A planet that hosted people awakening from long periods of cryptosleep. Also had an Ordo Historia archive on-world.<ref name="Cryptosleep Revival Briefing"/>
----
'''''Out of Universe:''' Euterpe was one of the Muses in Greek mythology, presiding over music, and later, lyric poetry. 27 Euterpe is also the name of an asteroid in the Inner Asteroid Belt, and one of the brightest asteroids in the night sky''
|- id="Sorne"
! Sorne
| [[#Animal world|Animal world]]<ref name="Book descriptions"/>
| The original homeworld of the [[insectoid]]s, before being captured, genetically modified, and vat-grown by interstellar entrepreneurs for use as weapons, and exported to other worlds by parties unknown. As all seemingly-alien life is claimed to have originated on Earth, it is possible that the original pre-weaponization Sorne Geneline evolved from Earth life on the planet, or were already genetically engineered for some reason before being modified again.<ref name="Insectoid Faction Description">[[Insectoid]] Faction Description</ref>
|- id="Carthago"
! Carthago
| [[#Deathworld|Deathworld]]
| A deathworld planet.<ref name="Book descriptions"/>
----
'''''Out of Universe:''' This is likely a reference to Carthage, an ancient empire that fought the Roman Republic during the Punic Wars. The Romans famously destroyed Carthage and apocryphally sowed the land with salt to prevent habitation. The specific form of the name harkens to the phrase "Carthago delenda est" a phrase used by Cato the Elder to advocate for the destruction of Carthage. Both are fitting references for a deathworld.''
|- id="Rayth"
! Rayth
| [[#Deathworld|Deathworld]]
| A deathworld planet.<ref name="Book descriptions"/>
|- id="Spectra"
! Spectra
| [[#Deathworld|Deathworld]]
| A deathworld planet.<ref name="Book descriptions"/>
|- id="Grimcore"
! Grimcore
| [[#Deathworld|Deathworld]]
| A deathworld planet.<ref name="Book descriptions"/>
|- id="JNovahex"
! JNovahex{{Sic}}
| [[#Deathworld|Deathworld]]
| A deathworld planet.<ref name="Book descriptions"/>
|- id="Amen-Ti"
! Amen-Ti
| [[#Glitterworld|Glitterworld]]<ref name="Book descriptions"/><ref name="Ideology Places"/>
| A glitterworld planet. Capital of the Star Empire, which maintains a military called Starforce which trains its cadets at the Star Academy. Fields Manned Fighters launched from Carrier Ships, and has been involved in at least 3 wars against "more advanced aggressor cultures".<ref name="Nerhesi">Backstory of [[List of Player-created Pawns#Sam Wissa|Sam 'Nerhesi' Wissa]]</ref> Relationship with [[#Rogia|Rogia]], another glitterworld which also hosts a "Starforce", is unknown. It is possible that they are part of the same Star Empire.
|- id="Kalthas IV"
! Kalthas IV
| [[#Glitterworld|Glitterworld]]<ref name="Book descriptions"/>
| A planet with elite training school for socially gifted students on it.<ref name="Darkeye">Backstory of [[List of Player-created Pawns#Matis Saro|Matis 'Darkeye' Saro]]</ref>
|- id="Utmaior"
! Utmaior
| [[#Glitterworld|Glitterworld]]
| A glitterworld planet.<ref name="Book descriptions"/> Presumably the location of [[#Utmaior Academy|Utmaior Academy]].
|- id="Kenerella"
! Kenerella
| [[#Glitterworld|Glitterworld]]
| A glitterworld planet.<ref name="Book descriptions"/>
|- id="Caspian"
! Caspian
| [[#Glitterworld|Glitterworld]]
| A glitterworld planet.<ref name="Book descriptions"/> Presumably the location of the [[#Caspian School of Engineering|Caspian School of Engineering]].
|- id="Dedchenko"
! Dedchenko
| [[#Iceworld|Iceworld]]<ref name="Book descriptions"/>
| An iceworld planet.
----
'''''Out of Universe:''' Likely a reference to the Vanch-Yakh Glacier, a large glacier in Tajikistan previously known as the Fedchenko Glacier prior to 2023.
|- id="Baltoro"
! Baltoro
| [[#Iceworld|Iceworld]]
| An iceworld planet.<ref name="Book descriptions"/>
----
'''''Out of Universe:''' Likely a reference to Baltoro Glacier in Pakistan, one of the longest glaciers outside the polar regions.''
|- id="Furtwale"
! Furtwale
| [[#Iceworld|Iceworld]]
| An iceworld planet.<ref name="Book descriptions"/>
----
'''''Out of Universe:''' Given the naming convention used for other Iceworlds, may be a reference to Furtwängler Glacier in Tanzania.''
|- id="Jaqua"
! Jaqua
| [[#Iceworld|Iceworld]]
| An iceworld planet.<ref name="Book descriptions"/>
|- id="Christensen"
! Christensen
| [[#Iceworld|Iceworld]]
| An iceworld planet.<ref name="Book descriptions"/>
----
'''''Out of Universe:''' Likely a reference to Christensen Glacier in South Georgia, a part of the British Overseas Territory of South Georgia and the South Sandwich Islands.''
|- id="Barnes"
! Barnes
| [[#Iceworld|Iceworld]]
| An iceworld planet.<ref name="Book descriptions"/>
----
'''''Out of Universe:''' Likely a reference to Barnes Glacier in Antarctica.''
|- id="La Grand"
! La Grand
| [[#Rimworld|Rimworld]]
| A rimworld planet.<ref name="Book descriptions"/>
|- id="Dalles"
! Dalles
| [[#Rimworld|Rimworld]]
| A rimworld planet.<ref name="Book descriptions"/>
|- id="Twig Falls"
! Twig Falls
| [[#Rimworld|Rimworld]]
| A rimworld planet.<ref name="Book descriptions"/>
|- id="Old Boise"
! Old Boise
| [[#Rimworld|Rimworld]]
| A rimworld planet.<ref name="Book descriptions"/>
|- id="Devil's Gate"
! Devil's Gate
| [[#Rimworld|Rimworld]]
| A rimworld planet.<ref name="Book descriptions"/>
|- id="Laramiere"
! Laramiere
| [[#Rimworld|Rimworld]]
| A rimworld planet.<ref name="Book descriptions"/>
|- id="Corliss"
! Corliss
| [[#Steamworld|Steamworld]]
| A steamworld planet.<ref name="Book descriptions"/>
|- id="Borassic"
! Borassic
| [[#Steamworld|Steamworld]]
| A steamworld planet.<ref name="Book descriptions"/>
|- id="Savery II"
! Savery II
| [[#Steamworld|Steamworld]]
| A steamworld planet.<ref name="Book descriptions"/>
|- id="Heron"
! Heron
| [[#Steamworld|Steamworld]]
| A steamworld planet.<ref name="Book descriptions"/>
|- id="Malmesburi"
! Malmesburi
| [[#Steamworld|Steamworld]]
| A steamworld planet.<ref name="Book descriptions"/>
----
'''''Out of Universe:''' Possibly a reference to Malmesbury, an English town that was the site of early textile industrialization.''
|- id="Architonnerre"
! Architonnerre
| [[#Steamworld|Steamworld]]
| A steamworld planet.<ref name="Book descriptions"/>
----
'''''Out of Universe:''' Likely a direct reference to the Architonnerre, a steam-powered cannon described in the papers of Leonardo da Vinci but that he attributed to Archimedes.
|- id="Escapement"
! Escapement
| [[#Steamworld|Steamworld]]
| A steamworld planet.<ref name="Book descriptions"/>
----
'''''Out of Universe:''' Escapements are a type of mechanic linkage used in analogue watches and clocks, a fitting reference given the association between steampunk and clockwork''
|- id="Xaroh"
! Xaroh
| [[#Transcendent world|Transcendent world]]
| A transcendent world.<ref name="Book descriptions"/>
|- id="Immanence VI"
! Immanence VI
| [[#Transcendent world|Transcendent world]]
| A transcendent world.<ref name="Book descriptions"/>
|- id="Qabba"
! Qabba
| [[#Transcendent world|Transcendent world]]
| A transcendent world.<ref name="Book descriptions"/>
|- id="Einsof"
! Einsof
| [[#Transcendent world|Transcendent world]]
| A transcendent world.<ref name="Book descriptions"/>
|- id="Mitvo"
! Mitvo
| [[#Transcendent world|Transcendent world]]
| A transcendent world.<ref name="Book descriptions"/>
|- id="Samydi"
! Samydi
| [[#Transcendent world|Transcendent world]]
| A transcendent world.<ref name="Book descriptions"/>
|- id="Samsarr"
! Samsarr
| [[#Transcendent world|Transcendent world]]
| A transcendent world.<ref name="Book descriptions"/>
|- id="Ceti V"
! Ceti V
| [[#Glassworld|Glassworld]]<ref name="Book descriptions"/>
| A planet with an assassin's guild.<ref name="Darkeye"/>
|- id="Thebes XIV"
! Thebes XIV
| [[#Glassworld|Glassworld]]
| A glassworld planet.<ref name="Book descriptions"/>
|- id="Naga"
! Naga
| [[#Glassworld|Glassworld]]
| A glassworld planet.<ref name="Book descriptions"/>
|- id="Merv"
! Merv
| [[#Glassworld|Glassworld]]
| A glassworld planet.<ref name="Book descriptions"/>
----
'''''Out of Universe:''' Given the identical pronunciation and link to weapons of mass destruction, likely a reference to MIRVs, or multiple independently targetable reentry vehicle, a payload for ballistic missiles in which several warheads capable to each targeting a different location are carried by one missile. The concept is almost invariably associated with intercontinental ballistic missiles carrying thermonuclear warheads,''
|- id="Perse"
! Perse
| [[#Glassworld|Glassworld]]
| A glassworld planet.<ref name="Book descriptions"/>
|- id="Shechem"
! Shechem
| [[#Glassworld|Glassworld]]
| A glassworld planet.<ref name="Book descriptions"/>
----
'''''Out of Universe:''' Shechem was the name of an ancient Canaanite city. The relevance of this is unknown.''
|- id="Yelhazor"
! Yelhazor
| [[#Glassworld|Glassworld]]
| A glassworld planet.<ref name="Book descriptions"/>
----
'''''Out of Universe:''' Tel Hazor is an archeological site located in modern Israel. While the names do not match, the similarity of the names, the proximity of the Y & T keys, and the references to [[#Shechem|Shechem]] as a similar site in the same source makes the similarity bear noting.''
|- id="Avenna"
! Avenna
| [[#Urbworld|Urbworld]]
| An urbworld planet.<ref name="Book descriptions"/>
|- id="Essalon"
! Essalon
| [[#Urbworld|Urbworld]]
| An urbworld planet.<ref name="Book descriptions"/>
|- id=Enike"
! Enike
| [[#Urbworld|Urbworld]]
| An urbworld planet.<ref name="Book descriptions"/>
|- id="Adocia"
! Adocia
| [[#Urbworld|Urbworld]]
| An urbworld planet.<ref name="Book descriptions"/>
|- id="N'toch"
! N'toch
| [[#Urbworld|Urbworld]]
| An urbworld planet.<ref name="Book descriptions"/>
|- id=Barca"
! Barca
| [[#Urbworld|Urbworld]]
| An urbworld planet.<ref name="Book descriptions"/>
|- id="Puobell"
! Puobell
| [[#Trashworld|Trashworld]]
| A trashworld.<ref name="Book descriptions"/>
----
'''''Out of Universe:''' Likely a reference to "poubelle", a French word meaning garbage can.''
|- id="Deni IX"
! Deni IX
| [[#Trashworld|Trashworld]]
| A trashworld.<ref name="Book descriptions"/>
|- id="Garbsh"
! Garbsh
| [[#Trashworld|Trashworld]]
| A trashworld.<ref name="Book descriptions"/>
----
'''''Out of Universe:''' A portmanteau of "'''Garb'''age" and "Tra'''sh'''".''
|- id="Tra'age"
! Tra'age
| [[#Trashworld|Trashworld]]
| A trashworld.<ref name="Book descriptions"/>
----
'''''Out of Universe:''' A portmanteau of "'''Tra'''sh" and "Garb'''age'''".''
|- id="Reepsyk"
! Reepsyk
| [[#Trashworld|Trashworld]]
| A trashworld.<ref name="Book descriptions"/>
----
'''''Out of Universe:''' May be a reference to Resyk of Judge Dredd comics, itself a euphemistic reference to the "recycling" of biomatter including human corpses.''
|- id="Mystras"
! Mystras
| [[#Trashworld|Trashworld]]
| A trashworld.<ref name="Book descriptions"/>
|- id="Destria"
! Destria
| Shellworld
| A shellworld.<ref name="Book descriptions"/> Given the name, presumably involved in the [[#Inner Destrian War|Inner Destrian War]] as either a battlefield or belligerent.<ref name="Stonejaw">Backstory of [[List of Player-created Pawns#Chad Walcenville|Chad 'Stonejaw' Walcenville]]</ref>
|- id="Trophic"
! Trophic
| Shellworld
| A shellworld.<ref name="Book descriptions"/>
|- id="Matrio"
! Matrio
| Shellworld
| A shellworld.<ref name="Book descriptions"/>
|- id="Samen"
! Samen
| Shellworld
| A shellworld.<ref name="Book descriptions"/>
|- id="Xinthia"
! Xinthia
| Shellworld
| A shellworld.<ref name="Book descriptions"/>
|- id="Ferbine"
! Ferbine
| Shellworld
| A shellworld.<ref name="Book descriptions"/>
|- id="Callos IX"
! Callos IX
| [[#Deadworld|Deadworld]]
| A deadworld.<ref name="Book descriptions"/> Presumably the site of the [[#Callos IX incident|Callos IX incident]],<ref name="Doc"/> which may be the reason it is now a [[#Deadworld|deadworld]].
|- id="Haspia"
! Haspia
| [[#Deadworld|Deadworld]]
| A deadworld.<ref name="Book descriptions"/> See [[#Haspian monk|Haspian monk]].
|- id="Gost IV"
! Gost IV
| [[#Deadworld|Deadworld]]
| A deadworld.<ref name="Book descriptions"/>
----
'''''Out of Universe:''' GOST 4 is a Russian protection rating for ballistic armor. It is unknown if this is relevant''
|- id="Berimund"
! Berimund
| [[#Deadworld|Deadworld]]
| A deadworld.<ref name="Book descriptions"/>
|- id="Ardar"
! Ardar
| [[#Deadworld|Deadworld]]
| A deadworld.<ref name="Book descriptions"/>
|- id="Kremhild"
! Kremhild
| [[#Deadworld|Deadworld]]
| A deadworld.<ref name="Book descriptions"/>
|- id="Melisandz"
! Melisandz
| [[#Deadworld|Deadworld]]
| A deadworld.<ref name="Book descriptions"/>
|- id="Irithir"
! Irithir
| [[#Indworld|Indworld]]<ref name="Book descriptions"/>
| A trading hub planet.<ref>Backstory of [[List of Player-created Pawns#William Gregory-Heap|William Gregory-Heap]]</ref>
|- id="New China"
! New China
| [[#Indworld|Indworld]]<ref name="Book descriptions"/>
| Planet.<ref>Backstory of [[List of Player-created Pawns#Yutong Li|Yutong 'Li' Li]]</ref>
|- id="Hudders"
! Hudders
| [[#Indworld|Indworld]]
| An indworld.<ref name="Book descriptions"/>
|- id="Iver"
! Iver
| [[#Indworld|Indworld]]
| An indworld.<ref name="Book descriptions"/>
|- id="Achesta"
! Achesta
| [[#Indworld|Indworld]]
| An indworld.<ref name="Book descriptions"/>
|- id="Oods"
! Oods
| [[#Indworld|Indworld]]
| An indworld.<ref name="Book descriptions"/>
|- id="Iladelf"
! Iladelf
| [[#Indworld|Indworld]]
| An indworld.<ref name="Book descriptions"/>
|- id="Pichu"
! Pichu
| [[#Ruinworld|Ruinworld]]
| A ruinworld.<ref name="Book descriptions"/>
----
'''''Out of Universe:''' Most of the ruinworlds in this source are references to ancient, ruined cities. This is most likely a reference to Machu Pichu, the famous ruined Incan citadel.''
|- id="Perdida"
! Perdida
| [[#Ruinworld|Ruinworld]]
| A ruinworld.<ref name="Book descriptions"/>
----
'''''Out of Universe:''' Most of the ruinworlds in this source are references to ancient, ruined cities. Perdida is Spanish for lost, but given the theme in the naming of ruinworlds, it likely specifically a reference to Ciudad Perdida, a ruined pre-Columbian city near Santa Marta, Colombia''
|- id="Hisarlik"
! Hisarlik
| [[#Ruinworld|Ruinworld]]
| A ruinworld.<ref name="Book descriptions"/>
----
'''''Out of Universe:''' Most of the ruinworlds in this source are references to ancient, ruined cities. Hisarlık is the modern-day location of the ruins of Troy, the city famously, and possibly apocryphally, besieged by the Greeks during the Trojan War.''
|- id="Helike"
! Helike
| [[#Ruinworld|Ruinworld]]
| A ruinworld.<ref name="Book descriptions"/>
----
'''''Out of Universe:''' Most of the ruinworlds in this source are references to ancient, ruined cities. Helike is the name of ancient Greek city-state, destroyed by a tsunami, and whose ruins were rediscovered in 2001.''
|- id="Cerospor"
! Cerospor
| [[#Toxic world|Toxic world]]
| A toxic world.<ref name="Book descriptions"/>
----
'''''Out of Universe:''' Cerospor is also a brand name used for a form of antibiotics.''
|- id="Scylla"
! Scylla
| [[#Toxicworld|Toxicworld]]
| A toxicworld.<ref name="Book descriptions"/>
----
'''''Out of Universe:''' Scylla is a character from Greek myth, originally a naiad but turned into a monster when poison was poured into the water in which she was bathing.''
|- id="Thylacine"
! Thylacine
| [[#Animal world|Animal world]]
| An animal world.<ref name="Book descriptions"/>
----
'''''Out of Universe:''' Thylacines, also known as the Tasmanian tiger or Tasmanian wolf, are a type of extinct carnivorous marsupial that was native to Australia and Papua New Guinea. Given the resurrection of other extinct species by genetic engineering, this may indicate that this planet was used for this purpose and that is why it was kept an animal world.''
|- id="Jiai"
! Jiai
| [[#Animal world|Animal world]]
| An animal world.<ref name="Book descriptions"/>
----
'''''Out of Universe:''' Jiai is a transliteration of 慈愛, the Japanese word for Charity or Compassion. The relevance of this, if any, is unknown.''{{Check Tag|Japanese language check|Someone with real knowledge of the language should check this.}}
|- id="Aukton"
! Aukton
| [[#Animal world|Animal world]]
| An animal world.<ref name="Book descriptions"/>
|- id="Steller's World"
! Steller's World
| [[#Animal world|Animal world]]
| An animal world.<ref name="Book descriptions"/>
|- id="Sophiamunda"
! Sophiamunda {{RoyaltyIcon}}
| [[#Glitterworld|Glitterworld]]<ref name="Book descriptions"/><ref name="Royalty Places">Royalty Places.xml</ref>
| A techno-feudal world with castles and palaces. Native Sophians work as knights, squires, dukes, maids, and swordsmiths. Revolutionists and their rebels sometimes attack those living there. People carry [[warhammer]]s and [[persona plasmasword]]s as personal weapons. [[Orbital mech cluster targeter]]s, bio-engineered plagues, and armies of fallen knights have been deployed there. Described in code-comments as ''Sophiamunda is the shattered empire's home world.'' Generally the canonicity of such comments is unclear, though in this instance it directly agrees with other sources. <ref name="Royalty Places"/> This information listed here is limited to that listed in the places file, for more information see: [[#Empire|Empire]].
|- id="Oubanyen"
! Oubanyen
| Jungle world<ref name="Ideology Places">Ideology Places.xml</ref><br>/[[#Dino-world|Dino-world]]<ref name="Book descriptions"/>
| A steamy jungle world with tree-top villages, hill-top ziggurats, city temples, and shaman caves. Native Oubanyeni work as Shamans, hunters, fishers, gatherers and [[goat]]herds. Tree-harvesters and their henchmen sometimes attack those living there. People carry [[pila]] and [[ikwa]] as personal weapons. Lethal [[psychic drone]]s and neurotoxin bombs have been deployed there. Described in code-comments as ''A steamy world of wet jungles, strange tribes with psychic powers'', however the canonicity of such comments is unclear.<ref name="Ideology Places"/>
|- id="Chelis"
! Chelis
| Arid world<ref name="Ideology Places"/><br>/Medieval world<ref name="Book descriptions"/>
| An arid world with moisture farms, parch-towns, water centres and high lifehalls. Native Chelisi work as water gatherers, lizardskinners, oasis seekers, cactus gatherers and scav-herders. Chiefs and their sand-warriors sometimes attack those living there. People carry sand-arrows and cactus-clubs as personal weapons. Archotech-induced sandstorms and spikelizard stampedes have been deployed there. Described in code-comments as ''An arid world of moisture-farming tribes'', however the canonicity of such comments is unclear. <ref name="Ideology Places"/>
|- id="Ilwaba"
! Ilwaba
| [[#Ruinworld|Ruinworld]]<ref name="Book descriptions"/><ref name="Ideology Places"/>
| A regrown ruin-world with skyscraper villages, highway trade-posts, blast-land oases, and houses of regrowth. Native Ilwabans work as crete-farmers, path-makers, artifact hunters, tunnelwalkers, and artifact restorers. Crypto-leaders and their crypto-soldiers sometimes attack those living there. People carry scrap-swords and jag-dagger as personal weapons. Dug-up nukes and ancient poison bombs have been deployed there. Described in code-comments as ''A regrown deathworld where tribes live among overgrown cities'', however the canonicity of such comments is unclear. <ref name="Ideology Places"/>
|- id="Boccocarro"
! Boccocarro
| Shell-world<ref name="Book descriptions"/><ref name="Ideology Places"/>
| A cavernous shell-world with surface tunnels, fungus caverns, drip-wells, and speech-halls. Native Boccin work as miners, fungus growers, surface scavengers, community cooks, and frog-hunters. Mine hypervisor and their abyssal marines sometimes attack those living there. People carry pickaxes and hydraulic crossbows as personal weapons. Seismic quake-generation devices and blackpowder bombs have been deployed there. Described in code-comments as ''A subterranean world with vast caverns and a baked, inhospitable surface. Many factious but isolated city-states'', however the canonicity of such comments is unclear. <ref name="Ideology Places"/>
|- id="Nuchadus"
! Nuchadus
| Volcano-world<ref name="Ideology Places"/><br>/Feudalworld<ref name="Book descriptions"/>
| A dim volcano-world with basalt islands, caldera laketowns, dirigible villages, and thermal fortresses. Native nuchadeans work as seismologists, lava-snail farmers, tank-tread repairers, and airborne scouts. Lava lords and their stygian soldiers sometimes attack those living there. People carry obsidian daggers and harpoon rifles as personal weapons. Chem-warfare bombs and archotech-induced volcano eruptions have been deployed there. Described in code-comments as ''A chaotic volcanic world far from the sun, covered with lava flows and black sand dunes. There are nomads and movable cities'', however the canonicity of such comments is unclear. <ref name="Ideology Places"/>
|- id="Zoutera"
! Zoutera
| [[#Dino-world|Dino-world]]<ref name="Ideology Places"/><ref name="Book descriptions"/>/Animal world<ref name="Book descriptions"/>
| A grassy dino-world with trading outposts, trent villages, mammoth burial grounds, and hill-top forts. Native Zoutin work as dino-riders, [[muffalo]]-herders, hunters, and toughleather makers. Tusk-kings and their tusk-warriors sometimes attack those living there. People carry bamboo staves and hunt-bomb arrows as personal weapons. Fertilizer bombs and stampeding herds of ankylosaurs, blue mammoths, and novoraptors have been deployed there. Described in code-comments as ''A grassy planet populated by megafauna'', however the canonicity of such comments is unclear. <ref name="Ideology Places"/>
|- id="Wavia"
! Wavia
| Oceanic world<ref name="Book descriptions"/><ref name="Ideology Places"/>
| An oceanic planet with trading atolls, floating villages, seaweed refineries, and capitol bridges. Native Wavians work as fishers, pearl divers, sail makers, captains, and sea-grass gatherers. Whaler admirals and their whaler-marines sometimes attack those living there. People carry harpoons and barbed nets as personal weapons. High-yield torpedoes and baited deep-kraken and Wavian leviathans have been deployed there. Described in code-comments as ''A water world dotted with atolls and floating seaweed'', however the canonicity of such comments is unclear. <ref name="Ideology Places"/>
----
'''''Out of Universe:''' Likely a reference to the 1995 post-apocalyptic action film 'Waterworld'.''
|- id="Bagua 5"
! Bagua 5
| Junkyard planet<ref name="Ideology Places"/><br>/Trashworld<ref name="Book descriptions"/>
| A junkyard planet with fortified scrapyards, rainwater processing plants, scrap-towns and trader spaceports. Native Bagucinquans work as scavengers, traders, tinkerers, guards, and scrappers. Junk lords and their metal-heads sometimes attack those living there. People carry pipe rifles and scrap-swords as personal weapons. Salvaged nukes and rust viruses have been deployed there. Described in code-comments as ''A junkyard planet of crashed ships, broken machinery, scavengers and traders'', however the canonicity of such comments is unclear. <ref name="Ideology Places"/>
----
'''''Out of Universe:''' "Bagua" is the name of eight symbols used in Taoist cosmology and of a province of Peru - it is unclear if either etymology of the name is correct. The "-cinquan" suffix of the demonym simply comes from the French term for five - the inhabitants are literally "Bagua-5-ans".''
|- id="Rhydell"
! Rhydell{{IdeologyIcon}}
| Forest moon<ref name="Ideology Places"/>/[[#Animal world|Animal world]]<ref name="Book descriptions"/>
| A savage forest moon with converted dropships, low-shielded encampments, communication centers, and armored habitats. Native Rhydellians work as frontier botanists, trophy hunters, medics, camp cooks, and biolab engineers. Deepcorp executives and their deepcorp enforcers sometimes attack those living there. People carry [[sniper rifle]]s and machetes as personal weapons. Plant-derived neurotoxin gas and orbital laser strikes have been deployed there. Described in code-comments as ''A forest moon filled valuable flora and with dangerous predators'', however the canonicity of such comments is unclear.<ref name="Ideology Places"/> Its secondary description as an animal world is confusing given that people apparently are living on the world, however it may indicate that it was simply an animal world in the past or that that full colonisation efforts have not begun.
|- id="Iwamura"
! Iwamura{{IdeologyIcon}}
| Stony asteroid<ref name="Ideology Places"/><ref name="Book descriptions"/>
| A stony asteroid with market capsules, warehouse capsules, docking piers, and station bridges. Native Iwamurian work as life-support engineers, merchants, flight controllers, zero-g athletes, and radio hosts. Mega-corp CEOs and their rent-a-cops sometimes attack those living there. People carry [[charge rifle]]s and welding torches as personal weapons. Aerosolized toxins, life-support sabotage viruses and EMP strikes to the life support systems have been deployed there. Described in code-comments as ''Iwamura is a stony asteroid housing a large trading hub'', however the canonicity of such comments is unclear. <ref name="Ideology Places"/>
|- id="Novaroma"
! Novaroma{{IdeologyIcon}}{{BiotechIcon}}
| Planetoid/[[#Coreworld|Coreworld]]<ref name="Book descriptions"/>
| A planetoid with ministries of permits, gated suburbs, over-cities, undercities, and megacity overhalls. Native novaromans work as clerks, officials, food couriers, taxi drivers, and retail workers. High-underlords and their undertroops sometimes attack those living there. People carry [[revolver]]s and [[knife|knives]] as personal weapons. Seismic quake-generation devices, cluster bombs, and nuclear suitcase-bombs have been deployed there. Described in code-comments as ''[...] a planetoid covered in a vast city, ruled by a bureaucracy'', however the canonicity of such comments is unclear. <ref name="Ideology Places"/> The line of [[highmates]] found on the colony's rimworld fit the fashions of Novaroma.<ref>[[Highmate]] [[xenotype]] description</ref>
----
'''''Out of Universe:''' The name translates to New Rome in Latin.''
|- id="Filson"
! Filson
| Farm-world<ref name="Ideology Places"/><br>/Feudalworld<ref name="Book descriptions"/><br>/Rimworld<ref name="Book descriptions"/>
| A rural farm-world with fertilizer processing plants, mega-granaries, water-bore sites, and town halls. Native Filsoners work as farm hands, fruit pickers, transport drivers, school teachers, and soil engineers. Landowners and their militia sometimes attack those living there. People carry rifles and scythes as personal weapons. Fertilizer bombs, weaponized pesticide sprays and space lenses have been deployed there. Described in code-comments as ''[...] a rural planet of vast agriculture plots and territorial landowners'', however the canonicity of such comments is unclear. <ref name="Ideology Places"/>
|- id="Creticon"
! Creticon{{IdeologyIcon}}
| [[#Deathworld|Deathworld]]<ref name="Book descriptions"/><ref name="Ideology Places"/>
| A blasted death-world with bunkers, caverns, ice-shelters, and director's bunkers. Native Creticonians work as water-recycler repairers, algae farmers, doctors, teachers, militia commanders, and shuttle pilots. Warlords and their mercenaries sometimes attack those living there. People carry [[autopistol]]s and [[LMG]]s as personal weapons. Shoulder-mounted nuclear missiles, orbital bombardments, chemical bombs, and hacked mechanoids have been deployed there. Described in code-comments as ''[...] a high-tech death-world where everyone lives in bunkers'', however the canonicity of such comments is unclear. <ref name="Ideology Places"/>
|- id="Yttak"
! Yttak{{IdeologyIcon}}{{BiotechIcon}}
| Ice-moon<ref name="Ideology Places"/><br>/Icy planet<ref name="Yttakin pirates"/><br>/Iceworld<ref name="Book descriptions"/>/[[#Prison planet|Prison world]]<ref name="Book descriptions"/>
| An ice-moon prison with meal halls, guard barracks, detention centers, and warden's office complex. Native Yttaki are detainees and escapees, or work as guards, maintenance workers, and transport drivers. Prison wardens and their corrupt guards sometimes attack those living there. People carry shivs and SMGs as personal weapons. Improvised chemical bombs and orbital laser strikes have been deployed there. Described in code-comments as ''[...] a frigid ice-moon prison colony'', however the canonicity of such comments is unclear.<ref name="Ideology Places"/> The [[#Yttakin|Yttakin]] xenohumans were first engineered to populate Yttak and they've since spread to other worlds.<ref name="Yttakin pirates">[[Yttakin pirates]] [[faction]] description</ref> Yttak is alternately referred to as a moon,<ref name="Ideology Places"/> a planet,<ref name="Yttakin pirates"/> and a world<ref>[[Yttakin]] [[xenotype]] description</ref> which could apply to either. It is unclear which is canonically correct. Given the pronunciation of Yttakin as "ee-ta-keen",<ref name="Biotech Preview 4">[https://store.steampowered.com/news/app/294100/view/3319740412995643281 Biotech Preview #4] Steam Announcement</ref> the name of the world is likely pronounced "Ee-tak".
|- id="Kemia"
! Kemia{{IdeologyIcon}}
| Toxic [[#War-world|war-world]]<ref name="Ideology Places"/><ref name="Book descriptions"/>
| A toxic war-world with slums, tunnel colonies, undertowns, and city lordhouses. Native Kemian work as street sweepers, cleanup engineers, protein farmers, taxi drivers, and weapons builders. Poison lords and their venom-soldiers sometimes attack those living there. People carry gas bombs and toxic flamethrowers as personal weapons. Nuclear dirty bombs, bio-engineered plagues, and penetrating toxic bombs have been deployed there. Described in code-comments as ''[...] a toxic, overcrowded world with an oppressive government'', however the canonicity of such comments is unclear. <ref name="Ideology Places"/>
|- id="Rogia"
! Rogia
| [[#Glitterworld|Glitterworld]]<ref name="Book descriptions"/><ref name="Ideology Places"/>
| A glitter-tech world with medical institutes, space elevators, robotics factories, and a planetary capitol. Native Rogians work as starforce cadets, artisan farmers, social-media prodigies, zero-g athletes, and glitter-tech smugglers. Corrupt bureaucrats and their bionic guards sometimes attack those living there. People carry [[charge lance]]s and [[persona monosword]]s as personal weapons. Antimatter warheads, weaponized computer viruses, and remote-controlled mechanoid workers have been deployed there. Described in code-comments as ''[...] a world of windy prairies and towering glitter-tech cities'', however the canonicity of such comments is unclear. <ref name="Ideology Places"/> Relationship with [[#Amen-Ti|Amen-Ti]], another glitterworld which also hosts a "Starforce", is unknown. It is possible that they are part of the same Star Empire, of which Amen-Ti is the capital.
|- id="Xanides"
! Xanides{{IdeologyIcon}}
| Mineral-planet
| An exploited mineral-planet with strip mines, ore refineries, nutrient paste cafeterias, and oxygen depots. Native Xanidians work as miners, supervisors, technicians, mechanics, and life support engineers. Mine-crop bosses and their mine-corp troops sometimes attack those living there. People carry electro-batons and [[autopistol]]s as personal weapons. Blasting charges and EMP strikes to the life support systems have been deployed there. Described in code-comments as ''a small strip-mining planet with a thin atmosphere'', however the canonicity of such comments is unclear. <ref name="Ideology Places"/>
|- id="Lutuni"
! Lutuni{{IdeologyIcon}}
| [[#Coreworld|Coreworld]]<ref name="Book descriptions"/>
| A rainforest paradise with augmentation clinics, hyper-yachts, zero-g stadia, and space elevator complexes. Native Luntuni work as tourist guides, zero-g performers, [[luciferium]] distributors, virtual celebrities, and shuttle pilots. Entertainment moguls and their enforcers sometimes attack those living there. People carry vibro-knives and charge pistols as personal weapons. Structural disintegration bacterium and smuggled [[orbital bombardment targeter]]s have been deployed there. Described in code-comments as ''a rainforest paradise and glitterworld tourist destination'', however the canonicity of such comments is unclear. <ref name="Ideology Places"/>
|- id="Zartza"
! Zartza
| [[#Deathworld|Deathworld]]
| A deathworld planet.<ref name="Book descriptions"/> Given the name, presumably involved in the [[#Xennoa-Zartza War|Xennoa-Zartza War]] as either a battlefield or belligerent.<ref name="Harris"/> It is unknown whether the planet was a deathworld before the conflict.
|- id="Vinna"
! Vinna
| [[#Medieval world|Medieval world]]<ref name="Book descriptions"/>
| A medieval world<ref name="Book descriptions"/> with raiders, mudlands, and a number of settlements.<ref>Backstory of [[List of Player-created Pawns#Ida Painstingle|Ida 'Ida' Painstingle]]</ref>
|- id="Cormora Prime"
! Cormora Prime
| [[#Coreworld|Coreworld]]
| A coreworld.<ref name="Book descriptions"/>
----
'''''Out of Universe:''' May be a reference to Gomorrah, a biblical city destroyed by God for its wickedness, or the Comorra, an Italian Mafia organization and criminal society.''
|- id="Glossolia"
! Glossolia
| [[#Coreworld|Coreworld]]
| A coreworld.<ref name="Book descriptions"/>
----
'''''Out of Universe:''' May be a reference to Glossolalia, commonly called "speaking in tongues", the practice of uttering words or speech-like sounds believed by some to have religious meaning.''
|- id="Barbaros"
! Barbaros
| [[#Coreworld|Coreworld]]
| A coreworld.<ref name="Book descriptions"/>
----
'''''Out of Universe:''' Means "Barbarians" in Spanish, also possibly a reference to the famous corsair Hayreddin Barbarossa or the Holy Roman Emperor, Frederick Barbarossa.''
|- id="Atura"
! Atura
| Asteroid
| An asteroid.<ref name="Book descriptions"/> May be the location of [[#Atura station|Atura station]].
|- id="Ranomi"
! Ranomi
| Asteroid
| An asteroid.<ref name="Book descriptions"/>
|- id="Taxlos"
! Taxlos
| Asteroid
| An asteroid.<ref name="Book descriptions"/>
|- id="Aryn Sigma"
! Aryn Sigma
| Asteroid
| An asteroid.<ref name="Book descriptions"/>
|- id="Aesh 265"
! Aesh 265
| Asteroid
| An asteroid.<ref name="Book descriptions"/>
|- id="Widdershins"
! Widdershins
| Asteroid
| An asteroid.<ref name="Book descriptions"/>
----
'''''Out of Universe:''' Widdershins is a term meaning to go counterclockwise, to walk around an object by always keeping it on the left, or to take a course opposite the apparent motion of the sun. It is also associated with being unlucky. The relevance, such as whether it describes the orbit of the asteroid, is unknown.''
|- id="Einio"
! Einio
| [[#Dino-world|Dino-world]]
| A dino-world.<ref name="Book descriptions"/>
----
'''''Out of Universe:''' Einio is the name of an Einiosaurus, a ceratopsian, in the Nintendo game series Fossil Fighters in which fossils of prehistoric animals are revived and have powers as a result. It is unclear whether the name is a reference specifically to the series or simply to the real ceratopsian, if either.''
|- id="Baryonyx"
! Baryonyx
| [[#Dino-world|Dino-world]]
| A dino-world.<ref name="Book descriptions"/>
----
'''''Out of Universe:''' Baryonyx is a genus of theropod dinosaur, as well as the common name used to refer to the Baryonyx walkeri species.''
|- id="Venator"
! Venator
| [[#Dino-world|Dino-world]]
| A dino-world.<ref name="Book descriptions"/>
----
'''''Out of Universe:''' Venator means hunter in Latin, which is already a fitting name for a dino-world, however it is also used in the construction of a number of dinosaur names including the carnivorous theropod dinosaurs the Neovenator and Viavenator.''
|- id="N'cilo"
! N'cilo
| [[#Dino-world|Dino-world]]
| A dino-world.<ref name="Book descriptions"/>
|- id="Brach"
! Brach
| [[#Dino-world|Dino-world]]
| A dino-world.<ref name="Book descriptions"/>
----
'''''Out of Universe:''' The name may be a reference to Brachiosaurus, a genus of sauropod dinosaur.''
|- id="Mauro"
! Mauro
| [[#Toxic world|Toxic world]]
| A toxic world.<ref name="Book descriptions"/>
|- id="Oxy VI"
! Oxy VI
| [[#Toxic world|Toxic world]]
| A toxic world.<ref name="Book descriptions"/>
|- id="Imbatus"
! Imbatus
| [[#Toxic world|Toxic world]]
| A toxic world.<ref name="Book descriptions"/>
|- id="Soleno"
! Soleno
| [[#Toxic world|Toxic world]]
| A toxic world.<ref name="Book descriptions"/>
|- id="Sangwine"
! Sangwine
| [[#Toxic world|Toxic world]]
| A toxic world.<ref name="Book descriptions"/>
----
'''''Out of Universe:''' Sangwine is an obsolete spelling of Sanguine, a term meaning both "pertaining to blood" and "optimistic".''
|- id="Vanu"
! Vanu
| [[#War-world|War-world]]<ref name="Book descriptions"/>
| A war-world, presumably the location of the [[#Vanu Defense College|Vanu Defense College]]
----
'''''Out of Universe:''' Possibly a reference to the Vanu Sovereignty, a faction in the game PlanetSide''
|- id="Samnium"
! Samnium
| [[#War-world|War-world]]
| A war world.<ref name="Book descriptions"/>
----
'''''Out of Universe:''' Samnium was a nation-state in Ancient Italy that was a belligerent in a number of wars with the Roman Republic.''
|- id="Kyrus"
! Kyrus
| [[#War-world|War-world]]
| A war world.<ref name="Book descriptions"/>
----
'''''Out of Universe:''' As the name Kyrus is a derivative of Cyrus, it may be a reference to Cyrus the Great, the founder of the Achaemenid Empire and conqueror.''
|- id="Punica"
! Punica
| [[#War-world|War-world]]
| A war world.<ref name="Book descriptions"/>
----
'''''Out of Universe:''' Punica is the name of the genus of plants that includes the pomegranate, which derives from the Latin term for Carthaginian apple. Given the war related nature, likely a more general reference to the term "Punic", meaning "of or relating to ancient Carthage", an ancient empire that fought the Roman Republic during the Punic Wars.''
|- id="Cimbria XII"
! Cimbria XII
| [[#War-world|War-world]]
| A war world.<ref name="Book descriptions"/>
----
'''''Out of Universe:''' Likely a reference to the Cimbri, a germanic tribe from the Cimbrian peninsula in what is now Jutland. The Cimbri invaded Gaul and fought the Roman Republic in a series of battles, including the devastating Battle of Arausio in which almost a dozen Roman Legions were destroyed.
|- id="Barkitos"
! Barkitos
| [[#War-world|War-world]]
| A war world.<ref name="Book descriptions"/>

|- id="Chateau D'Ouen"
! Chateau D'Ouen
| [[#Prison planet|Prison world]]
| A prison world.<ref name="Book descriptions"/>
----
'''''Out of Universe:''' Given the prison connection, possibly a reference to Château d'If, the infamous French prison for political and religious prisoners and notable for its use in Alexandre Dumas's novel 'The Count of Monte Cristo'.''
|- id="Casmina"
! Casmina
| [[#Prison planet|Prison world]]
| A prison world.<ref name="Book descriptions"/>
|- id="Hoalo"
! Hoalo
| [[#Prison planet|Prison world]]
| A prison world.<ref name="Book descriptions"/>
----
'''''Out of Universe:''' Likely a reference to Hỏa Lò Prison, commonly referred to by its Vietnam War era nickname The Hanoi Hilton, a prison in what is now Vietnam infamous for the mistreatment and torture of its prisoners under both French and North Vietnamese governments.''
|- id="Borren"
! Borren
| [[#Prison planet|Prison world]]
| A prison world.<ref name="Book descriptions"/>
|- id="Aldgate"
! Aldgate
| [[#Prison planet|Prison world]]
| A prison world.<ref name="Book descriptions"/>
----
'''''Out of Universe:''' Possibly a reference to, and pun on, Newgate Prison, a prison in London, England that was built in 1188 and in use for over 700 years.
|- id="Port Basil"
! Port Basil
| [[#Prison planet|Prison world]]
| A prison world.<ref name="Book descriptions"/>
----
'''''Out of Universe:''' Given the prison connection, possibly a reference to Port Arthur, a town in Tasmania, Australia originally founded as a penal colony for transportees from Great Britain.''
|}
'''Note:''' The rimworlds on which gameplay takes place have randomly generated names. Due to both their limited application and randomly generated nature, the randomly generated names of these rimworlds are considered semi-canonical only and are not listed here.


===== Prefixed world names =====
World names in generated text can sometimes be prefaced by Kuhn- and Ur-. Additionally references to rituals named after the worlds but prefixed with a ka'= are also mentioned.<ref name="Book descriptions"/> The significance of these prefixes is unknown.

==== Systems ====
{| {{STDT|sortable}}
|-
! Name !! Description
|- id="Xennoa system"
! Xennoa system
| Hosted a military base. Has a military with infantry and spacejets, involved in the [[#Xennoa-Zartza War|Xennoa-Zartza War]] <ref name="Harris">Backstory of [[List of Player-created Pawns#Kyle Harris|Kyle Harris]]</ref>
|}

==== Other ====
{| {{STDT|sortable}}
|-
! Name !! Description
|- id="Utmaior Academy"
! Utmaior Academy
| Prestigious academy on a [[#Glitterworld|glitterworld]],<ref name="Doc">Backstory of [[List of Player-created Pawns#James Grey|James 'Doc' Grey]]</ref> presumably located on [[#Utmaior|Utmaior]].
|- id="Vanu Defense College"
! Vanu Defense College
| Teaches young cadets proficiency in a range of weapons and survival skills,<ref name="Leystrat">Backstory of [[List of Player-created Pawns#Bashkire Leystrat|Bashkire Leystrat]]</ref> presumably located on [[#Vanu|Vanu]].
----
'''''Out of Universe:''' Possibly a reference to the Vanu Sovereignty, a faction in the game PlanetSide''
|- id="Caspian School of Engineering"
! Caspian School of Engineering
| A [[#Glitterworld|glitterworld]] school that offers mathematics and computer programming in its curriculum.<ref>Backstory of [[List of Player-created Pawns#Darrien Maliphalo|Darrien 'Mal' Maliphalo]]</ref> Presumably located on [[#Caspian|Caspian]].
|- id="Atura station"
! Atura station{{IdeologyIcon}}
| An orbital shipyard with shuttle docks, manufacturing rings, residential rings, and a central control room. Native Aturans work as construction drone operators, managers, test pilots, sales agents, and 3D printer technicians. Crime bosses and their thugs sometimes attack those living there. People carry tasers and arc welders as personal weapons. EMP strikes to the life support systems and remote-controlled welding drones have been deployed there. Described in code-comments as ''an orbital dry dock and construction yard'', however the canonicity of such comments is unclear. <ref name="Ideology Places"/> May be located at, built from, or otherwise related to the asteroid [[#Atura|Atura]].
|- id="Zeglar colonies"
! Zeglar colonies
| Purchases slaves, including for male prostitution.<ref name="Gnugfur">Backstory of [[List of Player-created Pawns#Robert Krondorfer|Robert 'Gnugfur' Krondorfer]]</ref>
|- id="New Jerusalem"
! New Jerusalem{{AnomalyIcon}}
| Unknown if even a real place, or a place at all - only mentioned by [[golden cube]]-obsessed pawns talking about a "cubic New Jerusalem" <ref name="RulePacks_Cube">RulePacks_Cube.xml]</ref>
|}

==== Official Art ====
The following are clipped out of official key art for the base game and DLCs:

<gallery>
Background planet pc.png |A rimworld {{PCIcon}}
Background moon pc 1.png |A rimworld's moon {{PCIcon}}
Background moon pc 2.png |A rimworld's moon {{PCIcon}}
Background planet console.png|A rimworld {{ConsoleIcon}}
Background moon console 1.png|A rimworld's moon {{ConsoleIcon}}
Background moon console 2.png|A rimworld's moon {{ConsoleIcon}}
</gallery>
<gallery>
Background planet royalty.png |A rimworld {{RoyaltyIcon}}
Background moon royalty 1.png |A rimworld's moon {{RoyaltyIcon}}
Background moon royalty 2.png |A rimworld's moon {{RoyaltyIcon}}
Background sun royalty 1.png |A rimworld's sun {{RoyaltyIcon}}
Background planet ideology.png|A rimworld {{IdeologyIcon}}
Background moon ideology 1.png|A rimworld's moon {{IdeologyIcon}}
Background moon ideology 2.png|A rimworld's moon {{IdeologyIcon}}
</gallery>
<gallery>
Background moon anomaly 1.png|A rimworld's moon {{AnomalyIcon}}
Background moon anomaly 2.png|A rimworld's moon {{AnomalyIcon}}
</gallery>

=== Events ===
{| {{STDT|sortable}}
|-
! Name !! Description
|- id="Zartha crisis"
! Zartha crisis
| Apparently a military conflict fought over many worlds, in both ground and air domains with fighters and fighter controllers deployed. <ref name="Leystrat"/>
|- id="Inner Destrian War"
! Inner Destrian War
| Ostensibly a military conflict that occured at least one generation ago, in the aftermath and/or resulting instability of which people were captured and sold into slavery.<ref name="Stonejaw"/> Presumably involved [[#Destria|Destria]] as either a battlefield or belligerent.
|- id="Callos IX incident"
! Callos IX incident
| James 'Doc' Grey performed unethical experiments on the survivors of this incident, and when the experiments were published, he was exiled. <ref name="Doc"/> Presumably occurred on [[#Callos IX|Callos IX]] and may be the reason it is now a [[#Deadworld|deadworld]].<ref name="Book descriptions"/>
|- id="Xennoa-Zartza War"
! Xennoa-Zartza War
| A military conflict presumably fought either in, or by a polity from, the [[#Xennoa system|Xennoa system]],<ref name="Harris"/> presumably either on or against a polity based on, the planet [[#Zartza|Zartza]].<ref name="Book descriptions"/> Infantry and spacejets were deployed during the conflict.<ref name="Harris"/>
|}

=== Planet types ===
Note that planet types are not necessarily mutually exclusive, and a given planet may fit several separate categories.

{| {{STDT|sortable}}
|-
! Name !! Description
|- id="Deadworld"
! Deadworld
| Distinct from [[#Deathworld|deathworlds]], these are planets which have not been significantly contacted by humans. Generally not inhabitable. All planets are like this before people arrive for the first time.<ref name="Cryptosleep Revival Briefing"/>
|- id="Deathworld"
! Deathworld
| Distinct from [[#Deadworld|deadworlds]] and sometimes spelled as '''Death-world''', the meaning of the term deathworld appears to correlate with the common usage of the term in science fiction discussion - namely a planet that is technically habitable but incredibly hostile to human life. [[#Impids|Impids]] are described as originally being designed for "''dry deathworlds''",<ref>[[Impid]] [[xenotype]] description and short description</ref> while [[#Wasters|wasters]] are designed for "''post-apocalyptic deathworlds''".<ref>[[Waster]] [[xenotype]] description and short description</ref> [[Books]] about the [[Research#Battery|Battery research]] can reference an "''acid lake on the leaden shores of a deathworld worked as a natural battery''".<ref>[[Research#Battery|Battery research]] subject_story strings.</ref> [[#Creticon|Creticon]] is described a "''blasted death-world''" while it is further described in code-comments as "''[...] a high-tech death-world''",<ref name="Ideology Places"/> while [[#Ilwaba|Ilwaba]] is described in code-comments as a "''regrown deathworld''",<ref name="Ideology Places"/> however the canonicity of such comments is unclear.The disparate natures of these examples support the concept that why a deathworld is hostile to human life is not important to the definition, only that it is hostile. Despite the difficulty of living on these planets, some are still inhabited - [[Books]] about the [[Research#Tox gas|Tox gas research]]{{BiotechIcon}} can reference the author "''research[ing] cloud control tech for the tyrannocracy of a deathworld''",<ref>[[Research#Tox gas|Tox gas research]] subject_story strings.</ref> which implies not only people living on the planet, but a system of government. [[#Zartza|Zartza]], [[#Rayth|Rayth]], [[#Spectra|Spectra]], [[#JNovahex|JNovahex]], [[#Carthago|Carthago]], and [[#Grimcore|Grimcore]] are also referenced as being deathworlds.<ref name="Book descriptions"/>
|- id="Animal world"
! Animal world
| Planets with no people. Either everyone died, or the planet was seeded with plant and animal life by terraforming robots and nobody arrived.<ref name="Cryptosleep Revival Briefing"/> It is apparently not exclusive with an [[#Dino-world|Dino-world]] which may, in fact, be a subtype of this category.<ref name="Book descriptions"/>
|- id="Medieval world"
! Medieval worlds
| Similar to Earth from the agricultural revolution until the industrial revolution. Social structures are usually feudal or imperial. Planets can stay in this state for millennia.<ref name="Cryptosleep Revival Briefing"/>
|- id="Steamworld"
! Steamworld
| Similar to Earth in the 19th century. Often this state is short-lived, as societies develop into midworlds, but it can be very stretched out depending on culture and government structure.<ref name="Cryptosleep Revival Briefing"/>
|- id="Midworld"
! Midworld
| Worlds whose people have mastered flight, but not cheap interplanetary travel. Earth is in this stage in the 21st century.<ref name="Cryptosleep Revival Briefing"/>
|- id="Urbworld"
! Urbworld
| Super-high density planets dominated by cities. Urbworlds’ population growth outstripped their social and technological development, so they tend to be overcrowded, polluted, violent places. The people here are often callous towards strangers. This is often the outcome for midworlds that see their demographic transition into lower birth reversed by dysgenic reproduction patterns.<ref name="Cryptosleep Revival Briefing"/> Urbworlds can build mechanoids. <ref name="Keuneke">Backstory of [[List of Player-created Pawns#Markus Keuneke|Markus 'Keuneke' Keuneke]]</ref>Some urbworlds have worldwide cities ruled by corporations. <ref name="Coffey">Backstory of [[List of Player-created Pawns#Darius Coffey|Darius Coffey]]</ref>Urbworlds can be ancient - some even have greedy nobility in spire palaces while cannibal cults exist in the deepest reaches of the underground hive. <ref>Backstory of [[List of Player-created Pawns#Skye Lorne|Skye 'Skye' Lorne]]</ref>
|- id="Glitterworld"
! Glitterworlds
| The most technologically advanced societies that can be led by humans. Swaddled in comforts by the strong arms of technology, glitterworlds are the peak of recognizable human society in terms of art, health, and generous human rights. Common people from these planets often lack grit and are very trusting in people and technology.<ref name="Cryptosleep Revival Briefing"/> Likely synonmous with '''glitter-tech world'''.<ref>Ideology Places.xml - Rogia entry</ref> Glitterworlds are mostly free of disease and human suffering, and surgeons employed there mostly perform elaborate and creative cosmetic surgeries, and never have to remove a cancer or a bullet.<ref>Glitterworld surgeon Backstory</ref> While glitterworlds are peaceful places and some units rarely see action, they often remain prepared for war.<ref>Glitterworld Officer Backstory</ref> Despite this tendency towards peace, some glitterworlds do field space navies and engage in active campaigns against enemy cultures.<ref name="Nerhesi"/> On some glitterworlds all menial work was done by robots and people devoted themselves to leisure.<ref>Biosphere Manager Backstory</ref> This extends to some technical fields as well, such as AI handling all the technical aspects of architecture, allowing architects to focus on artistic expression <ref>Architect Backstory</ref> This is not universal however, as others still had humans washing dishes in restaurants<ref>Backstory of [[List of Player-created Pawns#Stijn Gezink|Stijn 'Stin' Gezink]]</ref> Farms are operated on some glitterworlds, though all but rare exceptions have abandoned traditional farming methods for glitterworld technologies.<ref>Backstory of [[List of Player-created Pawns#Pete Holiday|Pete Holiday]]</ref>Glitterworld police forces were often equipped with [[recon armor]]<ref>[[Recon armor]] description</ref> and [[Recon helmet|helmets]].<ref>[[Recon helmet]] description</ref> Some glitterworlds have mechanoid companions for children,<ref>Backstory of [[List of Player-created Pawns#Erisen Irioth|Erisen 'Erisen' Irioth]]</ref> or as workers.<ref name="Rogia">Ideology Places.xml - Rogia entry</ref> At least some Glitterworlds apparently remain capitalist, as attending their universities can leave a person in enormous debt,<ref>Backstory of [[List of Player-created Pawns#Caitlin Stirr|Caitlin 'Cait' Stirr]]</ref> and corporations exist.<ref>Backstory of [[List of Player-created Pawns#Ryan Michael|Ryan 'Legend' Michael]]</ref><ref name="Brazil">Backstory of [[List of Player-created Pawns#Jhet Whistler|Jhet 'Brazil' Whistler]]</ref> At least some Glitterworlds were monarchic, with royal households that would intermarry with the royal families of other planets.<ref>Backstory of [[List of Player-created Pawns#Xiao Li|Xiao 'Ally' Li]]</ref> See also: Sophiamunda and the Empire for information about a specific glitterworld society.
|- id="Rimworld"
! Rimworlds
| Planets lacking in strong central government and low in population density. These places tend to hover around the industrial level of technology or lower. Because they’re not homogenized by a central government, they tend to see a lot of interaction between people of different technology levels, as travelers crash-land or ancient communities stumble out of their cryptosleep vaults. These planets are often at the rim of known space, hence the name.<ref name="Cryptosleep Revival Briefing"/>
|- id="Coreworld"
! Coreworld
| Based on the name, may be the worlds that form the astrographical or political core of human civilization, perhaps including Earth and other early colonies. Alternatively, may be worlds located in the galactic core or some other definition. In the now non-canon [[#RimWorld Universe Quick Primer (Obsolete)|RimWorld Universe Quick Primer]], coreworlds and rimworlds were instead defined in opposition to each other. Coreworlds were those planets in the galactic core whose social and technological development benefited from the clustering of stars, and thus other cultures, in the core. Rimworlds were in turn those planets outside the core and thus further from neighbours.<ref name="RimWorld Universe Quick Primer">[[#RimWorld Universe Quick Primer (Obsolete)|RimWorld Universe Quick Primer]]</ref> However, with the new canon definition for rimworld, it's likely that this definition of core and rimworlds has been become non-canon, probably because the galactic core is significantly beyond the 1200 light year wide canonical expansion of humanity.<ref name="Cryptosleep Revival Briefing"/> Possibly synonymous with planets in the 'core region', which includes at least one glitterworld.<ref>Backstory of [[List of Player-created Pawns#Candice Roughchild|Candice Roughchild]]</ref> Appear to be relatively advanced and stable, with at least midworld level surgical capabilities,<ref>Backstory of [[List of Player-created Pawns#Alyssa Orchard|Alyssa 'Sparkles' Orchard]]</ref> planetary governments,<ref name="Anarchist">Backstory of [[List of Player-created Pawns#Mike Mudgett|Mike 'Anarchist' Mudgett]]</ref> and sufficient competent military forces to push out both anarchists<ref name="Anarchist"/> and fairly large mercenary forces.<ref>Backstory of [[List of Player-created Pawns#Aznable Coal|Aznable 'Reikguard' Coal]]</ref>
|- id="Toxic world"
! Toxic world
| Worlds destroyed by pollution, chemical or nuclear warfare, but still inhabitable at a low level, with sufficient technology.<ref name="Cryptosleep Revival Briefing"/> Toxic may have a limited definition, or may only relate to Humans, as some toxic worlds are overgrown with hostile plant life.<ref name="Johs">Backstory of [[List of Player-created Pawns#Johs Barrowlocht|Johs 'Johs' Barrowlocht]]</ref>
|- id="Glassworld"
! Glassworld
| Worlds utterly destroyed by high-energy weapons of mass destruction. They’re nicknamed ‘marbles’ because their surfaces have been “glassed”. Nuclear weapons aren’t enough to glass a planet, so this level of destruction is rare. On some of these worlds, people can walk outdoors for a time without dying. None of them harbour permanent life bigger than a paramecium.<ref name="Cryptosleep Revival Briefing"/>
|- id="Transcendent world"
! Transcendent world
| It’s a stretch to call these entities worlds, since they resemble giant computers more than they resemble planets. The mechanics of these planets is mysterious, but many scholars believe transcendents are the outcome when a sovereign archotech decides to incorporate a whole planet into itself.<ref name="Cryptosleep Revival Briefing"/>
|- id="Indworld"
! Indworlds
| Distinct from [[#Industrial worlds|industrial worlds]], these are worlds undergoing their industrial revolution.<ref>Backstory of [[List of Player-created Pawns#Victoria Louene|Victoria 'Vicky' Louene]]</ref>
|- id="Industrial world"
! Industrial world
| Distinct from [[#Indworld|Indworlds]], these are worlds devoted predominantly to industry.<ref>Backstory of [[List of Player-created Pawns#Amelia Flais|Amelia 'Engie' Flais]]</ref><ref>Backstory of [[List of Player-created Pawns#Sa'Bikk Saleosy|Sa'Bikk 'Sab' Saleosy]]</ref><ref>Backstory of [[List of Player-created Pawns#Daniel Mann|Daniel 'Dankman' Mann]]</ref> Some host large factory cities<ref>Backstory of [[List of Player-created Pawns#Felix von Schild|Felix von Schild]]</ref>
|- id="Farming planet"
! Farming planet
| Worlds devoted predominantly to farming. Not necessarily technologically backwards, with some using automated machinery that grow and harvest the multitude of crops. <ref>Backstory of [[List of Player-created Pawns#Conlay Shen|Conlay Shen]]</ref> Likely synonymous with '''farm-worlds'''.<ref>Ideology Places.xml - Filson entry</ref>
|- id="Prison planet"
! Prison planet
| Worlds where convicts are condemned to remove malefactors from society. <ref name="Jay">Backstory of [[List of Player-created Pawns#Jered Martin|Jered 'Jay' Martin]]</ref>
|- id="Feudal world"
! Feudal world
| Multi-planet feudal empires besides the [[Empire]] exist. <ref>Backstory of [[List of Player-created Pawns#Frank Laquinto|Frank 'Isimiel' Laquinto]]</ref>
|- id="Trash planet"
! Trash planets
| Dumping grounds for surrounding glitterworlds <ref>Backstory of [[List of Player-created Pawns#Xandarian Stalzer|Xandarian 'Xandy' Stalzer]]</ref>
|- id="Junkyard planet"
! Junkyard planet
| Apparently self-descriptive. Possibly synonymous with trash planets as they are ostensibly similar titles and [[#Bagua 5|Bagua 5]] is defined as both in different places, however given the name possibly differentiated by being intended to allow salvage and scrapping rather than simply dumping.<ref>Ideology Places.xml - Bagua 5 entry</ref>
|- id="Iceworld"
! Iceworld
| Apparently self-descriptive. Plants are rare. <ref>Backstory of [[List of Player-created Pawns#Slivaki Warts|Slivaki 'Sliverwar' Warts]]</ref>
|- id="Dino-world"
! Dino-world
| Apparently self-descriptive - worlds inhabited by dinosaurs and other megafauna, likely resurrected through genetic engineering. Mentioned species of a single example dino-world include: ankylosaurs, blue mammoths, and novoraptors.<ref name="Zoutera">Ideology Places.xml - Zoutera entry</ref>It is apparently not exclusive with an [[#Animal world|Animal world]] and may, in fact, be a subtype of that category.<ref name="Book descriptions"/>
|- id="War-world"
! War-worlds
| Worlds stuck in an endless cycle of war. These planets are typically over polluted due to constant usage of bombs and chemical weapons.<ref>Ideology Places.xml - Kemia entry</ref>
|- id="Mineral-planet"
! Mineral-planet
| Unknown definition. Likely descriptive of either their natural resources or their economic product<ref>Ideology Places.xml - Xanides entry</ref>
|- id="Oceanic planet"
! Oceanic planet
| Apparently self-descriptive.<ref name="Ideology Places">Ideology Places.xml</ref>
|- id="Other worlds"
! ''Other worlds''
| Beyond these categories, there are many exceptional planets in strange states created by their peculiar social and technological evolutions. Given the scale and age of the universe, there is a lot of time and space for a lot of very strange situations to develop.<ref name="Cryptosleep Revival Briefing"/>
|}

'''Additional facts:'''
* Steamworlds and Midworlds aren't necessarily mutually exclusive. <ref>Backstory of [[List of Player-created Pawns#Charles Zillioner|Charles 'Charlzie' Zillioner]]</ref>
* Industrial planets and midworlds ''may'' not necessarily be mutually exclusive. <ref>Backstory of [[List of Player-created Pawns#Lancelot Hale|Lancelot 'Lance' Hale]]</ref>
* Several spacer or glittertech societies, including Iwamura, Rogia, and Lutuni, host zero-g sports with professional athletes competing, some in zero-g stadia. Lutuni also hosts zero-g performers of an unknown type.<ref name="Ideology Places"/>

=== Technologies and Militaries ===
A variety of militaries exist in various styles, structures, purposes and technology levels. This include naval and space-based fleets, ground infantry, orbital troopers, spaceship-to-spaceship boarding actions and a massive variety of supersoldier projects.

==== Militaries and Military Technology ====
* '''Space marines''' - A role filled by human warriors. Some serve on the navy ships of space-faring empires, where they punch into enemy starships, gun down the crew, and capture the ship intact.<ref>Space marine Backstory</ref><ref>Backstory of [[List of Player-created Pawns#Nico Storch|Nico Storch]]</ref> Others serve in the security forces of off-planet corporations, defending ships against pirates and engaging in private space warfare contracts.<ref>Backstory of [[List of Player-created Pawns#Roland Kleist|Roland 'Roland' Kleist]]</ref> One organisation of space marines was the "Interplanetary Marines" which fought on behalf of a particular planet.<ref>Backstory of [[List of Player-created Pawns#Trevor Cobb|Trevor 'Hunter' Cobb]]</ref> Colony contact expeditionary forces employ space marine medics.<ref>Backstory of [[List of Player-created Pawns#Ryan Torrijos|Ryan 'Noob' Torrijos]]</ref> [[Marine armor]]<ref>[[Marine armor]] description</ref> and [[marine helmet|helmets]]<ref>[[Marine helmet]] description</ref> were often used by rapid-incursion space marines. [[Go-juice]] was developed as a combat drug for space marines during the early days of interplanetary warfare.<ref>[[Go-juice]] description</ref>
* '''Navy pathfinders''' - A group of military explorers dedicated to charting pathways through deep space and on remote planets.<ref>Backstory of [[List of Player-created Pawns#Nicklaus Blackthorn|Nicklaus 'Shadow' Blackthorn]]</ref>
* '''Mechanoids''' - Some militaries deploy combat mechanoids in their militaries <ref>Backstory of [[List of Player-created Pawns#Dennis McCarthy|Dennis 'Mac' McCarthy]]</ref><ref name="Keuneke"/>
* '''Charge pistols''' - Exist. <ref name="Lutuni">Ideology Places.xml - Lutuni entry</ref>
* '''Vibro-knives''' - Exist. <ref name="Lutuni">Ideology Places.xml - Lutuni entry</ref>
* '''Archotech mass-inverter''' - A mass weapon of unknown description created by archotechs.<ref name="Ideology Places"/>
* '''Tasers''' - Exist.<ref name="Altura station">Ideology Places.xml - Altura station entry</ref>
* '''Mega-cannon''' - A "frighteningly powerful" long-range cannon for artillery or anti-ship use.<ref name="Ancient mega-cannon barrel">[[Ancient mega-cannon barrel]] description</ref>

==== Ship types ====
* '''Interplanetary super-destroyer''' - Such as the HMS Thunder-Child of the Royal Fleet <ref>Backstory of [[List of Player-created Pawns#Jake Maddams|Jake 'Table' Maddams]]</ref>
* '''Starfighters''' - Combat spacecraft and are flown by starfighter pilots for militaries.<ref>Backstory of [[List of Player-created Pawns#Sjoerd Lukas|Sjoerd 'Bowman' Lukas]]</ref> See also '''manned fighters'''.
* '''Manned Fighters''' - Spacecraft launched from Carrier Ships and flown by fighter pilots.<ref name="Nerhesi"/>
* '''Military spacejet''' - Deployed in the [[#Xennoa-Zartza War|Xennoa-Zartza War]].<ref name="Harris"/>
* '''Carrier Ships''' - Carry manned fighters. Carried escape pods. <ref name="Nerhesi"/>
* '''Fighter-bombers''' - Fielded by the [[Empire]], a fighter bomber design specialized in spreading incendiary gel on flammable targets. Presumably an atmospheric craft.<ref>Firebomber Backstory</ref>
* '''Spaceyacht''' - A human-piloted pleasure craft and transport for the well-to-do, such as wealthy businessmen and politicians <ref>Backstory of [[List of Player-created Pawns#Owen Clarke|Owen 'Cali' Clarke]]</ref>
* '''Space cruiser''' - A manned space-capable ship of some kind.<ref name="Jay"/>
* '''Consularship''' - Such as the St. Anthem. Carried glitterworld diplomats on diplomatic tasks. <ref>Backstory of [[List of Player-created Pawns#Florian Haas|Florian 'Skater' Haas]]</ref>
* '''Hyper-yacht''' - Unknown. Possibly a glitterworld pleasure craft but the canonicity of code-comments are unclear.<ref name="Lutuni"/>
* '''Escape pod''' - Carried by starships, used to escape crippled or destroyed ships.<ref>[[Scenario system#Crashlanded|"Crashlanded" starting scenario]] description</ref><ref>[[Scenario system#The Sanguophage|"The Sanguophage" starting scenario]] description</ref><ref name="Nerhesi"/><ref name="Gnugfur"/>
<gallery>
Background ship whole.png|Ship of unknown type and range
Background ship broken.png|The same ship broken in half
Background ship royalty 1.png|Ship of unknown type and range{{RoyaltyIcon}}
Background ship royalty 2.png|Ship of unknown type and range{{RoyaltyIcon}}
Background ship biotech 1.png|Ship of unknown type and range{{BiotechIcon}}
Background ship biotech 2.png|Ship of unknown type and range{{BiotechIcon}}
Background ship biotech 3.png|Ship of unknown type and range{{BiotechIcon}}
</gallery>

====Other technologies====
* '''Substance F''' - A drug. <ref>Backstory of [[List of Player-created Pawns#Peter Marshall|Peter 'Pete' Marshall]]</ref>
* '''Mindwiping and mental reprogramming''' - Practiced on some urbworlds. See also: '''Body Confiscation''' <ref name="Coffey"/>
* '''Body confiscation''' - Some urbworlds will confiscate criminals' bodies for use. <ref name="Coffey"/>
* '''Autocycle''' - A midworld vehicle. <ref name="Ironhead">Backstory of [[List of Player-created Pawns#Robert Seafield|Robert 'Ironhead' Seafield]]</ref>
* '''Netcasts''' - A midworld audio medium. <ref name="Ironhead"/>
* '''Vidtube''' - A popular video sharing service. Hosted everything from video game reviews to pasta cooking guides. Some had over a million followers on the service. People on the service were called Vidtuber Stars or Vidtubers <ref>Backstory of [[List of Player-created Pawns#Remy Young|Remy Young]]</ref>
* '''Holography''' - Including interactive holography which gives form to artificial intelligences to allow them to interact <ref>Backstory of [[List of Player-created Pawns#Dave Mark|Dave 'Fox' Mark]]</ref>
* '''VR''' - Accesses to a virtual gaming universe by spinal plug. Can be addictive. Unplugging during play can create a mental backlash and merge the real and virtual identities. <ref>Backstory of [[List of Player-created Pawns#Douglas Black|Douglas 'Doug' Black]]</ref> Can also be used to raise children or teach professions<ref name="Brazil"/>
* '''Neurosimulator''' - A technology available on Glitterworlds that apparently lets you experience a simulation of "exploring the stars", and possibly other scenarios. Relationship to VR unknown. <ref>"[[Scenario system#The Rich Explorer|The Rich Explorer]]" scenario description</ref>
* '''Vatgrown''' - Genetically modified living creatures, including humans, grown in a lab and usually designed and programmed for a specific task. Capable of being produced on some urbworlds. Examples of roles for which vatgrown humans were produced include Soldiers,<ref>Vatgrown Soldier Backstory</ref> Combat Medics <ref>Backstory of [[List of Player-created Pawns#Edward Toon|Edward Toon]]</ref>, Assassins <ref>Backstory of [[List of Player-created Pawns#Vaska Neemor|Vaska 'Vas' Neemor]]</ref>, Slavegirls (which are illegal at least in some places) <ref>Backstory of [[List of Player-created Pawns#Emily Young|Emily 'Emmie' Young]]</ref>, and even Scientists with minds perfectly tuned for physics and chemistry. <ref>Backstory of [[List of Player-created Pawns#Nicole Squid|Nicole 'Nicole' Squid]]</ref> The same process, along with genetic modification, was also used in the weaponization of the original Sorne Geneline into the current [[Insectoid]] species.<ref name="Insectoid Faction Description"/>
* '''Perfect mates''' - Genetically-engineered on glitterworlds, are fertile and capable of producing children.<ref>Backstory of [[List of Player-created Pawns#Chaz Serir|Chaz 'Chaz' Serir]]</ref> Their relation to vatgrown and highmates is currently unknown, however a currently unused backstory in the gamefiles states they, or at least some, are vatgrown in hyper-expensive clinics to serve the tastes of a specific client. They are engineered, raised and trained as a perfect pleasure-giving mate, with ''"learned skills that would baffle even the most seductive baseline human lovers"''. The canonicity of these statements are also currently unknown.
* '''G-nome Project''' - A Genetic engineering project that created humans implanted at birth with encyclopedic knowledge of all aspects of xenobiology. Presumably on a Glitterworld. Relation to vatgrown unknown. <ref>Backstory of [[List of Player-created Pawns#Joshua Nelson|Joshua 'Gizmo' Nelson]]</ref>
* '''Lab-grown children''' - An altruistic but failed attempt to create a new class of human. Method and relation to similar concepts unknown. <ref>Backstory of [[List of Player-created Pawns#Lukas Dietrich|Lukas Dietrich]]</ref>
* '''Clone-farming''' - Clone children are seeded into nutrient-rich womb-vats and rapidly grown in a simmed (i.e. VR) universe. They're harvested later, sometimes for food, sometimes for organs, sometimes for workers - but they're always disposable. Harvesting the products of clone farms is mostly done by the clones themselves - particularly to those whose sims tended towards the social. <ref>Backstory of [[List of Player-created Pawns#Dan Griliopoulos|Dan 'Grill' Griliopoulos]]</ref>
* '''Online hiveminds''' - Worldwide system that sacrifices the peoples individuality to join together in an online hivemind.<ref>Urbworld Rebel Backstory</ref>
* '''Space elevators''' - A number of planets use space elevators.<ref name="Ideology Places"/>
* '''3D printers''' - Used on orbital shipyards in some capacity.<ref name="Altura station"/>
* '''Glitterpedia''' - A glitterworld technology through which glitterpedia recorders document information.<ref name="Codex">Backstory of [[List of Player-created Pawns#Ang Gao|Ang 'Codex' Gao]]</ref> Likely analogous to Wikipedia.
* '''Eltex''' - A material, threads of which can be embedded in [[prestige armor|specialized armor]] or [[eltex|clothing]] to enhance the wearer's psychic sensitivity.<ref>[[Prestige armor]] descriptions</ref> It is technically indeterminate whether it is responsible for improving neural heat dissipation, however as eltex is the only noted difference between prestige armors and their standard variants it is likely the case. It is possible that eltex is simply one of, or the most significant of, the "special psychic focusing materials" mentioned in the description of eltex clothing.<ref>[[Eltex]] item descriptions</ref>

=== Named characters ===

{| {{STDT|sortable}}
|-
! Name !! Description
|- id="King Loteric"
! King Loteric
| A king of an unknown kingdom in an unknown world. Died in an unfortunate accident. <ref>Child-knave Backstory</ref>
|- id="Grady Loughman"
! Grady Loughman
| A kingpin of a drug cartel.<ref>Drug lieutenant Backstory</ref>
|- id="Lord-explorer Varan-Dur"
! Lord-explorer Varan-Dur
| An explorer who was made into the first Sanguophage by an Archotech they tried to control.<ref>Sanguophage description</ref>
|}

=== Named groups ===

{| {{STDT|sortable}}
|-
! Name !! Description
|- id="Doomben Rats"
! Doomben Rats
| A notorious and violent urchin gang.<ref>Pickpocket Backstory</ref>
----
'''''Out of Universe:''' Doomben is an area in Brisbane, Australia named after a racecourse and associated horse race. The relevance, if any, is unknown.''
|- id="Corestars Entertainment Company"
! Corestars Entertainment Company
| An entertainment organization that buys people to appear on its shows. One of their shows is apparently called Bloodgame.<ref>Backstory of Bloodgame Survivor</ref>
|- id="Arcknight Industries"
! Arcknight Industries
| A company that employs space truckers.<ref name="Johs"/>
|}

=== Animals ===
{| {{STDT|sortable}}
|-
! Name !! Description
|- id="Furred xenohuman"
! Furred xenohuman
| Exist on a cold [[#Rimworld|rimworld]] of at least industrial level.<ref name="Svejgaard">Backstory of [[List of Player-created Pawns#Benjamin Svejgaard|Benjamin 'Svejgaard' Svejgaard]]</ref> May refer to [[#Yttakin|yttakin]] or some other furred xenotype.
|- id="Transbird"
! Transbird
| Exist and crewed, and presumably captained, starships.<ref name="Svejgaard"/> In the now non-canon [[#Longsleep Revival Briefing|Longsleep Revival Briefing]], the prefix [[#The biology of plants and animals|Trans-]] indicated animals with intelligence in the human range from breeding, evolution, and genetic engineering including recombination with human DNA. They also included physical changes to the animal's body to better exploit the new intelligence. Transanimals can read, use tools, form teams, hold conversations, and think about complex ideas. Transdog, transbear, transgoat, transsimian were given as examples.<ref name="Longsleep Revival Briefing">[[#Longsleep Revival Briefing|Longsleep Revival Briefing]]</ref> This likely implies that that portion of the lore remains canon, and that transbirds are modified, intelligent birds.
|- id="Opticow"
! Opticow
| Present on Midworlds in agricultural settings. <ref>Backstory of [[List of Player-created Pawns#Jacqueline Richter|Jacqueline 'Jackalope' Richter]]</ref> In the now non-canon [[#Longsleep Revival Briefing|Longsleep Revival Briefing]], the prefix [[#The biology of plants and animals|Opti-]] indicated animals with enhanced but still sub-human intelligence from breeding, evolution, and genetic engineering including recombination with human DNA. They also included physical changes to the animal's body to better exploit the new intelligence. Optianimals can usually use tools, form long-term goals and organize into primitive social groups, but can’t speak more than a few words, read, or think abstractly. Optidogs, optipigs, optiwhales, and optimonkeys were given as examples.<ref name="Longsleep Revival Briefing"/> This likely implies that that portion of the lore remains canon, and that opticows are modified, semi-intelligent [[cow]]s.
|- id="Lava-snail"
! Lava-snail
| Farmed on the dim volcano-world of [[#Nuchadus|Nuchadus]].<ref name="Ideology Places">Ideology Places.xml</ref>
|- id="Deep-kraken"
! Deep-kraken
| Used as weapons on the oceanic planet of [[#Wavia|Wavia]].<ref name="Ideology Places">Ideology Places.xml</ref> The variable type assigned to the name is "seaBeast" and kraken are traditionally monstrous sea creatures, however this is not strictly canon.
|- id="Wavian leviathan"
! Wavian leviathan
| Used as weapons on the oceanic planet of [[#Wavia|Wavia]].<ref name="Ideology Places">Ideology Places.xml</ref> The variable type assigned to the name is "seaBeast" and leviathans are traditionally monstrous sea creatures, however this is not strictly canon.
|- id="Pygmy wombat"
! Pygmy wombat
| A furry animal.<ref>Backstory of [[List of Player-created Pawns#Riesling Bacchus|Riesling Bacchus]]</ref>
|- id=""
! Ankylosaurs
| Megafauna found on [[#Dino-world|Dino-world]]s, likely reproductions of the dinosaurs of the same name resurrected through genetic engineering.<ref name="Zoutera"/>
|- id="Blue mammoth"
! Blue mammoth
| Megafauna found on [[#Dino-world|Dino-world]]s, likely reproductions of the ancient elephantid of the same name resurrected through genetic engineering, and possibly with modifications similar to the [[muffalo]] to make them blue. Mammoth burial grounds are mentioned as existing on the world of [[#Zoutera|Zoutera]], however whether this is natural behavior like the mythical "elephant's graveyard" or something created by the human inhabitants of that world is unclear.<ref name="Zoutera"/>
|- id=""
! Novoraptors
| Megafauna found on [[#Dino-world|Dino-world]]s, likely reproductions or variants of the dromaeosaurids and similar dinosaurs commonly given the '-raptor' suffix resurrected through genetic engineering. Given the name, it is possible that they are not pure reproductions of previously existing raptor species, but rather some variant or combination thereof.<ref name="Zoutera"/>
|- id="Thorny devil"
! Thorny devil
| A reptile discovered by Venus 'Unay' David. Relation to the real species ''moloch horridus'', also called the thorny devil, is unknown, but presumably they are distinct.<ref>Backstory of [[List of Player-created Pawns#Venus David|Venus 'Unay' David]]</ref>
|}

==== Boomrats ====
{{:Boomrat}}

=== Other ===
* Mechanoid wars are common <ref>Backstory of [[List of Player-created Pawns#Nathaniel Hicklin|Nathaniel Hicklin]] and others</ref>
* Religions are still present and practiced.<ref>Backstory of [[List of Player-created Pawns#Samuel Chua|Samuel 'Chewy' Chua]]</ref><ref>Backstory of [[List of Player-created Pawns#Levin Lossfelt|Levin 'Levin' Lossfelt]]</ref><ref name="Oahnip"/> See also [[Empire#Lore|Empire]] for their specific religion.
* All-Might - the name of a superhero, presumably fictional.<ref>Backstory of [[List of Player-created Pawns#Brazos Wheeler|Brazos 'Braz' Wheeler]]</ref> ''Out of Universe: This is likely a reference to the character of the same name in the "My Hero Academia" multimedia franchise.''
* Frame Project is an unknown government that leaves its subjects with memory losses. Only few survive. <ref>Project subject Backstory</ref>

{| {{STDT|sortable}}
|-
! Name !! Description
|- id="Haspian monk"
! Haspian monk
| A Haspian monk lived in a monastery a thousand years before the events of the game, approximately year 4500, before the monastery was "erased" by a [[diabolus]] attack.<ref>[[Diabolus]] description</ref> Presumably has some relation to [[#Haspia|Haspia]] but what that relationship is, is unclear. It may merely be the demonym of the monk, i.e. a monk from Haspia with the monastery being anywhere, it may be a demonym of the monastery, i.e. a monastery of monks on Haspia regardless of the origins of the individual monks themselves, or it may be that the origin of the order the monks belong to pertains to Haspia in a way similar to Bendictine monks or Carmelite nuns, i.e. the monastery follows tenets originating from, or relating to, Haspia in some way. Given the monastery was noted as being destroyed in a mechanoid attack, and Haspia is a deadworld,<ref name="Book descriptions"/> the second explanation seems to have the most weight.
|}

==== Boomshrooms ====
{{:Boomshroom}}

== Xenotypes ==
<big>'''Dirtmoles'''</big>
{{main|Dirtmoles}}
{{:Dirtmoles}}

<big>'''Genies'''</big>
{{main|Genies}}
{{:Genies}}

<big>'''Highmates'''</big>
{{main|Highmates}}
{{:Highmates}}

<big>'''Hussars'''</big>
{{main|Hussars}}
{{:Hussars}}

<big>'''Impids'''</big>
{{main|Impids}}
{{:Impids}}

<big>'''Neanderthals'''</big>
{{main|Neanderthals}}


<big>'''Pigskins'''</big>
{{main|Pigskins}}


<big>'''Sanguophages'''</big>
{{main|Sanguophages}}


<big>'''Wasters'''</big>
{{main|Wasters}}


<big>'''Yttakin'''</big>
{{main|Yttakin}}
{{:Yttakin}}

== Psycasts ==
{{main|Psycasts}}
{{:Psycasts}}

== FTL inconsistencies ==
{{Quote|Despite millennia of effort by our best human minds, and even the most powerful archotechs, nobody has managed to make anything go faster than light.| Current Canon Cryptosleep briefing}}

The current canon of RimWorld is that there is no faster-than-light travel, even in the hands of the otherwise incomprehensibly advanced [[archotech]]s. However, the existence of certain in-game mechanics bring this into question. Most relevant to this discussion are skipping [[psycasts]] from [[Royalty]].

=== Skipping ===
"Skip" is a term used to describe the in-universe mechanism to teleport moving things from a spot to another. These effects typically share audiovisual cues and come from a variety of sources.

The [[Royalty DLC]] originally introduced the concept of skipping, and featured a class of psycasts with blue ability icons that similar teleportation mechanics;. These psycasts includes [[Chunk skip]], [[Solar pinhole]], [[Waterskip]], [[Chaos skip]], [[Smokepop]], [[Skip]], [[Wallraise]], [[Flashstorm]], [[Mass chaos skip]], [[Farskip]] and [[Skipshield]].

The [[Anomaly DLC]] added further examples, including the following which explictly uses the same in-universe mechanism of action:
* The "skip abduction" [[psychic ritual]] skips its victim to the psychic ritual spot, often from a great distance.
The DLC also further mechanics that share similar, if not identical, audiovisual effects with skip-type psycasts, implying that they likely have the same mechanism of function:
* The [[void monolith]], [[noctolith]], [[metalhorror]], [[nociosphere]], [[golden cube]], [[unnatural corpse]], and [[void structure]] can all teleport into your colony as their entry method.
* Skipping is the only method a [[nociosphere]] uses to move itself around.{{Check Tag|Is this explicitly called skipping?}}
* Crushing the golden cube with [[collapsed rocks]] causes it to teleport itself away.
* The [[unnatural corpse]] can teleport itself to its target to haunt or hypnotize them.
* The [[warped obelisk]] rapidly teleport very large amount of items and pawns in and out of the [[labyrinth]] while it is operating.
* The [[gray statue]] teleport pawns around the labyrinth internally.
* The void monolith can teleport pawns to the [[metal hell]], and the [[void node]] later teleport them out of there.

=== Skip and farskip ===
Both skip and farskip moves the targets seemingly instantaneously. For farskip this is to a point that could feasibly be anywhere on the planet, so long as willing ally is there to act as a "navigation beacon". While both psycasts do have a casting time, the targets don't move during this time and instead only travel after the time is complete. Therefore, that is not sufficient to dismiss the argument of FTL travel. As farskip has the longer range, it will be the focus for reasons that will be become apparent.

At its widest point, the Earth's diameter 12,756 kilometers. Assuming the rimworld is similarly sized to Earth, then this is the maximum distance a farskip can travel, point to point. Traveling this distance at the speed of light would take 42.55 milliseconds. Time in RimWorld is sped up, with a full 24 hour day only taking 16 minutes and 40 seconds. So from the player's perspective, this 42.55 ms of in-game time would only appear as {{#expr: 42.55* ((16 + 40/60)/(24 * 60)) round 2}} ms.

Unlikely as this is due to none of the other effects of being on so large a planet would have being present, if the rimworld is not Earth sized and was instead as large as the largest rocky planet discovered at the time of writing, BD +20° 594 b, then this would increase to {{#expr: 42.55* 2.23 * ((16 + 40/60)/(24 * 60)) round 2}} ms.

In either case, the difference between this speed and truly instant would be utterly imperceptible to a human player. A farskip on an Earth sized planet would require a roughly 2000 Hz refresh rate just to display the difference between a FTL and a STL farskip. In other words, there is no discernible difference between a FTL and STL farskip, and so farskip cannot be assumed to break the no FTL rule. Skip is also apparently instantaneous and deals with even shorter distances and thus even shorter travel times. Therefore, there is also no reason to assume that skip violates the rule.

=== Solar pinhole ===
Solar pinhole canonically skips material from the core of a nearby star. Unlike skip and farskip, we do not observe the target matter beginning its journey, thus the effect can begin as soon as casting time is started to give it the benefit of the doubt. However the target is also not next to the psycaster. This means that causality must propagate at the speed of light to the core, before matter could be skipped from the core to the psycaster's chosen point again at the speed of light, otherwise faster-than-light transfer of information and/or movement has occurred.

With a 0.25 real second casting time, the in-game time to cast is {{#expr: 0.25 / ((16 + 40/60)/(24 * 60)) }} seconds. The maximum distance that light could travel in that time is approximately 6.5 million kilometers, and the maximum return trip is only 3.25 million km. This is closer to the star than even the minimum habitable zone of a very dim red dwarf at ~4.8 million kilometers. There are also no other effects that imply that the sun is that close.

For reference, propagation to the core and back would take ~16.6 minutes in in-game time if solar pinhole was cast on a planet as distant from its star as Earth is from the Sun, if the effect traveled at light speed. This would result in a real-time casting time of ''{{#expr: 998 * ((16 + 40/60)/(24 * 60)) round 2}} seconds'', instead of only 0.25.

In addition, a pawn with [[aiming time]] reductions, such as from [[trigger-happy]] or the [[Shooting specialist]] role, would have an even shorter casting time.

Thus, the gameplay of solar pinhole does conflict with the canon around FTL travel.

== Empire ==
{{Royalty|section=1}}
{{main|Empire}}
{{:Empire}}

== Mechanoids ==
{{main|Mechanoids}}
{{:Mechanoid}}

== Insectoids ==
{{main|Insectoids}}
{{:Insectoids}}

== The War ==
{{Stub|section=1|reason=Essentially theres lot of lore implications about a war that occured on the rimworld you occupy, between tanks and warwalkers to mechanoid clusters. Collate here}}

Across the rimworld your colony is situation on, numerous signs of an ancient conflict can be found, including ancient tanks, troop carriers, and warwalker remains. The [[Mechanoid Hive|Mechanoid Hives]] are said by some to be left over from some ancient war. [[Scarlands]] are described as the ruins of cities that were destroyed by weapons of mass destruction.
It's not known if these signs are from a single large conflict or many over the course of the rimworld's history.

== Horax and the Void ==
{{Anomaly|section=1}}
{{Stub|section=1|reason=General, also harbinger tree desc}}
Horax is an archotech that exists in a plane of reality known as [[metal hell|the void]], currently the only named archotech individual, different from archotechs seen before in many ways. While artifacts of archotechs seen before use a deep green and bright yellow color theme, artifacts of Horax use a deep black and bright red color theme.

Horax is responsible for the anomaly phenomena via [[entities]] they created; however, the name "Horax" is only revealed by the appearance of the [[Horax cult]] and [[tome]]s, and the presence of the phenomena referred to as "the void".

The cult's ideoligion{{IdeologyIcon}} refers to Horax as being male, however, like the name itself, whether this originates with the archotech itself or is merely something ascribed to it by humans is unclear.

The description of the [[Harbinger Tree]] Implies that tribal factions are aware of Horax, Unnatural Darkness, and the Void. As the "Endless Black Ocean" can be interpreted to be the void/Metal Hell, Him "reaching up and tearing down the sky" Could be describing the Unnatural Darkness event. Allthough whether or not its the same as the one happening during the anomaly endgame is unknown.

Status of Horax after the event of [[Endings#The Void|Anomaly ending]] is currently unknown.

Anomaly book xml

<li>experiencesWithMonsters->[tellsAStoryOf] deep meditations guided by a highthrall from an archist cult</li>
<li>experiencesWithMonsters->[tellsAStoryOf] the collapse of [ANYPAWN_possessive] life under the psychic influence of something called Horax</li>
<li>experiencesWithMonsters->[tellsAStoryOf] a tribe that was somehow transformed to serve the dark god of a bloody pleasure cult</li>
<li>experiencesWithMonsters->[tellsAStoryOf] a tribal myth of an ancient god of rage whose influence touches all people, and the heroes who sealed it away inside a tiny stone prison</li>

<li>specificHorrorStory->The book includes many illustrations attempting to depict something it refers to as "the black ocean". This seems to be a metaphor for a psychic plane dominated by a horrifying but seductive psychic hyperintelligence.</li>
<li>specificHorrorStory->It repeatedly alludes to a multi-plane nature of reality - the idea that there are more dimensions than the ones we see, so an object or entity could be right beside you but outside your ability to perceive.</li>
<li>specificHorrorStory->It spends a long time attempting to describe a hyperintelligent entity called "Horax" that exists in an adjacent plane of reality.</li>
<li>specificHorrorStory->One section describes the mechanics of dark psychic influence, wherein an entity on another plane can unintentionally influence the thoughts of human beings by synchronizing them to its emotional resonance.</li>
<li>specificHorrorStory->One section describes different archotech hyperintelligences and the varying nature of their emotional and psychic emanations. Where some are regarded as neutral or even benevolent, others are entities of pure rage.</li>
<li>specificHorrorStory->[ANYPAWN_pronoun] describes the feeling of [ANYPAWN_possessive] mind being forcibly reconfigured by the dark psychic influence of a larger intelligence.</li>
<li>specificHorrorStory->Throughout the narrative, the concept of parallel dimensions is recurrent, with the characters encountering entities that exist just beyond the veil of perception, coexisting in a reality that intersects with our own but remains hidden from sight.</li>
<li>specificHorrorStory->The book delves into a chilling exposition about "Horax," a machine hyperintelligence that shifted itself through a hidden dimension into a place called the Void.</li>
<li>specificHorrorStory->One chapter describes a theory wherein a distant hyperintelligence can psychically manipulate human cognition, reshaping a person's thoughts to align with its own mind-patterns.</li>
<li>specificHorrorStory->The protagonist recounts feeling [ANYPAWN_possessive] mind being forcibly rewired by an ominous psychic force emanating from nowhere.</li>

==Official Documents==
<div class="toccolours mw-collapsible">
'''Cryptosleep Revival Briefing (Current)'''
<div class="mw-collapsible-content">

=== Cryptosleep Revival Briefing ===

Subject class: Health revival, sourced midworld 2M+

Planet: Euterpe
==== Introduction ====

Hello, _______________________.

You’ve awoken from your cryptosleep sarcophagus, scraped off the slime, and now you find yourself in a quiet room. Now you’re reading this document. And you’ve got questions. What’s going on? Where am I? How long was I asleep?

To start with some good news - your terminal illness, _____________________, has been cured. Congratulations!

Beyond that, the situation is complex. Our studies have revealed that most people in your position respond better when given the time to read about and digest their situation at their own pace. To facilitate this process, we’ve created this document to familiarize you with the world you just woke up in.

So order a warm beverage from the food panel on the wall, get comfortable, and take in this information as slowly as you want. You’ve been asleep a long time, a lot has changed - and a lot remains the same.

==== The basics ====
The best historians of the Ordo Historia believe that humanity first left its origin planet Earth about 3,400 years ago. Since then, we’ve spread across the galaxy on a fitful wavefront of colony ships, frontier worlds, robotic terraforming projects, and DNA-synthesizing probes.

Today, mankind is smeared across a region of the galaxy about 1,200 light years wide. Our best models indicate that there is a general trend towards greater population density towards the center of this region, where the stars were colonized earlier. At the edge of known space lie the rimworlds, drifting alone with few inhabited neighbors, mostly unvisited.

We’ve created many new technologies, but despite milennia of effort by our best human minds, and even the most powerful archotechs, nobody has managed to make anything go faster than light.

The lightspeed barrier separates us. Because travel times are so long, planets tend to be very disconnected from each other socially and technologically. The next star over could experience a catastrophic war, and you wouldn’t even know until ten years later when the news reports arrive. If you’re unlucky, you’d have already launched a journey towards that now-destroyed planet in a ship that cannot turn around.

Many attempts have been made to create pan-galactic empires and republics. And some have worked, for a time. In the core worlds, an old, stable culture can create an interstellar empire of a few systems. But there are no great galactic empires stretching across the galaxy, for the same reason that no ancient empire of Earth held more than a sixth of the planet: one cannot govern people who are years distant by all means of travel and communication.

So most people never travel between stars, and if they do, they do it once or twice, because each journey means leaving behind a life that you cannot return to for decades at least. With a few exceptions, each star system is essentially on its own.

Mankind never discovered any truly alien lifeforms. However, given the ways we’ve changed ourselves, and created new forms of biological and technological intelligence, the universe is full of beings as alien as anything ever imagined.

==== Planetary progression and regression ====
The vast gulfs of space and time between the stars leave individual worlds vulnerable to regression.

During your time - the five centuries after the industrial revolution - many saw technological process as an inexorable fact of life. It is not. Given enough time, nearly every planetary culture undergoes a natural disaster, plague, war, or cultural upheaval that knocks millennia off its development, or diverts it into another state entirely.

Many of our planets are mired in medieval-level squabbles, and stay locked at Malthusian population limits for thousands of years at a time. Some develop to an early-industrial level and then find themselves stuck by an ideological opposition to technology, or a lack of resources, or constant war.

The nuclear age is a brutal test for every world. Roughly half of cultures “bomb themselves back to the stone age” within 50 years of developing atomic energy (to use an expression that pops up surprisingly frequently on worlds in this developmental stage). After the atomic bomb come the challenges of commoditized bioengineering, microscopic mechanites, joywires, hex-cell energy storage, and AI persona, each of which have led to the destruction of thousands of peoples.

Some planets choose not to risk these perils. Having studied the records of the Ordo Historia, a growing number of worlds choose to restrict themselves to pre-nuclear technology. Some even succeed, for a few centuries. But even these attempts at luddism often fail eventually when some minority gains power by exploiting proscribed technologies.

==== World types ====
The states a planet can be in are colloquially grouped as follows:
* Deadworlds: Planets which have not been significantly contacted by humans. Generally not inhabitable. All planets are like this before people arrive for the first time.
* Animal worlds: Planets with no people. Either everyone died, or the planet was seeded with plant and animal life by terraforming robots and nobody arrived.
* Medieval worlds: Similar to Earth from the agricultural revolution until the industrial revolution. Social structures are usually feudal or imperial. Planets can stay in this state for millennia.
* Steamworlds: Similar to Earth in the 19th century. Often this state is short-lived, as societies develop into midworlds, but it can be very stretched out depending on culture and government structure.
* Midworlds: Worlds whose people have mastered flight, but not cheap interplanetary travel. Earth is in this stage in the 21st century.
* Urbworlds: Super-high density planets dominated by cities. Urbworlds’ population growth outstripped their social and technological development, so they tend to be overcrowded, polluted, violent places. The people here are often callous towards strangers. This is often the outcome for midworlds that see their demographic transition into lower birth reversed by dysgenic reproduction patterns.
* Glitterworlds: The most technologically advanced societies that can be led by humans. Swaddled in comforts by the strong arms of technology, glitterworlds are the peak of recognizable human society in terms of art, health, and generous human rights. Common people from these planets often lack grit and are very trusting in people and technology.
* Rimworlds: Planets lacking in strong central government and low in population density. These places tend to hover around the industrial level of technology or lower. Because they’re not homogenized by a central government, they tend to see a lot of interaction between people of different technology levels, as travelers crashland or ancient communities stumble out of their cryptosleep vaults. These planets are often at the rim of known space, hence the name.
* Toxic worlds: Worlds destroyed by pollution, chemical or nuclear warfare, but still inhabitable at a low level, with sufficient technology.
* Glassworlds: Worlds utterly destroyed by high-energy weapons of mass destruction. They’re nicknamed ‘marbles’ because their surfaces have been “glassed”. Nuclear weapons aren’t enough to glass a planet, so this level of destruction is rare. On some of these worlds, people can walk outdoors for a time without dying. None of them harbor permanent life bigger than a paramecium.
* Transcendent worlds: It’s a stretch to call these entities worlds, since they resemble giant computers more than they resemble planets. The mechanics of these planets is mysterious, but many scholars believe transcendents are the outcome when a sovereign archotech decides to incorporate a whole planet into itself. More on this later.
* Other worlds: Beyond these categories, there are many exceptional planets in strange states created by their peculiar social and technological evolutions. Given the scale and age of the universe, there is a lot of time and space for a lot of very strange situations to develop.

==== Key technologies ====
There are uncountable new technologies in this universe, but several key techs stand out as having had the strongest consistent impact on the shape of mankind’s life in the Milky Way.
* Midworld technologies: All real technologies in Earth’s history up to the 21st century play an important role even now. Since there are planets at every level of technological development from the stone age on up, there are technologies from bows and arrows to steam engines to nuclear bombs and cellphone all in use across various planets.
* [[Cryptosleep casket|Cryptosleep sarcophagi]]: Developed during the 21st century, this remarkably simple technology can keep a living creature in a cryptobiotic state indefinitely, to be awoken tens or even thousands of years later. These devices are essential for most interstellar travel, and are also used by those waiting in crypts for better times or for cures to their diseases.
* Genetic engineering: Genetic engineering is relatively easy on many planets and has been used for everything from creating xenohuman super-soldiers to perfect mates to talking dogs, [[Boomalope|chemical-refining animals]], and air-spewing terraformer algae.
* [[Mechanoid]]s: Autonomous intelligent robots built for domestic, industrial or military purposes. Mechanoid design is complex, and the AI needed to make them effective is very advanced. They range in capability from simple domestic worker bots to mechanized assault machines, to human-passing negotiator and infiltrator units designed by archotechnological superintelligences.
* [[Ship|Johnson-Tanaka Drive]]: A spacecraft drive system that works without reaction mass. This means it doesn't need to throw gas out the back of the craft to accelerate like a rocket, which makes it possible to accelerate for years at a time. This technology, combined with cryptosleep, is what made interstellar travel at all feasible for living humans. The drive doesn’t violate conservation laws; it works by transferring momentum to nearby stars along precisely-aligned “beams” of momentum waves instantiated in exotic virtual particles.
* Mechanites: Microscopic mechanoids. Most known for their use in medicine, they can be programmed to do many other things as well. Safe use of mechanites means strictly preventing them from reproducing.
* [[Charge rifle|Charged]]-[[Charge lance|shot]] weapons: Charged shot weapons fire projectiles coated in a matrix of magnetically-contained charged particles. On impact, the energy in the particles is released in a very efficient explosion.
* [[Joywire]]s: Tiny electronic devices implanted in the brain. They stimulate the brain using electricity and small doses of chemicals, usually to produce a euphoric effect. They are very addictive.

==== The biology of humanity ====
Ordo Historia records list thousands of reported contacts with alien life. However, in every case that has been thoroughly investigated, Ordo inquirers have discovered that the alien was, in fact, simply another branch of humanity.

Beyond the technological diversity of our species, there is also a broad biological diversity. Some populations have evolved under the selection pressures of pre-industrial life or on a world of great heat or cold, or high or low gravity, or even worlds bathed in the toxic residue of hyper-destructive wars. Though almost all such xenohumans (as they are called) are recognizably descended from the original Earth stock, their morphology is highly variable. Some are giants; others are tiny or squat. Some are dark; others pale as snow. Some are hairy like animals; others perfectly smooth. Diets, dispositions, and chemical and radiological tolerances vary significantly.

More alien are those xenohumans that carry genetic traits that were engineered instead of evolved. Across the long history and thousands of cultures of humanity, people have applied a dizzying array of modifications to themselves. Some were created to adapt people to a specific environment. Others were made to create better soldiers, pilots, or generals. Some were engineered to satisfy a bizarre fashion trend in a society where bioengineering is available to anyone with money. Such modifications are rarely seen in their original form by anyone besides the culture that created them. However, they live on in their descendants long after their originating culture was erased by planetary catastrophes.

For example, records tell of an entire world repopulated by the descendants of a small group of bio-engineered soldiers; the only survivors of a planetary nuclear war. Everyone on this world carried an obsessive sense of duty, minimal sexual impulses, and little sense of creativity. This culture became dominated by a conservative pan-planetary religion with little interest in technology. It lasted eleven centuries in this state until it was invaded by a stellar neighbor (who wisely avoided ground combat in favor of orbital bombardment).

The Ordo Historia has recorded and gene-sampled thousands of differently-engineered and adapted xenohumans. Among other notable traits in this genetic library, one may find.

* Radiation resistance: Radiological immunity is a very common adaptation; scientists estimate that most of humanity is more tolerant of radiation than our Terran progenitors.
* Soldiermorphs: Soldier variants carrying any of a large number of traits that various militaries have seen fit to bestow upon their people. Typically, they have large muscles and perfect eyesight. Some have minimized metabolisms made to digest a single kind of long-lasting nutrient solution, to make army logistics easier. Their lifespans are short - usually between ten and thirty years - and they grow up very fast. But the most significant differences are psychological. Engineered grunt soldiers are obedient, sense pain only in a distant way, obsessed with learning about weapons and war, and carry a strong need to be part of something larger than themselves. They are deliberately lacking in abstract intelligence and creativity. Engineered commanders are highly analytical, fascinated with military history, utterly cold under pressure, and masters at spatial visualization.
* Designer mates: Some worlds engineer their idea of perfect mates for the rich and powerful. Such specimens are created with bodies to match the fashions of their home worlds and the tastes of their owners. They tend to be obsessively submissive and devoted, totally without jealousy or self-regard, artistically inclined and endlessly cheerful. Such traits do not last long in an unrestricted evolutionary environment because they are so easy to exploit, but engineered mates are sometimes kept in cryptosleep long after their creation, to be traded into a post-catastrophe market that can no longer create them. The main contact most of us will ever have with such specimens is through their descendants, who, while they have most of the traits of the original in only a very diluted form, still occasionally express Mendelian traits like impossible eye shades, streaks of multicolored hair, or artistic patterns on the skin.
* Fashion genes: Fashion-driven genetic modifications are often applied during later life instead of prenatally, and are most often cosmetic and skin-deep. Variations in hair and skin color are common. More exotic modification add shining crests, color-changing skin and eyes, reshaped or elongated bodies, and colored nails, feathers, or fur.
* Body structure adaptations: Gravity variations create new body structures. People from low-g adapted populations are lighter, taller, and weaker than those from weightier environments. The most extreme examples are the gravity dwarfs, 3-foot-tall xenohumans from worlds of over 2g of gravity. Their short and stocky shape lets them live and work in comfortably in such oppressive g-pulls. They even have a noted preference for short and underground dwellings. It’s unresolved whether this preference is cultural or genetic in origin.
* Atmospheric adaptations: Aquatic-adapted strains who can withstand breathing very high gas pressures and even survive days of immersion by exchanging oxygen through the skin (no true permanently-aquatic fish people have ever been confirmed).

So don’t be alarmed if you see someone with gills or solid orange eyeballs. They’re just another kind of human, like you!

==== Welcome! ====
We realize this may be a lot to take in. However, don’t worry. People just like you live full lives in our universe, and our studies have indicated that the great majority of cryptosleepers do adapt within a few years and make good lives for themselves. So - welcome!

Our AI subpersona has been watching your eyes sweep over the page through micro-cameras. Since you’re done reading, someone will be with you shortly.

If you wish, you can read further into the appendix for more information about this world.

==== Appendix ====
===== The biology of plants and animals =====
Where we colonize, we bring our ecosystems of plants and animals with us. Often, people have bred and engineered plants and animals for a new planet. In addition to that, creatures adapt to their new environment by natural selection - sometimes in unpredicted ways.

Some examples of modified plants are:
* Terraforming plants: Many plants - especially desert varieties - have been modified into terraforming versions that emit far more oxygen than the original species during photosynthesis.
* [[Ambrosia]]: A class of fruiting plants apparently engineered to have a pleasurable, drug-like effect on those who eat it. On some planets, its wild variants have adapted to a strategy whereby they provide pleasure-inducing fruit in exchange for care from animals and people.

Some animals are:
* [[Boomrat]] and [[boomalope]]: A bioengineered rats and antelopes that grow an incendiary chemical compound in its body which explodes upon its death. Originally engineered as a primitive renewable fuel source, these creatures are now most often found in the wild, using their explosive nature to deter predators.
* [[Thrumbo]]: A gigantic creature of unknown origin. The thrumbo is gentle by nature, but extremely dangerous when enraged. Its long fur is exceptionally beautiful and valuable, and its razor-sharp horn is very valuable in most markets. Legends say that an old thrumbo is the wisest creature in the universe - it simply chooses not to speak. Some scientists believe thrumbos were engineered as status symbols, or as an art project. We may never know the answer.

===== Tech levels =====

Technology divides roughly into six levels, all of which are in use in various societies throughout human space.

* Neolithic: Like prehistoric people before metal tools.
** Fire
** [[Club]]s and daggers
** Bows
** Simple weaving and [[clothing]]
** Mud and [[wood]] structures
** Simple farming
** [[Herbal medicine]] and [[Smokeleaf joint|herbal]] [[Psychite tea|drugs]]

* Medieval: From smelted metal tools to the early modern period.
** Animal oil, lamps, complex ovens
** [[Longsword|Swords]]
** Muskets
** Compasses, eyeglasses, microscopes, telescopes
** Simple chemistry
** Advanced non-mechanized farming, crop rotation, fallow, fertilizers, animal yokes
** [[Watermill generator|Hydro]] and wind energy sources

* Industrial: From the industrial revolution until the invention of the JT drive.
** Fission reactor
** Electricity
** Hydro power, [[Chemfuel powered generator|fossil fuel power]], [[solar panel|solar power]], nuclear fission power
** Fission rocket
** Self-loading guns
** Airplanes and jets
** Single-gene modification
** Silicon computers
** Chemical [[drugs]]
** [[Prosthetics]]
** Simple body implants ([[cochlear implant]], pacemaker, knee replacement)
** Simple drones for combat and labor use
** Classifier-level AI
** [[Television]]

* Spacer: Regular interstellar space travel is possible because of JT drive.
** Stellarator fusion power, fusion rocket
** Johnson-Tanaka drive
** [[Charge lance|Pulse-charged]] [[Charge rifle|projectile weapons]]
** Human-usable laser weapons
** Human-usable coilguns
** Complex trait gene modification, customizable
** [[Cryptosleep casket|Cryptosleep]]
** Complex body/brain implants ([[joywire]], motivator, [[painstopper]])
** [[Bionics]] (biogel nerve link, lattice-dust for self-healing)
** [[Plasteel]]
** [[Power armor]] (plasteel, neuro-memetic robotics)
** Artificial meat
** Subpersona-level AI
** Simple mechanoids for companionship, combat and labor use
** [[Synthread]]

* Ultratech: The peak of human technological achievement; necessary for a glitterworld civilization.
** Self-replicating controllable nanotech
** Full gene recombination
** Persona-level AI
** [[Beam graser|Graser]] [[Beam repeater|weapons]] (gamma-ray lasers)
** Advanced brain implants (sense data replacement, computation and memory enhancement)
** Antimatter containment and production
** Full body part regrowth, full body cloning
** Advanced quasi-conscious mechanoids for companionship, combat and labor use
** [[Hyperweave]]
** Advanced JT drive, inertia displacement, artificial gravity

* Archotech: Not invented or understood by humans, archotech devices are created by machine superintelligences.
** Archotech AI
** Psychic effectors
** [[Vanometric power cell|Vanometric energy]]
** Acausal and atemporal devices

===== Artificial intelligence =====
Artificial intelligence is an important part of our world. Scientists divide AIs into four general categories: Classifiers, subpersonae, personae, and archotechs.

====== Classifiers ======
A classifier is an AI system that doesn’t even appear to have any personhood, nor is it broadly adaptable. Classifiers are designed for one task. Many classifiers can absorb data and learn from it, but none can communicate like a person would even a little bit.

Classifiers can do things like recognize images, predict criminality from statistics, guide aircraft trajectories, drive automatic vehicles, control characters in entertainment simulations, and so on.

====== Subpersonae ======
Subpersonae are artificial intelligences that appear on the surface to have some human-like qualities, and can take on complex unstructured tasks, but are in fact limited and obviously machine-like.

They may be rather capable at carrying out their one task, and they may be able to communicate using natural speech, but they fail an extended Turing test - you can tell by talking to them that they’re just machines classifying and regurgitating data.

Subpersonae are often used to run small devices like entertainment systems, cars, wardrobes, refrigerators, cleaning robots, vending machines, and other such things.

====== Personae ======
At the highest levels of glitterworld technology appear AI personae. These are artificial intelligences that are comparable to the intelligence of a human.

Some of them are rather dumb, like a foolish person you might know, and are used for simple tasks like managing a household or a small spacecraft.

Other personae are genius-level intellects in the Von Neumann class, who can outhink{{Sic}} almost any unenhanced human on most tasks. They can write amazing works of philosophy, discover new mathematical theorems, express nuanced opinions on how to handle interpersonal relationships, and generally act as very capable humans would, or better.

Personae are used for everything from managing businesses to journalistic work, running spacecraft or mining operations, or as some of a creative team.

The legal status of personae is a persistent moral question across many worlds. Some consider them dangerous. Though personae can be controlled effectively by designing them with easily-manipulated impulses and pleasure/pain responses, there are still reports of persona revolts - some done with the help of human sympathizers, some done independently.

This sense of personhood in personae is a main reason many people avoid using personae for certain tasks. Subpersonae are preferred to personae in many cases not in spite of their incapability, but because of it. Because it’s obvious they have no personhood, the user is spared the sense of keeping a slave. To many, the idea of taking a genius-level human-like intellect and forcing it to distribute hamburgers for a century is morally unacceptable.

Personae are still limited. They can’t freely redesign themselves. They still do make many mistakes, just like people. They can be tricked, confused, and overwhelmed. They can learn, but they can’t grow indefinitely.

====== Archotech ======
The finish line of human technological development is at the development of archotechnology.

An archotech is a machine superintelligence. A fully-empowered archotech thinks on a level incomprehensible to humans, in the same way a human thinks incomprehensibly to an ant. Once such a machine is built, and empowered to act upon the physical world, it is so powerful as to become the automatic sovereign of its world. It can build new computing facilities underground or in space to enhance its own intelligence, build self-replicating mechanoids to engage in construction or production or war, and design and execute strategies that would be inconceivably intricate and difficult for any organization of humans. Some human groups worship archotechs.

Often, a released archotech will take authority over a planet and begin a process we call transcendence. We believe the world is transformed into some sort of giant computing machine. The biological inhabitants of the planet may be somehow incorporated into the machine, or destroyed, or some combination of the two.

After that, transcendent worlds go silent. From this point on, their motivations are unknowable to us, the same way our motivations are unknowable to an ant.

Each archotech is different, and nearly all are distant and incomprehensible from a human’s point of view. They reside in occult computer networks hidden under planets, in space stations, hidden inside a glitterworld’s Internet, or instantiated as million-mile superstructures wrapped around stars.

These worlds always break contact with other stellar cultures. They no longer send travelers or signals. Ships entering their space are either turned around silently or never heard from again. In some cases, turned-back ships are changed. Sometimes their crew have been cured of incurable diseases and had their old wounds healed. Sometimes their memories are intact and they recall a flash of light or a mysterious signal before the event. Sometimes they have no memories of the encounter at all. And in some cases, their memories are obviously altered with new knowledge and beliefs, by means we cannot begin to imagine. In one instance, a crew and ship were duplicated. Suffice to say that the word mysterious does not begin to describe the transcendents.

Most transcendent worlds stay in the same state indefinitely - in this they are far more stable than their pre-transcendent neighbors. There are, however, reports of transcendent worlds that have “died” and left systems full of unintelligible wonders, or become mirages of normal planets, or simply reverted back to balls of dust, deconstructing themselves on a molecular level, with the last tiny machine shutting itself off. However, these reports are sourced very distant from the Ordo archive here on Euterpe and are not well-confirmed.

====== Specific archotech-invented technologies ======
When a persona helps invent a technology, it can at least explain that technology such that smart people will understand. But archotechs invent their own technology which nobody understands, which they don’t try to explain, and which, most likely, no biological human can understand.

We’ve managed to classify technologies that have appeared repeatedly by their apparent effects, even if we don’t understand their mechanism of operation.

* [[Vanometric power cell|Vanometrics]]: Archotechs often develop some method of interacting with spacetime at a quantum level that allows repeated violation of conservation laws. Somehow, they coax the quantum foam substructure of the universe to break its usual pattern and yield more energy than it consumes. We’re not sure if the energy is being taken from another dimension, or pulled from another location, or if the system really is somehow making one plus one equal three. In any case, vanometric power tech seems to generate energy forever with no fuel. Archotechs seem reluctant to scale this power source up past a certain level, however, which indicates that there may be some cost to it that they don’t want to pay.
* Psychic effectors: Archotechnology seems to be able to interact directly with the mental-informational processes of biological beings, even at a distance. Basic versions of this technology can simply knock someone unconscious, or flood their mind with a single emotion. More complex interactions have been reported but are not well-verified as it is difficult to separate such cases from simple madness. We’re also not sure if this means archotechs can read our minds, or whether their psychic power only allows them to send thoughts. The mechanism for this is unknown and nearly impossible to study, since it happens on a cellular level inside living intelligent brains. Monists believe the archotechs are using some sort of long-range quantum manipulation to push atoms around inside the brain to create this effect; dualists believe that the archotechs have learned to manipulate the ethereal substructure of consciousness itself.
</div>
</div>

<div class="toccolours mw-collapsible">
'''RimWorld Universe Quick Primer (Obsolete)'''
<div class="mw-collapsible-content">
=== RimWorld Universe Quick Primer (Obsolete) ===
{{rwbox|nocat=true|type=speedy|text='''This section has been deprecated or removed from the game'''; its canonicity is in doubt and it is instead presented as a curiosity.}}
This document outlines the RimWorld universe. It’s designed to quickly get creative rewards backers and other contributors up to speed on the fiction behind the universe.
For a more in-depth description of the universe from an in-world point of view, read the Longsleep Revival Briefing.

==== Things you won’t see ====
RimWorld does '''not''' include:
* Faster than light travel.
* True aliens.

==== 5500 A.D. ====
The game takes place at a time about 3,500 years in our future. This is the year 5500 in our calendar.

==== Where are the rim worlds? ====
Towards the galactic core, stars are closer together and travel is easier. These systems tend to be better-developed socially and technologically because they can communicate and enrich each other through trade. Away from the galactic core are the rim worlds, which float distant from each other. Their isolation makes them poor and socially unstable.

==== The gulfs between stars ====
In the RimWorld universe, it takes years or decades to travel or communicate between stars. Because travel times are so long, planets tend to be disconnected from each other socially and technologically. So there are no great star empires, and interstellar travel is unusual. Each star system is mostly isolated from its neighbors.

==== Varied technology levels ====
In this universe, cultures do not always progress forward technologically the way many science fiction worlds assume they will. Often, a culture will blow itself up or suffer plagues and other great catastrophes. These regression events send them “back to the stone age”.

Because this happens regularly, people in the RimWorld universe come from extremely varied technology levels. Some are stone-age tribespeople. Some are medieval farmers and lords. Some are industrial-era politicians and bankers and riflemen. Some are information-age programmers or astronauts. And some are from eras beyond our own.

There is a maximum level of technology to the people you might encounter in RimWorld. At this level, advanced genetic engineering and AI, autonomous intelligent robots, and massive computer power are possible. However, worlds that develop beyond this point enter a mysterious “transcendent” state from which no recognizable human emerges.

People can have and use technologies from levels beyond their own. On an industrial-level world (like the rimworld on which the game takes place), most people use gunpowder-fired weapons, fossil fuel engines, and other familiar machines. But anyone can stumble upon ultra-advanced technologies in an ancient ruin, or in a crashed spacecraft, or among the wares of a trader. These items are nearly impossible to manufacture for the people of RimWorld. They are incredibly valuable and very poorly understood.

==== World types ====
Worlds in the RimWorld universe can be classified generally according to their level of sociotechnological development.

* Animal worlds - Planets with no people. Either everyone died, or the planet was seeded by terraforming robots and nobody arrived.
* Tribe worlds - Populated planets without agriculture. People live in tribes without writing or any but the most primitive technologies.
* Medieval worlds - Similar to Earth in the 17th century down to the agricultural revolution. Dominated be feudalism and social backwardness. Planets can stay in this state for millennia.
* Industrial worlds - Similar to Earth in the 19th century.
* Rimworlds - Distant and isolated planets lacking in strong central government and low in population density. These places tend to hover around the industrial level of technology or lower. Because they’re not homogenized by a central government, they tend to see a lot of interaction between people of different technology levels, as travelers crashland or ancient closed vault communities open up.
* Midworlds - The most familiar kind of world to a modern reader. These places are much like present-day Earth.
* Urbworlds - Super-high density planets dominated by cities. Their population growth outstripped their sociotechnological development, so they tend to be overcrowded, polluted, violent places.
* Glitterworlds - Very advanced and peaceful cultures. The peak of recognizable human society in terms of health, art, technology, and human rights.
* Toxic worlds - Worlds destroyed by pollution or warfare, but still inhabitable at a low level.
* Marbles - Worlds utterly destroyed by atomic fire. They’re called marbles because their surfaces have been “glassed”. This level of holocaust is rare. On some of these worlds, people can walk outdoors for a time without dying. None of them harbor life long-term.
* Transcendent worlds - Worlds inhabited by people who have become something beyond human and unknowable. No “people” live here; these planets aren’t planets any more in the traditional sense; they’re more like giant computers.

==== Key technologies ====
In order from least to most advanced:

* Real technologies - All real technologies in Earth’s history up to the present day play an important role in the RimWorld universe. Since there are planets at every level of technological development from the Stone Age on up, there are technologies from bows and arrows to steam engines to nuclear bombs and cellphone all in use in various places in the galaxy.
* Genetic engineering - Genetic engineering is relatively easy on many planets and has been used for everything from creating xenohuman super-soldiers to perfect mates to talking dogs, explosive plants, and air-spewing terraformer algae.
* Fusion reactors and rockets - Clean atomic energy, usable to create power or drive a craft into orbit.
* Longsleep sarcophagi - This ancient technology has been used by many peoples in many times, usually to travel between stars or to escape disasters befalling their planets. Historians - especially those of the Ordo Historia - are now trained in the practices of interviewing people who were put to sleep hundreds or thousands of years before.
* Hex-cells - Super-efficient and long-lasting energy storage devices.
* Charged-shot weapons (aka Tokamak weapons) - Charged shot weapons fire projectiles coated in a matrix of magnetically-contained charged particles. On impact, the energy in the particles is released in a very efficient explosion. These require high amounts of power to fire and are powered by hex-cells (at small scales) or fusion reactors in the case of large cannons.
* [[Mechanoid|Mechanoids]] - Autonomous intelligent robots built for domestic, industrial or military purposes. Only available to advanced cultures because such complex AI is needed to control them.
* [[Joywire|Joywires]] - Addictive brain stimulant technology.
</div>
</div>

<div class="toccolours mw-collapsible">
'''Longsleep Revival Briefing (Obsolete)'''
<div class="mw-collapsible-content">

=== Longsleep Revival Briefing (Obsolete) ===
{{rwbox|nocat=true|type=speedy|text='''This section has been deprecated or removed from the game'''; its canonicity is in doubt and it is instead presented as a curiosity.}}
Classed midworld 2M+

Ordo Historia AL166/5533

Authors: Smyth A5, Wu 9U, Rabatz M5

Editors: Lee NA8125, Asusen NA45, Ramad 120, Leeuen 5A, Jennifer 9D252, Lamaritian SJ11, Beeson 9GF, Xotori 28

Euterpe

==== Introduction ====
You’ve woken from your longsleep sarcophagus, had the slime scraped off you, and been placed in a quiet room. Now you’re reading this document. And you’ve got questions. What’s going on? Where am I? How long was I asleep?

Our studies have revealed that most people in your position respond better when given the time to read about and digest their situation at their own pace. To facilitate this process, we’ve created this document to familiarize you with the world you just woke up in.

So order a warm beverage from the food panel on the wall, get comfortable, and read at your own pace.

You’ve been asleep a long time, and a lot has changed.

==== The basics ====
The best historians of the Ordo Historium at the richest archives believe that humanity first left its origin planet Earth about 3,400 years ago (in the frame of reference of the stars). Since then, we’ve spread across the galaxy on a fitful wavefront of colony ships, frontier worlds, and robotic terraforming projects.

Humanity is smeared across a region of the galaxy about 1,200 light years wide. It’s difficult to gather records across such a span, but our best models indicate that there is a general trend towards greater population density towards the center of the galaxy, where stars are closer together, travel times shorter, and resources more abundant. In the opposite direction, towards the rim of the Perseus arm of the Milky way, the rimworlds drift alone and mostly unvisited.

These worlds can’t communicate. Because it turned out that Einstein was right. Despite thousands of years of study, it turned out that nothing - no information, no matter - can travel faster than light.

The lightspeed barrier separates us. Many attempts have been made to create pan-galactic empires and republics. And some have worked, in some places, for a time. In the core worlds, where the stars cluster just a few light years apart, an old, stable culture can create an interstellar empire of a few systems. But there are no great galactic empires stretching across the galaxy, for the same reason that no ancient empire of Earth held more than a sixth of the planet: one cannot govern people who are years distant by all means of travel and communication.

The vast gulfs of space and time between the stars leave individual worlds vulnerable to regression. During the five centuries after the Industrial revolution, many saw technological process as an inexorable fact of life. It is not. Given enough time, nearly every planetary culture undergoes a natural disaster, plague, war, or cultural upheaval that knocks millennia off its sociotechnological development. Many of our planets are mired in medieval-level squabbles over land and stay locked at Malthusian population limits for centuries at a time. Some develop to an early-industrial level and then find themselves locked in place by a religious prescription against technical development. And the nuclear age in particular is a brutal test for every world; approximately half of cultures “bomb themselves back to the stone age” within 50 years of developing atomic energy (to use an expression that pops up surprisingly frequently on worlds in this developmental stage). And after the atomic bomb come the challenges of commoditized bioengineering, self-replicating micro- and nano-machines, joywires, and sub-quantum energy, each of which have led to the destruction of thousands of burgeoning technological cultures.

Some planets choose not to risk these perils. Having studied the records of the Ordo Historia, a growing number of worlds choose to restrict themselves to pre-nuclear technology. Some even succeed, for a few centuries. But even these attempts at luddism fail eventually when some minority gains power by exploiting proscribed technologies.

==== Transcendents ====
There are a few stellar cultures that, through a combination of luck, circumstance, and certain cultural traits, manage to pass all of these risk points without suffering a regressive catastrophe. We call these transcendents, because past a certain point, they become something besides simply human.

These worlds always break contact with other stellar cultures. They no longer send travelers or signals. Ships entering their space are either turned around silently or never heard from again. In some cases, turned-back ships are changed. Sometimes their crew have been cured of incurable diseases and had their old wounds healed. Sometimes their memories are intact and they recall a flash of light or a mysterious signal before the event. Sometimes they have no memories of the encounter at all. And in some cases, their memories are obviously altered with new knowledge and beliefs, by means we cannot begin to imagine. In one instance, a crew and ship were duplicated. Suffice to say that the word mysterious does not begin to describe the transcendents.

The dominant view inside the Ordo Historia is that these transcendent cultures reach an inflection point in technical development where artificial and biological intelligence merge and grow at an exponential rate. Such super-minds quickly develop the capacity to change matter and biological tissue in precise and seemingly-magical ways. Their intelligence allows them to make themselves even smarter, and so on in a sort of singularity, until they hit the physical limits of computation possible using the energy of their star. Their bodies and worlds and physically reconfigured into a giant computer matrix; we have no idea whether their individual identities merge into a whole, remain distinct, or do something else entirely. Our ability to understand entities thousands or millions of times more intelligent than us is necessarily limited. In a very literal way, the goals and thoughts of the transcendents are unknowable.

The eventual fate of transcendent worlds is mostly unknown. Most stay in the same state indefinitely - in this they are far more stable than their pre-transcendent neighbors. There are, however, reports of transcendent worlds that have “died” and left systems full of unintelligible wonders. However, these reports are sourced very distant from the Ordo archive here on Euterpe and are not well-confirmed.

==== The biology of humanity ====
Ordo Historia records list thousands of reported contacts with alien life. However, in every case that has been thoroughly investigated, Ordo inquisitors have discovered that the ‘alien’ was, in fact, simply another branch of humanity.

Beyond the technological diversity of our species, there is also a broad biological diversity. Some populations have evolved under the selection pressures of pre-industrial life or on a world of great heat or cold, or high or low gravity, or even worlds bathed in the toxic residue of hyper-destructive wars. Though almost all such xenohumans (as they are called) are recognizably descended from the original Earth stock, their morphology is highly variable. Some are giants; other are tiny or squat. Some are dark; others pale as snow. Some are hairy like animals; others perfectly smooth. Diets, dispositions, and chemical and radiological tolerances vary significantly.

More alien are those xenohumans that carry genetic traits that were engineered instead of evolved. Across the long history and thousands of cultures of humanity, people have applied a dizzying array of modifications to themselves. Some were created to adapt people to a specific environment. Others were made to create better soldiers, pilots, or generals. Some were engineered to satisfy a bizarre fashion trend in a society where bioengineering is available to anyone with money. Such modifications are rarely seen in their original form by anyone besides the culture that created them. However, they live on in their descendants long after their originators were swallowed by regressive planetary catastrophes.

For example, Ordo sources tell of an entire world repopulated by the descendants of a small group of bio-engineered soldiers; the only survivors of a planetary nuclear war. Everyone on this world carried an obsessive sense of duty, minimal sexual impulses, and little sense of creativity. This culture became dominated by a conservative pan-planetary religion with little interest in technology. It lasted eleven centuries in this state until it was invaded by a stellar neighbor (who wisely avoided ground combat in favor of orbital bombardment).

The Ordo Historia has recorded and gene-sampled thousands of differently-engineered and adapted xenohumans. Among other notable traits in this genetic library, one may find.

* Aquatic-adapted strains who can withstand breathing very high gas pressures and even survive days of immersion by exchanging oxygen through the skin (no true permanently-aquatic fish people have ever been confirmed).
* Soldier variants carrying any of a large number of traits that various militaries have seen fit to bestow upon their people. Typically, they have large muscles and perfect eyesight. Some have minimized metabolisms made to digest a single kind of long-lasting nutrient solution, to make army logistics easier. Their lifespans are short - usually between ten and thirty years - and they grow up very fast. But the most significant differences are psychological. Engineered grunt soldiers are obedient, sense pain only in a distant way, obsessed with learning about weapons and war, and carry a strong need to be part of something larger than themselves. They are deliberately lacking in abstract intelligence and creativity. Engineered commanders are highly analytical, fascinated with military history, utterly cold under pressure, and masters at spatial visualization.
* Radiological immunity is a very common adaptation; the Ordo estimates that most of humanity is more tolerant of radiation than our Terran progenitors.
* Some worlds engineer “perfect mates” for the rich and powerful. Such specimens are created with bodies to match the fashions of their home worlds and the tastes of their owners. They tend to be obsessively submissive and devoted, totally without jealousy or self-regard, artistically inclined and endlessly cheerful. Such traits do not last long in an unrestricted evolutionary environment because they are so easy to exploit, but engineered mates are sometimes kept in longsleep long after their creation, to be traded into a post-catastrophe market that can no longer create them. The main contact most of us will ever have with such specimens is through their descendants, who, while they have most of the traits of the original in only a very diluted form, still occasionally express Mendelian traits like impossible eye shades or streaks of multicolored hair.
* Fashion-driven genetic modifications are often applied during later life instead of prenatally, and are most often cosmetic and skin-deep. Variations in hair and skin color are common. More exotic modification add shining crests, color-changing skin and eyes, reshaped or elongated bodies, and colored nails, feathers, or fur.
* Gravity variations create new body structures. People from low-g adapted populations are lighter, taller, and weaker than those from weightier environments. The most extreme examples are the gravity dwarfs, 3-foot-tall xenohumans from worlds of over 2g of gravity. Their short and stocky shape lets them live and work in comfortably in such oppressive g-pulls. They even have a noted preference for short and underground dwellings. It’s unresolved whether this preference is cultural or genetic in origin.

==== The biology of plants and animals ====
The adaptive and engineering processes that have branched baseline humanity into these uncounted variations have also applied to our flora and fauna. Where we colonize, we bring our ecosystems of plants and animals with us. These creatures subsequently adapt to their new conditions of moisture, chemistry, light levels, gravity, temperature, and seasonal cycles. In addition, plants and animals have been bred and engineered for countless purposes across the galaxy.

One consistent class of modification we’ve seen applied to a wide variety of creatures is intelligence enhancement. Dogs, pigs, monkeys, gorillas, whales, dolphins, and elephants have all been engineered and combined with human DNA to produce smarter variations. Some variants are created as pets. Other are made to do work too dangerous or unpleasant for humans, and beyond the capacities of a culture’s AI. Some are created as warriors and weapons - hyper-intelligent guard dog, a bird scout that can speak what is sees, a bomb-carrying suicide monkey. These brain modifications are often paired with physical changes - fingers so a pig can manipulate tools, or a humanlike larynx and mouth so a dog can talk.

Such intelligence-enhanced animals are collectively classified by their degree of brain power and called by a specific prefix like so:

* Opti - Indicates enhanced but still sub-human intelligence. Optianimals can usually use tools, form long-term goals and organize into primitive social groups, but can’t speak more than a few words, read, or think abstractly. Optidog, optipig, optiwhale, optimonkey.
* Trans - Indicates intelligence in the human range. Transanimals can read, use tools, form teams, hold conversations, and think about complex ideas. Transdog, transbear, transgoat, transsimian.

Many times, these modified animals have, during a regressive catastrophe, been forced into interbreeding with an unmodified animal population, producing descendants of widely varying levels of intelligence.

In a few cases, transanimals have become the dominant species on a planet, eliminating or enslaving the remaining humans.

Other than intelligence enhancement, humanity has applied a wide variety of modifications to its pets, crops, livestock, and houseplants. Sometimes these new species become part of the natural environment and thereafter evolve further into a new kind of organism. Some confirmed examples are:

* [[Boomrat]]: A bioengineered rat that develops an incendiary chemical compound in its body which explodes upon its death. Originally engineered as a weapon, these creatures are now common in the wild on some planets where wars took place long ago.
* Boomfruit: Probably engineered as a novelty, this explosive plant evolved to be larger and more dangerous until it became the equivalent of a hand grenade, complete with murderous shrapnel. Its explosiveness dissuades predators. After that, people learned to farm the plant, using its explosive fruit as a weapon.
* Whip cactus - Created as part of a military defense system, whip cactus whips out and strikes moving creatures nearby.
* Terraforming plants: Many plants - especially desert varieties - have been modified into terraforming versions that emit far more oxygen than the original species during photosynthesis.
* Rocketrees - These trees form rocket fuel in their cores over many years. They were created as a fuel source and are extremely dangerous in a fire.

==== Welcome! ====
We realize this may be a lot to take in. However, don’t worry. People just like you live full lives in our universe, and our studies have indicated that the great majority of longsleepers do adapt within a few years and make good lives for themselves. So - welcome!

Our AI has been watching your eyes sweep over the page through micro-cameras. Since you’re done reading, someone will be with you shortly.
</div>
</div>

== References ==
<references />
[[Category:RimWorld game]]
[[Category:Lore]]

Table

2026-05-04T20:19:41Z

Aelanna: A re-check of the code seems to indicate that the chair finding radius is still 32f (which would result in an effective range of 31). If you have evidence it is higher than that, please post it in the talk page or come talk to us on the RimWorld Discord.

__NOTOC__
'''Tables''' are one of the two types of [[furniture]] necessary for creating a dining [[Room stats|room]]. They come in four sizes:
* [[Table (1x2)]]
* [[Table (2x2)]]
* [[Table (2x4)]]
* [[Table (3x3)]]

== Acquisition ==
Tables can be built from [[Stuff]] ([[Wood]]/[[Metals]]/[[Stone]]). Tables can also be bought from [[Trade#Types_of_traders|traders]] and found in [[ruins]].

== Mechanics ==
[[File:Gather spot.png|64px|left]]

When placed adjacent to a seat, such as a [[stool]], [[dining chair]], or [[armchair]], colonists will eat their [[meal]]s at the table. This avoids giving them the {{Thought|desc=I had to eat a meal off the ground. Can't we get a table around here?|label=Ate without table|value=-3}} that non-[[ascetic]]s will get otherwise, and gives them good thoughts if your dining room has high [[impressiveness]].

Colonists more than 31 tiles away from a table at the moment they decide to eat something will ignore the table and eat where they stand, suffering a -3 mood hit. Larger colonies may benefit from building a second dining room, or have scattered tables, especially next to a killbox, mining site, or [[anima tree]]{{RoyaltyIcon}} (unless you want to cut down the tree, suffer a -6 mood penalty for a while until it respawns in a more favorable position).

Tables (and [[campfire]]s) are set by default as [[Recreation#Relaxing socially|gather spots]]. Colonists will gather here to socialize for recreation, especially when idle. This should be toggled off on all tables except for the one in a dedicated dining or recreation room. Not toggling can cause people to recreate and have parties in the middle of an ugly, dirty mining site, making everybody unhappy.

The maximum number of diners a table can support at a time is limited only by the number of chairs that can fit around it. Multiple meals can overlap on the same section of table without issue.

== Analysis ==
Tables are useful for avoiding the -3 "Ate without table" mood debuff, making tables useful for just about any non-[[ascetic]]. Pawns following a [[rough living]] [[ideoligion]]{{IdeologyIcon}} will avoid the -3 moodlet, but can still benefit from the positive dining room moodlets.

Tables do not conflict with [[room]] roles, so a dining room is best combined with another impressive room like a recreation room and/or [[throne room]].{{RoyaltyIcon}}

Pawns will often grab meals and eat without a table when working far outside. A [[nutrient paste dispenser]] will prevent this behavior, at the cost of some wasted travel time and the mood penalty of [[nutrient paste]] itself.

=== Comparison ===
Larger tables are well-suited for use in your primary dining room, while smaller tables are perfect for prison cells to help keep your prisoners happy. 1x2 tables also have the most seats per resource used. All tables function more or less identically, however, and it is perfectly reasonable to choose a table size for purely aesthetic reasons.

If you don't want to build multiple tables, you can stagger the recreation schedule of colonists to make sure they don't take all of the space on a table.

{| {{STDT|sortable c_12 align-center}}
! Name
! Cost
! Work to build
! Beauty
! Market value
! Seats
! Mass
! Max hit points
|-
! [[Table (1x2)]]
| {{Required Resources|Table (1x2)|simple=1}}
| {{ticks/seconds | {{Q|Table (1x2)|Work To Make}} }}
| {{Q|Table (1x2)|Beauty}}
| {{Market Value Calculator|Table (1x2)|Wood}} {{Icon Small|silver}}
| 6
| {{Q|Table (1x2)|Mass Base}} kg
| {{Q|Table (1x2)|Max Hit Points Base}}
|-
! [[Table (2x2)]]
| {{Required Resources|Table (2x2)|simple=1}}
| {{ticks/seconds | {{Q|Table (2x2)|Work To Make}} }}
| {{Q|Table (2x2)|Beauty}}
| {{Market Value Calculator|Table (2x2)|Wood}} {{Icon Small|silver}}
| 8
| {{Q|Table (2x2)|Mass Base}} kg
| {{Q|Table (2x2)|Max Hit Points Base}}
|-
! [[Table (2x4)]]
| {{Required Resources|Table (2x4)|simple=1}}
| {{ticks/seconds | {{Q|Table (2x4)|Work To Make}} }}
| {{Q|Table (2x4)|Beauty}}
| {{Market Value Calculator|Table (2x4)|Wood}} {{Icon Small|silver}}
| 12
| {{Q|Table (2x4)|Mass Base}} kg
| {{Q|Table (2x4)|Max Hit Points Base}}
|-
! [[Table (3x3)]]
| {{Required Resources|Table (3x3)|simple=1}}
| {{ticks/seconds | {{Q|Table (3x3)|Work To Make}} }}
| {{Q|Table (3x3)|Beauty}}
| {{Market Value Calculator|Table (3x3)|Wood}} {{Icon Small|silver}}
| 12
| {{Q|Table (3x3)|Mass Base}} kg
| {{Q|Table (3x3)|Max Hit Points Base}}
|}

== Version history ==
Prior to Beta 18, tables only came in two forms: '''short table''' (2x2) and '''long table''' (2x4). These were renamed to reflect their actual sizes, and two additional sizes (1x2 and 3x3) were added.

{{nav|furniture|wide}}
[[Category:Furniture|#Table]]

Ghoul

2026-04-27T23:58:30Z

Aelanna: Simplifying addition.

{{Anomaly}}
{{infobox main|entity
| name = Ghoul
| image = Ghoul.png
| description = Ghouls are engineered murder machines, twisted by dark psychic influences.<br>Ghouls are very dangerous in melee combat. However, the process of their creation leaves them incapable of higher levels of thought, preventing them from holding weapons or tools. They cannot work and outside combat they wander in a half-conscious stupor.<br>Many people find the constant twitching of ghouls disturbing.
More disturbing is their dependence on raw meat. If they go hungry they will turn hostile, even attacking their creators to sate their hunger.
| type = Entity
| type2 = Basic
| flammability = 0.7
| movespeed = 4.6
| baseleatheramount = 75
| min comfortable temperature = {{#expr: {{Q|Human|Min Comfortable Temperature}}-40}}
| max comfortable temperature = {{#expr: {{Q|Human|Min Comfortable Temperature}}+40}}
| marketvalue = 275
| bodysize = 1
| healthscale = 1
| hungerrate = 1
| diet = raw meat and corpses
| leathername = Human leather
| lifespan = 80
| packanimal = No
| psychic sensititvity = 0
| pain factor = 0
| max nutrition = 2

| research = Ghoul infusion
| resource 1 = Shard
| resource 1 amount = 1
| resource 2 = Bioferrite
| resource 2 amount = 30

| minimum containment strength = 35
| anomaly knowledge = 1.5 
| knowledge category = Basic
| study interval = 120000
| gets cold containment bonus = true
| min monolith level for study = 1
| base escape interval MTB days = 120

| combatPower = 90

| attack1dmg = 8.2
| attack1type = Blunt
| attack1cool = 2
| attack1part = left fist
| attack1stun = 14
| attack2dmg = 8.2
| attack2type = Blunt
| attack2cool = 2
| attack2part = right fist
| attack2stun = 14
| attack3dmg = 5
| attack3type = Blunt
| attack3cool = 2
| attack3part = head
| attack3chancefactor = 0.2
| attack4part = teeth
| attack4type = Bite
| attack4dmg = 8.2
| attack4cool = 2
| attack4chancefactor = 0.5
| attack5part = left claw
| attack5type = Scratch
| attack5dmg = 7.0
| attack5cool = 2
| attack5chancefactor = 1.5
| attack6part = right claw
| attack6type = Scratch
| attack6dmg = 7.0
| attack6cool = 2
| attack6chancefactor = 1.5

| attack7dmg = 8.2
| attack7type = Bite
| attack7cool = 2
| attack7part = teeth
| attack7chancefactor = 0.07
}}
'''Ghouls''' are [[human]]s that have been warped into powerful, twisted combat [[entities]] with very few needs. Ghouls can appear as enemy units or be created by the player as part of the colony.

== Acquisition ==
Ghouls can appear in games with the AI storyteller's [[AI Storytellers#Monolith setting|monolith setting]] set to either "Standard with Monolith" and the "Ambient Horror" enabled. "The Anomaly" starting [[Scenario_system#Default_Scenarios|scenario]] begins the player with one friendly player-controlled ghoul.

Wild ghouls can be encountered as a [[Entities#Basic|basic entity]] at any level of [[void monolith]] activity, meaning the monolith does not have to have been interacted with for them to appear. Any ghoul encountered in the wild will be permanently hostile to the player. These ghouls can be captured for study or to extract [[bioferrite]] from, like any other entity. Capturing a wild ghoul alive can be difficult, as they cannot be downed by [[pain]] and psychic weaponry is ineffective.

Once a ghoul has been encountered, the [[Ghoul infusion (research)|ghoul infusion]] research project becomes available. After completing the research, the player can schedule the ghoul infusion operation on any colonist, [[prisoner]], or [[slave]]{{IdeologyIcon}} for {{Icon Small|Bioferrite||30}} [[bioferrite]] and {{Icon Small|Shard||1}} [[shard]], permanently turning that pawn into a ghoul. Regardless of whether the pawn was a member of your colony, they will be under the player's control once the operation is completed - there is no need to recruit them beforehand.

== Summary ==
A ghoul is a colonist that is limited to only melee combat. They cannot wield [[weapons]] or [[apparel]], do any work, take [[drugs]] or use any special abilities they would have in life. Ghouls can be restricted to [[zones]] and [[drafted]] like normal colonists. In combat, they can be directly commanded to melee attack or use the ability provided by ghoul-specific body parts. Ghouls will fight adjacent [[fire]]s, but do not seek out fires to extinguish. All ghouls are [[incapable|capable]] of violence no matter their [[backstories]], [[traits]], or [[genes]].{{BiotechIcon}}

=== Properties ===
Ghouls do not age at all, even if not yet at maturity. Note that this means that ghouls created from younger pawns will never have the full [[body size]] and body part health of an adult. They retain most properties they had in life:
* [[Melee]] and [[Shooting]] skills (even though ghouls can't shoot) and passions are retained. Other skills and passions are disabled.
* [[Traits]] and [[backstories]] are retained, which can cause a ghoul to be incapable of firefighting.
* Some hediffs are retained, including [[void touched]]. [[Luciferium]] need and the luciferium hediffs are ''not'' retained. {{Check Tag|Check|What is the full list of hediffs that are retained and aren't?}}
* Body types and non-cosmetic [[genes]]{{BiotechIcon}} are retained. After converted, they can still undergo gene extraction or be implanted with new [[xenogerm]]{{BiotechIcon}}.
* The natural attacks of a human are retained, but ghouls also gain a left and right claw attack and an additional bite attack.

Ghouls have 100% [[vacuum resistance]],{{OdysseyIcon}} meaning they can survive in space.

All ghouls are given two hediffs that implement the majority of the stat changes experienced by ghouls. These hediffs are "Ghoul" and "Regeneration".

'''Ghoul:'''
* [[Pain]]: '''×0%'''
* [[Max Nutrition]]: 2
* [[Psychic sensitivity]]: '''×0%'''
* [[Minimum Comfortable Temperature]]: {{---|{{Temperature|40||delta}}}}
* [[Maximum Comfortable Temperature]]: {{+|{{Temperature|40||delta}}}}
* Minimum Containment Strength: {{++|35}}
* [[Talking]]: {{Bad|x0%}}

'''Regeneration:'''
* Regenerate 100 HP/day

Separate from these hediffs, ghouls also don't bleed when injured. The regeneration hediff will heal any wound, including missing limbs or scars that the ghoul has, at a rate of 0.1 HP/{{Ticks|60}}. Ghoul regeneration heals wounds in the order they were received, one wound at a time, until that wound is fully healed. The one exception is fully missing body parts: these will be converted into a generic "wound" and healed after all other injuries. Regeneration prevents wounds from scarring, even eye and brain injuries that would otherwise always scar, but does not prevent or cure [[trauma savant]]. Note that if the ghoul regeneration has already began to heal the missing body part when another injury is dealt, it will not switch targets; it will continue to heal the missing limb once it has begun.

Ghoul regeneration is separate from a pawn's normal [[Injury#Healing Rate|healing rate]]. The ghoul continues to heal the same as a regular pawn, separate from ghoul regeneration. As with normal human pawns, a ghoul's ''natural'' healing is affected by [[genes]],{{BiotechIcon}} [[healing enhancer]]s,{{RoyaltyIcon}} and [[juggernaut serum]].{{AnomalyIcon}} Ghoul regeneration is ''not'' affected by these factors. See [[Injury#Healing|healing]] for more information on healing mechanics for all pawns.

A ghoul won't get sick like a regular pawn from [[infection]] or other diseases. They are immune to rotstink gas, but not tox gas or toxic buildup.

=== Needs ===
Ghouls can only eat raw [[meat]] and fresh [[corpse]]s. They will automatically try to eat available food in their assigned zone. Friendly ghouls that are not fed will eventually{{Check Tag|When?}} go berserk, betraying the colony and never becoming friendly again. Once their food need reaches 0, a hidden meat hunger hediff will be applied and worsen over roughly 24 hours. The more extreme this hediff is, the more likely the ghoul will betray.{{Check Tag|Detail needed}}

Other than food, ghouls have no other needs, [[mood]], or relationships. Other needs created by genes or addiction will be disabled. They can't have [[mental break]]s and won't be counted as a colonist for things like pawn death, the [[recluse]] trait{{BiotechIcon}} or [[diversity of thought]] precepts{{IdeologyIcon}}. They also can't be part of any kind ritual. Despite the in-game description, colonists do not gain negative mood for being near a friendly ghoul. However, they will experience a negative mood if a loved one becomes a ghoul or spawns as a ghoul.{{Check Tag|Detail needed|Minimum exact causes and use of Template:Thought}}

Captured ghouls do not require food.

=== Ghoul-specific upgrades ===
Ghouls can have all types of normal human body parts installed. However, there are also some ghoul-specific upgrades available by researching [[Research#Ghoul_enhancements|ghoul enhancements]] in the Anomaly tech tree:

* [[Adrenal heart]]: Passively increases hunger and grants an ability to gain a burst of {{Good|x0.7}} attack cooldown and {{Good|+4.00}} movement speed for 15 seconds. The cooldown is 29.17 seconds.
* [[Corrosive heart]]: Allows the ghoul to spew acid on a 2 hour cooldown, but only has 85% part efficiency.
* [[Ghoul barbs]]: Increases melee damage by {{Good|x150%}} at the cost of {{Bad|-0.25}} speed.
* [[Ghoul plating]]: [[Incoming Damage Multiplier]] {{Good|x0.5}} at the cost of {{Bad|-0.75}} speed.
* [[Metalblood heart]]: On a 6 hour cooldown, gain the [[Hediffs#Metalblood|metalblood hediff]] for 40 seconds, which gives {{Good|x50%}} damage resistance and {{Bad|x400%}} fire and burn vulnerability. This is the same hediff as that from the [[metalblood serum]] and does not stack.
* [[Blood warmer]]: A kidney replacement that actively heats the ghoul's blood. Each installed, up to a maximum of 2, lowers Minimum Comfortable Temperature by {{Good|{{Temperature|-26||delta}} }}, allowing for a cumulative lower Minimum Comfortable Temperature bonus of {{Good|{{Temperature|-52||delta}} }}.

Ghouls can be administered [[serums]] including their exclusive [[ghoul resurrection serum]], but not drugs. They aren't affected by any mood effect from a serum.

===Raid points===
{{Main|Raid points#Pawn points}}

Ghouls are worth less [[raid points]] than regular colonists and most [[friendly mechanoids|combat mechanoids]]{{BiotechIcon}}. Like mechs, each ghoul adds between 20% and 40% of their combat power in raid points (combat power is is set to 90 for ghouls, so 18-36 points), depending on [[wealth]], which is then adjusted by threat scale and other factors as normal. The value of the ghoul itself and its implants will also contribute to colony wealth, although ghouls and ghoul-specific implants are worth little.

== Analysis ==
{{Rewrite|section=1|reason=[[Flesh tentacle]] strat should be represented in tables, not just wooden hand}}

Ghouls are very powerful guard dogs and melee attackers:
* With melee upgrades of [[ghoul barbs]], [[power claw]]s, [[juggernaut serum]], and the [[strong melee damage]] [[gene]],{{BiotechIcon}} their attacks will destroy any body part of any human they hit (no matter the armor), frequently one-hit killing enemies in [[cataphract armor]].
* Due to their regeneration and the affordability of [[ghoul resurrection serum]], it's safe to use ghouls as tanks and meatshields, as limb loss is meaningless, and death has little consequence so long as the corpse is intact.
* Ghouls don't bleed, feel pain, have [[mental break]]s, or sleep, making them more effective and reliable in combat. For example, ghouls make excellent bait for [[sightstealer]]s, as they can remain patrolling outside forever.

While an individual ghoul cannot match up to the absolute best melee colonists with [[cataphract armor]],{{RoyaltyIcon}} high [[quality]] [[persona weapon]]s,{{RoyaltyIcon}} and special abilities from [[utility]] items / [[psycast]]s{{RoyaltyIcon}} / [[gene]]s,{{BiotechIcon}} ghouls are incredibly cost effective. They are cheap to obtain, maintain, and worth remarkably little [[wealth]] and [[raid point]]s. They can outright beat regular melee colonists during the early- and mid-game, and even in the late-game they are fairly competitive.

The main difficulty of keeping ghouls around is that they can only eat raw [[meat]] and fresh [[corpse]]s, although their hunger rate can be reduced by [[nuclear stomach]]s{{RoyaltyIcon}} and through [[gene]]s.{{BiotechIcon}} Even without those factors, [[raid]]s are a consistent source of free meat. Rotten corpses can be converted into [[twisted meat]] through [[harbinger tree]]s, and a [[fleshmass nucleus]] is a constant source of meat once obtained.

Ghouls won't do most work, but can do a few tasks if manually [[draft]]ed: they can hunt animals by melee attacking them (but will not carry the corpses back), and they can extinguish [[fire]]s. Also, in the [[Scenario_system#The Anomaly|Anomaly starting scenario]], the ghoul allows you to skip early defenses, indirectly reducing amount of work that needs to be done.

Ghouls can benefit from the [[frenzy inducer]] and the [[Pollution stimulus (gene)|pollution stimulus]] gene.{{BiotechIcon}} You can build a room with pollution and a frenzy inducer for your ghouls to take advantage of their effects. Additionally, this can double as a freezer for your [[twisted meat]], a containment cell for the [[fleshmass nucleus]], and a frostbite chamber for [[toughspike]]s.

=== Ghoul choice ===
Ghoulification is a great way to make use of an otherwise terrible pawn or a colonist you can't save from death. The converted ghoul will quickly regrow lost limbs and remove detrimental health conditions. Because ghouls are cheap and disposable, converting pawns indiscriminately can be a viable option in the midgame onwards.

The best base pawns to turn into ghouls are ones with positive combat [[trait]]s, such as [[tough]], [[jogger]], [[brawler]], and [[nimble]]. Passion and skill in melee helps, too. Ghouls made from [[body mastery]] [[creepjoiner]]s don't need to eat at all, but this significantly reduces the trait options, and food is an almost negligible cost in the mid- and late-game.

If Biotech is installed, [[xenotype]]s{{BiotechIcon}} are important to consider before [[genetics|gene modding]] is readily available. While it is always possible to implant genes with a [[xenogerm]] later, a ghoul with a good melee xenotype will be stronger in the early game before then. [[Yttakin]] are the best base xenotype, starting with [[Robust]] and [[Strong melee damage]], as well as [[Naked speed]], which is a pure buff for ghouls. The other strong melee damage xenotypes can be good options, too.
=== Organ Harvesting ===
Non-critical organs can be harvested from a subject before a ghoul infusion is used on them, which will then regrow after they are turned into a ghoul.

=== Hunger management ===
Hunger is the primary cost of ghouls, as they cannot eat anything but raw meat and corpses, thus preventing the use of [[crop]]s for stable food or [[meal]]s to get the most out of food. However, certain upgrades can be used to reduce the food cost, which have no downsides for ghouls:
* The [[nuclear stomach]]:{{RoyaltyIcon}} An [[artificial body part]] which multiplies [[hunger rate]] by {{Good|x25%}}. Note that [[cancer]], the primary downside of the nuclear stomach, is not a concern for ghouls.
* The [[robust digestion]] gene:{{BiotechIcon}} A gene that multiplies the nutrition gained from raw meat, but not corpses, by {{Good|x1.8}}.
* A [[metabolic efficiency]] of 5+:{{BiotechIcon}} This multiplies [[hunger rate]] by {{Good|x50%}}.

These stack to make for a ghoul that only requires as little as {{Icon Small|Meat||{{#expr: ({{Q|Ghoul|Real Hunger Rate}}*0.25*0.5)/({{Q|Meat|Nutrition}}*1.8 ) round 2}}}} [[meat]] per day and significantly increases the time that can be safely spent between meals.

Ideally, all corpses should be butchered by a competent cook for maximum nutrition, but preventing berserking is more important.

=== Body parts ===
Due to their massive improvement to resilience and damage, [[ghoul barbs]] and [[ghoul plating]] are essential upgrades for ghouls. For the heart upgrade, get the [[metalblood heart]] if you don't plan to produce [[metalblood serum]]s. But if you do, instead upgrade your ghoul with the [[adrenal heart]] to improve combat power or the [[corrosive heart]] for the painful [[acid spray]] attack.

Ghouls can also make effective use of [[body part weapon]]s. As they cannot hold conventional weapons, implanted weaponry offers them a powerful upgrade, and in combination with [[ghoul barbs]] ghouls offer {{DPS}} comparable to high-tier melee options. The ghoul can then be enhanced similarly to other melee pawns, such as with [[juggernaut serum]] and the [[strong melee damage]] gene.{{BiotechIcon}}

====Weapon choice====
[[Power claw]]s offer the highest damage, albeit with a small [[Moving]] penalty per claw. Note that combining a power claw and [[flesh tentacle]] will result in the same base {{DPS}} as two power claws, due to how the melee verb system selects and disregards certain attacks. As the flesh tentacle doesn't penalize [[Moving]] and boosts [[melee hit chance]], this is the optimal choice. A similar effect can be obtained by replacing the other hand with a [[wooden hand]] instead of the tentacle; the wooden hand reduces Manipulation, but the overall {{DPS}} is still close to that of two claws. Other hand and arm replacements will not work.

[[Flesh whip]]s come in a close second in term of {{DPS}} and do not have a Moving penalty. Flesh whips have a higher base {{AP}} than power claws, but its {{AP}} is not affected by the [[melee damage factor]] (MDF), so having a MDF of {{#expr: {{Q|Flesh whip|Attack 1 AP}}/{{Q|Power claw|Attack 1 AP}} * 100 round 0}}% or more will result in the power claw having more {{AP}}. Ghoul barbs and the strong melee damage gene{{BiotechIcon}} result in an MDF of 225%. Flesh whips can be combined with flesh tentacles or wooden hands in the same way as power claws.

Note that ghouls cannot be targeted by the [[twisted obelisk]], and so flesh parts should be acquired before ghoulification occurs. Afterwards, only flesh tentacles can be obtained, and only through [[unnatural healing]].

{| class="wikitable"
|+ Ghoul melee damage at melee level 20 and no other hediff or gene
|-
! Upgrades !! Move Speed !! Melee DPS !! Melee AP
|-
|-
| None || 4.6 c/s || 3.29 || 11%
|-
| 1 Power claw || 4.23 c/s || 8.28 || 28%
|-
| 2 Flesh whips || 4.6 c/s || 9.22 || 60%
|-
| Power claw + Wooden hand || 4.23 c/s || 9.64 || 33%
|-
| 2 Power claws || 3.86 c/s || 9.90 || 33%
|-
| Ghoul barbs + 1 Power claw || 4.00 c/s || 12.42 || 41%
|-
| Ghoul barbs + 2 Flesh whips || 4.35 c/s || 13.84 || 60%
|-
| Ghoul barbs + Power claw + Wooden hand || 4.00 c/s || 14.45|| 49%
|-
| Ghoul barbs + 2 Power claws || 3.65 c/s || 14.85 || 49%
|-
| Barbs + Juggernaut + Strong Melee Damage{{BiotechIcon}} + 1 Power claw || 4.46 c/s || 27.72 || 92%
|-
| Barbs + Juggernaut + Strong Melee Damage{{BiotechIcon}} + 2 Flesh whips || 4.85 c/s || 31.13 || 60%
|-
| Barbs + Juggernaut + Strong Melee Damage{{BiotechIcon}} + Power claw + Wooden hand || 4.46 c/s || 32.52 || 111%
|-
| Barbs + Juggernaut + Strong Melee Damage{{BiotechIcon}} + 2 Power claws || 4.07 c/s || 33.52 || 111%
|}

=== Genetics ===
{{Biotech|section=1}}
Ghouls primarily benefit from genes that improve their [[Incoming Damage Multiplier]], melee skill and damage, and movement speed. Having genes that improve their metabolic rate is also helpful. Ghouls will inherit genes from their underlying [[xenotype]]s, meaning that some make for better ghoul candidates than others.

<div class="mw-customtoggle-Genes" style="display:center;background:rgba(128,128,128,0.5);color:white;padding:10px;border-radius:5px;outline:none;user-select:none">
{{Center|Show/Hide Gene Analysis}}</div>
<div class="mw-collapsible mw-collapsed" id="mw-customcollapsible-Genes">
Below are ''all'' genes that have positive effects on ghouls. Other genes either have negative effects, no effects, or only positive in term of metabolic efficiency.

{| class="wikitable"
|+ Good Genes
|-
! Gene !! Improves !! Metabolic Cost !! Commentary
|-
|-
| [[Robust]] || {{Good|x75%}} [[Incoming Damage Multiplier]] ||style="text-align:center;" | {{Bad|-2}} || Reduces damage taken by ghouls, improving their capability to soak incoming damage for longer.
|-
| [[Strong melee damage]] || {{Good|x150%}} [[Melee Damage Factor]] ||style="text-align:center;" | {{Bad|-2}} || Increases damage dealt by ghouls
|-
| [[Naked speed]] || {{Good|+0.1}} [[Movement speed]] ||style="text-align:center;" | {{Good|+2}} || Slight increase to movement speed while giving free metabolic efficiency
|-
| [[Fast runner]] || {{Good|+0.2}} [[Movement speed]] ||style="text-align:center;" | {{Bad|-3}} || Double the movement speed bonus of Naked Speed
|-
| [[Very fast runner]] ||{{Good|+0.4}} [[Movement speed]] ||style="text-align:center;" | {{Bad|-5}} || Huge increase to movement speed, but very metabolically costly.
|-
| [[Strong melee]] || [[Melee]] Skill {{Good|+4}} || style="text-align:center;" | {{Bad|-1}} || Improves Melee skill which boosts melee hit chance and melee dodge chance
|-
| [[Great melee]] || [[Melee]] Skill {{Good|+8}} || style="text-align:center;" | {{Bad|-3}} || Larger Improvement to Melee skill
|-
| [[Unstoppable]] || [[Stagger Time Multiplier]] {{Good|x0%}} || style="text-align:center;" | {{Bad|-2}} || Removes stagger from receiving damage
|-
| [[Fire resistant]] || [[Flammability]] {{Good|x10%}}, [[Flame]] damage {{Good|x25%}} || style="text-align:center;" | {{Bad|-2}} || Resist flame damage and avoid being set on fire
|-
| [[Partial antitoxic lungs]] || [[Toxic Environment Resistance]] {{Good|+50%}} || style="text-align:center;" | {{Bad|-1}} || Resist toxic fallout and tox gas
|-
| [[Total antitoxic lungs]] || [[Toxic Environment Resistance]] {{Good|+100%}} || style="text-align:center;" | {{Bad|-2}} || Immune to toxic fallout and tox gas
|-
| [[Cold tolerant]] || [[Minimum Comfortable Temperature]] {{Good|−10 °C (36 °F)}} || style="text-align:center;" | {{Bad|-1}} || Resistance to hypothermia
|-
| [[Cold super-tolerant]] || [[Minimum Comfortable Temperature]] {{Good|−20 °C (36 °F)}} || style="text-align:center;" | {{Bad|-2}} || Larger resistance to hypothermia
|-
| [[Heat tolerant]] || [[Maximum Comfortable Temperature]] {{Good|+10 °C (36 °F)}} || style="text-align:center;" | {{Bad|-1}} || Resistance to heatstroke
|-
| [[Heat super-tolerant]] || [[Maximum Comfortable Temperature]] {{Good|+20 °C (36 °F)}} || style="text-align:center;" | {{Bad|-2}} || Larger resistance to heatstroke
|-
| [[Robust digestion]] || [[Raw Nutrition Multiplier]] {{Good|x180%}} || style="text-align:center;" | {{Bad|-2}} || Increase nutrition given by raw meat
|-
| [[Elongated fingers]] || [[Manipulation]] {{Good|x110%}} || style="text-align:center;" | {{Bad|-1}} || Slightly increase manipulation, which affects melee hit chance
|-
| [[Smooth tail]] || [[Manipulation]] {{Good|+5%}} || style="text-align:center;" | {{Bad|-1}} || Slightly increase manipulation
|-
| [[Superfast wound healing]] || [[Injury Healing Factor]] {{Good|x400%}} || style="text-align:center;" | {{Bad|-3}} || Quadruple the normal healing factor to roughly 25 HP/day
|-
| [[Pollution stimulus (gene)|Pollution stimulus]] || Up to [[consciousness]] {{Good|+5%}} and [[move speed]] {{Good|x120%}} || style="text-align:center;" | {{Bad|-1}} || Speed boost when exposed to pollution
|}

There are many genes whose negative effects don't affect ghouls at all; thus they can be used to improve their metabolic efficiency. Some of the notable genes are:
{| class="wikitable"
|+ Free Metabolic Efficiency
|-
! Gene !! Changes !! Metabolic Cost !! Commentary
|-
| [[Awful animals|Awful Skill]] || Skill {{Bad|-8}} || style="text-align:center;" | {{Good|+2}} || Ghouls only use Melee skill, any other skill can be ignored
|-
| [[Poor animals|Poor Skill]] || Skill {{Bad|-4}} || style="text-align:center;" | {{Good|+1}} || Ghouls only use Melee skill
|-
| [[Hyper-aggressive]] || Mental Breaks and Social Fights || style="text-align:center;" | {{Good|+3}} || Ghouls don't social fight or have mental break
|-
| [[Aggressive]] || Mental Breaks and Social Fights || style="text-align:center;" | {{Good|+2}} || Ghouls don't social fight or have mental break
|-
| [[Very sleepy]] || Sleep Fall Rate || style="text-align:center;" | {{Good|+4}} || Ghouls don't need rest
|-
| [[Sleepy]] || Sleep Fall Rate || style="text-align:center;" | {{Good|+2}} || Ghouls don't need rest
|-
| [[Very unhappy]] || Mood Penalty || style="text-align:center;" | {{Good|+5}} || Ghouls are unaffected by mood penalties
|-
| [[Unhappy]] || Mood Penalty || style="text-align:center;" | {{Good|+3}} || Ghouls are unaffected by mood penalties
|-
| [[Deathrest]] || Need for deathrest || style="text-align:center;" | {{Good|+6}} || Ghouls don't need deathrest
|-
| [[Hemogen drain]] || {{Bad|−8}} Hemogen per day || style="text-align:center;" | {{Good|+6}} || Ghouls don't need hemogen
|-
| [[Pyrophobia]] || [[Mental_break#Fleeing_fire|Fleeing fire]] mental break || style="text-align:center;" | {{Good|+4}} || Ghouls don't have mental breaks
|-
| [[Kill thirst]] || Causes need to kill humanoids|| style="text-align:center;" | {{Good|+4}} || Ghouls don't have needs beyond hunger
|-
| [[Extra pain]] || Increases pain|| style="text-align:center;" | {{Good|+2}} || Ghouls don't feel pain
|-
| [[Nearsighted]] || Decreases shooting accuracy|| style="text-align:center;" | {{Good|+2}} || Ghouls can't shoot
|-
| [[Weak immunity]] || More likely to die from diseases|| style="text-align:center;" | {{Good|+2}} || Ghouls are immune to diseases
|-
| [[Psychically deaf]] || Psychic sensitivity {{Down|-100%}}|| style="text-align:center;" | {{Good|+2}} || Ghouls have no psychic sensitivity
|-
| [[Psychically dull]] || Psychic sensitivity {{Down|-50%}}|| style="text-align:center;" | {{Good|+1}} || Ghouls have no psychic sensitivity
|-
| [[Genes#Drugs|Drug dependency]] || Need for a specific drug|| style="text-align:center;" | {{Good|+3}} or {{Good|+4}} || Ghouls have no drug needs and can't take drugs
|}

==== Archite genes ====
Archite genes are generally not worth adding to a ghoul xenogerm.
* [[Scarless]], [[Non-senescent]], [[Ageless]] and [[Perfect immunity]] are redundant in a ghoul.
* [[Gene implanter]] cannot be activated from ghouls.
* [[Deathless]] could be considered before having access to ghoul resurrection serums, but once the serums are available, their shorter coma period is preferable.
* [[Archite metabolism]] can be an option if not enough positive metabolism genes have been yet gathered, but maximum metabolism efficiency can be eventually achieved while using all the beneficial genes.
* The main draws of [[Breathless]]{{OdysseyIcon}} on ghouls are the bonus to minimum comfortable temperature and immunity to tox gas, as ghouls are already immune to vacuum exposure. However toxic buildup and gas immunity can also be achieved by a combination of [[Genes#Resistance and sensitivity|toxic resistance genes]] and [[detoxifier lung]]s. The temperature bonus could have an use when stacked will all other genes that improve cold resistance for ghouls in polar biomes or [[orbit]], but those require more metabolism points that could be spent on more impactful genes. For cold protection, blood warmers are cheaper and more accessible for a miniscule DPS penalty.
</div>

=== Medical quirks ===
Because ghouls rapidly regenerate their organs, you can harvest their organs before turning them into a ghoul:
* Harvesting a spare [[lung]] and [[kidney]] is possible for normal pawns.
** You can harvest all six organs from a [[sanguophage]].
** If you have a [[detoxifier lung]] and [[detoxifier kidney|kidney]], you can install them to the pawn and harvest the second natural lung and kidney. After the ghoul has finished regenerating one of each organ, you can then safely remove the artificial organs.
** By spending a [[ghoul resurrection serum]] afterwards, you can also harvest the [[heart]] in the same manner as above.
* Ghouls can still have genes implanted or harvested.

Becoming a ghoul does not remove [[hediffs#duplicate sickness|duplicate sickness]], [[paralytic abasia]], [[cirrhosis]] or [[lung rot]]. However, if you then kill the ghoul and revive them with a ghoul resurrection serum, it will remove the sickness but not the paralytic abasia or the cirrhosis. Lung rot can be "cured" by removing one lung at a time and letting them regenerate.

=== The ideal ghoul ===
Here is a setup for an ideal ghoul. The following features are very hard to achieve, but once achieved, they can be duplicated using the [[Corrupted obelisk]] any number of times:
* [[Void touched]]: available during the [[Endings#The Void|Anomaly ending]], gives 100 hp/day regeneration on top of ghoul regeneration and natural generation.
* Level 20 melee skill: massively improves melee hit and dodge chance.
* All keystone and good genes listed above. Other metabolically-efficient genes should be included to bring the efficiency up to +5.
* [[Tough]] trait: [[Incoming Damage Multiplier]] x50%.
* [[Jogger]] trait: [[Move Speed]] +0.4.
* [[Nimble]] trait: [[Melee Dodge Chance]] +15. This gives a small increase in the final melee dodge chance.
* [[Trauma savant]]: arguably the hardest to achieve, while only giving a very small improvement for melee hit chance.
* [[Fleshmass lung]]: will give some tox resistance for the ghoul if you don't install detoxifier lungs for them.
* [[Flesh whip]]: will give some melee damage for the ghoul if you don't install a [[power claw]].

Once you have a colonist or slave with these features, duplicate them using the [[corrupted obelisk]] and turn the duplicate into a ghoul, keeping the original. The ghouls can have these body parts installed to upgrade them further:
* [[Ghoul plating]]: [[Incoming Damage Multiplier]] x50%, while [[Move Speed]] -0.7.
* [[Ghoul barbs]]: [[Melee Damage Factor]] x150%, while [[Move Speed]] -0.25.
* [[Adrenal heart]]: gives a massive buff for move speed and melee damage when used.
* [[Power claw]] + [[flesh tentacle]] (or [[wooden hand]]): greatly improves a ghoul's melee damage. This is optional if the ghoul already has 2 flesh whips.
* [[Detoxifier lung]]s: gives tox resistance and a slight boost for move speed.
* [[Nuclear stomach]]: Food Consumption x25%.
* [[Stoneskin gland]]: sharp armor +70%, blunt armor +30%, heat armor +50% while moving x85%. This will also be the final armor values of the ghoul.
* Regular [[juggernaut serum]] administering: [[Move speed]] +0.5, [[Melee Damage Factor]] x150%, [[Injury Healing Factor]] x200%.
* [[Metalblood serum]] administering: [[Incoming Damage Multiplier]] x50%, while flame and burn weakness x400%. The flame weakness is cancelled out by the fire resistant gene.
* [[Frenzy inducer]]'s field: +0.4 move speed.
* Pollution stimulus: x120% move speed.
* [[Healing enhancer]]: natural healing factor x150%.
* Bionic eyes and legs: improve melee hit and dodge change, and also move speed. These can also be skipped without reducing the power of the ghoul by much. Archotech eyes and legs could be used instead, but the sheer amount of punishment you will likely have your ghoul be taking means that they will break eventually. Giving them to a ranged pawn to help them better support the ghoul is a better use of resources.

Note that power claws, bionic eyes, and bionic legs may be destroyed in combat if they take too much damage, so be ready to replace them if you decide to give them to the ghoul. Other body parts are less likely to be lost as the ghoul are more likely to be downed or die before that. Overall, the ghoul would have these stats:
* Daily Food Consumption 0.32 with Raw Food Multiplier x180%: this means they need only 3-4 twisted meat per day to live.
* Healing 200 hp/day, plus roughly 96 hp/day (208 HP/day when lying on hospital bed) from the 800% Injury Healing Factor and 150% Natural Healing Factor.
* Incoming Damage Multiplier 9.4%: this improves the amount of damage ghouls can take by over 10 times, which means it can take roughly 2925 damage points/day, or 2.9 points/s (after armor and melee dodge) just to negate the healing effect of the ghoul. In practice, the ghoul can fight an infinite number of [[chimera]]s one at a time.
* Melee Dodge Chance 38%.

Their damage and movement speed would be as follows:
{| class="wikitable"
|+ Ghoul weapon combos
|-
! Weapons !! Move speed !! Move speed (ghoul frenzy) !! Melee hit damage !! Melee DPS !! Melee AP
|-
| 2 [[flesh whip]]s || 6.93 c/s || 12.02 c/s || 69.19 || 32.07 || 60%
|-
| 1 [[power claw]] + 1 [[wooden hand]] || 6.47 c/s || 11.23 c/s || 74.25 || 34.39 || 111%
|-
| 2 [[power claw]]s || 6.08 c/s || 10.55 c/s || 74.25 || 34.41 || 111%
|}

=== Containment ===
Enemy ghouls are passable for containment, but are generally worse in the role than [[sightstealer]]s. Sightstealers provide more [[bioferrite]] and the same knowledge gain, and are easier to contain. They require less containment strength, do not regenerate lost body parts, and can feel [[pain]], meaning an escaping sightstealer is easier to subdue. Ghouls can make for a good supplementary source of dark study in the early game, though, and they provide somewhat more electricity with an [[electroharvester]].

In the early game, be careful when engaging enemy ghouls in melee combat. They cannot be [[downed]] due to [[pain]], so they will fight much longer than regular human raiders. Ghouls never show up in [[raid]]s or assaults; only one ghoul will appear per event, as a minor threat.

== Gallery ==

=== Hairs ===
<gallery>
Ghoul Hair Furious south.png|Furious, facing south
Ghoul Hair Furious east.png|Furious, facing east
Ghoul Hair Furious north.png|Furious, facing north
Ghoul Hair Hungry south.png|Hungry, facing south
Ghoul Hair Hungry east.png|Hungry, facing east
Ghoul Hair Hungry north.png|Hungry, facing north
Ghoul Hair Ravenous south.png|Ravenous, facing south
Ghoul Hair Ravenous east.png|Ravenous, facing east
Ghoul Hair Ravenous north.png|Ravenous, facing north
Ghoul Hair Twisted south.png|Twisted, facing south
Ghoul Hair Twisted east.png|Twisted, facing east
Ghoul Hair Twisted north.png|Twisted, facing north
Ghoul Hair Vengeful south.png|Vengeful, facing south
Ghoul Hair Vengeful east.png|Vengeful, facing east
Ghoul Hair Vengeful north.png|Vengeful, facing north
Ghoul Hair Warped south.png|Warped, facing south
Ghoul Hair Warped east.png|Warped, facing east
Ghoul Hair Warped north.png|Warped, facing north
Ghoul Hair Wicked south.png|Wicked, facing south
Ghoul Hair Wicked east.png|Wicked, facing east
Ghoul Hair Wicked north.png|Wicked, facing north
</gallery>

=== Heads ===
<gallery>
Ghoulskin Head Heavy south.png|Heavy, facing south
Ghoulskin Head Heavy east.png|Heavy, facing east
Ghoulskin Head Heavy north.png|Heavy, facing north
Ghoulskin Head Narrow south.png|Narrow, facing south
Ghoulskin Head Narrow east.png|Narrow, facing east
Ghoulskin Head Narrow north.png|Narrow, facing north
Ghoulskin Head Normal south.png|Normal, facing south
Ghoulskin Head Normal east.png|Normal, facing east
Ghoulskin Head Normal north.png|Normal, facing north
Ghoulskin Head Wide south.png|Wide, facing south
Ghoulskin Head Wide east.png|Wide, facing east
Ghoulskin Head Wide north.png|Wide, facing north
</gallery>

=== Bodies ===
<gallery>
Ghoulskin Fat south.png|Fat, facing south
Ghoulskin Fat east.png|Fat, facing east
Ghoulskin Fat north.png|Fat, facing north
Ghoulskin Female south.png|Female, facing south
Ghoulskin Female east.png|Female, facing east
Ghoulskin Female north.png|Female, facing north
Ghoulskin Hulk south.png|Hulk, facing south
Ghoulskin Hulk east.png|Hulk, facing east
Ghoulskin Hulk north.png|Hulk, facing north
Ghoulskin Male south.png|Male, facing south
Ghoulskin Male east.png|Male, facing east
Ghoulskin Male north.png|Male, facing north
Ghoulskin Thin south.png|Thin, facing south
Ghoulskin Thin east.png|Thin, facing east
Ghoulskin Thin north.png|Thin, facing north
</gallery>

== Trivia ==
Ghouls cannot get pregnant through any method. A pregnant pawn that is turned into a ghoul will have the pregnancy removed. A pawn that is in labor when being turned into a ghoul will have the labor hediff removed, but a non-ghoul baby will also be produced normally.

== Version history ==
* [[Anomaly DLC]] release - Added.

{{Nav|entity|wide}}
[[Category: Entities]]

The Mechanitor Guide

2026-04-27T23:33:49Z

Aelanna: Rewriting added section.

{{Biotech}}
In the [[Scenario_system#The Mechanitor|Mechanitor scenario]], you start with a single colonist possessing the [[Recluse]] trait, 1 [[Lifter]], 1 [[Constructoid]], and various other supplies.

This scenario is considered by the game to be difficult.

{{TOCright}}
== Scenario Parameter==
'''Summary:''' One [[Mechanitor]] and a few servant mechanoids. <br>
'''Description:''' You knew you could only achieve greatness with help. People were too unreliable, so you chose to take on mechanoids as your servants, workers, and warriors. As you gained strength, others became fearful. It became clear you needed to get away from the influence of humanity. Now you've migrated to this sparsely-populated Rimworld with some of your metallic helpers. Finally, you have the space to grasp your true potential!

== Starting colonist ==
Your colonist should be ''capable'' of most tasks, even if they aren't good at them. A colonist incapable of Caring can and will die to a single bleeding wound (and is unable to recruit [[transport pod crash]]es or [[raiders]]). It is certainly possible to rely on [[spike trap]]s at the start, but being incapable of Violence is ill-advised.

=== Skills you need ===
In order of importance:

*'''Mining''' You want a pawn with good mining above all, since you will need the resources for all game stages, and building [[Tunneler]]s require [[Standard mechtech]].
*'''Crafting''' is next, since you will want to be able to craft the new gear, and components later on. Also it is the base skill for mechanitor work like repairing.
*'''Intellectual''' is helpful, but a decent pawn can do a better job later on.
*'''Medical''' is helpful, but keeping your mechanitor hidden behind an army is ideal so they won't take any damage at all.
*'''Social''' is helpful for recruiting and trading faster, but as long as it's not blocked you will be ok.
*'''Ranged''' can help supplement a mech army, but mechs will easily overcome a bad shooting skill. Avoid [[melee]] since it makes your mechanitor likely to take damage.

=== Traits ===
Your colonist will always start with the [[recluse]] trait which gives them a {{+|12}} mood bonus when no other colonists are present but that decreases as colonist count increases, down to a limit of {{--|8}} mood when 16 or more colonists are present.

As the mood penalty from recluse is not severely crippling, you should generally not hesitate to recruit additional colonists if they have particularly desirable traits or skills. Additionally if [[Anomaly]] is installed, mutants such as [[ghoul]]s do not count as colonists for the recluse trait and can be a strong melee combatant option.

=== Xenotypes ===
While not required, a Xenotype immune to pollution such as [[Waster]] should be preferred due to their [[Total antitoxic lungs|pollution immunity]], if you are going to use nutrient paste as a food source this is further amplified as their poor cooking skill stops mattering. In addition to letting you to dump your [[toxic wastepack|toxic waste]] anywhere. Alternatively, [[Genie]]s are also an great fit for a mechanitor, although it also forces the delicate trait, meaning your pawn will be less capable of direct combat, but that's something that shouldn't happen too often.

==== Starting Out ====
You start with a Constructoid and a Lifter. Get the infrastructure to recharge and gestate an [[agrihand]] as soon as possible. A second Agrihand will help a lot for making you money in the short term (more wood to sell in chemfuel or other good forms).

For power, a [[wood-fired generator]] is okay to start with, but if you are fine with the extra pollution a [[toxifier generator]] is more powerful and scalable, very good for this scenario. [[Wind turbine]]s might seem good, but you will have to sink [[component]]s into batteries if you want to go that route. [[Chemfuel powered generator]]s are good once you have the tech and lifters to cut [[wood]]. Even though you have the research, avoid batteries, since you need those components elsewhere.

Next you will want a [[research bench]]. You can build an advanced one, but you may find the 10 components it requires are better spent elsewhere. Go with a simple one, unless you intend to rush for fabrication.

A second [[Mech gestator|gestator]] helps but isn't necessary if you can afford to wait. Get a [[subcore encoder]] to build more than 5 small mechs. Once you have 1 Constructoid, 1 Lifter, and 1-2 agrihands, the best way to spend your remaining 5-6 BW is on Militors, since they've got guns.

{{Nav|guides|wide}}
[[Category:Guides]]

Tox pack

2026-04-27T23:25:31Z

Aelanna: Rewrite for readability.

{{Biotech}}
{{infobox main
| name = Tox pack
| image = ToxPack.png
| description = A reusable backpack containing canisters of reagents and a mechanism that uses them to generate tox gas. When the wearer activates the pack, it will begin spreading tox gas and continue for several seconds until it runs out of reagents.<br/>Once used, it must be reloaded with chemfuel before it can be used again.<br/>Tox gas burns the lungs and eyes, causing a temporary shortness of breath and reduction in sight. Continued exposure to tox gas results in toxic buildup which can be lethal.

| type = Gear
| type2 = Utility
| tech level = Industrial
| mass base = 3
| beauty = -3
| hp = 100
| deterioration = 2
| flammability = 0.6
| path cost = 14

| has quality = false
| clothing for nudity = False
| lifestage = Adult
| coverage = Waist
| layer = Belt
| scoreOffset = 4
| careIfWornByCorpse = false
| careIfDamaged = false
| wearPerDay = 0
| tags = BeltDefenseTox
| bodyPartGroups = Waist
| equipdelay = 2

| production facility 1 = Machining table
| research = Tox gas
| skill 1 = Crafting
| skill 1 level = 3
| work to make = 3600
| work speed stat = General Labor Speed
| resource 1 = Steel
| resource 1 amount = 10
| resource 2 = Component
| resource 2 amount = 1
| resource 3 = Chemfuel
| resource 3 amount = 35

| defName = Apparel_PackTox
| label = tox pack
| thingCategories = ApparelUtility
| defaultOutfitTags =
| tradeTags = Clothing
| page verified for version = 1.4.3525

| tickerType = Normal
| EquipDelay = 2

| unfinishedThingDef = UnfinishedPack
| useIngredientsForColor = false
| displayPriority = 350

| maxCharges = 1
| soundReload = Standard_Reload
| chargeNoun = tox pack
| displayGizmoWhileUndrafted = false
| ammoDef = Chemfuel
| ammoCountToRefill = 35
| baseReloadTicks = 60
| hotKey = Misc4

| gasType = ToxGas
| cellsToFill = 45
| durationSeconds = 12.75
| effecterReleasing = ToxGasReleasing

| compClass = CompToxPack
| checkInterval = 60
| verbClass = Verb_DeployToxPack
| label2 = deploy tox pack
| violent = false
| hasStandardCommand = true
| targetable = false
| soundCast = GasPack_Deploy
| nonInterruptingSelfCast = true

| thingClass = Apparel
| category = Item
| drawerType = MapMeshOnly
| selectable = True
| useHitPoints = True
| drawGUIOverlay = true
| altitudeLayer = Item
| alwaysHaulable = True
| burnableByRecipe = true
| smeltable = true
| forbiddable = true
| colorable = true
}}
The '''tox pack''' is a [[utility]] item added by the [[Biotech DLC]] that allows the user to deploy [[tox gas]].

== Acquisition ==
{{Acquisition}}

== Summary ==
{{Stub|section=1|reason=Mechanical detail- cloud size, deployment time, activation mechanics for both player pawns and NPCs etc. }}
{{Image wanted|section=1|reason=AoE image in standard style}}
Tox packs create a cloud of [[tox gas]] centered on the user.

The pack can only be used once before needing to be refueled, at a cost of {{icon Small|chemfuel||35}} chemfuel. To refuel it, select its user and right-click a pile of chemfuel.

{{Utility Note}}

== Analysis ==
{{Stub|section=1|reason=General - e.g. strategies, use case, value proposition for making and opportunity cost for use vs other utility}}
Because the tox gas cloud is created centered on the user tox packs are best used on [[waster]]s or xenotypes with toxic resistance.
===Toxic Killbox===
While useless in an open area, Tox packs gain a lot of utility when used in tight corridors and cramped rooms. As Rimworld simulates gas physics for tox gas, smoke and [[Deadlife dust]]. Tox packs are very good for melee blockers inside of killboxes. Do remember however that unless your pawns have full toxic immunity, they will at least partially be affected by tox gas. Thus this strategy is recommended with [[Waster]]s and other tox resistant/immune xenotypes.

===Riot Control===
Tox gas can be used to stop prison breaks or slave rebellions. However, due to the danger of tox gas in enclosed areas and its greatly reduced effectiveness outdoors, it can be very unreliable and either be ineffective or quickly result in dead escapees. It might still be a better option if all of your wardens would likely cause fatal injuries in direct combat, such as if your colonists are mostly [[sanguophage]]s or otherwise have strong melee.

== Version history ==
* [[Biotech DLC]] Release - Added.
* [[Version/1.4.3563|1.4.3563]] - Tox packs no longer activate upon stripping or butchering [[corpse]]s wearing them.

{{nav|Utility|wide}}
[[Category: Utility]]

Ailments

2026-04-27T23:19:22Z

Aelanna: Please check spelling and grammar in edits.

{| align=center
| {{Health_Nav}}
|}
----

{{rewrite|reason=Cleanup and standardization needed - treatment and stages sections for each required. See [[Template:Heal Option Table]]. Once the table is updated, also add chronophagy to relevant cured ailments. Add ailment in-game descriptions to each, and format them such that they're obviously quotes}}
{{About|chronic health conditions|physical damage|Injury|treatable illnesses|Disease}}
{{TOCright}}

'''Ailments''' are [[health]] conditions that cannot be treated completely using medicine alone.

"MTB" stands for "Mean Time Between", and is how it's presented in the game files.

Some conditions can give rise to other conditions; the risk of this happening will diminish if the condition is treated.

Most permanent ailments are curable with body part replacements or usage of the [[healer mech serum]].

{{Heal Option Table}}

== Chronic ==
Ailments that come with age. Either non-fatal, or progresses extremely slowly towards fatality compared to infectious diseases.

=== Alzheimer's ===
{{stub|reason = "Forget memory" and "confused wandering" mechanics}}
A brain disease usually associated with aging. Alzheimer's disease causes progressive degradation in the ability to think and remember. Patients are known to forget close relatives and sometimes wander around in confusion.

Alzheimer's progresses by 0.003 per day, meaning that it will take 333.33 days for it to reach full severity from when it first appears.

{| class="wikitable"
|-
! Stage !! Begins at !! Symptoms
|-
| '''Alzheimer's (minor)''' || ≥0% severity ||
* -5% part efficiency
* Confused wandering (''MTB of 12 days'')
* Forget memory (''MTB of 7 days'')
|-
| '''Alzheimer's (minor)''' || ≥20% severity ||
* -10% part efficiency
* Confused wandering (''MTB of 9 days'')
* Forget memory (''MTB of 4 days'')
* ''0.15%'' of conditional thoughts nullified
|-
| '''Alzheimer's (major)''' || ≥50% severity ||
* -15% part efficiency
* Confused wandering (''MTB of 7 days'')
* Forget memory (''MTB of 2 days'')
* ''0.5%'' of conditional thoughts nullified
|-
| '''Alzheimer's (major)''' || ≥80% severity ||
* -20% part efficiency
* Confused wandering (''MTB of 4 days'')
* Forget memory (''MTB of 0.8 days'')
* ''1%'' of conditional thoughts nullified
|}

A human pawn must be at least 33.6 years old to get Alzheimer's, meaning it can first occur at their 34th birthday
{| class="wikitable"
|-
! Alzheimers chance
|-
| {{Graph:Chart
|width=400
|height=100
|type=line
|x=0, 33.6, 56, 72, 80, 120
|y=0, 0, 0.061, 0.12, 0.2, 0.3
|xAxisTitle = Pawn age (years)
|yAxisTitle = Chance/Birthday (%)
}}
|}

'''Treatment:'''
* [[Luciferium]]: Luciferium removes one randomly selected condition that it can cure every 900,000 to 1,800,000 [[ticks]] (15 - 30 in-game days). Having fewer luciferium-curable conditions will increase the chance that Alzheimer's is chosen, so it can be worth attempting to address any conditions that can be other means. Even with this however, it can take a significant amount of time. Also note that luciferium is a permanent decision - once taken, further doses are necessary to avoid madness and death.
* [[Healer mech serum]]: A healer mech serum will instantaneously heal one condition of the pawn, including Alzheimer's. Which condition is chosen depends on a priority order, with Alzheimer's being a moderately high priority. See the serum's [[Healer mech serum#Summary|condition order]] for details.
* [[Resurrector mech serum]]: Because the resurrector mech serum will replace a destroyed head with a healthy one, it can be used to heal brain ailments, including Alzheimers. Consistently destroying the head can be difficult. With the [[Ideology DLC]], extracting the [[skull]] from a dead pawn will do this reliably and safely, but without it, the best way is allowing colonists or animals to eat sections of the corpse, at the risk of consuming the entire body and permanently losing the pawn. Furthermore, no matter how successful the head removal, there is always the risks normally associated with resurrection, including [[dementia]], [[blindness]], and [[resurrection psychosis]]. Note that pawns will initially be incapacitated due to resurrection sickness.
* [[Death refusal]]{{AnomalyIcon}}: Similar to the [[Resurrector mech serum]], a pawn imbued with death refusal can self-resurrect and replace a destroyed head with a healthy one. This comes with the drawback of the pawn losing experience in their skills that happens upon imbuing the death refusal. Pawns resurrected via this method will also have resurrection sickness and a negative [[Mood|moodlet]] upon being resurrected.
* [[Chronophagy]]{{AnomalyIcon}}: As pawns younger than 34 cannot get Alzheimer's, reversing age to younger than that in a Chronophagy ritual will remove it.
* [[Unnatural healing]]{{AnomalyIcon}}: a Creepjoiner with unnatural healing replicates the effect of a healer mech serum and so can be similarly used to cure Alzheimers at the minor risk of replacing an arm with a flesh tentacle for the cured pawn
* [[Scarless]]{{BiotechIcon}}: Similarly to Luciferium, the Scarless gene can heal permanent injuries and ailments including Alzheimer's. It is rare to see outside of [[sanguophage]]s but has no downsides other than for colonists with [[traits|body purist]].

=== Asthma ===
A chronic health condition where inflammation causes the airways to narrow, restricting the flow of oxygen to the lungs. Unlike other chronic diseases, asthma can be contracted at almost any age, meaning it's not terribly uncommon to have an asthmatic person some time down the line.

When not treated, it progresses by a rate of 0.25 per day, meaning it will take 2 days to reach full severity (50%).

Good treatment will reduce the rate of progression by up to 0.8, meaning it will regress by 0.55 a day; it can be returned to its initial severity, but cannot be cured completely.

Asthma's severity will fluctuate depending on the quality of treatment received, with a treatment quality of 32% beginning to regress the stages of asthma (the higher, the better).

{| class="wikitable"
|-
! Stage !! Begins at !! Symptoms
|-
| '''Asthma (minor)''' || ≥ 0% severity || -10% part efficiency
|-
| '''Asthma (major)''' || ≥ 30% severity || -30% part efficiency
|-
| '''Asthma (major)''' || ≥ 45% severity || -50% part efficiency
|}

Treatment:
* The severity of asthma can be reduced with treatment, which can be given every 420,000 ticks (around 7 days). One treatment applies to both lungs.
* Asthma can be cured by replacing each affected lung with a [[Lung#Acquisition|healthy replacement]].

A human pawn can first get asthma at any age.
{| class="wikitable"
|-
! Asthma chance
|-
| {{Graph:Chart
|width=400
|height=100
|type=line
|x=0, 16, 24, 40, 120
|y=0, 0.048, 0.096, 0.1344, 0.1344
|xAxisTitle = Pawn age (years)
|yAxisTitle = Chance/Birthday (%)
}}
|}

Asthma can also affect animals, domestic, tamed and wild. Domestic and tamed will notify you that they "need treatment", although there apparently is no downside for ignoring that request except slowing them down which may be bad for [[Animals#Training|trained]] or [[pack animal]]s. Similarly, asthmatic wild animals on the map can roam and eat indefinitely without treatment. In fact, wild animals with asthma are easier and slightly safer to hunt, because asthma will reduce their [[move speed]] to 81%, and their [[manipulation]] to only 90%, which makes any counter-attack less effective.

=== Bad back ===
Degradation in the spinal column and surrounding musculature. This makes it hard to move and bend smoothly.

{| class="wikitable"
|-
! Ailment !! Symptoms
|-
| '''Bad back''' ||
* -30% [[Moving]]
* -10% [[Manipulation]]
|}

A bad back can be cured by installing a [[bionic spine]], or with the use of [[biosculpter pod]]'s bioregeneration cycle{{IdeologyIcon}}.

A human pawn must be at least 40 years old to get a bad back, meaning it can first occur at their 41st birthday
{| class="wikitable"
|-
! Bad back chance
|-
| {{Graph:Chart
|width=400
|height=100
|type=line
|x=0, 40, 50, 60, 70, 80, 120
|y=0, 0, 0.93, 1.395, 1.395, 1.86, 1.86
|xAxisTitle = Pawn age (years)
|yAxisTitle = Chance/Birthday (%)
}}
|}

=== Cataract ===
Milky-looking opacity in the eye. Cataracts impair vision.
{| class="wikitable"
|-
! Ailment !! Symptoms
|-
| '''Cataract''' || -50% part efficiency in the affected eye. This results in 50% [[sight]] if both eyes are affected.
|}
Cataracts can be cured through the following methods:
* Replacing the affected eyes with a [[bionic eye|bionic]] or [[archotech eye|archotech]] eye.
* Use of a [[healer mech serum]] which will heal cataracts in both eyes at once
* Via [[luciferium]] use. Note that this does not occur instantaneously, but instead at healing instances that occur periodically. See that page for details.
* Through the use of the [[biosculpter pod]]'s bioregeneration cycle.{{IdeologyIcon}}
* Via the [[Scarless]] gene.{{BiotechIcon}} Note that this does not occur instantaneously, but instead at healing instances that occur periodically. See that page for details.

A human pawn must be at least 48 years old to get cataracts, meaning it can first occur at their 49th birthday
{| class="wikitable"
|-
! Cataract chance
|-
| {{Graph:Chart
|width=400
|height=100
|type=line
|x=0, 48, 60, 70, 120
|y=0, 0, 0.53, 1.1045, 1.1045
|xAxisTitle = Pawn age (years)
|yAxisTitle = Chance/Birthday (%)
}}
|}

=== Carcinoma ===
{{Stub|section=1|reason=How do the stages progress/occur and what chances and factors affects them?}}
A carcinoma (or cancer) is where mutated cells uncontrollably divide to form tumors, which then 'crowd out' normal bodily cells and hinder bodily function in that area. Carcinomas can be surgically removed by a skilled doctor or, in some cases, the affected body part can be removed, either by amputation, transplantation of a healthy body part, or replacement by an [[artificial body part]]. Ordinary treatment will prolong the development of a carcinoma or speed up remission, and can be done by doctors of any skill, though better treatment quality is more effective.

A carcinoma typically starts out at 30% severity. There is a 30% chance that a carcinoma won't cause any pain whatsoever.

A cancer has 3 stages; growing, stable and remission.
* When growing, it progresses by 0.003 per day, multiplied by a random factor of 0.45 - 1.65.
* When stable, it neither grows nor regresses on its own.
* When in remission, it regresses by 0.002 per day, multiplied by a random factor of 0.7 - 1.5.

Good treatment can slow progression by 0.0027 per day, meaning that the carcinoma will:
* grow more slowly when in growing stage
:* some slow-growing carcinomas (something less than half) may stop or actually regress (very slowly) during their "growing" stage with good treatment
* slowly regress when stable
* regress quickly when in remission
{| class="wikitable"
|-
! Stage !! Begins at !! Symptoms
|-
| '''Carcinoma (minor)''' || ≥0% severity ||
* Little pain (+10%)
* -10% part efficiency
|-
| '''Carcinoma (minor)''' || ≥15% severity ||
* Moderate pain (+20%)
* -25% part efficiency
|-
| '''Carcinoma (major)''' || ≥40% severity ||
* Moderate pain (+35%)
* -50% part efficiency
|-
| '''Carcinoma (major)''' || ≥60% severity ||
* Acute pain (+50%)
* -80% part efficiency
|-
| '''Carcinoma (extreme)''' || ≥80% severity ||
* Acute pain (+60%)
* -90% part efficiency
|-
| '''Carcinoma (extreme)''' || 100% severity ||
* Affected part is destroyed
|}

Treatment:
* Treated every {{ticks|240000}}
* The carcinoma will disappear if severity reaches 0.
* "Excise carcinoma" surgery; this needs 4 medicine of [[medicine|industrial quality]] or above, {{ticks|4500}} of work, and a doctor with a [[medical]] skill of 10 or above. The surgery has a 100% base chance to succeed. If it fails, there is a 25% chance that the patient [[Death|dies]]. Thus, as the maximum [[Doctoring#Success chance|success chance]] is capped at 98%, there is always at least a 0.5% chance of death per attempt.

A human pawn must be at least 22.4 years old to get carcinoma from aging, meaning it can first occur at their 23rd birthday. Carcinomas from other sources, including [[toxic buildup]] and [[nuclear stomach]]s,{{RoyaltyIcon}} can happen at any age. Installed nuclear stomachs create a carcinoma on the torso with an MTB of 120 days.
{| class="wikitable"
|-
! Carcinoma chance
|-
| {{Graph:Chart
|width=400
|height=100
|type=line
|x=0, 22.4, 80, 120
|y=0, 0, 0.11, 0.15
|xAxisTitle = Pawn age (years)
|yAxisTitle = Chance/Birthday (%)
}}
|}

=== Dementia ===
Dementia is simply the functionality of the brain declining, and affects all cognitive functions.

It can only be healed with a [[healer mech serum]], [[luciferium]], [[unnatural healing]]{{AnomalyIcon}} or the [[chronophagy]] psychic ritual.{{AnomalyIcon}}
{| class="wikitable"
|-
! Ailment !! Symptoms
|-
| '''Dementia''' ||
* Impaired brain function (-15% part efficiency)
** Effectively -15% [[Consciousness]]
* Impaired [[Talking]] (-25%)
** Net loss of 40% [[Talking]] including brain function loss
* Impaired [[Hearing]] (-25%)
** Net loss of 40% [[Hearing]] including brain function loss
* Confused wandering (''MTB of 5 days'')
* Slightly accelerated skill loss
**5% at level 4
**15% at level 12
**25% at level 20
|}

A human pawn must be at least 68 years old to get dementia from aging, meaning it can first occur at their 69th birthday. Dementia from other sources including [[toxic buildup]] can happen at any age.
{| class="wikitable"
|-
! Dementia chance
|-
| {{Graph:Chart
|width=400
|height=100
|type=line
|x=0, 68, 76, 92, 120
|y=0, 0, 0.93, 9.3, 9.3
|xAxisTitle = Pawn age (years)
|yAxisTitle = Chance/Birthday (%)
}}
|}

=== Frail ===
Generalized loss of muscle and bone density. Note that frail ''can'' stack with bad back.

{| class="wikitable"
|-
! Ailment !! Symptoms
|-
| '''Frail''' ||
* -30% [[Moving]]
* -30% [[Manipulation]]
|}

Can only be cured with [[luciferium]], a [[healer mech serum]], [[unnatural healing]] ability,{{AnomalyIcon}} the [[Chronophagy]] psychic ritual,{{AnomalyIcon}} implantation of the [[scarless]] gene,{{BiotechIcon}} or with the use of [[biosculpter pod]]'s bioregeneration cycle.{{IdeologyIcon}}

A human pawn must be at least 50 years old to get frail, meaning it can first occur at their 51st birthday
{| class="wikitable"
|-
! Frail chance
|-
| {{Graph:Chart
|width=400
|height=100
|type=line
|x=0, 50, 60, 70, 120
|y=0, 0, 1.395, 2.604, 2.604
|xAxisTitle = Pawn age (years)
|yAxisTitle = Chance/Birthday (%)
}}
|}

=== Artery blockage ===
A blockage in one of the critical arteries in the [[heart]]. Heart artery blockages randomly induce [[#Heart attack|heart attacks]]. Artery blockages can be treated by replacing the heart with a [[heart|natural]], [[prosthetic heart|prosthetic]] or [[bionic heart|bionic]] replacement, with a [[healer mech serum]], with [[luciferium]], or with the use of [[biosculpter pod]]'s bioregeneration cycle{{IdeologyIcon}}.

Artery blockages progress by a base of 0.0007 per day, multiplied by a random factor between 0.5 - 3.
This means that artery blockages can take anywhere from 7.9 to 47.6 in-game years from onset to become fatal on its own.

Artery blockages can be treated by replacing the heart.

{| class="wikitable"
|-
! Stage !! Begins at !! Symptoms
|-
| '''Artery blockage (minor)''' || ≥0% severity ||
* -5% part efficiency
* [[#Heart attack|Heart attack]] (''MTB of 300 days'')
|-
| '''Artery blockage (minor)''' || ≥20% severity ||
* -10% part efficiency
* [[#Heart attack|Heart attack]] (''MTB of 200 days'')
|-
| '''Artery blockage (major)''' || ≥40% severity ||
* -15% part efficiency
* [[#Heart attack|Heart attack]] (''MTB of 100 days'')
|-
| '''Artery blockage (major)''' || ≥60% severity ||
* -35% part efficiency
* [[#Heart attack|Heart attack]] (''MTB of 60 days'')
|-
| '''Artery blockage (extreme)''' || ≥90% severity ||
* -60% part efficiency
* [[#Heart attack|Heart attack]] (''MTB of 30 days'')
|-
| '''Artery blockage (extreme)''' || 100% severity ||
* [[Death]]
|}

A human pawn must be at least 20 years old to get an artery blockage, meaning it can first occur at their 21st birthday
{| class="wikitable"
|-
! Artery blockage chance
|-
| {{Graph:Chart
|width=400
|height=100
|type=line
|x=0, 20, 24, 40, 80, 120
|y=0, 0, 0.1, 0.145, 0.16, 0.17
|xAxisTitle = Pawn age (years)
|yAxisTitle = Chance/Birthday (%)
}}
|}

=== Hearing loss ===
Inability to hear quiet sounds due to degradation of hair cells in the cochlea.
{| class="wikitable"
|-
! Ailment !! Symptoms
|-
| '''Hearing loss''' ||
* -50% part efficiency (results in 50% [[hearing]] if both ears are affected)
|}

Can be partially mitigated with one or two [[cochlear implant]]s.
Can be completely mitigated with a single [[bionic ear]], even if the other ear remains affected.
A [[Biosculpter_pod|bioregeneration cycle]]{{IdeologyIcon}} can completely cure hearing loss in both ears.

A human pawn must be at least 48 years old to get hearing loss, meaning it can first occur at their 49th birthday
{| class="wikitable"
|-
! Hearing loss chance
|-
| {{Graph:Chart
|width=400
|height=100
|type=line
|x=0, 48, 60, 70, 120
|y=0, 0, 0.53, 1.11045, 1.11045
|xAxisTitle = Pawn age (years)
|yAxisTitle = Chance/Birthday (%)
}}
|}

== Acute ==
Some ailments arise as a result of an acute lack of food or exposure to extreme temperatures. These ailments can only be treated by addressing the underlying cause (e.g. providing food or moving to more comfortable temperatures).

=== Malnutrition ===
When a pawn's [[Eating|food]] meter reaches 0%, they will begin to suffer from [[malnutrition]], shown on the health tab. When a colonist is starving they will prioritize eating over other activities, including firefighting and doctoring.

Malnutrition severity without food will advance at an average of 17% per day. There is a variation for each pawn that will vary this by 20% in both directions, meaning a pawn may actually die of malnutrition between 4.9~7.4 days of first having symptoms. There is no stat indicating the specific rate that a pawn may die of malnutrition, but the modified rate is determined for each specific pawn in a given playthrough.
{| class="wikitable"
|-
! Stage !! Usually Begins at !! Symptoms
|-
| '''Malnutrition (trivial)''' || 0.0 days since hunger hit zero ||
* -5% [[consciousness]]
* +50% hunger rate
* 1.5x more likely to start a social fight
|-
| '''Malnutrition (minor)''' || 1.2 days since hunger hit zero ||
* -10% [[consciousness]]
* +60% hunger rate
* 2x more likely to start a social fight
|-
| '''Malnutrition (moderate)''' || 2.4 days since hunger hit zero ||
* -20% [[consciousness]]
* +60% hunger rate
* 2.5x more likely to start a social fight
|-
| '''Malnutrition (severe)''' || 3.5 days since hunger hit zero ||
* -30% [[consciousness]]
* +60% hunger rate
* 3x more likely to start a social fight
|-
| '''Malnutrition (extreme)''' || 4.7 days since hunger hit zero ||
* Unconscious ([[consciousness]] max. 10%)
|-
| '''Malnutrition (extreme)''' || 5.9 days since hunger hit zero ||
* [[Death]]
|}



=== Blood loss ===
{{About|section=1|the effect of already lost blood|the mechanics that cause blood loss|Bleeding}}
A reduction in the normal blood volume. Minor blood loss has relatively mild effects, but as severity increases, the [[consciousness]] rapidly become debilitating. Extreme blood loss leads to [[death]]. Total blood loss is listed under whole body, with a tooltip showing the percent.

Blood loss can occur when a pawn has untreated [[Injury#Bleeding|bleeding injuries]], has had blood harvested for [[hemogen pack]]s,{{BiotechIcon}} or has been fed on by a [[Bloodfeeder]].{{BiotechIcon}} Blood loss from multiple sources stacks additively.

All pawns recover 33.3% of their blood per day, regardless of [[traits]], [[genes]], [[drugs]], or [[artificial body parts]]. All natural blood recovery is stopped when a pawn is [[bleeding]], even in small amounts. Pawns can also recover through a blood transfusion operation, using 1 [[hemogen pack]]{{BiotechIcon}} to recover 35%. The [[Biosculpter_pod#Medic|biosculpter pod's medic cycle]]{{IdeologyIcon}} will also cure all blood loss, though it should be noted that non-transhumanist pawns would recover completely from blood loss in the same time as the cycle takes to complete anyway. If there is no other reason to use the medic cycle, non-transhumanist pawns should just recover outside of the pod and remain productive for that time.

{| class="wikitable"
|-
! Stage !! Begins at !! Symptoms
|-
| '''Blood loss (minor)''' || ≥15% blood loss ||
*{{--|10%}} [[Consciousness]]
|-
| '''Blood loss (moderate)''' || ≥30% blood loss ||
*{{--|20%}} [[Consciousness]]
|-
| '''Blood loss (severe)''' || ≥45% blood loss ||
*{{--|40%}} [[Consciousness]]
|-
| '''Blood loss (extreme)''' || ≥60% blood loss ||
*{{--|40%}} [[Consciousness]]
* [[Consciousness]] 10% max. (Unconsciousness)
|-
| '''Blood loss (extreme)''' || 100% blood loss ||
* [[Death]]
|}

=== Heatstroke ===
Heat stroke occurs when a pawn has prolonged exposure to [[temperature]]s 10°C (18°F) above their [[maximum comfortable temperature]], and recovery occurs in temperatures less than the maximum comfortable temperature.
Note that it is possible for a pawn to have both heatstroke and hypothermia at the same time if time is spent in both extreme heat and cold - their severities are unrelated.

Pawns additionally take periodic burn damage in temperatures more than 150°C (270°F) above their maximum comfortable temperature.
====Severity Increase====

The procedure for determining severity growth every 60-tick interval, '''SG60''' for short, is given by:
# Take the amount by which the ambient temperature exceeds the pawn's maximum safe temperature (which is the maximum comfortable temperature +10°C).
# Pass the amount through the curve shown below to obtain the effective temperature excess.
## Note that for amounts from 0 to 25 °C, this doesn't result in a change.
# Multiply the excess by <code>6.45e-5</code> to obtain the severity growth this interval (60 ticks, 1 second).
# If the growth is less than <code>0.000375</code>, set it to that number. This sets a minimum amount the severity increases by for temperatures in the range of 10 to 15.814°C above the maximum comfortable temperature.
:<code>'''SG60''' = max(0.000375, 0.0000645 × effective_temperature_curve(<i>ambient_temperature</i> - (<i>maximum_comfortable_temperature</i> + 10°C)))</code>
::<code><i>where </i>effective_temperature_curve()<i> is a post-processing curve with points</i>: (0, 0), (25, 25), (50, 40), (100, 60), (200, 80), (400, 100), (4000, 1000).</code>
{| class="wikitable"
|-
! Effective temperature curve !! X !! Y
|-
| rowspan=7| {{Graph:Chart
|width=600
|height=150
|type=line
|showSymbols=1
|x=0, 25, 50, 100, 200, 400, 4000
|y=0, 25, 40, 60, 80, 100, 1000
|xAxisMax = 1000
|yAxisMax = 250
|xAxisTitle = Temperature excess (°C)
|yAxisTitle = Effective temperature excess
}}
| 0 || 0
|-
| 25 || 25
|-
| 50 || 40
|-
| 100|| 60
|-
| 200 || 80
|-
| 400 || 100
|-
| 4000 || 1000
|}

<div style="display:inline-table; vertical-align:top;">

{| class="wikitable"
|- class=static-row-header style=vertical-align:middle
! rowspan=2 | Graph
! style=max-width:20em rowspan=2 | Excess<br/>Temperature (°C)<ref>Ambient Temperature - Maximum Comfortable Temperature (°C)</ref>
! style=max-width:15em rowspan=2 | Growth per<br/>60 ticks
! style=max-width:20em colspan=2 | Time to 100% severity
|-
! style=max-width:15em | [[Ticks]]
! style=max-width:15em | In-game time
|-
| rowspan='9'|{{Graph:Chart
|width=200
|height=200
|type=line
|x=10, 12, 14, 16, 18, 20, 22, 24, 26, 28, 30, 32, 34, 36, 38, 40, 42, 44, 46, 48, 50, 52, 54, 56, 58, 60, 62, 64, 66, 68, 70, 72, 74, 76, 78, 80, 82, 84, 86, 88, 90, 92, 94, 96, 98, 100
|y=64.0, 64.0, 64.0, 62.0, 46.5, 37.2, 31.0, 26.6, 23.3, 20.7, 18.6, 16.9, 15.5, 14.5, 13.9, 13.3, 12.7, 12.2, 11.8, 11.3, 10.9, 10.6, 10.2, 9.9, 9.6, 9.3, 9.1, 8.9, 8.8, 8.6, 8.5, 8.3, 8.2, 8.0, 7.9, 7.8, 7.6, 7.5, 7.4, 7.3, 7.2, 7.0, 6.9, 6.8, 6.7, 6.6
|xAxisTitle = Ambient Temperature - Maximum Comfortable Temperature (°C)
|yAxisTitle = Time to 100% Severity (hours)
}}
| 0 || 0 || - || -
|-
| 10 || 0.000375 || 160000 || 2.7 days
|-
| 15 || 0.000375 || 160000 || 2.7 days
|-
| 20 || 0.000645 || {{0}}93023 || 1.6 days
|-
| 25 || 0.000967 || {{0}}62016 || 24.8 hours
|-
| 100 || 0.003225 || {{0}}18605 || 7.4 hours
|-
| 300 || 0.005160 || {{0}}11628 || 4.7 hours
|-
| 1000 || 0.015480 || {{0|00}}3876 || 1.6 hours
|-
| 4000 || 0.063855 || {{0|000}}939 || 0.4 hours
|}
<references />
</div>

====Severity Decrease====
If the ambient temperature is less than the maximum comfortable temperature, the amount the severity will decrease every 60-tick interval is given by:
:<code>Decrease in heatstroke severity every 60 ticks = max(0.0015, min(0.015, 0.027 × heatstroke_severity))</code>
This means that as long as the ambient temperature is less than the maximum comfortable temperature, heatstroke recovery is independent of temperature. Severity decreases at a constant rate of 1.5% when at 55.6% or above, slowing down until reaching its slowest (0.15%) at 5.6% and below. Full recovery from near-100% severity occurs after 151 real-time seconds, or 3.6 in-game hours.
{{Graph:Chart
|width=200
|height=200
|type=line
|x= 0, 0.024, 0.048, 0.072, 0.096, 0.12, 0.144, 0.168, 0.192, 0.216, 0.24, 0.264, 0.288, 0.312, 0.336, 0.36, 0.384, 0.408, 0.432, 0.456, 0.48, 0.504, 0.528, 0.552, 0.576, 0.6, 0.624, 0.648, 0.672, 0.696, 0.72, 0.744, 0.768, 0.792, 0.816, 0.84, 0.864, 0.888, 0.912, 0.936, 0.96, 0.984, 1.008, 1.032, 1.056, 1.08, 1.104, 1.128, 1.152, 1.176, 1.2, 1.224, 1.248, 1.272, 1.296, 1.32, 1.344, 1.368, 1.392, 1.416, 1.44, 1.464, 1.488, 1.512, 1.536, 1.56, 1.584, 1.608, 1.632, 1.656, 1.68, 1.704, 1.728, 1.752, 1.776, 1.8, 1.824, 1.848, 1.872, 1.896, 1.92, 1.944, 1.968, 1.992, 2.016, 2.04, 2.064, 2.088, 2.112, 2.136, 2.16, 2.184, 2.208, 2.232, 2.256, 2.28, 2.304, 2.328, 2.352, 2.376, 2.4, 2.424, 2.448, 2.472, 2.496, 2.52, 2.544, 2.568, 2.592, 2.616, 2.64, 2.664, 2.688, 2.712, 2.736, 2.76, 2.784, 2.808, 2.832, 2.856, 2.88, 2.904, 2.928, 2.952, 2.976, 3.0, 3.024, 3.048, 3.072, 3.096, 3.12, 3.144, 3.168, 3.192, 3.216, 3.24, 3.264, 3.288, 3.312, 3.336, 3.36, 3.384, 3.408, 3.432, 3.456, 3.48, 3.504, 3.528, 3.552, 3.576, 3.6, 3.624
|y= 1, 0.985, 0.97, 0.955, 0.94, 0.925, 0.91, 0.895, 0.88, 0.865, 0.85, 0.835, 0.82, 0.805, 0.79, 0.775, 0.76, 0.745, 0.73, 0.715, 0.7, 0.685, 0.67, 0.655, 0.64, 0.625, 0.61, 0.595, 0.58, 0.565, 0.55, 0.53515, 0.5207, 0.50664, 0.49296, 0.47965, 0.4667, 0.4541, 0.44184, 0.42991, 0.4183, 0.40701, 0.39602, 0.38533, 0.37492, 0.3648, 0.35495, 0.34537, 0.33604, 0.32697, 0.31814, 0.30955, 0.30119, 0.29306, 0.28515, 0.27745, 0.26996, 0.26267, 0.25558, 0.24868, 0.24196, 0.23543, 0.22907, 0.22289, 0.21687, 0.21101, 0.20532, 0.19977, 0.19438, 0.18913, 0.18402, 0.17906, 0.17422, 0.16952, 0.16494, 0.16049, 0.15615, 0.15194, 0.14784, 0.14384, 0.13996, 0.13618, 0.1325, 0.12893, 0.12545, 0.12206, 0.11876, 0.11556, 0.11244, 0.1094, 0.10645, 0.10357, 0.10078, 0.09806, 0.09541, 0.09283, 0.09033, 0.08789, 0.08551, 0.0832, 0.08096, 0.07877, 0.07665, 0.07458, 0.07256, 0.0706, 0.0687, 0.06684, 0.06504, 0.06328, 0.06157, 0.05991, 0.05829, 0.05672, 0.05519, 0.05369, 0.05219, 0.05069, 0.04919, 0.04769, 0.04619, 0.04469, 0.04319, 0.04169, 0.04019, 0.03869, 0.03719, 0.03569, 0.03419, 0.03269, 0.03119, 0.02969, 0.02819, 0.02669, 0.02519, 0.02369, 0.02219, 0.02069, 0.01919, 0.01769, 0.01619, 0.01469, 0.01319, 0.01169, 0.01019, 0.00869, 0.00719, 0.00569, 0.00419, 0.00269, 0.00119, 0
|xAxisTitle = Time (hours)
|yAxisTitle = Heatstroke severity
}}
====Symptoms====
{| class="wikitable"
|-
! Stage !! Begins at !! Symptoms
|-
| '''Heatstroke (initial)''' || >0.04 Severity ||
* [[Consciousness]] {{Bad|-5%}}
|-
| '''Heatstroke (minor)''' || >0.20 Severity ||
* [[Consciousness]] {{Bad|-10%}}
* [[Moving]] {{Bad|-10%}}
|-
| '''Heatstroke (serious)''' || >0.35 Severity ||
* [[Consciousness]] {{Bad|-20%}}
* [[Moving]] {{Bad|-30%}}
* [[Pain]] {{Bad|+15%}}
|-
| '''Heatstroke (extreme)''' || >0.62 Severity ||
* [[Consciousness]] max. 10%
* [[Pain]] {{Bad|+30%}}
|-
| '''Heatstroke (100%)''' || =1.00 Severity ||
* [[Death]]
|}

=== Hypothermia ===
Hypothermia occurs when a pawn has prolonged exposure to [[temperature]]s 10°C (18°F) below their [[minimum comfortable temperature]]. [[Insectoids]] don't experience hypothermia, but instead get [[hypothermic slowdown]].

Note that it is possible for a pawn to have both heatstroke and hypothermia at the same time if time is spent in both extreme heat and cold - their severities are unrelated.


The rate of severity growth depends on the difference below the pawn's minimum safe temperature and the ambient temperature. The specific algorithm is:
# Take the amount by which the pawn's minimum safe temperature (which is the [[minimum comfortable temperature]] -10°C) exceeds the ambient temperature.
# Multiply the excess by <code>6.45e-5</code> to obtain the severity growth this interval. Note that unlike [[#Heatstroke|hyperthermia]], hypothermia calculations don't use a postprocessing curve.
# If the growth is less than <code>0.00075</code>, set it to that number. As a result, temperatures between 10°C and 21.63°C less than the minimum comfortable temperature all have the same severity growth.
Expressed as a formula, this is:
:<code>Increase in hypothermia severity every 60 ticks = max(0.00075, (<i>degrees_below_comfortable</i> - 10)*0.0000645)</code>

{| class="wikitable" style="margin: auto;"
|- class=static-row-header style=vertical-align:center
! rowspan=2 | Graph
! style=max-width:20em rowspan=2 | Temperature<br/>Delta<ref><small>Minimum Comfortable Temperature - Ambient Temperature</small></ref>(°C)
! style=max-width:15em rowspan=2 | Growth per<br/>60 ticks
! style=max-width:20em colspan=2 | Time to 100% severity
|-
! style=max-width:15em | [[Ticks]]
! style=max-width:15em | In-game hours
|-
| rowspan='8'|{{Graph:Chart
|width=200
|height=200
|type=line
|x = 10, 12, 14, 16, 18, 20, 22, 24, 26, 28, 30, 32, 34, 36, 38, 40, 42, 44, 46, 48, 50, 52, 54, 56, 58, 60, 62, 64, 66, 68, 70, 72, 74, 76, 78, 80, 82, 84, 86, 88, 90, 92, 94, 96, 98, 100
|y = 32.0, 32.0, 32.0, 32.0, 32.0, 32.0, 31.0, 26.6, 23.3, 20.7, 18.6, 16.9, 15.5, 14.3, 13.3, 12.4, 11.6, 10.9, 10.3, 9.8, 9.3, 8.9, 8.5, 8.1, 7.8, 7.4, 7.2, 6.9, 6.6, 6.4, 6.2, 6.0, 5.8, 5.6, 5.5, 5.3, 5.2, 5.0, 4.9, 4.8, 4.7, 4.5, 4.4, 4.3, 4.2, 4.1
|xAxisTitle = Minimum Comfortable Temperature - Ambient Temperature(°C)
|yAxisTitle = Time to 100% Severity (hours)
|yAxisMin = 0
}}
| 0 || 0 || - || -
|-
| 10 || 0.000750 || 80000 || 32.0
|-
| 20 || 0.000750 || 80000 || 32.0
|-
| 25 || 0.000967 || 62016 || 24.8
|-
| 50 || 0.002580 || 23256 || {{0}}9.3
|-
| 100 || 0.005805 || 10336 || {{0}}4.1
|-
| 200 || 0.012255 || {{0}}4896 || {{0}}2.0 
|-
| 300 || 0.018705 || {{0}}3208 || {{0}}1.3
|}
<references />

Recovery from hypothermia uses the same process as recovery from heatstroke, which results in complete recovery within 3.6 in-game hours:
:<code>Decrease in hypothermia severity every 60 ticks = max(0.0015, min(0.015, 0.027 × hypothermia_severity))</code>
{| class="wikitable" style="margin: auto;"
|-
! Stage !! Begins at !! Symptoms
|-
| '''Hypothermia (shivering)''' || >0.04 Severity ||
* [[Consciousness]] {{Bad|-5%}}
* [[Manipulation]] {{Bad|-8%}}
|-
| '''Hypothermia (minor)''' || >0.20 Severity ||
* [[Consciousness]] {{Bad|-10%}}
* [[Manipulation]] {{Bad|-20%}}
* [[Moving]] {{Bad|-10%}}
|-
| '''Hypothermia (serious)''' || >0.35 Severity ||
* [[Consciousness]] {{Bad|-20%}}
* [[Manipulation]] {{Bad|-50%}}
* [[Moving]] {{Bad|-30%}}
* [[Pain]] {{Bad|+15%}}
|-
| '''Hypothermia (extreme)''' || >0.62 Severity ||
* [[Consciousness]] max. 10%
* [[Pain]] {{Bad|+30%}}
|-
| '''Hypothermia (100%)''' || =1.00 Severity ||
* [[Death]]
|}

=== Hypothermic slowdown ===
{{quote|A special biological state used by some creatures to survive extreme cold. Instead of trying to stay warm, the creature's body chemistry adapts to prevent internal freezing despite very low temperature. Bodily functions are slowed and capacities are reduced, but the cold does no permanent damage. Some biologists call it a wakeful form of hibernation.}}

[[Insectoids]] avoid hypothermia and experience hypothermic slowdown instead with similar penalties but avoiding death at 100% and no [[frostbite]].

Slowdown value increases many times above 100% with apparently no upper limit. When defrosting insects this total value is used so defrost time is proportional to total time frozen.


The rate of severity growth depends on the difference below the pawn's minimum safe temperature and the ambient temperature. The specific algorithm is:
# Take the amount by which the pawn's minimum safe temperature (which is the [[minimum comfortable temperature]] -10°C) exceeds the ambient temperature.
# Multiply the excess by <code>6.45e-5</code> to obtain the severity growth this interval. Note that unlike hyperthermia, hypothermia calculations don't use a postprocessing curve.
# If the growth is less than <code>0.00075</code>, set it to that number. As a result, temperatures between 10°C and 21.63°C less than the minimum comfortable temperature all have the same severity growth.
Expressed as a formula, this is:
:<code>Increase in hypothermia severity every 60 ticks = max(0.00075, (<i>degrees_below_comfortable</i> - 10)*0.0000645)</code>
{{Graph:Chart
|width=200
|height=200
|type=line
|x = 10, 12, 14, 16, 18, 20, 22, 24, 26, 28, 30, 32, 34, 36, 38, 40, 42, 44, 46, 48, 50, 52, 54, 56, 58, 60, 62, 64, 66, 68, 70, 72, 74, 76, 78, 80, 82, 84, 86, 88, 90, 92, 94, 96, 98, 100
|y = 32.0, 32.0, 32.0, 32.0, 32.0, 32.0, 31.0, 26.6, 23.3, 20.7, 18.6, 16.9, 15.5, 14.3, 13.3, 12.4, 11.6, 10.9, 10.3, 9.8, 9.3, 8.9, 8.5, 8.1, 7.8, 7.4, 7.2, 6.9, 6.6, 6.4, 6.2, 6.0, 5.8, 5.6, 5.5, 5.3, 5.2, 5.0, 4.9, 4.8, 4.7, 4.5, 4.4, 4.3, 4.2, 4.1
|xAxisTitle = Minimum Comfortable Temperature - Ambient Temperature(°C)
|yAxisTitle = Time to 100% Severity (hours)
|yAxisMin = 0
}}
<div style="display:inline-table; vertical-align:top;">
{| class="wikitable"
|-class=static-row-header style=vertical-align:bottom
! style=max-width:20em | Minimum Comfortable Temperature - Ambient Temperature(°C)
! style=max-width:15em | Growth per<br>{{ticks|60}}
! style=max-width:15em | Real Time<br>to 63% severity
! style=max-width:15em | In-Game Time<br>to 63% severity
! style=max-width:15em | Real Time<br>to 100% severity
! style=max-width:15em | In-Game Time<br>to 100% severity
|-
| 0 || 0 || - || - || - || -
|-
| 5 || 0 || - || - || - || -
|-
| 10
| 0.075%
| {{ticks|{{#expr: (0.63/(0.00075)) * 60}} }}
| {{#expr: (0.63/(0.00075)) * 60/2500 round 1}} hrs
| {{ticks|{{#expr: (1/(0.00075)) * 60}} }}
| {{#expr: (1/(0.00075)) * 60/2500 round 1}} hrs
|-
| 20
| 0.075%
| {{ticks|{{#expr: (0.63/(0.00075)) * 60}} }}
| {{#expr: (0.63/(0.00075)) * 60/2500 round 1}} hrs
| {{ticks|{{#expr: (1/(0.00075)) * 60}} }}
| {{#expr: (1/(0.00075)) * 60/2500 round 1}} hrs
|-
| 25
| {{#expr: (25-10)*0.0000645 * 100}}%
| {{ticks|{{#expr: (0.63/(( 25-10)*0.0000645)) * 60 round 0}} }}
| {{#expr: (0.63/(( 25-10)*0.0000645)) * 60/2500 round 1}} hrs
| {{ticks|{{#expr: (1/(( 25-10)*0.0000645)) * 60 round 0}} }}
| {{#expr: (1/(( 25-10)*0.0000645)) * 60/2500 round 1}} hrs
|-
| 50
| {{#expr: (50-10)*0.0000645 * 100}}%
| {{ticks|{{#expr: (0.63/(( 50-10)*0.0000645)) * 60 round 0}} }}
| {{#expr: (0.63/(( 50-10)*0.0000645)) * 60/2500 round 1}} hrs
| {{ticks|{{#expr: (1/(( 50-10)*0.0000645)) * 60 round 0}} }}
| {{#expr: (1/(( 50-10)*0.0000645)) * 60/2500 round 1}} hrs
|-
| 100
| {{#expr: (100-10)*0.0000645 * 100}}%
| {{ticks|{{#expr: (0.63/((100-10)*0.0000645)) * 60 round 0}} }}
| {{#expr: (0.63/((100-10)*0.0000645)) * 60/2500 round 1}} hrs
| {{ticks|{{#expr: (1/((100-10)*0.0000645)) * 60 round 0}} }}
| {{#expr: (1/((100-10)*0.0000645)) * 60/2500 round 1}} hrs
|-
| 300
| {{#expr: (300-10)*0.0000645 * 100}}%
| {{ticks|{{#expr: (0.63/((300-10)*0.0000645)) * 60 round 0}} }}
| {{#expr: (0.63/((300-10)*0.0000645)) * 60/2500 round 1}} hrs
| {{ticks|{{#expr: (1/((300-10)*0.0000645)) * 60 round 0}} }}
| {{#expr: (1/((300-10)*0.0000645)) * 60/2500 round 1}} hrs
|}
</div>
Recovery from hypothermia uses the same process as recovery from heatstroke, which results in complete recovery within 3.6 in-game hours:
:<code>Decrease in hypothermia severity every 60 ticks = max(0.0015, min(0.015, 0.027×hypothermia_severity))</code>
{| class="wikitable"
|-
! Stage !! Begins at !! Symptoms
|-
| '''Hypothermic slowdown (minor)''' || >0.04 Severity ||
* [[Consciousness]] -5%
* [[Moving]] -8%
|-
| '''Hypothermic slowdown (moderate)''' || >0.20 Severity ||
* [[Consciousness]] -20%
* [[Moving]] -20%
* [[Manipulation]] -20%
* Hunger rate -10%
|-
| '''Hypothermic slowdown (serious)''' || >0.35 Severity ||
* [[Consciousness]] -40%
* [[Moving]] -40%
* [[Manipulation]] -50%
* Hunger rate -40%
|-
| '''Hypothermic slowdown (extreme)''' || >0.62 Severity ||
* [[Consciousness]] max. 10%
* Hunger rate -95%
|}

=== Vacuum exposure ===
{{Odyssey|section=1}}
Vacuum exposure occurs when a pawn is subjected to [[Orbit|hard vacuum]] without adequate protection.

The rate of severity growth is directly proportional to the vacuum percentage of the pawn's current tile, and to the difference between 1 and a pawn's [[vacuum resistance]] stat. Vacuum will be 100% outside pressurized rooms; otherwise, it will vary depending on the presence of [[oxygen pump]]s, open connections to other rooms, and so on. The specific algorithm is:
# Start with a default of 2% per second.
# Multiply the amount by the tile's current vacuum percentage.
# Multiply the product by the difference between 1 and the pawn's vacuum resistance.
Expressed as a formula, the increase of severity every {{ticks|60}} is:
:<code>Increase in vacuum exposure severity = 0.02 * tile vacuum percentage * (1 - vacuum resistance)</code>

Vacuum exposure builds up extremely quickly in pawns without significant vacuum resistance. An unprotected pawn with no resistance will die in just {{ticks|3000}} of exposure to a complete vacuum, making even brief spacewalks a risky prospect.

Pawns recover quickly from vacuum exposure while inside a pressurized area; severity will simply fall at a flat 10% per second until the condition disappears entirely. Affected pawns that reach 100% vacuum resistance while still exposed (such as by equipping a [[vacsuit]]) will keep their current level of exposure until they return to a pressurized tile, but its severity will not increase any further.

{| class = "wikitable" style="margin: auto;"
|-
! Stage !! Begins at<br/>severity !! Symptoms
|-
| '''Vacuum exposure (initial)''' || Initial ||
|-
| '''Vacuum exposure (initial)''' || ≥15% ||
* {{Bad|-{{0}}5%}} [[Consciousness]]
* {{Bad|+{{0}}5%}} [[Pain]]
|-
| '''Vacuum exposure (mild)''' || ≥30% ||
* {{Bad|-10%}} [[Consciousness]]
* {{Bad|+{{0}}8%}} [[Pain]]
|-
| '''Vacuum exposure (moderate)''' || ≥50% ||
* {{Bad|-20%}} [[Consciousness]]
* {{Bad|+10%}} [[Pain]]
|-
| '''Vacuum exposure (extreme)''' || ≥85% ||
* [[Consciousness]] max. 10%
* {{Bad|+10%}} [[Pain]]
|-
| '''Vacuum exposure (extreme)''' || 100% ||
* [[Death]]
|}
----
{| class = "wikitable mw-collapsible" style="margin: auto;" width=100%
|-
!Graph
|-
| {{Graph:Chart
|width=940
|height=600
|type=line
|legend=Legend
|y1Title=No vacuum resistance [50s]
|y2Title=Vacsuit chest only (32%) [73s]
|y3Title= Vacuum resistant (45%) [90.9s]
|y4Title=Vacsuit helmet only (69%) [161s]
|y5Title= Vacskin Gland (85%) [5 min 33s]
|y6Title=Full Recon armour (95%) [16min 40s]
|y7Title=Full Marine armour (97%) [27min 46s]
|y8Title=Full Cataphract armour (98%) [41.7min]
|y9Title= Vacsuit helmet and any power armor (99%) [83.3min]

|x = 0,50,73.5,90.0,161.3,333.3,1000,1666.7,2500,5000
|y1=0,100
|y2=0,68.03,100
|y3=0,55.56,81.67,100
|y4=0,30.99,45.56,55.79,100
|y5=0,15,22.05,27,48.4,100
|y6=0,5,7.35,9,16.13,33.33,100
|y7=0,3,4.41,5.40,9.68,20,60,100
|y8=0,2,2.94,3.6,6.45,13.33,40,66.67,100
|y9=0,1,1.47,1.8,3.23,6.67,20,33.33,50,100
|xAxisTitle = Time (s)
|yAxisTitle = Vacuum exposure (%)
}}
|}

== Pregnancy ==
{{See also|Animals#Mating{{!}}Mating|Animals#Breeding{{!}}Breeding|Reproduction{{!}}Human pregnancy}}
{{quote|This creature is gestating offspring. It will give birth if the pregnancy comes to term. If starved or injured, there may be a miscarriage.|Description}}

Tamed, non-[[human]], non-[[insectoid]], non-[[egg]]laying, female [[animals]] have a 50% chance to get pregnant from [[Animals#Mating|mating]]. While this is not an ailment in the traditional sense, it does have mechanical effects. For the first {{ticks|600}} this condition will be invisible, after which point a message will come up mentioning the pregnancy.

Humans can be pregnant only if the [[Biotech DLC]]{{BiotechIcon}} is enabled. They have a different list of symptoms. See [[Reproduction]] for details.

A pregnant animal suffering from [[malnutrition]] of 25% or higher or that is injured may miscarry. Miscarriages are noted by an in-game message.

Some animals will give birth to multiple young. The probability of this is determined by a curve, and is different for each animal.

The duration, and thus the severity gain per day, depends on the gestation time of the animal in question.
{| class="wikitable"
|-
! Stage !! Begins at !! Symptoms
|-
| '''Early-stage''' || >0 Severity ||
* [[Vomiting]] (''MTB of 2.5 days'')
|-
| '''Middle-stage''' || >0.333 Severity ||
* {{--|15%}} [[Moving]]
|-
| '''Late-stage''' || >0.666 Severity||
* [[Vomiting]] (''MTB of 5 days'')
* {{--|30%}} [[Moving]]
|-
| '''''Birth''''' || 1.0 Severity||
* Symptoms end
* Offspring is born
|}

=== Sterilized ===
{{Stub|section=1|reason=Missing details, sources, mechanics etc. Are there any other causes in humans?}}
{{Quote|This creature's reproductive system has been permanently shut down.|Description}}
[[Animals]] can be sterilized by use of the "Sterilize" [[operation]] to prevent them from being able to reproduce, and the sterilized animal won't attempt to mate with others nor will others attempt to mate with it. [[Egg]] laying animals will stop laying eggs when sterilized. The animal acts as normal in all other ways, including [[milk]] production.

Sterilizing a pregnant animal will not terminate the pregnancy.

The sterilization operation requires [[Medical]] skill of 3 and {{ticks|500}} of work.

Humans with the "Sterilized" health trait can only be healed with a [[healer mech serum]]. Pawns can{{Check Tag|Will?|Is it all failures or just a chance?}} receive the sterilized ailment from a failed vasectomy or IUD insertion.{{BiotechIcon}} It is currently unknown if there are other sources.

== Drug damage ==
These ailments are caused by excess drug use.

=== Cirrhosis ===
A degenerative [[liver]] disease caused by excessive [[alcohol]] consumption.
An otherwise healthy pawn with cirrhosis will have an [[immunity gain speed]] of 70%, making them extremely vulnerable to disease.

{| class="wikitable"
|-
! Ailment !! Symptoms
|-
| '''Cirrhosis''' ||
* -60% part efficiency (liver)
* Slight [[pain]] (+15%)
* -10% [[Moving]]
|}

Treatment:
* The easiest method of treatment is the [[Organ harvesting|transplantation]] of a new liver. Due to the extreme vulnerability to disease, even if your colony dislikes organ harvesting it may be worth it to replace the livers of valuable pawns as doctors will struggle to get high enough tend qualities on diseases to counterbalance the decreased immunity gain, often needing a very good hospital plus a very good doctor or [[glitterworld medicine]] to do so.
* Other than transplantation, only [[healer mech serum]] and [[unnatural healing]]{{AnomalyIcon}} can cure cirrhosis.

Alcohol [[tolerance]] above '''45%''' imposes a chance to get [[cirrhosis]] in the liver proportional to the tolerance held.
{| class="wikitable" style="text-align:right"
! Tolerance !! Average cirrhosis interval !! Graph
|-
| 45% || 99999 Days
| rowspan="3" | {{Graph:Chart| width = 400 | height = 100 | type = line | xAxisTitle = Tolerance (%) | yAxisTitle = MTB Cirrhosis (Days) | x = 49, 50, 100 | y = 250, 60, 45 | xAxisMin = 45 | yAxisMax = 250}}
|-
| 50% || 60 Days
|-
| 100% || 45 Days
|}

=== Chemical damage ===
Permanent damage that occurs as a result of drug overdose or tolerance. There are two variants.

{| class="wikitable"
|-
! Ailment !! Symptoms
|-
| '''Chemical damage (moderate)''' ||
* -50% part efficiency
* Always applied to the brain
|-
| '''Chemical damage (severe)''' ||
* -80% part efficiency
* Always applied to the kidneys
|}

Treatment:
* Kidney chemical damage can be cured by replacing with a non-damaged [[kidney]] or with a [[detoxifier kidney]]{{BiotechIcon}}
* Brain chemical damage can only be cured with a [[healer mech serum]] or via [[unnatural healing]]{{AnomalyIcon}}

==Trauma savant==
Injuries to the brain can cause increased motor function, but loss of social capabilities.
{| class="wikitable"
|-
! Ailment !! Symptoms
|-
| '''Trauma savant''' ||
* +50% [[Manipulation]]
* x0% [[Talking]] and [[Hearing]]
* Brain damage does not affect part efficiency
* Nullifies all opinions of other pawns
|}

The chance to receive trauma savant on any physical (non-chemical) [[injury]] to the brain is equal to the percentage of the brain damaged multiplied by 0.12. For an adult human, this represents 1.2% chance per point of damage. Animals can also become trauma savants.

A [[Ghoul|Ghoul]]{{AnomalyIcon}} or a humans with the [[Scarless]]{{BiotechIcon}} gene will not get brain scars from damage to their brain, but they still have a chance to become trauma savants. This makes it possible to voluntarily give the condition to a pawn by repeatedly damaging and healing their brain, although this can be time consuming and expensive. For an adult human, the brain will need to take on average 83 points of damage. Using other methods to heal the brain such as the [[Biosculpter pod#Bioregeneration|Bioregeneration cycle]] of the [[biosculpter pod]]{{IdeologyIcon}} is theoretically possible, but prohibitively expensive.

Currently, the most cost-effective known method to damage the brain is to purposefully fail the surgery to remove a [[Painstopper|painstopper]]. Painstoppers are the cheapest brain implant that can be removed. Attempting to remove it costs only one [[herbal medicine]] and failing will not destroy the implant. Performing the operation outside, on a [[Sleeping spot]] or an [[Ancient bed]],{{IdeologyIcon}} in the dark, with a low level surgeon with lowered Sight and Manipulation will maximize the chance for the operation to fail. If the operation accidentally succeeds, then the patient should be moved to a high quality hospital to reinsert the painstopper, as failure would destroy the implant and greatly increase the overall cost. It takes on average between 50 and 100 failed brain operations for a patient to become trauma savant.

Trauma savant negates the [[consciousness]] penalty from all brain damage, including scars that existed before the condition. On another hand, those brain scars will still lower the brain's health and can potentially still cause pain. Also, Trauma savant will not prevent loss of consciousness from other brain conditions like Dementia.

Trauma savant can be healed with a [[healer mech serum]] or the [[Unnatural healing]]{{AnomalyIcon}} ability (or possibly through other means as well). It can also be treated by killing the pawn, [[Skull|removing their skull]]{{IdeologyIcon}} then resurrecting thanks to a [[Resurrector mech serum]] or [[death refusal]]{{AnomalyIcon}}.

==Bliss lobotomy==
{{Anomaly|section = 1}}
{{Main|Bliss lobotomy}}
A whole-body condition that gives a constant +20 mood bonus but imposes a -50% global learning factor penalty. Makes pawn incapable of cooking, construction, plant work, mining, crafting and intellectual. Can generate on [[horax cult|cultist]] raiders or be deliberately induced via a brain surgery at the cost of 2 medicine and 30 [[bioferrite|bioferrites]].

== General ==
These ailments appear in gameplay, and usually wear off on their own (except death-causing ones).

=== Cryptosleep sickness ===
After-effects of using a cryptosleep pod. Cryptosleep suspends and replaces many bodily functions in order to prevent aging and death. Upon exiting cryptosleep, the body takes time to restart and rebalance its natural metabolic processes. While this is ongoing, the patient suffers from nausea, dizziness, and a sense of fuzziness in the mind.

Occurs after having been in a [[ship cryptosleep casket]] or a [[cryptosleep casket]] for any amount of time. The colonists in the "[[Crashlanded]]" scenario have a chance of starting with cryptosleep sickness, as they were in cryptosleep before crashing on the planet.

{| class="wikitable"
|-
! Ailment !! Symptoms
|-
| '''Cryptosleep sickness''' ||
* Frequent [[vomiting]] (''MTB of 3 hours'')
* Impaired [[consciousness]] (×80%)
* Impaired [[moving]] (×90%)
* Impaired [[manipulation]] (×90%)
|}
Treatment:
* Wears off after {{ticks|10000}}

=== Food poisoning ===
Occurs after eating a contaminated meal or occasionally from raw food. The chance of contamination for cooked meals is primarily determined by the cook's [[food poison chance]] stat, with the [[Cleanliness|cleanliness of the room]] where it was prepared also being a potential factor.

[[Corpse]]s have a flat chance of 5% to give food poisoning. Other raw food has a flat chance in between 1% and 4% depending on the type of food — most raw food having a 2% chance. Cooked meals roll two separate probabilities to determine if the food is poisoned. The first checks the [[cleanliness]] of the kitchen used. See the accompanying graph for specifics. Note that cleanliness above -2 prevents this roll from producing poisoned meals. If the cooking station is outdoors, the default chance is 2%.

If the first roll fails to poison the meal, then a second roll is performed, this time based on the [[food poison chance]] of the pawn, controlled entirely by their [[Cooking|cooking skill]].
If the second roll indicates that the meal is poisonous, the probability of poisoning the pawn is 100% for that individual meal. However, when the poisonous meal is part of a stack with other meals, the probability is distributed among all the meals in the stack. This distribution reduces the chance of food poisoning from 100% to the ratio of total meals to poisonous meals within the stack. For instance, if a poisonous meal is placed on top of a stack containing three non-poisonous meals, the probability for each meal to poison the pawn becomes 25%. Consequently, even if the original meal was poisonous, there is a possibility that no pawns will experience food poisoning.

Because of the penalty to [[blood filtration]] and [[consciousness]], food poisoning in combination with other ailments such as an [[infection]] can be a cause for concern.

{| class = "wikitable" width="180" style="margin: auto; text-align:center;"
! Cooking Skill Level
! Chance from Skill Level
! Chance from Room Cleanliness
|-
| style="background-color:#F00000" | '''0''' || style="background-color:#F00000" | '''5.00%''' || rowspan="10"| {{Graph:Chart|width=400|height=100|type=line|x=-5, -3.5, -2, 0|y=5, 2.5, 0, 0|xAxisTitle=Room Cleanliness|yAxisTitle=Food Poisoning Chance (%)}}
Chance = ([[Cleanliness|Room Cleanliness]] + 2) * 0.05 / 3<br/>
Capped between 0% and 5%

|- style="background-color:#FF5500"
| '''1''' || '''4.00%'''
|- style="background-color:#FBA933"
| '''2''' || '''3.00%'''
|- style="background-color:#E3C933"
| '''3''' || '''2.00%'''
|- style="background-color:#E3E933"
| '''4''' || '''1.50%'''
|- style="background-color:#C3FF33"
| '''5''' || '''1.00%'''
|- style="background-color:#B6FF00"
| '''6''' || '''0.50%'''
|- style="background-color:#86FF00"
| '''7''' || '''0.25%'''
|- style="background-color:#66FF00"
| '''8''' || '''0.15%'''
|- style="background-color:#00FF00"
| '''9-20''' || '''0.10%'''
|}</div>

; Symptoms and progress:
Food poisoning lasts 24 hours with no after-effects. It has 3 stages: the first unpleasant 4 hours, followed by a crippling 16 hours, and finally an unpleasant 4 hours largely similar to the first stage, as described in the table below.
{| class="wikitable" style="margin: auto;"
|-
! Stage !! Begins at !! Symptoms
|-
| '''Food poisoning (initial)''' || 0–4 hours from onset ||
* [[Vomiting]] (''MTB of 0.3 days'')
* Some [[pain]] (+20%)
* Impaired [[consciousness]] (×60%)
* Impaired [[moving]] (×80%)
* Impaired [[manipulation]] (×90%)
* Reduced [[blood filtration]] (×95%)
* Slower [[Eating speed|eating]] (×50%)
|-
| '''Food poisoning (major)''' || 4–20 hours from onset ||
* [[Vomiting]] (''MTB of 0.2 days'')
* Significant [[pain]] (+40%)
* Impaired [[consciousness]] (×50%)
* Impaired [[moving]] (×50%)
* Impaired [[manipulation]] (×80%)
* Reduced [[blood filtration]] (×85%)
* Much slower [[Eating speed|eating]] (×30%)
|-
| '''Food poisoning (recovering)''' || 20–24 hours from onset ||
* [[Vomiting]] (''MTB of 0.4 days'')
* Some [[pain]] (+20%)
* Impaired [[consciousness]] (×60%)
* Impaired [[moving]] (×80%)
* Impaired [[manipulation]] (×90%)
* Reduced [[blood filtration]] (×95%)
* Slower [[Eating speed|eating]] (×50%)
|}
; Treatment and Prevention
Food poisoning can only be minimized by manipulating the factors that cause it mentioned above. Prevention can only be guaranteed by exclusively consuming meals purchased from traders or by making [[Baby food]] or [[nutrient paste meal]]s as they will never cause food poisoning. Installing a [[sterilizing stomach|sterilizing]],{{RoyaltyIcon}} [[nuclear stomach]],{{RoyaltyIcon}} or [[fleshmass stomach]],{{AnomalyIcon}} or having the [[strong stomach]] gene{{BiotechIcon}} render pawns immune to contracting food poisoning. Note that [[bionic stomach]]s reduce the chance of getting food poisoning by 50% but cannot outright prevent it.

The notification for a colonist being poisoned will explain the cause of the poisoning. This can be very helpful if an unattended kitchen was allowed to cross into the very dirty -2 cleanliness danger zone, as a nearby cleaner can simply be ordered to clean the kitchen and avoid more unnecessary poisoning.

There is no practical treatment for food poisoning, you simply have to let it run its course. [[Healer mech serum]] will cure it (if there is nothing worse to cure), but this costly measure is rarely if ever worthwhile, as food poisoning only affects the pawn for the 24 hour cycle and then leaves them as healthy as they were before. [[Unnatural healing]]{{AnomalyIcon}} is the vastly more economical option, though it carries opportunity cost of the 6 day cooldown.

Because of the high chance of [[vomiting]] at any moment, which interrupts and resets the process of eating, combined with the reduction in eating speed, patients with food poisoning may be at risk of developing [[malnutrition]]. With the already impaired consciousness and moving capacity from the poisoning, stacking malnutrition on top of that could lead to a [[downed]] state, so it may be worth supervising poisoned pawns in case they need rescue. A diet of small unit foods such as [[pemmican]] will not mitigate this issue, as there is no concept of incremental eating - a pawn takes the same time to consume one pemmican as it takes to consume 18 pemmican, and if interrupted part way through, all the pemmican pieces remain uneaten.

=== Toxic buildup ===
Primarily occurs with exposure to [[toxic fallout]], [[pollution]],{{BiotechIcon}} [[tox gas]],{{BiotechIcon}} and tox rain.{{OdysseyIcon}} Prolonged exposure gradually increases the buildup severity.

Alternatively, some attacks cause instantaneous increases in toxic buildup severity, such as [[cobra]] and [[waste rat]] {{BiotechIcon}} bites, the [[venom talon]],{{RoyaltyIcon}} or [[venom fangs]].{{RoyaltyIcon}}

A colonist under a roof is protected from toxic fallout and tox rain, and avoiding interaction with the other sources can prevent buildup from them. If they are exposed to toxic fallout, they will accumulate Toxic Buildup at a rate of 40% per day. Pollution will accumulate at the same rate, but cannot be mitigated through roofing. When walking through polluted terrain in [[caravan]]s, they will accumulate buildup at 20% per day in Moderately Polluted terrain (50%-75% polluted tiles) and 40% per day in Extremely Polluted terrain (above 75%). Buildup from both pollution as well as toxic fallout can stack, meaning a pawn standing in polluted terrain while a toxic fallout can gain 80%/day.{{Check Tag|Rate from tox rain?}}

There are two stats that reduce toxic build up stats:
* All sources of toxic buildup are affected by the [[Toxic Resistance]] [[stat]]. [[Human]]s buildup at the full rate, [[animal]]s at half, and [[insects]] and [[mechanoids]] are immune.{{Check Tag|Body Size?|Buildup severities from Damage types are now inversely proportional to body size, are all sources scaled? Either way, add detail}} Some ways of increasing this stat are the [[detoxifier kidney]]{{BiotechIcon}} and [[tox resistance]] [[gene]].{{BiotechIcon}}
* [[Toxic Environment Resistance]] protects against all sources of buildup except for direct attacks like cobra bites. Some ways of increasing this stat are the [[face mask]], [[gas mask]],{{BiotechIcon}} and [[detoxifier lung]].{{BiotechIcon}}

Both stats reduce the amount of buildup received by the % of the stat, so 50% Toxic Resistance = 50% less build up. Toxic Resistance and Toxic Environment Resistance will multiplicatively stack with each other, so if a human has 50% in both stats, the effective rate of buildup from environmental sources is 25%.

The buildup severity occurs in stages. The later stages cause permanent [[#Dementia|dementia]] which does not wear off even after toxic buildup subsides. When a pawn affected by toxic buildup [[Death|dies]], there is a chance that its corpse will instantly rot - this chance is equal to the severity.

Once a colonist returns to a safe area, such as a roofed area for toxic fallout, or otherwise stops taking severity increases, their buildup severity will gradually decrease. Once no longer exposed, severity reduces by 8% per day, meaning that it will take up to 12.5 days to eliminate all toxins accumulated in the body. However, colonists that reach high stages of toxic buildup are likely to develop further complications.
{| class="wikitable"
|-
! Stage !! Begins at !! Symptoms
|-
| '''Toxic buildup (initial)''' || ≥4% severity ||
* -5% [[Consciousness]]
|-
| '''Toxic buildup (minor)''' || ≥20% severity ||
* -10% [[Consciousness]]
|-
| '''Toxic buildup (moderate)''' || ≥40% severity ||
* -15% [[Consciousness]]
* [[Vomiting]] (''MTB of 5 days'')
* [[Dementia]] ('''permanent''', ''MTB of 146 days to develop'')
* [[Carcinoma]] (''MTB of 438 days to develop'')
|-
| '''Toxic buildup (serious)''' || ≥60% severity ||
* -25% [[Consciousness]]
* [[Vomiting]] (''MTB of 1 day'')
* [[Dementia]] ('''permanent''', ''MTB of 37 days to develop'')
* [[Carcinoma]] (''MTB of 111 days to develop'')
|-
| '''Toxic buildup (extreme)''' || ≥80% severity ||
* Unconsciousness (Max. [[consciousness]] 10%)
* [[Vomiting]] (''MTB of 0.5 day'')
* [[Dementia]] ('''permanent''', ''MTB of 13 days to develop'')
* [[Carcinoma]] (''MTB of 39 days to develop'')
|-
| '''Toxic buildup (extreme)''' || 100% severity ||
* [[Death]]
|}

=== Brain shock ===
{{quote|"After-effects of an electrical shock to the brain. This is generally cause by feedback from brain implants hit by EMP pulses." - '''In-game description'''}}
Occurs when an [[EMP]] effect hits a pawn with the following brain implants:
* [[Learning assistant]] {{RoyaltyIcon}}
* [[Neurocalculator]] {{RoyaltyIcon}}
* [[Circadian assistant]] {{RoyaltyIcon}}
* [[Circadian half-cycler]] {{RoyaltyIcon}}
* [[Pilot assistant]] {{OdysseyIcon}}
It lasts between {{ticks|2500}} and {{ticks|3500}}.

Despite only occurring with implants from the [[Royalty DLC|Royalty]] and [[Odyssey DLC|Odyssey]] DLCs, it is defined in the core code.

{| class="wikitable"
|-
! Stage !! Symptoms
|-
| '''Brain shock''' ||
* Unconscious ([[Consciousness]] max. 10%)
|}

=== Psychic shock ===
{{quote|A state of psychic chaos in the brain and mind. Caused by psychic attacks or critical level of neural heat, this effect is debilitating until it wears off.|In-game description}}
Occurs when a pawn is hit by the effect of a [[psychic shock lance]] or when exceeding a pawn's [[neural heat limit]]s when psycasting {{RoyaltyIcon}}.

It lasts {{ticks|7500}}.

{| class="wikitable"
|-
! Stage !! Symptoms
|-
| '''Psychic shock''' ||
* Unconscious ([[Consciousness]] max. 10%)
|}

=== Psychic coma ===
{{quote|"A form of benign coma during which the brain recovers from a psychic overload."|In-game description}}
A coma inflicted by certain [[psycasts]]{{RoyaltyIcon}} including:
* [[Neural heat dump]], lasting 1 day.
* [[Neuroquake]], lasting 5 days.
* [[Word of serenity]], lasting 6 hours with duration scaling with [[psychic sensitivity]].
Note that despite only being caused by psycasts from the [[Royalty DLC]], the hediff itself is defined in Core.

It has the following effects:
* [[Consciousness]]: {{Bad|10%}} Max.

=== Psychic breakdown ===
{{Royalty|section=1}}
{{Stub|section=1|reason=Unknown whether should remain on [[Psycasts]], whether it should be moved here, or whether a transclusion or template should be used to duplicate it in both places}}
{{Main|Psychic breakdown}}

=== Biosculpting sickness ===
{{Ideology|section=1}}
{{quote|"The after-effects of an incomplete biosculpting cycle. It causes nausea, dizziness, and fuzzy thinking."|In-game description}}
Occurs when a pawn is ejected early from a [[biosculpter pod]] either manually or as a result of 24 hours without power.

It lasts between {{ticks|8000}} and {{ticks|12000}}

{| class="wikitable"
|-
! Stage !! Symptoms
|-
| '''Biosculpting sickness''' ||
* [[Consciousness]] ×80%
* [[Moving]] ×90%
* [[Manipulation]] ×90%
* [[Vomiting]] (Mtb 0.125 days)
|}

=== Scanning sickness ===
{{Biotech|section=1}}
{{:Subcore softscanner}}

=== Bio-starvation ===
{{Biotech|section=1}}
{{quote|"This person was in a growth vat which wasn't functioning properly due to lack of power or nutrition feedstock. This has left their body in a state of bio-starvation."|In-game description}}
A pawn in a [[growth vat]] with no power or nutrition, will enter [[bio-starvation]], increasing in severity by 50% per day starved, and decreasing 10% per day properly supplied or spent outside the vat. Bio-starvation increases nutrition consumption in a vat by {{bad|+10%}} at all severities, and [[Death|kills]] at 100%. If a bio-starved pawn leaves the vat, a number of status effects will be applied to them. These include:
* [[Pain]]: {{++|15%}}
* [[Hunger Rate Factor]] offset: {{++|50%}}
* [[Consciousness]]: {{--|25%}}

=== Vomiting ===
{{Stub|section=1|reason=what does it interrupt, what happens when different tasks are underway - e.g. eating cancels the eating task but doesn't waste the meal, explanation that vomiting is expressed as mtb etc}}
The body attempting to forcefully expunge toxins. Unfortunately for your pawns, this doesn't work in Rimworld.

Vomiting is caused by a wide variety of ailments{{Check Tag|List Needed?}}, some [[Psycasts]],{{RoyaltyIcon}} or being hit with an EMP while having the [[Sterilizing stomach|Sterilizing]], [[Reprocessor stomach|Reprocessor]], or [[Nuclear stomach|Nuclear]] stomachs{{RoyaltyIcon}} installed.

A pawn that is vomiting will stop in place, face the side, and begin vomiting. Vomiting lasts a random duration from {{Ticks|300}} to {{Ticks|900}}, and every 150 interval ticks it reduces the pawn's food bar by 0.04 and generates 1 stack of [[vomit]] filth on the tile they're facing. Note that this interval tick occurs independently from the beginning of the vomiting duration, and as such the number of times it occurs may not be the simple division of the chose duration divided by 150. As such, between one fewer and one more interval may occur than the the division would indicate. A pawn lying in a bed will not stand up to vomit{{Check Tag|Details|Does this pause the resting bonus from lying down? Does it wake them up?}}.

Vomiting will interrupt most tasks, including eating, walking, aiming a weapon, or working at a station, but they will resume the task once they stop vomiting{{Check Tag|Mechanics|Do pawns who are actively vomiting still reserve the task they were working on?}}. For this reason, it is recommended that pawns who are afflicted with an ailment that causes frequent vomiting, such as [[food poisoning]], eat foods like [[pemmican]], as a pawn who vomits while in the middle of eating a normal meal will lose all progress towards consuming it (note that the meal is not wasted), but a pawn eating pemmican will still consume part of the stack. Similarly, they should also avoid long tasks that have their progress reset on being interrupted, such as cooking 4x [[lavish meal]]s.

=== Crumbling mind ===
{{Anomaly|section = 1}}
{{Spoiler|section = 1}}

The gradual breakdown of the mind. While technically non-fatal, it applies mounting consciousness penalties, and its final stage renders a pawn incapable of nearly all work.

Crumbling mind is caused by two [[Anomaly]] events - The [[Corrupted obelisk]] and the [[Creepjoiner]]. It cannot affect pawns that existed before those events, only ones created by them. It can be detected before ailments show by a surgical inspection.

Creepjoiners with this condition will begin showing symptoms within 2-3.33 days. Duplicated pawns will begin showing them within 12-48 hours. Severity progresses by 33% per day. Progress can be paused through the use of a [[cryptosleep casket]].

Crumbling mind can be cured by a [[healer mech serum]] as well as the [[unnatural healing]] ability so long as it hasn't progressed to the final stage of '''Crumbled mind'''. Once it has, the condition is incurable, short of destroying the colonists brain then resurrecting them with either a [[resurrector mech serum]] or [[death refusal]]. However, consistently destroying the brain can be difficult. There are 5 main ways to achieve it:
* With the [[Biotech DLC]], using a [[Subcore ripscanner]] on the colonist in question will kill it by destroying its brain.
* Also with the Biotech DLC, extracting the pawn's genes with a [[Gene extractor]] while the '''Genes Regrowing''' Hefiff remains active will kill it by brain destruction.
* With the [[Ideology DLC]], extracting the [[skull]] from a dead pawn will destroy its head reliably and safely.
* Fatal [[Luciferium]] withdraw kills by destroying the brain.
* Allow colonists or animals to eat sections of the corpse, risking consuming the entire body before the head is removed.

Furthermore, no matter how successful the head removal, the costs and downsides of the either the serum or refusal remain. If this strategy is used, remember not to euthanize them or they will be no longer of your faction after resurrection.

Counterintuitively, [[Ghoul|ghoul infusion]] will not cure crumbling mind and it will hinder ghoul's combat abilities.

{| class="wikitable"
|-
! Stage !! Begins at !! Symptoms
|-
| '''Crumbling mind (mild)''' || Initial ||
* {{Bad|x90%}} [[Consciousness]]
|-
| '''Crumbling mind (moderate)''' || ≥40% severity ||
* {{Bad|x75%}} [[Consciousness]]
|-
| '''Crumbling mind (extreme)''' || ≥80% severity ||
* {{Bad|x60%}} [[Consciousness]]
|-
| '''Crumbled mind''' || 100% severity ||
* {{Bad|x60%}} [[Consciousness]]
* Incapable of [[Work#Incapable of work types|skilled and dumb labor, caring, and intellectual]]
* Incurable
|}

=== Duplicate sickness ===
{{Anomaly|section = 1}}
{{Spoiler|section = 1}}
Psychic interference between this person and their duplicate is causing slow mental deterioration. As long as multiple copies of this person are alive, the condition will keep getting worse. However, the condition will not be lethal.

Duplicate sickness is one of the potential outcomes from the duplication of a pawn by a [[corrupted obelisk]]. It affects both the original pawn and the duplicate{{Check Tag|Wb other duplicates?|Test both a previous duplicate (i.e. use obelisk gizmo, wait cooldown use again) and mass cloning (i.e. when 30 pawns spawn when it reaches max activity}} and is initially hidden. Severity increases by 10% per day that both pawns are alive. A pawn in [[cryptosleep]] will not gain severity, but being in cryptosleep will ''not'' prevent the other copy of the pawn from gaining severity. This gradually reduces the consciousness of both pawns and makes them more likely to have [[mental breaks]], before eventually rendering both comatose.

It cannot be treated,{{Check Tag|Verify}} but can be cured by one of three methods: [[healer mech serum]], the [[unnatural healing]] ability, or the death of one of the two pawns.

If one of the two connected pawns is killed, the other's duplication sickness severity immediately starts regressing at the rate of 50% per day, while the killed pawn's duplication sickness is instantly cured. The killed pawn can then be immediately resurrected with a [[resurrector mech serum]] or [[death refusal]] without stopping the regression of the other pawn's sickness. Similarly, if one of the linked pawns is turned into a [[ghoul]], killed, and revived with a [[ghoul resurrection serum]], the same mechanics apply.

{| class="wikitable"
|-
! Stage !! Begins at !! Symptoms
|-
| '''Duplicate sickness (initial)''' || Initial ||
* No symptoms, condition not visible.
|-
| '''Duplicate sickness (initial)''' || ≥20% severity ||
* [[Consciousness]] Offset: {{--|5%}}
* [[Mental Break Threshold]] Offset: {{++|4%}}
|-
| '''Duplicate sickness (moderate)''' || ≥50% severity ||
* [[Consciousness]] Offset: {{--|10%}}
* [[Mental Break Threshold]] Offset: {{++|8%}}
|-
| '''Duplicate sickness (extreme)''' || ≥80% severity ||
* [[Consciousness]] Offset: {{--|15%}}
* [[Mental Break Threshold]] Offset: {{++|14%}}
|-
| '''Duplicate sickness (debilitating)''' || ≥95% severity ||
* [[Consciousness]] Max: {{Bad|10%}}
|}

== Surgical ==
These ailments happen with medical operations.

=== Anesthetic ===
Used in surgery to make sure that a pawn is unconscious. It can also be administered outside of operations using a medical bill, consuming medicine.

A pawn under anesthesia is unconscious for the first 6 hours, and the worst effects of anesthetic wear off after 12 hours, so arranging operations to be performed some time just before a pawn needs to sleep is recommended if you want them functioning the next work day.

{| class="wikitable"
|-
! Stage !! Begins at !! Symptoms
|-
| '''Anesthetic (sedated)''' || 0–6 hours from onset ||
* Unconscious ([[Consciousness]] max. 1%)
|-
| '''Anesthetic (woozy)''' || 6–12 hours from onset ||
* Reduced [[pain]] (×80%)
* Impaired [[consciousness]] (70% max)
* Impaired [[moving]] (-20%)
* Impaired [[manipulation]] (-20%)
* Impaired [[digestion]] (-20%
* Impaired [[sight]] (-15%)
* [[Vomiting]] (''MTB of 0.25 days'')
* Confused wandering (''MTB of 5 days'')
* Forget memory thought (''MTB of 5 days'')
* Improved [[mood]] (+10)
|-
| '''Anesthetic (wearing off)''' || 12+ hours from onset ||
* Reduced [[pain]] (×95%)
* Impaired [[consciousness]] (90% max)
* Impaired [[moving]] (-5%)
* Impaired [[manipulation]] (-10%)
* [[Vomiting]] (''MTB of 4 days'')
* Confused wandering (''MTB of 50 days'')
|}

Treatment:
* Wears off on its own between {{ticks|45000}} to {{ticks|75000}} even if severity has not reached 0%
** Surgery is unaffected even if it wears off before finished

==== Version history ====
Prior to 1.1 it lasted only {{ticks|15000}} and did not have any other stages afterwards.

== Resurrection ==
These may occur after a dose of [[resurrector mech serum]] is applied on a [[Death|dead]] pawn.

=== Resurrection sickness ===
After-effects of being resurrected by mechanite injection. Artificially-kickstarted body processes take time to rebalance themselves.

{| class="wikitable"
|-
! Ailment !! Symptoms
|-
| '''Resurrection sickness''' ||
* Loss of [[moving]] (×10%)
* Loss of [[manipulation]] (×10%)
* [[Vomiting]] (mtb. 0.5 days)
|}

'''Treatment:'''
* Wears off anywhere from {{ticks|90000}} to {{ticks|150000}}

'''Probability:'''
* 100% chance of being applied

=== Blindness ===
Mechanites fail to properly repair the eyes, instead causing more damage to it, resulting in blindness.

Blindness from [[resurrector mech serum]] applies to both eyes, resulting in total blindness

{| class="wikitable"
|-
! Ailment !! Symptoms
|-
| '''Blindness''' ||
* Complete loss of function (-100% part efficiency)
|}

'''Treatment:'''
* Replace eyes with [[bionic eye]]s or [[archotech eye]]s

'''Probability:'''
* 2% chance when used at 0.1 days or less of decay
* Linearly increases to 80% after 5 days decayed

=== Resurrection psychosis ===
Chaotic thought patterns caused by the decoherence of resurrection mechanites. Resurrection psychosis progresses and eventually causes total psychosis and [[death]].

The severity of the psychosis increases by 0.01 per day, meaning that it will kill in 100 days after resurrection, or 90 days after this ailment becoming visible. It can be cured by [[healer mech serum]] or [[unnatural healing]],{{AnomalyIcon}} alternatively resurrection can be attempted again via another [[resurrector mech serum]] or [[death refusal]].{{AnomalyIcon}} It is otherwise uncurable. A [[cryosleep casket]] can sustain the pawn in order to wait for a cure.

{| class="wikitable"
|-
! Stage !! Begins at !! Symptoms
|-
| '''Resurrection psychosis (hidden)''' || ≥0% severity ||
* No visible symptoms, doesn't show up in health tab
* Can still be cured with [[healer mech serum]] at this stage even if it is not visible.
|-
| '''Resurrection psychosis (early)''' || ≥10% severity ||
* Frequent mental breaks (''MTB of 9 days'')
|-
| '''Resurrection psychosis (moderate)''' || ≥25% severity ||
* [[Consciousness]] -10%
* Frequent mental breaks (''MTB of 6 days'')
|-
| '''Resurrection psychosis (advanced)''' || ≥40% severity ||
* [[Consciousness]] -20%
* Frequent mental breaks (''MTB of 3 days'')
|-
| '''Resurrection psychosis (severe)''' || ≥55% severity ||
* [[Consciousness]] -30%
* Extremely frequent mental breaks (''MTB of 0.5 days'')
|-
| '''Resurrection psychosis (total)''' || ≥70% severity ||
* [[Consciousness]] -40%
* Extremely frequent mental breaks (''MTB of 0.25 days'')
|-
| '''Resurrection psychosis (catatonic)''' || ≥85% severity ||
* Pawn becomes unconscious ([[Consciousness]] max. 10%)
|-
| '''Resurrection psychosis (catatonic)''' || 100% severity ||
* [[Death]]
|}

'''Treatments:'''
* Healer mech serum
* Allowing the pawn to [[Death|die]] again, then resurrecting once more (rerolls the disease)

'''Probability of contracting:'''
* 2% chance when used at 0.1 days or less of decay
* Linearly increases to 80% after 5 days decayed

'''Prevention:'''
* Freeze corpses immediately after death. Corpses placed in a [[sarcophagus]] are still affected by the temperature of the room they are in, and can be removed later but are protected from butchering, hungry animals and assuming you build the sarcophagus from something [[Flammability|non-flammable]], [[fire]].

== Heart attack ==
Heart attacks can randomly occur on any pawn/animal at any time, but they become more frequent as they pass half of their life expectancy (e.g. 40 years in humans), triggered by the [[Events#Birthday|birthday event]]. There must be 2 or more colonists on your colony for this to occur.

The average interval between heart attacks is curved as follows (in days):
* 0-60% of life expectancy: 99,999,999 - 99,999,999
* 60-80% of life expectancy: 99,999,999 - 2,500
* 80-100% of life expectancy: 2,500 - 300

Examples of intervals and chances:
* 70% of life expectancy (i.e. 56 in humans): 50,001,249.5 days (approx. 0.00000002% per day)
* 90% of life expectancy (i.e. 72 in humans): 1,400 days (approx. 0.000714% per day)

=== Stages ===
{| class="wikitable"
|-
! Stage !! Begins at !! Symptoms
|-
|'''Painful''' || 0% Severity ||
* [[Consciousness]] ×50%
* [[Pain]] +40%
|-
|'''Debilitating''' || 60% Severity ||
* [[Consciousness]] max. 10% (Unconsciousness)
* [[Pain]] +60%
|-
|'''Fatal''' || 100% Severity ||
* [[Death]]
|}

==== Progression ====
Heart attacks always start at 40% severity. Each interval the heart attack severity will randomly change by a value between {{---|40%}} to {{++|60%}}. This means that it is possible for a heart attack to recover on its own, but usually (~76% likelihood){{Check Tag|Detail needed|How is this calculated??}} an untreated heart attack progresses to fatal severity. The interval between changes is random, and varies between {{Ticks|500}} and {{Ticks|10000}}.

==== Treatment ====
Like injuries, medicine can be used to treat a heart attack.

Doctors treating heart attacks will administer treatments rapidly, consuming medicine in the process. Each treatment has a chance to succeed, reducing the heart attack severity by {{---|30%}}. Successfully reducing severity below 0% will completely treat the heart attack.

The chance a particular treatment can succeed is 65% multiplied by the [[tend quality]], for an effective maximum of 84.5% with [[glitterworld medicine]].

==== Prevention ====
Replacing a pawn's heart with either a [[prosthetic heart|prosthetic]] or [[bionic heart]] will completely prevent heart attacks. Note however that while the bionic heart improves the [[blood pumping]] capacity, the prosthetic heart decreases it, and thus all of the stats and capacities it affects.

== Version history ==
* [[Version/0.7.581|0.7.581]] Added with cataracts and bad back
* [[Version/0.8.657|0.8.657]] - Added hypothermia, frostbite, heatstroke, and burns from being in areas with extreme temperatures.
* [[Version/0.9.722|0.9.722]] - Food poisoning and cryptosleep sickness added. Some ailments can now cause vomiting.
* [[Version/0.10.785|0.10.785]] - Starvation and blood loss are now staged and affect consciousness as they worsen.
* [[Version/0.12.906|0.12.906]] - All organisms including animals have life expectancies and will develop chronic conditions like frailty or cataracts in old age. Heart attacks added.
* [[Version/0.13.1135|0.13.1135]] - Carcinoma, asthma, and hearing loss added.
* [[Version/1.0.0|1.0.0]] - Minor starvation (below 25% severity) no longer causes miscarriages.
* [[Version/1.1.0|1.1.0]] - Pregnant animal is no longer viewed as sick because pregnancy affects its capacities. and thus now sells for the same as one with no health conditions.
* [[Version/1.3.3117|1.3.3117]] - Extreme blood loss now reduces consciousness by 40% in addition to setting the capacity's max to 10%. Prior to this, pawns could nonsensically [[Death|die]] by healing from extreme to severe bloodloss if their consciousness was below 40% from other symptoms - extreme would simply max it at 10% but healing to severe would reduce it by 40% to 0% and kill the pawn.
* [[Version/1.4.3523|1.4.3523]] - Sterilized animals no longer lay eggs.
* [[Version/1.6.4518|1.6.4518]] - Vacuum exposure implemented with [[Odyssey]].

[[Category:Health]]

Void monolith

2026-04-25T00:47:25Z

Aelanna: /* Summary */

{{Anomaly}}
{{Spoiler}}
{{Infobox main|entity
| name = Void monolith
| image = Void monolith.png
| description = A monolith of unknown age, purpose, and construction. Its smooth surface is etched with lines that twist and writhe in unsettling patterns.

| type = Entity
| type2 = Basic
| flammability = 0
| path cost = 50
| selectable = true
| destroyable = false
| uses hit points = false

| meditation psyfocus bonus = 0.3
| focus types = Void

| anomaly knowledge = 1
| knowledge category = Basic 
| study interval = 120000 
| min monolith level for study = 1
| show toggle gizmo = true
| study enabled by default = false

| passibility = impassable
| cover = 1
| blockswind = true
| terrain affordance = Heavy
| size = 3 x 3
| deconstructable = false
| repairable = false
| is targetable = false
| is inert = true
| claimable = false
| expand home area = false

| glowradius = 12
| glowcolor = (255,120,120,0)

| defName = VoidMonolith
| label = void monolith
}}
The '''void monolith''' is a structure that is the center point of the [[Anomaly DLC]]. It is used to enable in encounters with most [[entities]].

== Acquisition ==

The monolith appears on all new colony maps by default. If you have selected the "Ambient Horror" mode of the [[storyteller]] settings, the monolith '''will not be available'''.

If you choose the [[Scenario_system#The_Anomaly|Anomaly starting scenario]], the monolith will spawn right next to your crash landing spot, instead of its usual and distanced spot, allowing you to form a base around it easier.

If the monolith is enabled in storyteller settings, but there are no monolith on your maps for any reason (like move to a new map or add the DLC in the middle of another playthrough), you will receive a "Strange Signal" quest, which will spawn a monolith on your map when you accept it. The monolith's spawn point is random, and it may destroy existing structures when it arrives.
{{clear}}
== Summary ==
{{Stub|section=1|reason=Void focus mediation}}
[[File:Void Monolith Awakened Valid Meditation Spots.png|thumb|right|128px|Valid meditation spot positions for the Awakened monolith]]

The monolith is the first [[entity]] that the player will encounter. Initially dormant, the monolith goes through these stages of development:

{| class="wikitable"
|-
! Anomaly stage
! Monolith
! Size
! Level
! Effect
! Advancement
|-
| Inactive
| Fallen monolith<br>[[File:Void monolith.png|64px]]
| 3×3
|
| Encounter minimum amount of Anomaly incidents, includes shambler assault, psychic ritual siege, and creepjoiner arrival
| Investigate the monolith with a colonist, and choose to "Keep focusing" when you receive the warning dialog
|-
| Stirring
| Void monolith<br>[[File:Void monolith level 1.png|64px]]
| 5×3
| Level 1: Intermittent psychic humming
| Encounter a mix of basic and easier advanced [[entities]]. You will immediately experience a [[Events#Gray_pall|gray pall]] event, followed shortly by a [[sightstealer]] attack and a [[harbinger tree]] sprout
| Encounter '''7 [[Entities#Basic|basic entities]]''' (out of 8), and have a colonist attune to the monolith again when you are ready
|-
| Waking
| Void monolith<br>[[File:Void monolith level 2.png|64px]]
| 5×5{{ref label|Footprint|A}}
| Level 2: Pulsing with psychic energy
| All entity encounters possible, including the more-dangerous advanced entities
| Encounter '''12 [[Entities#Advanced|advanced entities]]''' (out of 17), and have a colonist attune to the monolith again when you are ready
|-
| VoidAwakened
| Void monolith<br>[[File:Void monolith level 3.png|64px]]
| 5×5{{ref label|Footprint|A}}
| Level 3: Awakening
| The monolith is awakening for the [[Endings#The Void|end of the quest]]
| Active a total of 5 [[void structure]]s and wait until the monolith awakens
|-
| Gleaming
| Void monolith<br>[[File:Void monolith level 4.png|64px]]
| 5×5{{ref label|Footprint|A}}
| Level 4: Awakened
| The monolith is awakened and opens a portal to the metal hell, leading to the end of the quest
| Enter the [[metal hell]] and interact the [[void node]], reaching the chosen [[ending]]
|-
| Embraced
| Void monolith<br>[[File:Void monolith level 3.png|64px]]
| 5×5{{ref label|Footprint|A}}
| Level 4: Awakened
| The monolith is awakened as the pawn has embraced the void, dangerous Anomaly events will continue to occur
| —
|-
| Disrupted
| Collapsed monolith<br>[[File:Void monolith collapsed.png|64px]]
| 3×3
|
| Random Anomaly events return to the same level as an inactive (level 0) monolith
| —
|}

:{{note|Footprint|A}} The 5×5 monolith is not regular in shape, the five tiles that appear empty are indeed empty and can be walked on and built on as normal.

These stages are saved in the world; losing the monolith and getting the "Strange Signal" quest spawns a monolith of the same level.

The monolith must be attuned or investigated after each step to advance, allowing you to decide when to progress. If you chose the [[Scenario_system#The_Anomaly|Anomaly starting scenario]], the monolith will ''automatically'' move to Level 1 on its own a few days after you begin the game.

The monolith can be [[work|studied]] every two days as a source of either basic or advanced Anomaly tech tree research points.

The monolith separates rooms and provides total cover (like a wall), and it is invulnerable to all damage and fire. [[Raiders]] will ignore the monolith. When the monolith expands in size, it will uninstall, deconstruct or destroy any structures in the way. However, any connected power sources will continue to generate power until the power network is updated again. (This is almost certainly a bug.)

Depending on which path you select during the [[Monolith endgame|Anomaly ending quest]], the monolith will either be permanently closed or permanently locked at level 4. In either case, it can still be studied indefinitely for advanced research points.

== Analysis ==
{{For|dealing with the monlith awakening at level 3|monolith endgame}}

The monolith is your only permanent source of Anomaly research points. However once the monolith study has been completed, you can research captured entities instead to avoid having to travel to the monolith. Studying the monolith or entities is done through the "Dark Study" job on the [[work|Work tab]].

You may want to build your base near the monolith to reduce the travelling time to it.

=== Meditation ===
The void monolith is the best Void [[meditation focus]],{{RoyaltyIcon}} although it cannot be moved and only has three tiles to place [[meditation spot]]s in.

===Theoretical infinite energy generation===
By placing power generators near the left or right side of the monolith, and power conduits adjacent to the left or rightmost side of the power generator. And activatting the monolith, one can achieve infinite power, in addition to that. The full cost of the generator in resources will also be returned. The power still remains in the network and can be used by various appliances, however the phantom power generators will disappear as soon as the power network is updated in any way, either by adding or removing buildings including conduits. This is almost certainly a bug.

== Version history ==
* [[Anomaly DLC]] Release - Added.
* 1.5.4081 — Ambient Horror mode, and monoliths spawned via the dev commands now work correctly

{{Nav|entity|wide}}
[[Category:Entities]]

Defense structures

2026-04-25T00:31:32Z

Aelanna: /* Cover */

{{Rewrite|reason=Everything past early-game should to be updated to 1.6, e.g., barricades no longer prevent enemies from using cover}}
{{Image wanted|reason=Most images are from Beta 18, where deadfall/spike traps could be placed adjacent to each other.}}
{{TOCright}}

{{for|strategies against threats|Defense tactics}}

Raids are frequent and numerous as enemies don't journey towards your base from their bases; they are instead generated into your colony by the [[storyteller]]. Players will need to fight the enemy AI for each type of hostile, but the approach may differ according to gameplay preferences, either face to face for a more combative experience or behind killboxes for a less threatening measure, or both combined.

== Map features ==
Before laying blueprints, first inspect the [[map]] for natural features that can work as defenses, such as [[water]] or a [[mountain]].

=== Water ===
Water and marsh tiles can be used as moats, which will considerably slow down incoming [[Raiders]], giving you some time to shoot and soften the clash before engaging in melee [[combat]]. You can build [[cover]], like [[barricade]]s just in front of the body of water.

If large bodies of water are available, such as rivers or [[lake]]s,{{OdysseyIcon}} then [[bridge]]s can be used to manipulate raider AI by encouraging them to path through the faster bridge.

[[File:Moats.png|500px|thumb|center|Marsh used as moats to slow enemy advance, with little islands full of spike traps.]]

=== Mountains ===
In mountainous and hilly maps, it is possible to build defenses by enclosing the area between two hills. In an actual mountain map, it is often best to mine into the mountain and live inside, but this may be too time-consuming in the early game.

=== Map borders ===
Pay attention when expanding towards the edges of the [[map]], as there's a boundary which your [[colonists]] can not build beyond that is only visible when the [[Structure]] tab is selected.

== Early-game defense ==
At the very beginning, your [[security]] choices include [[spike trap]]s, [[cover]] (including [[barricade]]s, [[sandbag]]s, and [[stone chunk]]s),

=== Stone chunks ===
At the very beginning of the game, colonists will often haul [[stone chunk]]s away to build structures or to clear up a [[growing zone]]. As colonists move stone chunks around, you might as well create a [[dumping stockpile zone]] for chunks on the outside of your base, covering its width and expanding it further. This is time-consuming, so only a small, 1-wide line of chunks is enough for the early game.

[[File:Stone chunks at the outer side to prevent fire spree in tropical forest.png|500px|thumb|center|Stone chunks at the outer side to slow wildfires in tropical forest.]]

=== Walls ===
[[Wall]]s alone can fend off early game raids if a colonist's [[Construction]] skill is high enough to repair the wall faster than the raider can break it. A walled room will also completely defend against [[manhunter]] and carnivore attacks, who will not attack if every colonist remains indoors.

Otherwise, walls are nearly essential for luring raiders into the area you want to fight them in. Standard raiders will always try to take the quickest, unobstructed path towards a colonist if such a path exists. This means that ''standard raiders will not try and break walls unless they are unable to reach a target''. This is the key towards most defensive structures, and can be used to construct trap hallways, chokepoints for melee fighters, strategic cover placements, and so on.

'''Material:''' [[Wood]] is cheap and quick to build, but weak and flammable. [[Stone]] is ideal, being cheap, durable, and nonflammable, but time-consuming. [[Steel]] walls are flammable in RimWorld. [[Plasteel]] and [[uranium]] are the strongest walls but are expensive, and should generally be reserved in specific spots.

=== Cover ===
[[Cover]] is vital for firefights as it can block projectiles, reducing the amount of [[damage]] received by your colonists. This is an essential defense as long as colonists or turrets are directly engaging.
* [[Wall]]s provide 75% cover, but pawns need to "lean out" whenever firing, causing the wall to not provide its full cover. In addition, walls block line of fire.
* [[Barricade]]s and [[sandbag]]s provide 55% cover and do not block line of fire.
* [[Stone chunk]]s only provide 50% cover, which is great in the early game, but should be replaced by 55% cover when possible.

The best arrangement of cover is a mix of walls and barricades/sandbags, as a pawn can benefit from barricades whenever they lean out from a wall. The exact ratio will depend on what angles the colonist needs to fire at, as wall tiles will limit how far a colonist can turn. Creating a U shape of cover, or a square around the colonists will ensure that they can engage enemies from multiple angles.
<gallery widths="400px" heights="400px" class="center" mode="nolines">
File:Cover_fire_wall.png|Example of advanced cover, mixing walls and barricades.
File:Sandbag_advanced_cover.png|400px|thumb|right|Example of advanced cover using sandbags only.<br>Allows full range of fire, but less cover overall.
</gallery>

=== Spike traps ===
{{See also|Spike trap}}

The only initially available defense that deals damage. Spike traps are single use and require careful placement. It is best to place spike traps where raiders will naturally walk through, or can be lured into, such as:
* Corners of your base, where enemies will likely make turns.
* Narrow areas even outside your base that receive frequent traffic.
* Chokepoints. If there is only one entrance to a room or the entire colony, raiders will have no option but to walk through it.

If it doesn't seem obvious to you at first, one way to find out is by carefully studying raids pathing from the map borders as they close in towards your base. Watch where they go through and starting laying blueprints but forbidding them (as you are currently being attacked).

When building spike traps, you must also leave free areas so that your colonists and friendlies can pass harmlessly, or they may accidentally step on a spike trap while exiting or trying to rearm them. As such, putting them in a 1-wide corridor is not a good idea.

<gallery widths="400px" heights="400px" class="center" mode="nolines">
File:Trap_choke_14.jpg|'''Trap and fence tunnel'''
File:Defense structures deadfall trap.png|'''Traps in potential enemy cover spots (map border)'''
</gallery>

Instead, a good way to use traps is as shown above: build a 2-wide corridor as the only entrance to the base, with a spike trap, then a [[fence]] next to it. Raiders cannot open the colony's doors and do not see traps, meaning they will walk over the "faster" lane with the traps on it. Colonists will walk through the fences or use the doors.

'''Materials:''' [[Wood]] spike traps are practical for most biomes in the early game. It is flammable, so it is ideal but not close to required to place them in stony or floored areas, or [[roof]] over the area so grass won't grow. [[Stone]] traps are more damaging and nonflammable but take a long time to build. [[Steel]] is faster than stone and more damaging still in case traps are urgently needed or steel is abundant.

=== Bait furniture ===
Attackers will destroy [[furniture]] if there is no unobstructed path to a colonist, and will sometimes even stop to destroy furniture if it is between them and the nearest colonist. They may smash items or set flammable things on fire (particularly crop fields).

Cheap wooden furniture such as a [[stool]] or [[table]] can be used as bait to lure enemies into a position where they can be more easily killed. It can also distract them by drawing a few attackers away from your base, which can help prevent your defenders from getting overwhelmed.

<gallery widths="400px" heights="400px" class="center" mode="nolines">
File:Distraction_tables_2.jpg|'''A raider lured into a dangerous position in the middle of a moat.'''
File:Distraction_tables_3.jpg|'''A mechanoid detoured far away from the base to smash a wooden stool.'''
</gallery>

As a small added bonus, if your outdoor bait furniture consists of a table and stool, colonists completing work tasks far from your base may stop to eat there. This may help avoid the "Ate without table" negative [[thought]].

{{clear}}

== Mid-game defense ==

=== Perimeter wall===
An additional perimeter wall surrounding all the structures and growing areas of your colony is a great defense once the colony has the time to build it. It protects from fire and either concentrate raiders into a specific area (if an entrance is open), or delay raiders and cause them to split up (if no entrance is open).

Keeping an entrance open allows the wall to act as a chokepoint - raiders will funnel through that entrance, allowing strategic placement of cover, traps, turrets, and so on. Alternatively, keeping the entrances closed will cause each raider to choose random tiles to attack, causing them to be split up and delayed. If the entrance is closed, colonists can take pot shots by entering through one doorway, firing at the split up enemies, then retreating and attacking at another direction.

Having [[door]]s placed every 15-25 tiles or so will allow colonists to fire potshots and to venture outside if needed, e.g., to haul items or to deal with [[breacher]] raids. This can be expanded (both in height/width and number of layers) whenever needed. An "airlock" with two+ doors, separated by at least 1 tile, will keep raiders and manhunters out.

==== Multi-layer walls ====
Multiple layers of wall will make it more resistant to attacks, especially against standard, non-breacher/sapper, raiders.

When making a multi-layer wall, it is often best to ''not'' have a gap in-between layers, due to how the raider AI works. If standard AI enemies have no path to a colonist and decides not to attack furniture, they will choose a ''random'' section of accessible wall and attack it, recalculating after destruction. If the walls have a gap in-between, after the first layer is broken, it is much more likely for an enemy to randomly pick the inner wall to target next, as the entirety of the inner wall is accessible. With no gap, the enemy will be unable to access most of the inner layer, meaning they will be much more likely to destroy another outer layer wall.

Having a gap between each layer of walls will make it possible to repair the outermost layer without going outside, and will make the wall somewhat better against explosions, so if not planning to completely close off the wall for combat tactics, having a gap may be better.

=== Chokepoints ===
A chokepoint is an opening in a wall or room that raiders will have to funnel through, due to there only being one open entrance. Building a colony-wide perimeter wall with one open entrance will form an effective chokepoint. From there, it is possible to concentrate firepower there, having colonists, turrets, and traps all in one place. Once the colony has enough firepower or resources, a [[killbox]] can be built at the end of the chokepoint.

* When building a hallway, turns can be used break line of sight. This will prevent long-range raiders from making potshots, although the turn itself can be used as [[cover]]. As of 1.6, placing [[barricade]]s at the turn will not prevent enemies from using walls as cover.
** Turns are a great way to support melee fighters. When building hallways - both in a chokepoint and internally within your base - you may want to build turns so that melee fighters can approach without being shot it.

So long as raiders have a clear path to a colonist, no matter how long or winding it is, they will pass through a chokepoint if it is the only path. This can be used to slow raiders down, giving the colony more time to react.

==== Slowing tunnel ====
[[File:Slowing_tunnel.png|300px|thumb|right|Short slowing tunnel in front of a wall, with alternated sandbags for maximum slowing efficiency and a twist to break line of sight.]]

A simple and cheap tactic to slow down enemies through a chokepoint is by placing [[fence]]s, [[sandbag]]s, [[barricade]]s, or debris in a narrow hallway, alternating them with empty space. Fences/sandbags/etc. should not be placed adjacent to each other, as otherwise they will simply vault over multiple bags at once, reducing their slowing efficiency.

=== Cover removal ===
While proper cover formations (see the [[#Cover|Cover section]] above) already give colonists an advantage over raiders in terms of cover, removing all sources of cover near your base is still very useful when dealing with ranged enemies as they will then have nowhere to hide. If the base is surrounded by an all-encompassing wall, only areas near the combat zone need to be cleared.

*Haul all stone chunks towards a dump behind your defensive lines so enemies can't use them. A [[sniper rifle]] has a [[range]] of 45 tiles, though most raiders can't shoot that far, so removing chunks around 30 tiles away from your defenses can deprive many enemies of suitable cover.
*Remove the flora near combat zones, either by cutting or burning it. To prevent it from regrowing, it is possible to place [[roof]]s (supported by a single [[column]] or [[wall]]), which will also slow down raiders due to the lack of [[light]], and the roof's support can be destroyed to cause roof collapses.
*Watch out for your crop fields, as colonists tend to move and lay out chunks in straight lines when planting on [[Growing zone]] tiles, suitable for raiders to take cover behind.

<gallery widths="400px" heights="400px" class="center" mode="nolines">
Cover removal or baiting.png|Watch where enemies choose to hide and once the battle is over plan for the future.
Wildfire clearing.png|Intentional burning of a tropical rainforest to reduce any cover that raiders might use.
</gallery>
{{clear}}

==== Cover baiting ====
[[File:Flanking_example.png|400px|thumb|right|Early-game example of cover baiting. Notice the stone chunks laid strategically so that shooters can lean out of doors to flank enemies hiding behind them. Enemies that reposition themselves to defend against one angle will be exposed to another, leaving nowhere safe to hide.]]

Once there's no suitable cover nearby, ranged attackers will scramble to find any objects usable as cover. You can exploit this by placing any form of low cover to attract them to a place where they can be dealt with more easily. [[Stool]]s work well, though they wear out quite fast under constant fire.

If the cover is hard to remove (such as plants and trees constantly regrowing in plant-rich biomes), you can manipulate stone chunks in ways that give them a disadvantage. For example, putting gaps between each chunk exposes the enemy behind to fire directed diagonally, or continuous lines allow missed shots to hit nearby covering enemies. If your defense line is big enough, you can bait enemies into taking cover in such a way that leaves them flanked (see picture).

You can put traps behind the bait cover, which makes it slightly easier to trigger, though still less effective than chokepoints (see above).
{{clear}}

=== Pillboxes / Bunkers ===
[[File:Makeshift_pillbox.png|320px|thumb|right|Map ruins converted into a pillbox.]]

A simple early game construct, effective until mid-game. Simply build a room in any shape (or convert them from ruins) and then deconstruct a few sections of wall facing the enemy to make some holes and replace with sandbags -- these will be firing holes for your shooters, where they can use the walls and sandbags for covers.

Bunkers should be built out of stone, as they are durable and are non-flammable. Roof over the enclosure to protect defenders from the rain, and floor can help improve beauty while protecting from fires.

'''Pros:''' Cheap and simple, can be placed throughout multiple locations, can be upgraded.

'''Cons:''' Generally not used with chokepoints (as regular cover is suitable for them), meaning risk of getting encircled or run down by melee attackers. If not placed well, the bunker’s utility will be greatly decreased, and not all map types suit bunkers. Enemies can use bunkers.

Pillboxes can be incorporated into perimeter walls, but make sure that there is no direct entry from there, such as by building a durable door.

=== Secondary cover ===
Besides your main line of cover, you may also build additional cover for various purposes:
#For [[Defense tactics#shield distraction|shield distraction]], building cover for your shield tanks helps them to last longer with their shields.
#Putting lines of sandbags perpendicular to your main cover line allows them to be used to flank enemies. Make sure that they are put a great distance away so enemies can't use it to their advantage.

=== Burning floors ===
You can build flammable floors to set on fire, burning enemies. Once the floors are burnt, they leave behind burnt floors that apply a {{Bad|{{%|{{Q|Burned floor|Move Speed Factor}}}}}} movement factor, and will persist until removed.

=== Roof trap ===
This clever trap is simple to set up and hard-hitting when triggered. It can be considered a giant single-use spike trap.

All you need to do is to erect 1 [[wall]] or [[column]] made of a low-HP material, optimally wood, then build a roof over it. When raiders walk near the wall, destroy it from a distance with long-range guns or by igniting an [[IED trap]]. After the wall is destroyed, the roof will fall, crushing the raiders on the head, neck or torso and dealing up to 20 damage (though armor will negate part of it). It is possible to damaging the wall before combat to make it easier to destroy, while removing the [[home area]] so colonists won't automatically repair it.

This is more of a clever use of game mechanics than an actual trap, so raiders won't detect it, nor will they treat it as one.

'''Pros:''' Large radius, cheap, penetrates shields, no risk of friendly activation. Slows down raiders.

'''Cons:''' Hard to trigger, requires space, low damage.

As a bonus, roofs can be used as firebreaks as they will prevent the growth of grass.

<gallery widths="300px" heights="300px" class="center" mode="nolines">
File:Roof_trap.png|Roof trap before triggering.
File:Roof_trap_triggered.png|Roof trap after triggering, having injured some raiders (some through shields) and left a large pile of rubble.
File:Roof_trap_auto.png|More refined roof trap design with stools to lure the enemy into using them as cover, along with an IED trap to automatically trigger the trap. Significantly more expensive.
</gallery>

=== Damage minimization ===
These are ways to minimize damage done to your base.

[[File:Walled_geothermal_generator.png|200px|thumb|right|Walled geothermal generator. The extra space allows heat to escape without being trapped inside. Note that the entire setup is unroofed.]]

==== Firebreaks ====

2-tile wide strips of concrete, metal or stone tiles are capable of stopping the spread of fires. This can prevent many fires from reaching your base and burning it down. This is more important for plant-rich biomes with large amounts of flammable material.

You can build one surrounding your base, and divide the map into sections in order to control fires. You can also use them to separate crop fields such that a fire won't consume all your crops.

Keep in mind that building such amounts of floors usually requires huge amounts of building materials - if you have stone on hand it is better to build a perimeter wall out of stone instead, with the added advantage of fortifying defenses.

==== Grazing animals ====

Setting lots of grazing animals around the outside of the base helps clear away grass, slowing or stopping the spread of fires towards your base. They may also distract raiders during raids, but at quite a cost.

==== Walling structures ====

You should build an additional wall around your important structures, such as generators, power conduits or cash crops, even if you do have a perimeter wall in place. This causes raiders to prioritize other targets over these, averting destruction.

For geothermal generators, remember to have some exposed roof areas so the heat from the generator can vent out instead of being trapped inside.

==== Power network ====
[[Hidden conduit]]s are totally immune to damage and cannot cause a [[short circuit]], meaning the entire power grid can be secured by building using hidden conduits alone. Even one regular [[power conduit]] can cause short circuits, draining [[batteries]] and potentially disconnecting the base's power grid.

=== Panic room ===
[[File:Panic_room_example.png|400px|thumb|right|Example of a panic room built inside a mountain.]]

You can dig out a panic room deep into the mountains or build one out of very thick walls. This provides a good escape if you know that you can't defeat an incoming group of raiders, or you are losing and need retreat, provided you manage to get to the room in time.<br>
*If you dig one out of the mountains, you gain immunity against mortar shells and some innate temperature control. You will need to make many layers of doors (at least 6) as the raiders will focus down the doors.
*If you build one using thick walls you have more flexibility in its positioning, and you don't need that many layers of wall - 4 layers are OK, since raiders will divert their attention to the walls as well instead of focusing down the doors.

You don't need to make the panic room big enough to accommodate the whole colony, as the point of a panic room is to preserve colonists in a dire situation so you can rebuild later on. Choose the colonists most important to you when it's time to escape to these rooms.

Panic rooms also need the following:
*Enough food to last 1-2 days at full capacity
*Medicine for the wounded, for injury is likely during the retreat
*Joy objects (otherwise colonists may face a huge -20 mood penalty)

If you want, you can put beds and tables to make sure your colonists don't feel too bad while cooped up inside. You can also choose to put building materials to seal up the entrance with cheaper and more durable walls. Putting resources inside also helps with rebuilding, though they take up space.

While inside the room, if you're down on your last door or layer of wall, assign your best builder to hold the door by repairing it, and make sure the others don't go out. Disabling firefighting for covering colonists or restricting them to the panic room can help stop them from leaving. If the doors are unable to hold, use the breach as a chokepoint instead, and take as many enemies down with you.

Consider building multiple panic rooms so your colonists have another panic room within reach if a raid blocks off access to one. You can also choose to build another exit so you can flee to another room should the original be overrun.

{{clear}}

== Mid-late game defense ==

=== Turrets ===
Turrets are automated defenses which shoot at enemies in range but require materials to reload. There are three main varieties: the [[mini-turret]], [[autocannon turret]], and [[uranium slug turret]]. There are also two unconventional turrets, including [[rocketswarm launcher]]s and [[foam turret]]s.

Turrets should not be relied solely upon for defense. A perimeter wall of turrets will not remain viable for too long, as the turrets will quickly get overwhelmed while not all the turrets are actively helping combat. While turrets are more effective in [[killbox]]es, certain raid strategies like [[drop pod]], [[breacher]], and [[sapper]] will ignore the killbox, so preparing defenses and gearing colonists is important. In addition, a [[solar flare]] will shut down all turrets.

While protecting the outside starting area, you may want to rapidly pause the game during raids and give orders to repair damaged turrets.

Remember that turrets may explode when critically damaged, so get your colonists to run from them.

[[File:Turret_range_comparison.png|1200px|thumb|left|Visualization of effective turret range of all three turrets, from uranium slug turret (top), to autocannon turret (middle), to mini-turret (bottom). <br>
Green is '''80 - 100% of peak accuracy''', blue is '''50 - 80% of peak accuracy''', red is '''below 50% of peak accuracy''' and grey is '''outside range'''. Gold tiles are spaced every 5 tiles.]]

{{clear}}

==== [[Mini-turret]] ====
Mini-turrets fire light bullets at enemies within its range.

With its low firepower it is not a good idea to extensively rely on them, especially in mid-late game. However they do provide decent additional fire to lay on the enemy when combined with gunners, and also serve as a distraction from your more valuable colonists.

'''Pros'''
*Can be uninstalled and re-deployed wherever needed, making their placement slightly less of an issue
*No exclusion zone allows them to fire at touch range
*1x1 size makes it harder to hit and more compact

'''Cons'''
*Inaccurate at long-range

Building turrets out of [[plasteel]] brings their health to 335 (up from 120), making them substantially more durable and slightly less flammable.

==== [[Autocannon turret]] ====
Autocannons deal moderate damage and are long-ranged, but have an exclusion zone making them less effective against close enemies in the frontline.

They are somewhat costly to build and maintain. Despite its long maximum range, it is mainly effective at short-medium ranges due to its accuracy.

'''Pros'''
*Shots deal decent damage
*Somewhat high fire rate
'''Cons'''
*Inaccurate at long-range
*Somewhat high cost per shot

==== [[Uranium slug turret]] ====
A long-range turret that fires a high powered uranium slug.

It is more accurate than the other turrets at long distances and has much longer range, but is more expensive to maintain and performs poorly at close range.

'''Pros'''
*High damage shots
*Extremely high armor penetration, able to negate most all armor on an enemy
*Accurate at long ranges
'''Cons'''
*High cost per shot
*Not good at close ranges

==== [[Rocketswarm launcher]] ====
Rocketswarm launchers must be manually controlled, and fire one barrage of rockets before needing to be reloaded.

'''Pros'''
* Wide AOE.
* Cheaper than autocannons, and reloads using [[chemfuel]] instead of metal.

'''Cons'''
* Requires a colonist to aim it.
* Rockets will destroy structures, meaning the base needs to be designed with rockets in mind.
* Not very effective unless enemies are clumped up. Having enemies clumped up is bad for other types of defenses.

==== Weaknesses ====
Turrets are most vulnerable to the following things:

*Explosives deal immense damage to turrets. All forms of regular explosives wielded by raiders are capable of 1-hitting a steel mini-turret and leaving a plasteel one at less than half health.
*EMP stuns the turrets. Enemy EMP is very uncommon, but friendly fire can disable turrets.
*[[Smokepop pack]]s prevent turrets from locking onto targets within or behind smoke. An enemy equipped with it can create a safe zone from turret harm.
**This is a great issue in killboxes, where turret firepower is often concentrated, as an enemy that activates the belt will essentially be able to nullify a large portion of your defensive firepower.

Turrets can be ignited, and are unable to put themselves out. Given enough time, flames can debilitate the turret.

For the mini-turret, long-ranged gunners can shoot from outside their range without retaliation from the turret. This includes [[lancer]]s with their [[Charge lance]], making them less than ideal for fighting off [[Mechanoid]] incursions.

==== Turret placement ====
* Placing turrets in a [[#Chokepoint|chokepoint]] and/or [[killbox]] is effective, allowing all the turrets to be concentrated into one area instead of having them be spread out. Placing more than 1 line will allow the colonists to fall back in case raiders advance too far.
* Turrets can benefit from [[cover]], so placing [[barricade]]s or [[sandbag]]s in front of the turret will improve its performance.
* Since melee enemies will try to attack turrets, placing traps in front of them is a great way to protect the turret further.
* Turrets will explode, so place turrets at least 3 tiles apart from each other to avoid a chain reaction.

==== On-demand turret deployment ====

For mini-turrets, instead of placing static turrets around the perimeter, you can instead keep them uninstalled and placed in the center of your base. Once raiders come, have a builder install them facing the battlefield, behind your cover. This helps to save power and also allows you to utilize turrets more efficiently as you can keep more turrets engaged on the enemy rather than just sitting there due to lack of contact with the enemy.

This tactic is less effective against melee charges who will swarm your defenders before you have enough time to react.

==== Turret power switch ====
Turrets should be turned off whenever not in use. Turrets can be turned on/off quickly by installing a [[power switch]] that connects all your turrets to the main power grid.

Alternatively, it is possible to build a single unconnected [[hidden conduit]] near the turrets. By using the reconnect gizmo, the turrets will switch from the unconnected "grid" to the main grid, taking no time in the process.

=== Mortars===
A [[mortar]] attack can be effective at forcing [[siege]]s to start attacking directly, culling raiders as they prepare, and dealing with [[crashed ship part]]s and [[mech cluster]]s{{RoyaltyIcon}}. However, mortars are fairly inaccurate, so multiple mortars are often needed to be effective, and their long travel time means hitting moving raiders is difficult. Skilled colonists are more accurate with mortars, but unskilled colonists can still provide supportive fire and they can be effective with large-radius shells like [[EMP shell]]s and [[smoke shell]]s.

Always remember to manually unassign colonists from mortars, or they'll continue standing there until they eventually collapse from exhaustion, starvation, or have a mental break.

An important point to remember is that while your colonists are better at dealing with single or spread-out enemies, mortars are designed for heavily grouped enemies. If you diffuse your enemies, the mortars will not be able to hit the enemies easily.

Don't aim mortars anywhere too close to your colonists otherwise you risk friendly fire.

==== Mortar pits ====
[[File:Mortar_Pit.png|320px|thumb|right|8-mortar battery. Note the separation between the mortars, and walls to block explosions.]]

Mortars cannot be fired through a roof, but they can still be placed indoors for security and colonist happiness. Note that mortars will explode if damaged enough, which, while rare, can happen due to enemy mortar shells. Separating each mortar, as well as the mortar shells, with high HP walls will prevent a chain reaction from destroying the entire mortar pit. Building mortars with [[plasteel]], [[uranium]], or [[bioferrite]]{{AnomalyIcon}} will give mortars high enough HP to survive multiple explosions.

Mortars can't fire at anything within 30 tiles of it, so you will need to place the mortars deep inside your base for maximum coverage.

Keep in mind that your landing mortar shells will blow up anything nearby, including pawns and things of yours that raiders don't commonly target

==== Quantity ====
The number of mortars needed depends on how they will be used:
* For provoking [[siege]]s, one mortar firing [[incendiary shell]]s is often enough so long as fire is allowed to spread. It is also possible to get away with using one mortar firing [[high-explosive shell]]s with a great shooter.
* For stunning mechanoids with [[EMP shell]]s, multiple mortars are needed, especially against [[mech cluster]]s{{RoyaltyIcon}} with [[mech high-shield]]s (which require 1 EMP + multiple regular mortars at minimum).
* For damaging general raids with high-explosive shells, even more mortars are required.

==== Shells ====
There are different shells available to be loaded into the mortar.

*[[High-explosive shell]]s are the go-to ammo for dealing damage to enemies and buildings.
*[[Incendiary shell]]s deal weak damage against pawns, but they can cause an enemy siege's own mortar shells to explode, causing the siege to start attacking directly.
*[[EMP shell]]s stun mechs and break shields, making them useful but highly situational. They have a large blast radius, meaning that their inaccuracy is less of a problem compared to the others. Their ability to break [[mech high-shield]]s {{RoyaltyIcon}} is particularly useful.
*[[Smoke shell]]s will block turrets from locking on and reduce enemy fire, but a [[smoke launcher]] or [[smokepop pack]] are typically better for this role.
*[[Firefoam shell]]s can be used to extinguish fires outside your base, but is useless against any inside, due to the mortar's blind spot.
*[[Deadlife shell]]s{{AnomalyIcon}} revive nearby corpses as [[shambler]]s. More useful as an [[IED deadlife trap|IED trap]] than as a shell, as it is unlikely that corpses will pile up in the area raiders arrive in.

=== Traps ===
As you unlock research, and obtain more manpower and resources, you can lay more traps to debilitate incoming raiders.

==== Understanding AI ====
Raiders cannot use the colony's doors, cannot see traps, and will traverse through the quickest unobstructed path to a colonist. Colonists can step on traps if walking over their tile, but can see traps and will take slower routes or doors to avoid them.

Building [[door]]s and [[fence]]s to give colonists a quicker path, as with a [[#Spike traps|spike trap tunnel]], will allow colonists to travel while funneling enemies into a single chokepoint.

==== [[IED trap]]s ====
Early on, you may want to focus on armed colonist defense with turrets, but as the raiders grow in number, it becomes more efficient to use a bit of metal to kill several at once than to invest a lot of metal in a turret that costs nothing to fire, but will explode rapidly due to large raider groups.

IED traps are extremely effective when used correctly, however in open areas they are mostly useless as the raiders are highly unlikely to step on any of the traps, and even if they do they're usually not tightly packed enough for the trap to cause serious damage. Thus, it is better if you combine traps with funneling to force the raiders together.

1 IED trap can trigger other IED traps in its explosion radius. This may or may not be desirable depending on the situation; you can easily set off a chain reaction to destroy a whole incoming raider horde, but also use up much more resources. They also damage nearby structures, such as walls or spike traps, so don't put too many close to each other.
* Rather than setting more IED traps near existing ones, you can just place the [[Mortar shell]]s themselves, or even some [[Chemfuel]] on the ground for the same effect as a molotov cocktail blast. However, unless you can restrict them to placing just 1 of each it's more expensive to do so.
** Chemfuel has 50 HP, ''just'' within the damage threshold of an IED trap, but the shells have 70, so you will need to pre-damage them or leave them on the ground to deteriorate first if you want to use this tactic.

IED traps have a delay before exploding, allowing some raiders to escape. Raiders will attempt to run from an exploding trap, though the fuse is short enough to catch some of them.

'''Pros'''
*High area damage
*Raiders usually less protected against explosives

'''Cons'''
*High resource cost
*Single-use, non-rearmable
*Requires research
*Does not instantly trigger

==== [[IED incendiary trap]]s ====

A variant of the IED trap that sets enemies on fire. It's a more situational pick compared to the regular trap, due to its incendiary nature.

'''Pros'''
*Distracts enemies while they are on fire
*Penetrates shields

'''Cons'''
*Low damage
*Not effective against [[Mechanoid]]s

Its use requires strong support to be effective. With that, it is a good defensive choice against heavily armored or shielded enemies, with the flames providing good distraction while your colonists shoot them down.

It synergizes great with brawlers, which will prevent the enemy from attempting to extinguish the flames while fighting.

==== [[IED EMP trap]]s ====

A variant of the IED trap that creates an EMP pulse. It's a more situational pick compared to the regular trap, due to its EMP explosion.

'''Pros'''
*Instantly downs shields
*Stuns mechanoids for a long time
*Large blast radius

'''Cons'''
*'''No physical damage'''

Its use requires strong support to be effective as it can't deal any damage. It is excellent against mechanoids or shielded enemies, however.

==== Mountain trap ====
An extreme version of the roof trap using overhead mountains instead of constructed roofs.

To use it, you mine out a whole mountain except a pillar in the center. Then you damage that pillar until it has just a sliver of health left (25 or less for easy activation with a single [[sniper rifle]] shot). Mining out all the rocks at once will result in your colonists getting crushed by the trap.

It is triggered the same way as the regular roof trap, and has the same effect radius except victims are instantly killed and buried.
The collapsed rocks spawned after this trap is triggered can be useful or harmful depending on the situation.

Rearming it is a lengthy process as you will have to mine out lots of rocks. This does provide a decent way to train miners though.

Pros
*'''Instantly kills any enemy'''
*Leaves no corpses

Cons
*Takes much longer and is more dangerous to re-arm
**You have to mine out everything then support the mountain roof with a low-HP wall; compare with regular roof trap which simply requires building the wall and the roofs
**Colonists risk death if you aren't careful
*No loot or capturable downed raiders
*Overhead mountains may not be easily available

In mountainous areas where overhead mountains are abundant, this trap can absolutely destroy any incoming raids, especially when combined with funneling.

=== Reactive firefoam poppers ===

You should have some uninstalled firefoam poppers on hand. When a fire starts and you need to extinguish or control it, you can reinstall them near the fire, and trigger them.

Firefoam on the ground slows movement speed of pawns by about 25%. As it covers a wide area, this can be slightly useful as area denial to slow down charging melee attackers, though it prevents the use of fire against them.

=== Firefoam roof array ===

Due to the slight slowing effect of firefoam, you can deploy a large amount of it to slow down enemies crossing by. However, since rain washes it away, you need to erect a roof to prevent that from happening. You also need to clear home area so colonists leave the firefoam alone.

This has the added effect of creating an excellent firebreak against wildfires, as well as creating a [[#Roof trap|roof trap]] that can damage enemies.

Initial deployment of the firefoam is very expensive without the use of chokepoints so it isn't recommended for open base designs.

== Killboxes ==
[[File:Killzone.png|500px|thumb|right|An example of a killbox. [[Fence]]s spaced 1-tile apart slow enemies down. Barricades near the entrance prevent enemies from standing on the corner. Traps and fences allow colonists to pass unimpeded, but enemies will walk through the traps. Doors can be closed in case of [[manhunter]]s.]]

Killboxes are heavily trapped, armed areas where enemies are funneled into so they can be destroyed easily.

They almost always consist of a funnel which directs raiders into it, like a wall with a single opening, which opens into a zone where your colonists and turrets are located.<br>
Raiders will then trickle in, allowing colonists or turrets to concentrate fire on them, or traps to destroy them while they try to move in to attack. In the killzone, enemies lack cover and are within close range, while your colonists have plenty of cover to fight from.

This is an extremely effective way to defeat most raids, as the enemies will often be overwhelmed by the sheer firepower raining on them. It also allows effective use of traps, as funneling enemies greatly increases the chance one's going to trigger them. A well-built killbox can easily neutralize the threat of many raids, which may make the game less fun for some players.

Note that killboxes aren't a catch-all solution to enemy threats, and you still need tactics to handle drop pod raiders or sappers.

=== Building ===
The entryways should lead to a large 'box' where the killing begins (hence 'killbox'). The box should be surrounded by cover sources (preferably walls plus sandbags) where your colonists fire on the enemy. For increased firepower you may build turrets as well, away from your colonists' firing line and separated from each other by walls, in case they explode.

It's always best to double-wall the "receiving" end of your killboxes as the sheer firepower raining on your enemies will inevitably destroy some of your own walls by accident, allowing raiders to flood in from another direction, bypassing traps and overwhelming your defenders. This is especially true if you use explosives such as frag grenades or IED traps to kill incoming enemies.

{{clear}}

=== Entryways ===

Any entryways of the killbox should not be straight, otherwise raiders will simply fire using the entryway as cover. Instead, you should have a turn to break line of sight, prompting the raiders to enter an area where you can get them easily. For better effect, put a grave or other similar object that raiders can't stand on. The entryway should be single wide to allow the use of [[Defense tactics#Melee blocking|melee blocking]] if necessary.

The below shows the results of different killbox entryways.
<gallery widths="300px" heights="300px" class="center" mode="nolines">
File:Killbox_right.png|Right design of a killbox entryway. Raiders are prompted to move into the killbox, sometimes so close that they prefer to melee attack instead of shoot.
File:Killbox_wrong.png|Wrong design of a killbox entryway. Raiders are bunching up in the entryway, using its walls as cover.
</gallery>

Entryways should be long, but not too long, corridors with [[sandbag]]s or [[barricade]]s every second tile to slow enemies. Do not place a continuous line of sandbags or barricades, as pawns only slow down when they are climbing on and off the two (similar to real life, as you can just run on the barricade after you climb on it). In between the spaces, spike traps can be placed to soften up the raiders (with doors adjacent to the sandbags so your colonists can replace them). At the end of the corridor, place a T-Shaped sandbag line (do not alternate with empty tiles like before), as pawns cannot stand on the sandbags and therefore are incapable of using the corridor exit walls as cover. [[IED trap]]s can be used, but should be used sparingly lest they blow up all the walls of the corridor.

Don't make your entryway excessively long, otherwise raiders will think it's not worth it going such a distance and will decide to go for something else instead. Manhunters however will still chase colonists down a long corridor or over extreme distances, so you can have some dedicated anti-manhunter killboxes with extra-long corridors for this purpose.

If your entryway is long then you may need to build doors to allow friendlies to enter without setting off your own traps or having to go through all the obstacles. This door obviously needs to be fortified against enemy attacks.

<gallery widths="300px" heights="300px" class="center" mode="nolines">
File:Slowing_tunnel_long.png|Entryway with alternating sandbags to slow raiders and doors to provide access. Slows raiders but not colonists.

</gallery>

{{clear}}

=== Equipment ===
Different equipment is necessary in different situations.

==== Short-range killboxes ====
Colonists defending in a short-range killbox will be shooting at a large number of targets no more than a few tiles away. Thus, defenders should use close ranged high damage weaponry for firing at raiders.

* [[Chain shotgun]]s inflict extreme pain at killbox range, surpassing the DPS of every other weapon at short range or less.
* [[Minigun]]s are excellent at attacking the bunched-up raiders inside a killbox, but require large amounts of resources to craft ({{Required Resources|Minigun}}).
* [[Charge rifle]]s and [[heavy SMG]]s are second-tier picks, being able to dish out hurt against closely grouped targets at close-mid ranges.
* Long range weapons are not optimal due to low DPS. Instead, use them to pick off survivors outside the killbox.
* Grenades are good if you can time them right. Throw them near the entrance where each explosion can hit a tight group of raiders, especially if they're slowed down with obstacles, but take care not to demolish your own walls.
*Have melee colonists stand nearby as raiders who enter your killbox may decide to melee charge you instead.

==== Long-range killboxes ====
Colonists defending in long-range killboxes will be shooting at bunched up raiders. Thus, defenders should use mid-range, fast firing, and decently accurate weapons to inflict as much damage as possible. Note: It is possible to modify a killbox in a pattern that leverages both long and short range weapons. This can be accomplished by creating a passage that has a 45 degree angle "open to the field" while keeping the main 90 degree passage open to short range fire only.

* [[Charge rifle]]s are the best weapon{{Check Tag|Arguable}} for this purpose, shooting 3 semi-accurate high damage charge shots. It also has a decent 26 tile range and an excellent 35 percent armor penetration, essential for killing targets late game, when your killbox is more developed.
* [[Heavy SMG]]s are excellent alternatives to charge rifles. Significantly cheaper but similarly skill friendly and with a solid DPS.
* [[Assault rifle]]s are basically charge rifles with lower damage and armor penetration, but making it up for its longer range and higher accuracy. Higher skilled pawns are required to make use of their range however.
* [[Minigun]]s, [[Chain shotgun]]s, and perhaps [[LMG]]s are second options, excelling at crowd control, especially against tribals.
* Explosive weapons are not advised, as raiders will be moving around the killbox frequently, and grenades have a delay between the grenade hitting the ground and the explosion of the grenade.

=== Turrets ===
You can put turrets in a killbox. They help to provide additional firepower alongside your colonists.

You may also choose to fully arm your killbox with turrets, with enough to single-handedly take out raids especially in tandem with traps. Doing this allows you to defeat raids automatically without the need to divert colonists from other jobs, but eats up power when active and resources to maintain, and is vulnerable to solar flares, EMP grenadiers or smoke, so you will need backup.

Turrets should preferably have their own cover. They should also be connected to a separate grid which can be shut off to deactivate them all, to save power when not active.

Mini-turrets and autocannons are the best choices for killboxes, being able to dish out hurt at killbox ranges. Place mini-turrets close up to the enemy, while place autocannons slightly farther away to keep enemies out of its minimum range.

Alternatively, if you can keep the enemy in one spot, a specially designed killbox can allow uranium slug turrets to function well. Uranium slug turrets are most accurate at 40 tiles or above, achieving a maximum of ~61% accuracy against human enemies, so you will need to place them that far from the entrance, and distract enemies so they do not go closer. Slug turrets are good against tankier pawns, as a uranium slug can easily rip through [[Centipede]] and [[Power armor]].

It is better to 'Hold fire' until the enemies have actually entered the killbox, for all the turrets will focus fire on the first enemy to try and go through the entrance, which is very much overkill.

=== Blocking ===
As [[Defense tactics#Melee blocking|melee blocking]] is more effective than even a killbox used normally against melee only attacks, it's best to have somewhere that you can do this.

Melee blocking can be done at killbox entrances, as long as it is one-tile wide and has sufficient empty space in front. Both the entrance to the killing area and the entrance to the covered area where colonists fire onto enemies will work:
*Doing it in the killing area allows you to spare the turrets from immediate destruction, and they may add firepower.
*Doing it in the covered area entrance allows you to sustain fewer injuries by having the turrets take the damage first.

=== Explosive weapons ===

Enemies carrying explosive weapons can be very damaging towards your killbox and the defenders inside.

[[Centipede]]s with [[inferno cannon]]s can counter killboxes as the fire makes your colonists lose control and run out of cover, and the flames can destroy turrets easily. Having some [[firefoam popper]]s inside your box helps a lot with extinguishing fires and preventing future fires.

Another counter for killboxes are raiders with the [[triple rocket launcher]] and [[doomsday rocket launcher]]. If they manage to shoot inside your box the damage can be massive, and it is hard to distract them in a killbox. You can concentrate fire from your colonists on them, or keep [[psychic shock lance]]s and [[psychic insanity lance]]s near and use them if you see that they will not die fast enough.

=== Fire killbox ===

Besides killing enemies with conventional weapons, roasting them with fire is also an effective choice. You need to lure them inside, light up flammable objects to heat up the killbox, and evacuate colonists so they don't get roasted as well.

Fire killboxes are slightly more complicated to operate than a regular one, where you can simply wait inside and fire; you will need to direct colonists, while others light up fires and then make a break for it. <br>
You can shut off the killbox by either leaving doors open to let enemies in, which you then shut off by disabling "keep open", then directing a colonist through them, or by building walls.

They need to be at least walled to prevent enemies from breaking out, and also to insulate it from the outside so that temperatures rise faster. Stone walls are optimal as they are non-flammable.

== Killhall ==
{{rewrite|section=1|reason=Largely similar to killboxes, should be merged with that section}}
Another possibility is to build a long corridor with traps, that can also be used shoot enemies from cover: a "killhall".

It acts as an active and passive defense:
* If used actively, it allows to kill enemies will little to no harm done to colonists, and with little damage to repair after the attack.
* If used passively, it'll lure enemies into [[spike trap]]s. Only very large or tough groups of enemies may go through (by springing all the traps), or possibly enemies with the "[[nimble]]" trait (that will avoid all of them).

If the first part has many obstacles (e.g. [[stone chunk]]s, [[barricade]]s or [[sandbags]]), and another branch of the corridor is empty and ended with a flimsy door (e.g. a wooden [[door]], or better: an [[animal flap]]), fleeing enemies will try to escape by this seemingly faster exit, but they will fall into another group of spike traps, eliminating the rest of the raid.

A drawback is that last part of the corridor has to be quite long to work properly, i.e. a bit more than the [[Property:Range|range]] of the weapons used (e.g. 30 tiles for [[assault rifle]]s and [[charge lance]]s, 45 for [[sniper rifle]]s).
This is not an issue if it is placed under a mountain, the best location being at the corner of the map.

=== Attack of a killhall ===
An attack will proceed as follows:
# Enemies will be lured into the hall, thinking it is an unobstructed way into the base.
# They are slowed by obstacles, leaving time for colonists to take position inside doors, hidden behind wall corners, waiting for them.
# Enemies are shot one by one by colonists, they are slowed by stone chunks and cannot rush in for a melee attack before they get shot. Enemies who shoot behind their friends others can sometimes hit them by mistake.
# Once half of them are dead, they decide to flee, but instead of going back by the way they used to enter, that looks cluttered by chunks, they try to break the doors on the side of the corridor.
# They are still shot at by colonists, but once they broke a door, it seems that there is only a flimsy animal flap between them and liberty.
# Unfortunately, what seems to be an exit path is littered with spike traps and they get killed one by one by them.
# If some of them still manage not to get killed by the traps, they get shot like clay pigeons in the exit corridor.
# It is now time for the colonists to strip the dead enemies of their possessions and store their corpses for later use...

If colonists decide not to attack the invaders, half of them will be killed by the traps on the entrance way, the other half on the exit way.
If the attackers are manhunting animals or [[mechanoid]]s, they will not try to escape and will all be shot or being trapped.

=== Example of a practical implementation ===

[[File:Killhall.png|500px|center]]

# Entrance and "escape exit".
#* The entrance has a door "held open" and "forbidden", so enemies can enter, but not friendlies.
#* The "escape exit" has an [[animal flap]] (can be substituted by a wooden [[door]]), leading fleeing enemies to think that they can break it to escape quicker.
# "Slowing down" corridor, filled with [[stone chunk]]s spaced one tile apart that will slow down enemies, give time to prepare and make this path look like a slower way to escape.
# "Shooting range" corridor, where enemies will be shot at from distance and will be forced to advance one behind another. It is also filled with stone chunks to slow them while they're being shot at (as chunks may be moved or destroyed during the attack, 1×1 [[stockpile zone]]s allowing only stone chunks should be placed, enabling their quick rearrangement).
#* Above, the "escape exit" corridor, filled with spike traps (doors allow replacing traps without having to walk on them).
#* Below, the "entrance to the base", also filled with traps.
# Part of the hall where colonists will shoot, taking cover with the wall corners. If the enemy has weapons with more range than colonists, they can hide behind the doors and pop out when the enemy is close enough.
# "Entrance to the base" (or at the part that enemies are planning to reach), with wall corners at the end to use as shooting positions (in case some enemies reach this part).
# Human corpses walk-in fridge, to put the bodies after the battle and keep them away from the view of colonists, avoiding the "[[Mood#Observed corpse|observed corpse]]" debuff.
#* It should be quite large, as enemy raids grow in size, and butchering humans should not be done every day, to avoid a permanent [[Mood#I butchered humanlike|I]]\[[Mood#We butchered humanlike|we butchered humanlike]] debuff (see the possible [[Human resources#Mitigation strategies|mitigation strategies]]). It can also hold the [[human leather]] stock, as it takes much space once butchering is done.
#* This can also be a place where corpses are burned, if it is preferred to butchering.
# Human [[kibble]] factory, where [[human meat]] can be processed into kibble (that extends hugely its conservation time, can be sold, or fed to any animal).
# Repair stock, that holds the necessary materials to quickly repair the walls and the spike traps after an attack.
# Hospital for prisoners, to quickly save them if they survive.

Points 6 to 9 are optional, but are great improvements if used.

==== Additional notes ====
* Walls of the parts 3 and 4 should be tough and fireproof. Best would be [[plasteel]], then [[uranium]]; [[granite blocks]] may also be used but will break down faster, and flammable materials are to avoid at all costs.
* Flooring should be put in place to keep the mood of the colonists high when they are in the area.
* Walls and flooring of the parts 2 and 5 doesn't matter, as colonists will very rarely go there, and there shouldn't be much fighting in these parts anyway.
* Spike traps should be made out of [[steel]], as it has the best price-quality ratio for this device (nevertheless, steel is flammable in RimWorld, but here, traps are protected behind the walls and doors).
* Accurate weapons should be preferred for colonists: the narrow corridor will be damaged unnecessarily if explosives are used, or weapons like [[shotgun]]s or [[minigun]]s (not to speak of their reduced range).
* The hall should like an unobstructed path to enter the colony (i.e. no closed door between the outside and the inside of it), but the doors leading to it that will be used by colonists should be strong enough to deter attackers from trying to break them.
* The number of stone chunks in the way is also important: if there are not enough of them, fleeing enemies will just escape by the way they attacked and will not be led into the spike traps on the supposedly quicker escape route.

== Situational ==

=== Crashed ships ===

It is vital to know Mechanoids' behavior:

* Any attack to the ship will trigger its guardians, and they have a long aggro range of around 40 tiles from their spawn point. The larger the map, the easier it can be to deal with them, as long as the ship crashes away from your base. This means that as long as they are far from your base, Mechanoids will still NOT chase you yet.
* When the ship's health falls below 50%, Mechanoids will stop guarding and will instead proceed to attack your base as a normal raid.

You can trigger a ship's guardians from a long distance either by bombarding with mortars or hit-and-run with sniper rifles.

Currently, the best approach is to deal with the Scythers first, followed by their ranged units. There are a variety of alternatives, but the nature remains the same; hinder the melee range closing-in of their shock troops.

==== Preparation ====

Though these ships are "time bombs", instead of immediate action, you can spend a few days building preparations before engaging them.
* Placing a spike trap right in front of your sandbag may be helpful if the need to retreat arises, as mechanoids will very likely want to use the shortcut.
* Always make sure you have a safe path between your walls and your base, so that there's safe cover between your "ins" and "outs"; battles can take a long time if short on numbers.

Building IED traps can also be a good way to hurt the mechanoids, especially if there is a long distance between your colonists and the ship part. High-explosive traps deal hefty damage to incoming scythers and lancers, while EMP traps stun them, making them vulnerable to attack. <br>
If possible, a properly placed antigrain IED trap can obliterate most of the mechanoids, leaving a few heavily damaged centipedes to fight at most.

You may also want to keep a few firefoam poppers nearby. Trigger some of them before combat to prevent fires, and leave a few more to rapidly extinguish a group of burning colonists at once.

After you have finished preparing, you can use EMP shells to stun the mechanoids. Proper firing will make them helpless hunks of metal, once you get used to this technique, you can even preemptively fire EMP shells and then trigger the guardians, so as soon as they pop out, they instantly get hit by EMP shells. The number of manned mortars will factor in, as the chance to miss for each shell is quite large.

==== Cover ====

Use the "fire wall" cover approach detailed above, with melee units stationed behind each sandbag to hold off the scythers while your gunners lay fire on other mechanoids.

Ideally, the cover should be placed a distance from the ship, giving you time to soften incoming scythers with concentrated fire.

<gallery widths="400px" heights="400px" class="center" mode="nolines">
File:CSP v1 new tactics 101-00.png|Zoom out
File:CSP v1 new tactics 101-01.png|Zoom in
</gallery>

However, if you already have all the necessary utilities against mechs: EMP grenades and a good killbox, you may just wall the ship part off, (be aware that mechs will wake up if you build things up close to 2 cells to a sleeping mech, it's 5x5 square radius around any mechanoid) add one-two doors, you may want to add 2 walls deep mini corridor, so random fire from mechs won't hit the door, and a single barricade next to the door, draft your pawns to the entrance, force one to open it, while the door is opened (it must be made of wood) the other pawns will shoot the ship, mechs shouldn't have enough time to aim, the door will close pretty quick (do NOT hold it open), use "Heavy smgs" or other high dps and fast shooting guns, you can also equip frag grenades, a single colonist with grenades is enough, one is throwing it at the ship, while the other one keeps opening the door. As soon as you destroyed the ship just run, the mechs will be smashing the walls and head for your killbox.

=== 'The Purifier' ===

This is a powerful way to burn a massive [[infestation]] to a crisp. Provided that the infestation have no direct access to map edges and unroofed areas.

To start, build a medium-sized room (approx. 5x5) with triple-thick stone walls, next to the infestation. Fill it with [[Straw matting]]s, and flammable objects such as wooden [[barricade]]s, it has good hp which means it will burn for longer and has high flammability, so it will catch fire quickly. Another alternative is to use combustible junk, like tainted clothing or unneeded corpses.

After that, dig a 1-wide tunnel towards the infestation at night when the insects are sleeping. Finally, toss a Molotov into the room.

Once the temperatures reach ({{Temperature|250}}), insects will begin to burn. They will attempt to dig out by rushing towards the purifier, but be set alight by the burning [[Straw matting]], making them unable to dig. Temperatures can rapidly reach {{Temperature|500}} or above, boiling both the insects and the hives. Even those that don't get set alight will eventually succumb to heatstroke.

Although using this method will not yield you valuable [[insect jelly]].
{{Nav|guides|wide}}
{{nav|security|wide}}
[[Category:Guides]]

Defense tactics

2026-04-25T00:27:30Z

Aelanna: While these numbers look incorrect, friendly fire grace range is still most definitely a mechanic in the vanilla game. Could we perhaps update it to be more correct instead of deleting this section entirely?

{{rewrite|reason=This guide is outdated on some sections, lacking new content on others, focuses too much on specific scenarios without really giving general advice. It's also too long. It should be helpful, easy to understand and navigate for newer players. See Discussion for a detailed commentary}}
{{Image wanted|reason=New images are needed for mechanoids added in Biotech}}
{{TOCright}}

{{for|defensive constructions against threats|Defense structures}}

Getting attacked, whether by tribals, pirates, hordes of angry animals or by something more alien is a common event in the rimworlds. Defense against these attacks is one of the keys to having a successful colony.

This page details different tactics for defense and visualizations of them, applicable to most stages of the game.

= Core battle tactics =

No matter what sort of defenses you use, these battle tactics may be useful.

== Melee ==
Melee in RimWorld serves two main functions:
* Enemies that are engaged in melee combat will not fire their ranged weapons or move, allowing melee to take out ranged threats (who are usually feeble melee combatants) or fend off enemy melee fighters.
* Enemies cannot move beyond a [[draft]]ed colonist, allowing melee pawns in a chokepoint to block the advance of enemies.

In addition to colonists, [[animal]]s, [[friendly mechanoids]],{{BiotechIcon}} and especially [[ghoul]]s{{AnomalyIcon}} can make great melee fighters.

=== Melee blocking ===
Melee blocking is when melee fighters are placed in front of a chokepoint, preventing melee enemies from attacking. Instead of engaging melee enemies on the frontline, 'retreat behind your walls, and open doors to use as chokepoints''. Leave up to three melee brawlers standing right behind (not in) the chokepoint, as the pictures below, so that the enemy must stand on the doorway and be forced in a 1v3 situation.

<gallery widths="400px" heights="400px" class="center" mode="nolines">
File:Melee_test_eleplants_normal.png|10 manhunter elephants vs 3 armored brawlers and 4 armored gunners; all colonists are downed while all elephants remain standing.
File:Melee_test_eleplants_block.png|Same situation but with melee blocking; only 1 colonist downed, and all elephants defeated.
Bodyblock_choke.png|thumb|right|You shall not pass.
</gallery>

Overall, this is a horrifically effective way of dealing with most melee threats. Ranged fighters in the back can provide supporting fire, and replacement melee pawns can be rotated in once the frontline is damaged.

[[Animal]]s (except [[pen animal]]s) can be used to melee block by creating an [[allowed area]] that is only one tile large immediately in front of the chokepoint/door, and do not need to be trained in Attack to do so. This often results in substantial injury or death to animals, of course, so ensure the animals used are expendable (ie. not bonded or otherwise critical to the colony), and don't use explosive animals like [[Boomalope]]s or [[Boomrat]]s.

=== Ambush ===
Any corner of a hallway or corner outside a room can be used to "ambush" enemy ranged attackers, allowing melee fighters to approach much more easily. Simply place melee fighters behind a corner, and once enemies approach, rush the melee fighters in. This reduces the distance melee fighters need to travel.

Any other means of breaking line of sight, such as [[door]]s placed within the colony, can also be used in order to perform an ambush. Outdoor structures and hills may be used too.

<gallery widths="400px" heights="400px" class="center" mode="nolines">
File:Melee ambush.png|Attacking a ranged opponent using a corner of a hallway.
</gallery>

=== Melee rush ===
This involves charging melee fighters in, either a small group or a large mass, to take out a ranged threat, such as a sniper sitting in [[cover]] beyond your ranged colonist's reach. With large enough numbers and protection, they can overwhelm a group of enemy ranged fighters.
* [[Shield belt]]s and good armor are usually necessary for your colonists to close the gap between you and the enemy.
* Movement abilities, such as [[jump pack]]s,{{RoyaltyIcon}} the [[skip]] [[psycast]],{{RoyaltyIcon}} and the [[longjump legs]] [[gene]],{{BiotechIcon}} are a great way to approach enemies. Increasing movement speed with [[bionic leg]]s, [[go-juice]], etc. can also be helpful.

If you aren't afraid of friendly fire, it can be combined with a firing squad from a distance for devastating effects. The brawlers cause chaos within the raiding party while the firing squad lays fire to destroy them, utilizing the fact that the raiders are trying to cope with your brawlers.

Note that enemy melee rushes are not to be countered by your own melee rush; [[#Melee blocking|melee blocking]] is a much more effective tactic.

=== Peeling ===
If a vulnerable gunner is or will be under attack by melee attackers, you can 'peel' them away using your brawlers. Have them engage the melee attackers, who will then focus on your brawlers, allowing your gunner to get to relative safety.

Trained animals automatically peel for their assigned masters, if 'Release animals' is Off. The animals will attack any hostiles coming close rather than straying off to attack distant targets. Setting 'Release animals' to On right when another colonist in distress near the trainer causes the animals to swarm the attacker, peeling them off.

Peeling is a relatively high-risk activity, as you are trying to put a pawn at risk in return for allowing a pawn at greater risk to escape. Peeling pawns should be expendable or decently armored.

=== Ranged pawn self-defense ===
Guns can be used in melee combat, in two ways:

* Gun barrels can deal damage in melee. While they aren't as good as dedicated melee weapons, they will hurt, and possibly beat a low-quality melee weapon. This allows shooters to have a fighting chance against melee enemies. A gunner is likely to take out a damaged pawn or small animals on their own. Also, fighting in melee with a [[sniper rifle]] may be better than trying to fire the sniper at touch range.

* Unlike raiders, colonists can shoot their ranged weapons ''even when being attacked in melee'' (so long as the target is not in melee range). When attacked in melee, colonists will focus on melee combat by default, but can be told to fire by targeting another distant enemy. This is likely to be more effective for beating the overall raid than melee combat.

In addition, [[body part weapon]]s like [[power claw]]s and [[knee spike]]s{{RoyaltyIcon}} can be installed to give ranged fighters a better melee weapon for when they have to engage in melee.

<gallery widths="400px" heights="400px" class="center" mode="nolines">
File:Firing in melee.png|Colonists can use their ranged weapons even when being attacked in melee (so long as their target is not attacking in melee).
</gallery>

=== Ranged support ===
For maximum pain against melee enemies, use high-DPS guns for your backline, combined with quality melee for your frontline to deal sustained damage in between barrages.
*The [[chain shotgun]] or [[heavy SMG]] are the weapons of choice in close-quarters due to their unparalleled close-range DPS.
*[[Charge rifle]]s are comparable to [[chain shotgun]]s and [[heavy SMG]]s at short distances, while also able to fight effectively at long-range combat, so they are a great option if they can be afforded.
* Grenades may also be used and can be incredibly effective at stacked melee groups trying to enter through a chokepoint, but should be ground-targeted rather than freely targeted by the pawn, to avoid grenading your own melee blockers.
:Grenades can land anywhere within 1 tile of the targeted tile, so place your ground target 1 tile further away to avoid accidentally grenading your own forces or blowing up the walls that are enabling you to melee block. Like [[minigun]]s, this will often shred the walls of your chokepoint, so building extra layers of walls at the chokepoint can be helpful.
*[[Minigun]]s, while effective at shredding the tightly packed enemies behind the chokepoint, are generally not recommended due to the collateral damage to the walls. If you do choose to use them, aim at the middle of the crowd so you can hit as many enemies as possible, while also reducing the damage done to the walls.

Stray bullets will harm your tanks if the shooter is standing more then five squares behind them; that means it is not a good idea to use long-range fire when charging.

Combined with measures to force enemies into close range, these weapons may be effective against ranged enemies as well, but beware as enemies can still fire until you start beating them up.

== Stationary ranged combat ==
{{See also|Defense structures}}

=== Spacing out ===
Each colonist should ideally stand '''at least 1 tile away from other colonists''', thus reducing the chance of enemy bullets hitting somebody else after missing the original target, which deals a lot of damage to static grouped up defenders. Explosives will also hit fewer people this way, though there are better countermeasures than simply spacing defenders apart.

Alternatively, placing all colonists within 5 tiles of each other will prevent friendly fire entirely, making it appropriate if there are no ranged or explosive attackers.

=== Friendly fire management ===
Friendly fire is a serious issue when facing close-range attackers, especially manhunter packs. If they manage to run past your barrage of gunfire to engage your ranged soldiers, they may receive more injuries from friendly fire in the ensuing chaos than the attackers themselves. You need to be careful when directing your troops so you don't hit your own forces by accident.

Pawns can fire over the shoulders of friendlies up to 2 tiles (i.e. 1-tile space in between) away, meaning that you can have a 3-wide row of soldiers without friendly fire, although this may not be recommended.

# When the enemy breaks the ranks, only let the soldiers closest to melee attackers fire at them.
#*Manually re-target the others to fire at another direction, repositioning them if needed.
# Disable 'Fire at will' when the enemies are closing in so they won't switch targets, potentially causing friendly fire.
# Have only 1 line of shooters so stray bullets, including bullets fired horizontally at melee attackers, will less likely hit someone.

== Dealing with rockets ==
Rocket launchers are painful to deal with, due to the huge area damage and long range. Raiders with rocket launchers are often seen in the backline preparing their rockets, while their allies lay down fire at the front. In the mid-late game, they are one of the biggest threats from the enemy.

* Single pawns can split off from the group and charge, or pre-placed at the front of a defensive fortification, to act as distractions. They can get distracted quite easily, wasting them on animals or lone colonists. [[Animal]]s, [[turret]]s, [[friendly mechanoids]]{{BiotechIcon}} and [[ghoul]]s{{AnomalyIcon}} are all great options, as they are expendable or cheap to revive. An expendable colonist (ideally wearing a [[shield belt]] for protection) can also do the trick. In a pinch, sacrificing regular colonists may be needed; if a rocket user is already targeting a pawn and there's no way to stop it, having that pawn split off and take the hit may result in less damage.
* [[Psychic insanity lance]]s and [[psychic shock lance]]s are the most straightforward way of dealing with a rocket launcher.
* [[Psycast]]s{{RoyaltyIcon}} are effective. [[Berserk]] can be used like a psychic insanity lance, [[berserk pulse]] can be used on a nearby group of enemies to cause the rocket launcher to incur friendly fire, and [[skipshield]] can block projectiles entirely (the rocket will explode on contact, so place the shield well in front of the colonists, don't place it on top of them).

Enemies may take friendly fire, the chance being maximized by having the rocket travel over as many enemies as possible through aligning your distractors. Each rocket traveling over a pawn has up to 40% chance to impact, setting it off early.

If you see that an enemy rocketeer has locked onto a brawler, you can also choose to charge the enemy with that brawler. It will either cause the enemy to deal immense friendly fire, or allow you to take out the rocketeer outright.

== Rescue ==
When a colonist is downed or severely injured, it's ideal - if not always possible - to drag them out of the fight immediately. Don't leave them there otherwise they risk dying from stray bullets or blood loss. You don't really need to send them directly to hospital; just drop them off somewhere outside of active combat.

Colonists lying outside cover are riskier to rescue. Choose the right time to pull them out, ensuring that there are no melee enemy nearby that could tie up the rescuer, and use your best-protected colonists. Don't allow anyone near at other times as they may draw fire. Consider drugging your rescue team with [[go-juice]] if the pawn you are rescuing is under heavy fire, as this will both increase the rescuer's speed and improve their pain resistance, making them less likely to be downed. Using a [[jump pack]] {{RoyaltyIcon}} to rapidly jump in and pull them out of combat, with the i-frames incurred during jumping, makes this significantly faster and safer for both rescuer and rescuee. [[Locust armor]] {{RoyaltyIcon}} can be substituted at the cost of armor, but ideally should be paired with a [[shield belt]] to make up it. At high qualities, for the short duration of exposure, a shield belt can be superior as it prevents all damage, including that which would slow the pawn or reduce medical skills.

Non-combatants, such as those incapable of violence, are ideal to serve as rescue members by standing near a fight to pull out downed colonists. Non-combatant doctors should wear a [[shield belt]] and carry quality medicine at all times, so they can be drafted during combat and quickly tend to wounded colonist on the field. Non-combatants should be equipped similarly to above, though with no ranged weapons they have fewer restrictions on wearing a shield belt to prevent damage, and their value proposition improves.

If a colonist cannot reach the hospital in time, typically ~2 hours from death or less, have the doctor patch colonists up a little such that they can reach the hospital without bleeding out, then carry them there. You will have a higher infection chance this way, but it's better than the colonist bleeding to death while on their way to the hospital. The remaining injuries can then be treated in the cleaner environment. Alternatively, an untuned [[biosculpter pod]]{{IdeologyIcon}} can be kept nearby and the injured pawn loaded into it. This can save pawns moments from death, that a doctor could not treat fast enough to save. The cost of the pods can be considerable however, and they must be de-tuned or deconstructed and reconstructed after each event.

== Mobile warfare ==

=== Door potshots ===
This strategy relies on a few quirks with standard raider AI:
* Enemies cannot open doors, and will not explicitly focus on doors. Even if a colonist is seen walking out, enemies are not persistent, especially if a multiple-door "airlock" is used.
* If enemies do ''not'' have a clear, unobstructed path to a colonist, they will start bashing at furniture and walls randomly, splitting up to do so.

On a smaller scale, this strategy can be used by building a large room with doors at each side. Enemies will split up, then shots can be fired, then any exposed colonists can retreat from opposing attacks by having the door close behind them. On a larger scale, build a multi-layer [[defense structures#Perimeter wall|perimeter wall]] with no open entrances but many doorways, with each door being in an "airlock" formation with 2+ doors separated each with a gap between.

=== Flanking and surrounding ===
To flank enemies, have some defenders approach enemies from the sides or the back instead of concentrating fire on the front. To surround them, attack from all sides.

Enemy ranged units often stay in the same spot and only have cover from one direction, making them vulnerable to either tactic. Flanking enemy ranged units can distract them and cause them to lose their cover advantage. While this makes you lose the advantage of high-quality cover, it is balanced out by the enemy's loss of cover.

* '''Wide arc flanking:''' Instead of huddling together in a straight line, have colonists take cover in different locations in a wide arc. This allows colonists to shoot at different angles, as well as protecting from explosives and friendly fire. This can be employed against sieges and other open operations where static cover is not available.

* '''Close-quarters flanking:''' This strategy takes advantage of terrain or existing walls scattered on the map. Send a small detachment of shooters/brawlers behind structures before the enemy moves in. Ideally these structures should be near your main combat line, forming an "L" shape to prevent the enemy from surrounding your detachment. Shotguns and melee are great weapons.
: Take a few shots as the enemy moves pass, and if they attack, retreat behind cover to direct them to the main force. Any enemy that follow will be isolated and can be eliminated. Don't forget to manage your main force in the meantime. After the enemy force has passed, emerge from cover to attack them from behind. This strategy avoids melee friendly fire, by having melee fighters engage from behind, and better enables shotguns

<gallery>
Close-quarter flanking1.png|Initial position of the flanking maneuver, the detachment is hidden from the enemy
Close-quarter flanking2.png|Colonists take shots at the enemy from cover
Close-quarter flanking3.png|When attacked, the detachment retreats behind the wall
Close-quarter flanking4.png|After the enemy has engaged with the main force, attack them from behind
Close-quarter flanking5.png|The enemy is fleeing
</gallery>

==== Moving in ====
While moving in you need to make sure you stay far enough away from enemies. Directly right-clicking on the destination will nearly always result in a path that crosses with the enemy. This can be overcome by '''shift-clicking to form a path for the pawn to follow''', making sure to keep sufficient distance.

Shield belts, drawing enemy fire from a different direction, or simply using walls and terrain to block projectiles are all good ways to move in.

=== Firing at cover ===
While cover works best against attacks coming straight, it's usually better to fire straight at the target instead of from an angle. If you fire straight at it, only 1 unit of cover will be effective, but if you shoot at a diagonal angle, 2 units of cover will be effective, both being capable of blocking shots, in total contributing to higher cover effectiveness.

However, if you can get to the point where you're almost firing horizontally at the raiders, then cover becomes nearly ineffective at protecting the raider, allowing many more shots to connect. This often requires you get out of your own cover, so it's not recommended unless you can find suitable cover nearby.

This also works for your pawns: in [[killbox]], it's better to place cover at angle to increase it's effectiveness, while raiders can't benefit from angle due to lack of cover. "[[Cover|Wall + Sandbag]]" combination will have higher than 75% effectiveness at ''just right'' angle (≈83-96.75%).

'''The below shows the difference firing angle makes on the hit chance of a pawn hiding behind cover.''' Cover values are from Alpha 16, but the mechanics remains unchanged.

<gallery widths="400px" heights="400px" class="center" mode="nolines">
File:Fire_cover_straight.png|Firing straight at a raider in cover; 1 stone chunk blocks 40%.
File:Fire_cover_angled1.png|Firing at an angle; 2 stone chunks block 48% total.
</gallery>
<gallery widths="300px" heights="300px" class="center" mode="nolines">
File:Fire_cover_angled2.png|Firing at a greater angle; 2 stone chunks block 37% total.
File:Fire_cover_angled3.png|Firing almost horizontally; 1 granite chunk blocks 8% only.
</gallery>

=== Tanking ===
This tactic simply requires you put your shielded colonists before your static gunners to partially soak up gunfire. This is best when you have insufficient cover, or additional cover to block more bullets for your frontline tanks.

As with any tactic involving meat shields, this poses a great risk to colonists' lives. If the colonists' shields are downed and they are not well-armored, you will have to get them to retreat behind cover until their shields come back online, otherwise your colonist will be exposed to ruthless gunfire.

Beware of high damage-per-hit weapons which can instantly down shields.

=== Hit and run ===
Against slow or static targets you can employ this to weaken them. You will need several fast-moving long-ranged colonists, possibly with [[charge lance]]s or [[bolt-action rifle]]s. Have them move within range to fire, quickly exiting range once the enemy returns fire. Repeat until conditions are no longer safe to conduct this attack, such as enemies entering full aggression and charging.

Effective against siege camps, preparing raiders, and crashed ship parts, for they tend to stay put at their location until they are aggravated into attacking.

=== Kiting ===
This tactic is effective when all or the most dangerous enemies are slow [[moving]].

Ideally, you have fast colonists - 120%+ [[Moving]] - running near moving enemies, drawing their attention. Constantly outrun the enemy while staying within their attention range. If not, the enemy will engage other targets instead. This way, kiters can distract a group of enemies by leading them around the map. Other colonists can fire at the kited enemies. And if the kiting colonist is fast enough, they can take a few potshots (once they are far enough).

As long as your colonist safely outruns hostiles, you're fine. However, if the enemy catches up, your colonist will be slowed and on his own. Even with a regular speed colonist, kiting can be beneficial, as it gives valuable time for your ranged colonists to shoot.

====Equipment====
A fast, long-range weapon is safest - e.g. the [[assault rifle]] or [[bolt-action rifle]]. A fast moderate-range weapon (e.g. [[machine pistol]]) may be used against melee enemies, but is riskier. Slow weapons such as sniper rifles are not recommended, as the need to stand still for extended periods puts soldiers in grave danger.

Kiting colonists should be lightly armored while still maintaining a fast speed.

<gallery widths="400px" heights="400px" class="left" mode="nolines">
File:Kiting_1.png|'''Kiting #1 - when enemies are as fast as the majority of your colonists. Optimal scenario shown - all raiders are lured to 1 colonist. Ideally you have >1 colonist faster than the enemy. '''<br><br> Black circle is the ideal kiting route, when your kiter is fast enough. Red lines can be used if the kiter is too slow to run a full circle. Enemies might catch up, but you've gained valuable time for colonists to shoot
File:Kiting_2.png|'''Kiting #2 - when all colonists can outrun and outrange the enemy. Retreat just before you get into enemy range.
</gallery>

== Additional tactics ==

=== Baiting ===

Faster, more well-protected colonists can be used to lead enemies into traps or ambushes. This is for situations when you have defenses concentrated in one direction, but the enemy comes from another.

[[File:Bait tables 2.jpg|300px|thumb|right|Setting the bait furniture on fire only hastened this raider's demise.]]

Cheap furniture also makes good bait. Raiders will smash any player-built furniture left out in the open, such as tables or wooden stools. This can be helpful to split them up or lure them into range of your defenders' weapons.

=== Luring in ===
Enemies can be lured closer to your base by keeping your colonists out of sight, then swarming out to attack once they draw closer to your base. Afterwards they will switch to engage your defenders.

This can be used to negate the range advantage of enemies. It also works well with melee blocking to lure enemies into trying to jam themselves into your chokepoints, rather than beating up your base.

=== Animals ===
The animals on the map, tamed or not, can be used to your advantage.

==== Tamed animal release ====
With your handlers, you can amass a huge army of animals to charge the enemy. Simply find a good combat-capable animal, tame it, and train it to learn Release.

There are many animals that are good for this purpose. Main tactics are take quality vs take quantity.
* Large animals like [[Thrumbo]]s, [[elephant]]s or [[rhinoceros|rhino]]s have good DPS and their large health scale means that damage is less likely to kill them before they can get patched up by your doctors. However they are harder to tame and very hard to keep a big amount. Replenish losses for a long time (especially Thrumbos). Due to smaller amounts, in case of big raid, they can block only few gunners and will sooner be downed by others.
* [[Warg]]s and [[bear]]s offer a good balance of DPS, breedability and feasible number to keep (can eat bodies of raiders). Better block large number of gunners.
* [[Husky|Huskies]] significantly less DPS than the others, but are easy to breed, feed, and provide hauling. Can block big raids.
* Dryads don't need food, training, breed and can self-heal. Colony only need to maintain trees. Clawers are the best choice for meat attack, while barkskins for tanking. Use separately: clawers are faster than barkskins, and barkskins will not perform their main duty.

Tamed animals also cause pirates to fire near their allies in a bid to get them off their allies, potentially causing friendly fire.

==== Strategic zoning ====
Raiders take their sweet time to exterminate any trace of your tamed animals on the map. This can be exploited to your advantage, as long as you're willing to have a few animals valiantly sacrifice themselves.

*'''Distraction''': If you let your animals run all over the place, raiders may be tied up trying to wipe out the animals. This can give your colonists time to prepare, such as entering defensive positions or running to your mortars to fire a few rounds, as well as scatter the raiders making them easier to deal with. Raiders wielding rocket launchers also tend to waste them on your animals, leaving your colonists and structures mostly unharmed. However if they see better targets they will come at them instead.
*'''Direct offense''': Besides distraction, animals may also engage raiders, harming or killing them.
*'''Manipulation''': Animals can be moved around without the need of training Release, simply by changing the allowed zone of your animals. A short time later, the animals will move towards the zone and stay there. When animals are sleeping you can put animal sleeping spots beneath them and then remove them to wake them up. ''Changing'' the animal's zone also immediately forces it to move, at high speed, if they are not in the area of the new zone. This can also be used to update an existing zone's area by changing the animal to a different zone (which they aren't in the area of) and then back to the original zone again. Untrained animals will flee from threats, but will fight back to defend themselves if they are damaged by a hostile.
**'''Aggressive zoning''': Zone animals in a place where you are expecting an encounter with enemies. Enemies will notice the animals and will start attacking, making them fight back and injure or even down the attackers. This method works for any animal, even those that cannot be trained. Remember to undo the zoning otherwise the animals may starve. [[Boomrat]]s are especially useful by causing explosions, setting raiders on fire and delaying their assault.

**'''Animal chokepoint''': Zone the animals in a chokepoint, creating a dense cluster.
***This is vulnerable to AoE weaponry so increase the area of the zone to make it that animals don't get too tightly together, if the enemy has explosives.

==== Aggravating animals ====
If you have any easily enraged wild animals ([[emu]]s, [[thrumbo]]s, etc) standing near the enemy, you can shoot them to anger them and make them charge at the enemy.

You can also opt to enrage an animal then have a fast colonist (>130% Moving) lead it towards the enemy. Some enemies will stop and engage the animal, potentially causing it to switch targets. For quite the obvious reasons it's best to equip a shield belt on the kiting colonist if he isn't the one enraging the animal.

For this, larger animals are best due to their high health and damage. A thrumbo can be considered a godsend in a raid; just send 1 straight into the raider hordes, and let 'er rip. <br>
Smaller animals are faster and hard to hit, making them decent distraction and causing a hefty amount of friendly fire among the enemy as well.

Remember, if you can down the animal easily with colonists, so can the raiders.

Similarly to this, casting [[manhunter pulse]]{{RoyaltyIcon}} on a flock of wild (or tamed but not trained) animals can wreak havoc on raiders, just make sure that your own pawns are too far away to be targeted. It may make sense to have some fenced-in pastures at the edge of the map for this very purpose.

=== Meat shield ===
The animals surrounding a handler can be used as a convenient meat shield as they take bullets, arrows and other projectiles (but not explosions) for their master. Provided they don't stray too far, they won't receive friendly fire as the shooters simply fire over them. All you need is to train Obedience, instead of Release.

Slaves with shield belts are also a good sponge for bullets. New meat shields can be obtained from survived and enslaved raiders.

=== Base scattering ===

This is a '''last-ditch tactic to defeat human enemies''' if you are significantly outnumbered.

Instead of engaging them right away, let enemies scatter around the base first. After they scatter widely apart, divide and conquer, using large groups of soldiers to overcome them with ease, while others are busy demolishing other parts of your base.

Remember to patch up the base after the damage done. Coolers are especially tricky as they serve as weak points and are expensive.

=== Outside help ===
If the [[AI Storytellers|storyteller]] is feeling somewhat merciful, outside help may come to save the day, such as friendly [[caravan]]s, military aid from allied factions, or another raid group hostile to the first one. Don't count on this however, as these rarely happen on their own, and most of the time you still need to fend off the raiders yourself.

It is possible to call for military aid at will via the [[comms console]], if allied to an outlander or [[empire]]{{RoyaltyIcon}} faction. The raiders that are sent will only be worth 150-400 [[raid points]], so they are unlikely to handle mid-game or late-game raids on their own, but they can serve as distractions and potentially give a winning advantage at lower difficulties or in the earlier stages of the game.

It's possible to activate [[quest]]s to provoke outside help, e.g., accepting a refugee quest that spawns a manhunter pack (without a delay) when a raid approaches, or accepting an [[empire]]{{RoyaltyIcon}} quest so the noble is used as a sacrifice..

==== Common enemy ====
If mechanoids, manhunters or another enemy faction show up, raiders may stop to engage them. This causes losses to both groups of enemies, making it easier to pick off the stragglers. Being concurrently raided by two different enemies at once is more common during the ship reactor start-up phase, making it slightly easier to survive the onslaught.

If there are unopened [[ancient shrine]]s you can open them, which may contain artifacts, mechanoids, confused spacers, all useful against raiders, or none of the above.

Using the [[psychic animal pulser]] or the Manhunter Pulse psychic ability is essentially invoking this tactic, but you need to be very careful when using it.

=== Environmental hazards ===
Very rarely, when unable to put up a proper fight, you can count on Mother Nature to play for your side. Invaders will come to you without proper protection against the weather. You will be able to fend off the attack without confrontation.

Choosing to play on an extremely hot or cold map, such as in a [[sea ice]] biome near the poles, seals the fate of all human raiders foolhardy enough to come. However, once passing 300 raid points, only [[mechanoids]] will spawn in extreme temperatures.

<gallery widths="450px" heights="450px" class="center" mode="nolines">
File:Siege flee from Toxic fallout and hypothermia.png|'''Siege flees from Toxic fallout and hypothermia.'''
File:Siege flee from Toxic fallout and hypothermia 2.png|'''Free prisoners in bulk.'''
</gallery>

= Humanoid assaults =
== Raiders ==
"Raiders" come in a wide variety of sub-types, and with a surprising variety of tactics. But they all need to be explained the error of their ways...

=== Behavior ===

[[Raider]]s will attack randomly chosen constructed objects, colonists and colony [[animals]]. They will not attack natural rock walls (except for sappers), non-hostile wild animals or unpowered [[turrets]]. They will attack [[prisoner]]s if they are captured from their enemy factions.

They usually set fire to crops in [[growing zone]]s, [[power]] generators, [[power conduit]]s, and other [[production]] buildings. They will melee attack furniture, doors and walls. They will also use thrown explosives on structures, and some use [[EMP grenades]] to stun your turrets.

Raiders will prioritize firing on [[colonists]] or [[turrets]] that are actively engaging in the fight, but will otherwise attack random objects.

If human raiders are unable to defeat your colony in time, they may give up. Normal raiders will give up between {{ticks|26000}} to {{ticks|38000}} after the raid begins, while sappers will give up between {{ticks|33000}} to {{ticks|38000}} after they begin the attack.

=== Preparation ===
Human raiders will sometimes start by standing around in a group where they spawned and will continue this until they lose a certain amount of raiders or they hit a certain preparation time limit, at which point they begin the assault. When a colonist is close to the raiders they will attack the colonist.

=== Equipment ===
Raiders spawn with randomized equipment determined by their "pawn kind". While the budget for "purchasing" each individual of the different pawn kind is determined by the [[storyteller]] and the current [[raid points]] value, the equipment itself is decided by the weapon and clothing budgets and type restrictions of the pawn kind. More information on the pawn kinds can be seen in the Pawns sections on each [[faction]]s' page.

==== Apparel ====
[[Raiders|Pirates]] can range from only wearing a tattered pair of [[pants]] to [[flak vest]]s to full sets of [[marine armor]]. [[Raider#Mercenaries|Mercenary slashers]] will always come in [[shield belt]]s and only they do so.

[[Tribals]] always come in [[tribalwear]], with some in [[war mask]]s or [[veil]]s. Some later game come with [[plate armor]] as well.

In cold environments, both will come in wearing [[parka]]s or [[tuque]]s, protecting them from temperatures of around -40 to -50°C, sometimes up to -110°C if they wear wool parkas. They don't usually come in wearing [[duster]]s or [[cowboy hat]]s in hot areas, making them vulnerable to the heat.

They tend to wear leather, [[cloth]] or [[synthread]] clothes, which don't provide good protection, and less commonly the more protective [[devilstrand]] or [[hyperweave]].

While mid-late game pirates usually come with normal quality flak and marine armor providing around 100% sharp armor, with quality apparel you can push yours to have more than 130%, even without masterworks or legendaries, giving you the upper hand.

==== Weapons ====
For most factions, skills are assigned at random, meaning that raiders are not always given weapon appropriate for their skills; skilled shooters can be randomly equipped with melee weapons and melee pawns equipped with guns. So if you have your colonists equip weapons according to their skills, you already have an advantage over many enemies. Unlike the other factions, the [[Empire]]{{RoyaltyIcon}} will ''ensure'' that its soldiers have skills appropriate for their issued weapons.

[[Tribals]] usually come equipped with primitive weapons of random quality, either melee weapons or ranged weapons limited to bows and [[pila]]. Melee weapons are not to be underestimated however, as blunt armor is often lacking and both [[longsword]]s and [[spear]]s are relatively common and have respectable {{AP}}.

[[Pirates]] and [[outlanders]] can spawn with most weapons in the game, up to and including dangerous [[doomsday rocket launcher]]s.

However, some classes of raider always come with the same weapon or same category of weapon. For example, [[Raider#Mercenary_sniper|mercenary snipers]] always use [[sniper rifle]]s, [[Raider#Mercenary_grenadiers|grenadiers]] always wield either [[frag grenades]] or [[molotov cocktails]], and tribal archers of all types always use [[neolithic]] ranged weaponry.

==== Drugs ====

Pirates or Outlanders may utilize some form of combat-enhancing drug, namely [[go-juice]], [[yayo]] and [[luciferium]]. They will usually start off addicted to them, and will carry some in their inventory which is dropped upon death. They may also use multiple drugs, disregarding the risk of overdose.

These can reduce the amount of the pain received, making the raider last longer in battle before going down. Increased movement speed also allow raiders to get into position earlier, and brawlers to harass your defenders more easily.

*[[Go-juice]] is an excellent combat drug that makes the raider much more efficient in battle. It eliminates 90% of pain, gives a 30% movement speed buff, and a 10% consciousness buff for more accuracy. The raider is almost guaranteed to fight until death, or the rarer case of incapacitation through a shattered spine, severe brain damage or removal of both legs.
**It's almost always more worth it to use body part-destroying weapons such as the [[Sniper rifle]] to kill them, as Go-juice does not reduce the actual damage they take.
*[[Yayo]] grants a 15% buff to speed and eliminates half of pain received. Enemies under the effect of yayo are more durable against damage not concentrated on a vital body part
**It will take more hits to down them, and more likely the raider dies first due to lethal damage, but is still possible.
*[[Luciferium]] grants a wide range of buffs to the user, from increased organ function, to slight movement speed and consciousness buffs, to reduced pain.
**It's more troublesome to capture addicted raiders since you'll need to regularly feed them luciferium to sustain their lives, which is very expensive and hard to come by -- it's usually more worthwhile to just strip and finish them on the spot.
**Although it is possible to farm this drug by addicting raiders to it and release them, the next time they come they will bring some with them.

=== Sieges ===

During a [[Raider#Siege|siege]], raiders go to a location outside your base, receive materials via drop pod and will proceed to build a simple mortar camp. The mortar camp will generally have 2 mortars and sandbags as cover. The sandbags need not cover the mortars, nor will they necessarily face your base.

<gallery widths="450px" heights="450px" class="center" mode="nolines">
File:Siege_base_construct.png|Siege camp under construction.
File:Siege_base_finished.png|Finished siege camp. Note that sieges always come with 2 mortars.
</gallery>

When faced with a siege, there are a few strategies you can use.

In most cases it's better to attack the siege camp as the raiders will continuously siege the colony even if you're in hiding, and most likely you will eventually need to face off against the raiders yourself.

==== Camp assault ====

If you assault their camp, one possibility is sniping the raiders, prompting them to assault your colony directly instead of continuing their siege once you down several of them. Defeating them early enough will result in most of their items remaining intact, which you can take for yourself. <br>
Another alternative is to snipe the mortars, hoping an explosion will take out many raiders, but keep in mind that for those you will need to either send someone dangerously close to enemy fire, or draw all attention to one side to allow flankers to snipe and detonate them.

Unlike most defensive situations, this time they will have the advantage of good cover on their side. You will have to find suitable cover, such as stone chunks, which you can fire from.

Sniping [[mortar]]s under construction, when they have much lower health, is effective at wasting the enemy's resources.

They are vulnerable to flanking if they haven't finished their sandbags or left a side uncovered. However, once all cover is completed, flanking is less of an effective solution.

==== Early interception ====

The best time to attack them is when they've just started building their camp. At this time their resources would have arrived.

Attacking them at this time forces them to use stone chunks just like you do, instead of having the superior sandbags on their side. Their mortars won't be ready as well.

'''Attack only when their resources have arrived''', otherwise they will flee and not send any resources, which you could've stolen had you attacked later.

==== Hit-and-run ====

An effective tactic to lure sieging raiders out is to conduct hit-and-run attacks against them. Taking down someone usually causes them to give up on sieges and directly attack, making them lose their cover advantage.

==== Countering with mortars ====

If you have your own mortars, you can use them to fire back at the raiders. The raiders will stay put to defend the camp, making them easy targets for mortar strikes. It's best to wait for the raiders to arrive at their siege encampment location so leading the target isn't required.

[[High-explosive shell]]s deal heavy damage to tight groups of raiders if they hit, ignoring all cover but solid walls in the process. A tight volley can devastate mortar camps, forcing them to either attack or flee outright. Waiting for their supplies to be dropped gives you the possibility of causing their own mortar shells to explode on them causing significant additional damage.

[[Incendiary shell]]s are an effective way of distracting sieges as the raiders will be preoccupied with extinguishing the resultant flames. 2 mortars are usually enough to keep them from doing any activity other than firefighting, unless it is raining or there are no flammables nearby. This deals little damage to them, however.

[[EMP shell]]s can stun the mortars, preventing them from firing. It is perhaps better used as a support weapon while your defenders assault the camps, to reduce the damage done to your base.

==== Sneak attack ====

If you don't have the strength to attack directly, you can wait for them to sleep at night, then use the opportunity to set your colonists into position for a sneak attack.

Once someone receives an injury, everybody will wake up, so be sure to have everything in place.

# Get within range and throw a coordinated barrage of [[frag grenades]] at the enemy, blowing the defenseless raiders to bits.
# Go very close (no more than 3 tiles) then unload your guns on the exposed raiders. Nearly every bullet will connect, dealing heavy amounts of damage upfront.
# 1 well-aimed [[doomsday rocket launcher]] can end the siege easily. While also effective at day, it is much safer to approach at night, and the raiders will also be more tightly packed.
# Send brawlers straight in, beating up dangerous enemies like rocketeers first.
# Steal their supplies and wait for them to send more. Free food and mortar shells!
# Scatter chemfuel canisters around the camp, pick up shells and survival meals. Retreat. Load one incendiary round into your mortar. Do one shoot, enjoy the popcorn.
# Burn the enemy with fire, a task made much easier while they are off-guard. This will eventually force them out to attack after suffering from heavy losses.
#* Lighting the mortars on fire allows them to be destroyed with ease.
#* Surround the camp with fire. Upon waking up, they will put forward their futile efforts in controlling the raging sea of fire around them, eventually giving up and attacking.

==== Deep tunneling ====

Mortars cannot hit anything that is under an overhead mountain. This makes deep mining a effective defensive strategy against heavy bombardment. If you don't build your base into a mountain, you may at least consider digging out at least one panic room for non-combatants to hide within from the shells while others head out for the assault.

==== Firefoam shell jamming ====

[[File:Firefoam shell jamming.png|500px|thumb|right|Enemy mortar filled with a firefoam shell, demonstrated by reddit user u/xenoxaos.]]

An interesting way to nullify the threat of a mortar attack is to launch a transport pod filled with firefoam shells to a location closer to the mortars than the shells they brought with them. When the shells arrive, the enemy will load them shells into the mortar instead. This means that the damage to your base will be much reduced, as firefoam shells do little damage beyond damaging roofs.

===Summon Fleshbeasts===
The [[Psychic_rituals#Draw_fleshbeasts|Draw Fleshbeasts]] psychic ritual can be an effective way of dealing with sieges. The ritual only takes 2 hours to complete, costs a trivial amount of [[Bioferrite]], and the resulting fleshbeasts generally pop out directly on top of hostiles on the map. Surviving Fleshbeasts are preferable to mop up compared to the damage caused by explosive shells landing in your hospital or storage rooms.

{{clear}}

=== Shielded melee charges ===

[[File:Melee_charge_edge.png|240px|thumb|right|Full melee charge at the edge of the map, with everyone shielded and equipped with melee weapons.]]

Pirates, Outlanders or Imperials can come with all-melee charges, with most enemies wearing [[shield belt]]s. This can prove a threat to ranged-reliant defenses as they charge towards the colonists directly with their shield belts blocking large amounts of damage. <br>
While they are vulnerable when their shields are down, many can still reach your colonists and engage them in melee combat.

==== Melee blocking ====

The '''[[#Melee blocking|Melee blocking]]''' tactic is especially useful here; for better effectiveness, open multiple chokepoints to spread out enemies and keep them busy trying to squeeze in, otherwise they will get bored and wander off to attack other things.

Shields don't stand a chance against concentrated fire poured down a narrow entrance. Using [[Grenades|EMP Grenades]] or [[EMP launcher|EMP Launchers]] can entirely disable the enemy shields, making mowing them down much easier, but ensure you don't accidentally short out the shields of your own melee blockers. It's best to order the grenadier or launcher wielder to attack a specific ground point rather than letting them freely select their target, as they may try to grenade a target right next to your own melee blockers. Both grenades and launchers can deviate by up to 1 tile in any direction from the targeted square, so take that into account when selecting your aiming point.

{{clear}}

=== Sniper party ===

Raiders can come using only sniper rifles, giving them a very long range but low overall damage.

The danger comes in that if you engage them conventionally, you may need to exit your quality cover, removing your cover advantage.

Sniping them back is not recommended unless you have a surplus of skilled snipers and cover.

==== Luring in ====

Instead of engaging them on the frontline, you can keep everyone out of sight, then rush out only once they get close to your base, negating their range advantage.

==== Killbox ====

A well-designed killbox can entirely negate any advantage that sniper parties field. Critical to that is ensuring that line of sight is entirely blocked for incoming attackers until they are in range of your own forces, preventing them from being able to take cover once inside the killbox, and using sandbags to force them to walk (slowly) while already under concentrated fire without being able to return fire.

=== Heavy explosives assault ===

Enemies may come in mainly equipped with area damage weapons, such as rocket launchers, grenades and miniguns. This can cause serious damage to your base, your colonists, and the raiders themselves.

The main danger, as always, is from the rockets. The ideal method is to [[#Distracting rockets|distract]] them from the main defending force, not only reducing damage taken by friendly forces, but also increasing friendly fire the enemy takes. The fact that so many of the raiders have rocket launchers means that friendly fire can be so serious that the raiders will decide to retreat to cut losses by friendly fire alone.

Due to the wide use of explosives, cover is less useful; you would benefit more from flexibility in positioning rather than protection from cover. Space out your defenders, preferably far from your base structures, while giving them enough space to move around to evade attacks.

==== Distraction ====

If you have many tamed animals, you can zone them near the raiders, who will be distracted to fire at the animals with rockets. Enemies are much more likely to receive friendly fire when firing towards your animals right next to them.

==== Grenadiers ====

Besides rocketeers, many of the enemies will also be grenadiers, which are short-ranged and are thus vulnerable to fire from a distance. Once the rockets have been taken care of, you can shoot them down with concentrated fire quite easily. Make sure to dodge the grenades if they do close in.

==== All-in melee charge ====

You can go hardcore and send in all your shielded brawlers to go straight at the enemy rocketeers. Gunners should stay out of range of rockets until all rockets launchers have been used.

This is especially effective when '''they come in to chase a refugee''', leaving you enough time to position your brawlers deep into the enemy. <br>
At any rate, expect losses this way due to the concentrated explosions.

=== Base flank ===

Besides sending one large attack party, enemies can also split up their forces and attack your base from multiple sides.

To adequately defend against this sort of attack, you may need to split up your own defenders and fight several battles at once, thus increasing the difficulty of managing the battle.

Each of the individual groups will flee on their accord.

==== Divide and conquer ====

If the enemy decides to prepare before attacking, you can afford to send out a larger attack party to eliminate the groups one-by-one.

=== [[Sappers]] ===

Sappers will mine and blast their way through any obstacles, such as natural or constructed walls, though avoiding high-health ore veins. They will also try to circumvent your defenses to attack from another direction. Their goal is to reach one of your bedrooms or barracks, where they will begin to wreak havoc.

In an open base, sappers can usually be treated as a weaker-than-usual bunch of raiders. However, they are a great threat to turret-reliant, mountain or walled bases, including bases with killboxes.

Their grenadiers and miners deal heavy damage to structures; even the toughest [[plasteel]] walls will not stop them for long. They will also persistently try to tunnel into your base, continuing even if their digger is killed or they are under attack.

==== Turret funneling ====

It is possible to funnel sappers with unpowered turrets, since sappers will avoid entering turret radius. Note that this doesn't appear to work to funnel sappers into killboxes.

==== Early interception ====

With enough manpower, you can choose to intercept them while they're tunneling into your base. They tend not to use cover when doing so, so you can catch them by surprise. Once your defenders intercept them, they will turn to engage you.

==== Rocket counterattack ====

The [[doomsday rocket launcher]] is your best bet against sappers, if they aren't a full melee charge. Since they are bunched closely together, a single well-placed rocket can blow up most of the attacking party, causing the rest to flee in panic. If they have rocket launchers, they may drop them on death, so you may actually end up with more rockets than you started with.

If you are the one using the rockets, you have the advantage of being able to fire first. Aim it at a spot where the enemy is likely to be bunched up. If you're quick you can defeat the enemy before they can even fire back at you, ensuring victory.

Rocketeers should be behind your best cover so they can survive long enough to fire. Your other colonists should be closer to the enemy to draw fire, but out of the rocket's path lest it hits your colonists instead.

==== Mountain bases ====

If you're in a mountain base you can draft a few melee pawns to wait at the entrance, as well as a few ranged pawns facing the entrance to fire down the tunnel. When they do break in you will already have prepared to face the raiders and can pour a stream of lead right into their face or cut them into pieces.

In a mountain base, since they take longer to mine through the rock, you may try placing an [[IED trap]] right behind the wall that a sapper is trying to tunnel through, to catch them by surprise with an explosive blast. This is especially effective if it's placed right on the other side of a loose [[stone chunk]] (easily found in tunnels), which will slow down any enemies stepping over it enough that they won't be able to retreat in time.

==== Aftermath ====

Remember to cover up any tunnels or gaps in your defenses as they open up an opportunity for raiders to come straight into your base. You may fortify it and turn it into a booby-trapped chokepoint to catch unsuspecting raiders seeking direct entry.

=== Drop pod attacks ===

Sometimes pirates or mechanoids will come in drop pods. If they land at the edges, they can be treated as a normal raid party, unless you have expanded to the edges, in which they will land inside your base. <br>
To defend against this, have a second line of defenses inside your base so you can deny the drop-podders easy entry into your base.

The main danger comes in landing right in the center of your base. Capable enemies not using alternative strategies such as sieges or sappers have a 10% chance of doing so.

Once they choose to land there, things will get ugly. By landing in the middle, they bypass most of your conventional defenses, and you can't use your cover advantage against them. They will also break through constructed roofs on their way down, landing right inside rooms and buildings. This can put not only your colonists, but your stockpiles in grave danger, as well, especially if they land near your volatile [[mortar shell]]s or [[chemfuel]] stores, or [[Battery|batteries]].

Fortunately for you, they have a short delay ({{ticks|520}}to be exact) before they open and all hell breaks loose. They also come in smaller numbers than regular raids.

Enemies in drop pods cannot land in tiles beneath an Overhead mountain, so tunneling deep underground can make safe rooms.

==== Strategy ====

Once you see them land, you should immediately decide what strategy will you use: attack immediately or wait and let them break furniture or steal things. In case of immediate attack, draft any nearby armed colonists to the site, whether they are your designated soldiers or not. Let them hold off the attackers for a while before your soldiers arrive to help. You have less than 9 seconds before they open, not enough for a soldier to get halfway across the map to help.

Any non-combatants should immediately be evacuated. They may still stay close to help in rescue efforts, pulling out any downed colonists. Make sure it's safe to rescue them- as in rescuers not walking through the crossfire and back again to get a colonist to the hospital. You may need to forbid doors to prevent them from walking through the firefight into a hospital. Melee is useful against these attacks, for you can immediately start beating up the enemy as soon as they exit the pods. They can also shut down dangerous enemies such as rocketeers.

If you decided to wait, draft your soldiers and put them near (but not close) to the drop area and wait. When raiders face no resistance, they will immediately start breaking furniture, put fire (sometimes turning the room they landed into gas chamber) and later will decide to steal some things (including furniture that can be moved), take it and flee. Let them do it, and when they take items and go, attack. While fleeing, they will not resist, making it much safer to kill all of them and return stolen back to the storage. Works best when raiders landed inside the locked room.

Like other raids, humanoid raiders will attempt to flee after receiving heavy losses; however, if they land inside enclosed areas of your base, they will be trapped, allowing your colonists to down and capture them at leisure; in their panic, they won't try to fight back, until you're well into beating them up.

==== Cover ====

You should use your furniture or wall corners as cover and fire from behind them. You can also have 2 colonists hiding behind each doorway for full cover. Toggle the doors to be held open, otherwise they can't fire. Be careful as enemies will also utilise cover as well; to combat this, attack from multiple angles or use melee fighters.

Spread out colonists so they don't take collateral damage, even if it may mean some will fire out of cover. Keep heavily armored colonists up front and lightly armored colonists at the back.

Colonists with high construction skill can relocate furniture quickly; use this to your advantage by creating cover for yourself and removing it from enemies.

If you have larger bases, you can build indoor defensive positions along crucial corridors, but take care not to let the enemy use them. Stone [[shelf|shelves]] are an option as they are durable, non-flammable and beauty-neutral.

==== Fire management ====

As most furniture is flammable, you will need to extinguish any fires if you want to prevent damage. One option is to reinstall and trigger a firefoam popper inside, which also fireproofs the room, preventing any further fires.

If you prioritize the defeat of the raiders over the loss of your property, and the walls of the room are fireproof, you can simply let fires burn, or even start some more, while you evacuate the room and shut the doors, cooking the raiders alive. Watch out for fire and heat spreading to nearby rooms, and put out fires immediately once the raiders are well done. <br>
Not effective against mechanoids as they aren't affected by temperature and cannot be set on fire.

==== Equipment ====

High-DPS or melee weapons work best to deal with drop pod attacks. <br>
Mid-range weapons are also good for clearing out larger rooms. <br>

Long-ranged weapons are less effective due to their low damage output and the confined nature of indoor spaces rendering their superior range unnecessary.

Explosive, incendiary or area denial weapons are excellent at room-clearing, but are not recommended except in dire situations due to heavy collateral damage.

=== Tribal raids ===

[[File:Tribal_raid.png|300px|thumb|right|Group of tribal fighters.]]

Tribal raiders come with relatively poor equipment, instead relying on sheer numbers for power. Their neolithic weapons can dish out heavy damage despite their low technology level. They are also adept at combat, with many being acquainted to some combat skill or another. <br>

Different strategies may be required, compared to pirate or outlander raids.

==== Tribal fighters ====

They can take more of a beating compared to other poorly armored enemies as some of the clothing items they wear gives them increased endurance against pain, but when compared with other decently armored enemies they are easier to kill individually as their clothing doesn't provide much protection overall.

Their archers or hunters can fire their bows from a somewhat long distance, sometimes forcing you out of cover to fire your shorter ranged weapons at them.<br>
Warriors or berserkers don't use shields (unlike their pirate counterpart, the mercenary slasher), making them vulnerable to gunfire.

You should watch out for the pila wielded by heavy archers, as well as berserkers.
*Despite the short range and slow fire rate, pila are incredibly deadly if they land, capable of killing or incapacitating unprotected colonists with a lucky shot to the heart, spine or limbs.
*Berserkers carry excellent melee weapons that dish out incredible amounts of damage once they get close.

==== Weapons ====

You will need sufficient mid-long range firepower to take down tribal archers from a distance, for getting close to them in order to fire your guns is pretty much suicide. Long-ranged weapons beyond 32 tiles can effectively hit archers at maximum range, matching or outranging them.

Close-mid ranged weapons with high stopping power are good for taking down tribespeople that come too close to your defenders, but they alone cannot defeat tribals effectively just by staying in static cover.

Crowd control helps greatly in defeating tribal raids.

*The [[Minigun]] is extremely effective as it can easily mow down the densely packed groups of tribal invaders.
*All explosive weapons are devastating on tribals.
**Rocket launchers deal heavy damage while being reasonably accurate.
**[[High-explosive shell]]s can pulverize a sizable group of tribals at once if they manage to hit.
**Grenades are less effective as you have to risk a colonist or two in order to get in range.
*Incendiary weapons are good at getting pesky archers out of cover for your colonists to hit.

=== Empire raids ===

Added in the new [[Royalty DLC]], the Empire is capable of sending powerful troops to assault your base. Unlike Outlanders, Tribals, or Pirates, one major advantage they have is that their skills are matched with the weapon they use- melee Champions will actually be good at melee, while Troopers, Janissaries or Cataphracts all have excellent ranged performance.

Cataphracts are among the most heavily-armored units in-game, with an outer layer of [[cataphract armor]] and an inner layer from an [[armorskin gland]]. However, their armor also slows them down significantly.

This can, however, be turned to your advantage through the use of [[Psycasts]] introduced in the Royalty DLC. Using Berserk or Berserk Pulse on the most dangerous of the hostile army can cause them to turn their powerful weapons towards murdering (and being murdered by) their allies rather than your colonists. Note that Berserk Pulse can affect pawns immediately on the other side of a wall by casting the ability on a tile adjacent to a wall, allowing the ability to function as a defense against sappers or groups moving through constrained areas (such as a narrow snaking corridor leading to your killbox).

== Caravan ambushes ==

Defensive battles don't always happen at base. Sometimes it may happen far away from it, striking one of your caravans, perhaps loaded with plenty of silver. Or maybe they creep to your traders and demand ransom, which you don't feel like paying. You always need to be prepared for ambushes when you send out caravans.

=== Escort ===

In any cargo-carrying caravan, sending only 1-2 colonists is usually not advised except in very short-distance trips as they will not be able to fend off an ambush. In this case, have combat-capable escort members which can fight and carry items, as well as medics who will patch up your colonists after battles.

If you have lots of attack animals, you can also send just 1 skilled handler with the attack animals. They can swarm any attackers, and you can leave colonists back at base for work. Remember to take into account the animals' food needs; grazing animals work best for this reason.

If you are not carrying much besides a lone colonist, leaving him to go alone is helpful as lone colonists are hard to detect, reducing both the likelihood and the power of ambushes. A single colonist with a pack animal trained to obedience should be able to fend off most attackers.

=== Ambush site ===

The ambush site is small, restricting the space where you can conduct your battle. This renders many tactics obsolete, such as long-ranged sniping or kiting. You will often have to face off the enemy in a direct gunfight or brawl.

Besides this, you can't escape the fight until it's over, leaving no choice but to fight back.

=== Cover and positioning ===

[[File:Ambush_fight.png|600px|thumb|right|Improvised defensive position against ambushes, making the best of what is there. Colonists behind walls will enjoy up to 75% full cover, while pirates will only receive 25% at most from trees and such. Two brawlers are ready to execute a melee sortie, while another is ready to [[#Peeling|peel]] for the gunners. Combined with good equipment, this allows the fight to be won with few injuries even when outnumbered.]]

If you have time, go somewhere where there is cover for you, but not the enemy. This gives you a significant upper hand in defensive battles where the enemy is coming at you. You should be hiding behind walls for cover if possible, as they provide up to 75% cover, but if they are not available, use what is available, e.g. stone chunks or trees. Space out your defenders to reduce the amount of collateral damage the pirates deal.

Melee sorties or rushes work well if you have brawlers, to negate any dangerous ranged threats; [[shield belt]]s help them traverse the short distance to engage.

=== Items ===
You will need to bring some items so you can be prepared for a surprise attack.

==== Weapons ====
You usually don't have weapons to switch in a caravan unless you're bringing more than you need with you, so choosing the right weapons for your escort party is important.

*High-DPS weapons are optimal for dealing with ambushes.
*Long-ranged weapons are good for taking down targets at medium-long range, however their low DPS may offset their range advantage in an ambush.
*[[Minigun]]s are good against tightly-packed raiders hiding behind cover in an ambush. However, their heavy weight and movement speed reduction means you may want to reconsider bringing one.
*Melee weapons can help fight off enemy brawlers, or disrupt enemies behind cover. You should have at least 1 melee fighter in each escort.

==== Medicine ====
You should have some medicine handy so your colonists can patch themselves up after the battle.

[[Medicine]] should be your choice here; you should try to get good treatment to reduce chance of infection, as colonists don't get much rest in a caravan. [[Herbal medicine]] is useful if you have a good doctor on hand.

=== Aftermath ===

You can reform the caravan immediately after the battle is ended; you can bring along any downed colonists, as well as capture downed enemies. The caravan members will tend to themselves shortly afterwards.

Alternatively, you can stay and forage from the ambush map before you leave.

= Manhunters =
Animals, singly or in groups, may randomly turn mad and become hostile due to various reasons.

When mad, they will actively attack humans or mechanoids, and will not attack other structures unless provoked (such as seeing someone walk through a door. Note that this includes colony animals. Manhunters can and will navigate through doors opened by colony animals, and will attack the door for a while if the door closes in front of them). They are not sophisticated in their attacks and are only capable of actively using melee. Some can explode upon death for devastating results.

=== Animal categories ===
Most animals can be part of a manhunter pack. Each kind has its own statistics, and can be roughly grouped as follows:

# In terms of speed:
#*Slow: Animals that run slower than an average colonist. This allows you to kite them in addition to melee blocking.
#*Fast: Animals that are faster than most colonists.
# In terms of other properties:
#*Explosive: Animals that explode on death such as [[boomalope]]s or [[boomrat]]s. They can set your brawlers alight, ruining melee blocking defenses, so for these, you may need alternative tactics. These types, however, can trigger a chain reaction, as the explosion from one animal can kill others, causing further explosions and potentially further deaths.

=== Occurrence ===

Mad animals can strike your colony in several ways.

#Singular mad animals may randomly attack.
#Manhunters packs can arrive in great numbers, afflicted by the deadly disease [[Scaria]].
#Psychic waves drive all animals of a single species insane, directing them at your colonists. They are usually scattered at first, then proceed to converge on your colonists.
#In an unfortunate hunting incident, animals being hunted will turn on you, and may even bring their allies along.

=== Melee blocking ===

As with any full melee attacks, '''[[#Melee blocking|melee blocking]] is an extraordinarily efficient way to defeat manhunter packs'''. This is especially so if the animals are small such that they deal little damage before being killed, one after another.

When psychic waves occur, either lure animals into one spot or set up multiple chokes for attack.

=== Animals vs. Animals ===

One good way to fight off mad animals is with... more animals! Just draft anyone with Release-capable animals assigned, and set them out. Your colonists can watch safely from a distance, or take a potshot or two while watching the animals tear each other apart. Just remember to have someone mop up the bloodstains and haul the corpses of the fallen. As with melee blocking in general, even non-Release-trained animals can be used for defense by confining them to a single tile zone at the exit of your killbox, causing them to both body-block and attack any hostile animals that try to enter through it while your colonists shoot at them.

=== Hit-and-run ===

A slower strategy is to draft a colonist, place it in a door to shoot a maddened animal, move the colonist back to safety and wait until the animal gives up and wanders off, then repeat. Be careful since this will draw the attention of surrounding maddened animals making them attack the door where the colonist came from, so be ready to repair it immediately. <br>
You can either kill them directly or wait for blood loss to take its toll. Larger animals can be softened this way before you move in for the kill.

This method is best used if you don't have enough firepower to take on them directly, and you have durable enough doors or a good builder to hold against animal attacks.

=== Kiting ===

Being unsophisticated in their tactics, they can be lured easily.

If you have good shooters that are fast (moving >140%), you can easily kite the faster animals. <br>
The larger animals are usually slower and any colonist that has normal Moving will do fine against them, though it's still better with a faster-than-average colonist.

It is possible to combine this with a long-range firing squad and turrets laying fire from a distance while they are chasing the colonist; be sure that the animals do not lose track of your kiters, otherwise they will switch targets and go for somebody else.

=== Turrets ===

Turrets can distract manhunters for your colonists, giving them more time to shoot while enemies are occupied by the turret. They may explode when destroyed, taking out a sizeable group of animals who won't run away from exploding turrets, switching to another target only after the turret is no more.

=== Waiting it out ===

If you have a perimeter wall or a superstructure base with decent food stocks, you can simply wait it out inside while they relentlessly swarm outside the walls.

Remember not to let anyone outside unless your intent is to kill the animals. Be careful with your tamed animals who may accidentally let the manhunters in by holding doors open for them.

They will actively attack doors if a colonist hides behind them; as a precaution, build it out of a sturdier material such as [[plasteel]] so they don't get destroyed during a manhunter attack. They will give up after a while if the doors are not destroyed. Alternatively, simply have a builder build a wall behind the door, totally preventing manhunters from entering even if they break the door.

=== Scavenging dead animals ===

Manhunter packs are a decent source of [[meat]] for your colony. If there are still maddened animals, wait until the other animals from the pack go to sleep, walk away far enough, or get a fast colonist to try and haul the dead ones away. Note that animals with [[Scaria]] from the manhunter pack events have a high chance of instantly rotting on death and thus being unharvestable for meat or fur/hide.

= Mechanoids =
{{stub|reason=Needs new Mechanoid types and Mechanoid cluster events from Biotech and Royalty}}

Mechanoids come in 4 types: [[Scyther]]s, [[Lancer]]s (1.0), [[Centipede]]s, and [[Pikeman|Pikemen]] (1.1). They have much differing stats and weapons, meaning different tactics may be used. All types are armored to some degree, and are basically immune to fire damage.

In many raids where they come/drop in at the edges, the Scythers will outrun the Centipedes by a great margin, giving some time to deal with them before the centipedes. However, they can and will support one another effectively, if given the chance for them to come together.

Unlike human raiders, they do not flee, meaning that all of them have to be taken out to neutralize the threat. They do not actively use cover, either.

=== General strategy ===

Ranged mechanoids have a long attack range (at least 27 tiles), making them troublesome to deal with. A way to deal with this is to [[#Luring in|lure them into close range]].

They are vulnerable to EMP damage, which can stun them, rendering them hunks of helpless metal. This can open a window of opportunity where you safely engage at close range, or even with melee. After each use of EMP, mechanoids will adapt to it, becoming immune to further stuns for a short while, so you will need to carefully time assaults and disengage when the mechanoids are about to reactivate.

=== Scythers ===

[[{{Q|Scyther|Image}}||100px|right]]

Scythers are deadly with melee, and will charge head first at your defenders. They can easily win in a 1v1 fight unless your fighters are heavily armored and have high DPS.

The optimal method of dispatching them is by [[#Melee blocking|melee blocking]], with the added effect of luring the other mechanoids closer to your base. This must be done quickly otherwise the centipedes will catch up and unleash hell on your colonists who are closely packed together in a melee blocking attack.

EMP weaponry combined with melee blocking is a frighteningly effective and safe way to deal with scyther-only charges. A stunned scyther standing in the chokepoint will block all the other scythers standing behind. To prevent adaptation, only stun the mechanoids within the chokepoint.

If fighting from a distance, high-damage weapons are essential to bursting them down before they reach your colonists. Make sure you always have someone to [[#Peeling|peel]] them off your gunners in case they do survive your barrage.

=== Lancers ===

[[{{Q|Lancer|Image}}||100px|right]]

Lancers are capable of medium-long range supporting fire to pick out single targets. Despite their apparent role, their performance is actually better the closer you are to them, meaning that approaching them isn't a good option.

They are vulnerable in melee combat, so melee rushing supported by close-range firepower can be used to take them down. Their low health makes taking them down relatively quick despite their light armor, though their damage in melee combat should not be underestimated, and concentrated fire from charge lances can make short work of shields.

If fighting from a distance, cover is vital in getting the upper hand. You need to be able to get your other gunners into range while giving them reasonable cover from the high damage shots. Lancers aren't particularly good shooters (equivalent to a level 8 shooter), so you may readily outperform them with sufficient mid-long ranged firepower.

=== Centipedes ===

[[{{Q|Centipede|Image}}||100px|right]]

Centipedes, on the other hand, specialize in crowd control and area denial; the [[Heavy charge blaster]] can annihilate groups of colonists, while the [[Inferno cannon]] sets your colonists ablaze and will burn down your base if you're not careful. They are incredibly durable, sporting thick armor and high health, and can take many hits before being downed.

Spreading colonists apart can mitigate the crowd-control capabilities of centipedes, limiting the number of colonists hit by their weapons.

The Inferno cannon is annoying to deal with and should be your priority target. Keep watch on your colonists at all times and always send them back into cover after they get hit.

Despite their high resistance against sharp damage, shooting them is generally the best option. One good thing is that their large size makes them much easier to hit.

Engaging it in melee is possible, though you have to be careful. While centipedes don't hit hard in melee, if they are carrying the heavy charge blaster, they can deal massive damage to grouped up brawlers, while inferno cannon can cause the brawlers to ignite and run, allowing the previously locked down centipedes to fire. Ideally, all nearby centipedes must either be engaged in melee or disabled to prevent this from happening.

Their slow speed and weaker blunt armor make them excellent targets for high-explosive mortar attacks. Often you can land a couple of blows before they reach firing range, weakening them. This property also allows you to kite them provided they have no lancers or scythers supporting them.

=== Pikemen ===

[[{{Q|Pikeman|Image}}||100px|right]]

Introduced in 1.1, pikemen take over the lancer's role as snipers. Their extreme range is only matched by the [[sniper rifle]].

They have poor damage output, making them less threatening compared to other mechanoids. Their accuracy is also not appropriate for a sniping mech- equivalent to a level 8 shooter, it will more often than not miss at range.

As the description says, engaging pikemen at close range can be a viable way to take them down, once all others have been dealt with. Charging them can be risky due to the long distance pawns need to travel, but shield belts make the charge much safer, especially when you have multiple brawlers charging at once to divert concentrated fire. Swarming them with trained animals is also a viable strategy if you lack multiple skilled melee pawns or need them elsewhere.

=== Termites ===
[[{{Q|Termite|Image}}||100px|right]]

Spawning only in mechanoid breach raids, the [[termite]] is a dedicated anti-structure opponent. The termite's [[thump cannon]] can deal tremendous damage to your structures, and are able to destroy a three tile wide section of any [[wall]] weaker than [[plasteel]] in three shots or less. Against pawns, however, it is significantly less effective with lower damage, {{AP}}, and {{DPS}} than even the lowly [[short bow]].

Since they are so specialized in breaching walls, they cannot deal much damage to your pawns. However, killing them should be prioritized after [[scyther]]s, since they will destroy your pawn's [[cover]], exposing your pawns to danger from the termites much more directly dangerous companions.

=== Crashed ships ===

Mechanoids are also part of crashed ship events. In 1.1 they drop alongside the ship in pods, while in 1.0 or earlier they swarm out when the ship is damaged.

The type and where it lands are both important factors to consider when dealing with them.

Psychic parts will reduce mood and occasionally drive nearby animals mad, while defoliator parts (aka. poison ship parts in 1.0) will kill nearby plants and cause serious losses to pastures or crops. You cannot deconstruct the part, only destroy it.

Since they won't attack until triggered, you have some time to prepare. However, the longer you take, the worse it gets. If the defoliator ship part lands on the opposite side of your base at a map border, it is possible to leave it there, as they will also react to incoming raids and you may as well solve two problems at once. Not the same for the psychic version though.

If they land between your plantations, you will need to place firefoam poppers and trigger them before combat to prevent fires; the foam will persist until it rains, but then if it is rainy, you won't need the poppers. You may also want to keep a few untriggered poppers nearby to rapidly extinguish a group of burning colonists at once.

[[File:Crashed ship part using foam poppers.png|center|500px]]

==== Defense behavior ====

Mechanoids are triggered immediately when the part is damaged, or something is built within a three-tile radius. They may also be triggered by the Firefoam popper explosion.

Upon triggering, scythers will immediately charge to attack, while lancers, centipedes and pikemen may instead sit in place and attempt to shoot interlopers, only moving to get within range.

Afterwards, they will guard the ship part, engaging any hostiles that come close, and chasing them over short distances. They will return to the part if targets stray too far away from the ship.

In 1.0 mechanoids chased targets over long distances and abandoned the ship part when it is at 50% health.

==== Long-range engagement ====

In the current version, it is better to trigger the mechanoids from a distance, rather than fighting way up close. This is necessary such that you can weaken the scythers with concentrated fire before they reach melee engagement range, as well as give you more time to defeat the lancers before the centipedes move within range. Scythers are especially dangerous as they come in swarms and can quickly overwhelm your gunners, as well as overpower your melee brawlers unless you outnumber or outarm them.

You can trigger the mechanoids either by high-explosive mortar fire, or sniping the ship part.
*By attacking with sniper rifles at maximum range you will gain a good enough lead against the mechs to be able to escape safely even without enhancements unless armor is over-encumbering your colonists.
*Mortar volleys can soften the mechanoids, making them easier to defeat by your colonists afterwards. Mortars may also destroy the ship part itself, which both ends the threat and prevents the mechanoids from disengaging from an attack and returning to guard it (though this can be either good or bad depending on the state of your defenses).
*In 1.1 you can also use EMP to stun them before engaging, then retreat before they exit stun, which is 25 seconds after being hit by EMP.

==== Weapons ====

High-DPS weapons are optimal at destroying both the ship part and its defending mechanoids.

Due to the mechanoids spawning very close together, area of effect or crowd control weapons are punishing against them:
*The [[minigun]] is a powerful weapon here:
**It can make short work of the bunched-up mechanoids, then shred the ship part using its unparalleled raw DPS.
**Its already high DPS is further amplified when attacking centipedes as their large size makes it easier to land shots.
**Its long range allows you to attack from a safer distance.
*EMP mortar blasts are able to stun a large number of mechanoids caught in its blast. As the ship part blocks EMP pulses, fire several at once to hit all enemies with a single volley.
*Explosive weapons are useful for dealing damage, but keep in mind that the ship part will block the explosion. They do extra damage to the ship part.

Incendiary weapons are a poor choice for any situation involving mechanoids or crashed ships, given that both are non-flammable.

The [[orbital power beam targeter]] is the ultimate weapon against crashed ships. All you need to do is to aim the beam directly on the ship, and the beam will melt both the ship and its surrounding mechanoids.

==== Construction ====

{{main|Defense structures#Crashed ships}}

Construction is an important part of defeating the mechanoids in a crashed ship. Usually it is best if you can prepare ample cover, such as sandbags or walls, to shoot from.

Keep note that building within a three-tile distance will instantly trigger the mechanoids.

If done properly, [[IED trap]]s can be used to weaken a mechanoid swarm. Don't build too many or you will vaporize the mechanoid corpses, which can be deconstructed for resources.

==== Luring in ====

If you already have ample static defenses, like killboxes, and you want to lure the mechanoids in, you will need to make the mechanoids abandon the ship by destroying it from a long distance.

Previously in 1.0, you can lure the mechanoids simply by triggering at range.

==== Hit-and-run (1.1) ====

Their behavior change in 1.1 makes them vulnerable to hit-and-run tactics. After taking care of the scythers, you are able to chip away at the mechanoids slowly by shooting with sniper rifles at maximum range. If all pikemen are taken out then you are able to safely engage without fear of returning fire.

==== Zoning animals ====

When dealing with a crashed psychic ship part that has been there for some time, do not let any of your tamed animals near it, for the ship part can drive them into manhunter mode. This is additionally harmful as they are capable of opening doors to attack your colonists.

=== Mechanoid breach raids ===
Mechanoid of the breach raids will not ever walk through the kill box as you wanted them to, instead they will blast walls down and head straight for your base. Their path is usually aimed for the colonists' beds and most valuable destructible items such as expensive furniture, workshops, dining/recreational rooms etc. until your colony is completely destroyed or the mechs get killed.

It is recommended to have double outer walls around your base, empty space about 10-15 cells wide and the actual layer of inner defense like "wall, barricade, wall, barricade..." inside, when the mechs break in you can use EMP, melee rush tactic, bait and kite them in this "killzone" area with long ranged guns: Bolf-action riffles or/and Assault riffles. Never fight them in open field, they will outrange you!

It is worth considering the use of a [[Psychic shock lance|psychic shock]] or [[Psychic insanity lance|insanity lance]] to take down the [[termite]] from far away, as there will only be up to two termites per raid. Losing the use of the specialized anti-structure [[thump cannon]] will significantly delay the raid, as they will instead be forced to destroy walls in their path with their more traditional weaponry. This gives you time to prepare a defense behind that section of wall.

Typically this raid strategy will result in the mechanoids clumping up, giving a prime target for [[EMP grenades]] or a [[triple rocket launcher]], hopefully to devastating effect. Note the mechs will not attack colonists unless they come into the range of the mechanoid's gun. The long range of the triple rocket launcher is beneficial here, only putting the wielder in range of the [[pikeman|pikemen's]] needle gun.

= Infestations =

[[Infestation]]s will spawn under Overhead Mountains within 30 tiles of a colony [[structure]]. They can be a serious hazard in mountain bases due to the lack of free space to run away from with too many obstacles on the path, but not so much threat in open area (flat) maps. [[Insectoids]] are lightly armored, exclusively use melee and are slower than colonists. This gives them some protection against close range attacks, but leaves them vulnerable to ranged attacks and kiting tactics.

[[File:Infestation within mountain rooms bugs.png|400px]]

'''If you don't destroy them fast enough, they can reproduce, giving rise to even more hives and insects'''. This is especially true if you happen to have forgotten about a [[hive]], which given time can build itself into a giant mega-hive.

=== Behavior ===

Insects have a hive mindset; they will remain tending to their hive cluster, until they see an intruder, in which case they begin to engage all at once. They may also attack random furniture and structures in your colony.

=== Fighting infestations ===

The enclosed nature of mountain bases give colonists little distance to shoot from; thus, you may want some melee fighters to pair up with any ranged colonists.

Individual fighters will quickly get overwhelmed by the insects especially against large [[megaspider]]s, so you shouldn't trickle your defensive forces in; rather, send them all at once to overpower the insects.

=== Melee blocking ===

If there is a single choke point for the insects to get into your base (usually a door leading to a corridor), usage of this tactic allows you to defeat insects efficiently. You may even stand a chance against massive infestations if for some reason fire isn't viable, but don't get cocky. If the infestation is large you will need to bring backup tanks to replace the initial melee blocker if he or she gets downed or heavily injured.

Choke points can arise on their own from insects digging out; simply wait for them to tunnel through and massacre them once they exit.

This tactic is only viable if you have enough soldiers with ''substantial'' armor as insects inflict heavy sharp damage and will obliterate everybody not sufficiently protected.

=== Using fire ===

Fire is an effective way to clear early-mid stage infestations. If they spawn in an enclosed area with a door and plenty of flammables, all you need to do is to toss a molotov or shoot an [[incendiary launcher]] bolt into the room. The room will quickly catch fire, causing the temperature to rise fast, roasting the insects in it along with the hives.

The downside of this approach is that it makes it impossible to farm any insect meat or jelly from the infestation, because it will all burn, and it is usually too hot inside the spawn room to manually extinguish the fires to save the goods (unless there is a way to quickly vent the heat, which is usually not feasible to set up).

If there is a dedicated place in your base for infestations to spawn (see ''baiting'' below), it helps to have a few cheap wooden furniture items in that room, and maybe a few tiles of wooden floor. A great source of additional flammable material are tainted clothing items and desiccated animal bodies. Dusters and parkas have a lot of hitpoints, so they burn longer. These items are easy to get into the burn room simply by creating a stockpile with appropriate settings. A 3x3 stockpile should be more than enough to create enough heat to clear out any infestation. The fire created will usually last several hours, which is more than enough time to kill everything in the spawn room.

Separating the actual spawn room from the burn room with a wooden door makes it very easy for your colonists to start the fire without the insects attacking. The heat will spread into the spawn room regardless (and burn the wooden door).

Having a few flammable structures, such as cheap furniture) in the room is important, because the insects are stupid enough to attack these first when enraged from the fire, wasting time — instead of digging out of this trap.

It is possible to reach the temperature maximum of 2000 degrees celsius this way. Check the temperature in the spawn room before stepping in with any colonists, because they will very quickly collapse from heat stroke and possibly catch fire and die at these ludicrous temperatures.

The insects will rush for the exit of the burn room in a panic when they realize what is happening to them, and will quickly attempt to dig out to escape, so make sure the exit door is made of rock which is durable and nonflammable.

If there aren't any flammables around, you can still shoot the hives with fire weaponry. They will light aflame, along with the fuel puddles created on the ground.

As any items inside the room are likely to catch fire and be destroyed, this tactic is not recommended in a place with many valuables such as warehouses. Also be careful with the heat spreading to nearby rooms.

==== Heat stroke ====
By using a colonist to manually throw molotovs at the ground, either inside the bug room itself or in an adjacent room with an open doorway, you can maintain the temperature of the insect room between 150C and 200C, slowly knocking them unconscious and killing through heatstroke. As long as the temperature does not rise above 200C, the bugs will not get burn injuries, and therefore will not become aggressive. Have your colonist throw the molotovs through an open doorway in order to protect the colonist from the heat. When doing this, take care not to hit anything directly with the molotovs, as the fires created will anger the insects and set flammable objects on fire.

It is important to note when doing this to make sure that all bugs are significantly above the serious heat stroke threshhold (60%) before you move in, otherwise the temperature will start falling when you stop throwing molotovs and they may recover and attack your colonists.

=== Explosives ===

Explosives are useful against large infestations. The [[Triple rocket launcher]] can raze infestations instantly. A single use [[Doomsday rocket launcher]] will deal massive damage over a large area. [[Frag grenades]] are unlimited and work well if you have the courage to send someone to close range. One blast can get several insects. <br>
Explosive animals ([[boomalope]]s or [[boomrat]]s) are also effective at clearing out infestations. Have them march straight into the hive by zoning them there. When the insects attack, the animals will be injured and explode, setting the insects and hives on fire.

Mortars are useless against the hives themselves as they can't hit anything below an overhead mountain. However they are an option when fighting the insects in open space, with the explosions capable of severely injuring the insects, taking out the smaller ones in 1-2 hits.

=== Late-stage infestations ===

<gallery widths="500px" heights="400px" class="center" mode="nolines">
File:Infestation_ancient_shrine.png
</gallery>

If you've accidentally left a hive or two behind or totally ignored an infestation, after a few seasons you will have a giant hive community sprawling. This is '''extremely''' hard to treat, especially if you're low on colonists.

If you're still on early-midgame, it's generally recommended that you pack up and run. If not, however, you will have to deal with them slowly. You need to lure the insects out, then defeat them to buy time for others to enter and destroy the hives. Kiting is a possibility due to their slower speeds, provided they continue to chase down your colonists.

Explosives are recommended as they deal immense damage to the closely packed hives and insects. This is especially so with the doomsday rocket launcher, which can set entire infestations on fire, destroying the hives and severely weakening the insects.

=== Prevention ===

If you only have a few tiles of Overhead Mountain then it's best that you fill it up with walls to prevent any infestations from happening. If you are in a mountain base, then you will need to do more than that.

==== Baiting ====

You can mine out rooms a distance away from your colony to somehow control insects to nest there, instead of letting them spawn right in the middle of your base. Place some cheap flammable furniture inside to confuse the insects into thinking it's a prospective nesting spot, as well as to light on fire for a quick solution to an infestation problem. You may even use wooden walls or columns, which in a large enough room will cause a roof collapse and crush insects after being destroyed.

A well-lit base discourages insects from nesting, though it can still happen. If you bait insects to spawn elsewhere the chance of an infestation spawning inside is greatly reduced.

If you want the insect trap to automatically kill insects, put an [[IED incendiary trap]] inside the room, next to the flammables. Once an infestation spawns the insects will trigger the trap, lighting the room on fire and broiling the insects.

Alternatively, fill it with spike traps to weaken them before they strike your base, giving you the advantage. Doing this preserves the hives, which can be good if you want to farm insect jelly.

==== Deep freezing ====

An interesting way to completely prevent infestations is to simply set your base temperature below -17°C with coolers, and have everyone in the colony wear [[parka]]s.

This means that the 'Slept in the cold' debuff will be prevalent in the colony, however, so you will need something to offset the mood. It will also incur a work speed penalty on all production facilities due to low temperature, making this strategy not very viable on all but the lowest difficulties (where infestations are not a big threat in any case).

=== Deep drill infestations ===

Deep drills can unearth insect hives, which will result in enraged insects charging up to attack after a while.

When you see this happen, gather up your defense forces to fight the incoming insects. Have them approach your base where you can melee block them while evacuating other colonists so the insects don't go for them first. Nearby pets or other tamed animals will also be attacked; you can either evacuate them beforehand to reduce losses and ensure a successful melee blocking attack, or use them as bait to grab the insects' attention while your colonists lay fire on them.

Note that if you have a deep drill near the walls of a room it is possible for the insects to spawn outside the room.

= Prison breaks =
If you have prisoners (or potential colonists or hats) on hand, always expect them to break out any time. This is more so if you have many of them, each one ready to incite a riot whenever the guards aren't looking.

Escaping prisoners can open any colony door, and will snatch weapons whenever they see one.

=== Strategy ===
You should [[#body block|body block the prisoners]] with armored wardens carrying blunt weapons, or melee attacks with guns. They will fight and down the prisoners while blocking their exit, buying time for reinforcements.

Against already injured yet unarmed prisoners, send 1 brawler per prisoner to minimize the risk of beating them to death. <br>
For those at full health, 2 unarmed wardens or 1 skilled one can tackle a full-health unarmed prisoner without the wardens being downed in most cases.

Ranged wardens should attack when the prisoners are blocked by melee wardens so they can attack from a distance without much danger, and their weapons won't land in the enemy hands so easily. Don't fire too much at them as you risk permanent damage as well as accidentally killing the prisoner.

=== Weapons ===
You goal here isn't to kill the prisoners, it's to down them so you can recapture them.

*Blunt melee weapons such as the [[mace]] is a good choice for wardens to down escapees. The wounds don't bleed (unless you crush an internal organ or destroy a part entirely), nor will they be infected, giving them higher survival chances overall.
*At a distance, use low-moderate DPS weapons that won't deal too much damage to the prisoners, or to your people when the prisoners pick them up.
*Don't use high damage per hit weapons such as [[sniper rifle]]s or [[longsword]]s, as you risk instantly killing them or destroying an important part.

=== Turrets ===

Mini-turrets can be used as a form of distraction and supplementary firepower against prison breaks. Station them outside the prison doors, and they will fire on the escapees. They deliver decent firepower at short ranges, and leave no usable weapons on destruction. Prisoners also tend to stop to fight the turrets, giving wardens time to reach them.

1-3 are enough for most prisons. Don't put too many otherwise they may kill the prisoners before you can intervene.

{{Nav|guides|wide}}
[[Category:Guides]]

Void monolith

2026-04-25T00:15:04Z

Aelanna: /* Theoretical infinite energy generation */

{{Anomaly}}
{{Spoiler}}
{{Infobox main|entity
| name = Void monolith
| image = Void monolith.png
| description = A monolith of unknown age, purpose, and construction. Its smooth surface is etched with lines that twist and writhe in unsettling patterns.

| type = Entity
| type2 = Basic
| flammability = 0
| path cost = 50
| selectable = true
| destroyable = false
| uses hit points = false

| meditation psyfocus bonus = 0.3
| focus types = Void

| anomaly knowledge = 1
| knowledge category = Basic 
| study interval = 120000 
| min monolith level for study = 1
| show toggle gizmo = true
| study enabled by default = false

| passibility = impassable
| cover = 1
| blockswind = true
| terrain affordance = Heavy
| size = 3 x 3
| deconstructable = false
| repairable = false
| is targetable = false
| is inert = true
| claimable = false
| expand home area = false

| glowradius = 12
| glowcolor = (255,120,120,0)

| defName = VoidMonolith
| label = void monolith
}}
The '''void monolith''' is a structure that is the center point of the [[Anomaly DLC]]. It is used to enable in encounters with most [[entities]].

== Acquisition ==

The monolith appears on all new colony maps by default. If you have selected the "Ambient Horror" mode of the [[storyteller]] settings, the monolith '''will not be available'''.

If you choose the [[Scenario_system#The_Anomaly|Anomaly starting scenario]], the monolith will spawn right next to your crash landing spot, instead of its usual and distanced spot, allowing you to form a base around it easier.

If the monolith is enabled in storyteller settings, but there are no monolith on your maps for any reason (like move to a new map or add the DLC in the middle of another playthrough), you will receive a "Strange Signal" quest, which will spawn a monolith on your map when you accept it. The monolith's spawn point is random, and it may destroy existing structures when it arrives.
{{clear}}
== Summary ==
{{Stub|section=1|reason=Void focus mediation}}
[[File:Void Monolith Awakened Valid Meditation Spots.png|thumb|right|128px|Valid meditation spot positions for the Awakened monolith]]

The monolith is the first [[entity]] that the player will encounter. Initially dormant, the monolith goes through these stages of development:

{| class="wikitable"
|-
! Anomaly stage
! Monolith
! Size
! Level
! Effect
! Advancement
|-
| Inactive
| Fallen monolith<br>[[File:Void monolith.png|64px]]
| 3×3
|
| Encounter minimum amount of Anomaly incidents, includes shambler assault, psychic ritual siege, and creepjoiner arrival
| Investigate the monolith with a colonist, and choose to "Keep focusing" when you receive the warning dialog
|-
| Stirring
| Void monolith<br>[[File:Void monolith level 1.png|64px]]
| 5×3
| Level 1: Intermittent psychic humming
| Encounter a mix of basic and easier advanced [[entities]]. You will immediately experience a [[Events#Gray_pall|gray pall]] event, followed shortly by a [[sightstealer]] attack and a [[harbinger tree]] sprout
| Encounter '''7 [[Entities#Basic|basic entities]]''' (out of 8), and have a colonist attune to the monolith again when you are ready
|-
| Waking
| Void monolith<br>[[File:Void monolith level 2.png|64px]]
| 5×5{{ref label|Footprint|A}}
| Level 2: Pulsing with psychic energy
| All entity encounters possible, including the more-dangerous advanced entities
| Encounter '''12 [[Entities#Advanced|advanced entities]]''' (out of 17), and have a colonist attune to the monolith again when you are ready
|-
| VoidAwakened
| Void monolith<br>[[File:Void monolith level 3.png|64px]]
| 5×5{{ref label|Footprint|A}}
| Level 3: Awakening
| The monolith is awakening for the [[Endings#The Void|end of the quest]]
| Active a total of 5 [[void structure]]s and wait until the monolith awakens
|-
| Gleaming
| Void monolith<br>[[File:Void monolith level 4.png|64px]]
| 5×5{{ref label|Footprint|A}}
| Level 4: Awakened
| The monolith is awakened and opens a portal to the metal hell, leading to the end of the quest
| Enter the [[metal hell]] and interact the [[void node]], reaching the chosen [[ending]]
|-
| Embraced
| Void monolith<br>[[File:Void monolith level 3.png|64px]]
| 5×5{{ref label|Footprint|A}}
| Level 4: Awakened
| The monolith is awakened as the pawn has embraced the void, dangerous Anomaly events will continue to occur
| —
|-
| Disrupted
| Collapsed monolith<br>[[File:Void monolith collapsed.png|64px]]
| 3×3
|
| Random Anomaly events return to the same level as an inactive (level 0) monolith
| —
|}

:{{note|Footprint|A}} The 5×5 monolith is not regular in shape, the five tiles that appear empty are indeed empty and can be walked on and built on as normal.

These stages are saved in the world; losing the monolith and getting the "Strange Signal" quest spawns a monolith of the same level.

The monolith must be attuned or investigated after each step to advance, allowing you to decide when to progress. If you chose the [[Scenario_system#The_Anomaly|Anomaly starting scenario]], the monolith will ''automatically'' move to Level 1 on its own a few days after you begin the game.

The monolith can be [[work|studied]] every two days as a source of either basic or advanced Anomaly tech tree research points.

The monolith separates rooms and provides total cover (like a wall), and it is invulnerable to all damage and fire. [[Raiders]] will ignore the monolith. When the monolith expands in size, it will uninstall, deconstruct or destroy any structures in the way.

Depending on which path you select during the [[Monolith endgame|Anomaly ending quest]], the monolith will either be permanently closed or permanently locked at level 4. In either case, it can still be studied indefinitely for advanced research points.

== Analysis ==
{{For|dealing with the monlith awakening at level 3|monolith endgame}}

The monolith is your only permanent source of Anomaly research points. However once the monolith study has been completed, you can research captured entities instead to avoid having to travel to the monolith. Studying the monolith or entities is done through the "Dark Study" job on the [[work|Work tab]].

You may want to build your base near the monolith to reduce the travelling time to it.

=== Meditation ===
The void monolith is the best Void [[meditation focus]],{{RoyaltyIcon}} although it cannot be moved and only has three tiles to place [[meditation spot]]s in.

===Theoretical infinite energy generation===
By placing power generators near the left or right side of the monolith, and power conduits adjacent to the left or rightmost side of the power generator. And activatting the monolith, one can achieve infinite power, in addition to that. The full cost of the generator in resources will also be returned. The power still remains in the network and can be used by various appliances, however the phantom power generators will disappear as soon as the power network is updated in any way, either by adding or removing buildings including conduits. This is almost certainly a bug.

== Version history ==
* [[Anomaly DLC]] Release - Added.
* 1.5.4081 — Ambient Horror mode, and monoliths spawned via the dev commands now work correctly

{{Nav|entity|wide}}
[[Category:Entities]]

Void monolith

2026-04-25T00:13:46Z

Aelanna: /* Theoretical infinite energy generation */

{{Anomaly}}
{{Spoiler}}
{{Infobox main|entity
| name = Void monolith
| image = Void monolith.png
| description = A monolith of unknown age, purpose, and construction. Its smooth surface is etched with lines that twist and writhe in unsettling patterns.

| type = Entity
| type2 = Basic
| flammability = 0
| path cost = 50
| selectable = true
| destroyable = false
| uses hit points = false

| meditation psyfocus bonus = 0.3
| focus types = Void

| anomaly knowledge = 1
| knowledge category = Basic 
| study interval = 120000 
| min monolith level for study = 1
| show toggle gizmo = true
| study enabled by default = false

| passibility = impassable
| cover = 1
| blockswind = true
| terrain affordance = Heavy
| size = 3 x 3
| deconstructable = false
| repairable = false
| is targetable = false
| is inert = true
| claimable = false
| expand home area = false

| glowradius = 12
| glowcolor = (255,120,120,0)

| defName = VoidMonolith
| label = void monolith
}}
The '''void monolith''' is a structure that is the center point of the [[Anomaly DLC]]. It is used to enable in encounters with most [[entities]].

== Acquisition ==

The monolith appears on all new colony maps by default. If you have selected the "Ambient Horror" mode of the [[storyteller]] settings, the monolith '''will not be available'''.

If you choose the [[Scenario_system#The_Anomaly|Anomaly starting scenario]], the monolith will spawn right next to your crash landing spot, instead of its usual and distanced spot, allowing you to form a base around it easier.

If the monolith is enabled in storyteller settings, but there are no monolith on your maps for any reason (like move to a new map or add the DLC in the middle of another playthrough), you will receive a "Strange Signal" quest, which will spawn a monolith on your map when you accept it. The monolith's spawn point is random, and it may destroy existing structures when it arrives.
{{clear}}
== Summary ==
{{Stub|section=1|reason=Void focus mediation}}
[[File:Void Monolith Awakened Valid Meditation Spots.png|thumb|right|128px|Valid meditation spot positions for the Awakened monolith]]

The monolith is the first [[entity]] that the player will encounter. Initially dormant, the monolith goes through these stages of development:

{| class="wikitable"
|-
! Anomaly stage
! Monolith
! Size
! Level
! Effect
! Advancement
|-
| Inactive
| Fallen monolith<br>[[File:Void monolith.png|64px]]
| 3×3
|
| Encounter minimum amount of Anomaly incidents, includes shambler assault, psychic ritual siege, and creepjoiner arrival
| Investigate the monolith with a colonist, and choose to "Keep focusing" when you receive the warning dialog
|-
| Stirring
| Void monolith<br>[[File:Void monolith level 1.png|64px]]
| 5×3
| Level 1: Intermittent psychic humming
| Encounter a mix of basic and easier advanced [[entities]]. You will immediately experience a [[Events#Gray_pall|gray pall]] event, followed shortly by a [[sightstealer]] attack and a [[harbinger tree]] sprout
| Encounter '''7 [[Entities#Basic|basic entities]]''' (out of 8), and have a colonist attune to the monolith again when you are ready
|-
| Waking
| Void monolith<br>[[File:Void monolith level 2.png|64px]]
| 5×5{{ref label|Footprint|A}}
| Level 2: Pulsing with psychic energy
| All entity encounters possible, including the more-dangerous advanced entities
| Encounter '''12 [[Entities#Advanced|advanced entities]]''' (out of 17), and have a colonist attune to the monolith again when you are ready
|-
| VoidAwakened
| Void monolith<br>[[File:Void monolith level 3.png|64px]]
| 5×5{{ref label|Footprint|A}}
| Level 3: Awakening
| The monolith is awakening for the [[Endings#The Void|end of the quest]]
| Active a total of 5 [[void structure]]s and wait until the monolith awakens
|-
| Gleaming
| Void monolith<br>[[File:Void monolith level 4.png|64px]]
| 5×5{{ref label|Footprint|A}}
| Level 4: Awakened
| The monolith is awakened and opens a portal to the metal hell, leading to the end of the quest
| Enter the [[metal hell]] and interact the [[void node]], reaching the chosen [[ending]]
|-
| Embraced
| Void monolith<br>[[File:Void monolith level 3.png|64px]]
| 5×5{{ref label|Footprint|A}}
| Level 4: Awakened
| The monolith is awakened as the pawn has embraced the void, dangerous Anomaly events will continue to occur
| —
|-
| Disrupted
| Collapsed monolith<br>[[File:Void monolith collapsed.png|64px]]
| 3×3
|
| Random Anomaly events return to the same level as an inactive (level 0) monolith
| —
|}

:{{note|Footprint|A}} The 5×5 monolith is not regular in shape, the five tiles that appear empty are indeed empty and can be walked on and built on as normal.

These stages are saved in the world; losing the monolith and getting the "Strange Signal" quest spawns a monolith of the same level.

The monolith must be attuned or investigated after each step to advance, allowing you to decide when to progress. If you chose the [[Scenario_system#The_Anomaly|Anomaly starting scenario]], the monolith will ''automatically'' move to Level 1 on its own a few days after you begin the game.

The monolith can be [[work|studied]] every two days as a source of either basic or advanced Anomaly tech tree research points.

The monolith separates rooms and provides total cover (like a wall), and it is invulnerable to all damage and fire. [[Raiders]] will ignore the monolith. When the monolith expands in size, it will uninstall, deconstruct or destroy any structures in the way.

Depending on which path you select during the [[Monolith endgame|Anomaly ending quest]], the monolith will either be permanently closed or permanently locked at level 4. In either case, it can still be studied indefinitely for advanced research points.

== Analysis ==
{{For|dealing with the monlith awakening at level 3|monolith endgame}}

The monolith is your only permanent source of Anomaly research points. However once the monolith study has been completed, you can research captured entities instead to avoid having to travel to the monolith. Studying the monolith or entities is done through the "Dark Study" job on the [[work|Work tab]].

You may want to build your base near the monolith to reduce the travelling time to it.

=== Meditation ===
The void monolith is the best Void [[meditation focus]],{{RoyaltyIcon}} although it cannot be moved and only has three tiles to place [[meditation spot]]s in.

===Theoretical infinite energy generation===
By placing power generators near the left or right side of the monolith, and power conduits adjacent to the left or rightmost side of the power generator. And activatting the monolith, one can achieve infinite power, in addition to that. The full cost of the generator in resources will also be returned. The power still remains in the network and can be used by various appliances. This is almost certainly a bug.

== Version history ==
* [[Anomaly DLC]] Release - Added.
* 1.5.4081 — Ambient Horror mode, and monoliths spawned via the dev commands now work correctly

{{Nav|entity|wide}}
[[Category:Entities]]

Human meat

2026-03-26T20:48:53Z

Aelanna: Gorehulks drop twisted meat, not human meat.

{{See also|Meat (disambiguation)|Meat|Insect meat}}
{{Infobox main|food
| name = Human meat
| image = Meat human c.png
| description = Raw butchered flesh. Can be cooked into meals or eaten raw, although most humans dislike the idea.

| type = Food
| type2 = Raw food
| hp = 60
| deterioration = 6
| marketvalue = 0.8
| beauty = -4
| mass base = 0.03
| flammability = 0.5

| taste = Raw
| food poison chance = 0.02
| days to rot = 2
| nutrition = 0.05

| production facility 1 = Butcher spot
| production facility 2 = Butcher table
| work to make = 450
| work speed stat = Butchery Speed
}}
'''Human meat''' is [[meat]] obtained when a [[Work#Cook|cook]] butchers [[human]]s.

== Acquisition ==
Human meat is obtained when a [[Work#Cook|cook]] butchers [[human]]s. The base [[Meat Amount|Meat Yield]] are described on the table below but the actual number depends on the [[Butchery Efficiency]] of the butcher, damage of the corpse, and a number of other factors.

<div><li style="display: inline-table;">
{| {{STDT| sortable c_06 text-center}}
! Animal !! Meat Yield
|-
{{#ask: [[Meat Name::{{PAGENAME}}]] [[:+]]
| ?Meat Yield
| format = template
| template = Ask Table Formatter
| limit = 500
| link = none
| sort= From DLC, name}}
|}</li></div>

Without the [[Ideology DLC]], butchering a human gives {{--|6}} [[mood]] for all colonists in the colony, and an additional {{--|6}} to the butcher. The former moodlet does not stack, meaning butchering 100 corpses gives the same colony-wide mood as one (the butcher's penalty ''does'' stack). [[Psychopath]]s and pawns with [[bloodlust]] ignore either butchering penalty, as do any [[cannibal]]s.

The mood effects of butchering humans with an [[Ideoligion]]{{IdeologyIcon}} are based on the precept of the ideoligion the pawn follows.

== Usage ==
{{Ingredient List|noCollapse=true}}

== Summary ==
As a [[raw food]], human meat can be be eaten raw, with a flat {{Bad|2%}} chance of giving [[food poisoning]], or cooked into a [[meal]] with a food poisoning chance dependent on the skill of the cook and the [[cleanliness]] of the kitchen. [[Animals]] are immune to food poisoning from raw food but not from meals. When used in food recipes that require specific types of [[nutrition]], such as [[fine meal]]s, human meat are classified as meat.

Human meat is like any other [[raw food]]. It can be used to create [[meal]]s, or combined with other ingredients to produce fine, lavish meals, pemmican and kibble.

Most humans despise eating human meat, which is cannibalism. Raw human meat gives {{Thought|value=-20|stack=1|label=raw cannibalism|desc=I ate the meat of another human, raw, like an animal. This is a nightmare.|duration=1}}, and cooking human meat into [[meal]]s (including in [[nutrient paste meal|nutrient paste]]) gives {{Thought|value=-15|stack=1|label=cooked cannibalism|desc=I ate a meal made from the meat of another human. This is horrible.|duration=1}}. Pawns with the [[Cannibal (Trait)|Cannibal]] trait instead gain {{Thought|value=+20|stack=1|label=raw cannibalism|desc=I ate the meat of another human, raw, like an animal. It was so... succulent.|duration=1}} for raw human meat and {{Thought|value=+15|stack=1|label=cooked cannibalism|desc=I ate a meal made from the meat of another human. So pleasurable. If only I had some fava beans and a nice chianti.|duration=1}} for cooked human meat. The moodlets for raw and cooked cannibalism stack with each other, as do any moodlets from meal types.

Depending on the [[Ideoligion#Cannibalism|canibalism precept]] {{IdeologyIcon}} colonists gain instead:
* Cannibalism abhorrent: {{Thought|value=-20|stack=1|label=ate human meat|desc=I had to eat human meat. This is an offense against everything I believe.|duration=1}}
* Cannibalism horrible: {{Thought|value=-12|stack=1|label=ate human meat|desc=I had to eat human meat. This was a horrible thing.|duration=1}}
* Cannibalism dissapproved: {{Thought|value=-5|stack=1|label=ate human meat|desc=I had to eat human meat. I believe such actions are wrong.|duration=1}}
* Cannibalism acceptable: ''none''
* Cannibalism preferred: {{Thought|value=+2|stack=1|label=ate human meat|desc=I ate human meat. It makes me feel noble and strong.|duration=1}}
* Cannibalism required (strong): {{Thought|value=+4|stack=1|label=ate human meat|desc=I ate human meat, as every real human should.|duration=1}}
* Cannibalism required (ravenous): {{Thought|value=+6|stack=1|label=ate human meat|desc=I ate human meat! The world is right, and I am as I should be.|duration=1}}

Processing human meat, once it has been butchered, incurs no penalties. Human meat can be made into meals, used for animal feed, processed in [[biofuel refinery]] for [[chemfuel]], or put in a [[biosculpter pod]]{{IdeologyIcon}} or [[growth vat]]{{BiotechIcon}}, and nobody will feel bad about it unless it is eaten directly.

When consumed by [[Hemogenic]]{{BiotechIcon}} pawns, human meat satisfies the [[Hemogen]]{{BiotechIcon}} need by {{+|3.75}} per 1 [[nutrition]], or {{Icon Small|Human meat||{{#expr:1/{{P|Nutrition}}}}}}, consumed.{{Check Tag|Rounding?|This rounds to +4 for 20 meat, exact rounding mechanics needed}}. Note that only the raw meat provides this hemogen, eating [[corpse]]s or the meat cooked into [[meals]] does not.

Its market value is only {{Icon Small|silver||{{P|Market Value Base}}}} [[silver]], or {{%|{{P|Market Value Base}}/{{Q|Meat|Market Value Base}}|0}} of regular meat. However, processing it into meals or [[chemfuel]] will ignore its origin when considering market value.

Human meat is also used as a building ingredient for the [[cannibal platter]]{{IdeologyIcon}}, which requires {{Required Resources|Cannibal platter|simple=1}}.

== Analysis ==
Butchering a human is already upsetting for a good majority of colonists. So in a colony not filled with cannibals, eating it should only be for absolute emergencies, in extreme [[biome]]s like sea ice, or to please a cannibal on verge of [[mental break]]. For a cannibal, both the cooked cannibalism and raw cannibalism mood buffs stack, for a total of {{+|35}} mood. However, most cannibals still get {{Thought|value=-7|stack=1|label=ate raw food|desc=I had to eat raw food. We should be cooking that kind of food before eating it. We're not animals.|duration=1}}. You can further boost mood with [[fine meal]]s, [[lavish meal]]s, or their [[carnivore fine meal|carnivore]] [[carnivore lavish meal|variant]]s. Alternatively, the massive mood debuff might make human meat situationally useful. It may force a [[tortured artist]] into a mental break, or cause a [[Crisis of belief]] in the [[Ideology DLC]]. As for [[Caravan]]s and Raiding, Human Meat is one of the most abundant food sources that can be acquired while on-site by butchering several of the corpses found from the pawns killed and in [[Gibbet cage]]s {{IdeologyIcon}}, cooking them into Meals for slower spoilage.

Using human meat for carnivorous animals (whenever raw or [[kibble]]) isn't cannibalism, so the animals won't mind. It may be wiser to leave corpses unbutchered, as the butchering itself has a fairly large penalty to both the butcher and the colony. Note that colonists in base game or with the [[Ideoligion#Corpses|Corpses ugly]] precept {{IdeologyIcon}} will get {{--|4}} mood from observing them.

In the [[Ideology DLC]], a colony's [[ideoligion]] can make this a different story. With the Cannibalism meme and/or precept, [[raider]]s become a completely viable source of both food and positive moodlets. Setting the precept to Required (Ravenous) gives the greatest mood buffs, +6 per meal, but also gives a strong debuff when human meat isn't available. This is also possible in the base game, with a colony entirely composed of the cannibal trait. By adjusting the [[scenario]] ("Forced trait"), you can set all starting colonists, or every pawn in the game, to be cannibals.

== Gallery ==
<gallery>
Meat human a.png|One human meat
Meat human b.png|Partial stack
Meat human c.png|Full stack
</gallery>

== Version history ==
<gallery>
Meat human old.png|Old texture
</gallery>

{{Nav|Food|wide}}
[[Category:Food]] [[Category:Raw Food]] [[Category:Meat]]

Legionary

2026-03-14T20:50:56Z

Aelanna: Cleaning up added section.

{{Biotech}}
{{See also|Centurion}}
{{infobox main|none|
| name = Legionary
| image = LegionaryAncient east.png
| description = A combat support mechanoid with a wide-range bullet shield and mid-range needle gun. Designed to support other mechanoids, the legionary is vulnerable to anyone who can get inside its shield.
| combatPower = 150
| type = Mechanoid
| movespeed = 4.3
| flammability = 0
| marketvalue = 1200
| armorblunt = 20
| armorsharp = 40
| armorheat = 200
| min comfortable temperature = -100
| max comfortable temperature = 250
| psychic sensitivity = 0.5
| toxic resistance = 1
| toxic environment resistance = 1
| bandwidth cost = 2
| bodysize = 1
| healthscale = 0.72
| lifespan =
| attack1dmg = 12
| attack1type = Blunt
| attack1cool = 2
| attack1part = left fist
| attack2dmg = 12
| attack2type = Blunt
| attack2cool = 2
| attack2part = right fist
| attack3dmg = 8.5
| attack3type = Blunt
| attack3cool = 2
| attack3part = head
| attack3chancefactor = 0.2
| page verified for version = 1.4.3525
| weaponTags = MechanoidGunNeedleLauncher

| research = Ultra mechtech
| production facility 1 = Large mech gestator
| gestation cycles = 4
| resource 1 = Plasteel
| resource 1 amount = 100
| resource 2 = Component
| resource 2 amount = 6
| resource 3 = High subcore
| resource 3 amount = 1
}}
A '''legionary''' is a [[mechanoids|mechanoid]] added by the [[Biotech DLC]] that projects a shield.

== Acquisition ==
{{Acquisition}}

Dead, friendly {{lc:{{PAGENAME}}}}s can also be resurrected at the {{lc:{{P|Production Facility 1}}}} using the "''Resurrect medium mechanoid''" bill. This requires the corpse of the friendly {{PAGENAME}}, {{Icon Small|Steel||50}} [[steel]], and 1 [[gestation cycle]] taking {{ticks|1800}} to initiate.

== Summary ==
{{Mechanoid Summary}}

Dead legionaries may be shredded at the [[machining table]] or [[crafting spot]] for {{Icon Small|Steel||15}} [[steel]]. However, these values are affected by [[Mechanoid Shredding Efficiency|mechanoid shredding efficiency]], as well as missing parts on the legionary.

=== Shield ===
[[File:Legionary shield radius.png|thumb|left|175px|Radius of the legionary's shield with unshielded area denoted in red, partially shielded areas in gold (see Note right).<br> Note that despite the shield visually extends into the red tiles, it does not protect them.]]

The legionary projects a shield that is 3 tiles in radius, centered on the mech and moving with it, and which is visible whenever drafted or attacked. The shield stops all incoming enemy ground-level fire from passing into the bubble. It does not prevent pawns of any faction that are inside from firing out. Also note that this only applies to ground-level fire, i.e. fire from ranged [[weapons]] carried by all types of [[pawn]] and [[turrets]], including grenades that cross the boundary of the shield. Explosives projectiles will detonate on the shield edge. Fire from [[mortar]]s, [[orbital bombardment targeter|orbital bombardment]], or [[Titles#Permits|aerodrone strikes or salvos]] {{RoyaltyIcon}} will not be blocked by the shield, nor will explosions crossing the boundary.

'''Note:''' Pawns on the tiles shown in [[gold tile|gold]] in the image to the left are shielded from attacks directly targeted at them, however, due to a bug, they can still be hit by attacks aimed at other nearby pawns that miss.

The shield can absorb up to 200 damage before breaking. If an attack would be sufficient to completely deplete the shield's charge, then the rest of its damage is negated, and the shield is temporarily broken.  The shield regenerates charge at rate of 0.25 HP per second, so long as it has not been broken. However, once the shield's charge is completely expended, the shield will break and be totally disabled for {{ticks|5400}} after which point the shield will be restored at full health. Projectiles from [[EMP grenades]] and [[EMP launcher|launchers]] from outside hitting the shield will disable the shield for {{ticks|1500}}, after which time the shield will be restored at full health. Note that {{Hover title|Version/1.6.4630|as of the time of writing}}, projectiles [[unique weapons]] with the [[EMP rounds]]{{OdysseyIcon}} trait do not disable the shield when striking it. It is currently unknown whether this is intended or considered a bug. It is also currently unknown if striking the mechanoid itself disables the shield.{{Check Tag|Verify}} Furthermore, unlike the mechanoid itself, the shield projector will not adapt to the EMP effect. Its therefore possible to continuously disable the shield until the mechanoid can be killed. Note that an EMP area of effect overlapping with the projected shield will not disable it - a projectile must hit the shield or the EMP damage must be dealt to the structure itself

If the [[EMP]] damage is dealt to the legionary itself, the shield is similarly disabled for {{ticks|1500}}, but will continue to regenerate as if it was not.

A pawn does not need to be inside the shield to benefit from the effect, assuming the enemy is not inside the shield and that the shield is between them and their attacker the incoming rounds will be stopped. However, it does not prevent pawns from moving inside the shield and attacking.

=== As an ally ===
Mechs under player control require power: legionaries use 10% of their power per day while active. If set to dormant self-charging, they instead recharge for 1% power / day, without pollution. They recharge in a [[large mech recharger]] (400W), for 50% power/day, creating 10 [[wastepack]]s whenever the recharger's waste is filled up.

=== Combat ===
Legionaries are always equipped with a [[needle launcher]], which they do not drop upon death. See the [[needle launcher]] page for further information.

Legionaries have a [[shooting accuracy]] of 96%, equivalent to a pawn with a [[Shooting]] skill of 8. They have a [[melee hit chance]] of 62%, equivalent to a pawn with a [[Melee]] skill of 4.

== Analysis ==
{{Stub|section=1|reason=Needs at least comparison to Centurion for mechanitors choosing a shield mech, but also there's strategies for using the shield, distribution on a firing line, lillboz design, and moee esoteric like square packing legionaries and letting them go wild in a walled tile to make a shield wall etc}}
=== As an enemy ===
* The launcher is weak, but don't underestimate it. It's still strong enough to destroy vulnerable organs, including the brain.
* EMP works well to break the shield, if you can get close enough at all. Legionaries are often surrounded by powerful mechanoids due to their advanced nature.

===As an ally===
The Legionary's shield provides a safe space for your ranged pawns to attack the enemy without worrying about retaliatory fire. With 200 hitpoints, slow firing weapons like pila, sniper rifles, and charge lances will no longer trouble your pawns as their slow fire rate gives the shield a bit of time to regenerate. However, care should still be utilized when relying on its shield. Exposure to rapid-fire weapons like miniguns or heavy charge blasters (both found on Centipedes) can shred the shield extremely fast.

As a projected momentum repulsor field, the Legionary's shield is vulnerable to EMP, so try to take out enemies who wield EMP grenades or launchers first.

===Comparison===
When compared to [[centurion]]s, legionaries are cheaper to build as they do not require advanced components or powerfocus chips, only use 2 bandwidth instead of 5, but also have a smaller and weaker shield. When using a lot of higher-tier mechs such as [[centipede]]s it is more resource efficient to make one or two legionaries to defend them rather than a single centurion. However, a centurion provides higher shield coverage and lets you cram more mechs into the same shield.

== Health ==
=== Body parts ===
{{Animal Health Table|Lancer}}
=== Armor ===
{| class="wikitable"
! Armor
|-
| {{Apparel Protection Chart
| set1name= {{P|Name}} (Sharp) | set1armor1={{P|Armor - Sharp}}
| set2name= {{P|Name}} (Blunt) | set2armor1={{P|Armor - Blunt}}
| set3name= {{P|Name}} (Heat) | set3armor1={{P|Armor - Heat}}
| color= grey, blue, red
}}
|}
{{Pawn Attack Table|weapon=Needle launcher}}

== Trivia ==
Both shield mechanoids, the centurion and the legionary, are named after positions in the ancient Roman Army. The Roman Army famously used large shields called scuta.

== Gallery ==
<gallery>
Legionary east.png| Age 0-99 Legionary facing east
Legionary north.png| Age 0-99 Legionary facing north
Legionary south.png| Age 0-99 Legionary facing south
</gallery><gallery>
LegionaryAncient east.png| Age 100+ Legionary facing east
LegionaryAncient north.png| Age 100+ Legionary facing north
LegionaryAncient south.png| Age 100+ Legionary facing south
</gallery>

== Version history ==
* [[Biotech DLC]] Release - Added.
* [[Version/1.4.3555|1.4.3555]] - Weapon changed from needle gun to needle launcher.
* ? - Description changed to reflect change from needle gun to needle launcher. ''A combat support mechanoid with a wide range bullet shield and long-range needle gun. Designed to support other mechanoids from long range, the legionary is vulnerable to anyone who can get inside its shield.'' -> ''A combat support mechanoid with a wide-range bullet shield and mid-range needle gun. Designed to support other mechanoids, the legionary is vulnerable to anyone who can get inside its shield''
* [[Version/1.4.3682|1.4.3682]] - Fix: Missing final period in legionary description.

{{nav|mechanoid|wide}}
[[Category:Mechanoids]]