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









To explain how this works, it constructs a new Haywire Protocol ability internally called HaywireProtocol_LW that can be modified with my Algorithm Presets Modifier.
The reason why cancelling the ability doesn't work is because the base code is still looking for the original haywire protocol by name. I'll have to go through the code and do a more thorough reconstruction.
But, does this mess with the way the base haywire works? I canceled my hack attempt on a robot and the cool-down is still there. I've never had this problem before.
Thank you for the translation, I will upload that ASAP.
As for the hacking upgrade, I would have to put that to user concensus, as I have no experience balancing perks myself. At a glance, I would agree, as Restoration can instantly revive and heal an unconscious soldier.
Or it's still weak perk (Better than Resilience though), compares with other two.
Others are game changing perks. Yes, Haywire Protocol is also strong and game changing ability. But still, It is too easy to fail.
Btw, in your screenshot... how the hack, that soldier's hack stat is 361?
Translated Korean Local.