captainkidd5 / devexchangebot Goto Github PK

The Program.cs file contains the following comment:

// TODO: The client class shouldn't be public, but there are
// compatibility issues with the role menu system if we make
// this private. This needs fixing.

This problem is created due to the usage of the Program.Client in RoleMenuModel.GetAllEmojis(). This should be fixed, as outlined in the comment, it is bad practice to have the DiscordClient object staticly availably.

I'll be taking care of the virtual pet feature of the bot!

I'd like to make something, so people are able to quote messages using links.

Greetings, I'd like to try my luck with developing the Self-service Role Assignment System.

Hi, I'd like to work on the levelling system.

I'll get my hands on this heart board. Wish me luck!

The DSharpPlus version the bot is currently using is 4.1.0-nightly-00930. Recently, stable version 4.1.0 has come out which provides the same features without using the nightly build sources. The problem here is that the nightly sources seem to have become unavailable making it impossible to compile and run the bot anymore.

My suggestion would be to switch from the nightly build to the stable 4.1.0 version of DSharpPlus. It comes with the same features without the hassle of having to add additional NuGet sources to pull in the right packages. The bot is stable as-is, so nightly build sources would not be needed at this point.

Rafe needs a streak counter B)

The RoleMenuModel.cs class contains the following comment:

// DiscordEmoji.FromName() doesn't work with Unicode
// and DiscordEmoji.FromUnicode() doesn't work with Custom Guild Emojis
// So we have to do this stupid thing where Unicode emojis have no ID and Guild Emojis have no Unicode
// and when getting the Role we check if the RoleBind id is 0
// if it is then we yoink it via DiscordEmoji.FromUnicode() otherwise DiscordEmoji.FromGuildEmote()

// If anyone wants to fix it => I wish you good luck.

This seems to depend on the way Discord is handling emojis. There got to be a better way to fix this... Maybe there's a way to introduce a permanent solution to this problem that can be used consistently throughout the codebase?