Nettle - Whitelist Report: Dean and Chloe, Self Preservation for both Dean and Chloe.

Nettle - Whitelist Report: Dean and Chloe, Self Preservation for both Dean and Chloe.

What’s your BYOND key?

Nettle.

Round ID:

27095

Your character name:

Ancient Praetorian (WOE-196) for majority of the round.

Accused BYOND key:

SmellyHippie as Dean, Omicega as Chloe.

Accused character name:

Dean and Chloe.

What rule(s) were broken?:

Self Preservation for both Dean and Chloe.

Whitelist in question:

Synthetic

Description of the incident:

For Dean: 01:22 round time, they took a solo trip to the secondary telecommunications tower east of primary LZ to clear a pylon.
It is my understanding, that under current guidelines, the “Synthetics Cannot: Freely run around and explore the colony by themselves; Set up the comms/sensor towers by themselves” also implies the synth can’t go on a solo adventure to clear out pylons.

For Chloe: 01:27 round time they went to hive dive with one other person. All the way into north-west reactor while marines were occupied with recovering from a siege on the exact opposite edge of the map. As the result both of them were eliminated from the round, Chloe in particular was gibbed by the Queen and never recovered, since marines never made it past Bar throughout the round.

I want to make it clear that this report is not being written with a hot head, its not the “I died, de-WL them” kind of report. I’m almost entirely indifferent to its outcome and I personally don’t have anything against either of the players being reported. However, on multiple accounts in the past, when I would bring up my general dissatisfaction with this whitelist, and how guidelines are largely ineffective and WL holders casually don’t follow them every other round, I was told to report it. So I do now.

Evidence:

None that would help.

11 Likes

Hey guys.

Queen here.

Here is my perspective of both events in video format.

I did not make a report at the time because I was consulting with a Synthetic Councillor on whether or not this was a rule break since I am not aware of the intricacies of the synth whitelist as I only play TGMC synths which are very simple; stay with marines, and do not attack unless in self defense.

This streamable will end in about a day or so but I also sent the full mov file to the councillor in question for record keeping purposes as requested.

6 Likes

Hi, I play Chloe and was a FORECON synth for the incident in question. I have my own POV of events here for clarity’s sake.

For context, we had just had the FORECON CO get capped somewhere north of LZ1, and as a whole the FORECON squad decided to try and retrieve them despite the admittedly low odds of doing so. Somehow the rest of the FORECON team managed to get picked off and capped before we even formed up, so by the time we made it up north it was just myself and one last marine. The hope was that the new queen would be off ovi by the time we got there, and we could stuff any nested FORECON into bags and sneak back out of an unoccupied hive to try at least and save them.

We had to take a very circuitous route around the southern edge of the map and up north past the sensor tower to get into the eastern reactor at all without running into the xeno frontline. That’s where the footage picks up, with an Almayer SO giving us directions towards the nested FORECON CO via the tacmap.

I don’t have much to add beyond the context above and providing my own POV, which shows a bit of the leadup before the point at which Swagile’s links up with it. About the only thing I have to add is that the intention was to grab the captured FORECON and sneak out again, not to walk into a queen jumpscare after five minutes or so of no MD pings whatsoever.

11 Likes

Apologies for the late resolving of this report. The report has been accepted.

Player/Manager Dean has opted out of the WL so no punishment is needed.

Player Omicega has been issued a first time warning to not make the same mistake again, these violation falls under the new guideline updates. Which the player should reread and familiarise themselves with to avoid repeating these errors. This is a first offence, any repeat offences will bring harsher punishment.

2 Likes