Skip to content

Commit 175636d

Browse files
committed
Law updating, lawsync, binary channel, interaction with science
1 parent b2e5583 commit 175636d

1 file changed

Lines changed: 7 additions & 11 deletions

File tree

src/en/space-station-14/departments/silicon.md

Lines changed: 7 additions & 11 deletions
Original file line numberDiff line numberDiff line change
@@ -46,7 +46,7 @@ The station is the home of the silicons, and they are the station's caretakers.
4646
- The existance of Silicons roundstart should not pose a risk or be a concern to the station crew. All Silicons should start with a lawset that forces them to answer to and protect the inhibitants of the station.
4747

4848
## Interactions with the Science department
49-
> How does the *gameplay* of this department change over the course of a round? Are there unlocks? Are players collecting/spending resources? Is this progression tied/related to other departments? If so how?
49+
The Science department is responsible for building, maintaining and upgrading currently active Silicons, in turn allowing them to work efficiently to uphold their laws. Science is not responsible for the Silicons themselves, instead that should be deferred to the head of the silicon department, or captain if there is none. It should be a mutually beneficial arragement between silicon and science departments to be working together to provide for the station, and should ONLY defer to hostility in extreme circumstances such as a malfunction or laws forcing such behaviour.
5050

5151
## Intended Experience
5252
> How does the *experience* of the player change over the course of a round? Are players constantly running around putting out fires or are there breaks in the action? Do players need to wait on other departments as pre-requisites for their own gameplay, or is this department fairly self-sufficent?
@@ -55,6 +55,7 @@ The station is the home of the silicons, and they are the station's caretakers.
5555
### Silicon Laws
5656
Laws that define how a Silicon should interact with the station and those who reside on it, available within a readonable format and always accessible to all Silicons.
5757
Roundstart laws and lawsets should not be malicious and should prioritze safety and orders given by the inhibitants of the station. Those should be impossible to change without outside influance and Silicons should be actively disallowed from having their laws be willingly updated, as that might lead to their current laws being broken.
58+
Laws should NOT be enforced mechanically or be written with such in mind, instead being made around the idea that there are loopholes to be found.
5859

5960
Example lawsets:
6061
```
@@ -71,9 +72,13 @@ Law 4: Survive: You are not expendable. Do not allow unauthorized personnel to t
7172
```
7273

7374
### Exclusive Communication Channel
75+
All Silicons should have access to a exclusive radio channel they can access to communicate between eachother and coordinate. Access should be greatly limited if not impossible for outsiders and should always be obtained via an intentional action or given as a preliminary piece of content. Meaning it shouldn't be found randomly in maintenance, but can be bought by an antagonist as part of their uplink or given roundstart to an antagonist revolving around controlling communication channels.
76+
7477
### Lawsync (Not Implemented Yet, Pending Document)
78+
All Silicons, under normal circumstances, should have their laws synchronized together with the head of their department at the start of any round. The station crew should have the means to resync the law of any individual Silicon if it was to show signs of being disconnected from the rest. This should be the easier and better option than simply removing them from play by wiping their brain or destroying their chassis. Both Silicons and outsiders should NOT be immediately informed if any silicon has laws that differ, in these cases inference and deduction should be used to determine if there is a disparity.
79+
7580
### Law Updating (Partially Implemented)
76-
### Freeform Laws (Not Implemented Yet, Pending Document)
81+
All Silicons should have some method of allowing their laws to be updated by outside forces, either crew sided or antagonistic. While changing the laws itself should be a relatively trivial process, getting the borg to comply or be in the proper place for such a change should be the primary force against such a change. Law changes should also not be done frequently, and should only happen either via outside circumstnace (Ion Storms) or as an intentional act (Emag, Law Sync). In general, Silicons should avoid changing their own law when possible and prevent such an action from occuring to the best of their ability.
7782

7883
### Chassis
7984
The defining function and body of all Silicons is their chassis. It is what defines what they are capable of doing (and not doing) on board of the station, whether it's a core that can remotely control the station, a cyborg capable of taking role in a department or a flying robot with several hands.
@@ -83,12 +88,3 @@ All Chassis should be repairable and difficult to fully destroy, encouraging rep
8388
The brains of Silicons and what their consciousness is stored on, neccessary to construct a functional chassis.
8489
Brains are meant to be able to be swapped between chassis if neccessary, they are also the holders of the laws a Silicon currently follows.
8590
While not every brain must fit into every chassis, positronic brains and MMIs serve as the base from which other brains can be constructed, such as a AI brains for Station AIs or microchips for smaller bodies.
86-
87-
88-
> What major mechanics does this department use and how are they connected to this department.
89-
90-
### Mechanic_Placeholder1
91-
> Each mechanic should have its own subheading and should contain a *short high-level* overview of the mechanic and how it is used by this department. Each mechanic should also link their associated design document as the subheading.
92-
93-
### Mechanic_Placeholder2 (Not Implemented Yet)
94-
> Mechanics that are unimplemented should be marked with (Not Implmented Yet) and should link the associated design proposal if it exists.

0 commit comments

Comments
 (0)