Jakye

Hello @thephilluk , I've been thinking about adding this feature for a while now but besides the normal OAuth2 you're gonna have to also configure a Bearer token to log...

Hello @thephilluk, Right now I don't have the necessary free time to work on this feature, and I'm sorry about that. I can assure you that it has all the...

I've abandoned the idea of creating a Discord bot with an express API since I can hit Discord's API directly using the bot's access token. The next issue is that...

Discord added an "Interactions Endpoint URL" which allows the package to receive interactions through HTTP rather than a bot user. This solves the roles sync issue.  I'll have to...

Apparently, the "Interactions Endpoint URL" I mentioned earlier can only be used to receive interactions (e.g. slash commands), not events. (e.g. role added) Creating a slash command in the Discord...

I've implemented a prototype in #44. It is still a work in progress and testing is needed. If anyone is interested in testing it, here are the steps: - Create...

Thank you @SrPeterr for giving it a try. Seems like the issue is that the [2023_04_06_101123_add_roles_to_users_table.php](https://github.com/JakyeRU/Larascord/blob/feature-guild-roles/src/database/migrations/2023_04_06_101123_add_roles_to_users_table.php) migration did not run properly. I tested the migration on my MariaDB server. Are...

I have removed the default value for the column `roles`. It should allow you to run the migration now.

Yes, the first one is the ID of the guild, and then the ID(s) of the role(s).

In the next update, the bot and its access token will no longer be used to get the user's role. By requesting the OAuth2 permission `guilds.members.read` and hitting the endpoint...