how-to-use Booty video

Booty is a moderation bot for removing inactive members.

Tired of lurking and inactive members cluttering up your server? Introducing Booty!

Booty kicks inactive members after x days. If a member:

Did not join a voice room.
Haven’t messaged in x days.
No emoji reaction on a message.

You can specify the number of days and grant access for the slash commands (they need kick permissions). Booty will track your members’ activity while using minimal data.

In more detail, he will store this information:

Your server ID.
All user IDs of server members, excluding bots.
One timestamp per user.

This timestamp will be overwritten on user activity like sending a message, joining a voice room, or reacting with emojis. He doesn’t know the message content or what was said in any voice room.

Quickstart guide

Invite Booty
Run “/diagnose” - Diagnose checks if booty has all permissions it needs.

When booty can’t see a channel, maybe because it does not have the view access to it, then it can miss recording some activities.

In that case, simply include his role in the private channel and turn “View Channel” and “Send Message” permissions for his role.

Note about /update_db

Use the /update_db command as a backup solution. When Booty is invited to a server, he will automatically record the events (activities by server members) and try to include the server in its database.

When should you use this command?

Lets assume that some non-talking lurker joined while the bot was offline for maintenance. In this situation, update_db can fix it and record that lurker’s presens.

How to kick (or prune) inactive users?

/kick_status + number -> simulates kicking. It shows how many people would be kicked with their usernames and “last seen activity”. It doesn’t remove anyone from the member list.
/kick + number : same as kick_status but removes inactive users from your server. “number” means the number of days users have to be inactive for the bot to kick them. If no number is given, then 90 days are assumed.

Note : Booty can kick and list people whose highest role is the same as Booty’s highest role (a standard in Booty V3).

Optional Configurations:

Whitelist people

Booty will never kick or track other bots or system users, but you might want to ignore certain people. Simply use:

/whitelist_add + user
/whitelist_check
/whitelist_remove + user.

Whitelist roles

To whitelist entire roles, go to your server settings -> roles and move the role(s) above the booty role. Booty won’t kick anyone with a higher than his own. Note: users with admin privileges won’t be kicked or listed as being kicked.

Please note

Booty can only kick members after being on your server for a while. For example, to remove inactive members after 60 days, it will work 60 days after he arrives at your server.
Booty uses intents for kicking, the use of slash commands, and the “Server Members Intent” to update his database. He was extensively tested by other devs and normal users on test servers. If you find bugs, kindly join his support discord and let us know.
Drawings were ordered from the artist “alifia”. You may not use them without her written (and paid for!) permission. You can find her on Fiverr. She’ll be happy to work with you if you need any cartoonish avatar.
The bot is hosted on a reliable server, so he can handle all requests and is available 24/7.

Developer Information

Booty was mainly developed by Benjamin Terweiden.
The bot was built with:

pycord 2.5.0 (latest stable release)
aiomysql (a real database server)

Here’s the changelog from Booty V3:

Mobile optimization: messages are formatted differently when the slash command user is on a mobile device when writing the command (this only works when a user is not invisible).
Booty is now verified for the privileged guild presence intent. This allows him to see user status and Discord client type being used (app/mobile/browser). However, he doesn’t store or display this info to users, only to adjust displayed messages.
The content sent by Booty was spell-checked and edited by native speakers, resulting in polished and error-free content.
The help command now includes information about /diagnose.
The /diagnose command now works correctly with forum channels and their permission settings. This wasn’t the case in V2 because the permissions for sending messages are named differently for forum channels, meaning it displayed missing permissions for those even when working correctly.
The code was optimized and reorganized. Database queries are now handled with a connection pool, making it more responsive with decreased delay and increased reliability.

The Official Tutorial!