Problems with dynmap
ErythroCraft opened this issue · 15 comments
WorldEdit Version
3242-Spigot-6c1c1b2-d3cc412 (MC: 1.17.1) (Implementing API version 1.17.1-R0.1-SNAPSHOT)
Platform Version
7.2.7-SNAPSHOT
Confirmations
- I am using the most recent Minecraft release.
- I am using a version of WorldEdit compatible with my Minecraft version.
- I am using the latest or recommended version of my platform software.
- I am NOT using a hybrid server, e.g. a server that combines Bukkit and Forge. Examples include Arclight, Mohist, and Cardboard.
- I am NOT using a fork of WorldEdit, such as FastAsyncWorldEdit (FAWE) or AsyncWorldEdit (AWE)
Bug Description
After insttalling dynmap the server console say "Regen failed" .
Caused by: java.lang.IllegalStateException: Unregistered dimension type: net.minecraft.world.level.dimension.DimensionManager@67c59b2e
Befor I installed dynmap the command //regen was working.
Expected Behavior
Regenerate parts of chunks.
Reproduction Steps
- stopping server
- installing Dynmap version: core=3.2-beta-3-514, plugin=3.2-beta-3-514
- using //regen
Anything Else?
Please also explain how it can be fixed.
If I can fix it myself.
Installed Plugins on this server are
- Vault
- Multiverse-Core
- ProtocolLib
- dynmap
- WorldEdit
- Multiverse-Inventories
latest log here
latest.log
Yes. I had to install it because I was lost and no longer knew where I was.
I did that a few minutes ago.
It is the only thing that I have additionally installed.
Are you sure this is dynmap-related and not Multiverse? I don't understand what dynmap would be doing to cause this.
I test it with the new 4.3.2-SNAPSHOT-b862 of Multiverse.
But the same.
Can I link this issue to MV and Dynmap ?
Maybe they can help to understand.
Well, I can't reproduce on latest Paper, so I'm going to assume it's not dynmap. Try removing Multiverse and see if it helps. Or if you're going to insist it's dynmap, try removing it and see if it fixes the problem.
It works without Multiverse, but I do not understand.
Without dynmap and installed Multiverse it is functionaly fine.
So
Worldedit + MV = ✅
Worldedit + dynmap = ✅
Worldedit + MV + dynmap = ❎
Well that sounds more like a problem between MV + dynmap, then. Not sure there's much for us to fix.
Spigot does not work properly with datapacks, so that's very possible - Using datapacks with Spigot is known to irreparably corrupt worlds.
Indeed! I've been using this since it came out.
Since version 1.13 I use datapacks on my main server.
