People Playground

People Playground

Not enough ratings
Chaos 2.0
4
   
Award
Favorite
Favorited
Unfavorite
File Size
Posted
Updated
1.693 MB
2 Nov, 2022 @ 2:45am
11 Nov, 2022 @ 4:48am
3 Change Notes ( view )

Subscribe to download
Chaos 2.0

In 1 collection by ۞•★ᗪOᙀᒪIKIN★•۞
Secure Contain Protect | SCP
112 items
Description
Chaos 2.0

When writing object documents for the Chaos Rebels, it should be remembered that, unlike the Foundation, the Rebels actively use anomalous objects. Due to the division between the cells and the differences between the classes of personnel in each of them, the Delta Committee provides only the most necessary information. And all Rebels really need to know what to do with anomalies, not what they are and how exactly they work.

In fact, a member of the Delta Committee, codenamed "Engineer", constantly rewrites a massive list of instructions (a "Plan" divided into separate "Steps") without any adjustment in the immediate sense. The Delta Committee transmits these instructions on a descending basis to the rest of the Rebels. The rest of the Delta Committee members then scan and separate these Steps, compiling "Step-by-Step Sequence" documents from them.

These are the basics. Before you continue reading, you should probably familiarize yourself with the cycle "Darkness over the Abyss" (search on the tab "Selected data"). And then, you know, spoilers, and many things will be incomprehensible to you, so to speak.

Let's talk about the thematic basis of these documents. The essence of the image of Chaos Rebels in them is that absolutely all their data is dictated by the engine. This "object" format should embody the contradictions inherent in the nature of the Rebels of Chaos. This organization claims that its goal is a perfect understanding and integration of the abnormal, but does not tell its operatives anything about these paranormal objects or phenomena. There is an illusion of order - they adhere to a strict set of instructions. But the reality is chaos: the average Chaos Rebel operative doesn't know what he's doing or why. They just follow the engine's plan.

Who is the Driver? A member of the Delta Committee who is in constant telepathic contact with the engine and constantly formalizes the will of the latter in the form of a Plan. Mostly verbally. The mind of the engine is behind everything, but no one except the Delta Committee knows about the existence or true nature of this engine.

The last thing about these documents - we believe that it will be much more useful for you, as an author, to think not about the object you want to depict, but about the history associated with this object, and even more specifically, about what the Chaos Rebels are going to do with it. To portray what exactly an object is, you should recreate the knowledge hidden by the Rebels through subtexts, hints and references to other components of the Foundation universe.

Document breakdown
Number in the ORRCODE catalog: Number in the ORRCODE catalog (Department of Intelligence and Registration of the Delta Committee, English DeCIRO - Delta Command Intelligence Recording Office) - the Rebels of Chaos have an analog number in the Foundation database, with the exception that it is assigned to all documents.

Document Type: Although "Step-by-step sequence" is always indicated as the document type in its upper part, the included sub-documents may have other types. For more information about the sub-documents, see below.

Date of admission: Everything is clear here. The format DD.MM.YYYY is used as a template (for example: 04/22/1955) It should be borne in mind that these dates correlate with the ORRCODE number of the Step-by-step sequence.

Operation Status: If all the Steps in the document have been followed and no further Steps are expected, the operation is assigned the status "Completed". If the Rebels are planning further Steps and/or there is a suspicion that other related steps will be taken, the operation has the status of "In progress".

Preface: The Delta Committee consists of not quite sane persons. In the preface, they essentially address themselves (since no one else sees the preface), and their language, as a rule, is colorful or metaphorical. It is useful for dedicating the reader to the details of the impact, which would be difficult to understand by Steps.

1. STEP _ This is where the fun begins. The steps are what the Rebels are actually going to do with the object described in the document. Therefore, the description is not used too often. Instead, the Steps can be studies of a specific object and the attachment of the resulting research information.

Step-by-step Sequence Template
[[>]]
[[module Rate]]
[[/>]]

[[div style="float:right"]]
[[image chaos-insurgency-hub/CI%2520Document.png width="310 px"]]
[[/div]]

**Number in the ORRCODE catalog:** SC-[first Step]/[last Step]

**Document type:** Step-by-step sequence

**Date of receipt:** 31 Dec, 1969 @ 4:00pm31 Dec, 1969 @ 4:00pm[Vague description of the object, operation, and/or thoughts of the Delta Committee on this matter.] Next, we, the Delta Committee, present a document with a Step-by-Step Plan, deciphered by the Chaos Rebel Machinist. **1. STEP [last two digits of the year / step number for this year]** [A bunch of instructions] **2. STEP [last two digits of the year / step number for this year]** [Our song is good, start over] Template of sub-documents Final report > **Number in the ORRCODE catalog:** FR-[linked Step]-[number](e.g. 001) > > **Document Type:** Final Report > > **Date of receipt:** DD.MM.YYYY > > **Author:** [Name] > > **Final report:** [The research Report (Findings Reports or "FR-" for ORCOD) tells in detail about the research or exploration at the appropriate Step, and in the final report you... well, report on the results.] Analysis of operational actions > **Number in the ORRCODE catalog:** POR-[linked Step]-[number](e.g. 001) > > **Document type:** Analysis of operational actions (Post-Operation Summary Report) > > **Date of receipt:** DD.MM.YYYY > > **Author:** [Name] > > [Report details the results of the relevant combat operation.] Secret operation > **Number in the ORRCODE catalog:** CO-[linked Step]-[number](e.g. 001) > > **Document Type:** Secret operation > > **Date of receipt:** DD.MM.YYYY > > **Author:** Delta Committee > > [Instructions for a secret operation.] SCP + - Mods that do not greatly affect the construction, so you can do without them. *** - Mods that I didn't use but for some reason they appeared. Subscribe to my group. In it, you can ask me to make ANY SCP and communicate with the same as you. https://steamhost.cn/steamcommunity_com/groups/Dulikin [b]This contraption requires the following mods:[/b] - [url=https://steamhost.cn/steamcommunity_com/sharedfiles/filedetails/?id=2788364899] Detailed Mobile Task Forces [/url] - [url=https://steamhost.cn/steamcommunity_com

**Operation status:** In progress/Completed

**Preface:** [Vague description of the object, operation, and/or thoughts of the Delta Committee on this matter.]

Next, we, the Delta Committee, present a document with a Step-by-Step Plan, deciphered by the Chaos Rebel Machinist.

**1. STEP [last two digits of the year / step number for this year]**

[A bunch of instructions]

**2. STEP [last two digits of the year / step number for this year]**

[Our song is good, start over]
Template of sub-documents
Final report
> **Number in the ORRCODE catalog:** FR-[linked Step]-[number](e.g. 001)
>
> **Document Type:** Final Report
>
> **Date of receipt:** DD.MM.YYYY
>
> **Author:** [Name]
>
> **Final report:** [The research Report (Findings Reports or "FR-" for ORCOD) tells in detail about the research or exploration at the appropriate Step, and in the final report you... well, report on the results.]
Analysis of operational actions
> **Number in the ORRCODE catalog:** POR-[linked Step]-[number](e.g. 001)
>
> **Document type:** Analysis of operational actions (Post-Operation Summary Report)
>
> **Date of receipt:** DD.MM.YYYY
>
> **Author:** [Name]
>
> [Report details the results of the relevant combat operation.]
Secret operation
> **Number in the ORRCODE catalog:** CO-[linked Step]-[number](e.g. 001)
>
> **Document Type:** Secret operation
>
> **Date of receipt:** DD.MM.YYYY
>
> **Author:** Delta Committee
>
> [Instructions for a secret operation.]
SCP

+ - Mods that do not greatly affect the construction, so you can do without them.
*** - Mods that I didn't use but for some reason they appeared.

Subscribe to my group. In it, you can ask me to make ANY SCP and communicate with the same as you.
https://steamhost.cn/steamcommunity_com/groups/Dulikin

This contraption requires the following mods:
- Detailed Mobile Task Forces
- SCP: Armory
4 Comments
𝒄𝒐𝒐𝒍 5 Mar, 2023 @ 10:31pm 
wait where do you get those emojis tho
۞•★ᗪOᙀᒪIKIN★•۞  [author] 24 Feb, 2023 @ 12:47am 
@Simon "Ghost" Riley
What's the difference:riddle:
𝒄𝒐𝒐𝒍 23 Feb, 2023 @ 11:28pm 
BRO ITS NOT "Chaos" ITS "Chaos Insurgency" OH MY GOD BRUH WHY DO YOU KEEP MAKING CODE NAMES WRONG
Prepboar550 18 Jan, 2023 @ 10:59am 
Most of the SCP dupe mods you made have their armor missing just a heads up