Differences

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

--- en:network_terms:loss [2022-04-01-21-39] – ↷ Page moved from en:games:network_terms:loss to en:network_terms:loss 7saturn
+++ en:network_terms:loss [2022-04-02-11-06] (current) – 7saturn
@@ Line 2: / Line 2: @@
 In the gaming context, loss usually refers to one of the following two things: Losing a match or encounter and losing network packages. While the former is an obvious concept, the latter may not be, so it is described here in more detail.
-As most computer games use [[UDP]] for network communication, it is not always guaranteed, that a particular data package that was sent, is actually received by the recipient. As there is no connection or acknowledgement of a package, the sender does not know, whether the package is reaching the destination and the recipient is simply not waiting for any sent data. That's true for the basic UDP [[..:protocol]].
+As most computer games use [[UDP]] for network communication, it is not always guaranteed, that a particular data package that was sent, is actually received by the recipient. As there is no connection or acknowledgement of a package, the sender does not know, whether the package is reaching the destination and the recipient is simply not waiting for any sent data. That's true for the basic UDP [[..:network terms:protocol]].
-However, games implement additional layer(s) of protocol(s) on top of UDP. A simple example would be a serially incremented number in each package. It is incremented by each package sent to the communications partner and also the last received package number is included into the replies. This way the other side can see whether it missed packages. And also the sender will notice either missed packages of the other side or (with the reflected own numbers gotten back) finding out that loss happened when sending. So essentially there are means to measure loss. There are games, such as [[..:counter-strike_1_5|Counter-Strike 1.5]] or [[..:star_trek_-_voyager_elite_force|Star Trek: Voyager Elite Force]], that give a player the means of discovering and showing that ("net graph"). With the help of certain [[..:game_tech:cvar|cvars]], there are even some means available, to reduce the effects of a so-called lossy connection for example by sending a specific package multiple times.
+However, games implement additional layer(s) of protocol(s) on top of UDP. A simple example would be a serially incremented number in each package. It is incremented by each package sent to the communications partner and also the last received package number is included into the replies. This way the other side can see whether it missed packages. And also the sender will notice either missed packages of the other side or (with the reflected own numbers gotten back) finding out that loss happened when sending. So essentially there are means to measure loss. There are games, such as [[..:games:counter-strike_1_5|Counter-Strike 1.5]] or [[..:games:star_trek_-_voyager_elite_force|Star Trek: Voyager Elite Force]], that give a player the means of discovering and showing that ("net graph"). With the help of certain [[..:game_tech:cvar|cvars]], there are even some means available, to reduce the effects of a so-called lossy connection for example by sending a specific package multiple times.
-[ [[..:games_database]] ] [ [[..:network_terms]] ] [ [[..:game_related_terms]] ]
+[ [[..:Games Database]] ] [ [[..:Game Related Terms]] ] [ [[..:Network Terms]] ]