Player report - Jim (not asking for him to be in trouble)

[Royal Griffon]

Your Byond Key: Royal Griffon

Your Character Name: Mikey 'Snatch' Anders

Accused Byond Key(if known):

Character Name: Jim (synth)

Approximate time and date of the incident (Central US Time for fastest results): hmmm about 10:50-ish maybe EST

What rule(s) were broken: Synth roles and jobs

Description of the incident:
Well I did kind of ask for it, but not exactly. So I had been headbutted by a warrior in the head, giving me eye damage and a fractured skull, so I wondered around medbay a few, half the doctors were role-playing it seemed so they didn't really do their jobs like they were supposed to but I wouldn't blame them. But I wondered around and bumped into Jim, well hell synth players can usually do medical shit like it's nobody's business so I immediately ask for assistance asking if there was some quick fix for it and he told me the permanent way was surgery. Well of course I didn't deny that, free medical service and bumped to the top of the list. So I told him to go ahead and give me surgery, well he kind of forgot how to do it after saying he hadn't done surgery in a while in LOOC, well I gave him the benefit of the doubt and told him to continue in LOOC. However I knew that the surgery was likely very wrong saying my character began to get a very high fever and also began to lose feeling in their head.
Then the ship crashed into the Alaymer and well I woke up worse than I went in. So basically I got medical malpracticed by a synth due to them forgetting how to do medical and such.

Evidence (screenshots, logs, etc): none really Jim was the Synth, and I was a charlie engineer. I messaged Kekse or Kekke? The mentor about a xeno paincritting marines in nests that round's ending though.

How you would punish the accused: make sure they know how to do surgery and give them a re run of all the surgery procedures and such. Basically practice and yes I did make this so you guys could be aware about Jim. I'm not really asking for drama or anything bad to happen, but I do wanna make sure they don't do surgery without knowing how to do it again on someone else who isn't forgiving enough to not ask for their synth whitelist to be removed.

[solidfury7]

You likely got an infection during surgery.

I think there is a lot at play here,

The syth lacking knowledge on surgeries or at least being rusty.

The fact the dropship crashed in to the ship, likely taking down medicals apc and thus scanners.

Aliens being present on the vessel (Maybe ending surgery could have been a better solution than allowing you to be swarmed during it)

It's hard to tell with the limited data.

I can say however, while synths generally have to have a good knowledge of the game, we don't really enforce it in a way where people have to be excellent in every role.

Synths are people at the end of the day and slip ups can be made. From forgetfulness and misclicks.

[Karmac]

This is the kind of thing that, at worst, you would ahelp during the round, asking for a mentor to explain how 2 surgery for the guy. Not the kind of thing you make a player report about.

[Royal Griffon]

I know I just wanted to make sure you guys knew about it and such, in case they forget about going over it again and get someone a lot more angry about it than me and such

[contactdenied]

It's been a pretty long time since I actually had to do surgery, maybe a month or two, so I had to have the wiki up and constantly flick between it and the game. When I finished on your eyes and skull your head necrotized so I had to perform surgery on you again, though I'm pretty sure I did mess you up more than I helped, so sorry for that. I think I would've finished up faster had I not been confused where the tools were (didn't realize updates put them in surgical trays, i'm used to a bag or a table) but its unlikely. Again, super sorry for messing you up, I'll go a few rounds as doctor to un rusty myself.

[Emeraldblood]

This report isn't in need of any serious actions. Everyone makes mistakes sometimes and unless this becomes a bad trend, there's no need to take any action against someone for a simple mistake. Resolved - no actions required for this report.