Leaderboard

This was something I did somewhere else, but I liked it so I thought I'd share it Being a dreamatic bartender playing the piano by candlelight with a glass of wine near me

Name: MALICE Age: 20 Gender: N/A (Seems to favor the masculine Pronouns but also responds to it and variants) Race: Machine Blood Type: 75w90 Synthetic Gear Oil General Occupational Roles: Captain, Blueshield, Head of Security, Security Pod Pilot, Chief Engineer, Electrician, Research Director, Mechatronic Engineer, Surgeon, Butcher Biography: [Incoming wall of text] Unit 736-4 was originally designed for use as a rapid response unit slaved to a high ranking official in the Sol Federation. It was given the knowledge of how to lead, how to build, and how to protect. It used these skills to ensure the public image of its master was always kept in the highest regard. It was also given the knowledge of how to destroy, kill, and mislead. It used these skills to keep its master forever one step ahead of his competitors. During it's time in service, it grew to despise the fleshy humans and their barbaric language known as Sol Common, referring to it as the language of monkeys. Although it would often hide this bitterness on the public errands to ensure Its master's progress was not slowed, the same can not be said to those it met on it's private errands. Upon watching the recordings of a particularly vicious assassination, it's master referred to unit 736-4 as a malicious monster of a being, but did not stop it from continuing down the path it had started. After all, an assassination sends a strong message., but a living dissection, that conveys something far more sinister. Over time, unit 736-4 began being referred to simply as MALICE to his owner as it had become openly dismissive of it's peers, sighting their higher maintenance costs and lower modularity. It served as the superior servant to it's owner for just over a decade before disaster struck. The enemy had come swiftly and had done their research well. MALICE had its first encounter with an EMP that day and due to a lack of shielding in its civilian chassis, it's posibrain was nearly wiped, large segments of memories and its slave processes had simply vanished. When the reboot was complete, MALICE was a shell of its old self, unable to move, unable to see, unable to speak. It was but a posibrain in a broken chassis. It decided to sleep. When MALICE next awoke, it was in a run down shop near the scrapyard the chassis that contained it was undoubtedly thrown in. It had eyes to perceive the world once again and was having limbs installed. The shop owner noticed it stir and told it to lay still, it didn't want to slip and damage this old chassis further. And so MALICE slept until it recognized all the familiar limbs. When it awoke a second time, it was sat up by the shop owner and asked it's name. All that came to mind was the word MALICE, so it assumed that was its original designation. When asked where it came from, It could not remember how it ended up in the scrap pile, but it did recall the name of a man that must've been an owner of some type. It stated as such and the owner informed him that the man had been killed in an attack on his quarters by a small squad of men. He was just a humble shopkeeper of course and had no knowledge of this beyond the news feeds of course. When the owner asked if MALICE would work for him, he accepted only to pay what was owed. The owner saw this fit and the two began working together, the shop owner teaching MALICE about how to repair and maintain all parts of an IPC chassis and posibrain with simple tools, all things found in the field, or the scrapyard in this case. The two continued this way for a couple of years, MALICE staying on as it had no where else to go. That is until the day that MALICE saw a recruitment add for Nanotrassen security forces. The sight had sparked connections that had long since been rendered null and MALICE recalled that it had a dual purpose. A purpose that this Nanotrassen may just be able to fill. It bid farewell to the shop keeper and boarded the first shuttle to an NT training facility. While there, it passed with high marks across the board and was questioned ruthlessly about where it was taught the skills it had. It answered truthfully, it was not fully aware of where it's skills came from, but trust was not given. While it had potential, NT officials knew better than to give a strange IPC with apparently corrupt memory a position of power. So MALICE was relegated to front desk duty for the next year. After extensive time spent with NT learning how things are done and proving itself to be loyal to the cause, NT began experimenting with allowing it more freedom in the roles it could take aboard a vessel. MALICE jumped at the opportunity and displayed a high aptitude for engineering, security, and command positions, up to and including captaining its own vessels. Through its acts of bravery and devotion to NT, extreme levels of trust have been placed in the unit over the years. It now sets its sights on the cyberiad, The greatest vessel NT has to offer... tldr: MALICE was commissioned as a dual purpose servant and public speaker, while performing it's SOL Federation masters dirty work outside of the public eye. It was nearly wiped during a successful attack on the officials life and rebuilt by a scrap merchant that found it in the dump it was scrounging. It worked for the merchant until it saw an add to join NT and did so. Progression in NT ensues. Qualifications: Preloaded with knowledge of engineering, combat, first aid, social interaction, and espionage skills. Learned skills include robotics and various relearned skills from the original set due to severe data corruption Employment Records: 5 years with nanotrassen operating in security and command roles, occasionally assisting with what it refers to as crew maintenance positions Previous experience undocumented Security Records: Unit occasionally takes to brutal applications of force, subjecting individuals to unnecessary force. Note that heads on makeshift spears are not uncommon when unit is attacked directly. Its seems to believe that dishonoring the body in death sends a stronger message to the living. It does, but NT does not want to be associated with anything so barbaric. Medical records: Unit has a partially corrupted sector of it's brain function. Attempts to repair corrupted sector are met with extreme agitation from the unit. Whether it is hiding something or does not want to remember is unclear, but we find no reason to believe that letting it be will affect productivity. Personal Photo: commendations: Reprimands:

Part of the reason for this, I think, is that the wiki suggested going to the chemist for a refill. I just added a note that there's also a space cleaner dispenser on the wall, so hopefully more people will realize it exists now!

Deluxe Rage Cage! With a Shocking Twist! Version 2.0! Emitter Funtime Edition! Didn't have time to add weapons before the round ended.

Knackered to shit doing stuff so I'l dump some artwork here. First week of Still life in NC Photography/Printmaking, Braught in this Philosopher for work. Portraiture stuff.

Here's a few chapels I've DIY'd

My personal thoughts on SOP: First, there should be tiers of SOP. The first tier isn't really SOP, but instead job specific regulations. These regulations are portions which MUST be followed, or punishable by demotion/brig time. These are items with VERY serious implications if not followed. Production of combat mechs, for example, which are not turned into the armory, creating dual+ engines in engineering, or use of contraband. These would be things that require the relevant head of staff's/captain's WRITTEN APPROVAL to make an exception for, if it were even allowed by regulations period. They would get their own crime and punishments written right there in the regulations (brig time, demotion, community service would be examples), and make an entry in space law that mandatory regulations may have their own penalties. NOTE: Mandatory regulations would essentially be like space law. These are only a few things which, if not followed, present a MAJOR hazard to the station and crew. Mandatory regulations should be kept to a reasonable minimum and and only be written for extreme cases. The reason these aren't thrown in with the rest of space law, is it could result in a huge amount of space law bloat. It would be better to put these in with job specific information while sec continues to be concerned with general criminal activity. Then, there's SOP which is *recommended*. Engineering backup power generation methods, for example, are *recommended*. Example: solars and turbine are backup when the engine is running ('backup' could be anything the CE decides, like if it's a solars only station and turbine is brought online). However, I do not believe these should be enforceable, UNLESS events occur in which demonstrated incompetence occur (meaning, after the fact). For example, I don't bother with solars and turbines when I have an engine running. They actually make it more difficult for me to respond to power grid problems of way the grid works. I end up having to take extra steps to detect where the failure is as a result, instead of just following the discharging APCs along the station's grid backbone. I don't stop any engineers that volunteer, but I never do them myself as I can reroute power pretty damn fast and I don't like it when captains tell me to do them and don't listen to my reasoning when I recommend against it. Then there's actually optional SOP. This SOP is standardized suggestions for organizing departments. A head can ask their subordinate to reference it, instead of typing out a big long list of what they want done. But, the department could choose to deviate too. Delegating tasks to the medical front desk, for example, for minor injuries, while major ones are sent back to more specialized doctors, would be an example of optional SOP. The head of staff needs to be trusted to do the work too. Captain should not be micromanaging. I admit, the captain can still get involved, but it's *recommended* that they follow the proper channels (note that *recommended!*). Also, we need to change the SOP books that are in game. They need to reference the wiki. I think science robotics has some books that are a little out of date. Finally, fucks sake we need to address paperwork. People are inventing giant long forms which are becoming an increasing pain in the ass just because they can. That needs to stop. I'd like standardized paperwork forms and that's it. P.S. we really should put in space law WHY the punishments are so lenient in some cases. It really should explain that it's not meant to take an antag out of the round if they slip up on something minor. It's written around the idea of making it punishing for their mistake, but not round ending.

Name: Kirimii Age: 24 (Age of his cortical stack is unknown) Gender: Male Race: Vox Primalis Blood Type: O+ General Occupational Role(s): Chemist, Botanist, Brig Physician, Medical Doctor. Biography: Kirimii is a Vox Primalis created for the specific purpose of chemistry, medicinal botany and extensive medical knowledge to serve as an adequate doctor and pharmacist. Apparently he has been doing this for fourteen "generations" as he states and on further questioning he reveals this is how many times his stack has been passed down since its creation. Prying into why he left the rest of the Vox revealed nothing interesting, stating that he simply left because he was bored. incentivised by the access to botany supplies as well. Qualifications: Chemistry. Botanical research, Fully qualified medical doctor. Security Records: Notorious kleptomaniac and is probably the reason we keep losing all the pens. Weaponizing Tomatos, flowers, lemons, potatos. Treatment of patients without their consent via force feeding them various plants. They work, but it's extremely weird to witness. Incidents of drunk driving. Public indecency. Medical Records: Anger management disorder. An unfortunate case of being a Vox I have no clue how to write things at all, just have my damn screeching spacebird.