WorldEdit Version

Bukkit-Official(7.3.0-SNAPSHOT+6521-bba73e5)

Platform Version

1.20.2 Paper Build 195

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

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

Expected Behavior

Generate the correct area using the world's seed.

Reproduction Steps

1. Load server with the above Paper, WorldEdit, WorldGuard versions, as well as latest Multiverse: https://github.com/Multiverse/Multiverse-Core/releases/tag/4.3.12
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.

Anything Else?

Wondering if this has ever been fixed as I've noticed it occurring for a very long time (years) and there continue to be reports about it until this day. Example: #1544 (2020, with latest reply this year in 2023). Would appreciate any help here. CC: @dumptruckman

This issue has been automatically marked as stale because it has not been fully confirmed. It will be closed if no further activity occurs. Thank you for your contributions.

This issue continues to persist.

The reply to the issue in 2023 was about someone using an incompatible version of WE (the unrelated error that was brought up)

Only the original poster of that old issue had the issue you're describing. It hasn't been "fixed" as so far only two people have ever reported it, and no one else has ever been able to reproduce it.

We need more information to fix an issue like this, but given on the other issue worldedit was working fine in other worlds it does sound like the seed is just not being given to MC by the world creation system properly

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.

it's possible that the nms we use to retrieve the seed somehow doesn't match up to where it's set in api/paper/whatever. especially since iirc paper has some patch to allow more seed customization, maybe that data is stored elsewhere.

WorldEdit gets the seed straight from the world itself, so the only way it could be generating with the wrong seed is if Multiverse is not actually saving the seed to the world correctly

This is an issue with Multiverse, not sure if we can fix it.

This issue has been automatically marked as stale because it has not been fully confirmed. It will be closed if no further activity occurs. Thank you for your contributions.

This is an issue with Multiverse, not sure if we can fix it.

Looks like they responded that it's an issue with WorldEdit:
Multiverse/Multiverse-Core#3035

We didn't say it was a WorldEdit issue. We're just saying we are just setting the seed from the Bukkit/Spigot/Paper API. If that is wrong, then the issue is likely with the API implementation. One possible alternate explanation could be that the seed is changing after it has been set via the WorldCreator API (which Multiverse does when using /mv create and when loading the worlds on startup). So if you create a world, and then somehow change the seed without restarting the server, and then use //regen, that could explain this mismatch. If that's not it, it seems like it would be the API implementation.

We didn't say it was a WorldEdit issue. We're just saying we are just setting the seed from the Bukkit/Spigot/Paper API. If that is wrong, then the issue is likely with the API implementation. One possible alternate explanation could be that the seed is changing after it has been set via the WorldCreator API (which Multiverse does when using /mv create and when loading the worlds on startup). So if you create a world, and then somehow change the seed without restarting the server, and then use //regen, that could explain this mismatch. If that's not it, it seems like it would be the API implementation.

We never change the seed on our server. We simply create the world with MultiVerse and the //regen command doesn't seem to actually regen the chunks from that seed.

Basically the same steps as in the original post above.