Differences

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

--- en:games:star_trek_-_voyager_elite_force:server_query_protocol [2023-07-31-23-03] – [Announce Game Server to Masterserver (Heartbeat)] 7saturn
+++ en:games:star_trek_-_voyager_elite_force:server_query_protocol [2023-08-14-11-07] (current) – [Announce Game Server to Masterserver (Heartbeat)] 7saturn
@@ Line 7: / Line 7: @@
 A game server may announce itself to the master server by simply sending the string ''ÿÿÿÿ\heartbeat\//27960//\gamename\STEF1\''. The digit series ''//27960//'' corresponds to the port of the reporting server and can deviate accordingly. The master server will then attempt to query the server status //of the sender//. If this succeeds, the server will be added. The IP, the port and the protocol of the game server, as well as the information whether it is empty or full, are stored information. This means that the client is only informed about the servers it can play on. For Eliteforce 1.2 or newer the protocol number is ''24'' (or for older versions like 0.28 it can also be ''22''). On the other hand, the client already specifies whether it wants to receive full and/or empty servers when the master server queries it. If the request is filtered, it will be answered accordingly.
-After that, no more things happen. There will be no response to the game server. The master also checks if the game server is still running. For this purpose there is a simple replacement mechanism: When a server is stopped (command ''quit'') it sends a last heartbeat and then goes offline. Since the master server does not receive an answer when querying the server status, it assumes that the server is dead and does not return it in client responses.
+After that, no more things happen. There will be no response to the game server. The master also checks if the game server is still running. For this purpose there is a simple replacement mechanism: When a server is stopped (command ''quit'') it sends a last heartbeat (actually two) and then goes offline. Since the master server does not receive an answer when querying the server status, it assumes that the server is dead and does not return it in client responses.
 The game server, on the other hand, reports to the master server at regular intervals, like when the status changes from empty to not empty or when the map changes. This also has the effect that a message possibly not received by the master server will (hopefully) be received after some time, and the game server will then be listed.