Innocent Me was charged with killing a seeker in dau while I was pilotting an XC moth.
The rat shooting at me hit the seeker while I was docking. As soon as I undocked the strike force killed me.

I dont think I even bumped the seeker but there was a lot of lag present.

XC's should be exempted from this as well as ships that havent fired a shot.

It's impossible to lose faction standing from killing a seeker. Your explosion either damaged a station guard or something else happened.

Im pretty sure nobody here cares about innocent you Pak, everyone has to deal with the limitations of the AI.

XC's should be exempted from this as well as ships that havent fired a shot.

How about death explosions don't count and fix the underlying problem instead of making an exception for your corner case?

Arf has the right idea.

Of course, then PaK'll whine about people exploding their buses on him without penalty.

Considering collisions cancel the /explode timer and it's really damn hard to blow up on someone close enough to do damage without actually touching them, I'd say that's an acceptable risk.

I didnt kill the seeker with a death explosion....I docked just fine.

I agree death explosions shouldnt count but this wasnt the case here.

How the heck did you kill it then? Ramming hardly does any damage at all anymore.

Ive seen this exploit before... very annoying.

Do you even know that you killed it? As in, did the game actually say, "You killed Aerna Seeker AD342f"? You don't have to actually kill anything to trigger the temp-kos; an injury is sufficient.

I feel compelled to point out that the in-game warranty mechanic prevents this problem....but to take advantage of it you would have to remove he bigoted homophobic guild leader from his position of authority. I guess I can see why you're trying to change the game rather than do the right thing....

an injury is sufficient.

No, a hit from weapons fire is sufficient. I've rammed plenty of people away from docks in the NFZ. Conversely, concussion mines and shield turrets still trigger the NFZ violation even though they effectively do no damage.

The explosion problem has to do with the individual strike force bots going aggro when you blow up on them and happens even outside the NFZ.

ARF I did not even bump it or blow up near it , I docked - the rat killed it while shooting at me.
and I had no weapons since I was in an XC....
it was in my sensor log so yes I was credited improperly with the kill..

@savet this is not a rp forum - this is a discussion of game mechanics
If you cant separate your personal issues then refrain from posting.

Pot... Allow me to introduce you to kettle. The complaint strains credulity, so it's kind of hard to take it seriously.

Well, it sounds like a bug to me then.

Of course, the request for special exemptions for the XC is just silly nonsense. Fix the actual bug, don't tack on half-drunken workarounds.

True Pizza - an actual bug fix would be better.

In the past the Devs have stated it is difficult to determine who fired at times. Marking which ships cant/havent fired since entry into the sector would go a long way toward eliminating some of the exploits and bugs in the system. <Shrug>

The moral of the story is that one must always remove one's pants from one's head before one makes a bug report.

Who cares if you've fired or not. What matters is whether you hit someone (violated the NFZ) or not. Are you sure those SF weren't trying to kill someone else and just caught you in the crossfire?

A *lot* of NPC exploits (not just the strike force) have to do with the NPCs firing at their "enemy" without any regard for what is in the way. I've de-shielded plenty of capships in Deneb this way using a well-placed fighter and an enemy Teradon.

Yeah but you personally didnt do the killing. :P
Part of the faction systems purpose is to assign blame if you will.
Sometimes figuring out who didnt do something is quicker then figuring out who did...

Except that this isn't a murder mystery crime scene, it's a computer game. Things actually *are* absolutes here. There's no maybe shot or maybe hit. Simulating who shot and who hit is part of what the server does. If the server's simulation doesn't say you hit someone, then the hit doesn't register at all.

Since this hasn't been said yet: Is this reproducible? Can you get it to do this consistently?

Oh I play the victim all the time :P
I suspect this is related to some of the other exploits the rats like to try but I didnt really see the whole thing.
I docked literally as the missles were exploding.

I would think figuring out who did what would be easy but I know the situation gets a lot more complex as real time is somewhat flexable and while the server does have all the info there is simply not enuogh time to check every possibility.