Direct answer

This Leaf feature aims to reduce movement updates sent for entities. It targets network packet volume, not the CPU cost of mob pathfinding or entity AI itself.

This is a Leaf-specific configuration option, not a general Paper or Folia setting. Confirm the key is present in the configuration generated by your own build before changing it.

How to check it

  1. Determine whether the problem is client bandwidth/packet volume or high server MSPT. Entity movement packets will not fix a heavily loaded tick thread.
  2. Use a repeatable crowd, animal farm or vehicle scenario and observe actual client-side movement and tracking.
  3. Identify disguise, NPC, replay and custom-entity plugins that depend on entity motion updates.

What to change

  1. The option appears as reduce-entity-move-packets inside the reduce-packets configuration block in published Leaf references. Check the generated configuration for your version.
  2. Back up that setting and enable a single controlled test rather than combining several packet- and entity-tracking tweaks.
Rollback first
  1. Copy the current configuration and note the previous value before running a controlled test.

Software and version notes

Published configuration path: performance.reduce-packets.reduce-entity-move-packets.

Reduced packet frequency or selection can affect apparent motion smoothness, position interpolation or plugin-generated entities. It should not be described as a universal TPS fix.

The archived Leaf global YAML documents the 1.21.1 branch; newer official examples differ. Do not copy an older default or missing block into a current server without verifying that release.

Verify the result

Observe moving mobs, boats, minecarts, NPCs and anti-cheat reactions with multiple clients. Compare network use and visible movement quality before deciding whether to keep it.

Keep the A/B test results, server build, config diff and rollback notes together so the result can be reproduced.

References