Kaed

I feel like this would need to also have a whitelist sort of thing. For people you know well IC, so they're auto-recognized at round start and you always see their name on the radio. It might also need to be paired with descriptors that can be applied to unknown voices, like . So, you see masculine unathi voice says, "What iss with thiss radio?" These are automatically applied based on your character, but voice mimicry would have to have a way to falsify that too. The concept of self-designating something to put to a voice could also work, allowing you to click on an unidentified voice and designate it as something (Unathi Intruder A), though their name still exists and it will sync up if you manage to see them and hear them talk off-radio? It's a difficult prospect to enforce mechanically.

Eh. It's not like they have to advertise that they did it. But honestly. I'd like it if the vending machine were changed to something less inside joke meme shit. Seriously, is there any food you've even seen called "Human Food"? And yet, we have 'Skrellsnax' and "Nathi-snack canned meat' (which, by the way, changes its name from a typoed version of the product to correctly spelled after you finish eating it). Not to mention references to clowns, syndicate, and griefing (4no raisins). "lol we're an evil corporation we serve people muhhuhuh' is not the right way to do it though, I don't think. Soylent green existed in the setting it was created in for a valid reason - the world was overpopulated and people didn't have enough to eat. There is no actual reason for a space-faring race having general prosperity and lots of breathing room on their many planets to begin processing their own species as food other than for shits and giggles. I would much more prefer that the food items inside become something a little more generic and lore friendly. For instance, skrell are a somewhat logical, analytical race, so Skrellsnax could be come something dry and boring sounding like "Skrellian Nutrient Strips". And maybe rename 'Cheese Honkers' to something less clownmeme like 'Cheese'ums' or whatever. The raisins can be called Star-Maid Raisins, to be in line with some of the other pun-expy products we have. And so on.

I know Opamator exists, and I've seen him... in rounds. But we have never interacted that I recall. I've also never seen this Toronto-88, but if I had, I would feel equally as antipathic towards them if they were a HoS. So I'm not really targeting you specifically, and in fact I have no positive or negative bias towards you as a player due to my lack of interaction. This is entirely based on my feelings about an IPC being an HoS I'm not really sure of your argument about a HoS being a replacement warden. You could just... be a warden, instead. And then we would have a warden. I feel like you are somewhat missing my point, however. I'm not bragging that I could take anyone down. In fact, you would probably win unless I ganked you with emps or an ion rifle, I'm horrendous at combat. This was more an expression of the tenuous nature of your desired position, and how untenable it is. If the consequences for removing the Head of Security from the round via violence are legally barely more than a firm slap on the wrist because they aren't a person, it creates an unstable position of authority. Unlike with other departments where an IPC head can just be considered an advisory position there to help the department function to its best, the security department's culture is rooted in combat. Many antagonists are also capable of combat and it forwards their goals. The consequences of a murder charge and a HuT are a powerful deterrent for nor casually killing someone who is in your way. It's difficult to recognize the superiority of an individual who is legally your inferior, much less spiritually or ideologically. Unathi, for instance, generally do not believe that synthetics have souls and would have some difficulty bending knee to them, authority wise. I know mine would, anyway. And a head of security is, in the viewpoint of the crew, basically just below the captain in terms of authority during a crisis. Possibly during other times, too, regardless of the command standard that 'all heads are technically equal', people will be people and defer authority to certain roles in certain situations. It's one thing to work alongside a synthetic, it's entirely another to be told you are their subordinate. I'm aware this is delving far more into sociopolitical concepts than most of the other comments, which mostly amount to 'yeah he's a pretty good roleplayer +1", but these are the things I actually think and care about in my spacemen simulator, even if other people don't.

