Staff report - SpookyDonut

[Chaznoodles]

Your Byond Key: Chaznoodles

Your Character Name: Marcellus Mason

Their Byond key: Spookydonut

Approximate time and date of the incident (Central Us Time for best results): 29/09/2018, 15:20CST

Which Staff Protocols (http://www.colonial-marines.com/viewtop ... =57&t=5647) were broken: Code Of Conduct - Do not abuse your power, preserve the RP and enjoyment of the server (Do not try to heavily influence the game unless it is for very good reasoning). No staff protocols as staff member is a developer.

Description of the incident:

With the help of two others, I killed a predator - played by Spooky - that had been firing plasma launcher shots at the FOB and spikelaunching every marine in sight. I nick his armour and pouch, as marines are wont to do as trophies. I womble around in the kit, looking swanky, xenos eventually board. I trigger not one, not two, but THREE claymores. With the first one I put it down to something going wrong, after the second and third I adminhelp, replies from Dorkkeli stating:



Round shortly ends, I bring up the issue in OOC. Spooky replies, see evidence. It's downright abuse of a developer's - and a head of staff's - powers to interfere in someone's round purely because you died, and has left yet another bad taste in my mouth in regards to my interaction with him.

Evidence (screenshots, logs, etc):




How you would punish the accused: Unlikely he'll be punished at all because he contributes to the code, even though this sort of thing has apparently happened more than a few times. Removal of public server +FLAGs, restrict them purely to private server use so he can't pull another stunt like this.

[Survivor]

I was a witness to this. Although I like spooky, I have to agree that this is not right, and not only affected Chaznoodles, but it affected me.


I was the Commander when he set off a mine directly next to me, injuring not only Chaz, but also me. Although it was near the end of the round, I still don't think it's right for this to be allowed, and it really surprises me it was a head of staff who abused this power.


Edit: Seriously, that is ridiculous that the mod got demoted for being honest about Spooky abusing his power.

[Tharinoma]

Some logs were pulled, not posting them here as they obviously contain staff-only info.

[Kerek]

A little bit ago Spooky gibbed a hunter for no reason. This is his second instance of abuse, and this needs to be more than just a warning. There needs to be some sort of reprimand for this as he clearly cannot be trusted with perms like this.

Information that got your boy on probation. Audios peeps.

[Emeraldblood]

This is under investigation. If you don't have anything related to this case, please abstain from commenting.

[RedsPro]

Chaz also got to an Escape Pod that round and closed the doors right before a runner caught up to him. Then the door was deleted and the runner walked on in. That may have been spooky as well

[Chaznoodles]

Chaz also got to an Escape Pod that round and closed the doors right before a runner caught up to him. Then the door was deleted and the runner walked on in. That may have been spooky as well

This would make a lot of sense. I did hit the button to lock the escape pod and launch and the doors did close. I was under the impression they had been forced open by the runner, but this would make more sense as there was no door icon left on the tile.

Information that got your boy on probation. Audios peeps.

I'm disappointed in whoever demoting a staff member for being transparent was a good idea. I've had a few people message me with issues they've had with Spooky in the past, which they haven't felt keen enough to post in the thread. This sort of staff attitude, where someone gets put on probation for making information public regarding other issues, contributes to nobody making reports and people getting away with their actions. Without problems being mentioned openly, without the threat of reprisals for honesty, we end up with situations exactly like this - people getting away with things they shouldn't.

Shame on whoever did this.

[Novus Luna]

This would make a lot of sense. I did hit the button to lock the escape pod and launch and the doors did close. I was under the impression they had been forced open by the runner, but this would make more sense as there was no door icon left on the tile.



I'm disappointed in whoever demoting a staff member for being transparent was a good idea. I've had a few people message me with issues they've had with Spooky in the past, which they haven't felt keen enough to post in the thread. This sort of staff attitude, where someone gets put on probation for making information public regarding other issues, contributes to nobody making reports and people getting away with their actions. Without problems being mentioned openly, without the threat of reprisals for honesty, we end up with situations exactly like this - people getting away with things they shouldn't.

Shame on whoever did this.

This was discussed at the Townhall and I can agree well with SLC. The issue isn't that he posted, it's that he posted something opinionated. The first sentence of his comment where he said a factual witness statement was fine, it was his opinion on how to address it that was an issue. SLC also stated that the probation was a bad move and attempted to undo it.

[spookydonut]

After discussing this with Jamie we agreed it was a few steps too far for rule 0.

As such I would like to apologise to chaz for unduly affecting his round, as well as all those affected by the mine blasts, it was wrong of me to do so. I will do my best to ensure this doesn't happen again.

[Chaznoodles]

After discussing this with Jamie we agreed it was a few steps too far for rule 0.

As such I would like to apologise to chaz for unduly affecting his round, as well as all those affected by the mine blasts, it was wrong of me to do so. I will do my best to ensure this doesn't happen again.

That doesn't cut it. A fake apology is just as bad as the abuse itself. You're only apologising because someone else, in frank terms, told you to.

1. This sort of thing has happened before, this isn't the first time. There's a trend here of abuse of role powers that an apology doesn't just make magically vanish.

2. It took another, higher member of staff to point out that it was too much, else you would've just went along your merry way.

3. If this report hadn't been made to cause #2 to happen, you'd have just went along your merry way.


I've had more than a few messages now concerning other abuses of power from him - such as gibbing xenos, respawning himself after ghosting if he died/got arrested for improper escalation, marines being gibbed or nuggeted, and people feeling targeted by his actions. The lack of any attention it's received from staff, as well as the unwillingness of players to make reports due to possible repercussions of doing so, is a complete joke.

[Emeraldblood]

I've gotten a few messages and concerns about it but this case isn't being closed with Spooky saying sorry and isn't being overlooked by head staff. While it may be a few hours or a day before we get an official closure to this, it's not being dropped or ignored. Spooky and Jamie tend to be around (as per EST) during night hours and Slc and I are on during the day which means we're not all around at the same time. There will be an update to what's going on so just hold on for us.

Regarding Kerek, I'm not going to go into details as you can talk to him if needed, but there was a conflict with him and another staff which lead to him saying he'd rather just retire than deal with it. The conflict wasn't about him sharing information but him being openly hostile to a fellow staff. All head staff agree that we don't want staff to say things like that in public about fellow staff but it never should have hit the point of retirement. I've talked to Kerek to resolved this issue and he is back on the team with no strings attached.

[slc97]

Alright, Emerald, Jamie and I have discussed what we believe to be the most appropriate action. At this time we are removing permissions for whitelist roles from Spooky that he did not receive by application, i.e. CO and predator. These will be removed for an as of yet undetermined amount of time. We believe and hope that Spooky has seen the error of his ways; however, should abusive behavior continue, perms will continue to be stripped and removal from headstaff is not out of the question. This is not old CM. There is no permanency to headstaff positions.

My response to Chaz in the matter is this: Just chill, man. If Spooky's apology was gonna be all that was done here, we would have locked the thread and been done with it, but that's not how we operate anymore. Everyone is accountable for their actions now. We get it, you're a crusader for truth, justice, and the American way, but a lot of what you said is blatantly untrue. We do not just ignore issues of abuse. This complaint has been up 24 hours and it's about a headstaff member. That just takes time. Furthermore, the community has no reason to fear reporting instances of abuse by any staff member. The only time there will ever be punishment is for blatantly false reports. Otherwise, the worst thing that will happen is me telling you not to be as much of a drama queen. In the last months we've administered CM and involved the community in a much more fair way than has been done in the past. All we ask for is a little faith before y'all light the torches and pull out the pitchforks.

Jamie will be revoking the perms, and we are considering this report resolved.