安装 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(越南语)
Українська(乌克兰语)
报告翻译问题
One dumb way I can think working around the 100% limit (1% loss an hour) problem, would be to keep a reference of connected generators and add 1% condition every x.x hours or whatever metric you want to use, to counteract the "loss" if you will. I assume that in theory, it would be a hacky way of implementing a "condition loss override" adjustment so that generators degrade slower.
In theory, if you set it to recover 1% every 2.0 hours, the generator would last about 2x as long, depending on how the timer would work. Ideally each generator would have its own condition managed as an instance, and the timer would be retained between loading a game/server world, but even a global timer should do well enough, as long as the timer is tracked and does not reset.
The closer to 1.0 you go, the longer the generator would last before needing repairs. if it were set to 100.0 hours, it would in effect disable any modification, though I don't see much point in allowing extreme values, then just disable the mod at that point xD
Main issue with that approach is how significant even a small change in values will have on the effect with this approach, making it a bit hard to estimate how long a generator will actually last.