> For the complete documentation index, see [llms.txt](https://edseries-plugins.gitbook.io/p/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://edseries-plugins.gitbook.io/p/eddungeons/essential/zones/visibility-handlers.md).

# Visibility Handlers

### Overview

Zone visibility handlers are system components that control player visibility within mob zones. These handlers determine which players can see each other when they occupy the same zone.

### How Zone Visibility Works

When players enter a zone, the active zone visibility handler processes the player list and applies its specific visibility rules. These rules determine:

* Which players are visible to other players
* Which players remain hidden from view
* How the visibility state is maintained as players join or leave the zone

### Available Handlers

Currently, these are the available **zone visibility handlers**:

#### `default-zone-hiding`

**Behavior**: Hides all players from each other within the same zone.

This handler implements complete player isolation within a zone. When active, no players can see any other players, regardless of how many players are present in the zone. Each player experiences the zone as if they were alone.

***

#### `random-10-players`

**Behavior**: Makes only 10 randomly selected players visible to each other, while hiding all remaining players.

This handler creates a limited visibility environment where only a subset of players can interact visually. The 10 players are selected randomly from all players in the zone.

***

#### `all-players-visible`

**Behavior**: Makes all players in the same zone visible to each other.

This is the most open visibility handler, where every player in the zone can see every other player. No hiding or filtering is applied, providing full transparency of all zone occupants.


---

# 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://edseries-plugins.gitbook.io/p/eddungeons/essential/zones/visibility-handlers.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.