Xelnagahunter

As a former CCIA member, this is one of the things I think I can weigh in on why leaving them unbiased is important. First is OOC reasoning. It's easiest just to make them this way. If we decided to make CCIA biased how do we regulate it at all? Do we assign bias to individual CCIA members so that we can insure that each race has someone on the IC team that hates them? If not what happens when too many CCIA agents hardcore hate one race? I don't think people realize just how much CCIA have to play their CCIAA in their head while doing something else. Second is, why wouldn't NT throw out something that appears to be a true equal opportunity bone? Sure, they are paid less. Maybe they are given shittier jobs or restricted from having some of the higher end ones, but why not give them an equal means to resist physical and emotional oppression on station? This will give them a reason to feel protected and stay on with the company as cheaper labor. Anyways, those are my thoughts on it. It isn't really broken and there are reasons for it to make sense both IC and OOC.

Keep in mind that the "one success" was only out of five events run this week alone. The antag contest has been in operation for some time with normal antagonist rounds helping to push odds in the favor of one faction or another. In the long run, pro-synth factions did a lot of work and in the last week they were largely suppressed due to threat of force. Those events and the 20% pro-synth success rate vs the 80% anti-synth success rate, adjusted the final totals to create the 49%-48% (which I assume includes 3% neutral) victory for the Pro-Synth movements and organizations. So the Synths win a small victory in the long scheme.

Along the same lines with a different example. I was playing my Captain, a security background character with basic emergency engineering training as would/should be standard for anyone in a space faring Navy. Malf AI wanted a reset for one of their units, Sec was already disabled and the only other heads I had alive were HoP and CMO. Robotics was also empty, so the captain was demanded to perform the task due to allowances on his ID. I tried very hard to RP this as something he had NO clue how to perform, even though robotics was one of my first jobs in the game. It was all I could do to convince the AI and cyborg ICly that he didn't know how to operate the machines properly nor how to properly install the reset module. The cyborg I was trying to convince in LOOC as well. The AI took to telling the crew they would die if I didn't complete the task and the rest of the crew started telling him it was easy and that any 4 year old could do it. opening a robot, not damaging wiring or existing machinery, and installing the module, should not be that simple though. The printing of the device I could get cause buttons, but not the installation. In the end I just had him do it justified my IC and OOC stalling to type as representative time it would take someone without the knowledge to perform. Our community can, at times, make it seem like the game's mechanics are as simple as the click actions they take.

TO: Edmund Blade, NSS Exodus FROM: Greg Ashcraft, NMSS Odin SUBJECT: RE: Incident Report -------------------- BODY: This is an automated message to inform you that an investigation has now been opened regarding your incident report, and assigned to Greg Ashcraft (Xelnagahunter) You may be contacted by the duty officer for an interview, or you may contact them directly if you have any questions. -------------------- DTG: 5-3:47-TAU CETI STANDARD-6-2458 SIGN:Greg Ashcraft

In my experience, most people will recognize someone who has been prominent to them in the past. You can't be a passing conversation unless it becomes a religions thing that you do every time you're both on station and then it gets absorbed after several interactions. It works the same way in the real world. If I say hello to the same guy leaving my apartment every day because we leave at the same time, eventually I'll ask his name and address him by it when I see him.

I dunno. I just like it as is I guess. makes dates simple. If YOU wanna accelerate your character's growth like that then fine, but to make it cannon puts a lot of strain on date relevant roles, such as CCIA. As for working 2 hour shifts, that's already been justified, not sure if publicly or not, by lore staff: we aren't meant to jump on every single crew transfer. The infection and doctor thing is a bit of a big deal, but computer aided medical stuff and thinks like the gel that mends bones should make medical stuff faster. Infections could simply be keeping up with our advancement in medical science. There's a lot there that can be justified as is. There's pros and cons to both sides and I get where you guys are coming from, but I feel that the cons, from my perspective, outweigh the pros.

I'm actually against this Idea. The standpoint has a few implications, DOs would be changing their DO characters every few years and constantly making younger ones. IRs would take over a year to complete. "You have 7 days to respond to us or you're getting fucked for not doing so" become "you have 6 months." IR interviews now take half a day or more to complete when all you had was a few questions. Beyond DO stuff, what about people who play once a week? "Dude? Where have you been for the last 6 months?" Better yet, I play my captain for a day. then I don't play him at all for a few then play him straight again for a few days. Where is that consistancy? DTG would be fucked and I'd be constantly looking up the date/time for faxes IRs, and the like. In the longrun it turns into book keeping for the player. I'm not willing to play a game that I have to put more time into preparing for than I do when I run DnD games. Not happening at all. Also, I type slow. So you get a sentence from me every hour or so in game. Nah.

