Direct answer
The current configuration documents separate search-radius.acquire-poi and search-radius.nearest-bed-sensor values, plus a different spawn-iron-golem.radius feature. Do not mix them.
How to check it
- Inspect the generated villager section and identify which search path is relevant: POI acquisition, nearest bed detection or golem spawn check.
- Reproduce the issue with a village that has known beds, job sites and golem spawn conditions.
- Profile villager AI in a busy village before editing any radius.
What to change
- Test only the radius tied to the demonstrated problem, preserving the generated defaults as a rollback point.
- Avoid shrinking search ranges so far that villagers cannot find their intended beds or job sites.
- Treat the golem spawn radius and related limit as a separate gameplay configuration, not as this setting.
Software and version notes
Compatibility and safety
Purpur’s current config describes acquire-poi and nearest-bed-sensor separately. Verify exact YAML nesting in the build-generated file before copying keys across Minecraft versions.
Verify the result
Re-test villager bed claiming, job-site acquisition, iron golem spawning and MSPT; if behavior worsens, revert.