Kintsugi

Going to play devil's advocate here: The scuttling device doesn't need secrecy. It is common knowledge the ship has one, and it is totally inert and safe unless the SCC provides a code to detonate it. If anything, it is good that it is outside the bridge. In a situation where you actually need to scuttle the ship, you don't want it to be isolated (and therefore vulnerable) and hard to get to. You want it to be in a location that is easily accessible and easily-defended. As for the vault, I guess there's no harm in having one... Except that I've always found that "rob the vault" gimmicks are very, very boring. The contents of the vault are meaningless and vault gimmicks just tend to not be engaging.

I am not suggesting we mechanically remove artifacts or golems. I'm just saying all we should do is decanonize. Their mechanics are, as such, irrelevant in the course of this discussion. "Rework don't remove" is a platitude repeated since time immemorial, one that is empty and has a similar outcome every time: here's the fact of the matter. It's easy to say "rework don't remove", but it's a lot harder to actually make that happen, and hoping someone else is going to do it just isn't going to work.

I'm going to keep this brief. Perhaps on account of the setting change to the Horizon, we've recently had a number of situations where golems and especially artifacts (in one situation, a machine that makes crabs out of thin air) appearing ingame. While these are fine in the course of gameplay, they are largely incompatible with our setting and dissonant with our tone, as evidenced by the frequent mentions of these entities in the relay and the cyclical and bizarre conversations that they bring about. No, I'm sorry, machine that draw out your blood and turn them into green blobs of flesh or create infinite sources of food don't belong in our canon. Artifacts and golems are technically canon, according to the bluespace page - https://wiki.aurorastation.org/index.php?title=Bluespace#Artefacts - however, this lore is nearly a decade old and is a relic of a time when Aurora was a much sillier server. It doesn't have a place on our server. I suggest that all golems and artifacts be decanonized. Perhaps in order to give xenoarcheologists something to talk about, people could be allowed to ahelp to ask for explicit permission to keep an interaction with an artifact canon, provided it is one that fits more in line with our standards as a server. But otherwise, I see no gain in keeping artifacts canon and I am getting tired of seeing them referenced in IC mediums and derailing conversations and interactions with bizarre tonally-dissonant tangents.

I closed the PR. At the end of the day, regardless of my personal feelings, any change with public opinion so decisively against it as this one just isn't a good idea and shouldn't be pursued.

>Then fix him, or suggest for someone else to do it. No. "Improve not remove" is not a valid reply. If you want it improved or fixed, it's up to you to code that, not me. >This is a trope that is absurdly common in fiction where people keep otherwise hostile creatures as pets. She's a baby who's being cared for by humans. This is a thing that happens in actual life with otherwise hostile animals. I don't really care if it's a fiction trope. Fiction tropes don't guide design. >They literally can be in the modern day, let alone in the future. Science experiment in Russia. Frankly, I don't care if there are a few supposedly domesticated foxes somewhere in Siberia - dancing bears aren't okay for the station, either. >I say again, fix him or get someone else to do it. No. "Improve not remove" is not a valid reply. If you want it improved or fixed, it's up to you to code that, not me.

This thread has been created as required by PR #14173 (Animal Control) https://github.com/Aurorastation/Aurora.3/pull/14173

Made at my own behest for https://github.com/Aurorastation/Aurora.3/pull/13830 How do you feel about this PR and its many changes? From sanasomnum to the TC count buff to the armory restock to others. Anything you feel could be better or would like changed?

Might be a little nebulous, but maybe a checklist of sorts? Otherwise I'd go for a clearly visible identifier of departmental affiliation, like an armband/badge/hat/other large clothing item in departmental colors.

