BUG/Glitch: Cancel Assassination by thruster pack

Like the title says. I even have a recording of it. I’m at work now and I’ll try my best to get the footage linked to this thread.

Story #1

In a nutshell what happened in the clip: Im playing on Truth. I jumped down to move towards center of map with my AR. I begin shooting an enemy. Another player comes up to me when I have my back turned to him and he begins the assassination animation because my camera begins to go to 3rd person. I used my thruster pack to go backwards just by reaction and it broke the animation and I wasn’t assassinated. I still afterwards when I was being shot but that wasn’t from the assassination.

Story #2

My brother and I were playing on Empire. He goes to assassinate someone and they used their thruster pack to cancel the assassination.
TLDR; Thruster pack cancels assassination.

Edit: Found my clip https://xboxdvr.com/my5dollarFTlong/80bb63e0-ff18-4c99-9182-2fe5fe901464 happens at 0:16

Bump for edit to OP with clip

I didn’t see you get brought into assassination animation…
if you go frame by frame at 9 seconds remaining, he is already in front of you using melee. at that point you use thruster and die…

Yea, I saw that too, but I was brought into the 3rd person camera. Either him being in front of me was lag or he was initiating the assassination, but going frame by frame, you can see that the camera goes all the way out before the thruster happens. Whatever this is, I don’t think its “normal”.

> 2533274868265432;3:
> I didn’t see you get brought into assassination animation…
> if you go frame by frame at 9 seconds remaining, he is already in front of you using melee. at that point you use thruster and die…

He clearly goes into third-person at the specified time. Thruster pack doesn’t do that anymore, you stay in first-person when using it.
Guy melee-ing from the rear + third-person animation + lag = assassination

> 2533274847535647;5:
> > 2533274868265432;3:
> > I didn’t see you get brought into assassination animation…
> > if you go frame by frame at 9 seconds remaining, he is already in front of you using melee. at that point you use thruster and die…
>
>
>
> He clearly goes into third-person at the specified time. Thruster pack doesn’t do that anymore, you stay in first-person when using it.
> Guy melee-ing from the rear + third-person animation + lag = assassination

Yea that’s what I’m thinking is happening. We could chalk it up to be a lag issue only and wouldn’t happen under normal circumstances, but still something I noticed while playing. It happened when my brother went to assassinate someone as well. So it’s not just on our end.

Also, bump. Assassinations are hard enough to pull off in this new game; we gotta get this fixed.

> 2533274847535647;5:
> > 2533274868265432;3:
> > I didn’t see you get brought into assassination animation…
> > if you go frame by frame at 9 seconds remaining, he is already in front of you using melee. at that point you use thruster and die…
>
>
> He clearly goes into third-person at the specified time. Thruster pack doesn’t do that anymore, you stay in first-person when using it.
> Guy melee-ing from the rear + third-person animation + lag = assassination

i cant explain the 3rd person animation, so ill not argue this. though, he would have essentially used 2 thrusts in quick succession, 1 to break assassination and another a second later to run into the wall on the right…

> 2533274868265432;8:
> > 2533274847535647;5:
> > > 2533274868265432;3:
> > > I didn’t see you get brought into assassination animation…
> > > if you go frame by frame at 9 seconds remaining, he is already in front of you using melee. at that point you use thruster and die…
> >
> >
> >
> > He clearly goes into third-person at the specified time. Thruster pack doesn’t do that anymore, you stay in first-person when using it.
> > Guy melee-ing from the rear + third-person animation + lag = assassination
>
>
> i cant explain the 3rd person animation, so ill not argue this. though, he would have essentially used 2 thrusts in quick succession, 1 to break assassination and another a second later to run into the wall on the right…
>
> > 2533274868265432;8:
> > > 2533274847535647;5:
> > > > 2533274868265432;3:
> > > > I didn’t see you get brought into assassination animation…
> > > > if you go frame by frame at 9 seconds remaining, he is already in front of you using melee. at that point you use thruster and die…
> > >
> > >
> > >
> > > He clearly goes into third-person at the specified time. Thruster pack doesn’t do that anymore, you stay in first-person when using it.
> > > Guy melee-ing from the rear + third-person animation + lag = assassination
> >
> >
> > i cant explain the 3rd person animation, so ill not argue this. though, he would have essentially used 2 thrusts in quick succession, 1 to break assassination and another a second later to run into the wall on the right…
>
> If thats the case, then the thruster mechanics would be broken, as I shouldn’t be able to use my thruster twice so closely together. Unless it went assassination then thruster to cancel then thruster timer is reset because of these actions canceling out then thrusting a second time because timer reset.

