Skull132

Application was accepted and Moondancer reinstated as a coder. Locking and archiving.

The same mentality is applied to Github. If you are unable to adhere to the rules, and start wasting the staff's time by making joke edits, attempted griefing, etcetera, then you will be banned. Because, again, you're wasting staff's time and effort. We're here to deal with legitimate input.

As a short update, the development staff are having a meeting this weekend to decide on the initial plans of what's going to be implemented, and how. Stay tuned.

Aand. The wiki is now open. Login with the forum username and password. Note that usernames with certain symbols (specifically spaces) do not work. You have to ask an admin (or me) to change it on the forums for you. Note that because the two systems are linked, griefing or general idiocity on the wiki will result in a forum ban.

The logic in question is inherent to people who have a flawed understanding of biology and diona. They're not actually trees. They are not weeds and most likely don't have the easily targeted biological structures your common household weed has. Which is why plant-b-gone will never work on them as if it were some super-weapon. Further more, the volume of spray introduced into the body through the skin would be so minimal that Diona, being on average larger than humans, would have no trouble filtering the toxins out before it actually caused damage.

The moderation plugin has been installed and is currently being tested by the wiki team.

We're 79 posts in and running in circles. Whatever worth this thread might have had has either been eroded or absorbed, of this I am certain. To quickly address your points as a closing statement, I'll say the following: 1 - Assigning malicious intent to people without evidence is a sin and you should never open a thread with such idiotic accusations contained within again. 2 - Already implemented. The values can be tweaked if deemed necessary. As I am certain you remember, going full retard on a crusade is not smart. Precise and calculated tweaking of subtle mechanics will produce more desirable and less combustible results. 3 - Arrow's already on that. 4 - Healing's touchy, due to the fact that we must maintain a veil of believability. Again, stop thinking immediate gameplay rewards, as you tend to do, and think outside of the box. 5 - See above. 6 - I kinda like this one. A lunch break at a random point in the round would be neat ambiance, I think. Anyways, that's all, folks.

Server's back up. Yay for victory.

Update. Storage failure confirmed. Currently on a temporary setup, backing up the VMs. The drives will be swapped tomorrow once our backups are complete, and then we will most likely be required to reinstall the entire system. So ye. Roughly 20 - 48 hours of downtime left, depending on how much difficulty we run into.

Around 1700hrs GMT+0 the server became sporadically unresponsive. A quick inspection revealed nothing, so we have requested a full hardware inspection of the box. We suspect that the physical RAID controller of the server has failed, but this is still to be confirmed. We will see once Hetzner gets back to us. In the mean time, we have confirmed that our data backups are usable. So in the case where our hard drives are unrecoverable, we have the important data (characters, bans, player records) fully backed up as of midnight yesterday, 22AUG2018. At present, we are waiting for Hetzner to diagnose and fix the issue. Once they've done that, we'll see what needs to be done to get everything back up and going. Though, this will most likely take place some time tomorrow. I will post updates here as the situation has meaningful development.

This is more about server direction, than changing a specific mechanic or device.

So, the time, has come. Since I've written up a large enough document explaining all of the technicalities, let me cover the general basis instead. We've been doing roughly the same thing for about half a decade now. Well, the development team is now looking for ideas on how to change that. Specifically, we have a plan to implement larger scope projects in vain of the New Map Meme. We are looking for something which can be broken into chunks, implemented in an iterative and feature list based fashion. But, at the same time, such a project should change something about the core of the gameplay experience we've been enjoying for the past half a decade. Well, it should enhance it. Note that originally this was considered a staff only thing. This is where the more technical requirements stem from. But since some members of the playerbase have expressed an interest in generating ideas like this, we decided that we might as well include the opportunity for the players to get involved. The general breakdown of the plan is as follows: Submissions for this are open for 2 weeks. So expect a cut-off date at around 25-26AUG2018. Following this, the developers and the leadership of the server will go through all of this shit and create a concrete plan for what to develop. (Note we may pick more than one project, depending on their size.) Said plan will be reviewed publicly. Said plan will be executed in a bite-sized fashion. With that said, here's the fuck-off form. With instructions on how to fill it and how to submit it. General discussion here is welcome.

Musical instruments have a shit implementation for transferring sound files. One which bogs down clients with slower connection speed and disk speeds. I would rather not see instruments get given wider access until they're made more sane on the back-end.

General: Plasma = Phoron. (Used primarily by engineers and miners, but still general.) Phoron = Plasma. (Used primarily by science-y and well educated people.) (I might append to this list at some point.)

I thought it was because of Resilyn Was CH even nerfed? No nerfs were done during the time of Resi, so uh, :shrug:

Link to PR, for reference: https://github.com/Aurorastation/Aurora.3/pull/5067

