Staff Complaint - Alberyk

[GeneralCamo]

BYOND Key: generalcamo
Staff BYOND Key: alberyk
Game ID: Unknown, I believe the Round before ckZ-apDY
Reason for complaint: This complaint was late. This is being made due to, in hindsight, realizing what went wrong. I specifically believe that this incident was due to a lack of information I was given, as a relatively new player to events, and as such I contest the official warning being given due to having no knowledge of the specific bug, and little instruction in what languages I should have picked.

I volunteered for Dreary Futures: Episode 3. I was put onto the Elyran team, and given some instructions regarding the general idea of the round. This is all I was given, and when the event started, I had basically a character concept. I asked in AOOC what languages to pick, and one person (I believe Clem) stated "Sol Common, Elyran, and Tau Ceti Basic". This seemed reasonable to me, since we were expected to potentially directly get into conflict with the FSF (which is what happened), and talk with them. The other Elyran volunteer did not mention Sol Common, but I failed to see this and I had no reason to not pick it (based on what I knew of the round, and not knowing the existence of the bug).

During the round however, I noticed I had the other ship's comms. Noticing this, I mentioned this in AOOC. I was told it was an "unfixable bug" by dansemacabre, and not given anything else regarding it. My assumption was that event players were expected to deal with the bug, and not metagame. This was my first event, and I had no prior experience with multiple off-ship roles (My experience with off-ship roles up to this point involved only one off-map ship spawning). I ensured to ignore the words in sol common, and not use them to my advantage.

When the elyrans eventually boarded the Horizon, I mostly stayed in the hangar. When someone mentioned that the Sol Marines were moving, I moved back inside the shuttle and checked the sensors console. Based in their heading, I noticed that they were moving behind a dust cloud, which was a blind spot for those sensors. I assumed they were attempting to get behind the Horizon for another round of fire, and stated such in my team's radio. At this point, I was admin messaged by alberyk. They asked why I mentioned that they were potentially preparing to attack, and why I had sol common. I unfortunately do not remember exactly what I said, but I was warned in the end for "'During an event, picking the other team's language when they should have not due to ships' sharing comms." 

Evidence/logs/etc: I unfortunately neglected to take down exact logs for this complaint for this round. I genuinely felt extremely bad after that round. This complaint was made with the benefit of hindsight, but without the foresight of saving logs.
Additional remarks: I genuinely feel terrible for failing to have the foresight or confidence to question this directly in AOOC or an a-help after given the note that it was an "unfixable bug" by danse. My point here is to state that I had no prior experience with an event, no prior experience with off-ship roles involving multiple ships in the same map, no prior knowledge of this bug, and no clear indicators on exactly what I was to do. I was operating effectively blindly, and while I was praised for my efforts in the round, it did eventually lead to this unfortunate misunderstanding and event. My purpose of establishing this staff complaint is primarily to ensure this does not happens again, to anyone in a similar situation.

[Alberyk]

On 27/11/2022 at 07:57, GeneralCamo said:

This complaint was late. This is being made due to, in hindsight, realizing what went wrong. I specifically believe that this incident was due to a lack of information I was given, as a relatively new player to events, and as such I contest the official warning being given due to having no knowledge of the specific bug, and little instruction in what languages I should have picked.

You were made aware that I and the loremasters present at the time were running the show. Instead of using aooc or ahelp, which would likely get in contact with an admin, you just decided to ask in character, which is really weird.

On 27/11/2022 at 07:57, GeneralCamo said:

noticed that they were moving behind a dust cloud, which was a blind spot for those sensors.

There was no dust cloud.

The thing is, I only warned you for doing something that made no sense for the event. Why did you even pick sol common? You had basic. I decided to give you the benefit of doubt in regards to metagaming, because if I had enough evidence to decided that you did metagame, I was going to ban you. Playing as an event role is something important, and you are going to be held at a higher standard. This mostly comes down to some events getting "ruined" because of volunteers doing silly stuff.

[GeneralCamo]

On 28/11/2022 at 19:06, Alberyk said:

Instead of using aooc or ahelp, which would likely get in contact with an admin

I recall asking what languages I should pick in aooc, and being told "Sol Common", "Basic", and "Elyran" by a co-volunteer. I may be incorrect here.

On 28/11/2022 at 19:06, Alberyk said:

Why did you even pick sol common?

It seemed like an acceptable assumption that we would be engaging in discussion with the Sol Marines directly (though this did not happen admittedly).

[Garnascus]

Sorry for the late response. Was not aware this existed. My fault. 

Anyways, warning seems justified to me. Alb is correct that event volunteers are held to a higher standard due to the potential to really mess up a lot of work people put in to run events. A warning is exactly that "Hey you should not do this please dont do this again". 

[GeneralCamo]

The point of this primarily was to ensure this doesn't happen again. I believe a PR was merged in the interim to prevent exactly that. Since this was made, I cannot even recall any specifics of this event due to how long ago it was. I was pointed to some lore regarding languages in Elyra by another user, but I can't even recall if I was using that. This can be closed now.