[Resolved] Unfair Strike - Alberyk

[hivefleetchicken]

BYOND Key: Hivefleetchicken (Discord ID: #7397)

Staff BYOND Key: Alberyk, Skull132

Game ID: Occurred on discord.

Evidence/logs/etc:

 

 

Logs speak for themselves. My discord lagged out since I was on mobile. When I logged onto my computer I saw the message had duped 4 times. Alb gave me a strike for it and refused to remove it. I told Skull I was going to make a complaint if he didn't fix it and he got cheeky with me telling me he didn't even have to respond for 72 hours.

Proof I still have the strike:

 

 

Additional remarks: Yeah gonna' have to ask not to get pushed around by cocky staff because my discord lagged out. I want this strike removed, end of story.

[Alberyk]

I don't think I can remove strikes, if I could I would because I see this was caused by lag. I told you to ask skull because he can do so, and I have little control over what he can do or not. And I never refused to remove it because as I said, I can not remove strikes.

[Skull132]

Strikes require direct database manipulation to remove, because I'm too lazy to write up a proper interface for it. I told you I'd remove it tomorrow, twice. You were unhappy about it so I said that, as per our SOPs, we are given 72hrs to respond to most things. The implication being that I've acknowledged your query and will be responding to it within those 72hrs.

If recounting SOP is being cocky, then okay. The "Good luck" was added because you seemed to not be serious about it. (Seriously, getting in a tussle over being told that something takes time is childish, as is this complaint and your conduct about the matter.)

[Scheveningen]

Additionally, just last night when the server went down due to an issue with BYOND, about four people and I believe yourself were spamming the bot's commands and generally putting an unnecessary amount of strain on it and also spamming up the entire chat.

It was kinda hard not to assume that was going on since it occurred pretty much a couple hours since that happened and it didn't really occur to anyone that it was discord screwing up again. In spite of that, I still think it's a bit of an unlikelihood, but one has to at least look a bit inward and distance themselves from their own situation to see why staff actually did something. I like to think there was good intentions involved, I think Alberyk did think you were spamming.

As an end-result a single strike is really inconsequential and as Skull said, he'll try and fix it.

[Chada1]

I was there for this, I do think it was an accident on Alberyks part that he really shouldn't be held accountable for, it was an easy mistake to make, and one he hopefully won't make again under the same circumstances, as for that, it was also out of Hives control, so it would suck to keep this strike. But, I understand it's being removed, so that's all fair and good.

[Skull132]

Can [mention]hivefleetchicken[/mention] explain why this complaint is a thing? More specifically, what staff conduct rules were broken and what he expects done about it. Because.

Alb already explained why he issued the strike, on Discord.

I already answered, on Discord, that the strike would be removed today.

So what is the issue here? The fact that you didn't like our answers, despite there being literally nothing more to it?

[hivefleetchicken]

Just waiting for it to be removed fam

[Skull132]

I don't think that's valid use of staff complaints.

Understand: you submitted a complaint against the conduct of myself and Alberyk. This is not a support ticket for getting your strike removed.

So please, do answer my question.

[hivefleetchicken]

I made the complaint because me lagging out once was a reason to, without warning or orders to cease, give me a strike in Alb's eyes, and when I asked for it to be removed and explained my case, I was told to "take it to skull" instead of a "oh ok, ill speak to skull about fixing it" or anything short of "nothing im gonna do about it ask someone else". I brought it to you myself stating i would make a complaint if my strike was not removed, and you cheekily responded that you didnt even have to respond or fix anything within 72 hours, telling me "Sooooo good luck", so i just followed through and made one that i intend to bitch and moan on until you guys decide to remove it

there is LITERALLY nothing more to it than me wanting the strike removed, and you telling me "well i dont have to do anything for 72 hours sooooooo GOOD LUCK!" isnt a very courteous response to me asking for it to be removed after explaining it was an unintentional spam.

[Skull132]

So it does boil down to "You didn't talk to me as I think you should!" Okay.

Also, "i intend to bitch and moan on." Literally not how complaints work, and I would love something being done about this.

Anyways, until a third admin rolls around to address the complaint as an impartial party, I have little more to say on the matter.

[hivefleetchicken]

Lol okay skull.

Sure, I made this complaint because you responded like an actual baby when i respectfully requested for one of your admins, and then yourself, to fix an error you made.

Or maybe I just want the strike removed and for you to stop guffawing that "technically i can keep it on you for as long as up to 72 hours" because for some reason that seemed to really please you when you brought it up

I dont expect you to have much to say and i certainly expect you not to try to strawman me again, i just want it removed already fam.

[Faris]

A) When it comes to pinging the bot, do so in PM's as it still responds to it.

