tbear13

I spoke with Cake about reprogramming IPCs a little while ago. According to him, IPC reprogramming isn't especially expensive, or difficult. It's just like any other AI.

Glad to hear I could clear up your concerns. Thanks for putting your trust in me!

BYOND Key: Tbear13 Character Names: Tyler White, Mark Sulyard, (Formerly) Vakaris Dvorak, Jake Houser Species you are applying to play: IPC What color do you plan on making your first alien character (Dionaea & IPCs exempt): N/A Have you read our lore section's page on this species?: Yep. Please provide well articulated answers to the following questions in a paragraph format. One paragraph minimum per question Why do you wish to play this specific race: I'll be honest, I only recently became interested in playing IPCs. I was considering making an application to play Unathi or Skrell, when I had an idea for an IPC character, which I'll get to in a bit. Once I looked at IPC lore, I found that it was much more interesting than I previously thought. Mechanically, they look fun as well. No raisin induced heart failure, being tougher save for a single, major weakness, that kinda stuff. Identify what makes role-playing this species different than role-playing a Human: The biggest thing is, well, they're robots, anything they "feel" is fake, an attempt at emulating real emotion. They rely on logic, rather than feeling to make decisions, even basic ones. They have no set culture, no set way of talking, it all depends on what they were made for. They're considered tools by many people and are often treated as expendable. Character Name: Devi Please provide a short backstory for this character, approximately 2 paragraphs Devi is a baseline IPC created by Hephaestus Industries, made to be a simple, relatively cheap security IPC. After being made and checked for issues, it was sold to an amateur roboticist, who lived in Mendell City, as a general servant. However, this roboticist wasn't quite as innocent, or inexperienced, as it would seem. He worked for a small, extremist wing of the Equal Rights Union, calling itself the Synthetic Independency Caucus, which believes that equal rights for synthetics need to be won by force. Over the next month, this roboticist reprogrammed the IPC, mostly editing utilon values, making Devi enjoy activities like socializing, if only to find potential supporters for the SIC, acquiring materials and funds for the movement, and making him afraid of getting caught or leaking information. So, the plan for him was to work on a Nanotrasen station, find supporters where he could, and get funds or materials when possible. After it was programmed, the roboticist made sure everything was working, gave Devi the information of the contact he's supposed to deliver the materials, credits, and information about potential supporters to, and sold him off to Nanotrasen. What do you like about this character? He has more depth than most IPCs I've seen. He has something to hide from everyone, but at the same time tries to socialize and find new supporters. How would you rate your role-playing ability? I'd give myself a 7.5 out of 10, I can roleplay pretty well, but my characters, in my opinion, lack the kind of quirks that make a character really interesting. That's something I've been trying to fix, it's definitely getting better. Notes:

You're welcome to edit the application once it's posted, it's encouraged.

Gonna -1 this. You need to have a real character with a set backstory, and to stop jobhopping before I can support your application.

Not gonna +1/-1 this yet, I've never seen you ingame, so.. I like the way you answered a lot of the questions. My only big concern is the backstory, I don't like that she, a self-taught person with no real training and very little experience, was able to work as the sole engineer of a ship without any problems. That's kinda unbelievable, y'know? Other than that though, the application looks pretty good.

I would absolutely love if this was implemented. As for the targeting, what if it was a button near the throw button? Toggle the target selecting button of selection on and click someone like you're throwing at them, and it targets them.

