Jump to content

K0NFL1QT

Members
  • Posts

    474
  • Joined

  • Last visited

Everything posted by K0NFL1QT

  1. I was thinking about ion bullets for the .45 earlier. They'd do little to none direct damage, but disperse a strong EMP into the recieving body.
  2. So is hypnosis.
  3. I can get behind the idea of making brain injuries more fleshed out than mere numerical damage, but the fact is that in implementation brain traumas have been shoehorned into suddenly being such a huge and important part of almost every medical treatment, and there's rarely anyone who can do anything about it. The brain trauma 'update' is so far reaching that it's had to change doctors approach to injured people, changed chemistry, changed surgery, added anywhere from minutes to an hour of cloning aftercare for every clone, and on top of that this is all handled by a one-per shift role that is rarely occupied despite forcing an entire psych overhaul to deal with this. Run too much? You get a brain trauma. Loose air for a while? Brain trauma. Loose blood? Brain trauma. Cloned? Several brain traumas. While some of the above may actually be realistic, I would suggest toning down the ease of which characters can currently get these impactful conditions, and making them easier to deal with.
  4. I definately did not come here after PM harassment. I am conflicted about this application. I would +1 the player, but -1 the character. Suvek is a good officer, and you rightfully assess that he has a good grasp of regulations, but as Warden he too often goes to personally respond to combat situations or carp hunt. Learning to have access, authority and opportunity, yet still stay hands off whenever possible is a tricky thing for HoS players to come to terms with, myself included; the expected mentality needs to manifest in the character as part of their development before they would pass consideration, if they're working up the ranks. Also, Suvek suffers from the Unathi trait of being overly aggressive at times, he still holds onto his traditional prejudices, and will ignore better tactical options to use a traditional Unathi spear whenever possible despite that being needlessly risky. I am aware that a lot of this feedback can be construed as 'shave off all the unique Unathi traits', but I genuinely think NT would very carefully assess the temperment and composure of prospective Unathi Commanders. I know Suvek is 'old enough' to be promoted, but there are more qualifications than age when considering Command aptitude. Suvek is a driven character, so his reaching for promotion is understandable, but I just don't think he's ready. Suvek is one of my favorite, and I think best, examples of a well done Unathi on station; but the traits he emphasises don't, in my mind, predict a HoS that can be a calm, fair and unbiased, tactically adaptive co-ordinator.
  5. I had an IC conversation with a CCIA agent a few days ago, regarding Fraud and when it could be applied. We came to the conclusion that in the case of a roboticist selling prosthetics for personal profit, when they're using NT owned materials and machines, the character would be commiting fraud. Ergo, selling anything on the station for personal profit is likely chargable as fraud. Not that this doesn't exclude selling items for the profit of station department accounts, only for sales of NT owned property with the credits going to your personal account; the deception implicit to qualify this as fraud is that you claim to have the right to sell corporate property that in fact does not belong to you, thus you have no right to sell it or to claim the profit from that sale.
  6. I just have 'Lt. Columbo, follow me.' copied for any HoS round. Easy to modify for stay and attack, altough attack is far more cumbersome because you need to type the targets full name, and correctly.
  7. Give the Merc and Heister shuttle actual engines that run on a supply of phoron sheets, and can be damaged/destroyed, with each jump consuming from its internal store. A large jump, as in from the base to the asteroid and back, should consume maybe half of its total supply while shorter jumps consume much less. This prevents shuttle based antags from both 'leaving whenever they want', because they will either have to buy/steal some phoron to go home, and reduce the exceptionally annoying 'bounce around the asteroid' hunt that these rounds often become by making the antags plan out their jumps a little more.
  8. Absolutely. I always take on constructive feedback, and communication issues especially as HoS is something that has been raised against me before. I just haven't played much HoS lately, until the past few days, so I'm getting back into the swing of things. I'm trying to again find a good balance between being the department co-ordinater and actually doing something more exciting than sit in the office all round, but sometimes it feels like the only things people ever want a HoS to do is write warrants, swipe for red and open the armory, and never anything more involved.
  9. +1 dismissal. It's not griefing and Crossfire already requires 25 players.
  10. I know multitools have this stigma of being related to easily hacking doors, but you only need a multitool to get through bolted doors. Multitools don't reduce the risk of accidentally activating the shock wire; only insulated gloves protect. Any non-bolted door can be far more easily gotten through with only wirecutters and cutting the ID wire.
  11. This is both awesome and terrible. Awesome, because you're fleshing out IPC mechanics. Terrible, because you're moving IPCs closer to being just another human reskin, like every other race but Diona, by giving them blood and a heart.
  12. You seemed to do better that round, for sure. I was zipping around between security, and they seemed pretty well organized. And seeing as the whitelist team were summoned by one of the admins handling this complaint, I'd like to counter-submit the above game ID (bTK-cTV6) as positive evidence of my capacity to communicate and control a department. Again, granted, communications were down a lot, and the antags were peace wizards and a ninja that died early so things were less hectic and far less high stakes, but I hope it at least serves as a more positive example. [mention]ShameOnTurtles[/mention], [mention]sebkiller[/mention], [mention]Alberyk[/mention], [mention]Coalf[/mention], [mention]Datamatt[/mention],
  13. @[mention]tbear13[/mention] You were just ghosting over a round with me as Zane again. Granted there were power issues and telecom outages, but how do you feel about my performance for that round? Game ID: bTK-cTV6, Visitors, IPC Wizards and a dead ninja.
  14. I've proposed this before and been told that it is simply impossible to implement, or that it would take too much work. If you really want to have a stab at it, I salute the attempt. Regarding how to do it; vary the approach. For example, if you're trying to do surgery, you should check the characters surgery skill. If it's untrained, it should take much longer and you should have almost 100% chance to fail and make things worse. An Amateur, maybe 50/50 chance. Trained should be, maybe, 95% success, with professional being 100% success and possibly completing the task faster. Likewise, you can scale characters shooting accuracy in a similar way, from heavy penalties for the untrained up to basically how guns work, with minimal extra penalties, now for professionals. For chemistry, you can add in chances for the wrong chemical to be added to the beaker, with untrained perhaps dropping in a little water potassium for that catastrophic failure effect. In essence, a 'professional' character will be able to perform their actions near perfectly, and quickly, a trained character can do them with basically the same success rate as everyone currently has, and anything less than that incures heavy penalties. This rewards heavy investment and punishes 'dipping' into other fields. You want your surgeons to have focused deeply on surgery, not dabbled in it while learning karate, gun-fu and electrical repairs. Any investment put into skills your character isn't expected to use for the job they are paid to do, will probably end up being a detriment compared to specialising.
  15. It was in character for me to not inherantly trust the abilities of the officers in this situation, partly because the character is new to the station and is unfamiliar with the crew and their capabilities, and because taking down phazing mech is absolutely not something most officers are probably trained for. I did inform Security, as soon as I realised the Phazon was stolen and on the loose. I still hadn't decided how best to deal with it at that point, but I absolutely did inform the department that the mech was missing. I called for the engineers on the common channel. You should have seen it, but may have missed it and that's fine. But if you say I did not request engineering, I have to correct you. I did. But I was waiting for them to actually arrive before I started vocally planning and ordering a breach through the back path. It's not 'trust issues', it's 'newly transferred to the station and wtf these guys are not trained for this'. The first time we saw it in Robotics, people were trying to talk to Maline to persuade her into getting out of the mech and handing it over. I was more than happy to let that occur, and did not want to just 'no rp rush' them with ions because that is exceptionally shitty. I always sandbag for antags and give them every opportunity to stop, surrender and turn themselves in; sometimes that just gives them chance to kill me, and that's fine. I can take that. But I always make the effort. I was still roleplaying through the situation despite how frustrating a phazing mech, and wanted to talk to the antag. Weird I know, right? As for informing about its weapons, I can;t remember at exactly what point I was able to see it's weapons, but I'm fairly sure it had... the laser cannon, ion cannon, incindiary rifle and something else. If I can examine the mech, you can too. Except from my perspective, I protected my department by not ordering them to try and stop a heavily armed, high mobility killing machine, when there was one weapon that could threaten the mech and I happened to have it. That would be like ordering cadets to bumrush mercenaries, armed with only foam swords, and I wasn't going to order them to their deaths. Could I have handled the situation better? Yes and no. Yes, I could have spent more energy on giving the department some orders, that I will concede, and yes I could have gone to cargo to order more ions. I will try to keep that in mind for the future. That option aside, there wasn't really much more I could do, because the nature of the 'event' was initially 'there is something in the Vault that you are absolutely not to look at, investigate or touch at all, in any way, shape or form', and in general everyone was pretty much on the same level regarding information. Once the mech was loose, I had as much information as the officers did, and I passed it on. I did not know more than the rest of Security. Maybe I didn't take a minute to stop, pause, and make sure everyone was on the same page, but you were told about the mech before your first physical encounter at the Captains office. This is evidenced here, in your own words. You admit I informed you about the mech. You admit I authorised the Warden to hand out weapons. I didn't tell you where to go, because I did not know.
  16. If you don't know what I mean, maybe you shouldn't bring it up. I was sent a PDA message long before that, indicting the Warden of something. Ordinarily that would have been very important to shut down, investigate and parse out, but there was a phasing mech we had to deal with first. When exactly that was, it was either before I first went into the Vault or sometime around the time of the fight at the Captains office, either way before the fight at the RDs. And, to reiterate, when the gunfight at the RDs was occuring, I was locked in ahelps and not really able to manage the department or do anything about it myself. Ordinarily true, but these were extraordinary circumstances. Not only is 'stopping a rogue mech' not exactly standard in a days work for an officer, but you're overlooking the fact that the Captain themself put this directly on me when they asked me to move the mech that turned up stolen. And then Central Command announced that they knew it was stolen and we had to recover it, intact. That was an order from Central Command to get it done, and done right. There's 'assume basic competancy', which anyone who plays Head of Staff can tell you is simply not true, and then there's 'do you trust any of these officers to get this done', to which the answer was no. Because the character is new to the station and doesn't know these people yet. I wasn't going to order any officer I couldn't trust with a task of that magnitude, so yes I resolved to handle the mission myself. I got the same call to robotics that you all did. The HoS can't order officers to engage a suspect if he doesn't know where they are. The officers suggestion to surround them was a good idea; I like when officers do competant things. An officer may have also asked for engineers, but I know I also did too. And, yes, you recieved the same information from Central as I did. The only time I had more information than anyone else, was at the start of the situation when I accidentally spotted the mech in the Vault, but at that point we were on orders not to go anywhere near it. I'll concede that the stations ion rifle isn't, in theory, the only actual weapon the station can get to when you take cargo into account. Next time we need to catch a phazon, I'll try and order ion rifles for everybody. See above, and read back previous posts regarding why I had the rifle, I've answered most of these already. The only new point you've raised here is that I didn't rush cargo to order ions for everyone, which hey, you know, good idea.
  17. My memory regarding this round is a little less clear, given it was longer ago than the others, but I'll do my best to explain. It was extremely 'stealth and do nothing' malf. I can't remember exactly when I joined this round, but I do remember idly coming across the camera feed of a borg that was building defenses in the AI core for seemingly no reason. That was suspicious, but I definately didn't jump on the 'borgs are rogue' angle then. I just kept a close eye on that particular borg, checking their cameras every now and then. I was talking to the AI about this in the Command channel so all Command staff could hear, but I don't remember what I did or did not tell Security given that I wasn't trying to push a validhunt. I think I talked about it to one or two of them off comms, but didn't institute any orders regarding it. Sooner or later, we see this. Yes, that is the AI calling out that they are immediately about to lockdown and vent Security, which is the precise reason I ran out of my office, straight into the Armory to grab the ion rifle and run into maintenance, because the AI told us it was going to lock us in and kill us. There was a few minutes of unease and confusion as we debated in OOC whether we needed to void that, while IC we all had to hide from a radioactive storm. Eventually I think it was Nursie admin ruled that we should ignore it. We all had to wait around and it was kinda wierd for us, because the malf blew their intent to straight up murder security and we had to try and act like we hadn't seen it, essentially being forced to forget it and wait for the AI to kill us. I can't exactly remember what I did here. I think I wandered around a bit, tried to get into literally anything that could palette cleanse my mind of the fact that the AI was planning to gank me. Then the AI makes a report about intruders on tcoms, so I go to my camera console to look around to try and confirm the report, because I was trying to play along with the gimmick, only to realise that the camera consoles cannot see onto the telecom satellite at all. However, while I was checking for that camera, I see as the engineering borg goes onto the Bridge and dismantles the robotics control console. I ended up calling that one out over an intercom, I can't remember which channel to, because the AI shut down telecoms. As far as I could tell, the AIs claims of intruders were unverified, because literally nobody else had seen them and nobody was reporting the atmos alarms that you'd expect from a breach. Comms came back on and I was discussing the borg console problem with Command, when the AI claimed that 'no console had been deconstructed' despite me watching that it had been done. I still haven't jumped to 'borgs/AI are rogue' mode, but this is all getting too suspicious to ignore, so I went to the Bridge to check it out. I step into the Bridge and see the console I saw taken apart actually is deconstructed, so the AI is clearly lying to me to cover for the borg. As I'm on my way out of the Bridge the secborg from down the hall just opens up at me with its laser cannon. I get shot twice in supise before I can get cover, but I managed to call out that I was under fire on comms before they were disabled. I was also trying to call out my location and the situation to Security, while actively dodging laser fire, but comms were off. I had the ion rifle with me, so it wasn't really a fair fight for the borgs once they'd blown their suprise attack. I ioned and battoned them until they were offline, but the pain from the laser shots had rendered me unable to move anymore. I had my suit sensors maxed so people knew where I was, and came to get me. I get to taken to medical for treatment and the AI starts finally, openly taunting us over comms. The shuttle is called, and then Code Delta is called, so I announce to the whole crew that we're going to force launch and get off station as soon as possible. We go to the shuttle, I wait a minute, then force launch because the self destruct is active and I had no idea how long was left on the timer. That was all about that.
  18. Don't worry, I'm not offended or angry about constructive feedback. With your case, the warning was retracted because I realised I was being manipulated by a character with a grudge against yours. Beyond that, I feel like I'm being rightfully defensive because my whitelist is being called into question over communication; not powergaming, not metagrudging, not malicious abuse, not flagrant violations of in character regulations, not out of character rule breaking, but communication. Communication, in most cases where the people reporting their grievances are only aware of half the story, where I am actively communicating and co-ordinating with either Command Staff while trying to get correct and actionable information out of them, or I'm relaying information from Command to the Security team when Command is sending me reports. The round this complaint is based off was manipulated wierdly by admins, giving a traitor an overpowered and hard to deal with mech with only one manageable counter; the ion rifle. I took it upon myself to deal with it personally, given the danger posed by a rogue phasing mech with the new mech weapons, and the severity of the punishment for failure that Central was implying. This situation had to be dealt with correctly, and as safely as possible, and had to be dealt with swiftly. I had a subordinate team I could not trust to that degree, mostly out of unfamiliarity and the reasonable report against the Warden; sometimes doing something yourself is actually and fully the right way to handle things.
  19. I'll be honest, I dread when Shen is Captain and I'm HoS, because she will absolutely try and Command the department from under me, and make unwanted banter in the Security channel. I can't form an opinion around the rest of her when she annoys me so much by trying to HoS-Captain when there's somebody there to handle the department.
  20. Good idea. Ask any regular CE lately; that range always gets bombed and breaches the cargo maintenance above it.
  21. The situation you and me were going into, didn't even require the rifle that you were sent to get. As far as I was aware, we were going to go into the Vault, grab the mech, and walk it to Cargo. The Captain insisted you come, and come armed, but we didn't expect anyone to be down there. One of your main points of contension here seems to be that I didn't tell you about the mech in the first place. But if you recall, the initial Centcom message said it wasn't to be inspected, touched or even protected. Not to be interacted with at all, basically. I wasn't sure what I could tell you about it because WE weren't told anything about it as far as I knew (the Captain may have later gotten a fax for confirmation because the first announcement was super vague), I only knew what the announcement was about because I just happened to glance at the Vault cams and saw the mech before the announcement. I didn't feel like you needed to know much about the Mech that we weren't supposed to interact with at all, and was already locked safely in the Vault; like how the Captain knows there's a nuke on station, but doesn't tell anybody. I thought we were all supposed to be ignorant. You saw the mech in robotics, fully strapped up with lethal weapons, AFTER recieving two Centcom updates about it, and having seen it phase into the Captains office. I told you that mech had been stolen from the Vault. You saw the pilot use it to commit multiple high severity crimes. And all you can say is 'that's not exactly suspicious'? Were you paying any attention at all? Do you have the capacity to draw your own conclusions? One of the reasons I didn't give you all specific orders to hunt the mech, was because it was so heavily armed. If you tried to stop it, you would have been killed. I had the AI trying to discretely provide information. Could I have given somebody else the ion rifle and sent them after it? Sure. But I don't recall recognising any of the characters as trustworthy security mains from an OOC standpoint, and ICly the character is new to the station and doesn't know the capabilities of the people he's commanding. And if that ion rifle was lost then we were going to have been at the mechs total mercy, unable to stop it at all - that's the reason I rushed to get it in the first place; because I assumed the phasing mech would prioritise getting the only weapon that can threaten it, out of our hands. I called for engineers over the common communication channel, that you all have access to and see. Why would I request help over common, and then need to explain to you over security comms that I was requesting help over common to you? Had I seen engineers follow my request, I was planning to co-ordinate a breach of the back of the maintenance area to get Maline from that side, while I kept them busy in robotics. I didn't see any engineers turn up, so it wasn't a tactical option I wanted to talk about. One does not tell the admins to wait, when they have an issue. Overall, this was an unusual round due to the semi-secret nature of the mech delivery, the fact that I discovered it accidentally and that we were told in no uncertain terms that we were not to do anything at all to or around it, until we were then later ordered to move it. I could have sat you all down to explain that there was a mech in the Vault that I intended to move, but I was certain that somebody was going to steal it, so it was time-sensitive. But by that time it had already been stolen anyway. I was honestly a little unsure what we should do, because the circumstances were so unusual. I won't even question why admins thought spawning a free Phazon for Maline to steal, was a good idea or fair to all the traitors they weren't spawning mechs for, but hey, I roll with things as they develop. Admins use their verbs for fun things now and then.
  22. Local HoS issues the absolute minimum of punishments, that carries precisely zero consequences, based on the recomendation of his investigative staff. Then rescinds it with an apology as new information comes to him. Isn't a perfect human, but ends up doing the right thing. Better report that. It was a warning. You know what I do when a member of Security decides to issues warnings? I say thanks for whatever and go about my day, because warnings don't mean a damn thing. Sure, in this case, you were probably innocent and right to object, while the CSI wanted to punish you for getting in his way (I have seen him do this before), but we ended up at the right place in the end.
  23. It's a two day old character that you've been with on maybe one round as Fernando. On that one round, you reported a death to me and I was too busy actually relaying your information to Security and trying to co-ordinate them, instead of immediately acknowledging you, so you bold all caps called me the worst HoS in history IC.
  24. Local HoS arrives late, introduces himself, gets a feel for the department and gets caught up on any ongoing issues... then goes quiet, because there is little to Command them over on Code Green with not even a hint of anything wrong. You got no explanation because you aren't entitled to an explanation; you're expected to follow orders. I was co-ordinating with the Captain and discussing our approach long before you were called in. You were the nearest Officer so I enlisted your support on their orders. Being one of the only crew on the station able to pilot mechs, and being right at the elevator, then recieving a Central Command order that the Mech is to be immeditely moved, and the Captain authorises me to do it, yes I prioritised the $100,000,000 mech we were told to transport over the firefight in the OR that other officers were calling out that they were responding to. I let the officers attempt to handle the shoot out, while I attended the issue I was situated next to, prepared for and ordered to do so, both by CC and the Captain. I was talking to the Captain on comms while camera scanning the Command area, and I see the scientist that someone has just reported to me as potentially dangerous, is now breaching into the side of the Captains office with thermite. I know he's going to be in there before I can stop him and the Captain is in imminent danger, as in may be dead within seconds, so I inform Security of the location and head over as fast as I can. While trying to talk him down, the scientist opens fire on the Captain, and then me, and we tase him down, arrest them and leave. And that's the first time we see the Phazon, as it phases through us, the Captains office and the Bridge. Not only are we now looking at Grand Theft of an extremely valuable mech that will severely damage Nanotrasens relations if we lose, but the pilot is commiting Infiltration of Command areas freely after having broken into the Vault, and at such a speed that we basically have no hope of chasing them, armed with weapons that we cannot match and armor that we can only really threaten with one gun. Everyone is briefly very confused about the Phazon phasing through and around us. I decide our only chance to even stop it is to ion out its battery charge. I should note by this point that I have recieved a message that potentially indicts my Warden as an accomplice of the scientist we just arrested, so I have discounted being able to trust them. But I did not call for their arrest because I was missing actual evidence, and the Phazon was proving to be the bigger threat. So, yes. I got the ion rifle and carried it myself, because my Wardens loyalty was in question (and as it turned out they actually were a traitor). Why would you assume the situation had changed if you hadn't been given an update? I told you the stolen mech was on the loose; you saw it yourself. Did you want me to sit your character down for a briefing every five minutes? Please, god, show a little initiative over events you saw unfold before your very eyes. You read the same announcements as I did, you saw the mech. I couldn't tell you to setup a perimeter, because I had no idea where it would go, and knew it would phase through you anyway. I was constantly trying to get the AI to provide a location, or tracking, of the mech so that I could pass that on to you. Basically anytime I wasn't talking to you, I was either talking to Command and the AI, or moving somewhere with urgency. We found the mech in robotics, it phased away. I was on Command comms with the RD trying to figure out with the RD why the mech was there; it was there to charge. I asked them to dismantle the charging ports, to cut the mech off from its power. A minute later, the RD reports over Command to me that the mech is back in robotics, so I run in. I can see Maline is out of the mech, in a stolen RIG, attempting to climb back in, so I spray her and the mech with ions to shut down the Phazon and the RIGs power cells. And it works, because Maline has to try and fix the Phazon over the next few minutes, while Security surrounds them. Maline tries to install fresh batteries while I pull them out again. I have called for engineering to help officers breach in through the SMES room, but I don't remember them ever turning up. By this point, I was essentially taken out of the game by ahelps enquiring about my characters skills. I could ignore the game and deal with the admin breathing down my neck, or ignore the admin and play the game. Let me tell you, when you play Command and you suddenly have to deal with ahelps, you cannot perform your job at all. I had to spend the rest of the round focused on my ahelps, so I'm sorry I couldn't micromanage you through a firefight. I was standing by the Vault because I'd accidentally seen the Phazon down there, and the CC announcements were developing that situation. I assumed that someone was going to try and steal it, but I didn't expect Maline to breach in from the back like she did. I had no idea there was an alarm in the Vault that you were heading for, or an atmos situation down there that you needed to fix, so I held up the lift to stop anyone going in ahead of me while I discussed my next steps with the Captain. I didn't explain myself to you because I didn't have to; likewise, you didn't inform me that you knew anything about the Vault was amiss, even when given plenty of opportunity to say something, anything, while I conversed with the Captain.
  25. A lot of issues with this statement. It's not documented harassment. The only time we were marginally introduced to the fact this was not just humor including @LiliumArgentium is when they said the following in main discord, which Berry spoke to them about it. "I'm thinking about leaving Aurora." Not a lot of us are aware of this. This complaint brought it to light. No, this is not a clear case of lending power. This is a case of miscommunication. It's actually quite rude to call someone out for abuse like this with minimal to no evidence. I don't know when exactly that particular exchange with DatBerry was, but I know at the very least DatBerry/Catnip, Alberyk and I think Aboshedab were at least vaguely aware of the harassment going on over the last few weeks, as they have been either responding to unwarranted LOOC messages from players directed at Lilium, or have been spoken to directly regarding the matter, such as when somebody used 'you're a thot' as their reason for gibbing Lilium at the conclusion of an event round; and then they discussed it afterwards like adults. I'll grant, minimal evidence of no great abuse. I also noted that Nursie was not the only one, and was not even the most heinous aggressor. She was one of several but was doing it from a position of power, and happened be the one that pushed Lilium past her tolerance. But your verdict is your verdict and I have no stand to refute it. I hope everyone can move past this with a little empathy, and all treat each other more humanely in future.
×
×
  • Create New...