Command restrictions all/any/no needs finer control

[S1D3WYZ]

Issue: command restrictions limited with current < all || any || no > implementation

Example Case: follow check, currency check, NEGATIVE role check

If "all" : can pass follow & currency (& rank/role) If "no" : can pass permissions : role <Probation> exclusion check (role to not time/ban user, but limit points/commands/etc)

Possible solutions: Allow Permissions to be negated/NOT (pass if false) Could even pass +/- perm role/rank checks separately

OR Allow different AND / OR / NOT sections to Restrictions options

[CKY-]

for now use a conditional effect

[S1D3WYZ]

yeah, ended up figuring out that workaround .. much pain to copy to all commands and move the previous outputs inside ..

(would be a bit easier if there were a "cut effect" in addition to "copy effect" to take 2 actions instead of 3 .. for each effect .. wouldn't have been so bad to implement from beginning if i foresaw the issue on command creation instead of realization and back-porting .. but i can submit a separate FR for that too)

but yep, i got there . hope this can be added in the future

[ebiggz]

@S1D3WYZ Thanks for the suggestion! This has been implemented for the next release. All restrictions will have the option to be "inverted" 👍🏻

[github-actions[bot]]

Released in v5.65.0