Install Steam
login
|
language
简体中文 (Simplified Chinese)
繁體中文 (Traditional Chinese)
日本語 (Japanese)
한국어 (Korean)
ไทย (Thai)
Български (Bulgarian)
Čeština (Czech)
Dansk (Danish)
Deutsch (German)
Español - España (Spanish - Spain)
Español - Latinoamérica (Spanish - Latin America)
Ελληνικά (Greek)
Français (French)
Italiano (Italian)
Bahasa Indonesia (Indonesian)
Magyar (Hungarian)
Nederlands (Dutch)
Norsk (Norwegian)
Polski (Polish)
Português (Portuguese - Portugal)
Português - Brasil (Portuguese - Brazil)
Română (Romanian)
Русский (Russian)
Suomi (Finnish)
Svenska (Swedish)
Türkçe (Turkish)
Tiếng Việt (Vietnamese)
Українська (Ukrainian)
Report a translation problem
And don't count on a auto shutdown system, when reactor integrity is critical or a fuel meltdown occured its either manual fuel removal or explosion
Not sure how I would check each rod durability (would be equal to rod purity) to create a linear scale of the meltdown severity, or if its even possible to do so currently
If I tried to make a range factor for that concept it would involve two explosions and that means likely doubling server/client strains from those effects
Im using explosion to apply any radiation, so technically its already raytracing
Think I've tried multiple different approach to lessen the rubberbanding issue, haven't been sucessfull in any attempt to make significant changes
By time based could you elaborate a bit more how that would be code wise if you can?
Despite the mod I basically learned the 101 of baro modding on the go to make it
I love the effects of the mod, they are fun to experience in multiplayer, especially with added complications like Neurotrauma and a bunch of other mods.