"Say, Bobby weren't IPCs unsuitable for leadership positions?" "They were Billy, but Papa Dorn said they could be in charge of peoples after a bunch of them fought in a battle that benefited his goals." "Gee, Bobby. Synthetic rights sure are confusing and flipflop a lot. Why can't they just be happy we let em have free will?" "I reckon you're right, Billy. Can't trust a synth farther than ye can lawset it." I don't really want a robot HoS. I was under the impression IPCs couldn't be heads, but from what I hear, some random people won some most kills antag contest and got to force this policy change into the game because of it? That's a load of crock, as far as I'm concerned. If Opamator was built to be a security robot, then he needs to be a security robot. As far as I'm aware, lore has not yet changed to make IPCs people instead of station property, so the idea that we would give a glorified toaster that cannot even be loyalty implanted control over the station security department is ludicrous to me. Presumably there is some vague lore reason why it makes sense I haven't been able to find. "He is robust" seems to be a running theme here for approvals. A head of security has more implicit responsibilities than 'being robust'. If you want to be in firefights with him, he can do that as an officer. HoS aren't really supposed to be acting like frontline fighters, anyway (even though a lot of them do) Additionally, if he is effective at distributing equipment, he can do that just fine as a warden. He doesn't need to be a Head of Security to do that. I also feel I should point out that by current legal system, I could execute Head of Security Opamator as a an antagonist. or even member of the security team, and my legal sentence would be about a half hour (sabotage and assault on a head of staff). Possibly less if I turned myself in afterwards. At least being a head of a non-aggressive department (i.e. anything but security) doesn't put you in the cross-hairs for any anti-synth individual who wants to make a point about the irrelevancy of your authority and existence. Your position is a liability to the company more than a benefit in such a situation. -1

Yeah, that's a tough one, especially since antag rounds are common and considered to be noncanon. I would say everyone is assumed to not know anyone else outside of department unless you are IC friends. "I met them once three weeks ago in a round, I can't remember if it was an antag round or not though, guh." Additionally, if you walked up to this theoretical Kaed McKaed and said greeted him, he'd have his ID on probably (which you could verify with a glance), and the point is moot.

