Scaling Health

Scaling Health

23M Downloads

(Incompatibility) Ticking Entity Crashes

Coraline77447 opened this issue ยท 1 comments

commented

Hi, I'm experiencing some incompatibilities with this mod and Guard Villagers mod which causes the guard villagers to become ticking entities whenever scaling health mod is installed and getting too close to a village both vanilla and modded villages from Repurposed Structures mod.

Btw my minecraft java edition version is 1.16.4, forge version is 35.1.28, mods versions for both of them are: Guard Villagers 1.1.8, Scaling Health 4.0.1 +1, and SilentLib 4.9.0+63. Also I have OptiFine but OptiFine ain't the one causing this problem.

So can you please make both this mod and Guard Villagers mod compatible? (Btw I've already reported this same thing to Guard Villagers mod so that if they agree with the compatibility agreement for both this mod and Guard Villagers mod to be compatible with each other without ticking entities (btw when the guard villagers becomes ticking entities I would kill them via kill command (/kill @e[type=guardvillagers]) which I don't like doing that to the guard villagers but it's either them or me...) (btw sorry for this report not looking the way you want it to be but this ain't a bug report.. This is a incompatibility report as well as a crash report...)

UPDATE: The owner of Guard Villagers has said to me that their mod isn't what's causing my issue, its Lost Trinkets mod that's causing the ticking entities. Your mod and Lost Trinkets doesn't like each other cause lost trinkets is possibly hard-coded to the vanilla health system for some of it's trinkets while your mod slightly modifies the health system which lost trinkets mod doesn't like at all and causes ticking entities... I probably shouldn't play with this mod and Lost Trinkets or else there'll be ticking entities which I don't want any ticking entities....

commented

if this is still an issue, please test again using the latest version, remove optifine even if it isnt causing the issue, use a paste site to for the debug.log file after you encountered the bug (doesn't have to be just after)