Last updated: September 30, 2026 · Category: Guide · Editorial review · About the authors
Key Takeaways
- Discovering fake invites is a specific, bounded problem: exclude the confirmed accounts, not a reason to reset the whole leaderboard.
- A full reset punishes every legitimate inviter alongside the one who farmed, which is a worse outcome than a targeted correction.
- Recovery and prevention are two separate steps: cleaning up what happened, then setting a threshold so it does not happen again.
Finding out a leaderboard was farmed after the fact is unsettling, but the fix is narrower than it feels in the moment. A farming incident is a confirmed case of disposable accounts joining specifically to inflate an invite count for a reward, distinct from an ordinary drop in retention or a one-off suspicious join that turns out to be nothing. This is the sequence that resolves a confirmed incident without overcorrecting.
Step 1: Confirm the Scope Through an Audit
Before changing anything, audit the join timeline to establish exactly which accounts were involved and how large the problem actually is. A leaderboard that "feels farmed" because one inviter jumped unexpectedly is often a much smaller issue than it first appears, sometimes a single burst from one source rather than a systemic pattern across many.
This step matters because the natural reaction to discovering any farming is to distrust the entire leaderboard, when the actual scope, confirmed through an audit, is usually much narrower than that instinct suggests.
Step 2: Exclude the Confirmed Fake Joins, Nothing More
Once the audit identifies which specific joins were farmed, exclude exactly those from the leaderboard and any pending rewards. Resist the temptation to reset the whole leaderboard to zero. A full reset erases the real, legitimate history of every other inviter along with the fake one, which is a disproportionate response to a problem that, once confirmed, is usually limited to a specific account or small cluster of accounts.
A targeted exclusion is also fairer: a member who genuinely recruited 30 real invites over months should not lose that record because someone else farmed a leaderboard position around the same time.
Step 3: Decide on Moderation Action Separately
Whether to ban the accounts involved, or address the person behind them if identifiable, is a moderation decision distinct from the leaderboard fix. Discord's own guild ban action, retrieved 2026-09-30, is the mechanism if a server chooses to act on it, but the technical correction to the leaderboard does not depend on that decision being made first, or made at all.
Step 4: Set a Threshold So Recovery Does Not Repeat
An audit and cleanup fix what already happened. They do nothing to prevent it from happening again. This is the point at which an account-age anti-fake threshold sized to the server's actual reward stakes should go in, if it was not already active before the incident. Without this step, the same recovery process is likely to repeat around the next reward announcement.
Why the Targeted Approach Holds Up
A server that responds to a farming incident with a full reset sends an implicit message that no invite history can be trusted. That message discourages exactly the members who were recruiting legitimately. A targeted correction, confirmed by audit and limited to the accounts actually involved, fixes the specific problem without treating every real contributor as a suspect.
Frequently Asked Questions
Should I reset my entire invite leaderboard after finding fake invites?
Usually not. A full reset also erases every legitimate inviter's real history. Excluding the confirmed fake accounts and leaving everything else intact is more accurate and fairer to real contributors.
Should I ban the accounts used to farm invites?
That is a moderation decision separate from the leaderboard fix. Many farming accounts are already inactive or disposable, so banning has limited effect beyond making the intent explicit and preventing reuse.
What if the person who farmed invites is a known, otherwise-trusted member?
That is a moderation and trust decision the leaderboard fix does not make for you. The technical cleanup, excluding the fake joins, applies the same way regardless of who was behind it.
How do I stop it from happening again?
Set an account-age anti-fake threshold matched to your actual reward stakes going forward. The recovery fixes what already happened; the threshold prevents a repeat.