Leaderboard

This was something I've brought up a few times one the discord when people mention about how some races should have some more fluffing up to them. Currently how Skrells stand, you can breath underwater and you can't handle your alcohol. I've been thinking that fun thing to add to them is them having the ability to carry small items in their tendrils. So, they can carry things in the back of their heads, mostly likely be something that people wouldn't be able to see when being examined. And on a side note, remove the ability for Skrells to have their "hair" shaved and/or burned off, cause from my understanding that is a part of their fleshy bodies and would probably hurt like a bitch.

Hello! As a new member of both The Cyberiad and Byond itself, I'm certainly finding my way slowly, but man is it confusing. That aside, I'm an avid roleplayer in both chat based format and many other mediums, such as DnD. I look forward to working here with the NanoTrasen associates, and hope my addition of character will be enjoyable to all!

+1 to giving Skrell more variations to set them further apart from other species. "But officer I swear I don't know how the Captain's spare ID got there!"

Snowflaking code actually refers to putting something in that requires hooks and checks from a bunch of unrelated things to make it work. Like the pod code is slightly snowflakey in that it has to have it's own subset in the main damage and AI functions rather than independent ones as an example. In other words, Snowflaking is just another word for poor coding practices that act against OOP, the route that this codebase has decided to fully embrace, and ultimately lead to inconsistency and spaghetti code. That being said, it is commonly used as a cringy catchall for content that requires changes that feel different in game far more than they are in code. In this case, when people say snowflaky, it would be fair to say that it's the feel of it rather than the real details of the implementation. while this is ultimately valid criticism, it's being attributed to the wrong thing and using the wrong term in the wrong context to boot. On a side note, can confirm, learned C++ first, I fully understand that joke. Halp me.

Here's the explanation on the scheduler for those curious.

He's asking for options to have it travel to other Z-Levels rather than the current three it's restricted to.

You can move the white ship. You just need to find the computer board, which is hidden on a certain space station. I'll let you figure that out by yourself.

Felt like writing this, because I remembered a few things when I was doing robotics that made things go smoothly, or just less stressful/wasteful in general. DON'T BORG AN SSD BRAIN. After removing it (but before putting in the MMI), examine it to see if it has a spark of life! If you fuck up and have an SSD Borg on your hands, the only solution is complete deconstruction. ALWAYS HAVE A CYBORG BODY READY TO GO You never know when Security is going to knock on your door and tell you to borg someone, immediately. But don't forget to check if the brain is active first! ONLY ACTIVATE ONE POSIBRAIN AT A TIME. This limits frustration on the part of people who sign up. Which, in tandem with the above mentioned rule, means that you should always have a Posibrain in activation mode next to an empty Cyborg body, if possible. YOU DON'T ALWAYS NEED TO ORDER RIPLEY BOARDS. If R&D is doing their job, you should be able to print them fairly quickly. Additionally, you should only make these on demand if a miner requests one. There are better mining tools. COUNT YOUR RESOURCES BEFORE YOU MAKE THAT MECH. Yea, I know you want to make that Gygax/Durand, but check that you have the Diamonds/Uranium for the entire project. The armor takes a fuckton. You probably don't have enough. You probably shouldn't be making it anyway. DON'T EVEN TRY TO MAKE A PHAZON. It's bugged, it's awful, it's difficult to use and there's a very unique piece that is required to finish it. Don't waste resources on one unless the RD hands you the anomaly core and asks you to build him one. DO NOT PUT MMIs/POSIBRAINS IN MECHS. Yes, I know you can, but you shouldn't. They're unlawed and dealing with door access for them is obnoxious. UPGRADE A MECH'S BATTERY BEFORE IT LEAVES YOUR WORKSHOP. The stock battery for all mechs is 7500 (Thanks davidchan) and that's terrible. Here's how. UNDERSTAND HOW TO REPAIR IPCS. IPCs break. Constantly. Read the guide on how to put them back together. Please. IF A BORG IS EMAGGED, THE ONLY SOLUTION IS TO DECONSTRUCT IT. DO NOT RE-ACTIVATE EMAGGED BORGS. I mean it's hilarious when it happens, but still. THE TEXT "THE INTERFACE APPEARS TO BE DAMAGED" WHEN UNLOCKING A BORG WITH YOUR ID MEANS THE BORG IS EMAGGED/UNLOCKED BY THE AI. You should probably tell someone that your fellow Roboticist or RD is probably traitor. (Note: This may also appear if illegal mods have been legitimately installed through extensive R&D. Use common sense.) GET YOUR METAL AND GLASS WHEREVER YOU CAN. Scour maintenance (If it's safe!) Ask the AI for permission to take materials from EVA! Take them from wherever you can! You can also use a welder on metal rods to turn them into metal sheets. That way even if mining sucks, you can still build borgs instead of having to cryo out of boredom/shame/stress. REMEMBER THIS ORDER FOR BRAIN REMOVAL. Scapel, Hemostat, Retractor, Saw, Retractor, Hemostat. REMEMBER YOUR S.O.P.: Get paperwork for Cyborgification. (Signed by the victim subject, stamped by HoP or Captain, AND GET THEIR ID TERMINATED) Do not make un-approved Mechs. Remember Anesthetic for your patients. (Tell them to drag their old body to the morgue afterwards, too) DO NOT MAKE A HONK with tracking beacons. Give it a charged slime core and a mounted teleporter. Nothing bad will happen I swear. Without the expressed permission of both the Captain AND the RD