> For the complete documentation index, see [llms.txt](https://cesium.gitbook.io/cesium-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://cesium.gitbook.io/cesium-docs/modules/misc/name-protect.md).

# Name Protect

Hides or replaces player names and skins on your screen for streaming.

Hides or replaces player names and skins on your screen for streaming.

## What it does

Name Protect changes what you see, not what others see. It hides or fakes the names and skins of players on your client so a stream or recording does not expose them. Nothing is sent to the server.

## When to use it

Use it when recording or streaming and you do not want your own name, your friends' names, or your opponents' names on screen.

## Settings

You can adjust these in the module panel:

* Replace your own name
* Replace other players' names
* Hide skins
* Replacement text

## Video

{% hint style="info" %}
A short clip of this module is on the way.
{% endhint %}


---

# 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://cesium.gitbook.io/cesium-docs/modules/misc/name-protect.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.