Killerhurtz

I started this with three main pillars in mind: -Complement, not overwrite. -Establish legal context of forced cyborgification -Define, in clear and legible terms, what each category implies. Now, for the reason behind each decision: 'Animal borgs being robots' - I'm going to need to go into detail here. The suggestion I make is to differentiate between machines which use animal brain matter as processor and machines that use an actual integer brain as a processor. Chauncey's robo-chihuahua is an animal cyborg. DELTA-12, even though it has dog brainmatter, is a robot. Does that make sense? Positronic brain I have to agree - but as I said, it was designed to complement, not replace synthetic lore. Positronics were a thing in the lore, so I didn't dare replace it - but if that part is going to go up for review, I'm down with defining more closely what is, isn't, and what can replace a posibrain. Personally I can see it being a brand of processors. AI thing, as I said - complement and expand, not replace. Also, to me, it made sense that way - Nanotrasen is a rather human-centric company, and so even though Skrell are equal, it made sense to make it more focus on human stuff.

http://khzsandbox.wikia.com/wiki/Station-Bound_Synthetic Revised a bit of the history (and expanded upon it - notably, Biesel considers cyborgification legal if properly documented for specific types of criminals) of station-bound, lawed synthetics. It's a rough draft.

http://khzsandbox.wikia.com/wiki/Chemistry I made a short history of Chemistry to try and remove a bit of handwave.

So I made this... Thoughts?

Ribbed on. Teased. Being made fun of. Sybil's a few years old and was made on obsolete hardware. Jennifer was created two generations ago. Even Sybil's development hardware couldn't top that.

How about 'danger volunteering'? Brigged people would be given the offer to do a dangerous task relevant to their expertise (brigged securitycould be offered to deal with capturing advanced threats under supervision, engineers be offered to deal with a breach/blob, so on so on) instead of risking valuable crew on it? And if they succeed, their brig time is greatly reduced, if not eliminated.

So. As I said, it's not like "XYZ voted against him, no antags anymore" it's more of a "the majority of the server voted against them for three consecutive rounds, less antag chance". Though you tackle a good point - ideally there would be admin tools to reset it, and a format of appeal in which people could post in the 'unban requests' or something like that.

Alright, guess that answers it. Thanks!

I remember Edgar. They're pretty decent, and the sheet checks out. I approve. (Sometimes I feel like it's fortunate that I regularly browse the whitelist subforum...)

+1 flawless execution. No seriously - pin this shit for reference. When I think of a species whitelist, I couldn't think of a more glorious example than this. I absolutely LOVE the concept of Jennifer (and she's going to be ribbed on, a LOT, if her project files are open and she's in science, for being an ancient AI) and love how it ties in with the Apollo AI (Which I loved). That, combined with the fact that Elizabeth Solari and Apollo are among the more fleshed-out characters, both lore and personality wise, makes me incapable of doing nothing but giving full approval to this application. Saying that they're not a baldie is a disservice to their capabilities - if they refer to the fact that they don't know all departments, that's fixable. But quality-wise? They're a credit to the server. Can't wait for Sybil to rib on Jennifer.

-1. I've never seen the player in-game, but this attempt at a whitelist... Barely even filled out. A sentence isn't a paragraph, and "I don't have the answer" tells me that you're not ready for this. And "becoming an astronaut" - really? Lore-wise, it's not even astronauts anymore - space travel is as common as taking a plane is today. Also, don't Heads have a 30 year-old age minimum? Hell I don't even know what Head you plan on having them be. Also you can't just put your tag as 'processing' yourself - that's for the moderation team to do.

That's why I suggested that everyone starts at max out - because if the good ones have more chance, it means the new one are negatively impacted by having a lower relative chance. But yeah - otherwise, I suggest maybe making it exponential. One, two, three downvotes have pretty much no effect. Four, five, start having negligible effects - six, seven, eight, nine, ten get worse and worse, to the point of almost never getting it. NOTE: these votes are not called in TOTAL votes - they're binary server votes, so they're in ROUNDS that the majority downvoted. So if a new guy makes a honest mistake (or if butthurt's gonna butt), it won't actually impact their rating, most likely - for someone to get a downvote, they would need to actively piss off the majority of the station by their actions (like the nukeops deathtrain I've heard of a while back). Maybe have a fraction-vote - like 1/3rd or 1/4th for a downvote since not all antags involve all of the station. And the fact that everyone starts at one was also to avoid pressure: the system is not to make good antags better, it's to give the population of the server at large a tool to slowly weed out the shit antags.

This good?

Y'know, I thought of something. What about a weighted randomization? Right now antags are *cough* entirely random (at least as random as the Byond RNG is). But what if, each round, people had the chance to vote 'yay' or 'nay'? 'Nay' would make people drop in ranking - to the point where if they insist to be complete shitlers, they'll rarely if ever come up as antag. 'Yay', on the flipside, fixes 'nays' - it increases the 'probability quota' up to a maximum of 1 (which is what people start with, and the maximum attainable) That way, with this system - shitty antags get voted out of the system, while good antags can go on. And it doesn't discourage new antags because they'll start with the same chances as the best of the best - and if they don't act completely retarded they'll keep getting antags. (Plus, if people actually like being antag, they'll make an effort to improve their game) (Or maybe, to ensure no abuse happens, instead of a vote - an admin/mod has to manually lower the rating if there's too many complaints. It could serve two purposes: for people like Baka who get picked against all odds, it could fix that without being banned from a certain antag - all while keeping the shitty antags happening less often) Thoughts?

LOGIN>Databurst PASSWORD>************ ACCESS LEVEL> OPERATIVE NET ACCESS: Granted Welcome

That's Baystation though. If you say so I'll apply it - but I thought the Aurora was trying to distance itself a bit from Baystation?

And that answers that. Thanks for the info!

Anyone?

I know that reference. But I have twofold problems with this: One, it implies that the RD's pet actually breaks server rules by being a 'real character' Second, if it's a Headcrab and not a xeno facehugger, it implies that there is a non-zero possibility of connection with that world, and there's no lore to back it up. So either we face some cross-dimensional shenanigans or maybe the RD mildly knows about the xenomorphs.

Right, I'll re-package the files to reflect that new deconstruction path tonight. Though I'll need more information on how, exactly, the lock is coded to behave if you want fancy animations. Is it like, you need to place the item and THEN swipe it for it to lock, and the unlocked lock stays on until you grab it? (also speaking of fancy animations, now that I know exactly how the lock is deconstructed, I might just make fancy animations for the whole process )

So. The RD's pet, officially, is Lamarr right? And Lamarr is a declawed xenomorph facehugger. Does that mean that Research Directors should have knowledge of xenomorphs (which IIRC knowledge of should be limited since antag)? How does that work, lore-wise?

YES PLEASE

And it is done. I'm going to need to go over it for sure (because I just sprited it after what I thought was a logical pattern - screwdriver panel off, pulse with multitool, twist handles away, wrench bolts off to release cover, crowbar cover off, wrench bolts of subcover out, cut both support rods off with welder, then cut wire in main circuit to force the pistons to retract, gives a broken item) but it's a start, right?

Already on it - though I just realized, if we don't want power consumption - pneumatics/hydraulics are definitely an option, and those would only need energy to change state - so as long as the valve doesn't break, it will stay on there forever. Also gives a convenient mechanic: if a door lock has been disassembled/broken instead of unlocked, there can be slight overpressure/a massive oil stain to show it.

Ask for transparent and transparent you shall recieve.