Direct answer

Older Purpur builds exposed brain-ticks to reduce villager AI frequency. Higher intervals may reduce CPU work but can make villagers unresponsive, so this is a gameplay trade-off.

How to check it

  1. Verify the setting exists in the mob.villager section or equivalent generated configuration for your Purpur version.
  2. Collect a spark sample near a crowded trading hall and compare with an empty area.
  3. List important behaviors to preserve: bed/POI searches, job assignment, restocking, iron farm operation and breeder movement.

What to change

  1. Do not apply a copied value from another version; use the generated default as baseline.
  2. Test one modest change on a staging world and watch actual villager behavior for multiple day/night cycles.
  3. If tick cost is elsewhere, undo the change and investigate the profiler finding instead.

Software and version notes

Compatibility and safety

Historic documentation shows default interval 1 and notes that larger values slow brain logic. Current builds may rename or remove this key; confirm against a build-matched generated purpur.yml.

Verify the result

Compare profiler AI cost with villagers completing normal work, restocking and farm routines. Any gameplay breakage outweighs small tick-time savings.

References