Skull132

Into command bar, type this: "remov", press spacebar, press enter. It should automatically finish it as "remove-id". If it doesn't, then add two more key presses between pressing spacebar and pressing enter. This will eject the ID form your PDA, as long as your PDA is not contained in your ruck/satchel/whatever. The PDA doesn't even have to be on your person, it can be on the ground as well. Once you're done with your ID, just click the PDA again and voila.

Ervas cannot help but scoff at Abelard's suggestion. "Which friends would it be this time? Debt collectors? Divorcees?" he asks, a sarcastic grin hidden behind his ashlander scarf.

If skull is still alive somehow at that point. Maybe.

Reporting Personnel: Kimberly Riden Rank of Reporting Personnel: Security Officer, Internal Security Department, NSS Exodus (Temporarily) Personnel Involved: Amos Snyder, Detective, Internal Security Department, NSS Exodus; Ivan Ivanov, rank and department unconfirmed Time of Incident: 15/03/2458, around 0300hrs Tau Ceti time. Real time: 1900hrs GMT+0, 15MAR2016. Location of Incident: NSS Exodus (Primarily the bar) Nature of Incident: []Workplace Hazard [x]Accident/Injury []Destruction of Property [x]Neglect of Duty []Harassment [x]Assault [x]Misconduct []Other _____ Overview of the Incident: Three separate incidents will be explained in this report, that all occurred during the same shift. First, following the detainment of an SSD criminal who had taken items belonging to mr. Snyder, mr. Snyder attempted to remove items from the detained body of the suspect while I was taking them to the brig for processing. As far as protocol is concerned, all items located on a criminal are considered evidence until deemed otherwise in an investigation, and mr. Snyder should have waited until we got to the brig before trying to take back his hat. I informed him of this twice, both times electing to move the suspect's body so that he could not complete the actions of retrieving his hat. The third time, mr. Snyder drew his firearm, a colt .45. I froze, he took his hat, and reholstered his firearm. While he did not specifically point the weapon at me, considering the fact that there was no apparent physical threat to neither of us, it is my belief that the weapon was unholstered as a means of intimidation. At which point, this would be a violation of article i115 [Threat of Murder or Serious Injury] of Corporate Regulation. The second incident took place over the security channel roughly 15 minutes afterwards. While attempting to explain that policing one's brass is the hallmark of a disciplined weapon's user, mr. Snyder retorted over the security channel near-verbatim: "Do I strike you as disciplined?" With this incident having just occurred, I was walking past the bar. In there, I spotted mr. Snyder and mr. Ivanov engaging in a bar fight. At the moment of walking in, I saw both individuals armed with makeshift weaponry (broken bottles), and mr. Snyder was assailing mr. Ivanov. In order to defuse the situation, I utilized a flashbang and cuffed both individuals. I proceeded to request for assistance over the security channel at least three times, but was unable to receive a reply for at least five minutes. Both suspects were bleeding from the bruisers they had inflicted upon each other. I sat mr. Snyder down in a chair, and was holding mr. Ivanov next to myself. A medical officer came over and started treating mr. Ivanov. At this moment, I saw what I believed to be mr. Snyder attempting to break free of his restraints. Though bleeding, his injuries were light enough to enable this action. A further consideration for the following actions was the fact that mr. Snyder was still armed with his .45 caliber pistol, and that I had yet to receive any back-up. In order to stop any further trouble, I took my taser and fired three bolts at mr. Snyder and incapacitated him. Shortly thereafter, I gave mr. Ivanov to the medical officer and took mr. Snyder myself, we proceeded over to the medical bay. It is only at this point, following, as previously stated, roughly five minutes of constant requests over the security channel that another officer finally responded. Officer Olivia arrived at the medical bay and went to watch over the treatment of mr. Ivanov. I stayed with mr. Snyder and waited for the medical staff to clear him. Once cleared, we proceeded over to the brig where mr. Snyder was processed, his firearms removed, and his person searched. At this point, we discovered items belonging to the initial suspect (the scientist) on his person. Mr. Snyder excused himself, saying that he had been incapable of returning them. However, considering there was at least 15 minutes between the capture and processing of the scientist, in which mr. Snyder played an active role, and this situation, the excuse was deemed unfitting and he was charged with violating article i206 [Neglect of Duty] for failing to properly secure evidence in a timely fashion, and leaving them on his person. He was further charged with violation of article i103 [Minor Assault] of Corporate Regulation for attacking mr. Ivanov and causing his skull to fracture. Mr. Snyder explained that he was acting in self defence against an assailant with a knife, however, I saw no knife on the crimscene and mr. Snyder did not use proper means (his firearm loaded with LTL rounds) to defend himself; he instead opted to fight with improvised weaponry and sharp instruments, causing more than excessive damage to the claimed attacker. He also did not call for any assistance over the security radio network. Mr. Ivanov was also charged with violating i103 [Minor Assault] of Corporate Regulation for the same incident. Did you report it to a Head of Staff or IAA? If so, who?: Yes. Vira Taryk, Head of Security at the time, conducted an investigation into this incident during the duration of the shift. Additional notes: While the incidents were handled mid-shift by ms. Taryk, I would wish these to go on record, should further offences of similar nature arise with mr. Snyder involved. The misuse of firearms is a very serious issue.

