ben10083

[mention]LanceLynxx[/mention] But don't you agree how annoying it is when the round type you been voting for over and over again finally gets picked...only for 6 people not to ready up and force another vote?

As someone who plays CSI (albeit very rarely), I can confirm that tampering is quite annoying with this example: Spawn into round at beginning wait 30 minutes for stuff to go down Get reports of dead body and excitedly get over there see body already gone and everyone walking all over scene cry on the inside and complain on sec and common channels go back to office in defeat repeat. It isn't just that they CAN be arrested, but the person here wants the HoS/Warden/whatever to ENFORCE it.

CCIA should NOT be pushed put of IC matters, and although I am not a CCIA agent and cannot know for sure, I bet it was enjoyable inspecting medical with CCIA status and leading a ERT instead of investigating yet another report. Allow CCIA to do things instead of investigations. -1. (Also they are already a whitelist so what do you even mean by "yet another whitelist?)

I see no problem with how the raider team acted, sure they had trouble coming up with a gimic, but who doesn't? These people are only guilty of "winning" and as they said, why come back to the station when they know they are going to get pounded by the ERT that would likely be called if they come back, and the Durand(s) that sec would quickly find out about if they haven't already. From what I see raiders had two overall paths; 1. Go up to the inevitable Sec. ambush at the vault lift and either die quickly, ending the round rp, or killing all of sec causing salt about the slaiughter and calls of murderbone. 2. Escape stealthly because sec didn't bother to secure the sublevel.

DARNIT I was gonna report it lol

if you make the delay longer, then why not just shoot them normally? if we add a second delay the aim function it becomes useless -1

I think when it comes to increasing skill they should have it so people's skill develop as they do the task more and more (construction - building stuff, Anatomy - Doing surgery involving organs and/or bones). To make it fair the occupation they select their character to do will be permanent (unless the HoP reassigns you, which has them have to send the reassignment form to Centcom so it can be changed.)

Pretty sure, and if so, there is really no lore way to allow this to happen...

I feel that combat borgs can be a massive risk in terms of double edged sword, let me do an example to show you what I mean. One Traitor emags some drones and has them get to ai and emag THEM, making them loyal to him. He then has them stockpile reset modules. then the other traitor then takes the spare id and the first one overpowers the RD and takes their id, now they activate combat override. In summary, combat borgs can also work for antags unlike the ERT, and antaggy combat borgs sound much more interesting than them just being synthetic ERTs, so if they become something that only malf AIs can have happen (a tech that unlocks the module) it will be alot for interesting.

Ok I have seen a trend of IPCs acting like any damage they do can be cheaply fixed and that they should try to take damage to shield organics, this encourages non-sec IPCs to actively hinder antag activities much more than they should. As such I propose having it so structurally weak IPCs (Accessory, Mobility, Baseline...maybe.) or maybe even all of the models are programmed to try to protect themselves even more than other crew due to financial losses of repairing IPCs.

Weaknesses are a bad thing, that is why they are called weaknesses. Perhaps allow force gloves to have a slight armor value, and allow science to make "heavy duty" gloves which have a much higher armor value.

tbh as someone who does roboticist from time to time I always like having a spare cyborg body, and if this suggestion is implemented I would also make a IPC spare for the same reason; Shit happens. It is not powergamey to have a spare IPC or cyborg body because it makes sense ICly wise to do so, as their job is to repair IPCs and cyborgs as quickly as possible.

yeah this seems like an interesting alternate antag race, but NOT as one you can pick as a char itself, -1 unless it is a species for mercs and other baddies like that.

+1, drones are the unsung heroes of this station and if they band together they should be able to fix the WORLD.

I say have it so the shuttle and it's airlocks cant be touched, and departures cannot be vented, but otherwise the antag can make it as hard as possible to get there within reason.

Really want to hear this story of the spear, +1

Maybe have it so if someone resets the research servers, the levels are reset like how monthly is, to balance this the server room is moved to sublevel and is MUCH more protected.

I like this suggestion, too many times I have hugged people as security who have killed most of command and/or other shenanigans.

yeah maybe just have a "official" NanoTrasen announcement saying how NanoTrasen will no longer permit cyborg to IPC upgrades, that or just say that station bounds can no longer change to IPCs, but people who already did so are fine.

oh god I am having flashbacks of people getting ganked by bees. 1-hit kill bees, even the admins were terrified.

Ok have a seat let me set the stage... A person commonly plays a cyborg named C.A.R.L (not an actual person, just made it up) and becomes well known OOCly The Person eventually gets a IPC white-list accepted and changes C.A.R.L from a awesome cyborg to a IPC, for little reason. Ok with that lame example aside, the point I am trying to get at is that some people are using the cyborg role as "training wheels" for IPC, and when they get their IPC white-list accepted they make their cyborg a IPC for no reason RP wise (why would NanoTrasen need to upgrade their cyborg to a IPC that requires payment?). Overall I have a way to fix this; Cyborgs are not permitted to be changed into a IPC character, they are to remain a cyborg. This will encourage more creativity with IPC characters rather than "I am a cyborg you know that is now a IPC." and will allow for new characters, with new quirks and backgrounds.

[mention]Azande[/mention] you mean the request console which only allows you to send messages to like, 20 places? I mean communication as for forms like cyborgification forms and incident reports and etc. If request consoles CAN send papers and forms....Please PM me how or reply on this, as that would be important.

Fax Machines are in Aurora to allow for quick transport of documents to heads and/or cent-com, but overall they are rarely used for station purposes and just exist as a "centcom" button. I propose to add fax machines to the following areas; Department Lobbies (Cargo Office, security lobby, engineering desk, etc.) Robotics (many forms for robotics) Vacant Office (To allow for people to use it as a office more effectively.) and give Fax access to the following jobs; Cargo Personnel (exuding miners) Medical Personnel Warden and investigative roles (for incident reports and other security forms) Engineers (for the station modification forms and other things) Roboticist (For the robotic forms) Clerical module equipped robots (If possible) Now I know what you are thinking: "People will abuse it by sending messages to centcom!!1!!" which is why I also propose having the access for fax machines changed by having instead of one access for the machines two, one for basic fax use (in station) and the other for centcom fax access (take a guess what it allows you to do.) Now to address another concern; spamming of faxes by people being assholes jerks, I propose modifying Corporate Regulation i107 (Misuse of Public Radio Channels) to allow people to be punished for misusing the fax system. Overall, If this is implemented people may be more willing to do paperwork, as they would now have to walk so far to get it to the right people, it also allows the fax machine to be MUCH more important to people who are not heads.

Yeah +1, I really hope they do this.

+1, if anything, make it easier to fix vending machines, and/or make it easily repaired by a debugger.