安裝 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(越南文)
Українська(烏克蘭文)
回報翻譯問題
Removing the line, adding a Behaviour line before, or commenting it out with ';' prevents issues.
It does create a Redscreen on non Steam variants if left in, as well as contributes to increased lag due to ram inflation, like any redundant lexicographic characters.
We've done our part reporting it and it's now resolved in the fix repository, whether you choose to update your main work is up to you, but at least now it's publically known for those experiencing issues. Thank you for clarifying that it's safe to cleanly delete as fastest method of correction.
My only nitpicks are that the voidweavers spawn too often sometimes, it was very common to see pods of a gatekeeper +2 voidweavers clustered near an identical pod in the same mission at high force levels.
That and I don't know how to feel about the Jaundiced in particular getting unavoidable damage on spawn unless you cheese the voidweaver with the old reaper + sniper combo. If he shows up you can kiss your flawless mission goodbye.
I did find a small bug (I think it's harmless, but it still should be fixed at some point, especially if it turns out it isn't harmless): when creating the Astral Vices templates you have "Templates.AddItem(GreedSpectreM1());" in there twice.
Awesome idea
I guess I'll have to do it then.
Don't mind if i do!
TdizzleGod if you add it mid campaign the only thing you won't get is the Voidweaver Autopsy, everything else should work fine and the Astral Beacon should be craftable from the start.