{{
`${userDetail.user.displayName}${userDetail.user.cachedBungieGlobalDisplayNameCode ? `#${standardizeBungieGlobalCode(userDetail.user.cachedBungieGlobalDisplayNameCode)}` : ""}`}}
{{getUserClans()}}
4/24/2017 11:46:34 PM
3
Hi. I've looked at your clip quite a few times and although you got the plate slam I don't think you got the back slam. It looks as if he started to teleport at the same time the warlock went to slam.
I have sent aksis to mid on that 7th teleport through this weeks challenge mode twice, but we did not shoot him until after the slap/ slam.
English
-
[quote]Hi. I've looked at your clip quite a few times and although you got the plate slam I don't think you got the back slam. It looks as if he started to teleport at the same time the warlock went to slam. I have sent aksis to mid on that 7th teleport through this weeks challenge mode twice, but we did not shoot him until after the slap/ slam.[/quote] All three folks so far have basically said the same thing. I have re watched and accept that must be where the flaw in completion must have been. What remains to be Bungie being at fault is that their game declares that he did land the slam. At the very least this video can be proof of THAT glitch for Bungo.
-
Bungie's on screen notifications have always come up slightly behind the actual actions on screen. Is it a glitch? Or just the best we can expect with a peer to peer network connecting us all together. It sucks but it is what it is.
-
At the least it's more reason for the demand of their own servers. If I were a designer it should be designed to lenient in the sense that their confirmations should be relied upon over the timing actions in game. But yes this has always been the case in Destiny 1.
