安装 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.