Range based operation

[GunpowderLullaby]

Is your feature request related to a problem? Please describe. A clear and concise description of what the problem is. Ex. I'm always frustrated when [...] No

Describe the solution you'd like A clear and concise description of what you want to happen. I would like to see a feature added to the facility control loop that starts up and shuts down the reactor system based on induction matrix charge level. For example the user could set their min and max charge levels to 10% and 95% so the system would start up at 10% run till 95%, shut down and remain dormant until 10% when the process starts again.

Additional context Add any other context or screenshots about the feature request here.

[MikaylaFischler]

I'm curious, what is the rationale is for this over just setting charge level control to 95%?

The biggest challenge for this will be finding a place to put those options on the Coordinator process control main display section, since nearly every space is currently occupied.

[GunpowderLullaby]

My rationale is for server resources and stability. When a large reactor complex is inert it uses far less system memory than one that is operational.

The second reason I would like to see something like this is server resets. Even with SCADA active, upon server restart there is a chance that something goes sideways and in that moment before RPS kicks in the reactor can melt down. I have found upon restart it tries to start back up at it's last burn rate value which is most likely the maximum set unit value allowing no time for coolant stability. So my thought process is that the more a reactor can be off the better.

[MikaylaFischler]

1. This is a valid rationale. I do know that on start/stop Mekanism eats up resources, and running a fuel production line is more costly than not.
2. Server restarts and chunk unloads have been extensively tested and will not lead to a hazardous situation as long as the Reactor PLC is in the same chunk as the reactor. Reactors are SCRAM'd at boot of the Reactor PLC, and if things resume without reboot and the Supervisor isn't there, it will also SCRAM. Automatic control by the Supervisor is only ever engaged if all systems are online (such as all cooling loop multiblocks are formed and ready). If anyone reports a meltdown after chunk load or server restart, I will be very surprised. An additional control mode would behave no differently than any of the other modes in terms of safety; it would be identical to monitored max burn or charge level control, just with a different input condition.