Jump to content

Server Setup: Difference between revisions

added versions
(fleshed out the introduction)
(added versions)
Line 1:
__TOC__
A '''server''' is a way of running Minecraft that separates the game into two parts. The ''server-side'' simulates the world, while thea ''client'' displays and handles input/output from theeach player. The two communicate constantly to create the game. Running GT:NH as a separate server is required for more than one player to access the same world. A separateMinecraft license is not required for the server, but each player connecting must have a valid Minecraft account. Servers need to be online to authenticate joining players.
 
==== Pros/Cons ====
Servers enable multiplayer fun, can improve TPS even in a single player (SP) world on the same machine, allow chunk-loaded areas to run 24/7 for passive resource production, and supports party progress in the [[Quest Book]]. They also have some downsides; while running a server/client split can improve performance for SP, it's more prone to bugs and stability issues. Having machines running constantly can cause breakdowns if [[maintenance]] isn't automated or something unforeseen happens. Servers are more complicated to set up than a SP instance of GT:NH and require regular technical support (restarts, backups, updates, lag-busting, etc.)
 
==== Versions ====
Servers can run either the Java8 or Java17+ build of GT:NH. '''Java17+ is strongly recommended''' unless a hybrid Thermos, Crucible or Ultramine server software setup is being deployed. Players connecting to the server can run either Java8 or Java17+ with their own launcher; it doesn't have to match the server, nor do all players need to use the same launcher to play. The ''version'' of GTNH (ex. 2.4.0) must match exactly between all clients and the server. If the server updates to a different version, all players will have to update as well to join again.
 
==Server update (All Platforms)==
4,389

edits

Cookies help us deliver our services. By using our services, you agree to our use of cookies.