There is a bug where if you get killed next a turret a conq station, your explosion will trigger as an attack on your own defenses and you'll be temp kos for 15 minutes. This does not seem to be intended.

It's not a bug and anyone worth their salt in station shenanigans knows of it (you included); don't hug your turrets you won't run into this issue. ;P

Makes sense Jaks. Spidey are you sure you get it? There is no legitimate reason why this would not be a bug. Perhaps instead of the word bug the right description is unintended, counterproductive phenomenon. Anyway, it belongs in this forum, and makes sense.

Just because it has not been reported before, does not mean it is not a bug. Please try to keep your replies constructive. Thank you.

Hmm. Basically, if we enable that, it allows people to potentially attack friendlies with their own explosions. Which may not sound likely, but we've seen that people will pursue all manner of trolling cases.

It might be a pretty wrangley piece of convoluted design to try and exclude this one special-case, from what is otherwise a generalized rule.

I'm going to rule this a non-bug, as it is the game behaving as intended, even if it is a side-effect.

If someone has some ideal solution to work around this, they're welcome to post that to Suggestions.

The issue is that in all other parts of the game, if your explosion (not caused by /explode) hurts something, it is NOT considered an attack.

Example: Go to Azek I-16, sit next to a turret, have another player shoot you till you die. The game doesn't say anything about not shooting the turret, nor does it agro on the dead player when they get back to Azek I-16.
In fact, whittle down the turret to super low, and have someone kill you, your blast will kill the turret and you won't take a faction hit.

I tested that on the test server just now https://youtu.be/GN80Rog4reY

So becoming tkos for harming turrets in the conq station with your ship's explosion is the exception to the rule, not the norm. Which is why I thought it a bug.

Well, we'll have to examine the code and see why it is behaving that way, and what the prior code-change commit logs say around it. Thanks for the report, regardless.

If memory serves me right ship explosions not caused by /explode had special rules applied to them when it came to faction standing impact; prevents trolls from blowing up newbs close to their already weakened ship to tank their standing in monitored (not guarded) space.

The current behavior in conq stations doesn't have special rules applied to it because it's the unaligned faction and not one of the three main factions.

Just a half baked guess based on vague memories of when this was occurring roughly ten years ago.

Bug or not, I don't think death explosions should trigger a tkos in the conq station sectors unless you /explode yourself. I'd like to know exactly what "trolling" case are you trying to prevent by applying tkos in this case, because I can't think of any real problems with it, while getting tkos with your station just because you died when a turret or guard happened to be near you is a real problem. Maybe this conversation needs to be moved to the suggestions forum?

Hawkfeather: the "trolling" mentioned is very much possible and observed in nation space or non-conquerable stations. It's just that conquerable station sectors haven't been applied as a exception to it, which, if your argument is correct, they should be.

As Jaks stated, the conq stations are currently already the exception; anywhere else you won't get tkos or faction repercussions for damaging something with your death explosion (unless you use /explode). It makes sense for that to work the same way for conq stations as well.

I was asking about "trolling" cases for exactly conquerable stations, because that's the only place we're suggesting anything should change.