Try   HackMD
tags: wip design-document

Access Refactor

Access Levels

This document will define some basic rules for how baseline card access levels should work.

Each card should have a basic Access Levels, determined by the card itself. This includes both a Type and a Level, from 1-5.

The numerical Access Level value should be used as such:

  • Level 1 gives access to the 'front door' of a department. This should branch outwards to all sides, for areas with multiple entrances/exits. Side-rooms and special passages such as Checkpoints generally require Level 3 instead.
  • Level 2 gives access to the majority of internal doors in the department, particularly main halls. This also includes most common low-risk devices/machines that require access, such as Departmental Protolathes (if that becomes a thing).
  • Level 3 gives access to specialised but low-risk doors inside the department (surgery, RnD, minimum for Safe SCPs, Low-Alert Armories, medical outposts, medical/engineering storage, security preps), and most specialized low-risk department devices/machines, including checkpoints.
  • Level 4 gives access to high-risk doors inside the department (High-Alert Armories, secure engineering storage, minimum for most SCPs (set as OR with a certain area, so temporary work passes can be provided), most special offices (Department Heads) in addition to needing area access).
  • Level 5 is held by each Department Head as "Level 4" (SCP Security Clearance goes from 0-5) Personnel, as well as the Site Director. This level is used for machines and devices relating to access, including Guest/Temporary passes, area access edits, promotions/demotions, job changes, etc. Highest-risk general areas are also locked behind an OR access type, between the Level 5 accesses. For example, the Emergency Bunker and Self-Destruct Room.

As an example for a relatively complex area (DCZ-LCZ) using this list:

  • The doors right in front of the stairs leading to DCZ should be Level 1 Security.
  • The doors in the hallways and crossroads leading up to DCZ checkpoint should be Level 2 Security.
  • The doors to access the DCZ Checkpoint room and the blast door buttons should be Level 3 Security.
  • The doors in LCZ past the stairs from DCZ should be Level 2 Security once again.
  • Safe SCP containments should be Level 3 or 4 Science. The doors leading into the hallway containing them should still be Level 2-3 Security.
  • SCP-173 Containment Observation should be Level 4 Science, as with the buttons. The doors themselves should be Level 4 Security, but can be opened with buttons inside of Observation with Level 4 Science as well.
  • The doors directly before HCZ/Stairs should be Level 1 Security.
  • Maintenances will likely be no restriction, or Level 1 of whatever side it's at, so LCZ to Archive will need Level 1 Security to get through the LCZ side door, Level 1 Admin to get through the Archive side door.

The O5 rep loses their all access, and instead has Level 3 access to all departments.

Containment cells should have the appropriate Security Level access for the Containment Zone they are in, and Science Level 3, to allow Senior Researchers to access CCs, and Engineering Level 3, to give the Containment Engineer and Chief Engineer access to repair CCs.

LCZ/HCZ will both be on Level 1 for the front doors, Level 2 for general access to Containment Cells/Class D areas, Level 3 for Zone Commander offices, and Level 4 for the Guard Commander.

Kaga Note: Remember that our design is not that of a space station, where long central hallways connect branching departments. Some departments are in their own branches, such as Engineering and Medical, but the majority INCLUDE the hallways within themselves, progressing through departments as you get closer to the Surface. This means that getting a departmental ID will be necessary to progress through most of the facility, or finding alternative methods/paths, or getting a hold of an ID with at least Level 2 access for most areas. Level 1 will only get you into the transition areas.

Personnel Access

Command

Site Director

  • Admin Level 5
  • Security Level 5
  • Medical Level 5
  • Engineering Level 5
  • Science Level 5
  • All Areas besides: Class D Checkpoint, Containment Units.

O5 Representative:

  • Admin Level 3
  • Security Level 3
  • Medical Level 3
  • Engineering Level 3
  • Science Level 3
  • All general areas Level 3 and below, except: Class D Checkpoint, Containment Units.

