usage_priority is not very clear
Posted: Fri Aug 16, 2024 7:51 pm
You can read here that there is several mode for priority, I think this can be improved for 2.0. Indeed I wish I would be able to better control electricity. Not gonna lie I don't use power switch :p.
I made a mod and after some testing, it look like there is no real practical difference between input and output. At least setting accumulator to secondary-output doesn't look to stop them to recharge. But put roboport to tertiary make them act like accumulator.
My biggest problem is currently there is not really a third level of priority. This mean we have only primary and secondary. Tertiary look more like a hack for accumulator.
If possible I would prefer a system like this:
I think that self explaining but the goal is to make it clear that some entity can do both, and the level is 0 top priority then 1 then 2, etc... thus only 0,1,2 could be enough.
This could also contains the input/output flow limit.
I made a mod and after some testing, it look like there is no real practical difference between input and output. At least setting accumulator to secondary-output doesn't look to stop them to recharge. But put roboport to tertiary make them act like accumulator.
My biggest problem is currently there is not really a third level of priority. This mean we have only primary and secondary. Tertiary look more like a hack for accumulator.
If possible I would prefer a system like this:
Code: Select all
"usage_priority": {
"type": "input/output/input-output",
"level": u8,
}
This could also contains the input/output flow limit.