We are hosting a minecraft-network with 500-1000 concurrent players and we love to use paper especially because of the performance problems in the new versions (our servers are running on 1.14.4).
Now we have a problem: With version 1.14 it is no longer posible to regenerate chunks like before: https://hub.spigotmc.org/javadocs/spigot/org/bukkit/World.html#regenerateChunk-int-int-
We need an implementation of that for the version 1.14.4 but our dev-team has not the time and the knowledge to do this. So we decided to give the person that can do this for us a donation of 150€. The condition is a working implementation for regenerating chunks that works like World#regenerateChunk in version 1.13.2 or better.
If you need any proof for this offer, add me on Discord: Cytoox#3169
Thanks for you time!
Cytoox
All 25 comments
@Spottedleaf ez 150€
HexedHero
on 12 Sep 2019
@Cytoox you could use https://www.spigotmc.org/resources/coreprotect.8631/ and restore area to its original state. I know it's not the same thing but would help in the mean time.
(note that this will apply only from the moment you'll install CoreProtect as it logs block changes, it won't be able to know what changes were made before its installation).
Can I get my 150€? lol
LoneDev6
on 20 Oct 2019
Well thats not what we want 😅
Cytoox
on 20 Oct 2019
From the JavaDocs
"Deprecated.
regenerating a single chunk is not likely to produce the same chunk as before as terrain decoration may be spread across chunks. Use of this method should be avoided as it is known to produce buggy results."
If you don't mind that, you can keep on using the regenerateChunk method.
If you do, you'd need to pretty much rewrite all world generation in order to support it. (Also, look below for another possible solution)
limwa
on 22 Oct 2019
@Cytoox
Only way to restore the exact state of chunk is to save it with a logger plugin or a custom made one (pretty simple to do, you just have to save chunk data on chunk generation event).
If you don't care about getting the same exact chunk you can use regenerateChunk method as @PixelLima said
LoneDev6
on 22 Oct 2019
... The point of this issue is that the method currently does not have any implementation at all.
KennyTV
on 22 Oct 2019
We don't need to restore the chunk 100% accurately. That's why we said "works like World#regenerateChunk in version 1.13.2 or better". It didn't work perfectly in 1.13.2 and doesn't need to be any better than that.
We can't use regenerateChunk, since it's functionality got completely removed. That's why we opened this issue in the first place.
Gerrygames
on 22 Oct 2019
Only way to do that is to save chunk data on its first generation and restore it later.
LoneDev6
on 22 Oct 2019
You are answering the wrong question - all they (and we) want is for that method to be reimplemented. Not to search for (hacky and/or memory intensive) alternatives 🤷♂️
KennyTV
on 22 Oct 2019
Well how did it work in 1.13.2 then? Again: We are not asking for chunks the be restored accurately. We only want an implementation in 1.14.4 like the one that exists in 1.13.2.
Gerrygames
on 22 Oct 2019
Let me see what I can do
limwa
on 22 Oct 2019
Maybe you can take a look at https://github.com/Jikoo/Regionerator code, it deletes chunk data directly from region files, so they can be regenerated automatically by server
LoneDev6
on 22 Oct 2019
World Edit has a fix for this, you could try using the WE API.
kickash32
on 21 Dec 2019
not so much a fix as a workaround. we just make a new world and copy blocks in from that.
wizjany
on 21 Dec 2019
Without restarting?
ForceUpdate1
on 21 Dec 2019
not so much a fix as a workaround. we just make a new world and copy blocks in from that.
Very smart, didn't think about this. Basically you have two copies of the world, one with no buildings and one where players can play?
LoneDev6
on 21 Dec 2019
no, but you can do that with backups and the snapshot restore feature, which is completely separate but honestly much more useful if people have the foresight to make a backup.
edit: also for the record there's /delchunks, which does essentially the same thing as the regionerator that was linked earlier, though we only do it on a restart for safety reasons.
wizjany
on 21 Dec 2019
World Edit has a fix for this, you could try using the WE API.
We are testing the workaround from worldedit on our live systems now.
It seems to work well!
Cytoox
on 23 Dec 2019
@wizjany Perhaps entities in the region should also be removed when regenerating
ForceUpdate1
on 23 Dec 2019
This isn't the place to discuss worldedit features.
wizjany
on 23 Dec 2019
I’ll give it a go, I’ve been working with terrain generation for 8 months so I feel like I should try to solve this problem.
dan-negura
on 10 Jan 2020
Alright so I thought regenerating was going to be easier to implement than how it is. So after many failed attempts I came up with a workaround that does it's job and replaces the chunks with original generation ones, but it requires first the creation of another world on the same server. Then the plugin allows for easy selection and import of chunks from the other world. The chunks are grabbed from the same place as the replaced ones, so there's no coordinate and schematic headaches.
Have a look for yourselves, I also published the source.
https://www.spigotmc.org/resources/chunktransfer-across-worlds-useful-for-chunk-regeneration.74219/
Edit: I know that this isn't a regen function, but honestly this is extremely close to that, and you don't need a backup, just instantiate a new world with the same seed and generator. Also this produces consistent results where the decoration is how it was originally (for obvious reasons).
dan-negura
on 11 Jan 2020
That's...pretty much exactly what worldedit does already?
wizjany
on 11 Jan 2020
That's...pretty much exactly what worldedit does already?
What command would you use from WE to do that?
I'm not sure how easy it is to use WE's function, I wrote something that made sense to me in terms of simplicity and goal. Also my approach loads one chunk at a time, I tested it on a 600MB server with 40 x 40 chunks transferred, and it was fine.
dan-negura
on 11 Jan 2020
I once created a suggestion for an implementation in Minecraft.
ForceUpdate1
on 25 Nov 2020
Related issues
James94665
·
3Comments
mibby
·
3Comments
devcat
·
3Comments
Shevchik
·
3Comments
dbkynd
·
3Comments
Most helpful comment
I’ll give it a go, I’ve been working with terrain generation for 8 months so I feel like I should try to solve this problem.