# Network Proximity Checker

{% hint style="danger" %}
**Network Proximity Checker is Obsolete - use** [**Spatial Hash**](/docs/manual/interest-management/spatial-hashing.md) **or** [**Distance**](/docs/manual/interest-management/distance.md) **Interest Management instead.**
{% endhint %}

The Network Proximity Checker component controls the visibility of game objects for network clients, based on proximity to players.

![](/files/-MUNa1tYU4VgHzOsvs3w)

* **Vis Range**\
   Define the range that the game object should be visible to observers.
* **Vis Update Interval**\
   Define how often (in seconds) the game object should check for observers entering its visible range.
* **Check Method**\
   Define which type of physics (2D or 3D) to use for proximity checking.
* **Force Hidden**\
   Tick this checkbox to hide this object from all players.

With the Network Proximity Checker, a game running on a client doesn’t have information about game objects that are not visible. This has two main benefits: it reduces the amount of data sent across the network, and it makes your game more secure against hacking.

This component relies on physics to calculate visibility, so observer game objects must also have a collider component on it.

A game object with a Network Proximity Checker component must also have a Network Identity component. When you create a Network Proximity Checker component on a game object, Mirror also creates a Network Identity component on that game object if it does not already have one.

Scene objects with a Network Proximity Checker component are disabled when they're out of range, and spawned objects are destroyed when they're out of range.


---

# Agent Instructions: 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:

```
GET https://mirror-networking.gitbook.io/docs/manual/components/deprecated/network-proximity-checker.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.