Install Steam
login
|
language
简体中文 (Simplified Chinese)
繁體中文 (Traditional Chinese)
日本語 (Japanese)
한국어 (Korean)
ไทย (Thai)
Български (Bulgarian)
Čeština (Czech)
Dansk (Danish)
Deutsch (German)
Español - España (Spanish - Spain)
Español - Latinoamérica (Spanish - Latin America)
Ελληνικά (Greek)
Français (French)
Italiano (Italian)
Bahasa Indonesia (Indonesian)
Magyar (Hungarian)
Nederlands (Dutch)
Norsk (Norwegian)
Polski (Polish)
Português (Portuguese - Portugal)
Português - Brasil (Portuguese - Brazil)
Română (Romanian)
Русский (Russian)
Suomi (Finnish)
Svenska (Swedish)
Türkçe (Turkish)
Tiếng Việt (Vietnamese)
Українська (Ukrainian)
Report a translation problem
*\Steam\steamapps\common\RimWorld\Mods\Core\Defs\Storyteller\Storytellers.xml
The general idea is roughly the same though so I'll explain some of them. These are the B18 values, I don't have b19 loaded and it's in such a state of flux it wouldn't be worth going through currently.
<populationIntentFromPopCurve>
<points>
<li>0, 8</li>
<li>1, 4</li>
<li>5, 1</li>
<li>9, 0.5</li>
<li>13, 0</li>
<li>18, -1</li>
</points>
</populationIntentFromPopCurve>
For population there is a scaling system that determines how easy it is to get new colonists. In the newer versions it's a curve rather than having the desired population values. At very low population the storyteller will create more "free colonist" events like wanderers joining or escape pods crashing down, as population increases those events become much less frequent. Once population hits 13 then those free pop the free colonist events stop and you have to recruit prisoners to gain more population. As population rises further and hits 18 and beyond, the chance for downing raiders instead of killing them decreases and the chance to recruit them drops until they are all 99%.
threatCycleLength no longer exists and I'm not sure exactly what it did before.
<threatOffDays>6.0</threatOffDays>
<threatOnDays>4.6</threatOnDays>
These are the values that replaced threatCycleLength I believe, but they have no obvious function.
<mtbDaysThreatSmall>3.75</mtbDaysThreatSmall>
<mtbDaysThreatBig>1.20</mtbDaysThreatBig>
mtb = mean time between
It means on average every 3.75 days a small threat will happen. A small threat is single animal insanity, a big threat is a raid, infestation, crashed ship chunk, manhunter pack ,or mass animal insanity.
<minDaysBetweenThreatBigs>1.9</minDaysBetweenThreatBigs>
This does what it says, it's minimum days between big threats. Yes the average is lower than the mininum, I don't know why. It means Casandra sends big threats at you like clockwork though, almost every 2 days.
Randy works very differently. He doesn't break down events into different categories and send them at you individually, instead he has a single pool of all events and pulls at them randomly based on a weight.
<mtbDays>1.13</mtbDays>
So every 1.13 days on a average he picks an event from the following list:
<Misc>5.5</Misc>
<OrbitalVisitor>1</OrbitalVisitor>
<ThreatBig>1</ThreatBig>
<ThreatSmall>0.9</ThreatSmall>
<AllyArrival>1</AllyArrival>
<AllyAssistance>0.5</AllyAssistance>
<ShipChunkDrop>0.5</ShipChunkDrop>
The numbers are the weights, so he has roughly a 50% chance to create a misc event and a 10% chance to create a big threat event. Then he has the following value:
<maxThreatBigIntervalDays>13</maxThreatBigIntervalDays>
This is the opposite of what casandra and phoebe have, instead of a minimum interval between big threats he has a max interval, because with a 10% chance per day it's possible to go a long time without creating a big threat. That value makes it so if no big threat is created after 13 days the game will try to force one, but it can be blocked if it's an invalid threat type (like an infestation with no viable spawn locations).
Very helpful information Astasia
Thank you for taking the time to post what you know. I have a feeling that the parameters you're not sure about must be staring you in your eyes, and making you wonder "what are you thinking Mr Data" ... It would bother me, that's for sure ... :)
I was unaware of the overhaul in b18/19 I'll have a look at the file myself also. However thank you greatly for the clearly constructed breakdown of the data. I appreciate it.