Important Important Notice For All New Minecraft Services (and anybody using 1.13+)

Discussion in 'News and Updates' started by Richard_BN, Jan 24, 2019.

  1. Richard_BN

    Richard_BN
    BeastNode Staff

    Joined:
    Dec 18, 2015
    Messages:
    540
    Likes Received:
    135
    Trophy Points:
    108
    Gender:
    Male
    Occupation:
    BeastNode Support Agent
    Location:
    The Realm of Obscurity.
    This is just a quick post to emphasize two very common issues we are getting on the tickets, and are getting a lot of people cancelling due to before contacting us regarding the issue. We have added a warning regarding the first problem in the Minecraft Server Information email that is sent out when you purchase a server, but this seems to be completely ignored/not noticed in the majority of cases.

    COMMON ISSUE FOR NEW MINECRAFT SERVER ORDERS
    If you have just purchased a new server and do not wish to use Minecraft 1.13+ please be aware of something very important - A Minecraft 1.13+ world will NOT work on Minecraft 1.12.2 or older, or on a modded setup. A 1.13+ world will either cause constant issues in the world when loaded on an older Minecraft version, or it will simply crash the server on world load during startup - if you switch to Minecraft 1.12.2 or older, or a modpack/modded setup, without generating a new world then your server will not work.

    If you are planning on changing your server version to anything other than Vanilla 1.13+ or CraftBukkit/Spigot/PaperSpigot 1.13+, then you need to generate a new world once you have selected the new version.
    To do so - after you have selected your new/desired option on the control panels drop down list, or after you have installed your own custom jar/setup - you either need to log into the server files and delete the world folder before restarting your server, or you can enter a new world name in the World box on your control panel and save changes at the bottom of the page before restarting your server on the new option/setup.

    As a general rule of thumb this is something that should always be done when you change to a vastly different Minecraft version - particularly when you first set up a new modpack/set of mods, as any world generated with different mods or no mods (and especially on a different Minecraft version) will have issues in general.



    COMMON PERFORMANCE ISSUES FOR MINECRAFT SERVERS RUNNING ON 1.13.2
    Minecraft 1.13+ is full of performance issues, with a much higher RAM and CPU usage than 1.12.2 and older as a result. A number of these issues are resolved in the 1.13.2 release but it is still a lot more CPU/RAM heavy than 1.12.2 and older and is not considered 'Stable'.
    At this point 1.13 and 1.13.1 should no longer be in use - if you are using these versions it is heavily recommended to update to 1.13.2 ASAP.

    As a result of the increase in resource usage in the jump from 1.12.2 to 1.13+ it is not recommended to have less than 2GB of RAM for a Vanilla (or CraftBukkit) 1.13.2 server. Spigot/PaperSpigot 1.13.2 can run reasonably well on 1GB of RAM, but less than 1GB of RAM is not recommended for any version of 1.13.2.

    There are a few recommendations we can make to help alleviate the issues on a 1.13.2 server - however it should be noted that even with all of these in effect there is no guarantee that the server won't still have some performance issues.

    It is recommended to lower the view-distance in the server.properties (Files > Config Files > Server Settings on the control panel) to 5 or 6, save changes and restart the server to lower how many chunks will load in around players on the server which will help with the CPU usage spikes.

    It is also recommended to avoid travelling long distances quickly (ie flying around or travelling full speed by boat across oceans) as loading in a lot of chunks at once will spike the CPU and RAM usage considerably on 1.13+. Avoiding the usual potential lag causes such as mob build ups/grinders or large amounts of active redstone etc.. is also recommended.

    Another recommendation for servers using Vanilla 1.13.2 is to use Spigot 1.13.2 instead - A number of issues in Vanilla have been patched in Spigot, so even if you never install a single plugin it will run somewhat better than Vanilla will. Without any plugins installed it will still run the same as Vanilla ingame.
    This recommendation also applies to servers running on CraftBukkit 1.13.2 - Spigot is recommended over CraftBukkit (and in general, always is and has been for a long time now). It will run the same plugins that CraftBukkit 1.13.2 will, but with plenty of patches to aid the performance of the server.

    Make sure to also restart the server regularly (recommended at least once a day) to unload excess chunks and entities and refresh the RAM usage.

    Beyond these suggestions however there is no way to resolve these issues completely - An unstable server setup cannot be made to run perfectly, only to run a bit better. At this point these issues will not be resolved game-side until 1.14 has been released (hopefully...).
     
  2. Richard_BN

    Richard_BN
    BeastNode Staff

    Joined:
    Dec 18, 2015
    Messages:
    540
    Likes Received:
    135
    Trophy Points:
    108
    Gender:
    Male
    Occupation:
    BeastNode Support Agent
    Location:
    The Realm of Obscurity.
    Note that the performance issues are still present on Minecraft 1.14 - and in a lot of cases are actually worse on Vanilla 1.14 than on 1.13-1.13.2.


    Unfortunately for 1.14 servers there is currently not a lot that you can do about this. Lowering the view distance, not loading in a lot of chunks at once, restarting regularly and avoiding general causes of lag is still advised but currently it simply won't perform well no matter what. Spigot does not have a stable 1.14 release to cover this either (and their dev builds are NOT recommended to be used over Vanilla).

    1.14.1 is in the works and will hopefully fix the majority of the main issues (and I imagine Spigot won't release a 'stable' build until 1.14.1 at least anyway now), but for now we cannot help with these issues.
     

Share This Page