Skip to content

GitLab

  • Projects
  • Groups
  • Snippets
  • Help
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in
MythicMobs MythicMobs
  • Project overview
    • Project overview
    • Details
    • Activity
  • Issues 132
    • Issues 132
    • List
    • Boards
    • Labels
    • Service Desk
    • Milestones
  • Operations
    • Operations
    • Incidents
  • Analytics
    • Analytics
    • Repository
    • Value Stream
  • Wiki
    • Wiki
  • Members
    • Members
  • Activity
  • Create a new issue
  • Issue Boards
Collapse sidebar
  • MythicCraft
  • MythicMobsMythicMobs
  • Issues
  • #325

Closed
Open
Created Feb 12, 2021 by Henry@Henry055

Mobs Become Untracked After Restarts

Summary

We have certain mobs that become untracked by MythicMobs and loose their properties, such as our specified loot drops and disguises. They keep their names but look like vanilla mobs and become incompatible with MM commands. Here's an example:

UndisguisedRat

Steps to reproduce

We haven't been able to recreate it on any localhost or testing servers but we do know it happens when the when the server restarts. Here are our spawners and mobs that have been affected:

  • Rat Spawner 1
  • Rat Spawner 2
  • Rat Mob
  • Random Spawns
  • Random Spawn Mobs

Current behavior

Mobs spawned prior to restarts are becoming undisguised and unrecognised by MythicMobs after restarts. These unrecognised mobs are exempt from Mythic Mobs commands, such as /mm m killall <radius>, drop vanilla loot and don't abide by spawner limits. We are also seeing this issue with our random spawns which are also becoming untracked and losing their properties.

Intended correct behavior

What should happen is that our mobs should remain tracked by MythicMobs after restarts. The mobs should stay disguised, be compatible with MythicMobs commands, abide by spawner limits and drop the loot we specified instead of vanilla drops upon death.

Server log file

Server Log

Debug log snippet

We are unable to trigger this bug on command and it only seems to happen on server restarts.

Assignee
Assign to
None
Milestone
None
Assign milestone
Time tracking