Some advice please: must I self destruct? (crime & punishment)

[Willard73]

On accepting any mission to blow someone or something up, you should be aware of the risk that you may be committing a crime.

Knowing this, you should look around the locale to locate the nearest IF office to clean your ship of any bounties incurred through your mission.

On realising that Robigo is the nearest IF office, you would have seen that there was a fuel risk. You could have mitigated that by shipping a fuel scoop or fuel tank to Sothis in advance.

I know thinking and planning isn't everyone's cup of tea, but I really like the opportunities to play smart and have responsibilty and consequences to factor in to what I do in the game.

Good luck! 7

Thanks Marra, I've been playing ED for a while and have read the C&P changes, but I didn't see anything that would have helped me avoid my current predicament. Had I known scenario C had different rules to A and B, I.e. a 400cr assault bounty but yet no murder bounty(!) I would have played it differently.

You seem knowledgeable about ED. Are you able to tell me why it's fine to shoot first at wanted mission targets in nav beacons and res without gaining an assault bounty, but it's a crime when I drop into a wanted mission target's low wake and shoot first ?

 

[conceit]

I think what happened here is that the mission target either was not considered as "wanted" in the system where OP shot him, or, after leaving SC, he might have been required to re-scan the target (not sure about this). It's an old problem that attacking targets that are wanted by some other obvious reason except a scan leads to a bounty. E.g. you see an offender attacking a clean (or syssec) ship does not allow you to attack the offender until having properly scanned it and actually seeing the "wanted" mark in the scanner display.

Same applies for dropping out of SC or being interdicted - some time ago you needed to re-scan, as the status of a target disappeared from the scanner display after disengaging SC. Thought thas was fixed.

 

[EvoBeardy]

Quoting the OP with the color turned off so it is readable to folks like me using the 'Official Frontier Theme' (White Text on White Background = Invisible Text.)

Thank you, on my phone and wondered why it was an empty post, thought OP had deleted it.

 

[Willard73]

I think what happened here is that the mission target either was not considered as "wanted" in the system where OP shot him, or, after leaving SC, he might have been required to re-scan the target (not sure about this). It's an old problem that attacking targets that are wanted by some other obvious reason except a scan leads to a bounty. E.g. you see an offender attacking a clean (or syssec) ship does not allow you to attack the offender until having properly scanned it and actually seeing the "wanted" mark in the scanner display.

Same applies for dropping out of SC or being interdicted - some time ago you needed to re-scan, as the status of a target disappeared from the scanner display after disengaging SC. Thought thas was fixed.

ahh yes that probably it. Thanks Conceit.

 

[Willard73]

My mate came out with fuel limpets, I made it to Robigo and paid the bounties.. Now back in Sothis with a clean record to continue the grind.

thanks everyone

 

[Greybeard_LXI]

I think what happened here is that the mission target either was not considered as "wanted" in the system where OP shot him, or, after leaving SC, he might have been required to re-scan the target (not sure about this). It's an old problem that attacking targets that are wanted by some other obvious reason except a scan leads to a bounty. E.g. you see an offender attacking a clean (or syssec) ship does not allow you to attack the offender until having properly scanned it and actually seeing the "wanted" mark in the scanner display.

Same applies for dropping out of SC or being interdicted - some time ago you needed to re-scan, as the status of a target disappeared from the scanner display after disengaging SC. Thought thas was fixed.

The way I understand it is you found a target in the super cruise instance, it is destroyed in the instance and creates a low wake object. When you follow the low wake object and leave super cruise it creates a new instance with a new target. You need to scan the new target before you know it is wanted.

This should be changed next week. From a Frontier post late in the 3.03 announcement thread:

A full list of changes will be posted on the day of the update; however, we will also be making some revisions to crime functionality. We’ve provided some details by Lead Designer, Sandro Sammarco, below:

For 3.0.3 we’re altering crime functionality: when you are wanted in a jurisdiction, your ship automatically deactivates the system authority link to prevent crimes gainst you from being detected. This is in line with it using anonymous access protocols to protect you from detection when docking at ports where you are wanted. It means that players will no longer be committing crimes when attacking wanted ships, even if they have not scanned them. It is still important to scan vessels that you are unsure about, but you will no longer become a criminal for attacking a criminal.

 

[Drelthar]

So the general view is that my situation is 'intended' I.e. It's not some sort of bug?

its odd that I can fire first in Res or nav beacon and not get a bounty, but if I drop into a mission target's low wake and fire first I get a 200 credit bounty, (but not a murder bounty)

Were they wanted when you dropped into their wake?

Because Jurisdictions are not system wide. You may have followed them into a region of the system which is controlled by another faction, which does not have a bounty on them, meaning they are clean in that area, which is why you would get a bounty for attacking them. This is also why the new kill warrant scanner is good, it means you can scan them and find their bounty from another jurisdiction, and then have full licence to kill them,.

 

[Willard73]

Were they wanted when you dropped into their wake?

Because Jurisdictions are not system wide. You may have followed them into a region of the system which is controlled by another faction, which does not have a bounty on them, meaning they are clean in that area, which is why you would get a bounty for attacking them. This is also why the new kill warrant scanner is good, it means you can scan them and find their bounty from another jurisdiction, and then have full licence to kill them,.

yes they were both wanted and a mission target. Lots of red text. Despite this, it seems I should have scanned it again. Good news is this is being fixed by FD.

 

[Willard73]

M

The way I understand it is you found a target in the super cruise instance, it is destroyed in the instance and creates a low wake object. When you follow the low wake object and leave super cruise it creates a new instance with a new target. You need to scan the new target before you know it is wanted.

This should be changed next week. From a Frontier post late in the 3.03 announcement thread:

Ahh ok. Thanks. I'm glad it's going to be fixed soon.