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
IIRC after the trigger became "project reached 2 pips" in 1.1, it created some edge cases for lower difficulties where players who pulled super far ahead could repeatedly remove the single pip and not find out for a very long time. And I think there was a bug identified where if liberation happened before 2 pips it broke the UI but I'm only vaguely going off recollection of a discord discussion. It's also possible I'm confusing 1.1 changes with intermediate 1.2 builds.
Anyway, Tedster should've fixed that in the final 1.2 build (the current "main" release) by enabling both the original liberate a region condition and 2 pips are reached whichever one comes first. If you are on 1.2 then you may want to join the discord and report a bug if you have anything to help the dev team troubleshoot the issue.
Infos are on the long war of the chosen workshop page.
For now, you can try enabling console commands and try the command
LWOTC_RevealAvatarProject