Lurapa

What. Never mentioned Staff in that comment. It's, for me, 1) Contractor is seen as High Risk, High Reward, but often is 2) High Risk, High Reward for lesser known players, Medium Risk High Reward for more known players. Players can conjure up any RP reason to assist Contractors/Vampires/So on. Donation is a IC thing that's been happening and is very easy to pull-off/justify. Donating blood, donating themselves to (the joke used a tonne by community) Brazil for free Vacation, donating ID/DNA sting. People can be drained 0% if they're X personality, or Y friends. The antag-aid rule is very passable. Has nothing to do with staff or how they enforce it. The rule is just as it is and exists. It applies to all resource antags. But that's not the point of this topic, Contractor and Hijacker. Don't want to derail this topic, so if you have further replies - can DM.

Contractor is an issue, within and without Hijack. Often you see people 'ask' to be sent to 'brazil'. - 'Can I borrow you for a few moments, paid trip to brazil'. - 'It'll be quick, won't hurt'. People often cooperate with the contractor. And after noticing that, it went from a 'high risk, high reward' playstyle to - 'Is my target someone who'll cooperate and has the RP for that?' Or if I'm someone known, who can just loosely play within the 'don't aid antags unless valid rp' thing. Contractor needs to dip from Hijack. And Contractor needs to actually be high risk.

I'd love to learn more about this topic. I am simply approaching it from a player perspective that almost every extended round is taken with adminbus liberties. It is why I went to a public forum with the suggestion. To create a dialogue. If I am wrong, then I can be corrected and learn from it. With that said fighting the meta of assuming a round type in game is not ideal, at least for me when playing/participating in rounds where that's the method. If it is wizard, or nuke, or blob. They often leave the shift in an irreparable state. Or if it is recoverable, it is often too much of a headache to continue. Its been years, and its the life-blood of many players, if not all players. When one screams WIZARD, it is like a domino effect. Priorities shift, and the shift becomes a focus of Station Vs Wizard, Station Vs Blob, Station Vs Nuke Ops. Each assumed round-type doing varying levels of harm. That rarely get remedied after the players deal with the threat, and try and continue the shift. What the focus of this suggestion is. Is to respect the circumstance, don't adminbus after 60 minutes of quiet and 80% of Security is cyro. With the adminbus being something Security would be needed to react to. To try and avoid fighting the meta, because the rare extended shift every 2nd day that fights the meta by giving us raging wizard blobs, won't change years of, for lack of better word, indoctrination to how rounds and antags are perceived. Extended needs spice, sure. But almost every extended round of recent has been admin bus'd into a chimera of various rounds, instead of extended with event. I for one hate extended as Security. With or without adminbus presence. Because as you said, with 1). The Greytide often becomes a strong force absent of antags/eoc. So you're already fatigued by the Greytide. And then varying quality of adminbus occur to put the nail in the coffin. - all in all, I personally don't like the notion of fighting the meta in a game mode like Extended. It would be more reoccuring, more prominent if present in a Discord post or Wiki page, or even a forum post. To redirect the path community takes in regards to meta. Like we could nerf the rule that allows Cyberiad meta-knowledge of all antags, and eocs, and how to deal with them. It allows for people to 4th wall meme, 'i heard shifts end after a wizard is skilled, its magic' loosely into IC say.

The main issue with shrooms is their ability to replicate, and our inability to counter that. With nodes, deleting all reliant shrooms. It would buff player practicability. And through that psuedo nerf the shrooms, not through lowering their luminosity, growth rate, or spread. But through introducing a new, reasonable way to destroy them. Both as Antagonist (animal or other) and as Crew. Above all else our inability to reasonably destroy them, is what makes them so strong. A shadowling will need to spend time, take damage, and is psuedo locked from using the shroom's weakness (welders). And while they're attacking it, it'll replicate. If we make it a node, and improve our ability to destroy. It'll boost Slings, boost Antags, boost Crew, and nerf Shrooms without actually changing how they work. Just how they die.