No, it isn't fair. Whether or not the rest of the crew wears their uniforms is not relevant. Every player for every other department in the game could happily wear their uniforms, and it would still be irrelevant to the point this thread is making. There is no regulation requiring other departments to wear their uniform. They have the freedom to choose, security does not. Ergo, not fair. It is not fair to force security to wear their uniforms, when every other department has the choice between loadout items and their job uniforms. Again, not relevant. This thread is suggesting that the requirement be changed so that: 1. Security is allowed to wear business-appropriate clothing 2. As long as they are easily identifiable as security. Clearly, your examples run contrary to the suggestion made by this thread. Again, not relevant. This is a strawman. See above: We are saying security should still be easily identifiable as security. One does not need to wear the uniform to be easily identifiable as security, as a plethora of items exist that make them identifiable as such, including:

What it says up there. Frankly, at the moment, security's uniforms are a highly contentious thing to talk about in regards to our community. This topic is not about whether or not they're good. It is about how this regulation arbitrarily restricts security from enjoying the same freedom of loadout use as the rest of the jobs on the server. I don't need to write up an essay justifying my position on why this is bad: It's just not fair. The regulation isn't enforced as it is, with most command characters wisely avoiding bothering to force officers to wear uniforms that don't aesthetically match half of what we have on offer as far clothing sprites on the server are concerned. Change the regulation. Officers are no longer strictly required to wear their exact uniforms - instead, business-appropriate attire along with being identifiable as a member of security at a glance should be enough.

The images were created by https://github.com/openai/dall-e , as per their license https://github.com/openai/DALL-E/blob/master/LICENSE all images created by me belong to me, credit should be given to the project itself as well, however.

Lore Impact: Small Species: Human Short Description: A number of minor additions to the Visegrad page that didn't make it into the original release. This includes some reference images (AI-generated - consider it an experiment), lore for cities, an additional city, some changes to Visegradi Creole and to the politics section, and a new section on the Visegradi-Plutonian enmity. How will this be reflected on-station?: Character backgrounds. Does this addition do anything not achieved by what already exists?: Yes. Do you understand that the project may change over time in ways you may not foresee once it is handed over to the Lore Team? Yes Long Description: https://docs.google.com/document/d/1dDSB81pW7Oi4t6KM7rhp4Xju3da6tSa3GknFczYNYVQ/edit

Changeling's potential for developing a narrative is pretty much tapped out. They don't have the tools other antagonists do for narrative development, and at the same time they're individually quite weak and are focused for stealth on a server where stealth is dissuaded. I don't hate changeling but it's one of those gamemodes we have, like vampire or cult, that is showing its origin as a flawed, objective-based gamemode that mostly exists in the modern day for the sake of "variety". At the very least I can tell you just about every changeling round I've ever played on Aurora has felt the same as the last, unless the ling in question got horror form. This isn't a matter of ten bad rounds, but of hundreds.

Wait, what's the NBT? Why are we switching maps? Are we a milRP server now? I don't want to play on a ship, why would my character leave Tau Ceti?

I didn’t realize Aurora’s seriousness was up for debate.

Do you think mercs and raiders should get overmap-capable shuttles? I am personally of the mindset that we should give them such, on the condition that they must nonetheless engage the crew in some way, instead of flying around the overmap and doing their own thing. One thing to consider is that it may be necessary to buff security voidsuits - security's voidsuit armor is paper-thin for anything other than melee combat, which means a boarding operation is nearly-suicidal.

The Aurora lore universe is expansive - probably the most expansive lore any SS13 server's ever seen - deep, nuanced, interconnected, and constantly evolving. Let's say the story's coming to a close: the year is 2050 and Aurora, the last surviving SS13 server, with a population of deep cover FBI agents and semi-autonomous bot-players, is finally shutting down - and the loremind (an artificial intelligence devoted to developing Aurorastation's lore, based off of brainscans of every member of the lore team to ever exist, and myself as well) has decided we got the Bad Ending. What does it look like to you? What do you think Aurora's Bad End is?

