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
I requested for the UCP to use the largest two planet sizes for planet construction but WhatIsSol didn't react to my post.
If you'd like it to do that you'd have to ask WhatIsSol.
Error parsing Backend.Galaxy.PlanetSizeType. Key 'planetsize_gigantic' on Variable 'satelliteSizeChances' with value 'QiHe.Yaml.Grammar.Sequence'.
Error parsing Backend.Galaxy.PlanetSizeType. Key 'planetsize_gasgiant' on Variable 'satelliteSizeChances' with value 'QiHe.Yaml.Grammar.Sequence'.
As far as I can tell, a zero value for any of the satellite properties is invalid and fails to parse. This is supported by the fact that in the original PlantSizeType file the properties for any that would have a value of zero ARE OMITTED rather than declared as zero. That is likely not an accident.
I used a new game with a colossal home planet for the test and encountered no problems.