Steps to Reproduce:
Go to Settings > Creator and enable Content Log GUI
Set GUI Log Level to Inform or Verbose
Open a world
Spawn an entity that can attack other entities
Observed Results:
The following content log error appears:
[Json][inform]-minecraft:entity_name | minecraft:behavior.nearest_attackable_target | minecraft:entity_name | For entity entity_name, "attack_interval" is disabled (max <= 0); goal will fall back to "scan_interval" (ticks).
Expected Results:
No content log errors should appear.
Notes:
This issue does not occur in 1.21.121.
Screenshot:
I would like to add some details based on my testing.
According to the 1.21.130 release notes, the
attack_intervalfield of thebehavior.nearest_attackable_targetcomponent was modified to supportrange_minandrange_max.However, many vanilla mobs do not define
attack_interval. As a result, the game now generates log messages like the one shown in this report:This log message appears continuously for many entities, such as zombies, skeletons, and creepers. I tested this issue in the following environments:
Minecraft for Windows 11
BDS for Windows
BDS for Linux
Explicitly defining
attack_intervalin a behavior pack using the following code prevents these log messages from appearing:Additionally, mobs that already have an attack_interval (such as cave spiders) do not display an error log message.
This suggests that the fallback logic for entities that do not define
attack_intervalwas unintentionally affected by the 1.21.130 change mentioned at the beginning.I hope this additional information helps with diagnosis and reproduction.