This would be really hard to enforce mechanically. I guess the only way would be to make everyone show up as 'Unknown' unless examined while they have their ID visible from a certain distance. But that doesn't cover AI or people who introduce themselves. It would be much easier to just adjust what the rules consider 'metagaming', and enforce it via admins, much like how we expect people not to shriek "AI MALF" the second they see a dark blue APC or 'WIZARD IN THE BAR" because some guy in a gentleman's suit and hat appeared in a cloud of smoke. The AI announcing "Officer is being attacked by unknown intruder in engineering"serves the point just as well as 'Officer Jenkins is being attacked by intruder Ether in engineering." The AI recognition tree should roughly work like this -Someone is on the radio -Can you track this person? -If yes, can you see their face? (If their face is concealed, you should still be able to identify their ID's job designation by activating your sechud if you have one) -If yes, are they on the crew manifest? -If Yes, then you can assume you know who they are. If any of those were 'no', then you cannot immediately identify the person talking on the radio, unless you have previously spoken to them and they identified themselves.

How many distinct sprites are there? And could you provide me with a file of them?

I thought about this for a while, and I can't think of any way that this could be mechanically enforced, so I'll make it a recommendation on roleplaying rules instead. It's bugging me when people recognize the name of everyone by their voice and face, even when they're an intruder antagonist or are a voice of a character who doesn't exist via voice mimicry, or who the person identifying them has never met. Yes, I know it's easy to just read the name on the screen, but how would you just know that is their name? It's not feasible that everyone knows the names and voices of every crewmember on a constantly changing workforce at round start. Maybe in the department you're in would be a reasonable limit. AI and synths are particularly bad about this and voices on the radio. I've heard so many excuses like 'it was coded into their radio transmission' to explain how they know "Ethar' is the name of the mercenary Ether that the synth's player couldn't spell, who just spoke on the radio for the first time in the round. This would create interesting scenarios where you have to describe someone based on their physical features, which is a lot more involving than running around until you see someone whose name is the one you're looking for when you hover your cursor over them. People have an opportunity to change clothing and hair and not be instantly caught because their name is still Bobert Bobby, the assistant traitor who was spotted breaking into maintenance by a doctor from across the room, after which he immediately ran away, and the doctor never saw more than the back of their head and a glimpse of their face. Basically, unless you're actually interacting with someone in close proximity, and they are wearing an ID, you should not be able to identify them with perfect accuracy on your first meeting, unless I suppose you share a department. Get to know your coworkers instead of relying on assumptions of recognition. I'm also not sure at what point it was presumed that synths can recognize the name of anyone talking on comms by [insert vague technobabble], but that shit should stop too. Faces of crewmembers, I can see. They have a database to work with on that.

I dunno, man. You can easily use a common wrench for that. They're not hard to find. Unless you're going for the idea that it can't be sealed back up?

That's not helpful. It's entirely possible for a pAI to be under orders from their master to be a shitlord. Or not have a master at all. Ahelping them for being annoying doesn't fix the issue of them being very difficult to pin down, when they have a valid reason to be allowed to be annoying.

I feel like the intent behind pAIs was not to be small, almost untrackable shitlord who spends the whole round hiding in maintenance and irritating everyone over the common channel. They're more supposed to be little personal assistants that stick near a master? Now that they apparently get to share access, the right pAI can be absolutely obnoxious with a very low chance of ever being caught. Could we implement some way of dealing with 'rogue' pAIs. Whether it be just a tracking beacon inside them, or a remote delete function for them, or even something that disables pAI access to the common channel.

No one said anything about them being equal. Just separate. Maybe we don't want the dirty synths mucking up our medical records "Excuse me, I am injured, doctor. Beep boop." "We don't serve your kind here, synth. Go to the minori- I mean, the robotics bay."

Currently, IPCs are treated like normal crewmembers in their records in every way. They have records stored in the medical database, even though they do not visit medical to be repaired, because medical is not equipped to fix them. I propose that IPC medical records be moved to a special Synthetic Records computer available to roboticists in science. They would have more relevant reason to need to access that than medical, anyway.

No. If the tesla gets out, it can't be recovered. There is no benefit to letting engineers be shielded from it other than allowing them to cackle manically while everyone else dies. They can suffer with everyone else.

Exactly. If you want to do these things, then you can already do so. But that only works if you have a competent medical team. If you have doctors that dont even move themselfs to cryo, then the best system is useless. You know, that's more of an ooc issue. Saying we shouldn't implement anything to improve medical because 'no one would use it due to being incompetent buffoons' strikes me as fairly pessimistic. True as it may be or not, QoL improvements shouldn't just be discarded because you think they'd never end up being used. Sure, that works. I mean, as long as it's there, whatever provides you with the data organized by doctor is fine.

That's all well and good, but it's not actually what I'm asking for. Leaving a note on someone's medical record is centralized to that person. There is no way to sort activity based on a doctor, not a patient. We could certainly work a 'reporting your services' mechanic into the medical hud instead of making an entirely new console, but I'd still like there to be a tertiary system SEPARATE from medical records. Doctor activity logs, if you will. I want to see what my doctors have done on a shift, in an easy to access format that doesn't require me to look at every medical record and take tally. 'Are there currently corpses and blood in medical' is not sufficient data for what I'm wanting, either. I don't know why anyone would ever respond to an suggestion about additional data entry mechanics with 'just track activity by how many bodies are in medical'. "Is there blood all over the floor?" "No sir." "Welp, guess that's all I needed to know! Medical must be doing it's job!" Sheesh. I will admit that the triage tag thing could probably be replaced by huds , except... -Medical huds are only found in one out of the way place of medical and no one spawns with them -Not everyone wants to wear a medical hud at all times and would rather rely on direct observations, because medical huds are inaccurate. -If we're going to leave notes about someone's status on their records via huds, it's going to get cluttered fast. A simple colored tag would be a very efficient visual marker. -Medical huds look really stupid (this is actually just an opinion, though)

This still doesn't address tracking doctor activity or the triviality of writing every scratch onto someone's medical records.

... No, it isn't. Medical records document relevant medical information about an individual. They do not track the activity and performance of a doctor over a shift. Medical records also can only be accessed at certain desks, and has a really gross, wonky formatting system. Forcing doctors to go to these consoles after every patient is a hassle which this suggestion tries to alleviate. "Treated for cut on leg by Doctor McNurse" is not a relevant enough addition to medical records to justify it, and further does not allow you to sort by doctor. Similarly, medical huds only give you very general level of the health of a subject, rather than their actual injuries. Someone can have less physical damage than another person, but be suffering from internal bleeding and broken bones. This is especially true if first aid is being performed on external injuries. Relying entirely on the medical hud can put that person in danger. Sure, you could rely on every doctor wordlessly walking by and scanning every wounded person with a handheld scanner, or... you could rely on some kind of teamwork for the medical staff and allow some people to carry out initial diagnosis and severity before tagging patients for the actual doctors to prioritize.

That's technically a different suggestion, but I revised the title and added it to be part of the same suggestion.

As Zuh stated. Literally why nymphs (bloodsucking bundles of alien branches) and drones (probably covered in oil, dust, grime, and other goodness; otherwise metallic objects) are pick-up-able is because of developer indulgence. Believe it or not, the feature is internally consistent with already established mechanics of being able to pick up all holder mobs. This list of mobs also includes dirty, hairy, lab monkeys who wear diapers. (Diapers which probably have shit in them!) I hope I've been graphic enough to get my point across. A recommendation: please present an issue for what it is next time. That way we can discuss the actual issue, instead of us having to read your walls of text about matters which are only tangentially related. And also, recall Samantha Mason? The mice loving doctor/CMO who existed before Nanako was a member of this community? She always dragged a mice with her, even if she couldn't put it on her shoulder. I don't remember Samantha Mason, no. But you are correct, I should have narrowed down my suggestion to something a little more precise, and I do tend to get rambly when irritated about something. Either way, the suggestion is out there now.

Medical can be a chaotic place during busy rounds, and often becomes a blood-soaked nightmare where people lose track of who they treated and for what. So, I propose a simple in-round documentation system that stores medical visits and activity involved under the doctor who performed them. This could be done at a special console located in places throughout the medical, or even through the medical PDA, I suppose. It would auto-fill some things like time of form submission and date, but the end result would be an array of documented activity for every doctor/patient interaction, including data like: -Name of Doctor -Name of Patient -Time of patient arrival -Diagnosis (broken leg, trauma wounds on head and neck, poisoning, deceased on arrival, etc) -Treatment procedure (Used basic first aid kit, administered dylovene, performed bone reconstructive surgery, cloned, etc) -Patient condition on release This would be organized on a per-doctor basis, allowing the CMO to track what doctors are doing what, and if they aren't doing anything and are being lesbians in the back room all shift slacking off. Psychiatrists could also submit their own form, but it might arranged a little differently, because they don't generally treat physical problems. Also, some way of designating a crowd of wounded/dead thrown in medicals lap to prioritize them, such as color-coded tags you can put on people (triage tags) after a cursory examination to help doctors prioritize properly, would be good. Probably via a device that lets you pick the tag color and then apply it to a downed person, rather than a finite quantity of them in some sort of box.

A feature existing entirely due to developer self-indulgence doesn't particularly inspire me as to the validity of its existence. That being said, I stand by my previous long post about why specifically mice are an issue and the direction I feel should be taken.

You were waiting on me? You should have formed the comment as a question, then. Because it sounded more like you were just commenting on the comparison to other mobs. But sure, I'll elaborate. The mob holder concept was originally generally reserved for things like cats, maint drones, and diona, I might be missing something, but let me elaborate on why those ones actually have valid reasons to be picked up. Cats: These are domesticated pets. Cats are predisposed to liking to be picked up and petted, and to be around humans. Maint drones: These are tiny robots that run around and fix the station. You shouldn't technically be picking them up, but they certainly aren't going to hurt you because of you because of their laws. Almost all of them are player controlled too, since they only spawn when someone becomes one. There also once a time when they had a slightly hard time getting around because there were no door hatches or disposal travel, and they had to rely on awkward vent teleporting. Carrying them through a few doors could help them out. Diona nymphs: Bloodsucking pests though they may be, this fall under a similar category to drones. They are mostly player controlled, and nominally intelligent enough to speak. You could put one on your shoulder and pick it up if you are willing to trust it enough to not suck your blood. Diona nymph mobility was even worse than drones in the past, because they couldn't even use borg powers to remotely open doors. On the other hand, mice are not supposed to be roles you use to interact with the crew in a positive fashion. Sometimes they appear on station with announcements that they need to be cleared out. People keep saying they're just vermin, kill them if you want. In fact, they are almost mechanically identical to lizards, which nearly everyone just kills on sight, except they have a slew of extra abilities for PLAYER mice to use, like vent crawling, being able to eat food, hiding under objects, and being able to emote squeaking with a sound byte accompanying it. Most of these are traits you would put on a thing you designed for ghosts to join as when they don't really want to participate in the round but would like to be there as observers. Most of these things are also designed around making you an annoying vermin - making irritating sounds, running away from people trying to exterminate you, and eating the crew's food. Then a developer came along who really liked mice, and undercut their entire intended dynamic of 'unwanted vermin' by pushing in a change that let people pick up mice and put them on their shoulders. Unlike cats, which exist in a finite quantity and are supposed to be tame, and drones/diona, which mainly exist as player mobs, mice are and remain primarily an 'environmental' mob that people exterminate or at best ignore. People honestly shouldn't be picking up a possibly diseased rodent and carrying it around to poop on their shoulder and panic every time something large moves nearby. But they can, because of one person's moderate obsession with them while they were still on the dev team. I could potentially see an argument for only letting player-controlled mice be picked up and worn on the shoulder, if they really want to roleplay as a tame friendly mouse, but the majority of the time, people who are wearing mice now are people who picked up a mindless mob that they're supposed to be role-playing is a wild, untamed animal. Just so they could use it as an accessory. There is another thread about mice biting people who pick them up. This could also be a solution to people not grabbing non-player mice to use as a kawaii accessory. Because I think that's largely the root of the problem here. Picking up and carrying mice that are not containing a ckey, because they are incapable of roleplaying resistance to the idea or really participating in any way. And yeah, it's pretty easy to undercut the whole subject by going 'lol mouse outrage again?' and trivializing problem, but I'm mainly trying to fix what I see as another dumb oversight Nanako made that is creating characters with 'pet mice' that they picked up in a random maint shaft. I'm not against people playing their mice how they want, but when there isn't even a player involved and they become an animal prop, I feel mechanics abuse is happening. So, tl;dr verision: Figure out a way to stop or discourage people from picking up mice without a ckey in them. As an aside note, I notice I seem to come into conflict with people in threads a lot because I have a game development mentality that seems to be different from a lot of people. I'll try and summarize it like this: -If a mechanic exists, and it serves no useful purpose in the roleplay setting other than to be irritating, distracting, or serve to make your character more snowflakey at the expensive of a sense of immersion, then it needs to be revised or removed. "Because it's funny" is never a valid reason to preserve something for me. Insisting that the ball be passed to admins for everything feels lazy to me, when something I feel should be dealt with on the coding level. I'll make a more relevant comparison to the issue with mining and unlimited pizza spawns, which I also made a thread about. Sure, it doesn't hurt anyone to tile the entire cargo bay with stacks of pizza boxes, but it there really a valid reason you should be able to do this? Rather than just suggesting an admin be called every time it happens, how about fix the issue that allowed it to occur?

I was asked to weigh in on this application by Munks. I guess I don't see anything particularly bad. He's an okay roleplayer. I don't generally have a lot of invested interest in tajarans, and I only barely know their lore, because I am too busy with lizardmens. But I guess he is a field medic that came here to be a paramedic? Seems solid. If that backstory doesn't work for tajarans, it's not really my place to say. Someone who knows more about them would have to judge that. If you start putting mice on your shoulder and being nursey-kawaii, I will murder you, Munks.

I understand the words you have said here, individually. But put together, they don't make sense. Anyway, yeah. There are definitely ways around not needing stairs added.