danktuary / rinon Goto Github PK

Once the DB rewrite gets pushed, add a command that allows users to rename their currently pending requests, because of typos and casing and whatnot.

Dunno how I didn't notice this earlier, but blob requests can still pass the filter if they're formatted like BlobSomething or bLOBsomething and stuff like that. Just add the i flag to the regex, I suppose.

I see it all too often - An emote that gets used gets removed and replaced.

Keep track of the amount of times emotes are used. Maybe even give an option to auto replace the least used emote with an emote of choice.

Since all the DB data has been successfully moved, the old polls can be moved/deleted/hidden.

Things like "There was an error trying to execute that command" and "There was an error trying to create that poll" are pretty vague and not helpful. Would be nice if it displayed the error message under it.

Tiny thing, but sometimes requests get made as >request :designatedName: :actualEmoji:, because users sometimes forget to remove the colons around it (myself included), so it'd be a nice addition if the RequestTransformer class accounted for this. This would affect all transformations except the .fromEmoji() method.

Make sure to add a test for this as well.

Once the DB rewrite gets pushed, add a command that allows users to cancel their currently pending requests.

Might be a good idea to have the add command work from anywhere. Just have the bot fall back to whatever server has free space or make the server settable by the owner.

As an addition, upon adding a new emoji you could tell the user in which server it was posted if it's not the same one they used the command in.

Because this is juuuuust a bit misleading.

Self-explanatory image:

Basic idea:

Implement a check on submission which searches the client's emojis collection for an emote with the same name as the one being requested. If one exist and belongs to an emoji guild, post the emoji + the guild name and ask the user to compare, hinting that it might be a duplicate upload.

As it checks the client's emojis collection, this would act as a "global" dupe check for all emoji servers, not just the one it's being requested on.

Currently not entirely sure how to implement this, but a command to preview how an emoji would look would be pretty nice. For gifs, either try to find a gif resizer API or send two messages with a temporary emoji.

In addition, it'd be nice to let them know about files larger than the max size limit. Could still create the preview itself, but would add a message above the previews.

Would be nice to see the name of the emoji in here:

Things like disabling the default notification settings that everyone always complains about, moving channels where they belong, deleting the default voice channel, etc.