General Info

• I am running a modpack
• I can reproduce this issue consistently
  • In single player
  • In multiplayer
• I have searched for this issue previously and it was either (1) not previously reported, or (2) previously fixed and I'm having the same problem.
• I am crashing and can provide my crash report(s)
• I am using the latest version of the mod

Client Info

• Minecraft Version: 1.12.2

• Forge Version: 14.23.5.2768

• Mod Version: 1.6.5

• Java Version: 1.8.0_111 64 bit

Issue Description

Server crashes whenever a Minotaurus is spawned

Reproduce Steps

Spawn a Minotaurus

Additional Information

https://pastebin.com/w0pxVWE3 <--crash log

Changed config for Minotaurus spawn to zero and ran fine. Teleported to an area that had Minotaurus before the crash and server crashed upon arrival. Downgraded back to 1.6.4 and no crash around them.

same here

This is a ticking entity issue. It is usually caused when upgrading versions on dedicated servers. (Refer to issue #78 for reference).

The only way to solve this is to remove the entity in question.

I cannot recreate this issue. I managed to spawn them in both using a Monster Egg and naturally;

(A skyblock map with the Minotaurus spawn rate set to 1,000,000)

maybe my report will help
crash-2018-10-10_22.35.52-server.txt

Same here, confirming problem.

General Info

• I am running a modpack
• I can reproduce this issue consistently
  • In single player
  • In multiplayer
• I have searched for this issue previously and it was either (1) not previously reported, or (2) previously fixed and I'm having the same problem.
• I am crashing and can provide my crash report(s)
• I am using the latest version of the mod

Client Info

• Minecraft Version: 1.12.2

• Forge Version: 14.23.4.2705

• Mod Version: 1.6.5

• Java Version: 1.8.0_181

Issue Description

Server crashes whenever a Minotaurus is spawned

Reproduce Steps

Spawn a Minotaurus

Additional Information

crash log -> https://hastebin.com/qufopacice.cs

Please read the comment above; it is a ticking entity issue.

You need to remove the mob in question from the chunk it is located in.

This issue should have been resolved with the 1.6.6 update and further concluded with the 1.6.7 update.