You can. The ironic thing is, killing slimes with massive amounts of brute damage is more effective than water atm. Which is awful, and will be changed, by making extinguishers more effective.

Analogous solutions are solutions to coding issues. Specifically asking the question of, "We have this issue, how did the other codebases solve this?" An example is the autobanner solution, which Scopes and I developed partially based on the input of a GOON coder discussing it on reddit. At this point, I've developed our model to be different to a good degree, but the solutions are analogous in that they solve the same issue in different ways.

As a note, I've assigned this to Lord Lag. The first thing we're looking into is making low temperature kill slimes again.

Considering the relative openness of your initial statement, I was posting my views on the subject as the head developer and a coder.

What's funny is, the only major abnormalities in their code are items relating to their webAPI and their management of the UIs. The rest is standard coding in a shitty language. One of the major things they have going for them is the fact that they have folks who fit the role of game designers. You know, people who can think of nifty puzzles and shit. In order to fill that void, we'd have to basically copy over their concepts and story. But, we're not GOON, none of that would fit here? Once we have time, I do intend on looking into a few things relating to that topic, but atm, we have no time. I honestly don't think you have a solid understanding of what their codebase contains.

A vampire has amazingly powerful stun abilities that go through sec shades. Why were they not used, and why was it necessary to immediately escalate to lethals? Further, while sec may have been valid as far as the gank rules go. The same rules also require that the amount of collateral damage be kept to a minimum. This means that the room venting should have been a last resort type deal.

TL;DR: no. GOON code has been isolated from other codebases for over half a decade, literally. It is not compatible even on the very core systems level, and making snippets of it functional would include a silly amount of work. The best use for this codebase is as another source of analogous solutions, but that's about it. I also have a personal distain for how the release came about, and don't feel like touching it for that reason as well.

As the Estonian saying goes, "You don't strike the mouth of the person asking." But that doesn't mean we'll go with what you're suggesting, either. Change one is silly, except for autotraitor that needs to be fixed. Change two will effectively be covered once I port our age ban system from old code. Change three is also silly. It is the heads of staff's job to know wtf different departments are doing. If they don't feel like doing that, then they can get blown to bits for all I care. Change four is silly, and fits in line with your apparent mentality of, "Make everything easy for me, please." Change 5 is too large for me to bother the mappers with at this time, as they're working on the new map. I do agree with the discussion about timing, and wonder if we should either return the majority voting system, or simply increase the harddeck of when voting is allowed.

