Configuring System Power #523
Unanswered
alexanderson1993
asked this question in
Ideas
Replies: 0 comments
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
There has been a lot discussed about power already. The one thing that hasn't been addressed yet is how systems get their power and what they do with it.
First off, one thing that hasn't really been addressed is power overloads. It should be possible to allocate more power than is necessary into a system to make it operate better. A 200% increase in impulse engine power should double the possible impulse engine speed, etc. Overloading a system will automatically induce damage or an efficiency decrease, comparable to the amount of power supplied above the recommended amount.
To illustrate this, let's look at a few different kinds of systems and how they respond to power usage.
More system situations are described here: #349
So, how do we devise a system for defining power that works across all of these different ways of consuming power?
In Thorium Classic, power was defined with three properties:
My proposal for Thorium Nova is three (only 3!) different properties:
requiredPower
- The minimum amount of power required to make the system operate. Below this and the system shows an "Insufficient Power" warning.defaultPower
- The normal amount of power the system will request. The system should operate at the expected levels when at this power level.maxSafePower
- The threshold of power usage for safely using this system. It should be possible to increase power usage up to this point without damaging the system. Any usage above this point will overload the system and cause better-than-expected output while damaging the system and decreasing efficiency.How are systems overloaded? By deactivating the safety protocols on a system. This would be done from the power distribution screen. I'm not sure exactly how this will work yet, whether it's merely toggling the safeties on or off, or whether it should be possible to choose exactly how much power the system will accept. Probably the latter, to make it possible to have the system never use more than that requested power, and to limit how much a power hungry system can damage itself.
Examples:
defaultPower
, but will continue to work (but worse) up to therequiredPower
level. Sensor scans will cause power to spike by some amount (configurable on the sensors system itself) up to themaxSafePower
level, at which point sensor scans will slow down. If there isn't enough power, concurrent scans will spread power, slowing all of them down.requiredPower
of 4 and amaxSafePower
of 10 would consume 4 units of power at ¼ impulse, 6 at ½ impulse, 8 at ¾ impulse, 10 at full impulse, and overload to 12 at destructive impulse. ThedefaultPower
would automatically be set at themaxSafePower
, making it possible to accelerate to any speed exceptdestructive
.requiredPower
level, and recharge faster with higher power usage. When recharging, they will always consume any surplus power.requiredPower
is how much is consumed during the loading phase, anddefaultPower
is how much is required to launch a torpedo. Using up to themaxSafePower
will make torpedos load and launch faster.One great way you can comment: Pick another system (link above) and describe how you think it should work based on these three properties.
Of course, thoughts, questions, comments, and suggestions are welcome as well.
Beta Was this translation helpful? Give feedback.
All reactions