𝗦𝘆𝗻𝗲𝗿𝗴𝘆 (𝗮𝗹𝗹-𝗶𝗻-𝟭-𝗮𝗽𝗽) 𝟭/𝟭𝟭/𝟮𝟱 → Special Rotating Notices!!!

[cexmental]

#Synergy 1/12/25 12:15 am update
+ re-wrote /rnotice (rotating notice) engine
^ complete rewrite. Less moving parts. Better error checking. More options!!
+ added model admin database permissions
^ model can delete from any mod/user database
+ added 'username' to model /notice? output
+ added [ option ] notice support
+ updated related help windows
+ updated translations

This updated command allows you to create a list of rotating notices. Each verified notice is stored in your personal database. You may delete from, add to, or view your database at any time. You database is removed when the app stops/ends. The default time is a 10 minute rotation. To create a notice, type /rnotice 15 Please vote for me :cbthumb. This notice would appear in public chat every 15 minutes. Notices can be sent privately to users by name, group, or status using option notices. The create an option notice, type /rnotice 7 [ bold #FFFFFF user01,user02 f -t ] Hey, don't forget to tip! . This notice would appear privately for each individual user (user01, user02, all fan club, and all non-tippers) every 7 minutes in red and bold font.

Example of available [ options ]:



Example of the model database view (/rnotice?):



Notices are listed from most recent (05) to first entered (01). The time (7:15 or 14:37) following each number informs when this notice will execute next. The name following each time is the user who submitted that notice. Usernames are validated by CB naming conventions and online status before sending, this greatly reduces undelivered notices.

𝐼𝑓 𝑦𝑜𝑢 𝑤𝑜𝑢𝑙𝑑 𝑙𝑖𝑘𝑒 𝑎 𝑐𝑢𝑠𝑡𝑜𝑚 𝑣𝑒𝑟𝑠𝑖𝑜𝑛 𝑜𝑓 𝑡ℎ𝑖𝑠 𝑏𝑜𝑡, 𝑝𝑙𝑒𝑎𝑠𝑒 𝑐𝑜𝑛𝑡𝑎𝑐𝑡 𝑚𝑒.
DM @cexmental on X-Twitter or SynergyChaturbate @ gmail

Cheers,
Cexmental

 

[cexmental]

#Synergy 1/14/25 6:25 am update.
+ updated [ m ] execution to avoid sending mods (who are also 'special privileged users') duplicate option notices.
+ added redundant 'in chat' back-up database for /rnotice engine
+ optimized /rnotice engine

I've added a redundant data back-up for CB's asynchronous cb.getRoomUsersData callback. Due to the nature of callbacks, data can be returned out of sync with app execution. This results in empty lists and notices that fail to deliver. The redundant data back-up stores user activity on-enter and purges on-leave. CB's async callback is always referenced first, when that fails, error checks run against the redundant back-up database.

Neither solution is perfect. The async function can fail to respond with correct data and has intolerable scoping issues. The back-up isn't populated with users already in chat on app re-start. The back-up also can not track user color transitions (IE: A grey who enters, then buys tokens, is still a grey until they leave). Verifying if a user is actually in chat is not a requirement. Notices directed to a user not in chat will simply fail to display. However, they are still executed. By including redundant checking, we reduce overhead and the overall app footprint (IE: Imagine 3,000 undelivered notices!).

Cheers,
Cexmental