Multiverse and Bukkit Settings are Different (1.16) #2318
Comments
|
The bukkit setting stems from the server.properties/bukkit.yml or a different plugin changing that via the api. Did you test without any other plugin and the default configs? |
|
This is happening to me too, our server is live so I'm not able to remove everything and test. Every time I restart the server, mob spawning stops in all of our worlds. The settings in multiverse worlds.yml are always set to true. I'm not sure how to access the monster settings shown above. Would appreciate any thoughts/solutions :) |
|
I can confirm this is happening in 1.16. Not sure if its a server bug or some plugin is resetting the value. Strangely for some worlds on my server the setting was synced, but for some other worlds it is not. |
|
Can confirm, this exact same thing is happening on my server too. Server.properties has spawn-monsters=true. Using /mv reload fixes the issue but restarting the server causes it to come up again. I can use /mv info 3 to see the multiverse setting for monsters is true but the bukkit setting is false. I do have access to a test environment though, if we think another plugin might be causing it. |
|
Just to provide my own two cents: This does not happen to me using Multiverse-Core 4.1.0-b775 and Paper b101. |
Can you post your list of plugins? Here's mine: Luckperms 5.1.26 |
No, they are too many (and mostly not even widely used/public so the list itself would be pointless) and have nothing to do with your bug as none of my plugins touches that setting. Out of your plugins I don't use the following though so maybe test without them (and with Paper): |
|
I removed all plugins in my test env except Multiverse-Core, used the latest Paper build (#110), and still have the same issue.
|
|
I'm still having the same issue in Paper #110, but /mv reload does help. |
|
I decided to do some testing on a completely fresh instance of Paper #135 and Multiverse Core 4.1.0. After installing, I tried setting the monsters to false on the initial "world" world. After a restart, it remembered the change. I then created a new overworld called "test." I set the monsters to false and reset the server. When it rebooted, it remembered the setting for "test" but not for "world." /mv reload fixed it as expected. Hopefully someone can reproduce the problem with my steps. |
|
I'm experiencing this too, both in git-Spigot-17d78db-f8d4da0 and Paper build 204 with MV2 Core build 793. It happened with Paper 202, 101, and earlier Spigot and Paper 1.16.x versions as well. I can provide or test whatever you want. |
|
If you've got the time, can you try it on older versions of Minecraft, like 1.15, 1.14, and 1.13? |
|
The issue exists since 1.16. |
|
I just wanted to be sure that the Multiverse and Bukkit settings were the same on older versions of Minecraft. |
Been running MV2 Core since MC 1.8, this is the first time this problem ever manifested. Never happened in 1.15, 1.14, 1.13, or older versions. The world configuration I currently have has been largely the same (about 12 or so worlds) since 1.13 with the addition of one more a few months ago, which the problem predates. (I can spin it up again anyway if you really want me to though.) |
|
Actually, I'll do my own testing, and if I can't reproduce, then I'll ask for more details. |
|
-_- as usual, I cannot reproduce the issue on a fresh server install. Although, I don't doubt the issue exists. Can someone give me reproduction steps from a fresh server install. P.S. I am testing on Paper Build 204, and MV Core Build 793. |
nicegamer7
added
Bug: Confirmed
Putting one together right now, will document the steps I take and at which point it manifests. |
|
!!!!! ISSUE MANIFESTS AT STEP 34 !!!!! I think it's isolated to my MV2 configs, based on the action taken below. I've attached my config.yml and worlds.yml files as a result. These same configs were used in Spigot/Paper 1.13.x, 1.14.x, and 1.15.x without issue. Possibly a config setting that didn't matter before but does now? ======================== 01: Placed "paper-204.jar" and "start-v2paper.bat" in the same folder (in this case named MC 1.16.03 PAPR-T). Contents of file "start-v2paper.bat" are as such (all one line): 02: Ran "start-v2paper.bat" to generate the eula.txt, which was set to "true", then reran the batch file to start it for real. 03: Logged into the server with zero plugins, observed hostile mobs spawning at night. 04: Stopped server, added MV2 Core 793, relaunched server. 05: Observed hostile mobs spawning at night. 06: Stopped server, changed difficulty to hard in "server.properties" and "./plugins/Multiverse-Core/worlds.yml" to more accurately match my own server's setup. 07: Started server, observed hostile mobs spawning at night, opped myself via console. 08: Copied server worlds "survival3" (originally generated in MC 1.10), "creative2" (originally generated in MC 1.8), "mushtown" (originally generated in Minecraft Beta 1.x), and "spawntown" (originally generated in MC Alpha 1.x) from the current production server into the root server folder alongside the default worlds. 09: Started server and ran /mvimport survival3 NORMAL. Command succeeded. 10: Ran /mvtp survival3, successfully teleported to the world, observed hostile mobs spawning at night and /mvinfo 3 shows mobs as True for both Bukkit and MV2, monster that can spawn is ALL. 11: Stopped server, relaunched server, mobs are still spawning, /mvinfo 3 still shows true for both. 12: Ran /mvimport creative2 NORMAL. Command succeeded. 13: Ran /mvtp creative2, teleported to the world, mobs are spawning properly and settings remain correct. 14: Stopped server, relaunched server, mobs are still working in all worlds. 15: Ran /mvimport mushtown NORMAL, it succeeded, ran /mvtp mushtown and successfully teleported to the world, /mvinfo 3 is correct but mobs did not spawn due to MV2 detecting the world's PEACEFUL difficulty. 16: Stopped server, changed difficulty of "mushtown" to HARD in "./plugins/Multiverse-Core/worlds.yml", relaunched server, hostile mobs now spawn. 17: Ran /mvimport spawntown NORMAL, it succeeded. 18: Ran /mvtp spawntown, successfully teleported, no mobs due to imported PEACEFUL world difficulty. 19: Changed difficulty from PEACEFUL to HARD in "./plugins/Multiverse-Core/worlds.yml", ran /mvreload, hostile mobs now spawn, /mvinfo 3 is true for both. 20: Stopped server, relaunched server, hostile mobs are still spawning in all worlds. 21: Stopped server, copied in MV2 Portals and MV2 Netherportals, launched server to generate configs, then stopped it and relaunched, hostile mobs are still working and /mvinfo 3 settings are still True. 22: Stopped server, copied in plugins WorldEdit 7.2.0 Beta 2 and WorldGuard 7.0.4 Beta 1, started server, mobs and settings are still working. 23: Stopped server and relaunched server, still working. 24: Stopped server, copied in plugin Luckperms 5.1.93, started server, mobs and settings are still correct. 25: Stopped server, copied in plugins AsyncWorldEdit 3.7.5 and Warpalicious 1.11, started server, mobs and settings are still correct. 26: Stopped server, copied in plugin CoreProtect 19.2, started server, mobs and settings are still correct. 27: Stopped and relaunched server, still working. 28: Stopped server, copied in EliteMobs 7.1.44, started server, mobs and settings are still correct. 29: Stopped server, copied in plugins BetterSleeping 3.0.3 and ChopTree 2 2.4.3, started server, mobs and settings are still correct. 30: Stopped server, copied in plugins Vault 1.7.3 and Vault Chat Formatter 1.0, started server, mobs and settings are still correct. 31: Stopped server, copied in plugin OhTheDungeonsYou'llGo 7.2, started server, mobs and settings are still correct. 32: Stopped server, copied in plugin PerfectBackup 1.6, started server, mobs and settings are still correct. 33: Stopped server, copied in PerWorldInventory 2.3.2, mobs and settings are still correct. At this point, all production plugins are present in this server instance, issue has not manifested yet. 34: Deleted the MV2 Core configs and all world folders. Copied in the worlds.yml and config.yml files from the production server. Changed the "level-name" value in server.properties to "spawn". Copied in all worlds from the production server: ajproject, cachestore, cacheworld, creative, creative2, creative2_nether, creative2_the_end, em_guild, eventure1, experiments, experiments_nether, experiments_the_end, ktundra, mushtown, oceantown, pixelart, pixelart2, spawn, spawn_nether, spawn_the_end, spawntown, survival3, survival3_nether, survival3_the_end, survival3em1, wtundra. All other plugins still have their default unmodified configs. 35: Started server, survival3 mobs and settings are working fine, but creative2 and survival3em1 are not spawning mobs and the Bukkit setting is now False for both too. Running /mvreload causes the Bukkit setting to change back to True and hostile mobs immediately began spawning in both worlds. 36: Stopped server, removed all plugins except MV2 Core, MV2 Portals, MV2 Netherportals, and PerWorldInventory by moving their .jar files into a ./!REDACTED folder. Started server, Bukkit setting is back to False for both creative2 and survival3em1, no mobs are spawning. Ran /mvreload, mobs and settings are fixed again. 37: Stopped server, removed PerWorldInventory, MV2 Portals, and MV2 Netherportals, started server, creative2 and survival3em1 Bukkit settings are back to False. Running /mvreload fixed it again as usual. At this point, MV2 Core build 793 with my own configs is the only plugin the server is running. The creative2 world didn't exhibit the problem when newly imported earlier, only when the original configs were copied in and it was recopied, but the configs also brought in a pile of other worlds as well. |
|
Did a little bit more testing. Spinning up a new server and only installing MV2 and copying in my production server's worlds and MV2 configs causes the behavior to happen as well, which can be aligned as steps 01 to 07, then 34 to 37 in the previous message. |
|
maybe this is somehow related to the 1.16 mojang stupidity where main level-name is actually "minecraft:overworld" now and all the associated issues; perhaps bukkit is defaulting to monsters false on non-main worlds and isn't saving references/preferences to other worlds properly because of this change? could be a bukkit bug then what limited info i've seen, here: Multiverse/Multiverse-NetherPortals#173 (comment) |
|
Also happens using git-Spigot-17d68db-f8d4da0, using the same short method described in my previous comment. |
Did you check if there were any differences in the world's config section? |
I want to say I checked that a while back and found nothing of consequence, but I don't remember for sure so I did it again. Only different settings are as such: ORIGINAL CONFIG: NEWLY IMPORTED CONFIG: (The "alias" and "respawnWorld" settings are just '' as there is nothing between the two apostrophes, as is normal for a blank default MV2 world setting.) EDIT: Don't see how any of those three could cause this though. |
nicegamer7
changed the title
nicegamer7
added
Bug: Confirmed
|
I was able to reproduce the issue using the instructions given here. Will be investigating some more. |
|
I've reported this issue to Spigot with a simple plugin that demonstrates the bug: |
|
This has just been fixed by Spigot. If someone could please confirm it's working for them by building the latest version of Spigot using BuildTools it would be appreciated. |
I just tested this out using the instructions I provided on Paper 261 and the latest Spigot from BuildTools (git-Spigot-37d799b-bc6a175). I'm using Multiverse-Core-4.2.2 It worked perfectly on Spigot but it did not work on Paper. Here's every command I typed starting from a fresh server instance with only Multiverse installed. This was actually done entirely in the terminal and I never entered the server as a player. Hopefully I was able to add a little extra helpful info. |
|
Afaik Paper fixed the issue in Build 262 |
|
@Brokkonaut is correct, Paper Build 262 incorporates this fix. Thanks for everyone who participated! |
I've found that after updating to 1.16.1, monsters are no longer spawning in any of my worlds. When I change it back with the /mv modify set command, it reverts back on a server restart. The Multiverse Setting is always true, but the Bukkit Setting gets reset with every restart.
The text was updated successfully, but these errors were encountered: