I currently have a ticket raffle running, and noticed that the automatic announcements are not firing.
I had them set to once every 30 minutes, and after a few hours noticed nothing is being announced, so I set the interval to 1 minute and have still not seen anything.
!traffle autoannouncemessage test
!traffle autoannounceinterval 1
Also tried !traffle autoannounceinterval 5 in the event 1 was too low.
I also tried entering random text into the chat, in case this announcement shared the same chat message count requirements as the normal automated announcements.
On a related note:
There are some inconsistencies between command syntax/structures for regular raffles and ticket raffles that make setting them up using commands (rather than the web panel) confusing.
As listed on commands page:
!raffle messagetimer [minutes]
!traffle autoannounceinterval (missing [minutes] )
For “raffle” the command “message” seems to apply to the automated announcement message, but under “traffle” the command “message” seems to be related to an entry message, and the sub-command “autoannouncemessage” is used. (same term, 2 different implementations) My moderators got quite frustrated with this one so I actually had to stop activity on stream to set this up myself. (only to then discover that auto announcements are not working)
Having the same functionality using different syntax between such similar commands (“raffle” and “traffle”) makes memorizing commands difficult/impossible. This is something I’ve touched on before with other commands, where there did not seem to be standardization of terminology, which I’m guessing is a symptom of multiple developers splitting up and tackling different aspects of the bot. Totally understandable, and super common, but should be addressed as a priority.
The syntax used on the commands page seems to be !command sub-command or !command [option] where a user-defined parameter (message, numerical value, username, etc) is represented with brackets.
If you filter the commands list by “traffle” you will notice many of the commands there have their sub-command (not a user-defined parameter) in brackets.
While this is not a serious issue, it does cause a bit of confusion. Might be nice to add a housekeeping task to clean up the commands list, and also use that opportunity to re-define some commands that perform similar tasks to use standardized syntax. IE: autoannouncemessage in !traffle vs. message in !raffle
I totally understand the inconsistency in the command structures/syntax/etc. as I see this type of issue arise all the time when working with teams of multiple developers, especially with teams that don’t have the luxury of project managers helping keep everyone on the same page. Here it’s just highlighted since those commands are the primary interface to this product, especially for moderators, and this inconsistency makes memorization and efficient use of the commands difficult/impossible. This makes relying on the commands list on the website a requirement rather than an option. Not the end of the world, but an unnecessary complication.
While cleanup/maintenance tasks like this are not as satisfying as stomping out bugs, it’s important that these issues get cleaned up since these commands are the moderators only interface with the bot. To that point, have you thought about adding the ability to add moderator user accounts to the web panel? Since these commands are inconsistent and confusing for my moderators it would be nice if I could give limited web panel access to the moderators so they don’t have to rely on commands alone.
Again, totally love, respect, and support everything the team here is doing! Especially given that this is all done on a volunteer basis!