run1e / acebot Goto Github PK

Title says it all. It happens from time to time that somebody opens a help channel (usually they trigger the ‘anti-cheat’ message) and then just decide to delete their message (or maybe Staff does). In this case the channel just lingers around for 30 minutes.
If it's not too big of a deal, I would like to see it close automatically in this case. I guess there would have to be a check that there are no other non-bot messages in the channel. Not sure.
That's all!

license good, ace should have a license rather than be proprietary.

Now that the codebase is formatted with black, there should exist some sort of mechanism to enforce new code is formatted with black. One can use pre-commit for this, plus pre-commit.ci in order to have automatic lint on every commit locally, and automatic lint on every pull request and commit.

(I personally don't use pre-commit.ci much as I like having more control and running it in github actions, but for this project, it seems like a better option)

If !w [location] returns multiple possible results, reply with them in a numbered list, and respond with the correct location at the response of a number.

I'm not sure if there's a good way to describe the title, but its when a channel is claimed the entire channel list will bounce around. Its annoying since it happens quite often, however there's an easy solution to the problem.

As proven on the Python Discord, if a channel position is not provided in the edit when switching categories, they will not bounce around. This does mean that when channels are moved they will always default to the bottom of the category. This should cause less channel bounce.

Affected Lines:

If this is approved I can make a fix and submit a pull request myself.

The !del command would delete the last message A_AhkBot posted on behalf of the person who says "!del". I.e. to correct mistakes when highlighting code with !hl [code].

👋

I also will be contributing to this bot as well :)

In some cases, unmuting a user does not always clear the record in the database that a user was temporarily muted.

I've narrowed it down to be a cause of having a is_bot check when updating the database.

There's two possible solutions. One solution is to prevent muting bots, which I am personally against. The other solution is to remove the check for if the member is a bot when unmuting them.

instead of using commands.Bot use commands.AutoShardedBot for better connection and faster response time

There's not a good way to view which avatar you want to view. I propose either a subcommand or a new command to explicitly choose. The current one does the display avatar, so a subcommand might be more beneficial. Of course, adding a subcommand for the per-server avatar would be nice too, in case someone has the same name as the subcommand.

When someone responds with .ask in #general, either with a ping or at a slow time of day, the asker may see the message much later. The suggested channels may have been claimed, and the newcomer just doing what they were told accidentally asks in the wrong place a second time.

Ace should store a queue of tuples containing old message IDs, suggested channel 1, and suggested channel 2. When a channel is claimed, Ace should edit the next queue item to instead point to #how-to-get-help until neither of the next queue item's suggested channels are the just claimed channel.

Cannot find locations, especially after bugging it for a while