Skip to content

GitLab

Closed
Created by Soumyakanti Roy@smyaknti

MythicMobs-5.0.0-alpha1 throwing excessive NullPointerException in Console but Mobs and Spawners work as intended.

Summary

The main issue is MythicMobs-5.0.0-alpha1 version is spamming the server console at the rate of about 20 NullPointerExceptions per second with no way to supress them. Server log files are generating at 10 MB/hr and the console is practically unusable.

Console Spam

Steps to reproduce

Server version: git-Tuinity-"dc9d19c" Link here MythicMobs version: 5.0.0-alpha1 (free version test release) Fresh Install of MythicMobs

  1. Disable Random Spawns (this is how I keep in my server, but it happened while randomspawns were enabled as well)
  2. Set any mob to not despawn in their properties (here the default Skeleton King mob worked as well)
  3. The whole plugin will work, no server lag or anything just the console will spam the following error: Could not pass event EntityDamageByEntityEvent to MythicMobs v5.0.0-SNAPSHOT-5145f853 java.lang.NullPointerException: Cannot invoke "io.lumine.xikage.mythicmobs.mobs.MythicMob.getDespawns()" because the return value of "io.lumine.xikage.mythicmobs.mobs.ActiveMob.getType()" is null or something similiar (The NullPointerException Remains persistent as the details of the mob in the ActiveMobs.yml file has no data of its type.)

Current behavior

The server console is basically unreadable and DiscordSrv is delayed by upto 4 hours due to it not being able to keep up with the log spam.

Another thing that I found is the /mythicmobs mobs listactive command shows the mobs with the errors:

Entity errors

The UUIDs return nothing and I cannot even find or kill those entities from minecraft. I even disabled global spawning of spiders from world guard regions, still it was persistent. I am unable to narrow it down further than this.

Intended correct behavior

Describe what you think should happen instead of the bug.

Debug log snippet

Common Error Snippet

Proposed fixes

I suppose supressing the console spam would be sufficient as of now as the plugin behaves as intended and there are no memory leaks as well.

Additional Comments

In case of anything needed, feel free to ask, I shall cooperate with the same.