{{
`${userDetail.user.displayName}${userDetail.user.cachedBungieGlobalDisplayNameCode ? `#${standardizeBungieGlobalCode(userDetail.user.cachedBungieGlobalDisplayNameCode)}` : ""}`}}
{{getUserClans()}}
6/30/2016 10:10:50 PM
3
a wise man said once:
Unlagged uses a technique called “backward reconciliation” for hitscan weapons' hit tests. For the duration of a hit test, it moves players to where you saw them when you fired. (It knows because it sent you the player origins in the first place, it saves that information up in a history queue, and your fire command contains a timestamp.) After the hit test, it moves them back.
Moving player entities around like that is perfectly fine, as long as the entities' states are restored exactly, [u]and as long as no code runs which requires players in their correct state [/u]while the [u][b]server[/b][/u] is in a backward-reconciled state. Unlagged is very[u] careful [/u]about such things, so it doesn't present any problems.
English
-
[quote]a wise man said once: Unlagged uses a technique called “backward reconciliation” for hitscan weapons' hit tests. For the duration of a hit test, it moves players to where you saw them when you fired. (It knows because it sent you the player origins in the first place, it saves that information up in a history queue, and your fire command contains a timestamp.) After the hit test, it moves them back. Moving player entities around like that is perfectly fine, as long as the entities' states are restored exactly, [u]and as long as no code runs which requires players in their correct state [/u]while the [u][b]server[/b][/u] is in a backward-reconciled state. Unlagged is very[u] careful [/u]about such things, so it doesn't present any problems.[/quote]
