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






there is an issue for it on the mod's github repo as well
https://github.com/Cozarkian/QualityExpanded/issues/2
I verified local files and started the game, and it looks like it's back in action! Got tons of stuff to repair now. ;-) Thank you again!
The modification of max hit points is done through code. Thus, there is overlap and this mod "wins" by using Harmony's priority system to ensure it overwrites any changes by other mods. However, max hit points is only relevant at spawn, after a quality loss, and on the inspect screen for the selected item, so it shouldn't cause performance issues.
I guess my question is *how* it achieves that compatibility? Does it disable parts of itself? Do we need to check those settings ourselves? I like the idea for the mod, but before I pull the trigger I just want to know what overlap is expected, or if I should drop some mods for a more complete solution.
And no, it can't cause cascading loss. In your example, since the lower quality is at max 200 hit points, the building can't degrade until it is already at 199 hit points. I'll add more to the FAQ to explain.
Example: damaging a fortified door, might:
cause 10 initial damage ---> degrade quality ---> lower max hit points by 200 ----> result in 210 hit points lost
?