# Troubleshooting

If something isn’t working as expected, try the quick checks first:

* Refresh the page and reconnect your wallet.
* Revisit your referral link (ensure `?ref=` or a `ref` cookie exists).
* Wait \~10–20 seconds for UI to reflect backend changes, then refresh.
* For `/api/ref/attach`: it only supports **POST** (use `GET ?probe=1` just for debugging).

***

## Open a Support Ticket (Discord)

The fastest way to get help is to open a ticket in our Discord.

1. **Join Discord:** \[DISCORD INVITE LINK]
2. **Create a ticket** in **#support** (or press the “Create Ticket” button).
3. Provide details so we can reproduce quickly:
   * Wallet address (lowercased) and your referral alias (if any)
   * What page/flow you used (Profile, Leaderboard, referral attach, X link)
   * Exact steps to reproduce + timestamps (UTC)
   * Screenshots or short screen recording
   * Browser + OS + device

> **Security:** Never share your seed phrase or private keys. We will never ask for them.

***

## Common Issues

**“Referred by” doesn’t show immediately**

* Ensure you arrived with a valid `?ref=` or `ref` cookie.
* The attach window is limited (default **48h** from first visit). If already attached or window expired, the API returns a specific reason.
* Refresh Profile after a short delay.

**`/api/ref/attach` returns `METHOD_NOT_ALLOWED`**

* Only **POST** is supported. Use `GET /api/ref/attach?probe=1` for a non-mutating check.

**500 on `/api/ref/attach`**

* Usually a race on duplicate insert; the route is idempotent. If you already got `attached: true`, no repeat action is needed.

**XP shows 0 for a new user**

* If the user was created “sideways” (e.g., via referral attach) and never visited Profile, they might not have received the welcome XP yet. Visiting `/api/profile?ensure=1` (via the app) applies the welcome grant.

**Boost math**

* +5% per successful referral (capped at +50%), +10% if your own X is linked. Ranking is still by XP; Boost is a visual indicator.

***

## Still stuck?

Open a ticket on Discord (**#support**) with the details above.


---

# Agent Instructions: Querying This Documentation

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

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://baddies.gitbook.io/baddies/faq/troubleshooting.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.