Jump to content

Owen

Administrators
  • Posts

    1,102
  • Joined

  • Last visited

Everything posted by Owen

  1. But AI is tasked to oversee the crew. So of course it's going to be more efficient to allow security officers to arrest based on AIs word. So where's logic in, "Let's make a machine that can see everything but put limitations infront of it so it cant be at 100% efficiency" Wait. Are you saying based on evidence that the AI provides or just if the AI tells someone to arrest someone? Because, if the AI can prove that there is a threat, Security Officers can act on it. However, the AI cannot and will not be allowed to command around the crew. Many species that are employed by NanoTrasen wouldn't want to give an AI that amount of power to order around people. I honestly, think it is fine how it is now.
  2. If you are referring to the Third Incident. It ended in 2192. It still took over a century for the Skrell to begin to recover. So, I would say that there is a real reason for people not to believe they are accurate 100% or even need to trust them to begin with. Currently, I feel that the system that we have is fine. The AI alerts either Security or Command about something that is happening. It is then the Head of Security's, Captain's or Warden's decision to write a warrant and deal with the issue. Of course, the AI is also able to alert Security about major threats such as intruders on station that would mean that they would not need a warrant to deal with. As stated before, the AI is not a commanding figure on the station. It is meant to serve and assist the crew. Its word alone should not be enough to command Security to arrest someone.
  3. At least the Altmer and Maormer would be Skrell. The other elves, I'm not sure about. The Stormcloaks would be NanoTrasen and Miranda Trasen is Ulfric, MT=Ulfric confirmed
  4. Probably the Frontier or something.
  5. Yep. Totally legit realistic guide
  6. Hahahaha you think you were the first CCIA to kill another CCIA. You innocent being. But yes, this was an amazing thing. Of course you wouldn't know about the other 'incidents'... They were never made public for obvious reasons. If you find this, congratulations to you
  7. It hasn't started yet.
  8. I just said that they were allowed because it never has been directly stated that they couldn't be one. I think it makes sense for them not to be in the IAA position as they aren't allowed in many valuable positions. After the antag contest IPCs will be allowed to be in all of command or not at all anyway so I'd just go with what the administration says for now. Edit: Saw previous post. Open to making a temporary ruling if needed until the contests results come in.
  9. That isn't a bad idea. I can see about getting it changed possibly. It could probably be an Officer, AI or Loyalty Implanted person, directly witnessing a crime. I'll think about it.
  10. Owen

    Bridge Secretary

    I don't really want this to be a thing, honestly. I like to think that I'm pretty experienced in both being a Captain and Head of Personnel and there are rarely times besides either super chaotic events or sometimes Mercenary where things get so out of control that nothing can be done. During normal extended shifts or quieter rounds, I feel that if there is a Captain/Head of Personnel, there isn't really a need for an assistant. I personally don't like having assistants and don't have them when I'm in Command. I get it, people like having an assistant which is totally fine as they can promote someone who isn't doing anything to help them. I just feel that if we had that role I would purposely be avoiding Command roles that deal with them just due to my general disliking to having them. Basically, no to secretary, people who want one can promote an assistant if needed.
  11. It is meant to keep Security from waving their dick around and forcing entry to other departments and just arresting people without permission. It also gives the peasants the impression that they have actual rights. Hah, as if
  12. Alright so, while I was reading over this application, there were some points that sort of confused me. I'm not sure if I just couldn't understand what you were trying to say but this stood out to me the most.
  13. I might be interested. I have had this game for years now and have hundreds of hours in it. Still pretty shit at it though
  14. Game is fun. I is shit
  15. Closed due to inactivity and little shown interest from the players to get the IR dealt with.
  16. Applications are now closed. The following applications have been accepted: - Jboy2000000 - Bedshaped - Whiterabit - Arcbot - Pikl Any concerns may be addressed to me directly, through PMs or Discord.
  17. If you wish to apply for the CCIA, please fill out the form provided and then either post it to this thread or PM it to me directly. If you have any questions about the applications, you can message anyone involved with the CCIA and they will try to help you. Do note that we are trying to once again, raise our numbers in order to work through the backlog of Incident Reports. [b]Byond key:[/b] [b]Character names:[/b] [b]What times are you available? In GMT: [/b] [b]Do you have any experience with Moderating? Or similar.[/b] [b]Why do you want to be in the CCIA Division?[/b] [b]How well can you handle stress?[/b] [b]What does it mean to be an agent?[/b] [b]How active on the forums and server are you?[/b] [b]Anything else to add?[/b]
  18. If you want to continue a complaint on Garn's AI then please do so on another thread as I acknowledged that the AI was not good but focused the complaint on LordRaven's character who already had a decision made on them. Just want to note that the AI had reason to keep the door shut because the Nuke Ops said that they were going to use their nuke on us if we tried to evacuate and someone continued to use the consoles to call the shuttle even though they knew the threat. It was locked in order to keep people from breaking into the office and calling the shuttle (Which people were calling the shuttle a lot before the Captain arrived). The reason that the door continued to stay closed is because the Captain made it known that he wanted to call the shuttle which would've risked all the crew, property and the AI itself so I think it justifies keeping the door closed.
  19. Full logs after the arrival of Akero'Ceita Ceeta'Pleat
  20. BYOND Key: YouJustGotOwened Player Byond Key: LordRaven001 (This round was horrible overall but I had the biggest issue with LR’s character’s actions) Staff involved: None Reason for complaint: (I’m going to be posting all of the logs from my side at the end) When LR joined the round as his Captain, Akero'Ceita Ceeta'Pleat, almost right away, he started antagonizing the AI (Visual Basic. Not sure of the ckey) He said things like, Now, this sort of escalation was not warranted. I get it, the AI was being a little bit of a shitter at times during the round but it was a high-stake Merc round. I believe that the reason that LR’s Captain said what he did right then was because the AI made this announcement. Not the best choice of words, I get it. But, there is no reason for a Captain, a Skrell at that to act so rash and continuously threaten the AI and claim that it is rebelling. Your Skrell is allowed to be scarred from the Third Incident (Glorsh-Omega) but they likely have gone through plenty of psychiatric exams so he should be stable enough to not flip out whenever an AI is on station with them. Shortly after that exchange went down, the Captain began arguing over the Command frequency with the AI about having his office locked down due to the Mercenaries claiming that they had a nuclear device and that they would detonate it if we attempted to evacuate the station. Nevertheless, the Captain continued to order the AI to open his office and was insistent on calling an emergency shuttle even though he didn’t take the time to stop and get updated on the situation. With these logs, you can see that both the Captain and the AI were acting pretty standoffish towards each other. My issue with this again is that the Captain was basically ignoring everyone else and being insistent on ending the round. There were nuke ops, yes. But the ERT was here and the Nuke Ops threatened to completely wipe out the station if we attempted to evacuate. The AI continued to tell the Captain about the nuke being stolen and that we couldn't risk evacuating (Captain still hasn't really stopped to ask what was going on) and the Captain would say things like this. Both the AI and the Captain kept antagonizing each other and the Captain continued telling the AI that they shouldn't revolt against their superiors and how he will destroy/eliminate it if it didn't listen. I don't care how scarred your Captain is from the Third Incident. He could've been face to face with Glorsh-Omega but this is severely overreacting while there was a much larger situation going on. Your Captain should be mentally stable enough to put his distrust aside if people are assuring him that it is fine and work to deal with the actual danger. After it is dealt with, by all means. Check the AI's laws. Make sure it is operating appropriately. It was being a little extra aggressive. This is where my character (Finis Eridau) voiced his concern about the Captain's actions because he really was adding a lot more risk by evacuating the station. I still, OOCly feel that continuing to call the AI a rebel isn't helping. There are still a lot more logs that are pretty much having me make the same point. I'll put the full logs in a second post. There were some major announcements that pretty much screamed about how the AI was rebelling made by the Captain. I really don't like making complaints but I've seen this issue coming from LordRaven's Skrell and would like to see his whitelist removed until he can better figure out how to roleplay as a Skrell. I have no issue with him reapplying for it in the future though. Also, just wanted to note that I am not actually mad about this just want it to be addressed as I don't believe a Skrell should act in this manner. Approximate Date/Time: Around 5:30 EST. June 1, 2016
×
×
  • Create New...