Skip to content

Suggestion: Prevent running a certain Booster if another one is active #35

Description

@0x484

Make a "Conflict" option in order to prevent starting a certain booster while another is one is already active.
+Maybe a bypass permission for this
Example config option:
conflicts: [Booster-ID]

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type
    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions