DevinXoptoh - Player Report: WorkingJoe1612, Synthetic combat

DevinXoptoh - Player Report: WorkingJoe1612, Synthetic combat

What’s your BYOND key?

DevinXoptoh

Round ID:

21039

Your character name:

Runner CT-523

Accused BYOND key:

Unknown

Accused character name:

WorkingJoe1612

What rule(s) were broken?:

Synthetic combat

Description of the incident:

I was a runner attacking the APC in the engine room.
I did not attack the working joe or cause it any harm, if anything I was actively ignoring it entirely.
It then proceeded to attack me and put me into critical, which lead to my death.

I purposefully ignored the working joe on the grounds of them being non hostile unless provoked.

Evidence:

Was told by an admin that this was not an issue for them to deal with and was instead a whitelist issue, which is absolutely understandable

10 Likes

Relevant logs are posted below.

Involved Parties, Ckeys provided only for the reporting and accused players, all others are omitted.

Working Joe #1612 | Accused | Ro3ger
CT-631 - Xenomorph, Runner | DevinXoptoh


I should note that the Working Joe was controlled by a member of Staff.

The Working Joe uses emotes at assumed presence of a Xenomorph inside the Engine Core.
Feb 25, 2024 @ 23:19:28.213 21039 EMOTE EMOTE: Working Joe #1612/Ro3ger : presencelogged
Feb 25, 2024 @ 23:19:28.213 21039 SAY SAY: Working Joe #1612 [1]: Your presence has been logged. (CKEY: Ro3ger) (JOB: Working Joe)
Feb 25, 2024 @ 23:19:31.141 21039 SAY SAY: Working Joe #1612 [1]: You’re not allowed in there. (CKEY: Ro3ger) (JOB: Working Joe)
Feb 25, 2024 @ 23:19:31.141 21039 EMOTE EMOTE: Working Joe #1612/Ro3ger : notallowedthere

There is no log indicating that the Runner, CT-631, attacked or grabbed the Working Joe prior to this engagement, there are also no logs indicating if the runner had attacked any area of the Engine core, although the game does not appear to log this. But they undoubtedly had entered into the Engine Reactor Core Room.

