Killing the same Assassination Targets time and again. Luck of draw?

I've taken a few Pirate Lord Assassination missions since the update rolled out, as before hand they were quite broken whether the target would spawn on time or not. Now they spawn, only its 50/50 if it will register the death of the person as the actual target, despite displaying them as the target and sharing the same name.

This is in SC and in mission target zones. I'm legit growing tired of the issues in this game and wasting my time here when it could be better spent. Has anybody got any advice or is this still broken?

Cheers in advance
 
I took ~10 assassination missions since 3.3 and they all worked flawlessly. Not saying your issue doesn't exist, just a information that it isn't always broken.

PS
They've all been in the target USS or I got interdicted by them.
 
Last edited:
Question: As we can't 'honk' on entry to a system any more. Does the Nav. panel still show us the target location?
 
Umm... yea I think your apathy regarding the controls that actually allow utilization of the game itself is the issue. Good luck! If you can't lift a finger, you'll need it.
 
In response to everyone else. I've just fought the same FDL Nick Jewell about 6 times, killed him and despite it showing "Mission Target" and being located in a threat level 6 zone now, it won't register the kill. Jumped out and back into the system also.

Now my ship is in a mess thanks to all the vultures around him and me being out of scb's from the previous encounters, so the repairs will exceed the mission payout if it ever bothers to award it.

Mission abort? This doesn't seem to want to register as complete. 1 hour and 50 remaining.
 
In response to everyone else. I've just fought the same FDL Nick Jewell about 6 times, killed him and despite it showing "Mission Target" and being located in a threat level 6 zone now, it won't register the kill. Jumped out and back into the system also.

Now my ship is in a mess thanks to all the vultures around him and me being out of scb's from the previous encounters, so the repairs will exceed the mission payout if it ever bothers to award it.

Mission abort? This doesn't seem to want to register as complete. 1 hour and 50 remaining.
Bug report and a note to support. Definitely should not be like that.

have you tried logging out and coming back again?
 
Last edited:
Bug report and a note to support. Definitely should not be like that.

have you tried logging out and coming back again?

I've given up. Seems it hasn't been entirely fixed, sadly. Was wondering if anyone had any advice to trigger or fix it somehow.

As for support, they're inundated with major issues since Q4. I won't hold my breath with this one, so ain't jumping hoops. Thanks all.
 
I've given up. Seems it hasn't been entirely fixed, sadly. Was wondering if anyone had any advice to trigger or fix it somehow.

As for support, they're inundated with major issues since Q4. I won't hold my breath with this one, so ain't jumping hoops. Thanks all.

Only advice I can give is to abandon the mission immediately when you encounter a bug rather than wasting time and effort to kill him 5 more times.
 
I took a couple of these this week. Both times, the target interdicted me within 30 seconds of arriving in the system then proceeded to batter themselves to death on my shields.

Challenge: zero.

One of them was an Imperial Navy rank mission. I earned a fancy title by barely lifting a finger.
 
I took ~10 assassination missions since 3.3 and they all worked flawlessly. Not saying your issue doesn't exist, just a information that it isn't always broken.

PS
They've all been in the target USS or I got interdicted by them.

I took only one pirate lord mission and it happened to me.

I killed the pirate with just 14% hull remaining. I saw the notice that I completed the mission and got credits for the bounties on the pirate. I docked my SLF and then the same pirate lord appeared and destroyed me. I checked and got no credit.

These are more like rats than bugs.
 
I haven't seen the bug the OP describes post 3.3 but I was interdicted by a non-mission specific Elite Anaconda (while I was in the FSS Scanner Screen) earlier today while on a fetch quest. Once I had their hull down to around 20% they charged FSD as usual (didn't notice whether they stopped firing) and I popped them before they jumped away but it took a while & I was expecting them to escape at any moment. I manually scooped the mats & as I got to the last white target on the scanner I realised it was a high wake signature with the NPCs name on it. I didn't have a wake scanner on me to chase the ghost.
 
Last edited:
Only my targets did say "Mission Target", as I'd expressed. So this won't be clear cut enough for FD to figure out since they never play their own game, judging by every release they go live with. Lol.

Hmm, that's a new one. :) In this case post bug report and maybe at some unspecified point into the future they'll fix it.

<...> Once I had their hull down to around 20% they charged FSD as usual (didn't notice whether they stopped firing) <...>

Now they do stop firing, this was fixed. They still keep cheating with everything else though. :)

Also try reading this thread. :) (I see Miko already did.)
 
Last edited:
Just had the pleasure to enjoy similar experience. Of course, my ship is not so easily destroyed. :)

[video=youtube_share;_fbHi_GbMME]https://youtu.be/_fbHi_GbMME[/video]
 
Back
Top Bottom