Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[Feature Request] Trigger Groups for quick bulk changes #576

Open
H0LD-MY-BEAR opened this issue Mar 12, 2018 · 4 comments
Open

[Feature Request] Trigger Groups for quick bulk changes #576

H0LD-MY-BEAR opened this issue Mar 12, 2018 · 4 comments
Labels
Enhancement A feature request or improvement v6 Enhancement that will likely not be considered until v6

Comments

@H0LD-MY-BEAR
Copy link

What version of Firebot are you running?

Release v4.10.5

Please describe the issue or feature requests in as much detail as possible.

Feature Request: Chat Command groupings that can be bulk toggled to Active/Disabled state - Example Concept: Subscriber Commands - If a streamer would like to disable a large selection of chat commands (their sub commands), the streamer currently needs to manually disable each command one at a time in a minimum of 3 clicks (open command -> uncheck 'active' -> save) or come up with a scripted way to recurse through a custom list of commands and activate/disable each one (I don't even know if that is supported, I'm just assuming). Giving Firebot the ability to quickly disable an entire group of chat commands would give bot-users quick, easy control over an interactive feature they offer as a reward to special members of their community, who still, at times, abuse the reward at undesired times =)

@ebiggz
Copy link
Member

ebiggz commented Mar 12, 2018

I can definitely see the need for this.

I think the best way to accomplish this is to create an “Update Command” effect that, like the existing “Update Button” effect, would let you edit the active state of a given command. Then you could set up a hotkey or an interactive button to disable whatever commands you wanted.

@kateract kateract added the Enhancement A feature request or improvement label Mar 13, 2018
@Firebottle Firebottle added this to the Future milestone Jan 3, 2020
@Firebottle Firebottle removed this from the Future milestone Feb 2, 2020
@ebiggz ebiggz changed the title Chat Command Groupings for Quick Bulk-Activate/Disable State Changes [Feature Request] Chat Command Groupings for Quick Bulk-Activate/Disable State Changes Feb 24, 2020
@ebiggz ebiggz added this to To do in Work Status Feb 27, 2020
@ebiggz ebiggz added this to Needs triage in Priority Feb 27, 2020
@ebiggz ebiggz moved this from Needs triage to Low priority in Priority Feb 27, 2020
@CaveMobster CaveMobster moved this from To do to Backlog in Work Status Dec 24, 2021
@Anabella00geek
Copy link

Addition of Groups so that commands, channel rewards, present effect lists, and timers could all be added to groups that could be turned off and on when needed. You could set up the group and add all the things that you would want to turn off with the click of a button within that one group.

@ebiggz ebiggz changed the title [Feature Request] Chat Command Groupings for Quick Bulk-Activate/Disable State Changes [Feature Request] Trigger Groups for quick bulk changes May 10, 2022
@izzy
Copy link

izzy commented Jun 16, 2023

Having Sets analogous to Event Sets in all the other groupable items like Commands, Rewards, Preset Lists, ... seems logical.

Another great addition would be the ability to specify/mass edit certain properties like Groups and Queues, otherwise with say 50 commands having to go through each one to move it to a new group will be tedious.

Instead I propose selecting with a checkbox or the likes of Shift+LMB to select multiple items and having a toolbar with applyable changes. A good example for this would be Github's own issue list.

@C3l4h1r
Copy link

C3l4h1r commented Feb 1, 2024

At it's core I was looking for something like this purely for an aesthetical, overview reason. Freely creatable folders to group commands or any trigger for that matter. Would really help and clean up some of the clutter I have right now with a growing list of triggers and events. Disabling triggers and the like on a folder based settings is a logical addition to this.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Enhancement A feature request or improvement v6 Enhancement that will likely not be considered until v6
Projects
Status: Backlog
Work Status
  
Backlog
Priority
  
Low priority
Development

No branches or pull requests

7 participants