Commissar_Drew

Had the opportunity to play a round with their RD. Communicated well. Worked with other command staff to address the issues on station. Seems to have solid control and smooth operation of their own department from an outside perspective. +1.

Good to go. Thanks.

BYOND Key: commissardrew Total Ban Length: 1 minute Banning staff member's Key: ffrances Reason of Ban: You, or another user of this computer or connection (wizard1012) is banned from playing here. The ban reason is: No roleplay, spamming allcaps curses in adminhelp when contacted. Reason for Appeal: I am once again asking for help removing a ban that I am unfamiliar with. It was applied on 2014-12-21 19:09:10. The system has failed us again. Please help.

I approve of this. Would be a good addition to officer lockers and the loadout alike.

Corporate Security Beret under beret options, please!

Reporting Personnel: Kris Broklaw Job Title of Reporting Personnel: Security Officer Personnel in Question: Ryan Barrett Job Title of Personnel in Question: Cargo Technician Reason for Review: [x] - Extended Arrest History [ ] - Grievous Infraction on Record [ ] - Other: ____ Notes: Is not receptive to low level corrective action by security or station command personnel. Current records indicate employee is part of the Solarian Prison Outreach Program. The reasoning for his posting is to "improve his work ethic around co-workers of other species." Current arrest history does not show desired improvement for the program.

BYOND Key: Commissar_Drew (client sometimes registers it as commissardrew). Total Ban Length: Unknown. Banning staff member's Key: alberyk Reason of Ban: assaulting someone for little reason and then going ssd right after Reason for Appeal: Date of the ban is listed as 2020-06-11 at 1530. I was not playing on the server at this time. I believe there is some sort of technical issue here as I have been playing over the last several days - after having returned from a few years long hiatus last week - without any issues.

Please note, no relation between Milo Frost and our erstwhile admiral.

There is a cryo pod in the brig for permanent holding prisoners to utilize if they don't want to hang around the brig.

Even in shelved death, Milo was still HoSsin' on.

I like the idea, 1138. Perhaps, in addition to this change, have a message sent to heads of staff that an ERT is en route? This would lessen the amount of "ERT called > Immediately call shuttle" that I feel may occur if there is no confirmation that the call was received. The confirmation could be fax, requests console, or a PM a la the emergency message CentComm response.

Byond key: Commissar_Drew Character names: Milo Hachert ; Lukas Cain ; Drew Valstrom What times are you available? In GMT: 11 PM - 4 AM (weekdays) ; Open (weekends) Do you have any experience with Moderating? Or similar. Former Baystation12 moderator. Former Aurora moderator. Former administrator on Exogenesis. Why do you want to be a Duty Officer? It seems that more Duty Officers are required. I love Aurora. It's my favorite station to space on. I want to "give back" in some manner, and being a DO seems like an excellent way to do so. How well can you handle stress? I am under the impression that I can handle stress fairly well. I have operated in a leadership capacity under stressful physical and mental conditions in the past, and I emerged from the experience with a deeper understanding of what stress really is. What does it mean to be a Duty Officer? ICly: To be a DO is to be the voice of the corporation. You are the impartial voice on the far end of a telecommunication line, or the black clad inspector stalking the halls. To be a DO is to embody the idea of NanoTrasen. You are the corporation made manifest. You ensure the image of NanoTrasen remains untarnished will profit margins remain high. You eliminate incompetents and liabilities and laud professionalism. OOCly: You are in place to provide advice when called upon and facilitate RP situations for the crew. You must be attentive and professional to provide a fun experience to as many as possible. To be a DO is to be a sort of mini-DM. You must hold other's experience above that of your own for you DM not for yourself, but for the players. How active on the forums and server are you? I check both daily. Often I play at least one round a day. Anything else to add? It's good to be back again.

Onto the subject at hand. People, for some reason that I have yet to comprehend, dislike those in positions of authority, or those who enforce the status quo. The "man" always seems to be in the way stamping down on "fun". In some cases, this is true, and these cases bring me to point one: Security can be lenient. Issue warnings. Talk to folks. RP it out. This segways into point two: act professional. Be professional. As a security officer one should maintain a certain level of decorum. This does not mean you need to be an unfeeling robot, but as an officer, ideally, people should be unbiased, cool, and collected when responding to situations. And hopefully not threatening people with beatings, briggings, or such (overtly). I have guides, several, actually, that I have written over the past few years. They outline behavior for an officer and promote a thinking, feeling, professional. But, in reality, what it boils down to is having thick skin. As security, you need to brush off the stupid and function as a professional. Person berating you, your mother, and your dog? "Thank you for your time, sir. Have a secure day." Cowboy up. To be in a position of authority, to be a leader, to be a sheepdog you must be able to shrug off the sheep's bleating and keep the vigil all while not nipping the sheep too hard.