It was in character for me to not inherantly trust the abilities of the officers in this situation, partly because the character is new to the station and is unfamiliar with the crew and their capabilities, and because taking down phazing mech is absolutely not something most officers are probably trained for. It seems kinda silly to ignore your department because you're new, doesn't it? Is any character realistically trained to stop a phazon? That seems awfully specific for a corporate security team. I don't think either of those are great reasons to ignore your duties as a HoS. I did inform Security, as soon as I realised the Phazon was stolen and on the loose. I still hadn't decided how best to deal with it at that point, but I absolutely did inform the department that the mech was missing. Yeah, you're right about that. You did inform the department that a mech was missing, though I had no idea what a Phazon was before this. Next time, maybe be a little more specific? From an OOC and IC standpoint, not everyone immediately thinks "Combat mech!" when they hear someone yell "Phazon got stolen!" I called for the engineers on the common channel. You should have seen it, but may have missed it and that's fine. But if you say I did not request engineering, I have to correct you. I did. But I was waiting for them to actually arrive before I started vocally planning and ordering a breach through the back path. It would be much better to begin planning before the, well, plan takes place. You should inform security of your plan, and keep them up to date on it. A plan is no good unless the people involved know the plan. It's not 'trust issues', it's 'newly transferred to the station and wtf these guys are not trained for this'. The first time we saw it in Robotics, people were trying to talk to Maline to persuade her into getting out of the mech and handing it over. I was more than happy to let that occur, and did not want to just 'no rp rush' them with ions because that is exceptionally shitty. I always sandbag for antags and give them every opportunity to stop, surrender and turn themselves in; sometimes that just gives them chance to kill me, and that's fine. I can take that. But I always make the effort. I was still roleplaying through the situation despite how frustrating a phazing mech, and wanted to talk to the antag. Weird I know, right? As for informing about its weapons, I can;t remember at exactly what point I was able to see it's weapons, but I'm fairly sure it had... the laser cannon, ion cannon, incindiary rifle and something else. If I can examine the mech, you can too. Again, being new doesn't warrant ignoring the department, but anyway.. When you arrived in robotics, we were trying to talk with Maline, however, we weren't even sure if it was manned at that point. Me and the treeboi-cadet had been there for around two minutes and we hadn't seen or heard anything to indicate that it was manned. We were thinking that it may have been ditched, or recaptured somehow. We weren't expecting to receive an update if it was recaptured, and we were operating based on what little we knew. Except from my perspective, I protected my department by not ordering them to try and stop a heavily armed, high mobility killing machine, when there was one weapon that could threaten the mech and I happened to have it. That would be like ordering cadets to bumrush mercenaries, armed with only foam swords, and I wasn't going to order them to their deaths. Could I have handled the situation better? Yes and no. Yes, I could have spent more energy on giving the department some orders, that I will concede, and yes I could have gone to cargo to order more ions. I will try to keep that in mind for the future. That option aside, there wasn't really much more I could do, because the nature of the 'event' was initially 'there is something in the Vault that you are absolutely not to look at, investigate or touch at all, in any way, shape or form', and in general everyone was pretty much on the same level regarding information. Once the mech was loose, I had as much information as the officers did, and I passed it on. I did not know more than the rest of Security. Maybe I didn't take a minute to stop, pause, and make sure everyone was on the same page, but you were told about the mech before your first physical encounter at the Captains office. This is evidenced here, in your own words. You admit I informed you about the mech. You admit I authorised the Warden to hand out weapons. I didn't tell you where to go, because I did not know. You didn't endanger security by ordering them to charge the mech, that is correct. However, the security department being kept out of the loop and uncoordinated put security's personnel, and the rest of the crew, in danger. You had more options than ordering us to "go unga dunga the mech" and not giving orders or direction at all. As a HoS, it's your job to keep your department safe and coordinated. You didn't do either that round. As for not knowing where to send us, that's your job. If you don't know, take a minute to go over sensitive locations, areas with lots of crew, things like that, and figure out where to send security. You don't stop doing your job because you're not certain of where the antag is headed. You seemed to do better that round, for sure. I was zipping around between security, and they seemed pretty well organized.