Start: Extended is a game mode that is needed every so often. It enables Engineering to plan, for Science to research, for Medical to hone their crafts. Overall it is a game mode where everyone but Security have meaningful progression. Be it becoming more efficient, trying something new out, or just exploring the Cyberiad as a new player. The Pros: - Expand gameplay/skill without hindrance (e.g hijack, assassination target, greytiders [because security can easily react to greytiding without whole other threats using up resources). - Science/Chemist/Xeno/Botany/Chef/Bartender get to perfect their skills via reagents, npcs. The Cons: - Security suffer from SSD/Cyro. As do Medical. Security need stimulation through prey and hunt. Medical need stimulation through mending/supporting. Suggestion: Protect Extended from certain adminbus by introduced guidelines. To help staff understand what sort of adminbus would be appropriate and add to a round, versus take away from a round. An example of this: 1. Don't give the illusion of Nuke Ops / Wizard / Raging Wizard early into an Extended Round. Why: Giving the illusion of Nuke Ops / Wizard / Raging Wizard when it is Extended tricks the Crew into - best to put it - a simple mindset. They arm up, they get access/improved access, they ignore aspects of their job they'd otherwise do, Space Law is skirted. And once they defeat the threat, they are left not with a 'Round is restarting in 60 seconds' but the ticking of their shift timer. The high, the adrenaline drops and dies off. And they're left to wonder - 'was that it?'. As they search for the last Wizard, the last Nuke Op. Surely thinking they missed one. It's worse if it is the illusion of raging wizard, that is spaced out heavily. With high intensity hijack sabotage at the start, e.g gibbing a Captain, hitting vital areas. Followed by 20 minutes of absent participation and then a low intensity wizard, playing duck duck goose. 2. Use Extended to be creative, to make something that would not be possible in other shifts. There are no threats, there are no hostiles. You are not, as a Staff, screwing over the Greentext of a Changeling, if in fact there is no EoC to screw over. Why: You can't step on any EoC toes if there are none. Introduce a custom EoC, a janky one thats new, fresh, and has a conclusion or a story to it. The world is your event oyster. Use the end-round verb if it dies or something. Or keep it going. 3. Blob and Terror Spiders are wholely acceptable. Why: They're team-orientated. Medical get to heal, Security get to fight. Science/Cargo/Botany get to put their efforts to use. All-round a very accessible duo of adminbus. What Made Me Suggest This: I want extended to be respected as extended, OR, a canvas to produce events on. What often happens is that the paint is flung at the canvas, not applied delicately. You see a Wizard, then a 2nd Wizard, then a Slaughter Demon, then a Blob, then Terror Spiders, then another Wizard. If I wanted to participate in a Wizard round, I'd happily crew vs wizard. Same with Blob, same with Terrors, same with anything really. The issue is, they have rounds dedicated to them. Or mid-rounds dedicated to them. And it is not because these occur during extended. But rather they occur at horrible times (low momentum, low motivation crew-wide) or in horrible order. The community have grown to understand if a Wizard appears, it likely means Wiznerd round, that'll conclude asap. And if it doesnt the Wizard is a lich, OR it's raging Wizard. I love what the staff do. It's a hobby, and they're donating their time to the game. But lord, lord do we need some sort of protections for Extended as a vanila game-mode. This mostly comes from #fatiguedfrompoorlytimedextendedadminbus. Where Security are already defeated not from Antags/EoC, but from SSD and Cyro. And the threat appears to a sleep-walking crew. Or the threat appears as Blob, or Wizard 5 minutes in. Having crew assume, high on adrenaline, that it'll conclude after this hunt n prey combo.

CM handles this sort of this perfectly. Namely with weeds/xeno tiles. 1) Plant the Glowshroom / Shadowshroom down. 2) That placement will be the HQ, and slightly thicker than the rest around it - to help players identify. 3) Attack that HQ, and progressively have all the glowshroom/shadowshroom spawned from that 1, be killed. IC way would be the HQ sacrifice the spawns it made, to protect itself. Eventually dying. It can remain the same, but be easier to destroy as an antag / shadowling. Less obnoxious to hunt down. So you're not hitting shroom 55, and 56, 57, 58, 59 spawn. Alternatively have it be like a supply chain. Where you have to feed the Shrooms nutrient/water - to further its growth and spread. Like a supply chain. That way you can cut it off at idk Botany, or 5 HQs down, and it'll kill HQ 6-30 if not reconnected. Odd language use, odd temrinology etc. But I think they are fine as is, in terms of purpose. They REALLY REALLY just need a way to delete, via players. Easier.

My balance to this would be introducing scale to the blueshield. Shift Start: Normal Access, Normal Radio. Radio: - Security Radio once a Command Member has a clear threat directed at them. Given to the Blueshield when Security determines it as such, through investigation or the Head actually being attacked and there being clear indication of it. ID Access: - To departments whom had their Head of Department office hacked into, the Head attacked/or made a clear target. /or Medbay and or Security whom Heads are around people constantly during Red. This can be done through AA to THOSE departments. Not AA 5 minutes into Shift. Weaponry/Items: - If it justifies the threat. Blueshield is a Bodyguard. They shouldn't waltz into X, Y, Z Department WITH the enabled access to swipe a security headset, a detective scanner, six crew monitors, the entire assortment of medical supplies from the table east of Chemist. Scale would make them more fair, fun, and enjoyable. The Community has warped the Blueshield anything but. It's hardly anything like the Wiki Guideline, or the SoP now. And that is rarely ever punished. Staff are torn on how Blueshield interacts with powergame rules. When it is made quite clear, from a personal perspective/opinion. IF you change keywords from Security Officer, etc - to Blueshield. It should not be intended. If a Security Officer tasked with protecting the Station, is unable to hoard medical supplies to heal up potential victims of a Space Crime, just because. A Blueshield shouldn't need a whole surgery table, a dozen medical variants. They get given what they should get. Stuff. To. Stabilize. Death Implants to announce when they die, not Security Comms. It makes me kind of wish we had a sort of CM system. Giving a Sec Officer /Blueshield higher slip/fail rate versus a Medical Doctor /Surgeon.

While in Admin Complaint, it is feedback. I love events, and moreso the ones that go into themes. Asked in A-Help, and Ghost Chat where best to place this post. With no reply I surfed and found that Admin Complaint was also used as Feedback, or Positive commentary. Contrary to the prior words 'Admin Complaint'. It is more feedback than complaint. While I do apologize as to its placement. I do appreciate/respect the professionalism to stick to format. When asked, I was told in-game that round that they were to assist Security and would be equip befitting of that. While a disconnect of communication between myself and the Captain. Who was the main person telling me what was up and what to expect. I assumed wrongly that it would include some 'in the norm' fitting, what I mean by that is touching upon how ERT are dynamic, and often have switch-weapons. Now, my expectations did not meet reality, purely because I was thinking about conventional ERTs. And had no knowledge of what to expect, such as horses and whatnot. Yeah. It's just unfortunate that they were in a round where they were needed to be present. And due to their presence resulted in Captain assuming otherwise, not calling an ERT. It sadly left a Traitor to be unassumed in their actions. And with AA. In conclusion the event added to the round, and was intended to be beneficial. But a lot of the negatives came from non-staff selection. 1. ID/Access 2. Who was in it 3. Extra equipment/equipment to actually react to threats. Captain never reinstated a HoS, nor fixed a chain of command in Security. And mis-used the Knights as HoS/Warden replacements when they weren't equip nor knowledgeable to do so. As HoS/Warden are both time-locked and require a deep understanding of attention that a lot of the Knights failed to pay attention to Security/Brig/Procedure with. I would suggest a more HRP/indepth training montage, but that would take forever in a limited time-frame (2 hours). Which would likely detract from the event/shift/participants. However I do think, hearing your replies, that the selection/armoury should be staff-side, with consultation of Captain. Not captain-side, as they can make or break a round. Handling an event they neither set-up nor knew indepth about (as much as the host/creator of the event). A nerd way to conclude, would to be summarize my suggestions to giving the role of Captain to the Event Admin, and the role of Nanotrasen Rep to the in-game Captain. AKA the Event Admin can balance who is selected, based off their current-round position, security record, etc. And the Captain can advise a 'no, yes, sure idk'. What would be immensely cute would simply be restricting hiring to Assistants / Civilians as 1st preference, then building up towards Security. Not playing favourites, but pooling from the people who tend to not have a demanded job, e.g Engineer. Why I say this is because the IDs / Jobs weren't properly altered, to open up a slot. They for some reason remained in their respective occupations. While not doing their occupations. Thus locking new players from their occupation, while RPing Elysian Knights.

