> For the complete documentation index, see [llms.txt](https://bygonespoofer.gitbook.io/bygonespoofer-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://bygonespoofer.gitbook.io/bygonespoofer-docs/using-the-spoofer/spoofing-modes.md).

# Spoofing Modes

Under **1. Spoofing** you'll find four modes. Pick based on the kind of ban you're dealing with.

```
    ─────────────────────────────  Spoofing  ──────────────────────────────

        1. Recommended   (traces + MAC, no HWID)   <-- start here
        2. Full Spoof    (HWID + MAC + EDID + traces)
        3. Light Spoof   (MAC + EDID + traces)
        4. Reverse       (undo changes / restore backup)
        0. Back

    [?] Select an option:
```

## 🟢 1. Recommended — *start here*

**Changes:** Trace cleanup + MAC address. **No HWID/SMBIOS changes.**

The safest option and the one you should try **first**. It clears local traces and randomizes your MAC without touching low-level hardware identifiers, so there's no risk of destabilizing your PC and no HWID reset needed for your executor.

> Use when: you got soft-banned or just want a clean slate to continue playing.

## 🔴 2. Full Spoof — *hard ban only*

**Changes:** HWID (SMBIOS UUID + serials) + MAC + EDID + traces.

The "hard spoof". This rewrites deep hardware identifiers via AMIDEWIN. Use it **only** if a Recommended spoof didn't lift a genuine hardware ban.

{% hint style="warning" %}
⚠️ A Full/hard spoof can destabilize some systems and **will throw off any script or executor that uses HWID to detect multiple devices** — you'll need to do an **HWID reset in that executor after every hard spoof**. Read the full [Hard Spoof Warning](/bygonespoofer-docs/warnings/hard-spoof.md) before using this.
{% endhint %}

## 🟡 3. Light Spoof — *soft ban*

**Changes:** MAC + EDID + traces. Skips the SMBIOS/HWID rewrite.

A middle ground: more than Recommended, but without the risky HWID changes.

## ♻️ 4. Reverse — *undo*

Restores your MAC to default and, if you made one, restores your hardware IDs from the backup file. Use this to roll back any changes.

## 📊 Quick comparison

| Mode            | Traces | MAC | EDID | HWID/SMBIOS | Risk      | Try when           |
| --------------- | :----: | :-: | :--: | :---------: | --------- | ------------------ |
| **Recommended** |    ✅   |  ✅  |   ❌  |      ❌      | 🟢 Low    | First, always      |
| **Light**       |    ✅   |  ✅  |   ✅  |      ❌      | 🟡 Medium | Soft ban persists  |
| **Full**        |    ✅   |  ✅  |   ✅  |      ✅      | 🔴 High   | Confirmed hard ban |
| **Reverse**     |    —   |  ↩️ |  ↩️  |      ↩️     | 🟢 Low    | Undo everything    |

## ➡️ Next

See a mode in action → [Full Walkthrough](/bygonespoofer-docs/using-the-spoofer/walkthrough.md).


---

# 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 dynamically by asking a question.

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

```
GET https://bygonespoofer.gitbook.io/bygonespoofer-docs/using-the-spoofer/spoofing-modes.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.