polyhaze / volte Goto Github PK

Currently, it just adds without checking: https://i.greemdev.net/b9tu4i9ff4c53yj.png

https://i.greemdev.net/kcrw1dpc3i8lhjt.png

Currently, it's in every command that you need to add a permission check. Let's migrate that to a custom precondition.

Example: https://docs.stillu.cc/guides/commands/preconditions.html#example---creating-a-custom-precondition

The readme references Midnight when the bot is actually called Adora

currently it shows it in year-accuracy, e.g. "one year ago" which isn't very informational. This issue suggests that it be changed to show months and days maybe.

the event is still hooked properly..... but the command isn't.

will be in 2.3.1.

https://imgur.com/a/IXRcdJ9

regardless of the DeleteMessageOnCommand server setting.

currently, it doesn't, which adds extra work for anyone using the command.

This will add:

• Config option to choose whether or not you want this functionality enabled.
• Separate object; to specify if you want this enabled, the Channel ID, etc.
• Show the amount of users/bots.
  • If there's more bots than users, ping the bot owner for potentially malicious activity.
• Show the Guild name, for use in the ForceLeave command if you don't want the bot in that guild.

Now that I know how Microsoft.CodeAnalysis.CSharp.Scripting works, let's put it to use!

title

https://i.greemdev.net/psmkbwad51epcmm.png

How did I overlook this?

PingChecks has a command to set the value, but not a Service to handle the moderation.
Command: https://github.com/GreemDev/Volte/blob/rewrite/Volte/Core/Modules/Admin/PingChecksCommand.cs
Services: https://github.com/GreemDev/Volte/tree/rewrite/Volte/Core/Services

Currently, the Confluence Documentation has all of Volte V1's commands documented. I'll add commands that are missing to V2, as well as rewriting them (of course).

This would allow for less repeating code, and generally easier to write code while being functionally identical.

When you do a poll and the question (the first option in the list) is longer than 256 characters an exception will be raised because the poll question is used as the title for the returned embed which is limited to 256 characters

Proposed solutions:

• Move the question in the description and make the individual answers fields
• Add a check for character limit and warn user about the question (or answers) being too long thus giving a more user friendly experience

This would make the Help command a little bit more user-friendly, as well as reduce support requests for command argument syntax.

Greem can't code if his life depended on it

The Abyss bot has been renamed once again - the readme currently has it down as Zelda, one of the previous names, yet it appears it has been renamed again to Midnight.

Currently it does regardless, which might not be good for announcements.

The current logger is very bland and uninteresting. Let's change that, shall we?

Similar to Rapptz/RoboDanny; this would allow for placeholders as well so you can mention the user calling the tag, etc.

https://i.greemdev.net/t56u8qaitptv3s7.png

This doesnt affect the actual URLs they lead to, it's just an eyesore.
https://i.greemdev.net/rllp5fawzlucuh0.png

https://github.com/GreemDev/Volte/blob/rewrite/Volte/Core/Extensions/HttpExtensions.cs#L9

Title.

Let users know how to setup Volte.

If it can't send a PM, get a list of the channels, grab the first one, and send it there along with an @ to get their attention.

Currently, it's the old SIVA header. Let's change that.

the release of V2 us upon us!

• when i am at my pc next, i will check every command for consistency, an example would be leaving out a role check in an admin command.
• test a majority of the commands and services
• fix what needs to be fixed
• this means that Volte will have a public version again

This was deprecated, as I discontinued my Patreon.
https://github.com/GreemDev/Volte/blob/rewrite/Volte/Core/Data/Objects/Server.cs#L27

Some commands, like Ban, require the bot to have given permissions (BanMembers in this case). There's no checks for those permissions in the code and the bot can end up DMing a member saying they were banned even though such action wouldn't be able to take place.

All commands such as the Ban command should try/catch DMing the user as it may fail, if the user has disabled messages from guild members.

plzfix

https://i.greemdev.net/ybziuvxztijmd14.png

It also replaces {UserTag} with their full username#discrim, and not just their discrim.