1.10 Update

[ViggyIggy]

Forgive the double-post, but I just proved myself wrong:

Ignore the bleed on some of the edges as I hadn't run a trim. I did that with /wb <world> shape rectangular and then /wb <world> setcorners x1 z1 x2 z2. The border distance from the edge is configurable for preventing external chunk generation.

 

[Dallen]

you can also just use packets to create fake world boarders. But that is most likely over kill, Im sure there is a way to stop chunk generation very easily we just need to find it.

 

[q220]

Forgive the double-post, but I just proved myself wrong:

View attachment 6563

Ignore the bleed on some of the edges as I hadn't run a trim. I did that with /wb <world> shape rectangular and then /wb <world> setcorners x1 z1 x2 z2. The border distance from the edge is configurable for preventing external chunk generation.

Is that default Spigot or a plugin that you are using to set that border? Cause it won't accept those arguments for me?

 

[ViggyIggy]

Is that default Spigot or a plugin that you are using to set that border? Cause it won't accept those arguments for me?

I'm using the plugin WorldBorder. Last update was in Jan but it works still.

 

[Dallen]

So after doing a little more research I found that the API is not broken but updated to ensure files do not become corrupted. You can no longer unload chunks that a player is in as this would cause problems. What you need to instead do is track the chunks that need to be deleted and schedule a task to delete them after the player has left that region. If you want to maintain that front end look of unloaded chunks you can simply stop those chunk packets from being sent using protocol lib. Simply register a handler for those packets and filter out the ones that you don't want.