About to make major changes / and pull updates to multiple files across my DAO bot, having to change both database tables and backend logic for services using those tables + front end logic for mini-app that deals with the databases. I am creating badge system, that issues badges via court records section, there will be global scoped badges and dao-scoped badges, and dao admins can issue dao scoped badges, with badge images being mutable with a seperate table for badge_images, that allows badge images to be updated. /n There will be milestone badges built in (like dao-scoped badges for hitting certain checkin streak milestones) as well as other types of badges. /n/n I am going to implement "historical" badges that commemorate current events that will become major points in history in the future. getting awarded the Badge for the Iran War will prove you were monitoring the situation. /n/n Court records will have badges issued, badge_images table will store images seperately from issued badges to allow visual updates or tweaks. I'm also expanding features of dao_members tables (not global users, users can be in multiple daos) as I will implementing a system and variables for tracking current checkin streaks and longest checkin streaks. Streaks will be broken if people midss 2 consecutive snapshot windows (that have snapshots for those days). Streak checking logic is only iterating through UTC calender dates that contain a snapshot window, as I'm accounting for potential future maintance downtime both in and out of testing phase, as to not reset existing streaks if the bot has downtime. I have pivoted from frontend back to backend (and will have to pivot back to frontend after) as a result of the new variables and table structures needed + logic built, and hopefully this will help me create a better foundation to built from as I encounter having to patch in different variables and data throughout my entire codebase and learn how to do it more efficiently. Bear with me these next couple days, once I pull these changes, likely i will have to iron out some errors and flawed implementations, and rather than revert to the working branch immediately, i will likely go into a period of intense debugging and the bot will be turning on and off and on and off as I tweak code and test changes, in which case if you happen to try to checkin when the bot is off, you will get no popup or success / failure message or anything (remember you have to dm @PsyopDaily_DAO_Bot '/start' for it to be able to DM you.. Shortly after I make this announcement, i will be pulling changes and testing and iterating, maybe be just a few hours of downtime, may be a few days. A few badges in court records have been issued for initial tests on badges as i pulled those changes, but i was issuing dao scoped badges to all users, resulting in 2 duplicate beta tester badges for global users who are in both existing daos. I deleted those badges. I need to snapshot court records along with some other peripheal data that isnt in main snapshots. I will improve snapshot logic to include more database tables soon, court records can be dao scoped or global scoped. I will need to implement global scope snapshots soon that dont contain dao-specific data, but contain global data (global user table, court records entries for global bans / suspensions / badges etc). With that said, I will get to it soon. If you wonder why the bot isnt working or is down in coming hours or days that is why