AbettorBot Blog + Info


AbettorBot is a bot written entirely by Rwarcards762 as a bot to do “the things other bots didn’t do the way he liked.”

AbettorBot recently underwent an entire rewrite from discord.py 0.16.12 to 1.3.3.

All documentation under “Reference Pages” is up to date based on the label on the button.


Reference Pages


Additional Links


Update Blog Posts

11/28/21 — I’m alive, I promise!

Hey all, I haven’t written one of these in MONTHS. A few reasons why — I moved (twice, technically) and am now working full-time. Free time has been something that has eluded me for the past months as I’ve settled in to my new job. Thankfully, I’m finally starting to settle in and think I…

6/4/21 — Birthday System Patch (BETA-1.0.7)

Hey all, it’s been a while. I’m currently on painkillers after wisdom tooth surgery… the perfect time to fix bugs in your bot, right? Sorry for the lack of updates recently, I’ve just graduated college and have been hunting for a job! I knew the birthday system had some odd quirks that had not been…

3/21/21 — AbettorBot 3 Progress, AbettorBot2 Bug Fixes (v1.0.6)

Hey all, I’m back to write a bit more finally. Since last posting, I finally dug in and cleaned up some bugs… thanks to my girlfriend for finding them on accident (of course.) I’m not certain what sort of bug mentions I’ve put into my blog posts previously, so I figured I’ll just put everything…


Want to stay updated on AbettorBot?

If you’re the kind of person who likes everything to come to you, then this is the way to go. You’ll get an update when blog posts are made, so you can be aware of the latest changes and features.


Have feedback or suggestions? Want to report a bug?

Feel free to reach out to me on Discord, Twitter, or any other social media. Twitter: https://twitter.com/rwarcards762
Discord: Rwarcards762#0762


A Terms and Conditions of Sorts

Updated 9/8/20 — Revision I: Added information about birthday system

Preface
At some point, I will inevitably have to get AbettorBot “verified” by Discord. In preparation, I plan to keep a running post (like this) so that all users are aware of what information I have.
AbettorBot has always been and continues to be a one-man show. I, Rwarcards762, am the only person with access to AbettorBot’s user token, source code, and stored data. AbettorBot keeps no sorts of chat logs, command usage logs, or any sort of frivolous information like that. The only information stored by AbettorBot is that which is needed for the bot to perform its functions. As a disclaimer, AbettorBot originally was distributed with the generic “Administrator” privilege. Obviously, this was overkill and was done in the early stages to simplify the process and usage. As of May 2020, AbettorBot’s invite link does NOT grant the Administrator privilege. I will now summarize the data used by AbettorBot.
I. Reminders
Reminders are generated by users and stored within AbettorBot’s data storage filesystem. The information stored about reminders is only the information that was provided by the users when they created the reminder: Duration of Reminder in seconds, what time it is due to complete, the messageID (used to generate pseudorandomness in the filenames, allowing for users to create reminders with the same amount of time without overwriting previous), the channelID (used for knowing where you need to be reminded), your userID (for mentioning you when it has completed, and for naming the file accordingly), as well as the contents of your reminder (whatever message you want to be reminded of.) These reminders are stored in files only so that if the bot has an issue and must be restarted, reminders can be re-initialized. Once a reminder is complete, the file corresponding to it is automatically deleted.
II. Color Roles
Information about how a server’s color role system is configured must be stored so that the bot knows how the server wants the system to function. Information stored locally includes configuration options (is the system enabled, can users create their own colors, can users name their own colors) as well as information about roles created with the bot (name of role, color value of role, roleID — so that the bot knows what it created, so that it can swap people’s roles without giving them access to roles not created for the color system’s purpose.) If the color role system has never been enabled, none of these files will exist. If the color role system is disabled by a user, it resets the configuration data and deletes all information about the roles that had been created.
III. Bot Administrators
AbettorBot has no information about who has “admin” permissions in a Discord server. AbettorBot may serve better for you as a color-commands bot and a toy, which is fine. There are plenty of solid administration bots out there. Therefore, AbettorBot only keeps track of admins who are explicitly given permission to use the AbettorBot’s admin (a@) commands. [Adding and removing AbettorBot admins can be done with a@addmod and a@delmod.] These admin lists only contain the serverID and the userIDs of any bot-assigned admins. No other information about admins is stored (because there is absolutely no need.)
IV. In Regards to “Privileged Gateway Intents” (Discord Verification Process)
AbettorBot does not keep track of any presence data for users, including but not limited to current Game status, Spotify listening, Activity status (Away/Online/etc), and et cetera. AbettorBot also does not keep a running list of members in a server. The only information stored about users is reminders they may set. The entire member list is not downloaded at any time– the only time the members of a server are grabbed is for ID lookups to get a user’s “User” object for usage in mentions and other internal functions. This information is then discarded once used.
V. Birthdays
AbettorBot now (as of version v1.0.5) features a system which allows servers to assign birthday roles for users automatically. Users may input their birthday to be saved for usage in this system. This system is entirely opt-in only. All birthdays are stored locally and used only for this system. I, Rwarcards762, am the only person authorized to see these files. I shall not use these files for anything other than the Discord bot, which is handled automatically.
VI. Closing Statements
I, Rwarcards762, have direct access to all of this information, just like any bot owner would. I never look into any of the files created with my bot other than files I have specifically created for testing (for which I can identify them as the file name contains my userID or something similar.) Do note that information like serverIDs, messageIDs, userIDs, and more can be easily obtained by anyone. This isn’t some magical bot power. If you are uncomfortable with me even having the ability to see this information, Discord Bots may not be for you. Again, all information the bot uses is stored locally. My goal is to provide a service to users while also enjoying the process of solving problems in Python. Thank you again for your support. If you ever have questions about the privacy of your information or would like to request anything the bot has about you, please reach out to me on Discord.