The working joe attacks the runner, knocking them into critical health status.
Feb 25, 2024 @ 23:19:38.143 21039 ATTACK ATTACK: Ro3ger/(Working Joe #1612) attacked DevinXoptoh/(Runner (CT-631)) with �K92 Maintenance Jack (INTENT: HURT) (DAMTYE: BRUTE) in the �Engine Reactor Core Room (268,57,3).
Feb 25, 2024 @ 23:19:39.455 21039 ATTACK ATTACK: Ro3ger/(Working Joe #1612) attacked DevinXoptoh/(Runner (CT-631)) with �K92 Maintenance Jack (INTENT: HURT) (DAMTYE: BRUTE) in the �Engine Reactor Core Room (268,56,3).
Feb 25, 2024 @ 23:19:40.594 21039 ATTACK ATTACK: Ro3ger/(Working Joe #1612) attacked DevinXoptoh/(Runner (CT-631)) with �K92 Maintenance Jack (INTENT: HURT) (DAMTYE: BRUTE) in the �Engine Reactor Core Room (268,56,3).
Feb 25, 2024 @ 23:19:41.827 21039 ATTACK ATTACK: Ro3ger/(Working Joe #1612) attacked DevinXoptoh/(Runner (CT-631)) with �K92 Maintenance Jack (INTENT: HURT) (DAMTYE: BRUTE) in the �Engine Reactor Core Room (268,56,3).

This action results in the death of the runner.

ATTACK: Runner (CT-631) has died to �K92 Maintenance Jack at the �Engine Reactor Core Room from Working Joe #1612

There are no further relevant in-round events.

Ahelp logs.

Ahelp between Runner and Admin.
Feb 25, 2024 @ 23:19:51.930 21039 ADMIN ADMIN: Ticket #20: DevinXoptoh/(Runner (CT-631)): A working joe just put me in crit.
Feb 25, 2024 @ 23:22:56.265 21039 ADMIN ADMIN: PM: Biolock/()->DevinXoptoh/(Runner (CT-631)): Had to do some digging. It’s allowed in engineering.
Feb 25, 2024 @ 23:26:50.379 21039 ADMIN ADMIN: PM: Biolock/()->DevinXoptoh/(Runner (CT-631)): Technically it’s a whitelist issue, so if you’d like to chase this further I suppose you’d want to either make a player report or DM a synthetic whitelist councilor. However, to help you make an informed decision, I will post the whitelist rule here: In this emergency alert state, Biohazard Containment Level Gamma is in effect for the priority system locations: AI Core, and Engineering. This means that if a Working Joe is attacked, it may escalate with reciprocal force and neutralize the threat. However, the Working Joe(s) dispatched to Engineering 1F - Reactor Core should focus on priority repairs unless provoked, with trespassing generally being of insignificance during this emergency state.
Feb 25, 2024 @ 23:27:44.822 21039 ADMIN ADMIN: PM: DevinXoptoh/(Runner (CT-631))->Biolock/(): If its grounds of them being attacked meaning they can kill me? thats fine. I didnt touch them however and they just whacked me unprovoked
Feb 25, 2024 @ 23:28:43.933 21039 ADMIN ADMIN: PM: Biolock/()->DevinXoptoh/(Runner (CT-631)): You’re welcome to take it up with a councilor. Here is the full WJ manual: (Seegson Working Joe Manual - CM-SS13 - Wiki). Staff don’t handle whitelist violations unless they breach server rules.
Feb 25, 2024 @ 23:29:24.927 21039 ADMIN ADMIN: PM: DevinXoptoh/(Runner (CT-631))->Biolock/(): Is there a way I can get the logs pasted here so I can open the ticket properly and have the information required? It was 1612 correct?
Feb 25, 2024 @ 23:30:48.360 21039 ADMIN ADMIN: PM: Biolock/()->DevinXoptoh/(Runner (CT-631)): Yep, the working joe is #1612. If you post it on the forums staff will follow up and post the logs from the incident. Just make sure to include the working joe’s number, the round ID (found on the status tab), and a general overview of the incidents as you experienced them.

Reminder of this ahelp interaction are instructions on forum usage and is not relevant to this report.

Ahelp between the Working Joe and Admin.
Feb 25, 2024 @ 23:20:49.299 21039 ADMIN ADMIN: PM: Biolock/()->Ro3ger/(Working Joe #1612): You can not engage in combat outside the ARES core as far as I’m aware.
Feb 25, 2024 @ 23:21:00.392 21039 ADMIN ADMIN: PM: Ro3ger/(Working Joe #1612)->Biolock/(): I talked extensivly with the WL, go look at discord
Feb 25, 2024 @ 23:21:23.752 21039 ADMIN ADMIN: PM: Ro3ger/(Working Joe #1612)->Biolock/(): WJ part, I had a long chat and durring delta aparently you can combat inside engine core is what i got told
Feb 25, 2024 @ 23:21:25.270 21039 ADMIN ADMIN: PM: Biolock/()->Ro3ger/(Working Joe #1612): The working joe discord?
Feb 25, 2024 @ 23:21:54.558 21039 ADMIN ADMIN: PM: Ro3ger/(Working Joe #1612)->Biolock/(): Discord
Feb 25, 2024 @ 23:22:31.884 21039 ADMIN ADMIN: PM: Biolock/()->Ro3ger/(Working Joe #1612): Noted, ty
Feb 25, 2024 @ 23:33:44.642 21039 ADMIN ADMIN: PM: Ro3ger/(Working Joe #1612)->Biolock/(): For whatever report comes later, i looked into it, another runner had attacked me at the engine core so when the other guy came in i wasn’t reading names so I had assumed it was the other runner coming back to attack the engines then me
Feb 25, 2024 @ 23:35:21.940 21039 ADMIN ADMIN: PM: Biolock/()->Ro3ger/(Working Joe #1612): If a player report is generated, it’ll be up to the council. I can’t speak to any of this.
Feb 25, 2024 @ 23:35:48.217 21039 ADMIN ADMIN: PM: Ro3ger/(Working Joe #1612)->Biolock/(): ayup was just putting it down so when the report does eventually come out I can note a observation ahead of time

There are additional admin say logs regarding this incident, however due to these logs being privileged they will only be provided publicly if required by management.

Added report:needverdict and removed report:pendinglogs

Added report:synth

Hey DevinXoptoh and thanks for your report.

We would like to thank the moderator team and Steelpoint for posting logs for this situation.

After reviewing all of the available evidence and logs pertaining to this situation, there is now a clear picture of the situation and what occured.

As a forenote, during Delta Alert, Biohazard Containment Level Gamma is in effect at critical AI areas, this is highly restricted but it does include the Reactor Core in 1F Engineering.

A Working Joe is not permitted to attack you for trespassing Engineering under general circumstances, however, your case was different for two reasons. Prior to you entering the room, another runner and a lesser drone entered, and engaged critical infrastructure including the Working Joe - thus elevating the engagement in a manner which was hostile. Secondly, you attacked an APC in the core which is critical to powering the AI Core, as a result the Working Joe would have been justified in utilizing force against you.

Once again we would like to thank Steelpoint for their extensive logdives and allowing us to understand the situation collectively.

The report is denied; Working Joe 1612 was complaint to their programming in neutralizing and removing you from the Reactor Core due to hostile behavior from yourself and your fellow Xenomorphs - damaging WJ#1612 and critical infrastructure. I wish everyone pleasant day :slight_smile:

2 Likes

Added report:denied and removed report:needverdict

From Player Reports to Whitelist Reports