Direct answer

DAB slows more distant mobs, but the configured interval prevents eligible AI brain work from being delayed indefinitely. A value of 20 corresponds to about one update per second at 20 TPS; larger numbers permit slower updates, not higher FPS.

How to check it

  1. Check that DAB is enabled and mobs are far enough from players for it to apply.
  2. Compare targeting, villager reactions and farm timing before adjusting the limit.
  3. Check that the issue is not caused by the separate activation range or by chunk unloading.

What to change

Change one interval in the existing config, not the entire DAB block:

dab:
  max-tick-freq: 20  # 20 ticks is ~1 second at 20 TPS

Reduce the number for more responsive distant behavior, or consider a higher number only after establishing that AI cost is the bottleneck and gameplay remains correct.

Compatibility and safety

The explanation is based on Pufferfish’s documented DAB algorithm; no universal “best” limit is safe for every plugin/farm combination or newer fork.

Software and version notes

The Pufferfish Host knowledgebase is historical configuration documentation. Check current pufferfish.yml and the changelog of your exact Pufferfish build before applying example values.

Verify the result

At the same player distance, compare observed AI response intervals and tick cost. Return to the previous value if AI appears frozen.

References