安装 Steam
登录
|
语言
繁體中文（繁体中文）
日本語（日语）
한국어（韩语）
ไทย（泰语）
български（保加利亚语）
Čeština（捷克语）
Dansk（丹麦语）
Deutsch（德语）
English（英语）
Español-España（西班牙语 - 西班牙）
Español - Latinoamérica（西班牙语 - 拉丁美洲）
Ελληνικά（希腊语）
Français（法语）
Italiano（意大利语）
Bahasa Indonesia（印度尼西亚语）
Magyar（匈牙利语）
Nederlands（荷兰语）
Norsk（挪威语）
Polski（波兰语）
Português（葡萄牙语 - 葡萄牙）
Português-Brasil（葡萄牙语 - 巴西）
Română（罗马尼亚语）
Русский（俄语）
Suomi（芬兰语）
Svenska（瑞典语）
Türkçe（土耳其语）
Tiếng Việt（越南语）
Українська（乌克兰语）
报告翻译问题
> mind explaining / defining this for clarity?
"In terms of hypothetical future official updates,
this is important since re-compiles are forbidden due to testing cost and risk"
Compiling a map changes too much information about the .bsps even if it's supposed to be the same.
And since the L4D2 maps were compiled around 10 years ago, the tools that were used to compile them may have changed drastically.
This has the chance to introduce some new bugs, crashes, or slowdowns, and risking that with a big playerbase isn't worth it.
Source Engine looks at these files as direct *.BSP file updates.
So that means this can only be played locally or with others who also have the mod.
Modification of lighting and map geometry without Hammer or re-compiles.
it modifies the already existing original campaigns.
"In terms of hypothetical future official updates,
this is important since re-compiles are forbidden due to testing cost and risk"