Skull132

And I'm of favour to remove it from extended completely, but to keep it for antag rounds. Anyways, we'll see what the other staff think in a few days.

To explain where it came from: It's a random event that has existed since January. It's just been such a low chance that it never happened (except like, once over 5 months). When Nanako rejigged the event probabilities, it became a thing that might creep up more often. Anyways, since it's now an actually active topic, I'll throw it to the admins to chew on this Friday. (We're having a meeting.) Will report back on whether or not it gets disabled after said meeting.

...Didn't we unban you after you wrote a relatively decent appeal a few months back? Someone remind me, my brain is fuzzy on this.

If implemented, this system should be implemented with reactive oversight. Meaning, you assume all suspensions to be legitimate until a complaint comes up. Once a complaint does come up, whether we funnel it to admins or DOs, it can be mopped up within 24 hours easily, and misuse punished at that point. It would also help if you establish a clear, "Fuck up twice, you're out," system, whereby you directly go after someone's whitelist if it's confirmed that they abuse it. Remember: they're whitelisted. Staff have the authority to remove that whitelist upon misuse. That is literally why the whitelist system is a thing, it's not just there to test your writing skills. And if it gets abused en-masse. Just take away the toy the whitelisted players ruined for themselves. As for whether or not it should be implemented. Well, let's look at a few things. Intent is to make the consequence for failure more tangible, specifically if failure comes from bad conduct. The tools fall in line with temporary punishment shenanigans, and are intended to be an inconvenience and an ego-blow at most. Monitoring won't be an issue, everything can be logged. If successfully implemented, this would enable DOs to very easily and very quickly acquire more boots on the ground. Basically, you have people to delegate minor issues to, enabling the DOs themselves to deal with higher level issues. It would also amplify the effects of DO policy, if the whitelisted players start enforcing it. Boots on the ground are what's needed to enforce policy, remember this. And DOs right now, still lack an onboard presence enough to actually make them effective. This might be a way to achieve this. The risk is obvious: someone's stupid with it. That someone can get reported and his whitelist nixed. And as said, if abuse is en-masse, then we'll just shut it down and call the experiment a failure. Is this risk of abuse something we're willing to take, at the benefit of adding actual consequence to certain action?

It comes from species that have dark-vision. The way Bay uses that specific mob mechanic is by giving all species with darkvision very slight visibility in an n-radius, while in pitchblack. It's barely noticeable without mesons. However, put mesons on, and the shadows from that dark-vision clear up completely. You won't see further de jure, but you can utilize your dark vision properly. To understand what I'm talking about, play a Tajaran and put mesons on in a pitch black hallway.

Except. Would they? As someone with access to staff channels, ya, sure, you can say that they would. But lemme paint this from the perspective of a random player. Wake up one day, open inbox, see this beauty lying there. Your next step is to try to figure out what the fuck is going on, and what the fuck you missed. Well, hey, two days later an explanation is posted here. And as far as I've been told, some personal inquiries into this matter have been ignored. The sum of all of this is a viewpoint whereby the Lore Master just does shit first, and thinks about communicating it later. Which is a very basic, very fundamental violation of trust that needs to exist between the playerbase and the admins. Communication, communication, communication. Right now, we've been lacking in that department.

That's confusing! For a map, here's how the easiest way of making a translator for this goes: Input in Taj language -> break up into words -> look up and pull all individual words from the database -> replace word for word -> voila, you now have translated content. This, however, relies on the dictionary being already premade. Which, right now, it's not.

Aww, that's lazy though

A funny thing I've wanted to try. Just for the sake of trying it. Is to upload the cache of a language onto an SQL database every round, and pull on round start. Basically: have a persistent language. The only issue with this (beyond the fucking size of the array I might be constructing after a month or two) is the fact that the language code doesn't recognize derivation. Meaning you will have derivation which makes absoloutely no sense. For example: "you" being "jurl", for example, and "yours" being "rrhaz". Also, can't tell if AJAX and fully dynamic, or reloads from PHP every time I press button.

Imma sidestep the discussion in earnest, because I don't play enough to make a call on whether or not these points are valid. One thing I would like to direct your attention to, however, is how we communicate. Or in this case, how we are literally trying anything but direct communication. If there's an issue with a specific player's conduct as Tajaran, then that player should be sidelined for a few and the problem discussed. If possible, a solution reached and agreed upon. Right now, we've tried the IC NKVD/Stasi approach, and now we're doing the "general, point fingers at everyone without committing to calling out individuals," spiel. Both of which are great for raising an amazing bruahaha and racket, but not actually solving the issues. Seriously, grab the dudes who are causing issues and have a chat with them. Get their side of the picture, give them yours, see if you can come to an agreeable solution.

Application accepted based on previous cooperative work experience. Welcome to the team.

My view on it: NanoTrasen negotiates and cooperates with terrorists as long as it is within their interests to do so. Simple as that. Oh, and company policy is quite different from a co-worker's view on the situation.

I'm confused here. What exactly is the issue, because the original post fails to word a it. "This is an English only server," very plainly refers to the fact that you will use English as your primary means of communication both IC and OOC. I do not care, nor should the rules, for the semantics that exist IC around the made-up languages. If you are given a prompt into which you can enter words which may be heard by other players, you will, 9/10 times, enter those words in English. That is what the rule mandates. Accenting IC speech is permitted as a universally understood mechanic of displaying an accent for the character.

/me looks at the vote count. Welp. That's that, then. Also, regarding blue and blue (command and sec), we'll have a look at alternatives for command as well.

Long story short, for those of you who haven't been around long enough, Aurora used to have a custom set of blue sprites for everything security. Effectively changing redsec to bluesec. The only remnants was the channel colour, really. This geddup has not yet been ported. However, following my vacation this week, I'll be looking into bringing them back. Thus, I'd like to see if anyone has any outstanding issues with this (the old ones, which have been overruled already with the initial introduction of bluesec a year ago, not withstanding). What I'd also like to see is if there are any opinions on what sprites should be changed/redone. I know that our set wasn't completed until the very last few months, with sec borgs and RIGs being red even after a long pause. This will obviously be rectified from the getgo this time around. Was there anything else we missed? Also, what to do with command? With bluesec, command was blue with light blue highlights, while security had golden highlights. But I think this is far from an idea solution. As such, what other options would there be on how to make command more easily stand out? Images of bluesec in action:

Movement only would be better. You lost your power somehow. Chances are, you fucked up. Giving a radio would make the punishment for failure too lenient, IMO, as you can just scream for help and someone will come and get you. Communication > mobility, always.

For reference, he got a warning for this on 11AUG2016. If he meme'd over IC after that (over the past few days), please reply and let us know.

Application accepted into trial - 07AUG2016 We will see how they manage in the active dev team.

Application accepted into trial - 07AUG2016 We will see how they manage in the active dev team.

Application archived - 07AUG2016

Application archived - 07AUG2016

Application archived - 07AUG2016

Application archived - 07AUG2016

Application archived - 07AUG2016

Erm. Spacesuits ARE softsuits, though. A softsuit is a spacesuit that is not rigid, ergo, that is not a RIG or a Voidsuit.