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
https://steamcommunity.com/app/562860/discussions/0/3940146862829928372/?l=czech
That's what "should" happen, but what if that doesn't work?
This game is quite faithful. It perfectly emulates the games of the early 90's in terms of gameplay but also in terms of technical issues. A DLC expansion not being compatible with the main game was fairly common back then, but it's certainly not something you'd expect in 2024.
And the intended plan is still that it will be as soon as the base game is updated to the v3.x code base. Even if that had been done on the same day that Aftershock had been released nothing would be any different here... The base game and the expansion would have both been using v3.x game code, and an old save file from v2.x would still be an old save file from v2.x and would still not be entirely compatible with v3.x.
It would've been nice if the devs implemented an additional check when loading a save or trying to equip the shotgun to ensure this bug doesn't occur.