Shadeykins

Or how about... Round is over and has no bearing on anything. And is therefore not even IC, and requires no explanation. Once again I'm solidly against this. And poking fun at this and trying to legitimize the removal of End of Round "grief" certainly helps. It exists because it's impossible to manage an end of round hugbox which leads to a fuckton of pointless ban appeals. More Work, with no benefit < Less Work

*Gasp* They're doing it wrong! All you need is three things of C4 to kill the AI. ;p

They do, yes, but because they're typically overpowered in 1-1 scenarios. They bumrush the player and are unstunnable. This makes them very effective in close quarters, and hilariously ineffective in every other situation.

It wasn't even remotely one of the reasons why the Gauntlet away missions was removed. That was removed solely because of the risk/reward.

If you don't like the disadvantages of playing a race, you shouldn't really play as them. Kidan are relatively balanced, and trade off this sort of "standard utility" to be all around more resilient (which is a huge advantage outright).

I don't really consider an antag getting a victory as a mistake. There's in fact very few things I consider to be a mistake given the length of rounds and the fact that this isn't a "persistent" server. It's not really the job of anyone on station to definitively deny antagonists greentext possibilities if they aren't outright violent/obvious. Anyways, very seldom does BYOND actually crash at round end. Typically I only ever crash when Narnar gets summoned and I'm right there.

I fucking hate it. I want to see all the antags I've failed to catch as captain/security/AI/validhunting NT Rep so I can be better suited to catch them in the future. A BYOND-crashing bomb basically impacts my learning experience. I sincerely hope this is satire. If it isn't, it amounts to "I want to look at who was antag that round, so I know who to metagrudge."

Make sure any lore changes are thoroughly reviewed/approved by the 'min team as they have a direct impact on the server as a whole.

And then I absorbed you in the MORGUE. Also, Halogen is female. ;p

It is how it is because it's going to happen anyways and the admins don't have the time to adequately deal with someone "griefing" with only sixty seconds to go. There's simply too many attack logs and too much going on in that sixty seconds to even begin to keep track of everything, or bwoink people, or figure out what's even going on. The only thing removing post-round "grief" does is create a massive workload for admins, and punish a bunch of people for actions that are literally - in every sense of the word - irrelevant. What occurs post round has no bearing on anything whatsoever, it doesn't affect the round (since the round is already done) and it doesn't affect future rounds. I like to think it also casually prevents metagrudging by giving people an opportunity to let it out on someone and being bloody well done with it. Comdoms for instance get super lynched post round, and they're rarely ever talked about beyond that (Whereas I think there'd be a lot more whining if everyone had to behave that last 60 seconds). No, no, and no.

Actually that's a brilliant idea False. Make the syndicate keys use randomized agent names, or better yet... Give it the ability to choose a preset name when you buy the key. This way even if security gets their hand on a key it doesn't automatically out every other traitor, and allows for some interesting plays. This solves the voice changer + encryption key issue too. Make sure to update the encryption key description if this happens to boot, maybe stating the radio handle and that the user will be anonymous/have their identity protected when speaking on the channel.

The NAD is unimplantable, but can technically be implanted by putting it in a box and implanting it. It's also a great way to get bwoinked for deliberate use of exploits. If the nukies kill the Captain, who has the disk, they by all means should have the disk and not have to spend 30 minutes trying to do surgery - or gibbing the guy (which destroys implanted items, for reference).

Basic programming logic would figure that the restock units don't actually exist until the machine is deconned, at which point it's inventory no longer exists either. Without some major changes to the way things are constructed (Since all things in essence do exactly this), it's not possible to have it "track inventory". There's also no real point. This went from "Make vendors deconstructable and more boards craftable" to "how can we nerf the shit out of the autodrobe for no good reason?" I have no idea why you would want this, honestly.

As commits can be easily reverted, there's no real reason for you not to go ahead and edit the wiki if it improves layout, or makes it better and easier to read. This was one of the things I wanted to get around to at some point anyways, so! Go for it. We really need a table with those values.

2 TC may be fair in the scheme of things, yes. I'm not going for fair. I'm going for "What encourages coordination, and more interaction between traitors?" This not only have the possibility of reducing over the top antags (Because it allows traitors to coordinate, and thus be more discreet/avoid security and other situations), but also lets some more interesting schemes be pulled off and roleplay between traitors to flourish. Right now the cost of coordinate is actually 5TC, because you're also going to need a voice changer if you want to talk on syndicate radio, as security generally gets a key at least once or there's always at least one traitor who will rat everyone out so they can sit in an inescapable hole for the rest of the round rather than die. 2TC may be fair, but if 1TC creates more interaction between players it's more than worth the change. Here's another thought - let taters start off with a traitor enabled radio key, and change the encryption key to be solely comms monitoring and 1 TC. More or less every other antag can communicate and coordinate with one another in a reasonable fashion without sacrificing any of their utility which tends to make the rounds more interesting. Traitors can't, and actually have to spend a fair chunk of their utility (1/10th, or 1/4th) in order to communicate and coordinate effectively. A lot of people tend to find the roundtype boring when it should be anything but, and this could be an equitable way to address that. If it doesn't work out, it's just as easy to remove.

The logout button does not log out when you are at security level 0, because security level 0 requires you to only stand at the ATM and click it to work. Set security level to 1, or pocket your ID and click logout.

As of now a screwdriver and a crowbar are all it's needed to get a full (duplicated BTW) restock. Screwdriver, crowbar and multitool = infinite syndicakes. Current machines can't spam anything that is much of an issue I think, but if all vendor machines became able to be infinitely restocked that way it'd throw off the balance I guess -- maybe not since it's still boring to do unless it's for giggles or to get a restock in a pinch, but still... I am aware. Thoroughly against the idea of losing restock units, or having them have "counted inventory" for the exact reason I am against the Autodrobe having a finite amount of certain items. The only way I might potentially agree with this is if you made restocking machines also part of the janitor's job, or have a flunky engineer-type role known as a "Maintenance Technician" who's job is to fix small things like this and restock vendors.

If that's the case then you should require the restock units as part of the construction and make it the only item that is not returned with deconstruction. This shouldn't be a hard edit to make Thoroughly against this idea. You shouldn't lose the restock units upon deconstruction.

Good to know. :H works just fine since the syndikey is always inserted into a headset after the initial key is in. Can we please discuss the original topic?

Individual vending machines have no boards printable for them whatsoever for reasons unknown.

It's the :h channel.

Changes and bug reports should be on there. Any form of discussion should not be, as the bulk of the server - and even the forum users don't use/look at the github unless linked to it directly.

I don't have the time nor resources to pay attention to multiple sites at once, which is why I was thoroughly against GitHub in the first place. It removes a good amount of community feedback and shouldn't be used for discussion - regardless not the place to discuss this. It sounds like it wasn't mapped properly. I'll maybe take a few pokes at it.

It gives you access to the :h channel, and allows you to coordinate with other traitors.

Yeah but clicks are a sound people can try to mimic. I mean we created tools and communication devices that use clicks and click-like sounds to share information. It's kind of different in that respect from strange sounds. I meant on the server. I'm pretty sure it doesn't parse as a bunch of text. It parses as the kidan making clicking noises (unless that's been changed). I don't think that everything should have to visually make sense in terms of language. We're talking about a wide variety of alien species here, who's to say that everything spoken must parse in an even remotely understandable way?