You do have a point here, Skull. I'll concede that it may not be a good idea to include it to tator tots uplinks; however, I still feel that armor (i.e. hardsuits) should block it out. One of two ain't too bad. I do think this "range cap" would cut down on the silly situation of taser versus lethally armed opponent. I'm not precisely sure what you're saying here, Skull. Maybe you've misunderstood me, or I am misunderstanding you. Could you rephrase your point here, please? Specifically: Thank you.

Right, folks: long ago after the taser was originally pulled from the depths of the Bay code, I remember the conversations that flew. We decided the taser was too weak, so it was buffed to its current state. Now certain parties are suggesting the switch back to the original. Let me reiterate the biggest concern I can remember: "Security will resort to lethal weapons too often." And, to be honest, wesecurity will. People will die. People will complain. And we'll need to switch /something/ again. WeSecurity shouldn't need to break out a rifle for that knife wielding assistant (and you know wethey very well might) To those who say that they don't like seeing security rush into a hostage situation: It's going to happen /regardless/ of gear. Security players are not trained. Some do not know how to approach a situation like that. Some do /not/ think critically and just seek out "Catch that antag." You debuff tasers? They go in with batons and flashbangs. The only way to stay on top of this is to /train/. It is to prepare officers for this. Which is a responsibility that I feel falls to our heads of staff whitelistees and server staff in situations that outstandingly call for it (repeated behavior despite training, etc). Personally, as a security regular, I have a pair of counter-suggestions: 1) Instead of a debuffed through number of shots needed to down a suspect, could we limit range? Our pepperspray is already capped at three tiles. Would it be difficult apply a range cap for the taser? (//ASIDE\\ Hell, if we went this way and coupled it with the next option, we could make it one hit again, but that is neither here nor there.). 2) Grant tator tots equipment that is taser resistant. My taser /shouldn't/get through that hardsuit rearguards of it being security, engineering, or operative. For your run-of-the-mill tators, grant them, perhaps, armor/padding option through the relay. Something concealable. Perhaps add resistance to the chameleon jumpsuit? So, folks, let's not debuff the tasers to require more shots. Let's buff the bad guys who needshould have the buff.

Reporting Personnel: Milo Hachert Rank of Reporting Personnel: Head of Security Personnel Involved: Maka Hirasawa, Reported Person ; Jim Calhoun, Security Officer, Reported Person Milo Hachert, Head of Security, Reporting Person Elephant, Security Officer, Witness ; Eliot Clef, Security Officer, Witness ; Skyler Brigs, Security Officer, Witness Time of Incident: ~14:30 Location of Incident: Brig Nature of Incident: []Workplace Hazard []Accident/Injury []Destruction of Property [X]Neglect of Duty []Harassment [X]Assault [X]Misconduct []Other _____ Overview of the Incident: All security personnel were provided with the following 'brig rules': Within a short amount of time, it was found that Officer Calhoun ordered a 'party crate' from cargo. It was shortly after this that officers reported Warden Hirasawa and Officer Calhoun consuming liquor. Officers detained Calhoun without incident for violation of i111: Failure to Execute an Order; however, upon confronting Hirasawa, she drew her taser on personnel and fled. Upon being cornered, she surrendered, but not before deploying her taser against Commander Hachert. Both were promptly placed in a brig cell and their charges applied (i111 for Calhoun. i111 and i202 for Hirasawa). Further, both were suspended immediately. Following his suspension, Calhoun exhibited suicidal tenancies and was found covered in his own blood. He was promptly handed off to medical. Hirasawa was reported to be "hoping to become an mercenary and take you (Commander Hachert) out." However, due to the insubstantial nature of the report as to Hirasawa actually saying this, no action was taken on that specific comment. Did you report it to a Head of Staff or IAA? If so, who?: Yes. Roxanna Yamato, Captain Additional Notes Recommend Action - Suspension from Security. - Mandatory psychiatric evaluation for both.

Reporting Personnel: Milo Hachert Rank of Reporting Personnel: Security Officer Personnel Involved: Milo Hachert, Security Officer, Victim/Reporting Person ; Nia Snyder, Security Cadet, Perpetrator ; IAM, Forensic Technician, Witness ; Sslazhir Yinzr, Security Officer, Witness ; Raymond Galloway, Head of Personnel, Head of Staff handling situation Time of Incident: Approximately 13:50 Location of Incident: Primary Tool Storage ; Brig Nature of Incident: []Workplace Hazard []Accident/Injury []Destruction of Property [X]Neglect of Duty []Harassment [X]Assault [X]Misconduct []Other _____ Overview of the Incident: Miss Snyder was assigned to my person by Commander Ezra Scott at approximately 13:45 station time. We commenced a patrol from the fore section of Aurora Station to the Arrivals' Checkpoint. En route to Arrivals, our patrol encounter Through Rising Flames (TRF), a diona assigned to the facility atmospherics. Cadet Snyder approached TRF and ordered him to remove the fire-suit he was wearing on threat of detainment. Cadet Snyder was requested by me to provide the regulation that TRF was violating. She failed to provide any valid regulation. She then proceeded to insult me, utilizing the word "retard" and question my competence as a security officer. TRF was instructed to carry on by me. Cadet Snyder then pursued TRF and attempted to flash him. I drew my taser and ordered her to halt. After a short exchanged laced with further insults from Snyder, during which I holstered my taser, she handcuffed TRF and escorted him to the brig. Upon reaching the brig, Snyder was question as to why she had arrested TRF. She again failed to provide a charge and stated that she was "confiscating the equipment." Officer Yinzr and Technician IAM unrestrained TRF and removed him from the brig. Snyder then applied more insults to my person, again questioned my competence and departed. I followed, saying that this situation was not resolved, as it wasn't due to her violation of i205: Illegal Detainment. She then turned, rushed at me, and struck me twice due to me referring to her as a cadet, which was her proper rank at the time. Snyder was then detained utilizing a stun baton and placed in the brig under violations of i103: Minor Assault and i205: Illegal Detainment. Mister Raymond Galloway, Head of Personnel, was informed. On his order, Miss Snyder was suspended for the remainder of the shift from security. Did you report it to a Head of Staff or IAA? If so, who?: Yes. Raymond Galloway, Head of Personnel. Additional notes: Miss Snyder was shown to be quite insubordinate to Commander Scott prior to her pairing with this officer. Showing a lack of respect that further reinforces the point below: It is the opinion of this officer that Miss Snyder should receive suspension from security/demotion to security cadet until such a time that she can show a more accomplished understanding of the department's role, respect to her fellow crew members inside and out the department, and a more complete understanding of Corporate Regulations. Conduct such as hers shines a negative light on the department as a whole and creates a toxic work environment within the department.

Point One: Crew (Players) and Fight/Flight Point Two: Difficulty of Denial of Exfiltration TLDR I don't see any need to go after this 'issue' OOCly. This comes down to player behavior ICly and the mindset of evacuation plans that many have. You want to fight? Fight. You want to run? Run. No matter what we change, people will still do whatever they want. If they run now to the outposts, they'll run in the future. If they hold on facility, they'll hold on facility. If they fight, they'll fight. If antags WANT to deny evacuation, well, they better have a plan and a good one at that. And then be able to react to circumstances. WARNING: Personal Bias Ahead (and some coarse language) Edit was under personal bias. Stuff about evacuations.

Reporting Personnel: Milo Hachert Rank of Reporting Personnel: Head of Security Personnel Involved: Zubari Akenzua, Investigator ; Lauren Blade, Maintenance Technician Time of Incident: ~13:15 Location of Incident: N.S.S. Aurora, Maintenance Tunnels near Engineering Department Nature of Incident: []Workplace Hazard []Accident/Injury []Destruction of Property [X]Neglect of Duty []Harassment []Assault []Misconduct []Other _____ Overview of the Incident: Investigator Akenzua intervened in security's detainment of Lauren Blade for a violation of i107: Misuse of Public Radio Channels. His sidearm was discharged during the altercation with Blade. Attached below are transcripts of the interviews with Akenzua and the immediate action taken by myself in regards to the matter before it could be properly forwarded. First Interview Action Taken Did you report it to a Head of Staff or IAA? If so, who?: Yes. Elena Raschnikova, Captain Additional notes: Investigator Akenzua complied totally with my investigation. It is my professional recommendation that Akenzua be issued an injunction regarding the carrying and use of firearms during standard operation.

Milo gazed down at the form atop the table before him. "This isn't gonna change nothin'. . . but, screw it. . ." he said with a sigh. He plucked up a pen and committed his signature to the form.

[*]Security lobby/holding cell blast doors have no control point. No way to drop them. [*]Front Lobby desk in security does not have blast doors covering windows looking out into main hallway. [*]Prison wing has no blast doors. Personal Note:

Security-moblies. Hoth trooper-security. Take. My. Money.

Loading documents. . . . . . . . . loaded Injunction - T. Davis Injunction - W. Carton SitRep 001 Loading attached letter. . . . . . loading failed. ((I'll get to this tomorrow. . . just wanted to get the documents up.))