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
In the Character GUI there is only the reference to $SECOND$
But I couldn't find this second anywhere, in this SECOND String/Localization is described from where the game picks it localization, we only edited the localization for the one with two personalities, which is in the file a7x492 told above.
It has nothing to do with the AI personality strings.
- GetAIPersonality is looking for "$ADJECTIVE$ $NOUN$" when a noun is present. If an adjective is not found, it will gracefully resolve to just the noun.
- Because your mod changes the syntax of AI_PERSONALITY_ADJECTIVE_NOUN:0 to "[$ADJECTIVE$|E] [$NOUN$|E]", something is breaking the graceful resolution. It must have an adjective, and because its undefined the call breaks and you end up with the string of the noun, which never got processed. I briefly looked around in vanilla and my installed mods and I found very few instances of a localization key like $ADJECTIVE$ wrapped in a game concept link. It's possible GetAIPersonality won't accept this syntax.
Have you tried some sort of method to pass a blank adjective, or one that is an empty string?
Your game concept is:
blackguard = {
alias = {blackguard_female}
}
So I added one more as:
blackguard_femal = {
alias = {blackguard_female}
}
and localization:
game_concept_blackguard_femal: "Blackguard"
game_concept_blackguard_femal_desc: "A blackguard is #italic much#! #bold less#! likely to honor relationships and [alliances|E] and #italic much#! #bold more#! likely to become an [agent|E]."
So the problem isnt hard to fix, it's just tedious. Now I'm not sure about the alias, you probably don't want two concepts to have the same aliases.