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









Aaaand it's back up after a rebuild of the core systems.
@/dev/null
I had to get rid of your custom stacking system, somehow it was causing trouble during mission start on missions after the first, if I had to guess, something is off with the gamestate handling.
I've switched to basic effectstate stacking, using:
[code]
DuplicateResponse=eDupe_Refresh
bStackOnRefresh=true
[/code]
And a simple GetToHitModifiers that uses the iStacks variable on the effect gamestate and caps the total aim bonus.
The stacks condition was also adjusted to use iStacks variable;
This is admittedly less versatile than your custom stacking system, but it has the benefit of working in WOTC.
Thanks for letting me know.
Yeah, my bad for not seeing this comment.
Despite some tests, it was still crashing, so I took it down.
I'm re-evaluating my approach, I'll probably have to rebuild it instead of using /dev/null's code.
I've been playing around with some stuff, doing a basic version is fairly simple, so I'll do that.
Were there problems with that build? Its entry's removed or hidden on the Workshop...
Here we go, I've tested it some, and it appears to be working as it should.