Direct answer
This option limits AI processing for mobs that are not aware. It is different from turning off AI for every entity and from the separate inactive goal-selector optimization.
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
- Check whether plugins, spawn systems or commands create mobs with awareness disabled, and whether those entities dominate the profiling sample.
- Test the difference between a passive display mob and a naturally spawned hostile mob that still needs targeting and navigation.
- Record affected mob types and the specific behaviors that matter for your server.
What to change
- Look for skip-ai-for-non-aware-mob in the generated performance configuration and confirm the actual build supports it.
- If you change it, make a backup and test both intentionally non-aware mobs and normal gameplay mobs.
- Do not treat this key as a replacement for controlling excessive active entity counts.
- Copy the current configuration and note the previous value before running a controlled test.
Software and version notes
Published configuration path: performance.skip-ai-for-non-aware-mob.
Mob awareness is an implementation/API property; skipping AI work for non-aware mobs does not imply all mobs freeze or all navigation runs asynchronously.
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
Check decorative mob displays, plugins that set awareness, spawning behavior, normal combat AI and profiler samples. Restore the old value if plugin-created mobs behave unexpectedly.
Keep the A/B test results, server build, config diff and rollback notes together so the result can be reproduced.