> For the complete documentation index, see [llms.txt](https://unixx.shop/docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://unixx.shop/docs/games/rocket-league-bot-setup-download-and-installation-guides/choose-a-rocket-league-bot-setup-guide/averia-ai-bot-setup-guides-for-rocket-league/rocket-league-ban-avoidance-guide.md).

# Rocket League Ban Avoidance Guide

Review Rocket League AI bot account-risk guidance, reported ban factors, usage limitations, and the important product disclaimer before playing.

## Rocket League AI Bot Account-Risk Guide

Review these account-risk considerations before using the Averia Rocket League AI Bot. Use only an account you are willing to risk.

{% hint style="danger" %}
If you have been banned before you will need to spoof + clean correctly, please do so following [this guide](/docs/games/hwid-spoofer-setup-download-and-installation-guides/choose-an-hwid-spoofer/averia-temp-spoofer/download-and-install-averia-temp-spoofer.md#install-averia-temp-spoofer).
{% endhint %}

### General advice

* Configure your bot settings **in the main menu only** — avoid adjusting anything in-game
* **Only use the bot on an account you are willing to risk.**

### Performance expectations

* With **Bot ON** (queueing with randoms): → Plays at **GC3 – Low SSL level**
* With **Bot ON + another bot in 2s**: → Plays at **Low SSL – Mid SSL level**

### Important rules

#### Do not toggle mid-game

Do **not** toggle the bot or open the menu during a match.

> This can be detected by **EAC** due to sudden input changes and may result in a ban.

#### Do not tab out or go AFK

If you leave the game running in the background or tab out for extended periods:

> **EAC server-side checks** can detect this behavior and flag your account.

Stay active while the bot is running.

#### Avoid excessive reports

Rocket League uses a **report-based flagging system**:

* The more reports you receive, the higher your risk
* Better / older accounts receive fewer reports
* You can **buy tracker views** to reduce reports and make your account appear more authentic

#### Avoid suspicious account behavior

EAC uses **heuristics-based detection**:

* Fresh accounts + sudden high performance (e.g. 20–0 streaks) = flagged
* You should use:
  * An **aged account**
  * With **legit playtime**
  * Preferably with **existing stats/history**

### Additional account-risk guidance

* Use **in-game chat** to appear human
* **NEVER USE THE BOT ON WANTED / MAIN ACCOUNTS**
* Avoid using:
  * Auto-queue
  * Auto skip replay

These can make your behaviour look unnatural.

### Disclaimer

We cannot guarantee you will never get banned. Bans are not caused by the product itself, but by **how legitimate your gameplay appears**.

* Accounts with history = **lower risk**
* Fresh or suspicious accounts = **higher risk**

The AI is continuously improving its humanization. Currently, only **\~1 in 25 users** encounter issues.

🚨 **Always use the product on an account you are willing to risk.** 🚨

### Frequently Asked Questions

#### Can bans be guaranteed against?

No. The product does not guarantee that bans will never occur.

#### Which account should I use?

Use only an account you are willing to risk.


---

# 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://unixx.shop/docs/games/rocket-league-bot-setup-download-and-installation-guides/choose-a-rocket-league-bot-setup-guide/averia-ai-bot-setup-guides-for-rocket-league/rocket-league-ban-avoidance-guide.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.