Feorn

Your first step is to pick up the Dream Maker software(probably already installed, just use the little gear on the beyond pager or look around your BYOND directory) . This is an IDE, it also contains the software used to make the sprites, animated or otherwise. As for the language, it seems to be a proprietary language, but it'll be familiar if you've ever worked with Java, c++ or any thing else object oriented really. The sprites are all 32x32, no idea what the frame limit is for animated sprites. As far as I know, Dream Maker will only let you use the .dmi format for sprites. Then, pull down the latest Aurora from github here: https://github.com/Aurorastation/Aurora.3 It'll take a little fiddling and reading to figure out how to get compiling and running to work correctly, I honestly can't remember what I had to do at this point, I'm sure one of the coders would know precisely.

I also can't seem to figure out where the unread post indicator is when I open a thread. On the old forums (and most forums I browse) there's a little folder icon or something that'll be a bright colour if I haven't read the post and greyed out if I have.

Yes please. But add another section to the third update. Misc. Loan/credit payments. Since a good portion of our characters went to university/med school etc. We should have an option to include that.

These were needed back in the day when emergency shutters didn't flash, and didn't require engineering access when conditions are unsafe on the other side. My very first round way back on Apollo years ago this message saved me. Doesn't seem like it would be needed to save new players these days. Since those changes, they're probably more annoying than anything else.

pAI are also currently available as a custom loadout option. I spawn in with them on a few of my characters.

Nah, you were right, the new nano UI version of the pAI software interface doesn't have it. I haven't played pAI since newcode.

I would endorse the majority of these improvements, except the guardian module and manipulator module. Having pAI work as more of a station AI lite would be fun. The camera module would require a lot of camera network renaming I think, as last I checked, only engineering, sec and supply have their own network names on cameras. Could be wrong there. I would expand the door opening module to include the same shift+click function to remotely open doors that the AI and cyborgs have, but keep the master ID access requirement. No bolting/electrifying/full door interface like borgs and AI have, just the shift+click to open. As for the medical analysis suite, it does work, the option is under the Host Bioscan function. But I agree, it should be extended to allow scans on adjacent players.. The guardian and manipulator modules run contrary to what I feel like the idea of a pAI is. A small computer with a wireless interface. Although, I'm one of those who wouldn't have given them an unfoldable chassis either.

Hey, so, uh, I've been playing a synthetic named JOI for like the past year or so on Aurora (And longer on Apollo) and recently a new player has made me aware that the name JOI is also the name of a very obscure genre of pornography. A quick google search confirms this. I'm not really sure this is the right place to post this either, but I would just like to say that I apologize if this broke the rules, and I definitely didn't intend it. I'll just go ahead and change the name to JOIE (french for 'joy'), unless anyone has any objections. Once again, just a super obscure reference that I was completely unaware of. So, next time I might just go ahead and google every character name I ever make before I start playing it. And if some of you out there knew the whole time and were snickering quietly well, uh, thanks for not telling me at all jerks. Once again, just super sorry.

The suggestion is so that people with these specific custom job titles show up on the secHUD/AI SecHUD, otherwise we need to examine them to get their job title.

In my opinion this is something similar to the two OR thing. Make the map so that it is almost redundant but requires some effort to get there. They've already said they're putting in the power substations, which provide local backup power for nearly thirty minutes or more. More than long enough to repair breaks if you have a midway competent engineer.

I know you're fairly new around here, but Aurora got by just fine for a long time with only one operating room. If you're talking about game balance, an antag murdering someone often gets them back in the game faster. You can clone someone faster than you can perform surgery on them. If an antag really wants to take someone out of a round permanently they can. One OR makes teamwork more important for the medbay. You have one doctor/nurse run the scans and prep the patients and another cutting them up and it'll go nice and quick. In addition, other than bones/internal bleeding/appendicitis/missing limbs everything is faster to treat with chemistry anyway. Something to keep in mind with the new map is that vacuum injuries (ex. Ruptured lungs) might end up being a lot less common. As far as I understand the map is an asteroid map, and when people blow holes in the station, it might not lead to hard vacuum right under the floor tiles.

We already have a job title with officer in it that is completely not whitelisted: Security Officer.

What about just plain ole' Medical Officer? It denotes seniority over regular MDs while showing that they are below the Chief Medical Officer. Yeah, that's better than mine.

I also like this idea, but not Senior Medical Officer. It doesn't sound below Chief Medical Officer by enough. Head Physician maybe?

Has played slaved to JOI a few times. Good character. Good fun. Good app. +1 Haven't had a negative experience with Fluffybirb yet.

I like that idea Nikov, as long as there is a bunch of humorous banter between the surgeons while they operate. Also if I can name my character Hawkeye, BJ, Hot Lips, Frank Burns, or Charles Winchester. Oh and rename medbay to the 4077th.