Human Resource Officer

  • Admin Level 4
  • Security Level 1
  • Medical Level 1
  • Engineering Level 1
  • Science Level 1

Chief Medical Officer

  • Admin Level 2
  • Security Level 1
  • Medical Level 4
  • Engineering Level 1
  • Science Level 1

Research Director

  • Admin Level 2
  • Security Level 1
  • Medical Level 1
  • Engineering Level 1
  • Science Level 4

Chief Engineer

  • Admin Level 2
  • Security Level 1
  • Medical Level 1
  • Engineering Level 4
  • Science Level 1

Archivist

  • Admin Level 3
  • Security Level 1
  • Medical Level 1
  • Engineering Level 1
  • Science Level 3 - is still a researcher, end of the day

Medical

Surgeon

  • Admin Level 1
  • Medical Level 3

Medical Doctor

  • Admin Level 1
  • Medical Level 3

Psychiatrist

  • Admin Level 1
  • Medical Level 2

Chemist

  • Admin Level 1
  • Medical Level 2

Emergency Medical Technician

  • Admin Level 2
  • Security Level 2
  • Medical Level 2
  • Engineering Level 2
  • Science Level 2

Research

Senior Robotics Technician/Senior Researcher

  • Admin Level 1
  • Science Level 3

Robotics Technician/Researcher

  • Admin Level 1
  • Science Level 2

Junior Robotics Technician/Junior Researcher

  • Admin Level 1
  • Science Level 2

Engineering

Containment Engineer

  • Admin Level 1
  • Security Level 2
  • Medical Level 1
  • Engineering Level 3
  • Science Level 1

Senior Engineer/Engineer/Junior Engineer

  • Admin Level 1
  • Engineering Level 2

Communications

Communications Officer

  • Admin Level 4
  • Security Level 1
  • Medical Level 1
  • Engineering Level 4
  • Science Level 1

Communications Technician

  • Admin Level 1
  • Engineering Level 2

Logistics

TODO: i don't really know what to do here

Logistics Officer

  • Admin Level 3
  • Logistics Area Access, allowing use of the Cargo App.

Logistics Technician

  • Admin Level 3
  • Logistics Area Access, allowing use of the Cargo App.

Security

Guard Commander

  • Admin Level 3
  • Security Level 5
  • Medical Level 2
  • Engineering Level 2
  • Science Level 2

EZ Supervisor/(HCZ/LCZ) Zone Commander

  • Admin Level 3
  • Security Level 4
  • Medical Level 2
  • Engineering Level 2
  • Science Level 2

(Senior) EZ Agent

  • Admin Level 2
  • Security Level 3
  • Medical Level 2
  • Engineering Level 2
  • Science Level 2

(LCZ/HCZ) Sergeant

  • Admin Level 1
  • Security Level 3
  • Medical Level 1
  • Engineering Level 1
  • Science Level 1

(LCZ/HCZ) Guard

  • Admin Level 1
  • Security Level 2
  • Medical Level 1
  • Engineering Level 1
  • Science Level 1

Service - Majority of Access should be Area-based.

Chef

  • "Service" ID type.
  • Admin Level 2 (for providing meals to the administrative offices?)

Janitor

  • "Janitor" special ID appearance. Purple?
  • Admin Level 2
  • Security Level 1
  • Medical Level 2
  • Engineering Level 2
  • Science Level 2

Bartender

  • "Service" ID type.
  • Admin Level 2

Officer Worker

  • "Employee" ID type.
  • Admin Level 2

Chaplain

  • "Employee" ID type.
  • Admin Level 2
  • Security Level 1
  • Medical Level 2
  • Engineering Level 2
  • Science Level 2

Class D

  • "Class D" ID type. Orange.
  • By default only areas (Class D in particular). Can purchase additional access through work points/kiosk, including to restricted CD areas. Will need a design document for the full CD gameplay loop, possibly a progression from low to high risk areas? Mining -> Medical -> Kitchen -> Botany?
