> For the complete documentation index, see [llms.txt](https://docs.signcod.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.signcod.com/sign/english/additional-guides/play-safely-in-cod.md).

# COD Safety

The testing sequence and follow-up options in the Thunex guide.

<mark style="color:$primary;">**SIGN · GUIDE**</mark>

## Testing sequence <a href="#steps" id="steps"></a>

{% stepper %}
{% step %}

### Start with a test account

This guide starts with a free Call of Duty account such as Warzone rather than the main account. It uses ESP only or light settings for **5–10 matches**.
{% endstep %}

{% step %}

### Follow the launch order

Start the software first and let it fully load before opening the game, as the product guide describes.
{% endstep %}

{% step %}

### Review the result

Close the game and software after the test. This guide suggests checking the account after about **10 hours** and continuing to observe for **24 hours** for a ban or shadow ban.
{% endstep %}

{% step %}

### If an issue appears

This guide lists a Windows reinstall from USB or a cleaner as follow-up options, then repeating the test on a free account. It notes that a cleaner is not fully reliable.
{% endstep %}
{% endstepper %}

## Follow-up options <a href="#options" id="options"></a>

{% tabs %}
{% tab title="Windows reinstall" %}
This guide links to this reinstall video and names Windows 10 Pro. Review the video and file backup requirements before making system changes.

{% embed url="<https://www.youtube.com/watch?v=WaFxvUmsNWs>" fullWidth="false" %}
{% endtab %}

{% tab title="Cleaner" %}
This guide describes a cleaner as a quicker option, with no guarantee of success.
{% endtab %}
{% endtabs %}

{% hint style="warning" %}
These are the observations and timings in this guide. A test without account penalties does not guarantee future account safety. If a problem appears, send the details to support rather than assuming its cause.
{% endhint %}

## Profile notes <a href="#profile" id="profile"></a>

This guide recommends keeping the light profile rather than a full profile after testing.

<a href="/sign/english/games/modern-warfare-4.md" class="button secondary" data-icon="arrow-right">Choose your game to find its profiles</a>

## Need a hand? <a href="#support" id="support"></a>

<mark style="color:$secondary;">**SIGN SUPPORT**</mark>

The Sign team is here to help. Open a Discord ticket and include the page name, the step you reached, and a screenshot of the issue so we can help you more clearly.

<a href="https://discord.gg/siin" class="button primary" data-icon="discord">Get help on Discord</a> <a href="https://www.signcod.com/ar" class="button secondary" data-icon="globe">Visit Sign Website</a>


---

# 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.signcod.com/sign/english/additional-guides/play-safely-in-cod.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.
