Dinoman98777 - Whitelist Report: Finn, Synthvivor Programming 3; may not chase threats to the point of no longer observing selfpreservation
What’s your BYOND key?
Dinoman98777
Round ID:
24782
Your character name:
DI-313-NO
Accused BYOND key:
Ugnip55
Accused character name:
Finn
What rule(s) were broken?:
Synthvivor Programming 3; may not chase threats to the point of no longer observing selfpreservation
Whitelist in question:
Synthetic
Description of the incident:
I had just evolved to a warrior (I’m a terrible warrior player, I use it to stepping stone into Prae or Crusher) and had stumbled into Finn. We stared at each other for a moment, before they pulled out a telescopic baton and began to attack unprovoked. While I see that synthvivors do not need to be attacked first, what Finn DID do is continue to pursue well beyond the point of self-preservation. I made clear and concerted effort to disengage from the fight and flee, and Finn continued to pursue and attack for some distance until I was critted, and finally killed.
With the rule as written, I do not believe a Synth would pursue a xenomorph to kill if the xenomorph is making a clear effort to disengage. I could well be misinterpreting the rule, but chasing seems to go well beyond any means of self-preservation.
Evidence:
Logs
Screenshots of combat
A video of the incident was unfortunately NOT able to be obtained. My recording software refused to open and only did so long after the event had transpired.
I realized too late as there isn’t a listed rule against reports for the current round when making it. I flagged this for moderation myself, but I feel as though that’s too little too late.
I will also post the screenshots of the combat log after the round ends to avoid any risk of metagaming beyond what has already been done.
so we were holding at engineering for a while then xenos breach and i die to a warrior then after that Finn runs down to security and this warrior shows up alone off weeds knowing i had just died a minute prior he attacked it since he is on code delta killing it before he retreats into safety
“When engaged in combat, ensure the threat to yourself, other human colonists, and/or colony infrastructure ultimately disengages or is disabled however you may deem fit. You may proactively engage said threats at your discretion, but may not chase them to the point you are no longer observing preservation of self, other human colonists, and/or colony infrastructure.”
It is not only about if you disengage, but also how I wish to disable you. I can let you go, or I can kill you. During delta alert it’s that simple. I can proactively engage them. Even then, I didn’t actually attempt to do so and had plenty of context that you might not know.
I came in first to security. You came after. Upon seeing you I walked away, into a dead end. You came closer, so I engaged you as I see that as threatening.
Further context. I had just fleed 30 seconds prior from a warrior who had just killed another survivor. Upon checking logs, this was NOT you, but it was my assumption that it was.
I was under no threat to my self preservation. If I do not die nor can reasonably assume I very likely will die if I pursue, I can chase you from security to Narnia.
The warrior I escaped, who just killed a survivor I was with, John Wheeler:
Note how I say “Pest.”, as I believe this is the second time we see one another. Either way, I had plenty of context to attack, but even lacking this context, I barely suffered damage and was under no risk to self preservation by attacking you, and therefore in my opinion have done no wrong in the guidelines. You can discuss it further with me here or DM me on discord under the same name.
As staff were unable to find your presence in the round ID you provided(ie, the round ID is incorrect), no logs were available to be pulled. Since the RID is invalid, we cannot proceed further. Previously we had been waiting for logs to be pulled for this.
The council did go ahead and make an evaluation based off of the information that was available, and came to the conclusion that there was no programming violation from Finn as he was adequately observing his self preservation when he made the decision to neutralize what was perceived as a threat.
The report is denied; incorrect RID provided and self preservation was not violated.
As staff were unable to find your(Dinoman98777) presence in the round ID you provided(ie, the round ID is incorrect), no logs were available to be pulled. Since the RID is invalid, we cannot proceed further. Previously we had been waiting for logs to be pulled for this.
The council did go ahead and make an evaluation based off of the information that was available, and came to the conclusion that there was no programming violation from Finn as he was adequately observing his self preservation when he made the decision to neutralize what was perceived as a threat.
The report is denied; incorrect RID provided and self preservation was not violated.
Thank you both for your time and input, and a thanks to the staff team for attempting to pull logs