The situation you and me were going into, didn't even require the rifle that you were sent to get. As far as I was aware, we were going to go into the Vault, grab the mech, and walk it to Cargo. The Captain insisted you come, and come armed, but we didn't expect anyone to be down there. Okay, that makes sense. It still would've been nice for you to let me know what was going on, but you also ignored my second point. You shouldn't be going around doing stuff yourself because of "trust issues" if you can't manage your department at the same time. One of your main points of contension here seems to be that I didn't tell you about the mech in the first place. But if you recall, the initial Centcom message said it wasn't to be inspected, touched or even protected. Not to be interacted with at all, basically. I wasn't sure what I could tell you about it because WE weren't told anything about it as far as I knew (the Captain may have later gotten a fax for confirmation because the first announcement was super vague), I only knew what the announcement was about because I just happened to glance at the Vault cams and saw the mech before the announcement. I didn't feel like you needed to know much about the Mech that we weren't supposed to interact with at all, and was already locked safely in the Vault; like how the Captain knows there's a nuke on station, but doesn't tell anybody. I thought we were all supposed to be ignorant. Right, I can't blame you for not telling us what it was before it was stolen. However, once it was stolen, you endangered the rest of security by not giving them a "There's a heavily armed mech on the loose, don't poke it!" The "you didn't need to know" excuse doesn't really hold up when you consider the fact that we were actively trying to stop the mech. That's like telling an engineer to go fix a breach without telling him where the breach is. You saw the mech in robotics, fully strapped up with lethal weapons, AFTER recieving two Centcom updates about it, and having seen it phase into the Captains office. I told you that mech had been stolen from the Vault. You saw the pilot use it to commit multiple high severity crimes. And all you can say is 'that's not exactly suspicious'? Were you paying any attention at all? Do you have the capacity to draw your own conclusions? One of the reasons I didn't give you all specific orders to hunt the mech, was because it was so heavily armed. If you tried to stop it, you would have been killed. I had the AI trying to discretely provide information. Could I have given somebody else the ion rifle and sent them after it? Sure. But I don't recall recognising any of the characters as trustworthy security mains from an OOC standpoint, and ICly the character is new to the station and doesn't know the capabilities of the people he's commanding. And if that ion rifle was lost then we were going to have been at the mechs total mercy, unable to stop it at all - that's the reason I rushed to get it in the first place; because I assumed the phasing mech would prioritise getting the only weapon that can threaten it, out of our hands. I called for engineers over the common communication channel, that you all have access to and see. Why would I request help over common, and then need to explain to you over security comms that I was requesting help over common to you? Had I seen engineers follow my request, I was planning to co-ordinate a breach of the back of the maintenance area to get Maline from that side, while I kept them busy in robotics. I didn't see any engineers turn up, so it wasn't a tactical option I wanted to talk about. Okay, like I said, a stationary mech that's been sitting there for around two minutes doesn't make me think "Better shoot that thing!" It was stationary and appeared unmanned. Backup was called, which you responded to as well. If it was so obviously a manned, hostile mech, why didn't you ion it then? Why didn't you inform anyone that it was heavily armed? We hadn't been aware of the fact that it had guns mounted on it until we got a close look in robotics. Why play a character with such severe trust issues that he considers his department more of a nuisance, it seems like you felt that way, rather than coworkers? I hadn't seem the engineering request over common, I was probably just a bit zoned out. My bad there! One does not tell the admins to wait, when they have an issue. Overall, this was an unusual round due to the semi-secret nature of the mech delivery, the fact that I discovered it accidentally and that we were told in no uncertain terms that we were not to do anything at all to or around it, until we were then later ordered to move it. I could have sat you all down to explain that there was a mech in the Vault that I intended to move, but I was certain that somebody was going to steal it, so it was time-sensitive. But by that time it had already been stolen anyway. I was honestly a little unsure what we should do, because the circumstances were so unusual. I won't even question why admins thought spawning a free Phazon for Maline to steal, was a good idea or fair to all the traitors they weren't spawning mechs for, but hey, I roll with things as they develop. Admins use their verbs for fun things now and then. Admemes are cool with waiting a minute, in my experience. I'd agree that the round was unusual. I don't believe you've given any valid excuses for totally ignoring the department you're in control of, however. The duties of a Head of Security, according to the wiki are "Coordinate security, maintain order." If you don't trust the rest of security, OOCly and ICly, don't play a job that requires you to command them. In my opinion, it's not acceptable from an IC standpoint to ignore your duties because you haven't talked to some of your officers before. OOCly, it's not much different. You ignored and endangered your department because of trust issues.

