sebastiaanyn / open-sourcebot Goto Github PK

Let's discuss the language choice for the bot here. Some options would be:

• Java
• JavaScript
• Python
• Kotlin
• Golang
• C#
• Rust

Please comment which language you would prefer, and the library you would want to use.

Describe the bug
https://github.com/The-SourceCode/Open-SourceBot/blob/63d2ca63e403fa496582f6f37a2bb3ee4f6ef46b/src/handler/Handler.js#L183
https://github.com/The-SourceCode/Open-SourceBot/blob/63d2ca63e403fa496582f6f37a2bb3ee4f6ef46b/src/handler/Handler.js#L195

When running command, any specified to it aliases will not work in any way.

To Reproduce
Steps to reproduce the behavior:

1. Command !help has aliase !h
2. By executing !h you will see that nothing happens.

Expected behavior
It should execute same code that !help does

Screenshots

Additional context
Add any other context about the problem here.

Let's discuss the bot features here.

• Which commands would you want to have in the bot?
• Should the bot be designed to work on one guild, or multiple?

Provide as much information as possible, so we can get a good understanding of the ideas and opinions.

Describe the bug
A clear and concise description of what the bug is.

When i try to add new feature (games)
const { Feature } = require("../../../handler");

module.exports = class extends Feature {
constructor() {
super("Игры", {
name: "Игры",
commands: ["rolldice","flipcoin","slots"],
events: []
});
}
};

Commands not appear in feature

how can i organize commands by category in help.js?

Describe the bug

https://github.com/The-SourceCode/Open-SourceBot/blob/ae60b017713c3c0635aca7fd6823bf58520c7754/src/handler/Handler.js#L59-L66

The code above silently ignores errors thrown while trying to instantiate a Command or Event class. The try/catch clause can't determine whether the error is thrown because CommandOrEvent is not a class, or because it gets errors while instantiating it.

To Reproduce
Steps to reproduce the behavior:

1. Create a Command class and give one of the options a wrong datatype.
2. When the application starts an error will be thrown and ignored.

Expected behavior
There should be an error to show the Command is invalid, and it shouldn't silently ignore them.

RichEmbed is not a constructor

TypeError: RichEmbed is not a constructor at module.exports.run (/home/pixel/Desktop/Fl4nnelBot/modules/general/commands/help.js:93:19) at Client.client.on (/home/pixel/Desktop/Fl4nnelBot/handler/Handler.js:209:19) at Client.emit (events.js:198:13) at MessageCreateAction.handle (/home/pixel/Desktop/Fl4nnelBot/node_modules/discord.js/src/client/actions/MessageCreate.js:31:14) at Object.module.exports [as MESSAGE_CREATE] (/home/pixel/Desktop/Fl4nnelBot/node_modules/discord.js/src/client/websocket/handlers/MESSAGE_CREATE.js:4:32) at WebSocketManager.handlePacket (/home/pixel/Desktop/Fl4nnelBot/node_modules/discord.js/src/client/websocket/WebSocketManager.js:386:31) at WebSocketShard.onPacket (/home/pixel/Desktop/Fl4nnelBot/node_modules/discord.js/src/client/websocket/WebSocketShard.js:436:22) at WebSocketShard.onMessage (/home/pixel/Desktop/Fl4nnelBot/node_modules/discord.js/src/client/websocket/WebSocketShard.js:293:10) at WebSocket.onMessage (/home/pixel/Desktop/Fl4nnelBot/node_modules/ws/lib/event-target.js:125:16) at WebSocket.emit (events.js:198:13)

Is your feature request related to a problem? Please describe.
You should easily be able to find the commands that the bot has. The current help command isn't well suited for this task.

Describe the solution you'd like
There should be a help command which can take in zero or one parameter.

If the command is used without any parameters it should return a message (embed?) listing all features, followed by the commands apart of the feature. If a command is not apart of a feature it should also be included separately.

If the command is used with a parameter a message should be returned showing the aliases, info, and usage of the command and whether it's only available inside guilds.

If you want to implement this feature request, please open a draft pull request which references this issue.