Helixsix - Staff Report: Behavior involving Misconduct - NessiePendragon

Helixsix - Staff Report: Behavior involving Misconduct - NessiePendragon

What’s your BYOND key:

Helixsix

Round ID:

28411

Your character name:

Arayli “Ashes” Svipul

Their BYOND key:

NessiePendragon

What are you reporting?:

Behavior involving Misconduct

Description of the incident:

Soro got an overhaul last night, and there was a tie between LV-624 and Soro, resulting in a Soro win. Nessie proceeded to force LV-624 and then disconnected from the server. This reset the Soro vote tally count due to Soro winning, and has prevented people from seeing how the overhauled Soro map is. It felt pretty shitty to have happen, and I wish admins wouldn’t do things like that when people are actually excited to play a map.

Evidence:

Should be able to review logs in the round, unfortunately my forum account was not approved and I did not realize what exactly would be needed.

20 Likes

So this is correct, yes, the votes for Sorokyne and LV were tied, and RNG selected Sorokyne. I took the initiative and forced the map to LV instead. If Sorokyne had won even by a single vote, I wouldn’t have done that. I didn’t really get a chance to play CM much during the day, so before going to bed, I wanted to enjoy a round on LV and no, I did not disconnect after forcing this. I played as a Xenomorph until hijack, and I had a great time.

I’m only just now hearing from you that there’s an overhaul for the Sorokyne map. No one informed me about this, and I’m not someone who actively reads PRs and test merges. If I had known about it earlier, of course I would’ve wanted to see the new version of Sorokyne. I am sorry about that.

14 Likes

This was a good faith mistake, and I will speak with Nessie regarding appropriate use of force map.

1 Like