ninodiscord/butterfly

🦋 Discord API Framework for JDA built in Kotlin

butterfly's Issues

Do not use CoroutineLaunch in the ButterflyClient

Instead, use the Mono API, which is just as rich and is runtime agnostic, hopefully will be executed in the JDA execution thread.

Remove ShadowJar

It just creates issues, and as this library is constantly being worked on there is no need for it.

Release 0.2.1

Update Dokka plugin

Add Interactions

Interactions are a conversation between a bot and one or more users, this will allow us to create more elegant menus.

Interactions are made of steps, and steps point to the next step or to end the interaction.

Adding test helper functions

Developers should not need to invest time in setting up their discord environment for their unit tests.
Butterfly should help users by providing environment building functions and helping developers write less code and achieving more.

Remove printing of the EventManager

Made in the constructor of ButterflyClient.

Move to JDK 11 Only

This is because Nino uses JDK 11, and Kotlin is unstable across multiple JDK versions.

Add stable documentation site

Only catch CommandExceptions

The client currently catches all exceptions and prints errors, let JDA catch all of the non-butterfly exceptions instead.

Fix IDEA failing to resolve classes

Related to https://youtrack.jetbrains.com/issue/KT-25709

Command Nesting and Command Groups

Problem

There can be multiple issues when working with nested commands:

• Permission bypassing
• Complexity of code
• Implementation bugs

Solution

One more class: CommandGroup
This class extends the normal Command and it's some kind of CommandHandler.
It accepts subcommands and a default command (no arguments) in its constructor.
In its execute() method, it works exactly like the CommandHandler, executing the correct subcommand according to its argument.

Move to Discord4J

Instead of using JDA and relying on two libraries: JDA and the jda-reactor library we can rely on Discord4J which is both tested and running on Project Reactor.
Also it has better support for Kotlin, moving should not take very long as the code doesn't rely too much on one library.

Language parameter is not included in the replyTranslate call

See the attached screenshot.

Use stdlib instead of stdlib-jdk8

Sharding support

Add a CommandException for when the bot calls context.reply with an embed and no permissions

Currently, it sends a message. I think that the better way is to let the user handle it as an exception.

MessageChannelExtensions.waitForMessages does not use its predicate.

See the attached screenshot for relevant information.

Add support for multiple owners

Title is self explainitory