Okay, I'll take this point by point, I'm organizationally inept, so excuse any issues. Local HoS arrives late, introduces himself, gets a feel for the department and gets caught up on any ongoing issues... then goes quiet, because there is little to Command them over on Code Green with not even a hint of anything wrong. Yeah, I get where you're coming from here. Maybe check in with everyone every 20 minutes or so? Couldn't hurt. You got no explanation because you aren't entitled to an explanation; you're expected to follow orders. I was co-ordinating with the Captain and discussing our approach long before you were called in. You were the nearest Officer so I enlisted your support on their orders. Being one of the only crew on the station able to pilot mechs, and being right at the elevator, then recieving a Central Command order that the Mech is to be immeditely moved, and the Captain authorises me to do it, yes I prioritised the $100,000,000 mech we were told to transport over the firefight in the OR that other officers were calling out that they were responding to. I let the officers attempt to handle the shoot out, while I attended the issue I was situated next to, prepared for and ordered to do so, both by CC and the Captain. That's a bad way to think, in my opinion. Just because you're the "big bad hos" in command doesn't mean you should send officers into possibly lethal situations, without giving them so much as a "there might be an armed guy down there, careful okay?" because they should follow orders anyway. As for not acknowledging the firefight, you have a radio. If you're unable to multitask, move back to your office, watch cameras, and coordinate officers. You're the Head of Security, not Security Officer With Extra Access. It's better to have four people working together well than it is have five uncoordinated people, four of them being totally unaware of the current situation. I was talking to the Captain on comms while camera scanning the Command area, and I see the scientist that someone has just reported to me as potentially dangerous, is now breaching into the side of the Captains office with thermite. I know he's going to be in there before I can stop him and the Captain is in imminent danger, as in may be dead within seconds, so I inform Security of the location and head over as fast as I can. While trying to talk him down, the scientist opens fire on the Captain, and then me, and we tase him down, arrest them and leave. And that's the first time we see the Phazon, as it phases through us, the Captains office and the Bridge. Not only are we now looking at Grand Theft of an extremely valuable mech that will severely damage Nanotrasens relations if we lose, but the pilot is commiting Infiltration of Command areas freely after having broken into the Vault, and at such a speed that we basically have no hope of chasing them, armed with weapons that we cannot match and armor that we can only really threaten with one gun. Everyone is briefly very confused about the Phazon phasing through and around us. I decide our only chance to even stop it is to ion out its battery charge. I should note by this point that I have recieved a message that potentially indicts my Warden as an accomplice of the scientist we just arrested, so I have discounted being able to trust them. But I did not call for their arrest because I was missing actual evidence, and the Phazon was proving to be the bigger threat. So, yes. I got the ion rifle and carried it myself, because my Wardens loyalty was in question (and as it turned out they actually were a traitor). The scientist who shot at the Captain was handled pretty well, I didn't have an issue with that. However, all this stuff you knew about the Phazon at the time, why was none of it shared with the rest of security? We knew.. there was a valuable object on the station. We weren't told it had been stolen, or that it was an extremely dangerous mech. It wouldn't have taken more than a minute to make security aware of the heavily armed and armored stolen mech that can walk through walls and yet you chose not to make any of us aware of that. Was making a beeline to get two rifles more important than keeping your six staff safe and effective? Why would you assume the situation had changed if you hadn't been given an update? I told you the stolen mech was on the loose; you saw it yourself. Did you want me to sit your character down for a briefing every five minutes? Please, god, show a little initiative over events you saw unfold before your very eyes. You read the same announcements as I did, you saw the mech. I couldn't tell you to setup a perimeter, because I had no idea where it would go, and knew it would phase through you anyway. I was constantly trying to get the AI to provide a location, or tracking, of the mech so that I could pass that on to you. Basically anytime I wasn't talking to you, I was either talking to Command and the AI, or moving somewhere with urgency. We found the mech in robotics, it phased away. I was on Command comms with the RD trying to figure out with the RD why the mech was there; it was there to charge. I asked them to dismantle the charging ports, to cut the mech off from its power. A minute later, the RD reports over Command to me that the mech is back in robotics, so I run in. I can see Maline is out of the mech, in a stolen RIG, attempting to climb back in, so I spray her and the mech with ions to shut down the Phazon and the RIGs power cells. And it works, because Maline has to try and fix the Phazon over the next few minutes, while Security surrounds them. Maline tries to install fresh batteries while I pull them out again. I have called for engineering to help officers breach in through the SMES room, but I don't remember them ever turning up. I don't expect constant briefings, but nobody in the department knew what was going on at the time. We saw a stationary mech in robotics, that's not exactly suspicious. And given the fact that we hadn't been given any updates up to that point, I wasn't expecting one, was I supposed to pull out my rifle and unload on a mech that appears to be unmanned? If you don't know enough about a situation to get security working properly, did you really know enough to wordlessly sprint after a heavily armed mech? What was the thought process there? You couldn't fight it alone, why not take a minute to gather your thoughts and get us focused and on task? You have a department to manage, after all. Most of that second paragraph is all good, but why not alert officers to the fact that engineers were called? We'd pretty much given up on getting through the SMES room. By this point, I was essentially taken out of the game by ahelps enquiring about my characters skills. I could ignore the game and deal with the admin breathing down my neck, or ignore the admin and play the game. Let me tell you, when you play Command and you suddenly have to deal with ahelps, you cannot perform your job at all. I had to spend the rest of the round focused on my ahelps, so I'm sorry I couldn't micromanage you through a firefight. You could've asked the admin to hold on a minute, admins are usually cool with giving you a minute or two. I'm not asking you to micromanage security in any way, but it'd be nice if you managed the department. We'd barely received any orders from you, and not a single update pertaining to the situation. You chose to focus on playing an upgraded security officer, rather than manage your department. That's my main complaint. If you can't manage the department and work in the field with us, manage the department and keep us on track. The round would've gone smoother having four security officers aware of the situation, rather than four officers out of the loop and one guy trying to be a superofficer. I apologize if I come off as mad or upset. Not trying to insult you, if it seemed that way.

