Skip to content

[Automation] Local settings or variables or signals for buildings #95

@nommygit

Description

@nommygit

One example is I would like to be able to set a Priority for each pump that affects when it starts and stops.
I'd like to be able to reference this Priority in multiple rules on that building.
I'd also like to be able to use the same rules for each pump, copy them, using the same name for Priority, but with it able to be set to different values on different buildings.

Some sort of local signal could work e.g
(act Signals.SetLocal 'Priority' 8) perhaps.
and
condition: (ge (sig Signals.Local.Priority) (sig Signals.RunPriority)) or something to unpause.

The trouble with just hard-coding 8 (or any value) is you would need to dig through the rules and change it in each one where it's used to alter it.
Using a unique signal for every building e.g Pump15Priority is also sub-optimal.

Even better would be some way, separate from the rules to define settings, so copying rules doesn't alter the settings. I'm not sure this is worth the effort though, but I'm mentioning it for thought.

Another use case is MinLevel and MaxLevel for goods to control when producers and consumers run which you might want to set to be different between different buildings but copy the same script to each.

Metadata

Metadata

Assignees

No one assigned

    Labels

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions