> For the complete documentation index, see [llms.txt](https://docs.invitelogger.me/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.invitelogger.me/premium/features/anti-rejoin-system.md).

# Anti rejoin system

A common way to bypass invite tracking during invite leaderboard challenges is through **rejoins**.

#### What is a rejoin?

A **rejoin** occurs when a user leaves and rejoins a server using a different invite to manipulate invite counts.

**Example scenario:**

1. Member A joins using Member B’s invite → B gets **+1**
2. Member A leaves the server → B gets **-1**
3. Member A rejoins using Member C’s invite → C would normally get **+1**

This behavior can artificially inflate invite scores.

***

### Rejoin Detection & Protection

To mitigate this, the **Rejoin System** provides two main features:

#### Rejoin Alert Logs

Receive alerts whenever a user rejoins the server using a different inviter.

* Helps moderators identify suspicious behavior
* Can be configured via:
  * Dashboard
  * `/setlogs` command

<figure><img src="https://1233429419-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-MW_7KWGOtXaonSVC9Jd%2Fuploads%2FMELzyNoCreoYDY1aQf3o%2Fimage.png?alt=media&amp;token=ef6a3b79-db72-43af-a60e-687571955b54" alt=""><figcaption></figcaption></figure>

#### Anti-Rejoin Behavior

Ensures that only the **original inviter** is credited, even if a user rejoins using a different invite.

**Example with anti-rejoin enabled:**

1. Member A joins using B → B gets **+1**
2. Member A leaves → B gets **-1**
3. Member A rejoins using C → **B gets +1 (not C)**

* Prevents invite farming via rejoins
* Can be configured via:
  * Dashboard
  * `/advancedconfig` menu

<figure><img src="https://1233429419-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-MW_7KWGOtXaonSVC9Jd%2Fuploads%2FLEgqnjt0x4lFzHecThS0%2Fimage.png?alt=media&amp;token=ce937353-bcac-49a4-a337-850f4d33c9f8" alt=""><figcaption></figcaption></figure>

You can if you want set a pardon threshold though the same command / menu

#### Anti rejoin fake parameter

Allows you to count rejoin-related invites as fake.

You can setup it:

* &#x20;though the /fakeconfig&#x20;
* Though the security tab of the dashboard


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.invitelogger.me/premium/features/anti-rejoin-system.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.