Bicardine. Sometimes the bone is too brittle to be fixed via surgery. Administering a dose of Bicardine before surgery should fix this.

If you look at the image, they're around the time when the shuttle left the station. Past that point, the IC in OOC rule is lifted. So they're in the clear.

The science and robotics crew have survived without these dispensers for years. Literally. Their removal is hardly "crippling" to them. Though, here's an interesting point. I've been observing a good amount of players actually playing roboticists. Then again, I've not seen many mechs, so I doubt they're even using the dispensers. Observations not relevant to anything forever ever!

for scientists, it doesn't matter: there's a chem dispenser on the outpost to which they have access to anyways. For the roboticists, idno. Will have to think.

Corrected original complaint: Greggbot does not play John Altmann, Brosefstalin does. Looking at the LOOC remarks, Gregg was ghosting at the time and couldn't have done it. This also removes most of the outright incriminating things.

Actually, it did happen, and this complaint was discussed right before that with Delta. The consensus reached with Delta was this: TL;DR: in this specific case, the use of force was valid. And the roleplay had by Sue was also valid. While we would rather not see suicide dramas like this on a daily basis, one decently RP-d out suicide drama is not grounds for a kneejerk. Also note that the use of violence is valid, if the roleplay around it makes it reasonable. In this case, someone close to Yinzr had died, and he wanted her cloned. Ergo, the escalation from pleading to bribing to physical intimidation is fair game. This complaint in specific is deemed as invalid, and now resolved. The admin meeting hinted at in this discussion was had according to the dates, and we went over the actions of Alberyk. Also discussed them with him. At that point, the weekend ended and I was needed at work. So the situation has been stalled until my shifts were done. I will post a more detailed description of what the admin's thoughts on the Alberyk as a sec-lizard situation were in this thread tomorrow. And we'll use that as a basis on deciding how we wish to resolve that situation. Tangentially related to that whole fiasco is this one, here. Which I also stopped processing for the same reason I stopped processing this one, but will get onto with Hive, as I only work 2 days this week. (Some partial actions were already taken by Tenenza, following the meeting.) Long story short, having a job sucks when it requires 12 hours per day, as I really can't be arsed to deal with the server afterwards. Unless it's super critical. and until I get around to figuring out which admins to promote, there are a few issues where my involvement is required. Anyways, since actions for this complaint are done, I'll be closing and archiving this.

I actually did leave instructions v.v The command sent to BOREALIS. People are not stupid, and can figure out the IP as they need to. Either by searching the forums, or asking. As for advanced notice, it used to be done automatically with no notice at all, until the automated system borked. It's effectively SOP to go hidden on weekends, and because it's SOP, it's not something we always tell people about. We usually just mention it in passing and people track it relatively quickly. http://aurorastation.org/forums/viewtopic.php?f=17&t=480 Here's the reasoning and the whys and the hows. This is a global sticky, visible on all forums. There's also a link on the forums, towards the top, titled "Server Status Link". There's also a link on the main website, aurorastation.net, to "Board the Aurora". There's also a sticky in the announcements regarding server status, that has the IP and server status displayed. This is echoed every time I take the server down for updates. Seriously. If you use the forums, passively even, there are so many places to find this information. The only place it's lacking in is the server MOTD, but that's negligible, considering the slew of information I listed off above. As for the first timers. If you enjoyed your time on Aurora, chances are, you'll notice it back up after however many days it has been hidden for. Then you'll sign on, and ask wtf's going on. And then you'll receive an answer. I'll probably write it into the MOTD again, where it used to be, but that's about it. (Notice given to the fact that most people disregard the MOTD anyways as visual noise.)

A Dunmer warrior walks up to the board, scrunching his nose. Body defilers, nobles and Argonians, or more nobles. "Fair enough," he mutters to himself after signing his name, 'Ervas', on the top most contract. Body defilers it is.

