[SPIGOT-6425] Hostile mobs do not spawn in nether when using DIM-1 generated in vanilla Created: 16/Apr/21  Updated: 30/Jul/21

Status: Open
Project: Spigot
Component/s: None
Affects Version/s: None
Fix Version/s: None

Type: Bug Priority: Minor
Reporter: Boen Cao Assignee: Unassigned
Resolution: Unresolved Votes: 2
Labels: None
Environment:

4gb ram server hosted via bisecthosting


Attachments: File bukkit.yml     File level.dat     File server.properties     File spigot.yml    
Version: 1.16.5
Plugin: NONE
Guidelines Read: Yes

 Description   

There is no plugin installed.

All mobs spawn normally in vanilla 1.16.5. After converting it from vanilla to spigot 1.16.5, no hostile mobs are spawning in the nether anymore (end and overworld are fine).

It is the same DIM-1 folder, but there is mob spawning issue when using spigot while there isn't using vanilla.

If I just create a new world or totally reset nether, there is also no issue. The problem is I do not want to reset nether because I want to keep the farms and tunnels I built in the nether. 



 Comments   
Comment by Brandon der Blatter [ 30/Jul/21 ]

I can confirm this issue, I generated a world in vanilla and used it fine with a vanilla server, a forge server, and with Spigot 1.16.2 but when I switched to 1.17.0 and then 1.17.1 mobs stopped spawning in the nether despite checking the difficulty levels and gamerule doMobSpawning. I fixed it by deleting the world_nether/DIM-1/entities folder and letting the server regenerate it. This messed up some farms since all entities got deleted but otherwise had no adverse effects. It looks like the issue is specifically with how entity data is stored.

Comment by md_5 [ 09/May/21 ]

level.dat doesn't look materially different from my native spigot nether

Comment by Boen Cao [ 09/May/21 ]

Thank you for your responses! First of all, I resolved the problem using "dumb" alternative method by creating a new nether and manually copying and pasting structures from one save to another, which also means the migrating issue still persist but I no longer need a fix at least for now. However, if you want to dive further into the problem and find a fix so that others won't encounter the same problem, I will provide some additional information. I have a very special case so I don't know if it is worth fixing. So my Minecraft world is first created in 1.8.10 version. The very same nether has been directly used in all the consequent Minecraft versions (1.12 1.13 etc). Before importing into 1.16 vanilla, MCA selector was used to delete many chunks in the nether so that new feature would be about to be updated to those chunks. So technically, it is a 1.8.10 nether world that got imported into 1.16 vanilla then spigot having the mob spawning problem. I have uploaded the level.dat from the old world but unfortunately, I no longer have the file for the imported world. I could try to get one if you need it. Please let me know!

Comment by Julian v.d Berkmortel [ 08/May/21 ]

I wasn't able to reproduce the issue after migrating a nether world from a vanilla Minecraft server to Spigot. @Boen Co, is this still reproduceable in the latest Spigot version using BuildTools?

If this is not yet resolved, could it be possible to receive a copy of the "level.dat" from both worlds (one from the world generated by Spigot and one from the world which was migrated)?

Comment by Black Hole [ 16/Apr/21 ]

In Spigot there are gamerules per world. So you have to go to the world with an op player and check that the games rules like doMobSpawning are set right.

Generated at Fri Apr 11 16:22:13 UTC 2025 using Jira 10.3.3#10030003-sha1:d220e3fefc8dfc6d47f522d3b9a20c1455e12b7b.