安裝 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(越南文)
Українська(烏克蘭文)
回報翻譯問題
The game is not optimized for having tons of timers running and being triggered at tick rate. It never will be.
not second
What I've done:
Named the timers "Firing Stage 1 Adv" (no quotes), "Firing Stage 2 Adv" etc.
They all chain to each other - this was tested without the script and works.
They all have a time of 60 (1 second).
I've recompiled the script after naming each timer.
I triggered "Firing Stage 1 Adv" (result below).
I stopped all timers, and started (didn't trigger) "Firing Stage 1 Adv" (same result).
I set the delay of each item to one second and triggered the timer again (see second result below)
When I execute the first timer (using Trigger Now, though the others are just linked with Start) and the timers are configured to chain with sixty-second intervals (before the script's intervention), the timers execute with a sixty-second delay, as opposed to a one-second delay.
When I repeat with a one-second timer, the sequence executes as normal.
Glad to hear it!
Also, if an updade broke this script, you would fix it, right?