Oh, and for the love of GOD! If you take a player hostage who is ready and willing to play along, give them some leeway. I got taken hostage once with plenty of chance to fight back from a meta standpoint. I elected not to because my character is that against conflict that even with a drill in hand he didn't want to have to fight. I was captured and dragged through space (without a suit) to the skipjack. I was then bucklecuffed to a chair and punched whenever I tried to talk saying that I was willing to help them if they'd let me go when they left, which was honest. I didn't want to be free right away, I just wanted to be able to interact rather than sit there and get beaten. If I recall I just ghosted because I was tired of being bored and later joined the ERT, at which point I was OOCly pissed off enough to not give any shits. If you take hostages, then at least make it fun.

Thanks so much.

You got uncannily close to my real name there. >.> Just had to throw that out there.

A big thing for keeping up with lore, from my perspective, is that I learn a thing and then have to be given links on where to find it because it's so decentralized. I leanred recently (keep in mind I was gone for moths and haven't been back too long) that Taj from the Republic of Adhomai have a legal order to return to Tajaran nameing structure or face legal penalties. My personal grievances with this aside, I had to have someone link me the location for this. It's not in the wiki, where I assume important lore such as that would be, because I did go back over the wiki when I returned and wanted to play my catbeast. Find some way to centralize lore changes, even if you give each race's lore page a spreadsheet style update document, ei: Event name, enough details to understand it, date it was applied, date removed if applicable (with a strikeout through it all if it was removed).

Knowing a thing or two beyond your character's general technical capacity is fine, but should be targeted and specific. I'm not a mechanic, but I can operate tools and do simple fixes where needed. As such, knowing first aid or how to set an arm as a quartermaster isn't evil. Surgery would be an issue. Most of our jobs require significant schooling to obtain, those that don't require a larger quantity of experience. The civilian department is one of the few exceptions to this. But even still, there's a difference between cooking at home and being a professional chef or line cook, which I can example because I make a damn good meatloaf while being shit at much else. All in all the object of learning things is to use common sense in what your character knows. Having some hand to hand skill isn't bad. Being able to not drop a gun when you fire it is fine. Being a crack shot is not. In a recent round an AI forced my captain, with a security background, to change the module on one of it's units. Our game mechanic and flavor makes it as simple as putting a card in a slot. Really? I highly doubt this, but the AI insisted ICly that it was that simple. A jetpack is added in the same way... So where the fuck did the jetpack come from? Rant on that aside, to refer to the original topic as well, learning things in game is very acceptable. You should RP this learning process for some time. for something specific (hacking doors) it might take a couple weeks to learn how to read everything properly and avoid shocks, other tasks are not so simple. My captain will not know how to change modules forever, antag influence aside. That brings up a real issue though. Anything influenced by an antag is instantly non-canon. Our antag system demands and dictates this. Take from all that what you will, but it's my thoughts on the main topic and the sum of other conversation in the thread.

Here's the thing though, ICly how many times have they really been cloned? Are you saying that if the antag gibs me a bajillion times I can treat cloning as nothing out of the ordinary when it happens again? Oh wait... Most character deaths which result in cloning are non-cannon. Nifty thing about that. If they can't be bothered, they deserve a warning/tempban.

Probably because such would need to be canon. While I would like to see this in some form or other, even though it's not the sort of thing to happen, the primary issue is that something punched a big hole in the station from last shift, and unless we make the endless barrage of xenos and pirates canon, there's not really much explanation for it. This is the answer. The large quantity f antagonist rounds we have produce non-cannon events for the station. If a wizard blows up the station, you can have a conversation you had with a friend remain cannon, but the shift as a whole is not. there's also been explanations for why research resets and the like, it's because you're not gaining new research as much as proving the repetitive nature of the analytical data. Most of what we research exists in a solid enough of a form that it would be impossible for us to say we are discovering it for the first time.

Wow... worthy read...

TO: Zuleika Xrimqil-loix, NSS Exodus FROM: Greg Ashcraft, Central Command Internal Affairs, NMSS Odin SUBJECT: RE: Incident Report -------------------- BODY: Due to a lack of response from either party in regards to investigation, in particular from the complaintant, I am closing this Incident Report. -------------------- DTG: 5-3:47-TAU CETI STANDARD-6-2458 SIGN: Greg Ashcraft ((OOC Notice, Vengar Ra'iaxka and their player have not been active in two months.))

I have a character or two that I'd like to get ported over. I've redone my more prominent ones though.

Can I politely inquire as to status for this?

Excuse me. I have two copies of the rules for PnP fallout printed and bound thank you.

I disagree. I've seen several AI units, including my own Qwerty and the Katana series, work across several platforms. Katana's value as an AI does not decrease simply because she is in an IPC compared to an AI frame on the station. It SHOULD be the software that costs the most. Remember that programing unique AIs is still something being researched, mostly because I image things like identical codes behaving differently is a thing. I'd say an AI can run on any mass produced machine that costs next to nothing to build. Hence you would use the card to remove programming information and store it to keep it safe.