Admin(s) Key: @Elysian_prince Your ckey (Byond username): Lurapa Your Discord name (if applicable): Date(s) of incident (GMT preferred): 29/01/2021 (2 am if im converting right) Nature of complaint: Feedback (Select all that apply: EG - clarification required, misapplication of rules, misconduct, abuse of powers, feedback, other) Links to all relevant ban appeals for any bans related to this complaint: N/A Brief description (tl;dr here. Just the critical elements): A round where Security were bare-bone (100 players) had 10 Antagonist. Security started with less than 5, 4 at time of me joining. Join as Magistrate to find that Security lost their Acting HoS to a traitor. With the other few either SSD, Cyro, or Dead. The Event that occurred was a Medievil Knights ERT, that enlisted 6 persons to aid Security. One of which were Traitor. Full description of events: Round started for me 30 minutes into the shift. I joined as Magistrate and saw that there were 4x Officers, 1x Warden (who became Acting HoS). Find out that the Head of Security Office was bombed, and items stolen. By an Antagonist that had AA and access to Security Records. The one Officer who was present in the round, actively responding - etc. Was bested by the Antagonist and made the struggle that much more real. Now - seeing that we had barebone Security, or something. An Event was presented to the round. Twelve Knights of something, apparently ERT Access, and Authority. That pooled and recruited from the Station populace to aid Security. A really fun idea, that is great to see. But the round simply was not compatible with it. And therefore I am feedbacking for the event to be more dynamic, and more adaptable. We had no Security. The few we had went Cyro with their Security Belts. Thus making any new Security who joined, unable to fully equip themselves. The Captain assumed ERT (Security) could not be requested because of the ERT presence aboard the Station. And soon to be 6x ERT members (from Crew). While not fully not on the Admins running this event. The Event simply failed to remedy any issues Security were facing. Very-much so that they added to the negativity of the round. They were improperly equip to deal with anything but KoS targets. Had no non-lethal means to interact with minor/medium/major crimes. And some of the Recruits just did not know how to perform Security Duties so they simply took liberties with their extra access, authority, and power. It was a stressful shift as Security that round as Command failed to reinstate chain of command, lagging immensely on that. Confused by the illusion that the ERT Trainees / ERT person would be bolstering Security when they did anything but. No fault of their own, but their equipment was more changeling-arm-blade, than anything else. Feedback: Dynamic Weaponry: 1) Non-Lethal alternatives to the equipment. - A nerf-gun, with a bow-sprite, similar to what I had as a Clown via Honkmother one round. It used riot rounds, that hit stamina not health. Instead it was a DS rifle, with different ammo. The Bow could alternate like the DS Honkmother gun too, switching between arrows that embed/pierce to donksoft. 2) Perhaps a renamed Contractor Baton? - Balance needed, obviously. But it would serve them so much better to have multiple option weapon, while preserving their slots. And to rename it would make it more fluff-lore worthy. It could be a proto-type Baton that is in their knightly order, the schematic stolen by the Syndicate. /obj/item/melee/classic_baton/telescopic/knight name = "Elysian Knight Baton" desc = "A compact baton developed and used by the Elysian Knights of the Twelve Planets. Pushed into creation through the many unfortunate lethal arrests. The schematics stolen by the Syndicate for a more potent variant." // Overrides affect_silicon = TRUE stun_time = 1 cooldown = 1.5 SECONDS force_off = 5 force_on = 10 item_state_on = "contractor_baton" icon_state_off = "knight_baton_0" icon_state_on = "knight_baton_1" stun_sound = 'sound/weapons/contractorbatonhit.ogg' extend_sound = 'sound/weapons/contractorbatonextend.ogg' // Settings /// Stamina damage to deal on stun. var/stamina_damage = 20 //Doesn't jitter, or stun. Does Stamina Damage 70>20. 3) Combat Belt - For cuffs, other relatable items. Otherwise they're out of luck in inventory space. 4) Upgraded Mindshield (event/fluff) - To not enable Traitors/Antags into superior authority/access/immunity from Space Law. On tier of ERT. It doesn't seem intended to heighten an antagonist to such a degree. Where no one would question them. To circumvent this, have the Event Admin select from the pool. Or have a demographic to source from. e.g 1x Honkmother representation, 1x Mime representative. Meme it up, pull from the 'various houses' aka departments. So at least then the chance of pulling a traitor is less jank. (An idea would be: Have a Mindshield Implanter that auto-fails 1 random Objective. And that the Syndicate can spawn a ghost to try and contractor the Antagonist out of the Station to take the Trainee ERT equipment, mindshield, and punish the Syndicate Agent for participating in ERT training/indoctrination) 5) Be more clear on what they are. Are they ERT, do they have ERT authority, do their presence disqualify a shuttle (not shift-vote one), do their presence disqualify aspects of Fax Machine/Communication Console. 6) Give them chivalry/laws akin to an AI on how they have to deal with people. e.g Can't use a weapon if the opponent doesn't have a weapon drawn. Stuff like that, to make their extra boosts (AA, radio, authority) more balanced to Antagonist.

