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

​
Check server-side load

  1. Read the 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 before editing server.properties. Change one setting, restart, and compare the same area under similar player load. See 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.
Removing a behavior pack can damage or remove custom entities, blocks, items, and scripts already saved in the world. Test on a backup copy.

​
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 for an active incident.