This HTML5 document contains 5 embedded RDF statements represented using HTML+Microdata notation.

The embedded RDF content will be recognized by any processor of HTML5 Microdata.

PrefixNamespace IRI
n8http://dbkwik.webdatacommons.org/ontology/
n2http://dbkwik.webdatacommons.org/resource/GVhPp79v3ngNCYp9OkhP9w==
n6http://dbkwik.webdatacommons.org/team-fortress/property/
n5http://dbkwik.webdatacommons.org/resource/ompvaL2_hK2LEFYCtDH5kA==
rdfshttp://www.w3.org/2000/01/rdf-schema#
n4http://dbkwik.webdatacommons.org/teamfortress/property/
rdfhttp://www.w3.org/1999/02/22-rdf-syntax-ns#
n7http://dbkwik.webdatacommons.org/resource/4J9spGgivf7DTYVJbYeOew==
xsdhhttp://www.w3.org/2001/XMLSchema#
Subject Item
n2:
rdfs:label
Lag compensation
rdfs:comment
Team Fortress 2, being based on the Source Engine, is generally configured to make use of lag compensation. Lag compensation is most commonly the technical reason behind cases of kills or actions that would otherwise seem infeasible in given circumstances; for example, when players perceive themselves to have been "shot through a wall" by a Sniper, backstabs being performed at the incorrect angle (known as facestabs), or otherwise missing entirely (known as failstabs).
n4:wikiPageUsesTemplate
n5:
n6:wikiPageUsesTemplate
n7:
n8:abstract
Team Fortress 2, being based on the Source Engine, is generally configured to make use of lag compensation. Lag compensation is most commonly the technical reason behind cases of kills or actions that would otherwise seem infeasible in given circumstances; for example, when players perceive themselves to have been "shot through a wall" by a Sniper, backstabs being performed at the incorrect angle (known as facestabs), or otherwise missing entirely (known as failstabs). In a nutshell, when a high-latency (high-ping) player attacks, the server temporarily "rewinds" its copy of the action in order to compensate for their lag. For example, the enemy Sniper shoots when he sees your head, at that moment you and most other players may believe you successfully ran behind a wall. When the server receives the fire message from the Sniper, it "rewinds", finds out if you had ought to have been hit, and then deals damage, leading to the appearance of being "killed through a wall". This is an intentional engineering and design decision, a tradeoff to enhance the realism of attacks at the expense of the realism of taking damage. Were lag compensation disabled, many players would have cause to complain that they shot the enemy without inflicting any damage.