安装 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(越南语)
Українська(乌克兰语)
报告翻译问题
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.