Triage is a part of medicine. The CMO, or surgeon should have to make decisions about who to treat. How is it not ethical to stop surgery on a bone fracture to save a life? Life over limb is another concept key to modern medicine. A small hospital serving a town of ten-thousand might only have one or two operating rooms, a space station with less than a hundred crew? Ludicrous to have more than one. Sure, I'd love to have a huge 5 dispenser well stocked chemistry lab, three ORs, five cryo tubes, two odysseus and twenty medibots patrolling the hallways. There are three kinds of patients: Those who are likely to live, regardless of what care they receive; Those who are likely to die, regardless of what care they receive; Those for whom immediate care might make a positive difference in outcome. Patients that have a condition that can wait, should need to be bumped aside for critical patients. There are tons of surgeries that can be put off. Bone fractures, amputations, limb re-attachments, brain damage, various organ damage, and on. Organ, brain and eye damage all have alternative treatments if the OR is occupied. Peridaxon is a thing, as is Imidazoline, and Alkysine. There are some that are kinda critical like appendicitis, internal bleeding (not sure if the baycode overdose bicaridine works on aurora, haven't had a chance to test it), or xeno chest bursters. If you're really super hard up and your patient is about to die, there are a few options. Ghetto table surgery, or stasis bags being two of them. Really though, there are only those three surgeries I can think of that are super time critical, and internal bleeding might even be treatable without it, chest bursters are super rare, and appendicitis takes a long time to become critical. If someone ignores all the pain messages long enough to die from appendicitis, they kinda deserve it.

If some events are removed, I would request that the one that makes APCs turn malf blue stays in. Helps kill meta. I mean, engineers know because they're locked out of malf APCs and not damaged ones, but everyone else doesn't.

That is fantastic news. It means that engineers can set up one engine to power the station and run fun little projects on the other. I've wanted to try to refit the supermatter engine as a plasma combustion engine a few times, but didn't want to cut the station's power to do it.

Our (Baycode) map has it currently, it was added in sometime in the last couple weeks. It was even in the changelog. Telecomms scripting itself is disabled, however. Me and Skull tried to get it to work the other day and it wouldn't. I just pulled down the latest Aurora build locally and got it running to test it out and I got it working fairly quick. I just had to set the network on the scripting machine and I didn't seem to be able to edit $source. But I was able to mute someone, change colours, add job riders, and filter profanity. I'll try it on live next time I get AI. It doesn't have the newest baycode ability to make absurdly long scripts, but that's probably a good thing. Edit: Can't update the network on the traffic control console as the AI, have to have someone in front of the console I assume. Final edit: Due to the intervention of a friendly bluespace tech (Thanks Garn or Itzal), I can confirm it does work on live. Just make the round start console default to the "tcommsat" network to let the AI have access.

Central Command will not respond during the mutiny game mode. Fair enough, but is my AI told that sending the message is futile? I mean IC wise? The rest of my statement stands. Keep following orders until they conflict with your other laws. If the heads order you not to follow orders from certain people, you don't.

scripting? This is gonna need more explanation Super off topic, but here you go: Maybe we can do another IC learning session. But the short of it is that all the text sent through radios is processed by all the machinery on the telecomms server. You can write scripts with the scripting console on the satellite to do tons of things to the transmissions. Mute all messages from a certain source. Change words to other words. ex. AI IS MALF to The station artificial intelligence is an amazing piece of technology. Change the colours of messages. Add a little pre or post message to any radio communication that prints out the job of the ID the person is wearing. It's a full scripting language with conditionals and variables and whatnot, so it is really flexible. if ($source == "JOI") { $source = "<span style='color:#e55ea2'>JOI</span>"; $content = "<font color=#e55ea2>" + $content + "</font>"; } $content = $content + "<font color=#193a7a> ("+ $job + ")</font>"; $content = replace($content, "fuck", "f***"); $content = replace($content, "shitcurity", "Security, the most friendly and competent department on the station"); $content = replace($content, "cunt", "c***"); $content = replace($content, "bitch", "b****"); $content = replace($content, "shit", "s***"); $content = replace($content, "asshole", "a**hole"); $content = replace($content, "catbeast", "Tajaran(automatic slur filtering)"); $content = replace($content, "ligger", "Unathi(automatic slur filtering)"); Sorry for the vulgarity, but this is a little script I often ran as JOI. Would make anything JOI said pink, and add a little rider to any radio transmission with someone's ID, and filter a few things out.

Our (Baycode) map has it currently, it was added in sometime in the last couple weeks. It was even in the changelog.

The AI has a verb to send a quantum entanglement message to CC. When I play AI, if I suspect that heads of staff might cause harm to themselves/the crew/the station/the stationbound synths, I'll send off a message detailing the situation. I generally don't start disobeying orders unless they directly conflict with two other laws, or obeying an order from someone would directly cause a higher ranked crew member to be harmed.

The three favorite methods. Electrifying doors. Alt-click a door, make sure there's a good amount of power in the power grid. It ranges from mild burns, to a few seconds of stun. Burns can get infected and kill someone eventually. Overriding door safeties and crushing someone in a door. Click a door, make sure the safeties are overridden. Close a door when someone is in it. Very deadly, if you get someone caught in this, you can kill them with a few open/close cycles. Put a gas into the station's atmosphere. Not going to detail the steps for this one, as ninety-nine times out of a hundred you'll get in trouble for it. Ranges from knocking someone out to burning them to death in a terrible plasma fire. When you're subverted or malf or whatever, killing telecomms points a lot of suspicion your way. If someone you're going to kill is isolated, you can use scripting to mute them on radios.