Bug Closed · Resolved

Mobs Despawn After Server Restarts

#3385 opened by Unknown 3 years ago

Upvote 3
Unknownreported this bug

Mob Configuration: [Legacy attachment omitted]

Versions: Mythic Mob Version: 5.1.4 (FREE) Paper Server Build 192 Minecraft Version 1.19.2

Plugins Used: ONLY Mythicmobs-5.1.4

Steps to Reproduce:

  1. Summon this iron golem with this config
  2. Restart the server
  3. Enter the server again

Expected Behaviour:

  1. The iron golem should still be there

Actual Behaviour:

  1. The iron golem is not there.

Addition info:

This only applies to vanilla mob overrides. Vanilla mobs that are modified will have this bug even though the despawn option has been set to false.

Unknowncommented

These were some logs for the issue. The iron golem disappeared after i died and returned to my deathpoint. Despawn option is set to "false"

Logs:

[22:13:51 WARN]: [MythicMobs] Mob type Iron_Golem not found - removing mob 8baba3cf-58e1-4f75-b03a-64710ff22713 [22:13:51 ERROR]: [MythicMobs] [EVENTS] Exception thrown whilst handling event: org.bukkit.event.world.EntitiesLoadEvent [22:13:51 WARN]: java.lang.NullPointerException: Cannot invoke "io.lumine.mythic.api.adapters.AbstractEntity.getBukkitEntity()" because "aEntity" is null [22:13:51 WARN]: at MythicMobs-5.1.4.jar//io.lumine.mythic.core.mobs.MobType.applyMobOptions(MobType.java:841) [22:13:51 WARN]: at MythicMobs-5.1.4.jar//io.lumine.mythic.bukkit.listeners.MobListeners.lambda$load$5(MobListeners.java:288) [22:13:51 WARN]: at MythicMobs-5.1.4.jar//io.lumine.mythic.bukkit.utils.Delegates$ConsumerToBiConsumerSecond.accept(Delegates.java:144) [22:13:51 WARN]: at MythicMobs-5.1.4.jar//io.lumine.mythic.bukkit.utils.events.functional.single.EventListener.execute(EventListener.java:131) [22:13:51 WARN]: at co.aikar.timings.TimedEventExecutor.execute(TimedEventExecutor.java:76) [22:13:51 WARN]: at org.bukkit.plugin.RegisteredListener.callEvent(RegisteredListener.java:72) [22:13:51 WARN]: at org.bukkit.plugin.SimplePluginManager.callEvent(SimplePluginManager.java:683) [22:13:51 WARN]: at org.bukkit.craftbukkit.v1_19_R1.event.CraftEventFactory.callEntitiesLoadEvent(CraftEventFactory.java:1902) [22:13:51 WARN]: at net.minecraft.world.level.entity.PersistentEntitySectionManager.g(PersistentEntitySectionManager.java:384) [22:13:51 WARN]: at net.minecraft.world.level.entity.PersistentEntitySectionManager.a(PersistentEntitySectionManager.java:392) [22:13:51 WARN]: at net.minecraft.server.level.WorldServer.a(WorldServer.java:729) [22:13:51 WARN]: at net.minecraft.server.MinecraftServer.b(MinecraftServer.java:1571) [22:13:51 WARN]: at net.minecraft.server.dedicated.DedicatedServer.b(DedicatedServer.java:451) [22:13:51 WARN]: at net.minecraft.server.MinecraftServer.a(MinecraftServer.java:1433) [22:13:51 WARN]: at net.minecraft.server.MinecraftServer.v(MinecraftServer.java:1204) [22:13:51 WARN]: at net.minecraft.server.MinecraftServer.lambda$spin$1(MinecraftServer.java:307) [22:13:51 WARN]: at java.base/java.lang.Thread.run(Thread.java:833)

Unknowncommented

I also met this problem, and im using the latest dev build

Sign in to join the discussion.