The easiest way would be to just rename the plain text used in the menus. Renaming all of code to use trauma instead of brute would be dumb, and so much work for little gain. So just change how the front end looks, and done

Okay, so. This was my long week at work, and we had a decent load of stuff to do. So I neglected to check the Discord after waking up. I also managed to forget my phone home for the entire day, so I also couldn't check shit while on my lunch break or while coming home. So, shit circumstances squared, yaay. I usually don't go off the radar for this long without notifying folks. Since the phone was at home for 12 hours, GG. As for admins touching buttons. Deal with it. On a less aggressive note, what happened is that the entire OS shat itself. I am doubtful that Tenenza managed to cause any of it. DreamDaemon instability, aye, maybe. But I am doubtful that DreamDaemon could clog up the entire server machine enough for it to hard crash like this. Last point, the server itself. First off, understand that we are talking about a full virtual machine that also houses logs and other fun things. Though some operations might be restricted through user accounts (Would have to look that one up), I'd still consider it on par with giving someone full Root access. That is to say: they can do whatever they want. Lately I have been toying around with the idea of server maintainers. But since I also have other administrative things running alongside this, coupled with work and getting my shit sorted with the Defence Forces, this idea has been in the backburner. I did have a few candidates, however. Maybe in a few weeks. Also, protip to everyone saying that this should have been tested on a private server: if DreamDaemon indeed somehow caused the OS to hardcrash, then testing this would have either: resulted in nothing, or crashed the server anyways. The first one would have happened if the private test server was hosted on the admin's local machine. Since no one runs server software (OS-wise) on their personal machines, chances are, this crash wouldn't have been evident due to differences in how the systems are set up. The second one would have happened if we had used a second session of DreamDaemon running on the same box. Since the crash was OS wide, both servers would have been kill, despite the fact that the testing was done on a "private" server. So again, if this crash was caused by an admin, which I doubt, as I have never seen DD kill an entire OS (even with the abuse YeahChris threw at it), it would have been unforeseeable. The only thing that sucked was that we weren't able to restart the server until now.

It's back up. A bit of an explanation will follow shortly.

Kek. I was debating on whether or not to somehow tie Ervas with house Indoril as well. Chose not to, as he's too young, with exception made to one element. Also, Bokaza. As necessary, I can write up more backstory for the char. Whar I put up was about all I could manage before passing out last night.

I'm actually kind of interested in this, and if you're willing to bare with my work schedule to some degree, would like to join in! (I can explain my work schedule as needed, it's consistent and on point, just a bit odd.) Name: Ervas Description: Dunmer, with a gravely voice, sharp facial features and dark hair. O, and red eyes. Chainmail armour, with a few pieces of bonemold armour thrown on top. Also wears a tattered, blue travelling cloak. Primary skill: The ability to craft spell scrolls. Also enchanting as a byproduct of that, though the processes are different and as such, his enchantments are relatively minor. He's also relatively well practiced at using a sword. Misc skills: Knowledge of the Deadric language. Arbitrary survival skills required of a lonesome wanderer. Disadvantages: Literally Dunmer. That is to say: socially inept in "softer" and more civilized circumstances. Backstory: Though not old enough to remember the events of the Argonian invasion into Morrowind, Ervas has certainly felt its effects. His great and magnificent people, overwhelmed by a bunch of slaves. Eurgh, surely they were wrong to place their faith in the demigods who now lie dead, insane, or are just simply. Gone. Ervas did his best to try and remain content with the life he had: serving under the locally ruling great house, as a scrollsmith. The house lacked faith in the Telvanni mages, so they looked for skilled individuals who could also lift a sword, and would be willing to fight with one if all else failed. Eventually, however, due to the ongoing Argonian raids, similar to the one they launched on Solstheim about 50-60 years back, Ervas was pushed out of his home and forced to walk the road north. Much like many other Dunmer in a similar predicament, he ended up in Skyrim. Slightly more padded narrative, for narrative reasons. Raisins contained inside.