Cogs for the RED-based Homelab Discord server bot.
This is a joint project involving any of the Homelab Discord admins, moderators, and community members that would like to get involved.
A number of people have contributed to this project: Members of the moderation team, former members of the moderation team, and members of the wider community.
A massive thank you to all who've helped out with this project ❤️
- AutoReact: React to specific phrases with one or more emotes.
- AutoReply: Automatically replies to messages that match a trigger phrase.
- Convert: Converts any unit to any another unit.
- Enforcer: Allows you to enforce certain characteristics on a channel.
- Feed: This allows users to feed each other.
- Google: Send a google link to someone.
- LaTeX: Render a LaTeX statement.
- Notes: Manage notes and warnings against users.
- Penis: Allows users to check the size of their penis.
- Purge: This will purge users based on criteria.
- Quotes: Allows users to quote other users' messages in a quotes channel.
- Reactrole: Allows roles to be applied and removed using reactions.
- Report: Allows users to report issues.
- Roleinfo: Displays info on a role
- Verify: Allows users to verify themselves.
- xkcd: Allows users to look at xkcd comics.
This cog allows mods to add auto reactions to certain phrases.
[p]autoreact
This cog automatically responds to messages that match specific trigger phrases, set by admins.
[p]autoreact
Converts any unit to any another unit.
[p]convert
This cog allows you to enforce certain characteristics on a channel.
[p]enforcer
There are numerous attributes than can be used to restrict messages/content into a channel.
While some attributes are available in discord via role-based permissions, sometimes a bot may be better off enforcing content in a pinch.
[p]enforcer configure <channel> <attribute> [value]
Example:
[p]enforcer configure #channel enabled true
| Attribute | Type | Description |
|---|---|---|
enabled |
bool |
Whether to enable enforcements on a channel |
minchars |
int |
How many characters a message must contain to be allowed into the channel |
notext |
bool |
The sent message must have no text, i.e. should be an image-only message |
requiremedia |
bool |
The sent message must contain an attached image |
nomedia |
bool |
The sent message must not contain an attached image |
minimumguildage |
int |
How old a server member must be part of the guild, in seconds, before they are able to contribute to the channel |
minimumdiscordage |
int |
How old a member's discord account must be, in seconds, before they are able to contribute to the channel |
An example enforcement would be a channel to show off server pictures. In which case, you could allow members to post a set of images with a description of their setup.
In which case, the following would be appropriate
[p]enforcer logchannel #admin-log
[p]enforcer configure #serverpics requiremedia true
[p]enforcer configure #serverpics minimumguildage 600
[p]enforcer configure #serverpics minchars 20
[p]enforcer configure enabled true
This cog allows users to feed each other.
This cog allows users to send google links to each other.
[p]google <query>
This cog allows users to display complex mathematical information using LaTeX renderings.
[p]latex <latex statement>
Manage notes and warnings against users.
[p]notes
[p]warnings
Notes can be used for long-term storage information of problematic users or for future reference.
When listing the notes of a user, the warnings will be prioritised as they will be deemed more important.
It is possible to add notes to a user who has left or not yet joined. Notes are stored against a user's ID and do not require the user to be part of the server.
Deleting a note does not actually delete the note. It simply marks it in the datastore as deleted and does not show it in normal use. This can allow future recovery of notes (using the restore subcommand) if a bad party is attempting to wipe existing notes.
Notes and warnings can be edited using the edit subcommand.
This cog allows users to check the size of their penis.
[p]penis <user>
This cog will purge users that hold no roles as a way to combat accounts being created and left in an un-verified state.
[p]purge
-
[p]purge schedule "0 */6 * * *"- It is possible to run the purge on a schedule. By default, it is disabled, but configured for0 */6 * * *which is a crontab for every 6 hours. E.g. will run at00:00,06:00,12:00and18:00every day. -
[p]purge minage 5It will attempt to prune users that hold no roles, that have been part of the server for at least<minage>days (default to 5).<minage>can be altered to fit your server's requirements to ensure that people that joined but never verified, are not clogging up mention lists and to keep activity ratios high.
By default, purge's schedule is disabled and must be enabled to prune unverified users.
-
[p]purge simulate- It's possible to do a simulated purge by running[p]purge simulate. This will retrieve the list of users it would prune, had it run as normal. This allows moderators to test out configuration without performing any permanent actions. -
[p]purge exclude @Sneezey#2695- If a user does not hold any roles for any reason, but you wish to exclude them from the purge, it is possible to add this user to theexcludelist. This action can also be undone with theincludesubcommand. -
[p]purge status- To check how many users have been purged any other configuration items, the status command allows you to see the values in an easy-to-see embed.
This cog will allow members to add quotes to the quotes channel easily.
[p]quote
Allows roles to be applied and removed using reactions.
[p]reactrole
This cog will allow members to send a report into a channel where it can be reviewed and actioned upon by moderators.
-
[p]reports logchannel #admin-log- For reports to be able to be taken, a log channel must be set which will receive an embed upon a user using the report command. -
[p]reports channel [allow|deny] [channel]- Disallow thereport/emergencycommands to be used in certain channels -
[p]reports confirm [true|false]- When a report is issued, this sets whether the bot will DM the user with confirmation or not -
[p]report [message]- A report can be sent to the logchannel for any moderators to see and action upon when they are ready. -
[p]emergency [message]- An emergency can be requested which will ping all members in the configured logchannel if they are online.
Allows you to view info on a role
[p]roleinfo <role>
This cog will allow users to prove they're not a bot by having to read rules and complete an action. They will then be given the verified role if they can complete this.
[p]verify block <user>- Add the specified user to the verification blocklist.[p]verify channel <channel>- Set the channel in which the cog listens for verification attemps.[p]verify logchannel <channel>- Set the channel in which the cog logs verification attemps.[p]verify message <message>- Set the verification string (e.g.I agree to the rules.[p]verify role <role>- Set the role to which users are added upon successful verification.
Further configuration options can be seen with [p]verify help
This cog allows users to look at xkcd comics
[p]xkcd <comicnumber>
All code in this repository is licensed under the GNU General Public License version 3.
Copyright (c) 2018-2020 tigattack, contributors and original authors.
The CI will fail unless your code is PEP8 compliant.
pip install -r requirements-ci.txt
isort . # This will fix the order of imports
black . # This will auto-format and fix a lot of common mistakes
pylint * # This will show general pep8-violationsIf you use VSCode you can use the tasks integrated into the repo to locally run the same tasks as our CI
When suggesting changes, please open an issue so it can be reviewed by the team who can then suggest how and if the idea is to be implemented. When submitting changes, please create a pull request targeting the develop branch.