What is Different About the [Latest] JAR List Options and Why? The general way the jar list options are updated is simply by adding a second option with the new version, and then remove the older out of date option a few days later. However - Most clients are unaware that this ever happens and can go months before realizing that the option that they were using has been removed, which in turn will also cause issues with the control panel on restart where the server does not show as Online even though it is, which also disables some MultiCraft features (such as the Chat page) because the panel cannot pick up that the server is online when it is. This issue, coupled with the fact that each jar list option is using disk space on every single node on the system, has lead to a few changes being made - that being the [Latest] jar list options which are updated directly. This avoids adding lots of separate options on the jar list for options that are updated more frequently than others and using up a lot more system space that servers could otherwise need, and also means that if you do not wish to update you do not have to, and it will not stop showing as Online on the panel as it would otherwise as it is still running on the jar that was installed when you ran that jar option the first time. Modpack and Forge options will still be updated in the old manner of adding a second option for the update, otherwise restarting after the update would force install the new version due to the 1-click install feature (and in Forge's case wipe the mods folder again) rather than let the client choose if they wanted to update or not. How to Update These JAR List Options Updating these options is very simple, and only takes a few moments. To update these jar options when an update has come out and you need to/wish to update to the latest version, follow these steps: Shut the server down on your MultiCraft control panel. Go to Files > FTP File Access on the panel, and log into the files with your current MultiCraft password. Select and delete the '/jar' directory/folder. Once deleted, restart the server and it will reinstall the jar on it's updated version. For the most part this is not always necessary to do. For example, if you are using build #1050 of PaperSpigot 1.11.2 on your server, and it is running fine without issues, then you do not necessarily need to update the server to the current build. Updating will apply patches that your server does not have, but in a few very rare cases it can also apply issues that were not there before, so if you do not have any issues on the server you do not necessarily need to update (though it is always advised to keep up to date). The exception to this is the Spigot, PaperSpigot and CraftBukkit options for newly released MC versions. As they won't have had a lot of time for development/bug squashing there will still be a lot of bugs and kinks that need to be fixed, so patches are released very frequently to resolve the issues. As an example, there was a bug in the 1.9 jars early on that would randomly crash servers due to, what the errors made it appear to be, block errors, such as this: 06.03 14:36:30 [Server] INFO at net.minecraft.server.v1_9_R1.BlockIceFrost.a(SourceFile:72) ~[spigot_1.9_latest.jar:git-Spigot-ee4e41a-ea28c1e] 06.03 14:36:30 [Server] INFO at net.minecraft.server.v1_9_R1.BlockIce.b(BlockIce.java:54) ~[spigot_1.9_latest.jar:git-Spigot-ee4e41a-ea28c1e] This had lead a few clients to wipe worlds to try and fix the issue, when it was not actually due to block errors it was simply a bug in the 1.9 jars that has since been patched. As such, if you are using the Spigot/CraftBukkit/PaperSpigot options on the jarlist you should be updating regularly, especially during early release of that MC version, to avoid issues like this. We update the jars themselves with patches every 24 hours or so (Read the post HERE for information on this) to keep them up to date as much as possible to resolve these issues. **Side Note: If you are using the [Latest] Spigot/CraftBukkit/PaperSpigot options, please make sure that all plugins are on their latest versions (including development builds if they are newer and for that MC version when the last stable release is not specifically) - to make sure that they are compatible with the newest MC version. If they are on their latest version and cause issues or spam errors they should be disabled/removed or replaced until they have updated, as they will be causing issues aside from the error spam even if it isn't obvious. **Side Note 2: While it may seem beneficial for these options to auto-update when a new patch is released, we will not force the updates which is why the steps of deleting the .jar file/folder and restarting is needed, as there is no guarantee that a new patch won't cause any new problems (though this is very rare, the Spigot team are pretty good with their updates). As such forcing the updates automatically would put those issues onto servers without the owners knowledge or consent. We will keep the jar on the system up to date but it will always be the server owners responsibility to update as and when they need/wish to. Additional Step to Update the [Latest] Forge w/SpongeForge Option: Due to this option having an individual mod as part of the installation, just deleting the jar folder will not work. Deleting the jar folder by itself and restarting will update the Forge version, but not the mod itself. If you use this option and you need to/wish to update to the latest version, follow these steps: Shut the server down on your MultiCraft control panel. Go to Files > FTP File Access on the panel, and log into the files with your current MultiCraft password. Select and delete the '/jar' directory/folder. Go into the '/mods' directory/folder and delete the spongeforge jar file. Once deleted, restart the server and it will reinstall the jar on it's updated version correctly.