Leaderboard
Popular Content
Showing content with the highest reputation on 01/22/2021 in all areas
-
2 points
-
This was a long time ago. > be magistrate >not in bridge >nukies announced >another person makes a bomb with *clap as trigger to set it off >I come back to bridge >guy tells me "we made a bomb to kill the nukies when they come to the bridge" >I clap enthusiastically in response ...... >bomb goes off >bridge blown up >people dead >people going capslock in LOOC >me dying of laughter >apologised to admins >become admin long itme later >talk to admins about that some time random because suddenly remembering the event >some remember the event, tell me they cried with laughter2 points
-
So actually been considering this for a bit now, only recently thought of it again. Now I know we have a screenshot thread HOWEVER, this is meant to be for totally out of context chat pictures from the Discord. It could be anything, just so long as it can easily be taken completely wrong when thought of/read out of context! Again; Discord only! NOT in-game! When possible try and include the name of the person that said it in the screenshot, just so everyone can bully thank them for their funny contribution. To start things off, I give you this;1 point
-
Hi all, This is a suggestion to bring the Blueshield up to standard with other aspects of the game. Our Cyborgs, Security, and Command have Standard Operating Procedures and scale that protect the Shift's fun. Command: Can't participate as their own Security Force, and are more confined by their SoP than non-command. Security: Can valid-hunt, but are limited by the Alert Level. Cyborgs: Laws limit them. Manifest limits them. And some OOC Round Quality Control limits them. An Engineer Cyborg cannot fortify everything into Fort Bridgetta, Fort Cargonus, Fort Briggton. On Green, or Blue. But they can start to do so on Red. -- These are powerful roles that are all scaled to the Round's progression. The Blueshield is the only role that has such an immense, immediate, and expected power-creep. They rush for the AA (All-Access), and the AF (All-Frequency) Captain items. What I suggest is that the Blueshield be limited to the alert level, and more closely follow their SoP and Job Manual. 1. Blueshield does not get AA/AF. 1.1 Instead, if a Command is targeted/ the blueshield get AA to that department. 2. Limit valid-hunting, or valid-verbally. (Things like hawking monitor like the Paramedic, and announcing for people to congregate to X location because Y is dying. Sure, if it is a Command Staff, go ahead. But being a hawkish protect of the common-joe isn't your job and it can hinder Antagonists. Let Security / Detective do their soul-searching). Supporting Evidence: 1. Captain's Manual: "You are NOT the hero the station deserves, and you are most certainly are NOT the one it needs. Just because Operatives are bashing down your door looking for your disc (Which should be in your bag, RIGHT?!) does not mean you should be making a heroic stand against them. Run as fast as you can out the other way and run even faster away again. If you lose your life, as pointed out earlier you will, at the very least; be handing antagonists the skeleton key to all unbolted doors, and at the very worst; the nuclear disc to Nuclear Operatives. Even if you are certain that you can take them on with a team of reliable(?) people behind you, then proceed with caution, and be prepared to yackity sacks it out of there, should things turn for the worse." - The Captain, with his AA/AF, is expected to pussy-foot away. So why would a less-equip, same AA/AF Blueshield not be held to the same expectations? A Blueshield has poorer weaponry, poorer armor. They're suppose to die for the Captain to protect AA/AF. Not rush an Antagonist while having the items he is protecting from being taken if the Captain were to die. 2. Head of Personnel SoP (which is essentially: Identification Computer Handling SoP) "The Head of Personnel may not give any personnel increased access without authorization from the relevant Head of Staff. This includes the Head of Personnel. In addition, the Head of Personnel may only give Captain-Level access to someone if they are the Acting Captain. This access is to be removed when a proper Captain arrives on the station;" It can be argued, that HoP SoP is essentially ID Computer use SoP. Which the Captain should be subject to. It's just if the Captain were handling things in the HoP SoP a lot of it is auto-completed, he can approve his own stuff. I like to look at this as limiters to non-antag command, to stop power-bloating. As a closing note I'd like to parody the Blueshield's Manual: "One very important detail of your job is that you are not Security. Do not let your Security (and Detective) access fool you. Your ID lets you reach every single Command Office on the station. You should not be concerned with the goings-on at Security, nor should you be doing their job for them. You are not a Security Officer with a private office and snazzy outfit. You are a bodyguard." -> "One very important detail of your job is that you are Security, Medical, Science, Service, and Supply. Do not let your lack of authority dictate what you can say in command comms. Take advantage of your Captain Radio and turn advise into statements. You graduated the top of your class. You have all-access, and you should use it. Protect the Captain and HoP who have all-access from dying, by dying yourself. You didn't hand over the keys to the station, you simply died a bodyguard who happened to have worse equipment than the Captain, while sharing the same AA/AF." SOP would be 5000 pages long if it covered every small, loophole. All Access should be reserved for Captain. These balances are already on the Manual (wiki page for Captain and Blueshield) but because its not in the very short SoP list, people think otherwise.1 point
-
Have players report issues. Especially security officers. ANYONE hearing someone saying "X killed me" could report to admins someone is breaking CMD. Also, while you have 150 people, death can only happen in a very limited situation (I.E. a valid death), which would limit to max 2 people per antag... possibly more due to circumstance. As for actual punishments, it would be best for admins to decide what would they be, if they be interested in implementing that. But after so many community meetings and talks with admins its crystal clear they wont ever, so i dont think this discussion will go anywhere. As for assasination objectives. keeping all people in the round would have adverse effects. namely ghost roles, ERTs, midrounds, summons (like holoparas or cult ghosts), golems, borgs, etc would have a much harder time finding players to man these roles. Having your round ended early is a bummer, but that is by no definition, end of the game. Can always play the game, just on different terms. (can always go drone)1 point
-
Personally, I like the possibility of being ambushed and nearly instantly killed at any point in given time. Adds a bit of paranoia and to the danger. It's only annoying when you are assassination targeted multiple rounds in a row, perhaps even by several traitors (and of course if the traitor is sweaty stealth kill into decap into microwaved brain). Then again, it's been ages since I was targeted via assassination objective and actually killed, and most traitors don't do the sweaty tryhard strat, either from not wanting to or not knowing how.1 point
-
this won’t really fulfill the 'traitors won’t need to worry about the target being revived' part, since as soon as they’re cloned you know the "ZZQR^* ZQLEE THE SKRELL KILLED ME TWENTY MINUTES AGO IN NORTH ARRIVALS MAINTENANCE, THEY ARE A LIBRARIAN WEARING A RED VICTORIAN SUIT, JACKBOOTS AND A TOP HAT, THEY KILLED ME USING A SILENCED-STECHKIN WITH INCENDIARY AMMUNITION" is coming out, so traitors will opt to perma-kill them instead.1 point
-
1 point
-
1 point
-
Yeah, I agree. While a game-community issue. It can be influenced by ingame limitations. Be it the rules being updated, or the ingame start being respected and looked at more. e.g I don't want to see Blueshields, when Command is stacked. Having authority (when they do not have any) to change AI laws, call shuttle, contribute heavily to the RP scene of Command decisions. They can comment, but shouldn't be a raging wizard about it. Too often the Blueshield RP-breaks to snide-remark or comment/enforce an idea, action or other. To create a false authority. This is enabled further through Captain ID, Captain Radio. OOC Blueshields need to be looked at with more focus. It's an extremely powerful role, that is suppose to be limited, but has lost all those limitations through social engineering within our community. It is simply assumed that a BS now gets AA / AF. Can now get away with Redshield/Changing Laws. Mind me, though. That the lee-way is very much curved to Security as well. Who can unlawfully shoot, baton, or other - space law crime, and simply get ignored because #It's only Minor. Which baffles me since it may as well not be included in Space Law if no one, IC or OOC tries to properly enforce it. The few times as IAA, Magi, or other that I try to tell Blueshield or Security off via reports or spess law, its often responded to with - 'but y its minor crime...'1 point
-
Since this PR has been added slings have gone down to a 5% -10% (I guess I personally have never seen them ascend since the PR) win ratio. Do you think the PR should be reverted or other changes must happen? What are your thoughts. Ill add some ideas as I think of them. I have seen rounds be murderbone sec, ERT be called by command and them lose over and over. Maybe the duration of thralling someone lowered or even the cooldown be brought down? This will allow then to have a faster playstyle and encourage the round to be quick.1 point
-
When mindshields became sling-proof, it only downgraded the game mode to revolution with more steps, except worse for shadowlings. In revolution it made sense to make revs harshly curtailed by mindshields because it was a good balance to the fact that revs can very easily recruit because it's merely a click to do so. Slings don't have this benefit. Conversions are much more laborious on their part. The problem wasn't really that slings 'snowballed' because there's not really such a thing for slings, imo. They're just winning. When cult wipes out security and starts converting people en masse, they're not 'snowballing', they've just removed the only obstacle that all antags generally have. I'd posit that the real problem isn't that slings 'snowball' per se, it's just that they can win very early and very easily by getting the drop on security before security really has a chance to actually react to their presence and the fact that victory can be so assuredly locked down so early in the game makes people not even want to try to fight back and just slip into apathy as we see ascension 20 minutes in. Maybe a better solution to this is to prevent the potential for an early game locked in ascension by preventing slings from melting mindshields until they have a certain amount of thralls, or requiring one or two thralls to be present for the melting of a mindshield. This contrasts with the current change that pretty much guarantees a crew victory or endless murder bone depending on the ability to mass mindshield. Now if security is captured and enthralled it's often after the crew has had time to actually call out the slings and at that point security should be able to put up a worthwhile and fair fight, meaning that victories are earned rather than quickly stolen like a round start teleporter emag. If we're going by the original PR that made this change, the problem was that security was getting thralled and causing the slings to 'snowball' (i.e., win) and if the problem is that security shouldn't be able to be thralled, I don't understand why mindshields were made sling-proof, because that goes far, far beyond the original scope of the problem and just seems like the nuclear option rather than the sensible one.1 point
-
I did predict this happening. The PR put shadowlings into the exact same ballpark as revolutionaries, with security encouraged to immediately bumrush cargo to order implants, and slings inevitably forced to go lethal or die once the crew has started to become implanted. This doesn't make for good gameplay, and I wish the PR that changed this feature had been put on hold a bit longer to be discussed more. Frankly, I'd be down for just outright reverting the PR that changed this all in the first place. It turned something that was debatable as an issue in the first place into a massive gameplay problem. For most, the gamemode is no longer fun or even interesting to watch.1 point
-
Be AI. (W0LF.ai) CE can mist as a full powered vampire and cards me, everything off. Robot chat gone ignored. CE walking past CMO, security, random crew. Me trying to *scream to get attention. 2 security Voxes heard but could not locate me. CE misted in vault. Threats to kill me if I continued. Continued anyway knowing they wouldn’t. Command finally notes I am missing after 30 minutes. Random Vox who I screamed early commented that they did hear me when CE walked by. CE uncatchable, eats a random crew in arrival escape pod. Sec Pod did find CE but was quickly floored and thrown to space. I get yelled at in OOC for not getting anyone’s attention. *shrugs*1 point
-
>Be Borg >Swarmers followed by Terror Spiders >Manual Quarantine Lawset >Terror Spiders not dealt with at shift end >Oh no > 1v50 at escape as single borg >Die1 point
-
Tator fakes stumbling in the arcade and dropping a pizza box. "Hahaha, that's obviously a pizza bomb" I open the pizza. It's a pizza bomb.1 point