Wesley1808

Does this still happen when you set `optimizations.reduce_sync_loads` to false? And is this on Forge or Fabric?

Oh wait, this is probably a duplicate of #62 with different configuration which was fixed with commit https://github.com/Wesley1808/ServerCore/commit/03c993e9b3823d63b39e999c7d9cb5c4f946b01f I will probably backport 1.3.7 to 1.19.2 soon since its still used...

The results are indeed a bit different, but there's a very high chance its caused by the same patch. I haven't noticed anything else that could cause that and it...

Looks like a compatibility issue with `Minecraft-Water-Erosion` Setting `optimizations.cancel_duplicate_fluid_ticks` to `false` in the config (its default value) should work around this.

I don't see any error related to servercore or reason for any crash in that log. Just a reference to having created a crash report. Could you attach that crash...

They should be affected by it. There are some exclusions though, like when the item entity is moving around it gets temporary immunity to it, preventing tons of item entities...

I would recommend testing it with [Spark](https://spark.lucko.me/) to see what's causing the lag.

I've just tested this myself with 1562 item entities. Inside activation range it took ~43mspt, outside ~6.4ms.

Its very possible this was caused by https://github.com/Wesley1808/ServerCore/commit/c106bb26f5c49d8720a7daf16b079f2758594906 as items were sometimes keeping horizontal movement in *many* decimal numbers. My original test on this was with items spawned in through...

Regular natural monster / animal spawning is already capped by vanilla's own mobcaps. These work in pretty much the same way you suggested - by limiting the amount of mobs...