Last changed by 
 
Foundation 19
0
248

Read more

Sanity Framework

⚠️ Handled by Tsuru, Kaga ⚠️ Basic Goals A sanity statistic, ranging from 0-100%. This can be numerical, and the maximum should be modifiable. Should be simple to check and compare, for interactions. Unsure if it's better to be associated with the mob or the brain, but presumably the mob will be easier to pull values from while brain is more 'realistic' and should persist across transplants. Maybe have it on both, mirroring each other? Applies to all Carbon mobs. Can be affected by a simple Mental Damage type, in the same vein as Brute/Burn/Toxin/Oxy/Brain. Distinctly, should not just use Brain, as that refers to Bay's brainmed. Can be either mitigated or healed through the usage of psychiatric medications. Mitigation would only prevent the effects so long as the medications are in the bloodstream, Healing would recover Sanity gradually.

Sep 8, 2022
SCP-096 Preliminary Rework

⚠️ Handled by Kaga ⚠️ SCP-096 has the following key features: When its face is seen, whether in person, through a camera, or in a photograph, it will enrage and target those who have seen it. When enraged, it can tear through effectively anything. Materials which are labeled as invulnerable in the code should allow it to phase through instead. Upon encountering a target, it will begin ripping them apart. Calling gib() honestly isn't great, because per the article it does something [REDACTED] that leaves no trace of the body behind. Gibs and viscera, and maybe dropping the ID/equipment is fine, but for maximum 'interactivity' I could see it being something like tearing each limb off (qdeling limbs) and eating them? TBD Upon arriving at SCP-096-1's location, SCP-096 will proceed to kill and [DATA EXPUNGED] SCP-096-1. 100% of cases have left no traces of SCP-096-1. SCP-096 will then sit down for several minutes before regaining its composure and becoming docile once again. It will then attempt to make its way back to its natural habitat, [DATA REDACTED] After clearing its target list (the slower time-to-kill with the update kill method should make it take longer than before, while also giving more chances for people to see it and add to the list), it becomes calm and should enter a 'docile' stage, wherein it covers up its face on its own, and will not automatically uncover for a set grace period.

Sep 8, 2022
Alert Level

Drawing inspiration from Lockdown Protocols, we change our Alert Level system to integrate MTF deployment requests and Area/Secure Bunker lockdowns. The new Lockdown system will include: A new interface in the Command & Control Program, which can generate a Lockdown Response Code. A specific builder for the LRCs, with the Priority and Threat classification. Priority will range on a scale of A-C, with response times changing from: A: Immediate response required, multiple SCPs breached, mass casualty event among the staff, risk of total loss of containment. B: MTF response required, but limited risk of total loss of containment on the Site.

Sep 5, 2022
SCP-106 Preliminary Rework

⚠️ Handled by Kaga ⚠️ Key Features: 106 is capable of phasing through solid material, making it almost uncontainable. When phasing through solid material, it should leave an obvious corrosive 'mucus'. 106 possesses a Pocket Dimension, which decays anything foreign within. This mechanically functions as burn damage/acid damage that eventually breaks even objects down. The burn damage should be toned significantly down, as it's supposed to torment them for long periods of time. Moreso a round-long threat that can constantly cause damage to players and disrupt their activities, rather than a rapid round-end. 106 can send entities to the Pocket Dimension. This should not be instantaneous, and should require some disabling before occurring. Some kind of accelerated ability to break bones without causing lethal damage? 106 is drawn by pain and suffering, but has unknown motivations. There is some leeway to add our own explanations for its behavior as a result. 106 can enter its Pocket Dimension and exit at will. It enters and exits at the same location in the 'real world'. 106 can rot materials on contact, both organic and inorganic. This can be both an attack and an ability. Possibly adapt something from Rust Heretics?

Sep 4, 2022
Read more from Foundation 19
Published on HackMD