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



But, at that point, wouldn't be the modders' "job" to make the mod playable?
Generally I would agree... I'm not a modder but it is a source mod which has worked perfectly for 20 years (and been upkept by the devs of the mod) without any issues like this, still has a following and for whatever reason the most recent Steam Client update has been confirmed to prompted this specific issue which makes me feel like it could be an oversight in some way. I can still play, but only because I've locked it to the previous version of Steam Client, which ideally I'd like to be on the uptodate one. I was just checking if this is a known issue by valve, or something which they are currently working on, or even aware of... the dev's feel this is something valve will patch and not an issue with their game.