INVITE CODE WHEN A USER JOINS!!!!!!!!!
What up boys & girls. I'm looking to have a new object added to the `guildMemberAdd` event, this way we can search the invite code, and add logging for it an such, this would help severely with server raiders, and more protection details!
So essentially, all I'm looking for is Discord to add the invite code a user used when they joined, to the `guildMemberAdd` event.
Please.
-
I would also like this
1 -
Seems like a very nice addon i like the idea
1 -
Yes, this is very much needed! It would be very useful and I think a lot of people will like it.
1 -
I don't really see a need for this, there is already a way to do this, there is no need to fix something that isn't broken
-3 -
This would be ver nice
1 -
I think this was added before but was removed later due to invite reward bots. I think you can still tell on which invite a user joined by keeping track of all invites, and when a user joins, check which one grew by 1. This should still be implemented, since removing it (if it was removed) has no effect on the invite reward bots.
1 -
So you want to know who invited a specific user to your discord server? Don’t worry, this is quite a simple thing to do. By the end of the tutorial, you should be able to figure this out.
-2 -
There is a Discord bot that can track invites, try using this for now.
-1 -
Omfg Sam, do you have ANY IDEA WHAT YOU ARE SAYING.
This is an API related suggestion. This guy makes his own bot and wants an invite code to be added to an event. So stop commenting eveywhere if you don't know what you are taking about.0 -
This is a forum, why do you have to be so rude? I was just suggesting he use this bot 'for now' until he figures it out. Enjoy the rest of your day budddy.
0 -
These are suggestions for API additions, not a promotion form. I'm requesting an API addition, not a second bot for my server.
0 -
Jordan, I'd like to say, the feature that allows us to track what invite code a user joined with IS broken.
This has always been a guessing game, and requires assumptions and trust that the database isn't ever behind (and if it is, requires the bot to manipulate the uses stored to keep it in line with the uses count of each Invite. This is the definition of broken.
At first, my server (at the time had about 5000 users) was using a bot to monitor joins, leaves, and invite creation/deletion, but some data was lacking when it concerned potential raiders and alt accounts, and eventually the bot itself went permanently offline by the creator.
As of November 2021, our server grew to about 8000 users, and I designed an in-house bot that managed many logging and automated functions for our server (including the invites trackers, which also spit out the age of the account and their time spent in our server when they leave). However, there was a bit of a cripple that occurred back then with flooded events occurring: If multiple users join the server around the same second as one another, the bot won't be able to differentiate which user joined at what time - there will be more than one invite that gets increased (even worse if they use the same invite).
Now, My server has over 10K users, and we see raids at least on a monthly basis, and this throws our invite tracker out of whack every time - tons of missed logged data simply because it cannot tell who joined with what code - all we get when that happens is a user that joined (which Discord gives us anyway, but my logs at least tell me how old the account is and how long it spent in our server if they leave).
To The Discord API Developer Team:
If you include the invite code (again) with GuildMemberAdd events, this WILL cut down on API requests of any bot that tracks invite usage. Think about it - Every time a server with 10,000+ members (and usually over 1000 invites) experiences a leave, join, or an invite gets created/removed, the bot must not only tap its storage (usually a database) of the invites it's been tracking, it also must call Guild.invites.fetch() just to deal with counting against the record of invites (and flagging old invites as deleted when they are discovered), not to mention those very thorough bots that also end up having to forceLoad a User Object from the inviter.id because they might not be a member anymore and might not be in a server of the bot where their usercache still has their info... or god-forbid the damn bot suffered a recent restart and literally has NO CACHE and must force-load every member and user (and channel if it is logging/showing that information as to whether those channels still exist or not)...you see how many API requests a single user joining, leaving, or creating/deleting an invite can cause on a large server? This may not be much in the grand scheme of things, but imagine how many invite-tracking bots there are, including in-house bots of large servers, and you might actually see a serious reduction in the load of API requests on a daily basis!
Readding this back has no consequences that aren't already exploitable anyway, and since bot developers need reliability of what invite was used (especially since the Vanity URL invite code isn't part of the invites.fetch() group and has to be checked as an aside or added into the collection before being checked...wasting precious milliseconds on joins causing discrepancies), this would not only significantly reduce the number of API requests of each bot, it will also massively reduce the amount of code the botwriters would need to include just to obtain that information.
So, in short, PLEASE put this property on a GuildMember Object during GuildMemberAdd events!
0
Iniciar sesión para dejar un comentario.
Comentarios
12 comentarios