Terrain Conditional Stat Affecter - KonradHeinser/EBSGFramework GitHub Wiki
This gene conditional stat affecter causes the gene to have certain impacts when the pawn is standing in certain terrains. This can be added multiple times to the same gene to create more variance:
<conditionalStatAffecters>
<li Class="EBSGFramework.ConditionalStatAffecter_Terrain">
<statFactors>
</statFactors>
<statOffsets>
</statOffsets>
</li>
</conditionalStatAffecters>
Unlike most conditionals, this does not have default checks, so you'll have to set them up within the li:
- anyWater : Default (False) : Causes this to be active whenever the pawn is standing in any non-hated water terrain. If both this and anyNonWater remain False then only the terrains list determines if this is active
- anyNonWater : Default (False) : Causes this to be active whenever the pawn is standing in any non-hated non-water terrain. If both this and anyNonWater remain False then only the terrains list determines if this is active
- terrains : A list of TerrainDefs to check for. Whether this causes the condition to become active or not is based on hateTerrains
- hateTerrains : Default (False) : This changes what occurs when the pawn is standing on one of the listed terrains. If it remains False, then the conditional will be active when the pawn is standing on one of the terrains or meets the anyWater/anyNonWater condition if one of those is true. When True, the conditional will only be active when the pawn is not standing on one of the listed terrains and meets the anyWater/anyNonWater condition if one of those is true
- This set up makes it easier to utilize anyWater and anyNonWater. When hateTerrains is False while you have anyWater set to True, you only need to list non-water TerrainDefs because any water terrains will be automatically included in the list. If hateTerrains is True while you're using anyWater, then you can list any water TerrainDefs that you don't want included to limit what is allowed
- label : Default (Varies) : It is recommended to use this if you're using the terrains tag because while there are defaults set up for it, they are generic and make assumptions that have a 50% chance of being wrong
Important Note: If you're looking to include certain lands and exclude certain waters (or the reverse), you may need to instead only use the terrains tag to list all the lands and waters you want to have allowed to minimize the risk of unexpected things occurring. The terrains list will be much longer this way, but will also be more controlled