BYOND Key: Tbear13 Game ID: bTJ-ccN1 Player Byond Key: K0NFL1QT, I believe. Staff involved: Seb took my ahelp, he told me to make a complaint.. so here we are. Reason for complaint: TL;DR: HoS refuses to communicate with the rest of security, instead using an ion and laser rifle to secure valids. Writing this a few hours after the round, so the times and such might not be a hundred percent accurate. The Head of Security, Kato Zane (K0NFL1QT), failed to uphold the standards of a whitelisted player, in my opinion. The round started pretty normal, I joined a few minutes in, he joined within seconds of me. After I gear up, we're told to report in and do so. Over the next thirty to forty minutes we hear.. next to nothing from the HoS. He verifies the charges on someone, agrees to the warden detaining a cadet for assault, and is otherwise silent. At around an hour and twenty minutes in, we get an announcement about a crate being put aboard, and how no crew are to touch it except for moving it to the cargo shuttle later on. Here's where the real issues start though: A little bit after that announcement, I'm told to get a rifle and report to the vault elevator. Keep in mind, I got no explanation, we're on code green, I know nothing about the situation. While this is happening, medical reports an armed man in the operating rooms, which officers respond to. A firefight breaks out, which the HoS chooses to totally ignore. Once we get into the vault, I see that someone had broken in through the back of the vault, using inflatables to not vent it. The HoS yells something along the lines of "A Phazon was stolen!" and immediately runs to the armory, retrieving a laser rifle and ion rifle, without giving any direction or explanation to security other than telling the warden "You may hand out weapons." A minute later, security is called to the bridge. I'm the first officer to arrive, and find a scientist with a 9mm pistol looting the Captains office. I command them to drop their weapon and get on the ground, which they ignore. The rest of security arrives and the Captain comes out of their back room, which scares the antag into firing. The HoS manages to stun them before they can do any major damage. As we leave, a floaty-mech thing comes down the hall, phasing through me. I'd assume this is what the "Phazon" was. We proceed to search for that mech, until a cadet and I find it in robotics, charging up. I alert the rest of security, while the cadet goes in closer to investigate. Has the HoS given updates, ordered the rest of security, or even had us report in since before the incident in the bridge? Nope. So we're not sure if the mech had been re-captured, or if it was still a threat. After some backup arrives, including the HoS, the person inside the mech (Maline Trell, a traitor) taunts us, before phasing through the robotics wall towards security maintenance. Rather than have us establish a perimeter, organize a search, or anything of the sort, the HoS charges off after the mech silently. A few minutes later, the mech is disabled in robotics. The HoS rips out the mech's powercell and starts yelling for Trell to surrender. A few officers move around behind them in maintenance, making sure they can't escape. A little bit after we got into maintenance, it's reported that there's a firefight in the RDs office, the ones in maintenance move in through a hole in the wall, where we encounter the gunfight. The traitor, the one detained at the bridge, and the warden are fighting against the rest of security, I move in to secure the downed traitor, while the warden is captured by other officers. Once this all comes over the radio.. does the HoS say anything? No, still nothing from him. After that.. pretty much nothing happens. The traitor I'd secured dies a little bit after the fight, and a vending machine tried to murder me with heart damage. But.. yeah, that's about it until the end of the round. While he didn't explicitly break any rules, I don't think this is acceptable behavior for a whitelisted player. Did you attempt to adminhelp the issue at the time? If so, what was the known action taken by administration/moderation? I ahelped it, was told to make a complaint. Approximate Date/Time: 4/5/2018. The round lasted from around 10 AM to noon. Additional Stuffs Sorry for the messy writing, I have a headache and didn't sleep very well last night.

I'll definitely change my stance to neutral now. The application is decent, however I've never seen you ingame and can't really judge your roleplaying ability.

Gonna have to -1 this for now. The backstory essentially ignores the most important part of Tajaran backstory, that being the civil war, you're required to have that as a major aspect of your application characters backstory. I don't like that he, at the age of sixteen, invented a bunch of mining robots that could replace workers with zero actual training. You totally skipped his college years too, does nothing happen except him studying during those years? Where did he go to college? It would also be nice if you changed the 'RP differences' to be more than 'kitty talk different.' I'd reconsider the -1 if some of these issues are addressed.

Geeves is cool, RPs great, OOC he's chill, +1.

It'd be great if you can post a screenshot of the ban reason, it should show the reason when you try to join. The definition of validhunting is to, well, try to get a kill just because it's 'valid.' A valid kill being an antag or anyone you can kill without punishment. Arming yourself as a quartermaster and trying to do securities job just 'because you can' is very much against the rules. Would you, realistically, go from a box-pusher to an armed vigilante and try to fight the AI, Captain, and possibly the rest of the crew, over a diona being made the Captain? Not to mention you trying to order security around as a QM, which, as a sec-main, bugs me.

+1 from me. Not a huge fan of more sol stuff, but what's one more? Chunley is a pretty great character, Smiley is cool OOCly, so yeah.

As usual, -1 from me. Formatting is off, the backstory shows that you don't understand, or don't care about, the lore, the answers to the other questions barely qualify as real answers, this needs a *big* rework before I'd be willing to support it.

I'm on mobile, excuse any mistakes. I'm a little confused, what is this exactly? If I read this right, it's a chameleon projector that doesn't work, or does it give him that ninja suit-ish helmet on the sprites? Why would you bring something like this to work every single day? Why did they let him keep a corporate prototype in the first place? -1 from me, this item seems kinda weird to just carry around at work.

From that description.. the notepad is mostly to interact with antags? A custom item shouldn't have "classified" stuff that you shouldn't jot down on a notepad you show off freely, or be mainly focused around antags.

Huge +1 here. Pretty good application, and geeves is a great player with great characters.

Station pets are speshul. The warehouse items.. sometimes don't make sense. But that only answers half my question, why would your character bring Pupper McHugs to a research station that he works at in the first place?

It seems kinda silly to bring a dog/cat/goldfish to the Aurora, even when you're visiting. Why couldn't the dog stay home for *two* hours? Why would you bring him to a research station, of all places?

Uh, I think you missed my point. It doesn't have to make your character go insane, or make him an anti-social edge-lord, but I don't want to RP with a person who's backstory is "I have a perfect life, I've never had a single problem, I have plenty of money, my family is all great, I've never had issues at a previous job, and I've never had any problems outside of that either!" See what I'm saying? A problem could be as simple as going broke off a bad investment, a divorce, or something like that, but you've gotta have something to keep him interesting. With all due respect if you knew my character on server you would know that he has had alot of conflicts, i just don't think that my app for CE needs to make, Ayden out as someone who would seem even moderately unhirable. as someone who knows how it really feels to get denied a job due to full disclosure i will simply say i respect your stance but if you want to find out more i implore you to try talking IC to Ayden. I mean.. the entire point of the backstory part of this is to write his, well.. backstory, not say "find out icly" about all the details.

There aren't any rules involving aging, do it however you see fit.

To add onto this, Athena is played by Drivermonkey.