10-11-2017, 08:37 PM
Hello, welcome to the forum.
There might be some problems related to the 1.8 client version. For example, the recipes file Cuberite currently uses has recipes that are unavailable in the 1.8 client, and sometimes it may cause a disconnect for the client (such as when crafting anything from iron, you put in an iron ingot and the client disconnects, because the server gives it the "iron nugget" result, which the client cannot handle). You'd need to tweak the recipes and furnace smelting definitions to make it work.
As for the stability, the server generally runs fine, I've been running one on a RaspberryPi (the oldest one) for well over four years without any major trouble. I have a script in place that runs the server in a loop, together with updating the server - this means that if the server does crash, the executable is updated to the newest available and then restarted. Similarly, I could update the server simply by shutting it down by an in-game command, it will come back up again in a short while.
There is an area protection plugin that is good enough for most use-cases. It doesn't work with WorldEdit yet, this feature is under development.
https://github.com/cuberite/ProtectionAreas
Since I have no data to compare with, I can't say how well the permission system works. It does what we want it to do, it is flexible enough to run a public server with it. Are there any specific questions you have about it?
There might be some problems related to the 1.8 client version. For example, the recipes file Cuberite currently uses has recipes that are unavailable in the 1.8 client, and sometimes it may cause a disconnect for the client (such as when crafting anything from iron, you put in an iron ingot and the client disconnects, because the server gives it the "iron nugget" result, which the client cannot handle). You'd need to tweak the recipes and furnace smelting definitions to make it work.
As for the stability, the server generally runs fine, I've been running one on a RaspberryPi (the oldest one) for well over four years without any major trouble. I have a script in place that runs the server in a loop, together with updating the server - this means that if the server does crash, the executable is updated to the newest available and then restarted. Similarly, I could update the server simply by shutting it down by an in-game command, it will come back up again in a short while.
There is an area protection plugin that is good enough for most use-cases. It doesn't work with WorldEdit yet, this feature is under development.
https://github.com/cuberite/ProtectionAreas
Since I have no data to compare with, I can't say how well the permission system works. It does what we want it to do, it is flexible enough to run a public server with it. Are there any specific questions you have about it?