I am a bit of an optimist in thinking it is enforceable. Why? Because while there is 150 players, right? There are vastly fewer antagonists, and those antagonists only have 1-2 targets at best. So ballparking a guestimate: Staff watch out for 10 people or so. Staff don't have to watch out for persons targeted by Security, and thus killing Security in droves via self defense. At that point CMD is irrelevant, identity revealed. CMD can exist for the minor amount of targets pre-reveal. I am optimistic on this because metagame is snuffed out, when 150 players are applicable to be hawk-eyed on Peak Times. CMD enforcement can be narrowed down to targets of objectives who die, and revive. (additionally, that 10 can be narrowed down even further, via small code tweaks that flag when a target is killed AND revived.) Alternatively, Delete game-logs client-side, triggered via death. So ghost-chat is hidden, and game-chat prior to death is hidden. Personally, the amount of times I SCROLL for information (IC info, mind you. Not ghost-chat. E.g 'hey whats the passphrase you told me as blueshield'. And other stuff, like names of who I talked to. Im sure a lot of people scroll, so deleting chat on revive would be one way to not only psuedo CMD, but force people to try and recollect without RPing einstei) - quick edit: It could alert when a person kills X. So, when an objective is killed & revived. Have strings from the Traitor's character be highlighted (higlight strings already exist). e.g [Name], [Species], the word [Killed me]. Minor indicators towards a person who was killed by their traitor, and then revived. Such things wont happen if their traitor is unrelated to their death and revival.

A guide by Lurapa, Processing Area: Focus on the buddy rule. A table need a chair, and a chair needs a table. They are buddies. Without a chair you won't be capable of buckling a person in. Without a table you won't be capable of properly searching/displaying objects. *While having pipes, visible, and buckle-able to. This Guide respects IC and RP. Pipe Buckling is effective, but reminiscent in the grey zone of torture/inhumane treatment. Evidence - The Whats And Wheres Evidence Storage is where Objects, if capable of feelings, would die of loneliness. A lot of the Objects in here are in there for the sake of lazy, and not because they were participant to a crime. What Deserves The Plastic Embrace of Baggage: 1. + Bloodied Weaponry in Battery/Assault/Attempted Murder/Manslaughter/Murder charges [/or coroner report for used weaponry] 1.1 Bloodied Weaponry, to be scanned via Detective Scanner to determine attached blood. 1.2 Coroner report, detailing objects used to achieve the damage scanned. Cross-referenced with what is on the Suspect/Known Murderer. 2. + Tools related to Trespass/Major Trespass - Damage To Station Assets/Creating Workplace Hazard/Sabotage/Grand Sabotage. 2.1 If door was hacked open, take screwdriver, wirecutters, multitool, signalling device, crowbar, insulated gloves. 2.2 If in relation to Damage To Station Assets -> up to Grant Sabotage, look at the damage and what tools had to be used to achieve it, if any. *If found 1) During a Blue/Red Search, or, 2) Brig Search. *If handed in, willingly, make an effort to label it. Something like: Person's Name | Station Time | Officer Who Handled It. And if they so wish to gain a permit for maint/off-station loot, they can do so within a reason time. While not SoP to give the person handing it in, a chance. Give them 20-30 minutes (station time, since the label of it. Then consider it expired, and free-for-all for Security to get authorization for)Otherwise it helps differentiate between actual crime-contra(C) and non-crime-contra(C) for Security to use with proper authorization. The Layout/Color Schemes: Grab a floor-painter and section the Evidence Area into three parts. Plain: For Processing Contraband/Items. 1. Scanning via Detective, 2. Labeling, 3. Photographing. Yellow: For C-Tier Contraband. Red: For S-Tier Contraband. Labeling: You can do two things: 1) Name Evidence Bag, or 2) Name both the object and the Evidence Bag. evidence bag (Han Sprite | 13:35:00 | Irate Compliance Unit) Name of person you got the Contraband, etc off of. Station Time, you can do all the digits or simply the first four: 13:35. The Officer Handling / Setting the Label. Housekeeping: 1. You can burn weapon/restricted weapon/contraband in the incinerator. 1.1 Make sure you have evidence of it existing. Photograph + detective scanner, if evidence is needed for a trial. 2. You can safely return clothing, radios, tools, and equipment to their respective departments. If used in a crime, catalog it via scanner print. Clean blood of it, and return it. 2.1 Knife? Pop it back in Kitchen. Spear? Dismantle it. Hatchet? Botany. Insulated Gloves? Engineering. 3. Punish your fellows for not communicating/setting records. It'll remind them to set stuff, and be responsive. Do this by respecting the 10 minute processing timer. Release people if they are held in there because no one is commentating on the vague security record to provide clarification. *While having pipes, visible, and buckle-able to. This Guide respects IC and RP. Pipe Buckling is effective, but reminiscent in the grey zone of torture/inhumane treatment. - WIP, likely to progress it more via Google Document. As it is cuter formatting.