In light of the recent intensive and targeted griefing the manifest has sustained at the hands of an apparent community member who frequents the relay spanning multiple sheets now, I am unfortunately presented with an unpleasant situation: give up on the manifest, simply accept the persistent griefing moving forward, or try something new: an invite-only manifest. I have decided to do this on an experimental basis - my primary concern is that moving in an invite-only direction will kill activity on something that already struggles to maintain much activity at all past the first week of a new sheet. As such, from May 1st until July 1st (spanning two sheets), the manifest will be coming back. To gain access, you'll need to DM this account - Bone Courtier#4585 - which can be found in both the main Aurora discord and the Relay discord. Do not DM my account, please - just the one listed. You'll need to send it a gmail address - it doesn't have to be a real one, and can be a throwaway - and the name that that gmail address is associated with. For example, my gmail account could be sneedfeedandseed@gmail.com, with the name Charles Sneed as the name associated with the account. This is important to keep track of who is who - all edits made to the sheet will show up with the name associated with the account. From there, I will let you know that you have been added to the manifest and you'll be able to edit it freely, and hopefully without risk of griefing. This new manifest will also feature a few new relations on a trial basis - envy, contempt, disgust/discomfort, and nemesis. Additional ideas welcome. If these prove to be poorly received, they will be removed. Here is the new manifest: Click this - It will not be open to editing until May 1st, and only those added will be able to edit it, obviously.

I disagree completely as far as ERTs allowing you to play legitimate characters is concerned. The fact of the matter is that the frequency in which you have opportunities to play an ERT "character" and the time window you're presented within a round completely prevents you from achieving meaningful character development (and that fact their very involvement is non-canon in the first place). An ERT character played once a month for an hour window at each time and is immediately forgotten is hardly a character at all - merely a story element, a deus ex machina that arrives to change the narrative from its logical and fair conclusion. Third party ships spawn more frequently than ERTs, are around for the entire round, and can actually be remembered by the people they are involved with - just because the system they use to spawn in is the same as the ERT, doesn't mean they're similar in any respects. Finally, this isn't advocating for the outright removal of ERTs - it is advocating for the removal their automatic spawning when two characters arbitrarily decide "now is the time" by pressing a button on their screen. ERTs should be locked behind an admin decision, so if there really IS a need for one, and there really ISN'T any alternative, they can be sent in. For example, if no third party ship spawned.

The ERT is a controversial thing. It has a mixed reputation - some defend it as an absolute necessity to prevent rounds from devolving into total chaos as soon as security is defeated or outnumbered - others, like myself, feel it was a necessary evil that ultimately took the problem out of the hands of the station crew and placed it into the hands of faceless, heavily armored non-characters. Its sole redeeming factor was the fact that it could grant IC representation to lore factions that otherwise would not get it. But now the ERT is outmoded. The Horizon has more avenues of ending a threat that has overwhelmed security - it has the crew armory, more armed crew, and more guns lying around, available to be pressed into action in an emergency. As for the crew being wiped out, and IC representation for lore factions? Third-party ships exist to fill this niche. While there is doubtlessly risk of them showing up too early - the risk is the same for an ERT being called too early. And what's better is that third party ships can have consistent characters aboard them, instead of faceless goons that will never be seen again. In the face of the changing setting of the server, and the different mechanical situation ingame, I think ERTs should no longer exist at the beck and call of the ship. Don't outright remove them - but restrict them to being locked behind an admin's approval, like HAPT teams. If they're really, absolutely needed, an admin can send one. Otherwise, it's up to people actually in the game to solve an issue.

I think you might need more practice in intermediate roles before you go to head honcho command roles. Last night you were a captain during an admittedly-chaotic cult/vampire round that devolved into security having to act pretty much autonomously because you were largely absent, giving vague instructions, or outright conflicting instructions. All in all, I just don't think you're ready to play captain.

Chief Medical Officer exists Anyway, I support this. HoS is an awkward, unpleasant name

not well, they tell me I have seven hours to live

this spank guy sure is wild L-O-L

As I mentioned in discord last night, EE will never be a faction that can logically interact with the Horizon in anything but an unfriendly way, with the present lore in mind. It just doesn't work and every scenario presented to me so far has a logical rebuttal. Now adding a third party ship that is supposed to never interact with the Horizon is stupid; it doesn't generate interesting roleplay. Here's what I think: This is what I propose. That way EE would be able to exist and exist logically, while also allowing canonical interactions.