安裝 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（越南文）
Українська（烏克蘭文）
回報翻譯問題
0 
檢舉此篇文章
I have been able to confirm this issue. I have been able to reproduce it in singleplayer as well.
The cause for this bug has been found, but I'm unable to say when it will be fixed.
To explain the bug in simple terms, the activation delay ("First Horde Delay") is actually the delay that occurs after the spawner is created before it starts working.
If you used the editor to place down a spawner module, this means that this delay is basically the delay since mission start (+3 secs for internal reasons).
Essentially, "First Horde Delay" does not take activation into account, which is of course a bit misleading.
I'm surprised we haven't discovered this problem earlier.
To workaround it, you would have to create a spawner module on the fly using scripts, though this requires some skill in scripting and that you dePBO the Z&D file to get the right module variable names.
This may be a bit much, so my advice to anyone would be to avoid this module for now if you want zombies to spawn on specific activation + a noticeable delay.
Use triggers and BIS_fnc_spawnGroup-alike functions instead.