minecraft: 1.12.2
forge: 2654
spectrite: 1.6.5
fancy block particles: 2.3.9

Game randomly crashes, seems to do with one of the skeletons spawning and shooting an arrow. I believe this might have to do the fancy block particle mod's interaction with your mod's particles, assuming that the arrows do have a trail when they are shot. What the mod does it renders all particles (supposed to be just when breaking a block, but yes it does override all particles unless they are custom made like embers) as cubes instead of a 2D square. My guess is that the mod didn't know what do do when the particles got rendered.

report: here, via the server

Thank you for being so detailed. I can't really fix this now as my computer is in for repair but I'll get to it eventually.

So, to just give a small addition to this crash, if you use the latest version (1.12.2-2.2.8-91) of blood magic and use the turret array ("- The Turret Array:
> Place an array on top of an inventory with arrows and then place a bow and an arrow in the array. The array will target enemies greater than 3 blocks away and less than 32, using any arrows in the inventory." To quicken the bug find.) and give it any type of arrows, vanilla tipped or just arrows seem to produce the crash, you can get it to crash after like 5 arrows have been shot at mobs.

I think there's a bug with your looting hook. any non-mob thing that kills things is missing a check or something.

PMDescription: Ticking entity
java.lang.ClassCastException: weather2.entity.EntityMovingBlock cannot be cast to net.minecraft.entity.EntityLivingBase
at com.samuel.spectrite.eventhandlers.SpectriteGeneralEventHandler.onApplyLootingLevel(SpectriteGeneralEventHandler.java:749)
at net.minecraftforge.fml.common.eventhandler.ASMEventHandler_505_SpectriteGeneralEventHandler_onApplyLootingLevel_LootingLevelEvent.invoke(.dynamic)
at net.minecraftforge.fml.common.eventhandler.ASMEventHandler.invoke(ASMEventHandler.java:90)

It seems that's the case, yes. For the record, I still don't have my computer to fix this.

@greenking13 I am now fixing this issue. Were you getting the same stack trace as was originally posted or something different?

I am going to close this issue since the new build addresses the original issue. If there are any related crashes, please create a new issue for them.