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 said this is the fourth Good Place playthrough I'm doing and the first at night, in fog, with most of my mercs packing thermal scopes. So who knows?
Seems like a complete d-bag move *IF* intentional on the part of the developers. Going to start a new unmodded playthrough under the new patch and see if the problem persists.
Yeah nah we're specifically talking about loading a saved game and having an alarm triggered by an NPC within a couple of seconds of loading.
I have done reloads 10+ times to test and it happens regardless of merc positioning.
Ironically the last runthrough of Good Place was probably the easiest I've done despite the alarm being triggered- thank goodness for Livewire and Barry packing an RPG.
I did the same thing and got the same result, which is why I thought it was an anti-savescum mechanic.