Closed Kirottu closed 2 years ago
Can you test with vanilla serenity on the next branch (what poise uses, cargo docs) whether the guild is shown as unavailable in the Ready event too?
The latest serenity version on the next branch switched to a new Discord API version (v10), which might be the cause of your problem
That does seem to be the issue yes, after getting my project to compile for the next branch it gives the same UnavailableGuild output and I can not run any of the commands.
And I pressed the wrong button. Good job me.
Can you create an issue on the serenity repository? This issue seems to be outside poise's control
Yeah I guess I will do that, thank you anyway! Now closing for real.
That is about it, the
Ready
value inuser_data_setup
which I presume could be used for a ready function to report that the bot has logged in, has the guild I am testing in reported as unavailable like this:With the serenity standard framework this worked fine. Also it is not only slash commands that do not work, I can not use the
register
provided by examples orhelp
.