Enforced Cloning / Revive memory loss and then make perma-kill methods less desireable as options. The fact people can remember 100% of their stuff is very very unfun. Or slip in some ghost things. Hell I'd love it if Ghost view and chat didn't exist, only opening up when you do a setting similar to antag-hud. [Toggle Ghost View/Chat: you agree to not recall how you died etc] For how anti-locking ppl from rounds, this game is. It sure has a bunch of meta methods to keep your objective green texted and out of the round.

Overview of Permits/Weapons/Contraband(C) Possession of a Weapon -Legal if job weapon. E.g Knife, Hatchet. - Permitted to By Magistrate, Captain, or Head of Security. Possession of a Restricted Weapon -Legal if job weapon. E.g Baton, Taser, Fireaxe, Telescopic Baton, Laser Gun/Disabler, Shotgun, Two Barrel Shotgun. - Permitted to By Magistrate, Captain, or Head of Security. Possession of Contraband [C] -Legal if: Not Spawned From Uplink, AND, Not used in a crime, AND, Authorized/Permit for use. This Suggestion's Proposal: There is a grey zone that make Space Law and Possession of Contraband/Weapons not a positive experience. What I am talking about is that during Blue/Red. Security can conduct psuedo arrests, to enforce a search - cooperative or otherwise. And that is often when Weaponry/Contraband are found on a person. Or persons try and confess to possession, to squeeze in the fact they 'informed Security and were handing it in'. I personally think possession is possession, and if you try and confess to possession, when lawfully stopped (comply or be cuffed), you are past the point where you intended to walk up to the Brig and hand in a Weapon or Contraband. And I believe that there is a bunch of reasons why Players simply refuse to hand in (C) Contraband, or get it permitted. The Why: There simply isn't a procedure, be it SoP, or community, in place. That ensures a player is protected in this exchange. Shitcurity is a common phrase, but it is very much possible - and non-breaching of SoP, for Shitcurity to just give the person who wants a permit, the short-end of the stick. And there is apt nothing to really do about it besides get told, 'you turned it in'. What I propose: Introduce SoP in Legal: Evidence Storage Procedures General: [Rename Evidence Storage Procedures: -> Evidence Storage Procedures General] Physical evidence is defined as any object that can be used to prove that a particular person has committed a crime. 1. All evidence confiscated from arrested personnel is to be properly analyzed, then stored in Evidence Storage, either in the lockers in the Forensics Lab, or in the Evidence Storage Room in the Prison Wing; 2. Stored evidence is not be removed from Evidence Storage unless it is required for a trial; 3. As per 206 - "Abuse of Confiscated Equipment", stored evidence is not to be used; [NEW] vvvvv Evidence Storage: Permits Permit Objects are objects not found in Random Search, or Brig Search. They are Objects turned into Security, willingly, by Crew. These Objects can be: Weapons, Restricted Weapons, or C-Class Contraband. 1. All Permit Objects are to be placed in a evidence storage bag and labeled with relevant information: [NAME OF PERSON; STATION TIME; OFFICER HANDED TO] 2. Permit Objects are still owned by the person who handed them in. They have 20 Minutes to achieve a Permit for their object. 3. Evidence Bag with expired station-time is to be relabeled and is no longer eligible for permit, becoming Station Property. 4. Expired Permits can be requested authorization by Security Personnel. [People that actually write this stuff / fine-tune it can probably word it better, but I think this is a healthy suggestion to better make... Permits and not being looted of all your shit, a more fun experience overall] - From the Guy Who Keeps Looting Contraband / Maint Loot that wasn't declared,

