EngineHub / EngineHub/WorldEdit

//chunk & //regen using incorrect seed.

Open
#2,398 12 comments 0 reactions 0 assignees View on GitHub
platform:bukkit-spigot-paper status:upstream type:bug
Dominant language
Java
Stars
3.5k
Forks
960
Avg merge
6h 57m
Merged PRs (30d)
1

Description

### WorldEdit Version

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

### Platform Version

1.20.2 Paper Build 195

### Confirmations

- [X] I am using the most recent Minecraft release.
- [X] I am using a version of WorldEdit compatible with my Minecraft version.
- [X] I am using the latest or recommended version of my platform software.
- [X] I am NOT using a hybrid server, e.g. a server that combines Bukkit and Forge. Examples include Arclight, Mohist, and Cardboard.
- [X] 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: https://github.com/EngineHub/WorldEdit/issues/1544 (2020, with latest reply this year in 2023). Would appreciate any help here. CC: @dumptruckman

Contributor guide

Open the contributing guide

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.