(06-30-2013, 11:08 AM)Trail Wrote: To clarify C broke rule 5.8
C is aware who B is and is not allowed to engage that character (and vice versa)
That said since B is not aware of who C is he would not be breaking a rule if he engaged first unless C told B in advance on who he was. Of course if B does know who C is then they are both maliciously breaking 5.8 if they decided to fight anyway.
Nothing in the rules says C can't attack B, nor that B can't attack C. The player behind A and C is on a different character to the one he killed B on in the first place, so B is free to engage him. Where you got the idea that C can't engage B I have no idea.
Admin confirmation:
(03-04-2013, 09:46 PM)Gheis Wrote:
Scenario 2: I, LHI|Gheis.Mace, kill LR-Contrived.Name in California. I then, before the two hours are up, switch to OSI-Resolute captained InRP by Gheis Mace, and am engaged by LR-Contrived.Name in a separate interaction. Because the ship names are not notably similar (LHI|Gheis.Mace v OSI-Resolute), I cannot expect LR-Contrived.Name to have known I was the same person - or even the same character - and so no violation of reengagement has occurred. Because I'm notably different as well, LR-Contrived.Name can assume I've logged off and return to California if he so wishes.
the scenario you describe is different from the one in the OP. since while the now victim that is being attacked knows the person who was killed before. The killed doesnt know the victim. The victim is also not the one engaging the person who he killed before.
Quote: I cannot expect LR-Contrived.Name to have known I was the same person
He even says so.
meanwhile in the original scenario by monmarfori the person who engages B knows that he took out that character before.
Since C was the agressor in both scenarios that is re-engagement. However would C not have attacked the second time but instead had to defend it would not have been a rule violation. Since you can defend yourself regardless of the situation.