Content Log error appears when spawning certain entities

I would like to add some details based on my testing.

According to the 1.21.130 release notes, the attack_interval field of the behavior.nearest_attackable_target component was modified to support range_min and range_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:

[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).

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_interval in a behavior pack using the following code prevents these log messages from appearing:

"attack_interval": {
  "range_min": 1,
  "range_max": 1
}

"attack_interval": {
  "range_min": 1,
  "range_max": 1
}

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_interval was unintentionally affected by the 1.21.130 change mentioned at the beginning.

I hope this additional information helps with diagnosis and reproduction.

This error fills up the Bedrock Dedicated Server log file as well (Ubuntu BDS version 1.21.131.1)

Dec 29 12:10:22 SandraDesktop bedrock_server[270777]: [2025-12-29 12:10:22:106 INFO] [Json] minecraft:piglin | minecraft:behavior.nearest_attackable_target | minecraft:piglin | For entity piglin, "attack_interval" is disabled (max <= 0); goal will fall back to "scan_interval" (ticks).
Dec 29 12:10:22 SandraDesktop bedrock_server[270777]:
Dec 29 12:10:22 SandraDesktop bedrock_server[270777]: [2025-12-29 12:10:22:107 INFO] [Json] minecraft:piglin | minecraft:behavior.nearest_attackable_target | minecraft:piglin | For entity piglin, "attack_interval" is disabled (max <= 0); goal will fall back to "scan_interval" (ticks).
Dec 29 12:10:22 SandraDesktop bedrock_server[270777]:
Dec 29 12:10:31 SandraDesktop bedrock_server[270777]: [2025-12-29 12:10:31:855 INFO] [Json] minecraft:hoglin | minecraft:behavior.nearest_attackable_target | minecraft:hoglin | For entity hoglin, "attack_interval" is disabled (max <= 0); goal will fall back to "scan_interval" (ticks).
Dec 29 12:10:31 SandraDesktop bedrock_server[270777]:
Dec 29 12:10:32 SandraDesktop bedrock_server[270777]: [2025-12-29 12:10:32:205 INFO] [Json] minecraft:piglin | minecraft:behavior.nearest_attackable_target | minecraft:piglin | For entity piglin, "attack_interval" is disabled (max <= 0); goal will fall back to "scan_interval" (ticks).
Dec 29 12:10:32 SandraDesktop bedrock_server[270777]:
Dec 29 12:10:40 SandraDesktop bedrock_server[270777]: [2025-12-29 12:10:40:755 INFO] [Json] minecraft:hoglin | minecraft:behavior.nearest_attackable_target | minecraft:hoglin | For entity hoglin, "attack_interval" is disabled (max <= 0); goal will fall back to "scan_interval" (ticks).
Dec 29 12:10:40 SandraDesktop bedrock_server[270777]:
Dec 29 12:10:41 SandraDesktop bedrock_server[270777]: [2025-12-29 12:10:41:705 INFO] [Json] minecraft:piglin | minecraft:behavior.nearest_attackable_target | minecraft:piglin | For entity piglin, "attack_interval" is disabled (max <= 0); goal will fall back to "scan_interval" (ticks).

Thanks for posting this, Simon — this matches exactly what I’m seeing on both Windows and Linux BDS.

This confirms the issue is platform-independent and tied to the 1.21.130 engine change to minecraft:behavior.nearest_attackable_target.attack_interval.
Vanilla mobs like piglins and hoglins never defined attack_interval, so the fallback logic is now broken and emits this log every tick.

On large servers this log spam causes extreme disk I/O and has already led to LevelDB corruption for multiple operators, including myself.

Defining:

"attack_interval": { "range_min": 1, "range_max": 1 }

"attack_interval": { "range_min": 1, "range_max": 1 }

in behavior packs suppresses the issue, which strongly indicates this is a Bedrock engine regression and not addon or server misconfiguration.

— Dgtyhy

Hi @ika, this is @Dgtyhy.

I’ve been doing extended testing on this issue and I can now confirm that this is not caused by addons, plugins, or world corruption, but by a core Bedrock engine regression introduced in 1.21.130.

The change that modified minecraft:behavior.nearest_attackable_target.attack_interval to require range_min / range_max appears to have unintentionally broken the fallback logic used by vanilla mobs that never defined attack_interval at all (e.g. zombies, skeletons, creepers).

As a result, these mobs now continuously emit the log:

“For entity X, attack_interval is disabled (max <= 0); goal will fall back to scan_interval (ticks).”

This log is produced every tick per affected mob, which at scale causes extreme disk I/O pressure on Bedrock Dedicated Server, leading to LevelDB compaction failures and eventual database corruption.

Explicitly defining:

"attack_interval": {
  "range_min": 1,
  "range_max": 1
}

"attack_interval": {
  "range_min": 1,
  "range_max": 1
}

in behavior packs prevents the issue entirely, which strongly indicates that the fallback logic itself was broken in 1.21.130 rather than the data definitions.

This is therefore a Bedrock engine bug and not a server/operator configuration problem.

Thanks for continuing to investigate this — this regression is currently impacting large production BDS servers.
— Dgtyhy

myself and many other bedrock server owners are having this issue with the console spamming and causing lag/tps drops