Direct answer
A DAB exclusion does not remove mobs, alter spawn caps or force chunks to stay loaded. It tells DAB not to reduce update frequency for listed types. This can protect farms that rely on distant targeting, but also restores additional AI CPU cost.
How to check it
- First reproduce the problem with DAB enabled, then disabled, on a test copy. If behavior does not change, investigate another system.
- Identify the specific entity type involved instead of exempting every mob.
- Confirm the syntax accepted by your Pufferfish version and keep a copy of the old YAML.
What to change
The published Pufferfish documentation illustrates a list of entity identifiers:
dab:
blacklisted-entities:
- villagerAdd only the affected type. If there is no measurable improvement, remove the exclusion and inspect pathfinding, activation range, chunk loading or plugin changes.
Pufferfish and Leaf may differ in identifier capitalization and configuration nesting. This example follows the Pufferfish Host documentation; use names accepted by your generated config.
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
Check that the chosen farm or NPC behavior recovers, then compare the added AI cost under a representative player load.