feature-requests

I know all the buttons have the logic like: ID58, ID59 when we create them. However, I like to separete the buttons by setting a Prefix for all ID's based on the deck the button is upon creation. For example: Audio Deck: All ID's will start with AUDIO_ Commands Decks: All ID's will start with CMD_ Trigger Decks: All ID's will start with TRIG_ And so on. This could be something that the user defines, so it will be easier to organize and know where the button was created. This settings will be applied to any new button created inside the deck and if you change the deck settings it would apply only for new buttons.

It would be perfect to have a native kick intergration that doesn't relly on the bridge to stay on, because if the browser kills the tab because it is open for too long, the kick integration stops to work.

In regards to <#1381468997484150804> (Hoping it shows up properly in Discord): Is there a probability a "See own output" and a "Respond to own output" switch can be added to the settings, along with a warning, that it can cause recursive loops? That would make the switch between API message sending and normal message sending easier. In some cases the seeing is needed, when chat boxes are programmed, for example. Can be ditched as well. Keep me posted, if possible. Edit: Discord link, in case the link to the thread is needed instead: https://discord.com/channels/699319482442711072/1381468997484150804

I feel like for newer users they won't necessarily know what a command does. Providing a UI button that is a link to the documentation would help. It was brought up that pressing F1 when hovering over a command will do this, but I don't think new users will know keyboard shortcuts.

I feel like for users who are just trying to check out sammi expecting them to use an external site is too indirect. There should be a feedback form inside of the app.

Same as we have for Twitch Connect a second "BOT" account and be able to "Join Chat under this name", to be able sending messages to the Broadcaster Channel with the "BOT" account

I know its easy enough to get my live status using an API but I think it would be a pretty nice addition to include a global variable for instance live_on_twitch true/false, I kinda messed up in the first place by having multiple buttons poll the twitch api for my live status when I shouldve set it in a single button and referenced it where needed but I think adding a live status to the global variables would be much more intuitive for people, especially those who are less versed in using SAMMI. Even if it gets added as a separate option/config so those who don't need it can turn it off so it isn't constantly polling the api for nothing

It would be useful if we could prefix a variable with say _myVar and have it be immune to Delete Variable All or add some form of new delete variable that deletes all but the special prefixed ones. Sure its a niche case but It would open up the possibility to cache fetched data all self contained within a single button without needing to delete multiple specific variables at the start/end of every button or without needing to use another button to save said cache

Add a new Sammi command that allows exporting the JSON data of a specific button using its ID and storing it as a string. This string could then be saved to a file, replicating the functionality of 'right-click -> export JSON' but as a built-in Sammi command :3 <3

Earlier I worked on a button that would play an audio on a !command. I then organized my audio files and moved them around from its original file location. Took me some time to realize my organizing meant there wasn't a file to be played anymore! Some pop-up or notification that a file does not exist would be nice to have! I imagine something similar to OBS, where if a source file is moved you get a pop-up at startup. Or perhaps a red box if a path for a file doesn't exist.