Track who joined through what invite.

Planejada

Comentários

35 comentários

  • Vasp

    This would be awesome, but something like this is already possible to be created with a bot using discords current API https://discordpy.readthedocs.io/en/latest/api.html#invite

    When a user joins the server you can scan through the uses of each invite searching for the most recent changed and trace it back to the user that created said invite.

    11
  • Noah.DW

    Lmao ive been trying to get this to happen for so long like, i wanna be able to see who made the invite and who used it when

     

    5
  • megannnjay
    There are bots like Invite Manager which will allow you this functionality
    5
  • megannnjay
    I believe this is available in the API as bots like Invite Manager exist
    0
  • Sea.

    It will be a very nice feature!

    7
  • xRokz

    yeb

     

    1
  • BulzyKrown

    Yeah!

    0
  • chloroform chloe

    Discord
    Bots
    Already
    Do
    This
    THAT
    IS
    WHY
    BOTS
    CAN
    ACCESS
    THE
    API

    -52
  • megannnjay
    I hope eventually that's something we don't need a bot to see, but in the meantime there are bots like Invite Manager which can log who users were invited by and stuff like that
    4
  • chloroform chloe

    People have made similar suggestions to this literally HUNDREDS of times, ffs just do a quick search you aren't the first. Use a bot, they're MADE to extend functionality.

    -45
  • Frosty
    Not a bad idea. It might prevent new users to raid server.
    3
  • Giraffesyo

    How would Discord know who sent them the invite, if you have public invites?

    -5
  • webb

    Let me put it this way (and I will be editing this in) the method is what matters.

    If a user were to click on an invite in a message it would expose who wrote said message for example.

    -2
  • sugden

    to an extent, this can already be done, as other comments have stated, you can use bots to track which invite goes up when a user joins, or, if a raid is in progress, simply check the invites, and keep refreshing and see which one(s) are going up, not to say i don't approve of this though

    -2
  • Selim

    Sadly the implementation on the bot side is messy as well and can get confused (in theory as the bot grows) as it needs to watch which invite usage counter has increased and if many users join at once, that can get messy.  The Discord API doesn't give join information directly when a user joins, which is unfortunate and would make for a great addition to the API.

     

    14
  • MagicSword89

    Discord staff, can this be implemented yet? I haven't come across one small server owner/admin/mod who doesn't want to know this

    3
  • null_Zer0

    While this is already technically possible by tracking invite usage count (which doesn't work if 2+ people join at the same time), it would be 1000x better if a join event reported the invite used.

    3
  • cannot we add to audit logs?

    2
  • espen

    Hey Nelly,

    If we're not going to see this as a feature on the Discord client, why not build it into the API so that we can track these types of things accurately?

    Take a look at this suggestion. If an Invite Code is returned in the GuildMemberAdd event, it puts an end to the choppy motion of our currently available Invite Tracker bots. Enabling a ~100% accurate overview of the following:

    • Who's responsible for the raids*
    • Who is participating in the raids*
    • The number of participants
    • The invite associated with the raid

    This sounds like the best solution to me. What do you think?

    *Any invite code can be used, it doesn't have tho be the raiders' invite. Also, non-raiding users can join through the same Invite Code -- but this really isn't too relevant to my comment.

    Cheers,

    Charm

    6
  • Yourself

    Here's a bot that might help.

    https://top.gg/bot/409875566800404480 

    1
  • Exode Pendragon

    The thing a lot of you aren't entirely realizing is that we aren't looking for a bot solution in these suggestions; they're appreciated and probably already known about, but bots are a temp fix of extended functionality that can very well be unreliable in uptime, and that can be very devastating to some servers, targetted or not. 

    At this time of writing, I stumbled upon this thread because Invite Manager is suffering a big outage, and has had some outages in the past few weeks - as has other bots, due to Discord's change in bot limits - which can't be helped.

    6
  • MagentaRV

    Personally, I'd like a reliable way to do this as well.  Not to track who invited whom or raids, but instead to be able to have my bot assign roles and welcome users in their native language based on which server invite they used.  For example, I have multiple language channels in some of my larger servers and it'd be great to be able to say `Bonjour et bienvenue dans le {GuildName}!` and assign the @Français role on join with the invite for the #fr channel.

    3
  • Hopskotch

    It's so far beyond time to have this very small feature added to the API sets. A bot is not the answer -- particularly with Discords clouflare problems lately or even local issues to the bot causing missed joiners.

    A simple Invite code added to the guild members event would be fine. Even if it was the last one used only.

    It's been years and work is ongoing for discord --- can't we address this little feature??

    -1
  • RoboCoonie

    I don't care about which user did what. I want to know which particular invite code was used by a user when they joined. I have several out for specific purposes and sharing since only my mods can create links. And I want to be able to add roles accordingly if someone came in from XXXXXX code that I posted only on my FB, or if they come in from YYYYYY they're my friends and get that role accordingly. InviteManager doesn't seem to help me in this aspect.

    3
  • Emax

    Any update on this?

    2
  • cspotcode

    I would like the API to include a "joined_via" field on each member of a server, which has the ID of the invite they used to join the server.  The API already tells us the date and time when a member joined a guild, but it does not tell us the invitation that was used.

    Alternatively, the "invite" resource can be extended to expose a list of the members that used it to join.  It already includes the number of times it has been used and the member that created it, but not the members that used it.

    Suggesting that bots can reliably implement this feature is incorrect.  For example, if 2 users join at the same time via 2 different invites, a bot is unable to associate the users to the invites.

    5
  • xerof

    Why this still hasn't been implemented given the reasons why 3rd party applications don't always do a good job blows my mind. I find it very difficult when something happens and I need to track down which user invited others, even with bots that sometimes miss data.

    2
  • rav_kr

    Why it's still not implemented after two years 🤦‍♂️

    0
  • osumariokartman

    it'd be really swell if this were something we could have as server moderators.  I'm assuming that discord knows what link was clicked when the user joined the server, so it'd be great if that info was just in the audit logs instead of having to deal with semi-reliable 3rd-party bots.

    2
  • 4am

    Yeah this is something that should 100% be part of a moderator's toolkit. Users invite burner accounts to brigade and spew hate speech, and then abandon their burners and it's hard to be certain if the invite was created for that purpose or not.

    Sure they can just use a public invite for open servers but we're not talking about MENSA members here.

    Also not everyone wants to rely on a third party (or even self-hosting). Who's to say that data is reliable? Who's to say the bot will not be offline and miss something? If discord is serious about user safety this should be a core feature.

    (EDIT: I should add that I also agree with this being supported through the API as well, for anyone who wants to use a bot for their management.)

    4

Por favor, entrar para comentar.