Invite tracking
Who invited whom, invite leaderboards, fake/bonus accounting and cache synchronisation — the utility submodule.
Invite tracking is a submodule of the utility module. Enable the utility module, then the submodule:
,enable module utility
,enable submodule utility invitetrackerFrom then on every join is attributed to the invite that carried it, and vanity URL usage is tracked when vanity tracking is on.
Commands#
| Command | Permission | Purpose |
|---|---|---|
,invites [@member] | — | Invitation totals for you or another member (aliases ,myinvites, ,invitestats) |
,inviter @member | — | Who invited a member, and which code was used (aliases ,whoinvited, ,invitedby) |
,inviteleaderboard | — | Top inviters by net invites (aliases ,topinvites, ,ilb; limit 1–25, default 10) |
,inviteconfig … | Manage Server / Administrator | Configuration subcommands |
,invitesync | Manage Server / Administrator | Force re-sync the invite cache from the Discord API |
The leaderboard explains its arithmetic in the footer: net = regular + bonus − left − fake.
How counts are computed#
- Regular — joins attributed to a normal invite that are still members.
- Left — joins attributed to the member who have since left.
- Fake — accounts younger than the configured threshold (default 3 days, 0–30) when they joined.
- Bonus — manual adjustments via
,inviteconfig bonus @user <amount>(amount clamped to ±1000).
Configuration#
Dashboard (inside the utility module's module page) or ,inviteconfig:
| Setting | Purpose |
|---|---|
| Log channel | Optional channel for join/leave/invite events |
| Fake threshold days | 0–30, default 3 |
| Vanity tracking | Attribute vanity-URL joins |
,inviteconfig status prints the current settings; ,inviteconfig channel #logs sets (or clears, with clear) the log channel.
When the numbers look wrong#
Invite attribution is only as good as Discord's invite list. If someone created an invite and it was deleted, their attribution can decay. ,invitesync rebuilds the local cache from the API — run it after bulk invite cleanup, and remember the bot needs Manage Server to read the full invite list.