> ## Documentation Index
> Fetch the complete documentation index at: https://docs.purpify.host/llms.txt
> Use this file to discover all available pages before exploring further.

# Troubleshoot Bedrock server lag

> Identify server, network, or client lag and reduce load on a Purpify Minecraft Bedrock Edition server.

First determine whether the delay affects everyone, one connection, or one device. Lowering random settings will not fix client frame-rate or network problems.

| Lag type    | Common signs                                                                        |
| ----------- | ----------------------------------------------------------------------------------- |
| Server-side | Mobs, blocks, commands, and movement delay for everyone.                            |
| Connection  | One or several players rubber-band or time out while the server continues normally. |
| Client-side | One device loses frames while other players and server ticks remain normal.         |

## Check server-side load

1. Read the [console](/panel/console) for watchdog, scripting, add-on, save, or resource warnings.
2. Check whether the problem started after installing an add-on, enabling an experiment, uploading a world, or changing a game rule.
3. Test during similar player activity after each change.
4. Inspect busy areas for excessive entities, ticking blocks, redstone, command blocks, farms, or add-on scripts.

## Adjust Bedrock properties

Stop the server and create a [backup](/server/backups) before editing `server.properties`.

| Property                                         | Performance effect                                                                                       |
| ------------------------------------------------ | -------------------------------------------------------------------------------------------------------- |
| `tick-distance`                                  | Controls how far from players the server continues world simulation. Lower values reduce ticking work.   |
| `view-distance`                                  | Controls the requested chunk view distance. Lower values reduce world loading and network traffic.       |
| `max-threads`                                    | Controls server worker-thread behavior. Leave it unchanged unless Purpify provides a specific value.     |
| `compression-threshold` and compression settings | Affect network CPU and bandwidth tradeoffs. Keep the existing values unless diagnosing a specific issue. |

Change one setting, restart, and compare the same area under similar player load. See [Bedrock server properties](/bedrock/server-properties) for the supported settings.

## Isolate add-ons and experiments

Restore the backup made before the problem when possible. Otherwise, disable the most recently added pack or experiment, restart, and retest. Do not remove several packs at once because dependencies can make the result unclear.

<Warning>
  Removing a behavior pack can damage or remove custom entities, blocks, items, and scripts already saved in the world. Test on a backup copy.
</Warning>

## Check connection and client lag

* Confirm that affected players use the correct address and port.
* Compare players on different networks before assuming the server is overloaded.
* Ask one affected player to test without local resource packs and background downloads.
* Check whether only one device has frame-rate problems in the same world area.
* Review the [Purpify service status](https://uptime.purpify.host) for an active incident.