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.