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
A) The result is already determined earlier than it seems (e.g. a month or a year before you see the result) or blocked by a different mechanic (e.g. trying to romance a close relative with 100% always fails within a few days unless they have certain traits or hidden triggers)
B) The game draws numbers for random chances from a pre-rolled queue of numbers.
For example the current number queue is 27-81-52-98, then your event happens and it always picks the 27 because it is next in queue. So with a chance of 57%, 27 is too low and it always fails.
If another roll happened first, it would take up the first number and you get the next one for your event. In this case 81 would be enough to beat the 57% chance, so it would always succeed.
In some games this can be easily played around, like in TW:Warhammer if a specific hero action fails once, it will always fail after reloading; though you can simply do a different action with another hero first.
In CK3 this could be more difficult depending on how old the savegame is, due to things happening in realtime all over the world. Then again i don't know if CK3 actually uses this system, and if it uses the same number queue for everything.