Arguably a bad solution for the problem. Yes, AIs are powerful things that can and will and do regularly ruin antag rounds. However, simply plucking it out of rounds based on arbitrary stats does not solve the problem. It hides it. A more coherent solution would be far better.

One thing that could be added is the requirement to inform the journalist and what information needs to be contained in such a notice.

Some points. First, you need a minimum still. Some rounds, most notably team based one, have a minimum player count past which they cannot be scaled. At all. End of. Second, you will need a maximum. For ostensibly the same reason. Imagine a round with like, 5 or more lings. There's a sensible limit past which single antag modes get questionable (they weren't balanced for it, meant for it, etcetera). Your options at that point would be to either: scale to that point and stop. And accept the fact that you can potentially have scenarios of 70 players vs 5 lings. Or implement some form of more dynamic round make-up. Like giving each round a secondary antag type which it'll start to spawn in as it reaches its maximum threshold. Third. The percentage idea is really weird to think about. So uh, for the sake of making maintenance and clarity into a thing. Call it a ratio. Because it does the exact same thing, but it's way easier to imagine a ratio of 10:1 than... 10% crew must be antag. (The difference is easier to illustrate with less round numbers. And in general, a ratio is used to describe this things more commonly.)

Why? I can only presume you're using the APC to toggle atmospherics power of the room. But that's not a good solution either. Go look in the science gas mixing/cold chamber. It uses air injectors and controllable extractors. Without the need for extra APC or anything of the like. Or, again, use a large, stationary scrubber that's sitting in the corner of a cell. Controlled via a single computer which I'm sure you can find a way to accommodate.

Large scrubbers take up one tile. Just punch out the corner where there is no camera. Or implement proper scrubbers with piping. I do not see how space is an issue. As for the intended use, it still wouldn't work properly. Because, again, there's no way to clear it. If you want to just give them one gas chamber, then just give them one gas chamber, but still make sure that it's functioning properly? The old station had a singular space ventable cell. I don't see a reason not to only have one gas chamber.

You're trying to defend the implementation of a completely maligned system by saying that the alternative is too efficient. All similar systems on the map, where you can inject gasses into (furnace if we still have it, sciences two gas chambers, the brig) a controlled space, have effective scrubber setups. I am not seeing the point in making an exception to this convention.

Okay so here's a bit of a long winded deal about what I'm looking for and why. First, let's establish this: both sides can abuse these mechanics without any enforcement or policy. Captains can D-notice stuff until the cows come running home, and journalists can do things like leak security information to antags and so on. We have people who've abused both positions and have been warned, banned, etcetera for it. So whatever methods of handling are chosen, the must address both sides. Second, let us concede the fact that there has, thus far, been minimal or no policy surrounding D-notices. This means that any example of, "Look at how often this happens!" must be taken with the grain of salt that no one has had a major reason to consider acting a certain way about the issue. Nor have they had official guidance, meaning they have applied their own sensibilities to the matter in an unabated fashion. As such, the status quo is not a valid enough reason to request mechanical enforcement until the policy based solution proves ineffectual. Third, as we have established, there are valid circumstances where the Captain and command staff in general need to immediately D-notice a journalist's entry. Specifically in cases where the information contained in them poses a credible threat to personnel safety. Obviously the journalists have a responsibility to not commit actions like this, but it is probably saner for everyone involved if the Captain can D-notice and cut out critical mistakes. Now, minor violations of this are not a large enough concern to merit OOC intervention. This is my opinion. There are much harsher crimes which are punished ICly, not OOCly. A singular violation, with policy in place, would generally indicate a mistake. A mistake which can be rectified with IC guidance from the CCIA. In fact, it is my belief that this is exactly something the CCIA should be doing: establishing IC policy and making sure that it's adhered to. Resolving minor IC conflict is something the CCIA should be capable of, and their literal job. Of further note is the fact that this policy can easily be violated by either side in a fashion which does not conflict with the current rules. So again, CCIA realm vs Moderators. While discussing this in Discord, there were concerns about the capacity of the CCIA to enforce something so "important". At which point, I suggested that if CCIA are unable to do their job to the degree which is required, then that should be improved. This is not some magical unicorn. This is another piece of IC policy which is established to support new mechanics. Another day at the office. Or at least it should be. TL;DR: keep it IC. Seriously.

One example I immediately thought of is a journalist helping hostile forces by leaking security information out into the public, for example. Corporate secrets is another.

Yes there is. The air scrubber that is provided. That is. Not a good mechanic for doing this. Nor the standard one. Either do what research does and implement those large scrubbers with remote control, or implement a drain system in there. At present, there is no way to clear the pens without leaking the gasses and putting yourself at risk.