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
That doesn't sound like just a cap increase — looks like it's affecting the actual chance too, or something isn’t calculating correctly. Definitely feels off.
You just gained chance levels from somewhere at the same time. It does not raise the chance.
I thought that too at first, but nothing else changed — no new chance upgrades, no perks, nothing else added. I was watching it closely because the value looked suspiciously low.
The moment I put that one extra point into the cap upgrade, the prisoner chance jumped from 0.0016% to 0.0066% instantly. That’s not just a cap raise — that’s the actual value increasing. Unless there’s some hidden interaction I missed, it really seems like this upgrade is affecting more than just the cap.
Has anyone else seen the same behavior?
Maybe! That very well might have been the case — I can’t say for sure. But the chance % did go up by the exact cap margin right after I put that point into it. Could just be a huge coincidence, but it definitely looked suspicious in the moment.
I assume thats what Soehnie meant.
What difficulty are you in? easy to normal causes a catastrophic drop in prisoner rescue chance.
Just to reiterate, the instant increase from ~0.0016% to ~0.0066% exactly matches the 0.005% cap boost granted by that one additional level of the “Increase Prisoner Chance Cap” upgrade.
I just thought I would mention it as it could have been a bug; my bad, I wasn’t fully clear on the original post of the variables.
It doesn’t matter though—dev Soehnle looked into it and didn’t think there was an issue anyway.
Hope that clarifies things!