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's because Satisfying States only overrides a few character definitions, so the vast majority of the charcters are still the Vanilla ones.
For example, they have not updated their German decisions file, so if you use Satisfying States with Community Portrait Pack, changing the mod loading order won't change anything: you will keep the default Satisfying States portraits for Reicskommissars.
Basically, there is two ways to code portraits in a database (Vanilla or modded), the first is to give a specific file path of the desired image, the other is to point to a unique gfx object which then assigns an image path in a different interface file.
Paradox missed an oportunity by relying almost exclusively on the first way, until quite recently. They fixed it in 1.11.5, but modders haven't.
The (new) soft way of referencing an abstract object rather than a specific file path makes that portrait modders do not have to overwrite any characters definition in the database.