Securing high-value theft items in secure locations “just in case” someone tries to steal them is classified as powergaming. The nuke disk and spare ID are expected to be secured, however. Bolting down secure locations before any threat is seen is classified as powergaming. This is mainly a consideration for the AI - at shift start, bolting down the teleporter should not be done. EVA should almost never be locked down. The AI may however lock down or reinforce their satellite, in accordance with their laws. Amassing weapons and healing items for personal use “just in case” an antag attacks you is seen as powergaming - people should be acting as if it is an average shift (Until it’s not). Don’t act like a doomsday prepper. Keep your supplies reasonable for the role and situation. If you’re an engineer dealing with space carp, it’s quite reasonable to have healing supplies and a weapon - but not to outgun the armoury. Also remember other people may need these supplies. Each round is considered a new round, and actions from other rounds should not be taken into account for the next. If someone committed a crime in one round, you cannot send them to the brig in the next for it. A rule of thumb is to remember the positive but forget the negative. You can remember that someone is a good doctor or engineer, but you should not hold against them if they accidentally released the singularity a few rounds ago. -------------------------- Are some of the rules, I feel apply to the Blueshield stacking we see. I should stop calling it Blueshield power-ups, Blueshield sterioids. Blueshield - etc. The word I should have used is Powergaming. As mentioned in my 1st post, Cyborgs that Powergame are often asked to dismantle their constructs until Red Alert happens. The Blueshield Powergame ticks all these advanced rules that I have copy and pasted here. The argument against Blueshield not being nerfed as my suggestion goes. It simply - "They protect command and try and be ready for any threat, to be a bodyguard". Well, Security protect the Cyberiad/Crew. Cyborgs protect (depending on their laws). Those two demographics are blocked by the Powergame rules, to do as the Blueshield does.

Paradise's version of Colonial Marine's Xenomorphs are Terror Spiders. It is where all the art, code, and time have gone into. - They're a joy, and have counterplay, whereas Xeno's have only really had one major change to their code. From round rotation enabled, to disabled.

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...'

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.

They cannot perform OOC favouritism if they do not know who the player is. People cover up their OOC with IC. It is extremely difficult to catch meta-buddying, and it is extremely easy to perform meta-buddying under the guise of IC being built up, and then enforced. I don't make friendships because it reduces my fun for the game. I genuinely dislike being given aid, or being shown favouritism based off of my past exploits /or name I use. I don't push my IC connections into Discord, or get to know the player behind the Character. I just want my experience on Paradise to be what the IC is. A repeated instance of the same Shift. Where I know nothing of what Mike Murdock did as Security Officer 1 OOC year earlier, therefore I treat Mike better Icly because of my OOC knowledge of his past rounds. You can't assess what people have is IC or OOC knowledge. The end result is that X player can and will treat C player better if they know of the name, or exploits of that person. e.g Fiddler is a good example. OOCly and in past rounds he is hilariously robust. Very much so most people just go - 'oh fuck' in their brains, and oocly impact their IC when handling Fiddler. The server is medium roleplay, so I do understand where this concern comes from. People do seep their IC into their OOC and vice-versa. Especially if one character acts a certain way, people assume the OOC of that character is similar. People were annoyed at how incompetent one of my characters were as Security - and that they were still following SoP and Space Law, just extremely annoyingly. Thought I didn't understand SoP and Law, then realise my other RP character is Han Sprite, one of the older Magistrate mains. Essentially. I'm suggesting this because I'm bored of the same-old same-old. The Roleplay feels low-rp, and isn't getting any better. A lot of the established characters project their IC into their OOC and it's just boring. If I see certain characters I know 100% how they'll play the Shift.

