/mv version -p output

No link generated due to 502 at api.paste.gg

Server logs

On private request.

Server Version

1.20.1 Paper Build 195

Bug Description

When selecting a //chunk and //regen 'ing it, the area is not correspondent to the world seed at all.

Steps to reproduce

1. Load server with Paper, WorldEdit, WorldGuard versions, as well as latest Multiverse: https://github.com/Multiverse/Multiverse-Core/releases/tag/4.3.12 (no other plugins on the environment at all).
2. Use command /mv create testworld normal
3. Verify seed in game matches the seed in Multiverse config using /seed command
4. Go to any random chunk and select it with //chunk
5. Use //regen and notice it regenerates a completely different area.

Please see: EngineHub/WorldEdit#2398

Agreements

• I have searched for and ensured there isn't already an open or resolved issue(s) regarding this.
• I was able to reproduce my issue on a freshly setup and up-to-date server with the latest version of Multiverse plugins with no other plugins and with no kinds of other server or client mods.

It looks like //chunk & //regen is working fine when using on a world generated by Paper.
However, when the world is generated by multiverse, the //chunk & //regen command is not working correctly.

Thanks for the bug report, paste.gg is back up now and the information from that command would be quite useful, so the /mvv -p link would be really helpful. Could you also mention the world you are running this command in alongside that please :)

Paste link is as follows: https://paste.gg/p/anonymous/7228ed7dc8794226b578c18a769d24af
The commands are being run in the console to generate new worlds, that's it.

the seed in /seed is defined in your server.properties if you defined it NOT in multiverse.
so create your world
check your seed matches the worldfile
and delet the region folders and may the dat file in it.

//regen and other worldedit command dont use the multiverse seed.
so you might should report this to worldedit to respect multiworldseeds // multiverse seeds

That is incorrect, the //regen command does not grab the seed from the server.properties file.
If you have nothing valuable to add to the issue, there is no need responding to it.

That is incorrect, the //regen command does not grab the seed from the server.properties file. If you have nothing valuable to add to the issue, there is no need responding to it.

but it should use it fron the dat file of the world folder ;) and /seed is not working for the multi verse worlds it only works if your using the vanilla 3 dimension without a multiverse plugin.

Well at least. Worldedit grabs the seed for regen that is set in your world.dat
you can view the with a tool like NTB Explorer.
This seed should match the seed in your multiverse world if the world was generated multiverse

If //regen does not restpect this and generate something else. its not up to multiverse to handle worldedits behave.
Also if you took your world over some MC version you will notices even with the same seed the //regen version will look different because the seednumber design has changed in many versions.

So if //chunk //regen (both Multiverse commands) use a wrong seed. ask the WorldEdit engingub team to may respect the multiverse seeds.

The seed is managed by the server, multiverse simply uses the WorldCreator api by bukkit/paper. So of world.getSeed is returning the wrong thing, i doubt its a mulitverse issue

We are having the same problem.
WorldEdit stated this is an issue with Multiverse: EngineHub/WorldEdit#2398