B) Skull was unable to remove it instantly for reasons mentioned. The 72 hour remark was to show he is not obligated to drop everything he's doing to do the requested task.

C) The act of spamming the bot is done by people and they are punished accordingly. The levels of spam caused by your client is one I've personally not seen by anyone else so it's a fair assumption you may have done it maliciously, but it is now cleared it wasn't and you're being directed to privately PM the bot in the future.

Now, I believe this settles it. I'll keep this open for another 24 hours. Should there be more issues, it'll be extended.

[Scheveningen]

Alberyk - Yesterday at 5:14 PM
?strike @✞ just a whitey from blighty ✞
✞ just a whitey from blighty ✞ - Yesterday at 5:14 PM
how many times did that send
???realisBOT - Yesterday at 5:14 PM
.Alberyk, operation successful!
Alberyk - Yesterday at 5:14 PM
Stop with the spam.
✞ just a whitey from blighty ✞ - Yesterday at 5:14 PM
what.
that was lag.
Alberyk - Yesterday at 5:15 PM
So, pm the bot.
✞ just a whitey from blighty ✞ - Yesterday at 5:15 PM
i only did it once are you joking
Lohikar - Yesterday at 5:15 PM
Came through 3 times.
✞ just a whitey from blighty ✞ - Yesterday at 5:15 PM
its not my fault discord sucks
came through 4 times
Lohikar - Yesterday at 5:16 PM
Oop, didn't see the top one.
Alberyk - Yesterday at 5:16 PM
Ask skull to remove the strike then.
✞ just a whitey from blighty ✞ - Yesterday at 5:16 PM
that said, it's not my fault discord sucks
unstrike me
@King Floof
King Floof - Yesterday at 5:16 PM
Manana.
✞ just a whitey from blighty ✞ - Yesterday at 5:17 PM
unstrike me please @King Floof
King Floof - Yesterday at 5:17 PM
Tomorrow. 
✞ just a whitey from blighty ✞ - Yesterday at 5:17 PM
unstrike me now, please
or im gonna have to make a complaint
King Floof - Yesterday at 5:17 PM
Staff are required to respond within 72 hours. Soo.
Good luck.

 

Here are the logs for posterity. I'll weigh in.

1.) The nature of the strike. It looked like you were spamming. Until you, Hive, spoke up after the strike, we had no way of knowing otherwise. It is not easy to remove strikes, only an individual with database access to the strike system can do so. Since that is up to one person -- I'll touch on this in a later point.

2.) In response to the "unstrike me NOW" comment followed by the threat and eventual write-up thereof, a forum complaint. Right, in my opinion, Hive, I think you could've afforded to be more patient, and you'll generally find staff members unresponsive to statements like that because it is rude and unbecoming to conduct yourself in such a fashion that you are pretty much threatening a staff member to do something now or else you'll make a complaint on them. Skull could not, and most certainly would not, immediately beeline to his desktop, pull up the particulars of the database and rush to remove the strike on your discord account just because you said you'd make a complaint on him. We do not make good times intimidating players, nor should players try to do the same by attempting to threaten staff. Here we are, in that respect.

3.) I'm pretty sure you just now made this complaint because you still hold a semblance of a grudge against Alberyk and Skull after a year and a half to figure out how to drop it. I'm not going to detail specifically into the whys because that will generate more forum drama. But please step back for a moment and actually look at the content and phrasing of your attempt at engagement with both Alberyk and Skull. You are being unnecessarily hostile and overdramatic even though Skull would tell you he would take care of it within the three day period, at least 1 day at most 3 days. Are you not satisfied with that resolution? I'm confused, because that is a staff member who basically said he'll remove the equivalent of a warning after you asked for it to be removed and even Alberyk stated already that he would try to get it removed if he had that power. He doesn't, he deferred you to Skull, who told you at least in a day at most 3 days, and you got upset at hearing that.

I hope we can move on from our weekly moral outrage incident, we didn't seem to have one for awhile.

[hivefleetchicken]

I think youre reading into this way too much. I wanted my strike removed and now its removed so im happy. Requesting a lock.

[Faris]

Locking and archiving per request.