> 2533274868265432;8:
> > 2533274847535647;5:
> > > 2533274868265432;3:
> > > I didn’t see you get brought into assassination animation…
> > > if you go frame by frame at 9 seconds remaining, he is already in front of you using melee. at that point you use thruster and die…
> >
> >
> >
> > He clearly goes into third-person at the specified time. Thruster pack doesn’t do that anymore, you stay in first-person when using it.
> > Guy melee-ing from the rear + third-person animation + lag = assassination
>
>
> i cant explain the 3rd person animation, so ill not argue this. though, he would have essentially used 2 thrusts in quick succession, 1 to break assassination and another a second later to run into the wall on the right…

Just watched it again…I’m not seeing the second thrust you’re talking about. Also, I watched the thruster cooldown icon the whole time after the first thrust-- it was red until he died. The only thrust I see throws him out of the assassination and to the right, but he doesn’t hit a wall.

in op he said he broke the assassination with a thrust.
by the time he thrusts, he has seen the “assassin”, reloaded and lost shield
if it was a lag issue, I doubt that he’d see it again as he is claiming.
clearly he went into 3rd person and I cant explain that, but the thrust was a full second late

more likely lag than a bug, and he might have been the only one to see it occur. since he has seen it more than once, it could be connection/nat

> 2533274868265432;11:
> in op he said he broke the assassination with a thrust.
> by the time he thrusts, he has seen the “assassin”, reloaded and lost shield
> if it was a lag issue, I doubt that he’d see it again as he is claiming.
> clearly he went into 3rd person and I cant explain that, but the thrust was a full second late
>
> more likely lag than a bug, and he might have been the only one to see it occur. since he has seen it more than once, it could be connection/nat

If it was lag though, wouldn’t I of been assassinated then since my thrust was used a second later? On his end it would be assassination, on my end it would be lag then 1 second later thruster, yet my lag and thrust action was what happened during the game? It doesn’t make sense what happened, but as long as this gets attention and possibly officially reviewed and either fixed, or can’t replicate then I’d be happy. I just don’t want to see this in the final release of the game and everyone exploiting this when you try to assassinate them.

I will try and replicate this as much as possible when I play later tonight or tomorrow.

> 2533274823601925;12:
> > 2533274868265432;11:
> > in op he said he broke the assassination with a thrust.
> > by the time he thrusts, he has seen the “assassin”, reloaded and lost shield
> > if it was a lag issue, I doubt that he’d see it again as he is claiming.
> > clearly he went into 3rd person and I cant explain that, but the thrust was a full second late
> >
> > more likely lag than a bug, and he might have been the only one to see it occur. since he has seen it more than once, it could be connection/nat
>
>
> If it was lag though, wouldn’t I of been assassinated then since my thrust was used a second later? On his end it would be assassination, on my end it would be lag then 1 second later thruster, yet my lag and thrust action was what happened during the game? It doesn’t make sense what happened, but as long as this gets attention and possibly officially reviewed and either fixed, or can’t replicate then I’d be happy. I just don’t want to see this in the final release of the game and everyone exploiting this when you try to assassinate them.
>
> I will try and replicate this as much as possible when I play later tonight or tomorrow.

ill be trying it as well.
if it is a legit way to escape(within a small window) that’s cool, but don’t break the assassination

> 2533274868265432;13:
> > 2533274823601925;12:
> > > 2533274868265432;11:
> > > in op he said he broke the assassination with a thrust.
> > > by the time he thrusts, he has seen the “assassin”, reloaded and lost shield
> > > if it was a lag issue, I doubt that he’d see it again as he is claiming.
> > > clearly he went into 3rd person and I cant explain that, but the thrust was a full second late
> > >
> > > more likely lag than a bug, and he might have been the only one to see it occur. since he has seen it more than once, it could be connection/nat
> >
> >
> >
> > If it was lag though, wouldn’t I of been assassinated then since my thrust was used a second later? On his end it would be assassination, on my end it would be lag then 1 second later thruster, yet my lag and thrust action was what happened during the game? It doesn’t make sense what happened, but as long as this gets attention and possibly officially reviewed and either fixed, or can’t replicate then I’d be happy. I just don’t want to see this in the final release of the game and everyone exploiting this when you try to assassinate them.
> >
> > I will try and replicate this as much as possible when I play later tonight or tomorrow.
>
>
> ill be trying it as well.
> if it is a legit way to escape(within a small window) that’s cool, but don’t break the assassination

+1