User Tools

Site Tools


en:games:star_trek_-_voyager_elite_force:master_servers

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revisionPrevious revision
en:games:star_trek_-_voyager_elite_force:master_servers [2023-02-08-13-31] – [Technical Concept of the Master Server] 7saturnen:games:star_trek_-_voyager_elite_force:master_servers [2023-02-08-13-32] (current) 7saturn
Line 27: Line 27:
 On the other hand, the master server must first know about the existence of a game server (listen and LAN servers are not listed, only Internet servers, which is configured in the settings of a server by the variable definition ''dedicated = 2''). To do this, a game server with the appropriate settings reports to the master server via a so-called "heartbeat". This contains only the information "Huhu, here I am, please add me to your list". But the master only accepts servers that are actually reachable. He checks this by checking the status of the server that is currently reporting after a message like this (provides the number of players, version, etc...). If he does not receive an answer, he does not record the server. This must be taken into account, for example, when operating a server behind a firewall or [[en:network_terms:network_address_translation|NAT]]. If the server port is closed, the master server does not reach it, so it will not appear in the list. On the other hand, the master server must first know about the existence of a game server (listen and LAN servers are not listed, only Internet servers, which is configured in the settings of a server by the variable definition ''dedicated = 2''). To do this, a game server with the appropriate settings reports to the master server via a so-called "heartbeat". This contains only the information "Huhu, here I am, please add me to your list". But the master only accepts servers that are actually reachable. He checks this by checking the status of the server that is currently reporting after a message like this (provides the number of players, version, etc...). If he does not receive an answer, he does not record the server. This must be taken into account, for example, when operating a server behind a firewall or [[en:network_terms:network_address_translation|NAT]]. If the server port is closed, the master server does not reach it, so it will not appear in the list.
  
-Strictly speaking, only the servers that correspond to the version of the requester are reported back, possibly restricted to not full and/or not empty servers. Ultimately, the concept is very simple and has some minor vulnerabilities. For instance, the protocol (just like the game protocol) is based on UDP. This means that if a request or response is lost during transmission, no one will notice. This can also mean everything is completely OK at both ends, but you still don't get a server listed as a client. How exactly this works technically is described below. +Strictly speaking, only the servers that correspond to the version of the requester are reported back, possibly restricted to not full and/or not empty servers. Ultimately, the concept is very simple and has some minor vulnerabilities. For instance, the protocol (just like the game protocol) is based on UDP. This means that if a request or response is lost during transmission, no one will notice. This can also mean everything is completely OK at both ends, but you still don't get a server listed as a client. How exactly this works technically is described in the article [[server_query_protocol|Star Trek: Voyager Elite Force Master Server Protocol]].
-===== The Protocol Behind it ===== +
-See article [[server_query_protocol|Star Trek: Voyager Elite Force Master Server Protocol]] on the subject.+
  
 [[..:star trek - voyager elite force|Star Trek: Voyager Elite Force]] [[..:star trek - voyager elite force|Star Trek: Voyager Elite Force]]
en/games/star_trek_-_voyager_elite_force/master_servers.1675859507.txt.gz · Last modified: 2023-02-08-13-31 by 7saturn

Donate Powered by PHP Valid HTML5 Valid CSS Driven by DokuWiki