Board Thread:Suggestions forum/@comment-30575462-20161130004558/@comment-27219153-20161203211610

Ffets wrote: Minecraftmage113 wrote: or you could make it chunk loadI think, minecraft has forced chunks, so you could do it like that.

But imagine a server with 30 players and everyone hires 4 builders in different places to build a village each. Which means 120 villages built simultaneously with, let's assume 100 chunks (160x160 blocks) each. This makes 12000 chunks loaded and processed by the server in addition to the normal player chunks. Seems quite a lot to me, but I don't run servers and have to cope with that.

For comparison: If you have a viewing range of 10 chunks, 314 chunks should be loaded per player, so my example above would mean to process 38 additional players.

 ᚠᚠᛖᛏᛋ (ContentMod) If builders are going to load chunks (which I think they should), I think each player should be limited to "building" one structure at a time. I calculated 361 for render distance of 10 chunks, not 314, how did you get that number? Assuming 361 is correct and each player is limited to one structure, the equivalent additional players would be ~9. This would be a much more reasonable number. Also, forge has amazing configurability when it comes to forced chunk loading, so if servers are concerned about lag, they could simply disable/reduce it.

Another option to consider would be the mechanics of the ender quarry. For those of you who do not know what an ender quarry is, let me explain. The ender quarry is a block from the Extra Utilities mod. While it mines blocks from the ground, it only keeps two chunks loaded, the one it is in and the one it is mining in. For example, I've made quarries the size of 3000 by 3000 meters (that's over 35,000 chunks!), but luckily because it only keeps two chunks loaded it is not very resource intensive.

If builders were to only keep 1 or 2 chunks loaded, the additional lag would be quite minimal. To optimize this, it would be best if all parts of the structure located in the loaded chunk(s) were fully built before loading the next chunk to build in. I'm not really sure if this would be coding intensive or not.