Bots be access to see the Join Method #6674
Replies: 6 comments
|
I think you are very right. The code written for such a system needs to be simpler and more stable. We are now in a period where many servers are making their own special systems, and it seems ridiculous that such a code, which should be very simple, is so complex. According to what you said, the fact that it is not stable is a big problem. |
|
I do agree with this 100%, and I've created my detailed feature request going over on how to properly do that and some examples. It shouldn't be this complex to get what invite a member is joining off of, for security purposes to report them or anything like that. With the rise of security updates over the past years, I would assume this would be one of them? |
|
I would love that too |
|
Although I also would love to have that, I never had any issues with my module. And it doesn't care, when the bot joins, or how long he was offline. With the cache_invites() method, he builds his cache with every existing invite. Works like a charm on my own small server. |
|
I don't want to maintenance whole invite cache table just to unreliably see who used what invite, especially the info is already showed in the official app with a much more reliable alternative method, that can be added to bot API in future.
|
|
yeah |
Uh oh!
There was an error while loading. Please reload this page.
With our Discord bots, we need to listen to many events to find out which invite connection a member is using. For example, we listen to the inviteCreate event and save it to the database or cache. Then we listen to the guildMemberAdd event and after the incoming member, we send a request and get the usage of the available invite links, and whichever one is incremented, we say that the user entered through that invite link, but this is a way with a high error rate. If the bot is offline and more than 1 invitation is used, we cannot make an accurate determination.
All reactions