This mod is causing an excessive amount of beehives to spawn when leaving their beehives.

I've tried with disableEntity.false set to true and false, both showed the same issue.

Here is a crash log from Server Hang Watchdog

latest.log
(I used a kill command you can search for "kill" and find where it took place.)
I experienced the same bee spamming bug with Performant and MCMT installed alongside tons of other mods.
jmt_mcmt-1.16.5-0.22.87
performant-1.16.2-5-3.72m
On performant multiEntities = false
On MCMT disableWorld = true, disableWorldPostTick = true

The crash shows that you have a huge amount of extra mods installed. Did you tried it only with mc-mt and the bees mod just to be safe?

Hello, can you try disable world threading in mcmt config. For me it worked

@NXTler I've determined it's Performant causing this issue. I've disabled the multiEntities config in Performant like the README suggests, but I still am seeing this issue after changing that config.

@Vap0r1ze Regenerate the world and disable world threading in mcmt config as I suggested. It should work just fine.

@KubiRemPL Disabling world threading is a valid workaround for me as well, thank you! It's still a shame I'm left to process all of the worlds on the same thread.

Having the exact same issue

Having the exact same issue

Disable world threading as I sad earlier in this post

Ok this is odd, I'm pretty sure I know what the problem is tho; can you send me a world file with the associated bee bug?

Ok this is odd, I'm pretty sure I know what the problem is tho; can you send me a world file with the associated bee bug?

Sry, but i can't because i deleted those worlds but it seems they spawn from naturally generated bee hives

Hi @Vap0r1ze

Could you please test if the issue persists on latest version (you need to compile it from github). The issue should be resolved...

Could you please test if the issue persists on latest version (you need to compile it from github). The issue should be resolved...

I will try to get around to it in the upcoming week, and I'll let you know then.

I'll try to have a build published properly by the end of the week