> For the complete documentation index, see [llms.txt](https://docs.otherside.xyz/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.otherside.xyz/platform-documentation/creation/unreal-development/features-and-tutorials/player-entity-visibility.md).
# Player / Entity Visibility
By default, every player (and Morpheus entity with a render target) in a world is visible to every other player. Visibility can be controlled globally from the server, or locally by each client.
## Local (Per-Client) Visibility
Individual clients can hide specific players locally, while having no effect on other clients, by using either the `MorpheusActorRenderTargetComponent::SetHiddenLocally` or `MorpheusActor::SetHiddenLocally` nodes (the MorpheusActor variant just calls through to the component).
`SetHiddenLocally` must be called on the client, and has no effect if called on the server.
Visibility is managed entirely by the client, based on your gameplay logic. The render target stays loaded, but the character meshes are hidden.
Hiding is managed with a tagging system. All default meshes will be hidden, but if you have manually added additional meshes to the render target actor you will need to add the `MorpheusCharacterMesh` tag to your mesh component. Any meshes without the tag will not be hidden.
## Server (Replicated) Visibility
Morpheus entities can be hidden globally by using the `ServerSetEntityHidden` node.
`ServerSetEntityHidden` must be called on the server, and has no effect if called on clients.
This is replicated, and causes the render target to be fully unloaded on every client EXCEPT the authoritative client for that Morpheus actor. This can be used for shadow-banning players - their own client is unaffected, but the player entirely disappears from all other clients.
Combine it with `SetHiddenLocally` if the intent is to also hide the player on the authoritative client.
---
# 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.otherside.xyz/platform-documentation/creation/unreal-development/features-and-tutorials/player-entity-visibility.md?ask=&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.
