Skull132

It hasn't been like that all the time, though. At around spring, early summer I underwent a relatively hard crash, and felt a disconnect between myself and the community (also made the decision to abandon my 3 year commitment to an, arguably, tighter knit group on ArmA for this around that time). I could not figure out the people we had onboard anymore, despite some of them having been there from the start. It was unpleasant, and demoralizing to a degree. And to add, I had run out of things to do IC, so I stopped playing, basically. But I managed to adjust myself; from what I remember, I started playing Talon in engineering, from where evolved a nice, small story thread, and things moved on from there. The unfortunate fact is that everyone is an individual, and thus the means on fixing things like this are tailored individually (what worked for me might not work for you, what didn't work for me might work for you -- that kinda thing). As odd as it seems, making friends from within the community as a member of staff can be intimidating (or at least is, for me). On a personal note, I was lucky, and had a small group I became a part of during my days on Apollo. And they migrated over to Aurora, and are now mostly active on TS. Speaking of, as much as you may dislike the idea of using TS, it is a good way to just talk with people (as much as OOC serves for communication, I find that the amount of noise present there is not conducive to actual, meaningful communication). Despite the occasional sinning that takes place there. Ultimately, it is impossible to be familiar or even connected with the entire community, beyond the simple premise of, "We all play this game, on this one server." In my mind. Perhaps I'm wrong, dunno.

My views: Okay, fine, the review process failed and you got in as someone you really shouldn't be in as (no, someone like that, in my opinion, should never service a command position, both ICly and OOCly). But once things start piling up, reviews like this, NT would take action. Now, they wouldn't exactly, perhaps, care about the nature of the charge, but they would care about maintaining an effective command staff. This means, one that doesn't need to constantly keep unfucking or firing one of its members. And speaking OOCly, dealing with this can be annoying. It can be hell-a annoying when you sign up as a member of command staff, see the name on the manifest, and just go, "Right... Him again." It's a situation you would want to avoid, or at least have some avenue of action against (we are SUPPOSE to have IC complaint boards, but the dudes in charge of that have yet to produce results, so fine).

Internals: -i5-3570 CPU 4 cores 3.40 to 3.80GHz -GeForce GTX 770 -8GB of RAM -120GB SSD -1TB HDD -Assorted cooling fans and mobo Externals: -Logitech MX580 mouse (amazing) -Some random Logitech keyboard that's 6-8 years old (I don't ever want to swap: simple, effective, typed-in, and just works) -Corsair Vengeance 2100 headset (wireless) -2x LG 22EN43 (22'', full-HD) Only games I really play: -SS13 -EVE Conclusion: Skull has an overpowered computer for running a BYOND game.

Eh, my perspective on playing the game has certainly changed, but I do enjoy it still. But all of this gets tiring. I no longer partake in events, nuke rounds, heist rounds -- basically any round with a higher stress factor. I actually, actively look for ways to avoid conflict, something that is counted as a requirement for storytelling to exist. And should I end up in a high stress situation, I havr a habit of using knowledge to gain myself a comfortable position, if not an advantage in a situation. Is this against the rules? Not exactly. Is this a display of horrid form? Yes, definitely yes. Another oddity can be described with the phrase of, "Embrace the suck." It gets morphed into a pseudo-metagame for me, one with no victory condition. It's kind of fun to be presented with a conflict I know I'm going to have to solve, a verbal engagement I know I'm going to have to conduct, and trying to figure out how it'll go. It's tiring, but, I don't mind. I knew this would happen, and I have reasons to continue. I just hope that people like Rusty, JD, Nursie and whoever else don't mind. Also, a random bit of advice, if it proves necessary. I never found myself having success with characters that had predefined ideas behind them. Just throwing a name attached to a job, title and a few mannerisms into the chaos of the station has been a relatively good way for me to get reengaged. The character develops on their own, on-station.

As much as I enjoy jokes, please not here. So, TO OFF-TOPIC WE GO!

In ye olden forums, Far Cry started a thread that operated on the following premise: You would write a story with your character(s), but place them into an alternate universe or dimension. Regardless of what universe or setting you choose, the stories would be written as if the character had lived in that setting for their entire life. It's an interesting premise, and was executed rather well on the old boards. Let's see if anything interesting pops up here.

The man spoke words that ring close to my heart and mind. Changing my "maybe" to a +1. Still not sure about Tina as a character, but have confidence in the player.

Another note about subordinates is that you should be invested in their development. Taking the time and effort to teach new staff will give you a core group that is loyal, works as a team and has similar MO. This is preferable to looking at every new face as an incompetent baby who needs a bottle held up. Yes, you will have those too, but this should never be the start-state.

As far as introductions go, I'm shit at them. At least, without insulting people. So, let's just get this show on the road. The following are tips based on observation and my general knowledge of leadership. They are in no way priority order -- all of them should be given equal consideration. Hopefully this will help. Preface: In accordance with the Standard Operating Procedure, both old and new, all Heads of Staff are equal, regardless of whether or not a Captain is present. Standard operation does not warrant the promotion of an Acting Captain, as such, all Heads of Staff are equal and stay in their lane as needed. These are my personal views, opinions and experiences. Take them as you will. 0. Everyone is Human. Mistakes will happen. Solve them together and move out, together. Do unto others as you would have them do unto you. 1. You Live by Communicating Very simple, communicate. With your department, with your fellow commanders, with troublemakers. Communication is a basis for leadership, it enables you to command, to review, to assess, etcetera. Communication is a two way process. Listen, and be heard. Don't just do one without the other. Teach your subordinates to do the same. Even if someone fucks up, at the very least listen to the why, so you may curb behaviour and ensure that the fuck-up isn't repeated. Keep the comms clear. Any active head has a minimum of 3 radio channels to monitor: command net, department net, public net. Add to this local comms (verbal) and secondary channels (for HoP, Captain). This is a lot of comms traffic. Don't make the lives of other heads harder by picking up and carrying out verbal gunfights over the channels in question, it just serves to piss them off. Breed an environment of internal communication within your department: ask for situation reports, make sure major actions are communicated, make sure that communication is rewarded, discourage (and solve) verbal gunfights over net/within the department. You want to minimize miss-communication as much as possible. 2. Know Your Lane, Stick to It For a Head of Staff, their lane is defined as their department, the personnel involved, and actions concerning. As a Head of Staff, you should be primarily focused on your lane and its problems. Don't hop lanes (unnecessarily). If the situation is not critical, try not to provide even the tiniest comment regarding conduct, procedure, duties, etcetera to the personnel under the command of another Head of Staff. Doing so will serve to confuse personnel, undermine the leadership of the Head of Staff that is suppose to be responsible for them, and make him look impotent. Instead, contact the other Head of Staff, politely inform him of the issue, and let him sort it out. The latter note includes the tiniest of things, truly. Police your staff, and let others police theirs. If you need to stick your nose into someone else's business, make sure it's unavoidable, and you have damn solid ground to stand on. Otherwise the other Heads of Staff reserve the full right to have your arse (in my book). No, the HoP does not have the liberty to take Acting Captain as they please. No, the HoP should not stick around in security unless it's a matter of paperwork or an emergency. No, the HoP is not a replacement HoS; the Internal Security department can manage itself, stay the hell out of it! 3. Solve Problems, Enable Your main tool for solving problems: communication. Your main responsibility in-front of your personnel should be to enable them to work. RnD needs resources? Sort it out with the HoP and QM. Surgeon needs new tools? Talk to Cargo or RnD! See solutions, and not just problems to side-line. You are their extension and access card, help them. And they'll help you. Identify issues. Learn from previous mistakes and issues, and use the knowledge gained to identify issues before they repeat themselves. If the issue is not in your lane, or goes beyond it, contact the proper authorities with your concerns. They should listen to you, at the very least, as an equal. Be constructive. Once an issue has been identified, and you are in a position to help, do so. Pointing out and yelling is one thing. Going beyond that, assisting and being constructive about the matter is another. Know how to do identify, and more importantly, how to solve an issue. Even if it's a new issue, try. 4. Punish, Private; Praise, Public A very simple rule to live and operate by. If a member of your department needs to be punished, do it between closed doors and be constructive about it: give them a chance to fix themselves, and give them solutions to the problems that caused the breach in acceptable behaviour. If someone does something commendable, or even just maintains commendable behaviour, make others aware of it (a pat on the back is fine, be careful with raising someone onto a pedestal, though). Only, only, only punish and praise your own staff. Do not touch the staff of other Head of Staff. Refer to point 2. 5. My Character is n-phobic No, he's not. Get out. Whether bigotry, xenophobia, arachnophobia, or whatever, it cannot and should not lead to irrational or incompetent decisions. Basically: if it forces your character to commit an action that fucks the status quo in the ass so hard that it's unable to stand up afterwards, then that character should probably not be in a commanding position. And ICly speaking, issues like that come out. And even if they were able to keep it under wraps during evaluation, or somehow skimped out on a few parts of the evaluation process, erronious decisions made as a result of the aforementioned factors will build bulk, and eventually, CCIA will deal with him as they see fit. 6. Regarding Respect Most importantly of all, note this: respect is a two way street. You cannot demand nor expect respect outright. In no way, shape or form is this wise, or recommended. Respect is earned. Earned through actions, conduct, and a myriad of other factors. It will take time, it can be a difficult task, but it will pay dividends if accomplished properly. Assuming you are respected, and attempting to command respect will backfire terribly, always. I cannot stress this point enough. Yes, you've earned your whitelist. Yes, you can now play a role that is limited. However, you have yet to earn your position, in the eyes of your subordinates, as a leader. Be humble, have humility, and work with your subordinates and peers. Then, among other things, they will start to respect you.

You're missing a word here. The word "Officer" on its own does not imply much, and it usually needs to be attached to another word in order to describe what officer you are dealing with. In this case, we are very specifically dealing with [Private] Security Officers, or Officers, as members of a private security force. (Case and point: the US Navy has 4 types of "officers": Petty Officers, Chief Petty Officers, Warrant Officers and commissioned officers. To say, "Officer," would be to refer to the latter most, usually.) And I don't think a name can enforce a mentality like this. Adding the alternate title is fine, ish (minus an issue with standardization, that I need to ponder on when it's not 0255hrs local). But the reason presented for it feels a bit lackluster.

Jobban applied. NitrosKiller is free to appeal this at the appropriate subforums.

I'm in favour of a security job ban. Fully in favour.

The same exact thing is true for magazine fed weaponry. A reload that is unplanned will screw you just as well. The nuances are different, the point is the same.

Okay, been throwing this ball of yarn around, may have an idea. So, the key about weapon systems is that they need to, and are often made to, fit purpose. On station, that purpose realistically isn't expected to exceed to dispatching of carp, large crowds that gather, and the occasional lusty xenomorph maid. For this purpose, a weapon with a restriction on useage as heavy as a requirement to remain anchored to a singular recharge point seems fine. And let's be honest, systems like that would probably be cheaper. But for an actual combat force, such as ERT, such as the syndicate, a singular operator needs to be self-sustaining to the point where they can extract themselves from just about any situation. Obviously a weapon that requires a recharge there is not fitting for purpose. So, here goes my idea: weapons for ERT, syndicate and a certain crate from cargo are capable of accepting interchangeable energy-cells. Weapons for security start out as the current standard, but we add the ability for RnD to tinker with them, and make them accept a mobile cell-swap.

While I don't see any harm in unbanning all three, a part of me would like all of them to at least acknowledge that what they did was against our MO, instead of just getting a free pass on the count of their buddy.

Eh, as far as I'm concerned I'm good with another chance. Need to let the Head Admin get around to checking this, and make the final call.

Can we not clutter with WIP posts? They stack and stack and are ultimately useless. Use the "Save Draft" feature for it, if you need to.

Oh! I remember this one. And the ban is applied to your account specifically, so this isn't a mistake. Okay, so, the situation myself and TishinaStalker were presented with: Three assistants in an emergency storage closet. They start attacking eachother. We wind all three, and all three log right after this. You were one of them. Since we had other issues to tend to at the moment, we banned you all three permanently to sort the situation out later, in the appeals, here. So, if you could please describe why the situation above took place?

Two very simple actions: curb them, report them, done. Idiotic IAAs can be very easily dealt with in a running fashion, meaning you ahelp their conduct, it'll be reviewed, and dealt with usually on the spot.

Doing so would not only remove an element used for balance, but would also be very difficult, requiring a creation of a new entity on the whitelist. So, unfortunately, this is not something I would do.

I looked at them there logs. A few things I'd like to point out: At no point prior to arrest was the botanist, the detainee, informed of his charges The member of security who conducted the arrest did not run it through the proper channels The member of security who conducted the arrest made no effort to resolve the matter peacefully, or even give the detainee a chance to surrender of their own accord The lethal firearm was discharged due to a struggle between Nitroskiller and the roboticist (Valkrea), however, as the one lethally armed and as the individual who has control over the situation, the security officer should have handled his lethal firearm in a manner which would have made an accidental discharge like this impossible (read as: the weapon should not have been drawn, it should have remained stowed) The actions I am able to observe from the logs, in my opinion, confirm the points raised by the submitter of the complaint.

I'll fetch the logs for this when I get a chance, and see if they confirm your story. I'd also like to see if Nitros has anything to say about this situation. EDIT: a few questions for both parties to answer: Were the nuke ops quelled, and was there any active threat to the station still present? Was there a HoS? Who?

A check of the forum moderation logs shows that no actions were taken by any forum staff with regards to your topic. Something that may have happened is that you may have had a session timeout and it would have forced you to login alongside that. That would have lost you your post. Unless you actually saw the thread here, in these subforums and everything. At which point, I am slightly puzzled.

Okay, their relationship to CentralCommand does not, in my eyes, put them in a more favoured position to take command. However, it does enable them to ask for instruction, guidance and directive on a matter. Does this give them the authority to conduct the execution of the orders required? No. Does it give them the authority to say, "These are orders from Central Command regarding this situation, here is the stamped fax that describes them, you are to carry these out to the letter," and then watch? Yes. Also, as FFrances already pointed out, whitelisting IAA will only make it less played than it already is. They already have this function, kinda. This move requires no step other than actually talking to people without taking charge of a situation. Is some random department bickering amongst themselves while no head is present? Okay, go and resolve it -- do your job. Talk with people, interview people, resolve the matter and restore a state of functionality. But do not interrupt their work. If the work they are doing is in charge of Corporate Regs, then request to elevate the issue for Internal Security investigation and intervention. I'm going to have to disagree on this one. Leadership mentality should not be expected from an IAA. If a department needs a leader, then under perhaps the guidance and advisement of the IAA, they can have someone take initiative, or work together. However, to directly appoint someone without any leadership expectation in a command position like that is utterly foolish, to me. I tried answering these points in a manner where I'd bring out alternatives that are already feasible, as opposed to just flat out saying that they should not be done. The thing is, an IAA already fields enough say to resolve just about every conflict that I have seen brought up in this thread, if they communicate with the right people and speak the right words.

A message pops up, attached to it is a blue medical symbol as an avatar, covering for the lack of a webcam. The username is written as MDSunnyHill. "Mr. DeWitt, for one reason or another, I have always wondered about your attire and appearance. Most noteably, the tunic and disheevled hairstyle, and the lack of a professional appearance."