Attacking WANTED mission target makes me WANTED!

[Alec Turner]

I've taken on a couple of assasination missions now where, having been interdicted by my mission target who then scans as WANTED (and I've also KWS'd him too) - when I attack him, I've ended up being WANTED myself in the local system. Now admittedly he's in a wing with a couple of NPCs who are not WANTED, but I didn't fire on either of them so I'm slightly surprised. My understanding up until now had been that you could always fire on a WANTED ship without incurring a bounty yourself. Did this change with Powerplay (I've not pledged to anyone yet) or is this a bug?

 

[rizal72]

I've taken on a couple of assasination missions now where, having been interdicted by my mission target who then scans as WANTED (and I've also KWS'd him too) - when I attack him, I've ended up being WANTED myself in the local system. Now admittedly he's in a wing with a couple of NPCs who are not WANTED, but I didn't fire on either of them so I'm slightly surprised. My understanding up until now had been that you could always fire on a WANTED ship without incurring a bounty yourself. Did this change with Powerplay (I've not pledged to anyone yet) or is this a bug?

If your target was Wanted already before you KWS'd him, and you are sure you DID NOT shot him before the basic scan was over, and you are sure you DID NOT shot his clean wing mates, so then yes, it is a bug.

 

[Alec Turner]

I'm absolutely possitive I got WANTED after opening fire on a WANTED target (certainly the 2nd time it happened because I was half expecting it). If nobody else has an explanation for this then I'll file a report over on the bug forum.

 

[clemdha]

I'm absolutely possitive I got WANTED after opening fire on a WANTED target (certainly the 2nd time it happened because I was half expecting it). If nobody else has an explanation for this then I'll file a report over on the bug forum.

Same problem here.
I double checked like you and there is definitely a bug.

(and i think my 2nd target should not have been wanted in the first place : he was a movie star in an Orca - according to the communications he sent when i started shooting... Anyway movie stars are used to shooting sessions so i went on)

 

[Alec Turner]

Same problem here.
I double checked like you and there is definitely a bug.

(and i think my 2nd target should not have been wanted in the first place : he was a movie star in an Orca - according to the communications he sent when i started shooting... Anyway movie stars are used to shooting sessions so i went on)

I suspect the bug is not that I ended up wanted for shooting a wanted ship but that he should not have show up as wanted at all. His wingmen were't wanted and he was an assasination target, not necessarily a criminal, so there was no reason for him to be wanted really.

 

[Alec Turner]

Bug report here: https://forums.frontier.co.uk/showthread.php?t=160540

 

[Zplintz]

I've taken on a couple of assasination missions now where, having been interdicted by my mission target who then scans as WANTED (and I've also KWS'd him too) - when I attack him, I've ended up being WANTED myself in the local system. Now admittedly he's in a wing with a couple of NPCs who are not WANTED, but I didn't fire on either of them so I'm slightly surprised. My understanding up until now had been that you could always fire on a WANTED ship without incurring a bounty yourself. Did this change with Powerplay (I've not pledged to anyone yet) or is this a bug?

It makes you wanted (a local bounty) by the faction allied with the npc you assassinated. Whats so surprising about that?

Bounty systems changed with 1.3 not PP.

 

[Alec Turner]

It makes you wanted (a local bounty) by the faction allied with the npc you assassinated. Whats so surprising about that?

Bounty systems changed with 1.3 not PP.

He was WANTED, in the local system. I thought you could attack a ship that you'd scanned and that was showing as WANTED with impunity?