Skull132

I want to add, if this persists, namely the dereliction of head of staff RP during situations where a Head of Staff is required (such as during code Blue), then the whitelist can be removed. For chairRP, chosing a non-vital role is recommended.

I did, and I figured out how. It was weird.

http://puu.sh/l30uA/a23a0e55d6.png Almost done. Just one more bug, and then waiting on the sprites!

Jack, be careful. Using holodeck mechanics directly won't be a good idea: it'll break any machinery there, and the items can also act funky. Though, as long as you use New() procs, that problem should be remedied.

Displaying the date would also be right.

I'd suggest expending the office/surgery room area a little, perhaps on the count of the mechbay. It's really tight in there, specially with all of the surgery tools. And yes, medical laptop would be nice.

And people are free to gawk at all of my beautiful failures that I've made over the past one and a half years while here. There is a line I draw here, and that you saw enforced. Personal, real life information is something we outright scrub and delete. But online personas we consider disposable. You make the conscious decision of playing here as Sadistic (Nightmare), thus, you make the conscious decision of being recognized as Sadistic (Nightmare), if that makes sense. Though, if you feel like continuing this debate, fetch me via pager or PMs or something, as I'm archiving this thread until further notice. Plus, look at it this way: if they do look, and only see one ban appeal, as opposed to two, it is more reasonable that they assume you weren't banned again. As such, it is easy to assume that you didn't repeat the offence, and held onto the deal. Ban lifted.

You won't have to deal with them: their posts will be removed. As they have been already. And if they persist, further action will be taken. Beyond that, though. I read over the OOC logs that sparked the pagerPM, and I'm just slightly "Blaaa?" about it all. Basically, an OOC spat should under no circumstance escalate into an ambiguous as hell message, namely, one that can potentially be perceived as a threat, being sent to one party over a more private means of communication. If you can agree to not repeat it [the pulling people aside and sending them ambiguous messages that can be perceived as threats], then we'll be fine, and I'll lift the ban. Otherwise, going around and pagering people with, "You know, you've got a bigger digital footprint than I, maybe you should work on it?" will pretty much net you a ban for continued harassment. At least from this establishment. Sound reasonable enough?

I need to look into this being doable. It's not as easy as my things with with the heart were. Also, I am basically done with all of the concepts outlined in the original post. I just need to test it and get sprites. But since I have work for 2 days, that'll come towards the end of this week. Hopefully, though, around next week, we can have it in and working. EDIT: Update here: http://puu.sh/kZSyG/e1760521a6.png I have a few runtime errors and a few major functionality error to sift through, but otherwise, this is pretty good for a first run scenario. Also, if anyone knows how to make it possible for me to transfer liquids from a beaker into this machine, plz, let me know. Cause that's a pain atm.

I suppose I didn't clarify. You need to buckle people into the lifesupport enabled operating table. Surgical beds remain unaltered in their functionality.

http://aurorastation.org/forums/viewtopic.php?f=64&t=4035 There.

This can already be accomplished. You need to buckle the patient in anyways, and the patient themselves cannot unbuckle themselves. So, yeah. And as for infections, because it freezes the processing of most organs, they will not spread as rapidly. Further more, since you can have a transfusing process active within the machine, you can simply mix the blood to be transfused with spaceacillin, and voila: you have a constant spaceacillin/IV drip thing going on. Just need to get creative with how you use what you have available. Also, this shit is turning out the quite fun to code: http://puu.sh/kZvNU/2926dd5f0d.png Also, I'm of mind of not adding this. The table is already a straight up upgrade, but I'd rather it add new options, rather than make the other machines in the medical bay obsolete. You still get your standard info from the surgery computer. EDIT: Still need a spriter!

If I'm going to do that, I'll be awful about it, and force you to set the duration of the steps. If you get the duration wrong, they'll fuck up. But, anyways, that's later. Discuss present concept now, plz and thank you.

Maybe a later iteration? Too complex for initial introduction, IMHO.

Luna should probably added? I dunno if it has any cities, though.

https://github.com/Aurorastation/Aurora/pull/757 Here we are. Hopefully in the game soon. Hokay, so as a bit of a narrative, I wanted to code something cool. So I did! http://puu.sh/kZjYl/e582009f22.png The basic, core idea of what it does is this: Enable the removal of vital organs, such as the heart, so that they can be replaced. Make organ transplant surgeries easier, by freezing the processing procs of different internal organs. All this at the cost of requiring cryogenic fluid and power, constantly. But that seems kind of. Underwhelming. Doesn't it? So, here are some more things it could possibly do, that I'm debating on enabling: Built-in anesthesia (you have to insert the tank, adjust pressure, and so forth, though). Built-in blood transfusion mechanism (you can toggle it to automatically control the patient's bloodlevel, or use a manual switch; again, you need to make sure it's properly stocked, though). Also, this update will make both the normal surgery table and the advanced one constructable. You'll need RnD to make the latter, though (with medical level 4, and data 3, and possibly slightly more). SO, thoughts and ideas, plz? EDIT: Also, spriter needed to make a sprite for it, and the maintenance state of the normal table. Plz contact.

https://github.com/Aurorastation/Aurora/pull/753 Done and done, I'll pester him to have it run snap-ish.

...This is actually an awful oversight on my part... I'll get it fixed rickytick and see if Scopes can run a hotfix right quick.

Gonna get to this tomorrow, weee~ Although, I would like to see if Tainavaa has anything else to say on the matter before I move in?

I'd argue that people using tactics (two marksmen) is a positive. Also, if we just make it a one-shot-disable, then there's no point in removing the stun...

Cargo has like a stack of points gathered up almost every round, though? So that wouldn't really solve the issue. Also, to FFrances, I'd argue that stun is alot more powerful than lethals (specially that 2-hit-always taser). And has always been, purely because stun mechanics have more immediate effect.

I'd say that they're pretty much lethal enough? Like, if we keep the the stun effect they have, and just remove their ability to keep you in stun, they're still pretty fucking lethal if you don't longwolf, and actually use it with the help of others. (Namely, use the LWAP to initiate an assault.) As for the flushing, I wonder if that would actually make it even more difficult to use one, as you need to unscope, flush, rescope and re-acquire a target.

So, very simple idea. As it stands, a single sniper can pin a man, and keep him down (while firing at him) until they die, or are captured. This is called a stunlock. Stunlocks are very powerful. Snipers in and of themselves are already very powerful. So here's my proposal: simply extend the fire-delay between the shots, thus removing their ability to stunlock you and giving the target time to find some cover. Alternatively, lower the duration of the stunning effect. But basically, a weapon this powerful should not be able to stunlock, in my opinion. Stun? Yes, fine. Deliver high doses of damage? Yes, fine. Lock you on the ground, while delivering that high dose of damage and stunning you? No plz. EDIT: It would also make the sniper rifle a little less wide-usage, too. Basically, it would bring it closer to an actual, offensive weapon of assassination, rather than an all-purpose answer and a method for crowd-control on top of that. Plus, the ability to start off a charge with a sniper shot would remain unhindered, so you still have tactics to play around with. Thoughts?

Writing the code for the horsehead removal spell right meow. Done and waiting for Scope's pull.

And this is fine. In fact, if this happens, it'll be good for roleplay, as then the identity of the species is enforced through interact, and npt arbitrary mechanics.