Greetings all, This suggestion will be layered and built upon as the post is read. ]-----The Suggestion-----[ I suggest that we trial a thing I will herein refer to as 'Randomisation (RS)'. RS is a feature that is already in the game, under preferences. It alters your name, and other details that are displayed by your avatar to other players. Meaning each time you spawn into the shift you will have a different name, or look, each time. ]-----Why The Suggestion?-----[ I believe, personally, that this suggestion will help combat OOC in IC Met buddying. One of the most negative things about Paradise. Administration will have an easier time spotting patterns, and therefore an easier time enforcing the rules. This suggestion also connects with the lore that Paradise is built around: https://nanotrasen.se/wiki/index.php/Lore ]-----The Positives-----[ - Fresh faces. Perhaps a new Roleplay Character each shift... because it is a Medium Roleplay Server and not a Low Roleplay Server. - It will stop the OOC interactions, or the favouritism, or the group-greytiding, based off who the Player is behind the Character name. Promoting a more health, unbiased gameplay experience. - Respects the lore. - A more IC experience. - OOCly become more attached to the Ckey at the end of the Shift instead of the IC name during the Shift. ]-----The Negatives-----[ - Roleplay Characters will be randomised. Thus established figures won't appear. Meaning the main opposition to this suggestion are those who Roleplay a select few gimmicks or Characters. ]-----The Summary-----[ This suggestion is to promote a defence against met buddying while providing a fresh, new, shift-lore friendly experience to veteran players who are fatigued by seeing the same faces, act the same way, with the same people, each round, every round. It feels less like a Roleplay Game and more like an OOC self-insert most of the time. With established names being given favouritism because of their name. These IC bonds were formed IC. But have evolved into OOC friendships that are rarely handled in a way that promotes RP. As Characters become prominent, and played, the more they become OOC. ]-----Endnote-----[ This suggestion will get a lot of negative responses from those who have established characters, and have grown to play a certain way or RP a small manner of ways. It's an RP Game and they should be capable of adapting to a new RP each shift. Not reinforcing the same RP, over and over, that eventually turns OOC.

All in a days work, Tales From Shitcurity Post 1#: The Security Department had the following personnel, 1 Detective. 7 Officers. 1 Warden. 1 Head of Security. 1 Brig Physician 11 Security Personnel, not including a Blueshield. The Head of Security, knowing his numbers, decided to recruit the Clown, a Mime who talked, a paroled Traitor into the Security Department. Low and behold, the Mime and Clown were traitors. And the paroled Traitor managed to get his objectives completed - which was to assassinate the Head of Security. I find adding to the Security Personnel when there is 1 Officer, is fine. But when it is maxed? Naaaah man.

I would appreciate greatly a picture of Han Sprite for this biography. Make his ugliness stand out. Embrace the beauty of the Magistrate wig and robe. https://nanotrasen.se/forum/topic/12637-the-honourable-han-sprite/

Hello, Please add the following HTML and purposes. [Time] /= Places the Shift's time on the location. [Title] & [/Title] /= Whatever is in-between this, automatically renames the Paper to what is in the [Title] field. The ability to correlate your occupation to your load out. If you spawned in as a Head of Personnel, you will spawn in with whatever paperwork you had set to spawn and the html applied. This will save a lot of time, and seems easy in theory.

Yes. Head of Personnel are hard to execute. It's because they're never in a position to make decisions that lead down the execution path. And, cool enough is that a lot of what is written here is given to Han through other player characters. E.g calling him a demon, or a evil person on the right side of the law. Reason I made this post now is because I just discovered Character Biography's were a thing.

"Han's allies call him a monster. The Enemies of Nanotrasen call him a demon. Han thinks of his placement in this Universe as simple as being on the right side of Space Law." - Steve the Accountant The Honourable Han Sprite's age is unknown. Records show that he has been around for thousands upon thousands of years. Keeping his sense of 'self' through snacking on and devouring Diona Nymphs instead of taking the Nymph into his gestate. This sense of self, that Han has achieved lead him down a path of a sole personality - over a collective personality. A personality that is refined, to a Dominant Nymph, in a collective of Nymphs that make up of his tendril-like body. The Honourable Han Sprite has quite a track record with Nanotrasen, known for enforcing Space Law without bias and prejudice. This approach to Space Law that Han preaches is seen in his work. To date Han Sprite has neutralized the following, through a flick of his pen; 13 Captains. 8 Head of Security. 16 Security Officers. 20 Research Directors. 13 Chief Medical Officers. 2 Head of Personnel. 4 Chief Engineer. 78 Non-Command / Security. - 09/02/2018. "Diona are a resilient race. They are either dead, or alive. They are never dying, or surviving." - The Honourable Han Sprite. Caption: Han Sprite in his natural habitat. A law-abiding evil entity.