CatsinHD

I am, like many people here, all for making a rule restricting the use of "below-deck" work, especially during events. However, buy in large I am not adverse to the general use of "I had to do some maintenance on rooms below deck" and that general concept to explain why characters may have been gone for some time as long as it's within reason. This is entirely for people trying to claim heroics during a canon event they had no joined. It may not have a complete logical throughline, but that is less important in this situation and must be stored away with the other gaps in logic that are present when dealing with the messy world of off-server RP and continuity.

I am for this, as I am with most things that add some complexity to areas of med that could use it, especially as it gives Physicians a way out of the GTR clogging "awaiting bone surgery" scourge. I would like to see maybe some ideas on how fast the bone chem works since I feel like would end up being the deciding factor between bone surgeries disappearing except low-pop and having a semi-regular discussion on which treatment would be the better option. Ideally, it would be slow enough where surgery is the faster option, but not so ungodly slow that it nukes itself into uselessness. That way surgery is still useful when there is room in the ORs, but the physicians are left out to dry when John Sol rushed the mercs and got their bones giga-blasted. Obviously this should be discussed, though, as I imagine some people disagree. Regardless, love the idea and also agree with what Rooster said (especially the name). +1

The original decision for what's listed on the wiki is lost to time, as is for the age requirements in game. They likely don't line up because one got changed while the other didn't. Those requirements can be changed to fit whatever they need to fit on the wiki, in-game is another question. Don't sweat over what the wiki says too much, there's some requirements listed on there that don't make a ton of sense but isn't dire enough to take priority over other projects.

I like the idea quite of lot of renaming and changing the duties of XO and OM. On fact, it was my original suggestion to rename XO rather than make it 2iC, although my suggestions were Chief Bridge Officer or something similar. I will note on the topic of enacting acting captain, there is already procedure for this on the Chain of Command page: https://wiki.aurorastation.org/index.php?title=Chain_of_Command#Appointing_an_Acting_Captain The process is as simple as it looks on there. It is just a majority command vote, that's it, and there's no plans to change that.

I does work in my experience seeing as it's basically the only way I interaction with job closets. It can sometimes be finnicky, alt-click an adjacent tile until a tab called "turf" appears in the top right. Usually it will also open up automatically, which should make it easier. That aside, I thought the trash bag already had auto-pick up by clicking on the tile. Either way, I'm for it.

Binned due to OOC reasons

Oolong Cow and others have all made basically the same points I hold onto. As a medmain, it is especially tiresome for the inevitable call for a medic, the medic declaring ling dead, then minutes later hearing "This person just came back alive wtf!!!!" and medical freaking out because "my hud said they're dead, this is impossible!!". I have seen perhaps a handful of good ling rounds by players that I know and recognize that happened to have prefs on, and tried something different. It was still ling, with the same process of kill/capture/science or sec/repeat/die, but they managed to make it fun for the VERY few departments involved. Yet, this example, as I mentioned, was still the very annoying loop that is ling, and was marginally better IN SPITE of the gamemode. Suffice to say, I am tired of seeing it in secret. If someone comes up with a cool gimmick, or the server really wants to have a ling round (and hell, perhaps the absence of it in rotation means the few ling rounds that get voted are genuinely interesting), then people can still vote for it. As for developers and reworks, I also agree of Oolong Cow. Don't play expectations that aren't entirely guaranteed. Everyone on staff volunteers their effort and work, so whether something does or does not get done is never certain. Limit your scope, review the details, make action, see the results, repeat. I would go on with my own suggestions and thoughts on antags and a ling rework, but it would be out of the bounds for the scope of this thread, so I will simply deposit my +1 and move on.