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 134
    • Issues 134
    • 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
  • #420

Closed
Open
Created May 24, 2021 by Andre Vega@Andre1190

Spawners safe conditions after reload

I think if a mob spawner is underground, it will stop checking for is their safe conditions after any kind of reload (/mm reload; /reload or a regular full server reload with /stop)

I was having a bug related with creating a spawner underground; mobs where getting spawned in blocks and getting suffocated. I realized that this happens if I create the spawner and then do whatever of the reloads I mention. If I create the spawner, it works just fine, but it starts spawning mobs in walls as soon I do any kind of reloads. It wasn't complicated to get the bug, so it's not hard to reproduce.

When I create the spawner, players can get near and far away and it will keep working fine; but, as I said, the spawner gets broken with reloads.

Well, of course after the reloads the spawners would have to work fine, checking safe conditions after reloads. After any of the reloads, if I remove the spawner and create a new one just like the one I deleted, again, starts working fine

I don't think its necessary a log or any of this kind of things, there was nothing wrong about MM in the console and no errors appeared. The spawner I created was a simple zombie spawner with iron armor and with these properties: radius: 40 leashrange: 0 mobsperspawn: 10 maxmobs: 40 And also I don't think these data is important neither. I've tried with several properties and the problem is pretty much the same.

Edited May 24, 2021 by Andre Vega
Assignee
Assign to
None
Milestone
None
Assign milestone
Time tracking