New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
//chunk & //regen using incorrect seed. #2398
Comments
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. |
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 |
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. |
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. |
WorldEdit Version
Bukkit-Official(7.3.0-SNAPSHOT+6521-bba73e5)
Platform Version
1.20.2 Paper Build 195
Confirmations
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
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
The text was updated successfully, but these errors were encountered: