-
Posts
1,505 -
Joined
Content Type
Profiles
Forums
Events
Gallery
Everything posted by SierraKomodo
-
I have been successfully annoyed by flashing red text, Delta. Thread locked and archived by the OP's request.
-
Honestly, it should be relatively simple to define a specific item size between the nuke disc and research discs, assuming it's a simple variable definition like other things.
-
I do like the idea of miasma. However, I'm not too keen on it being a thing that sets in quickly or has too severe of an effect; You have to remind that if the station gets into a code red/lots of death situation, aint nobody going to have time to deal with corpses and blood, and making those corpses and blood start killing people within 10 minutes is just crippling the station even more in a situation where the station may already be, for lack of abetter term, utterly fucked. I'd recommend making it more along the lines of 30 minutes, and make the effects a little less severe. Instead of giving a random virus or something that could potentially become a fatal bio-bomb, start it off as a putrid odor. 10-15 minutes later, if you're within it long enough, you can get minor lung and/or eye infections. It'll have a clearly noticeable effect, but this leaves the results more open to a heavy-RP environment, and less arbitrarily-ganky of a mechanic when things start going south.
-
Hm, here's a thought. Have the fire alarms flash between 'white' and a color denoting which department the alert cover: Engineering: Orange Security: Blue Medbay: Green Research: Purple If it's a global blue alert, then it just flashes white. EDIT: We could also make it a 'Yellow Alert' instead of 'Blue', and use yellow instead of white as the flashing color.
-
A wheelchair's probably a better idea
-
http://aurorastation.org/forums/viewtopic.php?f=64&t=20 Thread cleaned up at the request of an admin, so let's keep things on topic shall we?
-
One major problem I can see with this is with how cargo tugs currently work, you'll essentially be immune to every form on non-lethal takedown method security has available. You'll be immune to tasers, stunbatons, and flashes while on it.
-
(Not Really A) Staff Complaint: Garnascus
SierraKomodo replied to LordRaven001's topic in Staff Complaints Archive
As the AI that actually sent security after Alberyk's character in this round, on hindsight I should have double checked and been sure of the situation first but I was handling about 20 other things at once.. Basically the interim CMO reported Alberyk had a gun and was firing on him. I glanced over, Alberyk's character had a laser rifle on his back and the CMO was running away. Called in security, gave them a location, opened doors, all this while Alberyk's character ran and hid in a closet that doesn't have a camera, then I went back to making sure the other issues were being handled. Hopefully that gives some better idea of what happened. -
Moved to the proper subforum.
-
LordQuailius's Tajara Application
SierraKomodo replied to LordQuailius's topic in Whitelist Applications Archives
Although I haven't had much interaction with your characters, I do like the backstory you've put in and think you have a good grasp of the species. It definitely sounds like you don't plan on making an angercat or what has recently become the stereotypical Tajara, so I like this. +1. -
Coolbc2000's THIRD app
SierraKomodo replied to coolbc2000's topic in Whitelist Applications Archives
This thread is degrading into useless banter, and I don't see anything else being posted here that hasn't already been said in nicer words. Locked until the head of staff managing admins can give a final say. -
Coolbc2000's THIRD app
SierraKomodo replied to coolbc2000's topic in Whitelist Applications Archives
As a note, you keep making a point that Mark is not the only character you play. The reason we're focusing on Mark is because it's that character you put in your application that's going to become a head of staff. Also, the DO's haven't done anything because: A: Half of what you do, like what I posted about, involved antags so we can't touch it B: Nobody reports anything in an IC manner so DO's can't do anything -
Coolbc2000's THIRD app
SierraKomodo replied to coolbc2000's topic in Whitelist Applications Archives
Right so having witnessed an earlier round with Mark Syion as an interim Head of Security? I'm saying no. Why? Syion, a cadet, and a prisoner are sitting in the communal brig. The cadet suddenly starts beating the prisoner after they argue for a bit, Syion sits there and watch. The prisoner retaliates, knocks over the cadet after being beaten several times.. And Syion stuns and cuffs the prisoner. Cadet gets off scotch free. I ahelped this issue, and I was informed that you were spoken to about this. But what's to say this won't happen again? I'm certainly not going to trust you with a head of staff whitelist if you can't even handle an interim head of staff position properly. -1 -
The ability to empty any liquid container (Beaker, bottles, syringes, cups, etc) by clicking on a sink with the container in your active hand would be useful. It's a bit annoying to have to dump something on the floor to empty it, and definitely doesn't fit in with a roleplay environment where something like that would probably get you fined or worse depending on the context.
-
What it says on the tin. There's been many times where it'd be useful for the AI to be able to set alert levels through the communications console (Code green and blue), and there have been heads of staff that thought an AI could do this. Naturally an AI can't call code red since that requires two heads of staff to swipe; Only what the communications console would normally allow.
-
How about instead of new alert levels, we keep the current green/blue/red, and there's an additional prompt that lets you select what type of alert/department it pertains to which defines the message it displays. I.e., you go to the console, set blue alert, and then select 'Engineering' as the department. Instead of the security related message, you get this: Blue Alert - Engineering! There is a possible or confirmed issue with the station. All crew are to obey directions given by engineering staff, and avoid any areas reported as breached or otherwise dangerous. Engineering staff are now exempt from trespassing regulations, and the Chief Engineer has command priority.
-
So one issue some people have with internal affairs is the lack of respect and attention they're given by the crew, which is a result of how many IA agents that come on board are players who are new to the game, new to our server, new to an HRP environment, or otherwise just don't give a good impression of the agents in general. As IAAs are supposed to have a very important role ICly, in regards to ensuring a station is running to regulation and essentially serving as Central Command's eyes and ears aboard the station (And with the duty officer's recent endeavors to involves internal affairs by having them perform mandated inspections/reviews), I think it might be a good idea to put IA under the head of staff whitelist. This would give players some OOC assurance that anyone playing IAA isn't going to be a newbie or someone that took the slot to mess around, and would in turn ensure that any IAs on station are players that can be trusted with the role by command staff and the duty officers.
-
The assistant's salary is pulled from the US military paygrade scales for E-1, albeit from the '10 years of enlistment' row, as the higher ranks do not have salaries listed for below 10 years. This is supposed to be a more generalized/average salary list; I can go back over it at some point and refine the numbers to better fit a 17 year old newly hired assistant vs a tier 3 employee. Also, as someone who currently lives on a $1,500/mo salary, after taxxes rent and bills it's really NOT that much money to have, just enough for a living and to have some left over.
-
MagnificentMelkior's Head application
SierraKomodo replied to MagnificentMelkior's topic in Whitelist Applications Archives
I distinctly recall an incident a couple weeks ago with Richter as a hulked out fully gene modded geneticist in a nuke op round. Nuke ops had subverted the AI, the AI refused to state the law or open a door or something. A few minutes later, Richter was outside the AI core using TK and xray vision to kill the AI with a light bulb. Not a word or anything from him, he'd just walked up to the maintenance tunnel wall and killed the AI solely because he thought it was subverted. I'm not sure the AI had even actually /done/ anything up to that point, and surely NT wouldn't appreciate you destroying an expensive piece of equipment instead of resetting its laws. There's also the countless number of times i've witnessed Security having to put you down as a hulk with lasers because you just wouldn't cooperate and were smashing things apart, albeit the last time I saw this was a couple months ago. I'm quite honestly amazed you aren't job-banned from genetics yet. -1. -
Now, about that. I have been a changeling at random as a Captain. Skull was on the server so I asked him if it was something that was supposed to happen. He said no and I agreed to be deantagged. I mean, it makes sense that a Captain or whatever could be a changeling as it isn't even them anymore but, I don't believe LI people are wanted to be Changelings. Well the staff that was online at the time this round happened (I forgot who it was) decided that it's fine for LI'd heads of staff to be antags.
-
I'd like to mention that, as it turns out, loyalty implanted persons are /not/ immune to being antags. I had a round the other day where both the captain and HOS spawned as changelings so.. That's not a thing that can considered with LIs anymore.
-
That's the thing. Nothing's really set in stone. It's all about how the implanted player interprets it, and what the currently active modmins decide is bad for an aimplanted person to do.
-
I honestly can't vote on this because, currently, staff have yet to come to a consistant consensus on what exactly a loyalty implant does ICly and OOCly
-
Staff Complaint: SierraKomodo, AimlessAnalyst, DO Corps
SierraKomodo replied to Ove's topic in Staff Complaints Archive
That was mostly a communication error on my part; I'd thought that fax had made it clear enough what the issue was when I sent it.