Hey there,

 

Throughout the years I worked on many entities and spawning systems but one problem seems to often arrise: users report their global mob spawns being reduced.

 

So I made a new system and voila, I receive the same complaints on day-one of release. So I am obviously missing an essential point of mob spawning.

 

In my current iteration I have a vanilla-inspired spawning system that uses an event to trigger, shown here: https://github.com/Daveyx0/MultiMob/blob/master/main/java/net/daveyx0/multimob/spawn/MMWorldSpawner.java

(all other relevant files are in the parent "spawn" package). It grabs spawn entries from configs to create spawns, but that presumably has nothing to do with my issue. It works (seemingly) completely seperate from the vanilla version of the system; yet it appears to affect it anyways. Reason for using this system is essentially the option to input my own conditions for spawning on a mod-basis-level and for flexibility.

 

I looked around in the source code for MC and was not able to detect a clue on why my code would hamper the spawning of vanilla mobs. In fact, it always APPEARS to work fine in dev environment, but users then report something completely different.

 

My question here essentially is if people know about a common mistake I'm running into (like a complete newb) or if there is something else at play here. Or am I cursed? Having a hard time with this one.

 

Thanks in advance!

 

Daveyx0

 

Edited December 18, 20186 yr by Daveyx0

Thanks for the response, diesieben. (Nice to see you are still at it on these forums :P ) Yes, I do use countEntities, but I use it to limit the spawn of that specific entity class, not ALL mobs. I received reports of modded mobs also spawning less and I cannot even check for those classes so I find it hard to believe that that would be the issue... I'll try to remove it when I get home from work and see, but I doubt it's the problem.

 

If you find anything else suspicious, please let me know. I'm still stumped.