SCP-359
SCP-359
Author: TopDownUnderTopDownUnder
Published on 29 Sep 2021 01:14
/* source: http://ah-sandbox.wikidot.com/component:collapsible-sidebar-x1 */
 
#top-bar .open-menu a {
        position: fixed;
        top: 0.5em;
        left: 0.5em;
        z-index: 5;
        font-family: 'Nanum Gothic', san-serif;
        font-size: 30px;
        font-weight: 700;
        width: 30px;
        height: 30px;
        line-height: 0.9em;
        text-align: center;
        border: 0.2em solid #888;
        background-color: #fff;
        border-radius: 3em;
        color: #888;
}
 
@media (min-width: 768px) {
 
    #top-bar .mobile-top-bar {
        display: block;
    }
 
    #top-bar .mobile-top-bar li {
        display: none;
    }
 
    #main-content {
        max-width: 708px;
        margin: 0 auto;
        padding: 0;
        transition: max-width 0.2s ease-in-out;
    }
 
    #side-bar {
        display: block;
        position: fixed;
        top: 0;
        left: -20em;
        width: 17.75em;
        height: 100%;
        margin: 0;
        overflow-y: auto;
        z-index: 10;
        padding: 1em 1em 0 1em;
        background-color: rgba(0,0,0,0.1);
        transition: left 0.4s ease-in-out;
 
        scrollbar-width: thin;
    }
 
    #side-bar:target {
        left: 0;
    }
 
     #top-bar .close-menu {
        margin-left: 19.75em;
        opacity: 0;
    }
    #side-bar:target .close-menu {
        display: block;
        position: fixed;
        width: 100%;
        height: 100%;
        top: 0;
        left: 0;
        z-index: -1;
    }
 
    #top-bar .open-menu a:hover {
        text-decoration: none;
    }
}
 
@supports selector(:focus-within) {
 
@media (min-width: 768px) {
    #top-bar .open-menu a {
        pointer-events: none;
    }
    #side-bar:not(:target) .close-menu {
        display: block;
        pointer-events: none;
        user-select: none;
        z-index: -1;
    }
 
    /* This pseudo-element is meant to overlay the regular sidebar button
    so the fixed positioning (top, left, right and/or bottom) has to match */
 
    #side-bar .close-menu::before {
        content: "";
        position: fixed;
        z-index: 5;
        display: block;
 
        top: 0.5em;
        left: 0.5em;
 
        border: 0.2em solid transparent;
        width: 30px;
        height: 30px;
        font-size: 30px;
        line-height: 0.9em;
 
        pointer-events: all;
        cursor: pointer;
    }
    #side-bar:focus-within {
        left: 0;
    }
    #side-bar:focus-within .close-menu::before {
        pointer-events: none;
    }
}
 
}
rating: +57+x

What this is

A bunch of miscellaneous CSS 'improvements' that I, CroquemboucheCroquembouche, use on a bunch of pages because I think it makes them easier to deal with.

The changes this component makes are bunch of really trivial modifications to ease the writing experience and to make documenting components/themes a bit easier (which I do a lot). It doesn't change anything about the page visually for the reader — the changes are for the writer.

I wouldn't expect translations of articles that use this component to also use this component, unless the translator likes it and would want to use it anyway.

This component probably won't conflict with other components or themes, and even if it does, it probably won't matter too much.

Usage

On any wiki:

[[include :scp-wiki:component:croqstyle]]

This component is designed to be used on other components. When using on another component, be sure to add this inside the component's [[iftags]] block, so that users of your component are not forced into also using Croqstyle.

Related components

Other personal styling components (which change just a couple things):

Personal styling themes (which are visual overhauls):

CSS changes

Reasonably-sized footnotes

Stops footnotes from being a million miles wide, so that you can actually read them.

.hovertip { max-width: 400px; }

Monospace edit/code

Makes the edit textbox monospace, and also changes all monospace text to Fira Code, the obviously superior monospace font.

@import url('https://fonts.googleapis.com/css2?family=Fira+Code:wght@400;700&display=swap');
 
:root { --mono-font: "Fira Code", Cousine, monospace; }
#edit-page-textarea, .code pre, .code p, .code, tt, .page-source { font-family: var(--mono-font); }
.code pre * { white-space: pre; }
.code *, .pre * { font-feature-settings: unset; }

Teletype backgrounds

Adds a light grey background to <tt> elements ({{text}}), so code snippets stand out more.

tt {
  background-color: var(--swatch-something-bhl-idk-will-fix-later, #f4f4f4);
  font-size: 85%;
  padding: 0.2em 0.4em;
  margin: 0;
  border-radius: 6px;
}

No more bigfaces

Stops big pictures from appearing when you hover over someone's avatar image, because they're stupid and really annoying and you can just click on them if you want to see the big version.

.avatar-hover { display: none !important; }

Breaky breaky

Any text inside a div with class nobreak has line-wrapping happen between every letter.

.nobreak { word-break: break-all; }

Code colours

Add my terminal's code colours as variables. Maybe I'll change this to a more common terminal theme like Monokai or something at some point, but for now it's just my personal theme, which is derived from Tomorrow Night Eighties.

Also, adding the .terminal class to a fake code block as [[div class="code terminal"]] gives it a sort of pseudo-terminal look with a dark background. Doesn't work with [[code]], because Wikidot inserts a bunch of syntax highlighting that you can't change yourself without a bunch of CSS. Use it for non-[[code]] code snippets only.

Quick tool to colourise a 'standard' Wikidot component usage example with the above vars: link

:root {
  --c-bg: #393939;
  --c-syntax: #e0e0e0;
  --c-comment: #999999;
  --c-error: #f2777a;
  --c-value: #f99157;
  --c-symbol: #ffcc66;
  --c-string: #99cc99;
  --c-operator: #66cccc;
  --c-builtin: #70a7df;
  --c-keyword: #cc99cc;
}
 
.terminal, .terminal > .code {
  color: var(--c-syntax);
  background: var(--c-bg);
  border: 0.4rem solid var(--c-comment);
  border-radius: 1rem;
}

Debug mode

Draw lines around anything inside .debug-mode. The colour of the lines is red but defers to CSS variable --debug-colour.

You can also add div.debug-info.over and div.debug-info.under inside an element to annotate the debug boxes — though you'll need to make sure to leave enough vertical space that the annotation doesn't overlap the thing above or below it.

…like this!

.debug-mode, .debug-mode *, .debug-mode *::before, .debug-mode *::after {
  outline: 1px solid var(--debug-colour, red);
  position: relative;
}
.debug-info {
  position: absolute;
  left: 50%;
  transform: translateX(-50%);
  font-family: 'Fira Code', monospace;
  font-size: 1rem;
  white-space: nowrap;
}
.debug-info.over { top: -2.5rem; }
.debug-info.under { bottom: -2.5rem; }
.debug-info p { margin: 0; }
:root {
    --posX: calc(50% - 358px - 12rem);
}
 
/*--- Footnote Auto-counter --*/
#page-content {
    counter-reset: megacount;
}
 
/*--- Footnote Superscript Number --*/
.fnnum {
    display: inline-block;
    width: min-content;
    text-indent: calc(-1% - 0.1em);
    overflow: hidden;
    line-height: 83%;
    text-decoration: none;
    font-weight: bold;
    font-style: initial;
    color: transparent;
    position: relative; top: -0.25em; font-size: 82%;
    padding: .15em calc(.21em - 0.4px) .12em calc(.11em - 1px);
    margin-left: -0.06em;
    margin-right: -0.25em;
    counter-increment: megacount;
    user-select: none;
}
.fnnum::after {
    content: "" counter(megacount);
    color: var(--fnColor, #E6283C);
}
.fnnum:hover {
    text-decoration: none;
    cursor: pointer;
    background-color: var(--fnColor, #E6283C);
}
.fnnum:hover::after { color: white; }
 
/*--- Footnote Content Wrapper --*/
.fncon {
    position: absolute;
    right: calc(var(--posX) + 80px);
    line-height: 1.2;
    padding: 0.82rem;
    width: 10.3rem;
    background: white;
    border: 2px solid black;
    font-weight: initial;
    font-style: initial;
    text-align: initial;
    pointer-events: none;
    opacity: 0;
    transition: opacity 0.15s linear, right 0.3s cubic-bezier(.08,.72,.5,.94);
    z-index: 9;
}
.fnnum:hover + .fncon {
    opacity: 1;
    right: var(--posX);
}
.fncon::before {
    position: absolute;
    top: 0; left: 0;
    transform: translateX(-52%) translateY(-55%) scale(1.15);
    background-color: var(--fnColor, #E6283C);
    color: white;
    content: counter(megacount);
    font-size: initial;
    font-weight: bold;
    font-style: initial;
    padding-left: 0.32em; padding-right: 0.32em;
    padding-top: 0.18rem; padding-bottom: 0.08rem;
}
 
/*--- Mobile Query --*/
@media only screen and (max-width: 1279px) {
    .fncon {
        position: fixed;
        bottom: 1.3rem;
        left: calc(11% - 50px);
        width: 70%;
        transition: opacity 0.15s linear, left 0.3s cubic-bezier(.08,.72,.5,.94);
    }
    .fnnum:hover + .fncon {
        left: 11%;
     }
}
rating: +57+x
perch.jpg
SCP-359 at rest.

Item #: SCP-359

Object Class: Euclid

Special Containment Procedures: Provisional Site-359 has been constructed in close vicinity to SCP-359's location. AMTF Gamma-27 ("Breaking and Entering") is currently stationed at Provisional Site-359, and are tasked with discovering and implementing procedures to both neutralize SCP-359 and gain access to SCP-359-A. The preservation of normalcy is to be disregarded when formulating neutralization proposals for SCP-359, due to the artificial remoteness of the area it inhabits.

Regular GPR readings are to be conducted on SCP-359-A to help deduce the exact amount of hephaesium.For information on hephaesium, refer to Addendum 359.2. contained within it.

Archived Containment Procedures 05/05/15: SCP-359 is to be kept under constant surveillance with a radio tracking device fastened to its leg. In cooperation with the Ohio Department of Transportation, the highway located near SCP-359's location is to be kept indefinitely closed to ensure no further civilian casualties.

Description: SCP-359 is a metal sculpture resembling a Buteo jamaicensis (Red-tailed Hawk) with a wingspan of 4.3m. The exact composition of the metal SCP-359 is constructed from is currently unknown, as no samples have been able to be retrieved. However, it is currently believed that a large portion of it is constructed from hephaesium. SCP-359 is completely inert during the day. Under normal circumstances, SCP-359 is only active during the night. During these active periods, SCP-359 takes on a predatory nature, attacking most moving objects it sees. Notably, SCP-359 does not consume any of its prey, even those of organic nature. Instead, SCP-359 has been seen picking up the remains of its prey, and depositing them near the boundaries of the area it is active in. Despite its small wingspan in relation to the rest of its body, SCP-359 is capable of flight, having demonstrated the ability to perform highly intricate manoeuvres.

SCP-359-A refers to a subterranean structure, which can be accessed via a hole located near SCP-359's perch. While the Foundation has reached the hole leading to SCP-359-A, it has yet to be breached. SCP-359 actively defends the entrance from any potential trespassers, which is the only circumstance in which it becomes active during daylight. It is unknown whether SCP-359 can detect the desire to enter SCP-359-A or simply attacks anything that gets close to it. Readings with a ground-penetrating radar (GPR) indicate a large hollow space, with masses of hephaesium detected within.

Addendum 359.1: Discovery

SCP-359 came to the Foundation's attention in January of 2009 after a string of disappearances were reported along State Route 33 in Ohio. Agents embedded in the Lancaster Police Department took notice and sent a team to investigate. The team uncovered both the desecrated corpses of the missing persons and the dried blood of the deceased on SCP-359's talons and beak. After the case was transferred to the Foundation by the state government, further investigations uncovered no records of SCP-359's construction, despite its relatively modern design. The first known mention of it was in 2006, when the property it is located on was donated to the city of Lancaster.

Addendum 359.2: Hephasium Dossier

metallurgydept.png

Prepared by the Department of Metallurgical Studies


Originally discovered and named by a Greek research team in the 1960s, hephaesium is an alloy composed of iron, beryllium bronze, and several unknown elements. Hephaesium is most commonly used in structures that are meant to be animate, such as SCP-359, SCP-070, and SCP-1451. While it's not the most common form of animation, it is most popular amongst those incapable of thaumaturgy or ontokinesis.

Named after the Hellenic god of the forge, Hephaestus, hephaesium is most commonly found in Ancient Greek ruins and artefacts. It was spread around the ancient world through trade and the conquests of Alexander the Great and, later, the Roman Empire. Traces of hephaesium have been found in Chinese shishi statues and Indian sculptures of Buddha and Hindi figures. Despite its widespread nature, production was limited to Greece. Due to this enforced secrecy, the method by which to produce hephaesium has since been lost to time, with the last known usage of it being in the Bernward Doors and Column constructed circa 1000 A.D for the St. Michael's Church in Hildesheim, Germany. There have been mentions of hephasium stashes throughout the Baltic States but, much like the means of production, knowledge on their location has been lost.

Objects animated via hephaesium aren't permanently animate, however. Over time, due to a chemical reaction with O2 in the atmosphere, hephaesium rusts and eventually becomes inert. This process can be sped up if objects in a O2-free environment are suddenly introduced to the gas. The rusting of hephaesium is usually characterized by the object becoming more sluggish and unresponsive to stimuli before eventually becoming fully inert.

Hephaesium is also subject to a second anomalous property, one seemingly implemented to protect against reverse engineering. If at any point after it has animated the alloy is removed, sampled, or otherwise detached from the main mass, it suddenly undergoes lunafaction.Alchemical term for the making of silver., rendering its anomalous properties null. As such, the exact composition of hephaesium is unknown.

The acquisition of hephaesium would be highly beneficial to the Foundation. Acquisition of such an easy means of animation could aid in efforts to automate certain parts of the Foundation, such as security, field missions, and other such tasks. Likewise, obtaining the knowledge on how to manufacture hephaesium and ensuring the Foundation is in sole possession of it could prove to be financially beneficial, as the Foundation would be the sole seller of the metal. While not as important as the last two reasons, rediscovering the means to create hephaesium would be a para-anthropological achievement, allowing for a deeper understanding of the cultures that produced and used the metal.

Addendum 359.3: Discovery of SCP-359-A

In 2015, as per the Survey Program being conducted by the Department of Geology, GPR readings were taken of the North American Continent to uncover subterranean anomalies. Readings conducted near SCP-359 indicated the existence of a hollow structure directly underneath its perch. Further readings focused on this structure pointed towards the existence of vast deposits of (presumably unactivated) hephaesium.

A reconnaissance team was sent to investigate, and potentially find or create an entrance into the subterranean structure.

2015 Reconnaissance Log


Date: 17/04/2015

Reconnaissance Team: Pi-27

Subject: RTF Pi-27 was deployed to investigate the area immediately above the subterranean structure for a possible entrance. If no entrance was discovered, a site was to be chosen to begin drilling.


Squad Lead: PI-1
Squad Members: PI-2, PI-3


[BEGIN LOG]


PI-1: Comms check.

PI-2: Sounding good.

PI-3: What's the point of comms? All we're doing is lugging this equipment over there in case we can't find a hole leading down there. It's not like we're gonna get separated or whatever.

PI-1: It's standard for all operations, even something small like this.

PI-2: The logs are also used for recordkeeping.

PI-1: That too. Let's get a move on, we're wasting daylight here.

PI-3: Yeah, yeah…

[PI-3 grunts as ze picks up the equipment. Pi-27 begins walking towards SCP-359's perch from Route 33.]

PI-2: That's one big bird. I'm surprised we've been able to keep it under wraps for so long with how large it is.

PI-3: We'll be safe from it, right?

PI-1: Did you read the debriefing, Three? It's only active during the night. If you wanna get specific, between 9 PM and 6 AM. It's 1:08 right now, we'll be fine.

PI-3: I mean, did we have to read the debriefing, One? All we're doing is either finding a hole or digging one. It's not like we're doing a blacks op mission to infiltrate the White House.

PI-2: Ze's got a point…

PI-1: Regardless. Let's carry on.

[Pi-27 passes by the corpse of a Odocoileus virginianus (White-tailed deer) hanging from a tree via its antlers.]

PI-2: We've reached its hunting grounds. We'll be seeing a lot more of those.

[Pi-27 reaches the perch of SCP-359, stopping within its shadow.]

PI-1: Can you check how close are we to the structure, Three?

PI-3: Give me a sec.

[PI-3 gently drops the equipment ze was carrying, reaching into zir backpack for a PDA.]

PI-3: We.. should be directly above the centre of it. The radar readings seem to show some sort of access tunnel close by, but it's pretty small.

PI-1: That'd be a great place to start, let's head there.

PI-2: Is this the hole you're talking about, Three?

[PI-1 and -3 walk over to where PI-2 is standing. PI-2 is pointing at a 0.5m wide hole in the ground. PI-3 checks zir PDA.]

hole.jpg
Still from PI-3's bodycam.

PI-3: Uhh… yeah, that's the one. It seems to be caved in some, and we might have to expand it a bit to get all the harvesting equipment the Department sent.

PI-2: Let's get to work then. I'll get to work setting up the equipment so you can catch a break, Three.

[PI-2 begins setting up the drilling equipment as PI-3 rests against a tree and PI-1 supervises. As PI-2 is about to activate the drill, the sound of metal scraping against metal could be heard. The three members of Pi-27 turn to look at SCP-359, which as its wings outstretched. SCP-359 launches itself from its perch, swooping down and grabbing PI-2 before ascending. The remaining members of Pi-27 scatter into the surrounding forest.]

PI-3: What the fuck was that, One?! I thought we were safe during the day! You said it yourself, and look what happened to ██████████!.PI-2's legal surname, redacted in accordance with PI-2's request to RAISA for anonymity.

PI-1: Calm down, Thre-

PI-3: Calm down? I just watched my coworker, my teammate, my fucking friend get snatched up by some big metal bird, how am I supposed to remain calm?

PI-1: I don't know, Three. I don't know. We just need to get out of here. I can already hear that bird coming back for us.

[SCP-359 could be heard as it flapped its wings, sending a small gust of wind through the forest's leaves. PI-1 and -3 begin running towards the State Route. SCP-359 breaks through the treeline in pursuit of Pi-27. PI-1 stops for a moment to catch her breath, giving SCP-359 an opportunity to catch her and take her into the air, alongside several uprooted tree trunks.]

PI-3: Fuc-!

[SCP-359 can be heard turning around for PI-3 as ze trip on an exposed tree root, landing on the bodycam. The resulting damage severs the connection.]

[END LOG]

Following the end of this log, PI-3 was later found on the nearby State Route, bloodied and bruised. PI-1 and PI-2 have both been declared deceased, which was confirmed when their corpses were found in similar conditions to those of SCP-359's prey.

Addendum 359.4: Formation of Gamma-27 and AWD Involvement

After the events of the Reconnaissance Log in Addendum 359.3, multiple, more heavily-armed, missions were sent to attempt to get past SCP-359 and gain access to SCP-359-A, all of which similarly ended in failure..Combined, all four missions have resulted in 6 dead and 10 wounded, as well as approximately $450,000 in broken equipment. It was decided by a Joint Committee of the Department of Metallurgical Studies, Department of Geology, and SCP-359's research team that greater measures had to be taken. As such, Provisional Site-359 was established, made up of detachments from the Departments of Geology, Metallurgical Studies, and Anomalous Weapons Development. Armed Mobile Task Force Gamma-27 ("Breaking and Entering") was also formed and stationed at Site-359. To quote the MTF Dossier;

Armed Mobile Task Force Gamma-27 consists of individuals gathered from failed missions to access SCP-359-A, as well as supplements from Nu-7 and other combat-oriented Task Forces. The sole purpose of Gamma-27 is the termination of SCP-359 and obtaining access to SCP-359-A. To accomplish this task, Gamma-27 regularly conducts missions to observe the behaviour of SCP-359 and its attack patterns. Data obtained from these missions are sent to the Departments of Anomalous Weapons Development and Metallurgical Studies to obtain a more in-depth understanding of SCP-359 and possible methods of termination.

SCP-359 Dossier

Department of Anomalous Weapons Development Design Packet
Compiled by Engineer Eren Everest for G-27


Description of Target: Entity is a large metallic sculpture (wingspan of 4m, estimated to be 9m in height, unknown weight) resembling a red-tailed hawk. Entity is made up of hephaesium, an alloy consisting of iron, Bbronze, and other unknown elements. Entity is only active A) during the night, or B) in defence of SCP-359-A. Entity is highly prejudicial in its defence of SCP-359-A, having been seen attacking any and all sources of movement.

Potential Exploitable Weaknesses:

  1. [UNUSABLE] - Entity is at least partially constructed from hephaesium, which has a melting point of 1,274°C. A paraweapon capable of causing the air around the entity to reach this temperature could be a viable option to terminate SCP-359. Reason: the potential damage to the surrounding environment and the subterranean structure is considered unacceptable.
  2. [UNUSABLE] - Entity's main weapons are its talons and beak. Disabling these appendages could render the entity harmless. A paraweapon capable of amputating the entity could make termination of the entity easier. Reason: Entity could still cause blunt force damage by flying into operatives.
  3. [CLEARED] [FAILURE] - Entity has so far only used its wings for locomotion. Using psionic paraweaponry to both launch and deploy chains, the entity's wings could be constrained, allowing for ease of termination. Update: The chains utilized in the Procedure proved to be too weak to restrain the entity, which broke out and then proceeded to terminate the psionic agent.
  4. [CLEARED] - Hephaesium, when removed from the main body, undergoes an alchemical process that transforms it into silver. Removing large portions of SCP-359 could render it inanimate as the hephaesium loses its anomalous characteristics. A procedure such as this could be accomplished via the use of thaumaturgical explosives propelled towards SCP-359.

Notes on Weapon-359-9:

To put it simply, the paraweapon is just explosives strapped to a magic rocket. The required components are:

  • 24kg of anomalously enhanced explosive material
  • Thaumaturgically activated and propelled propulsion system
  • A thaumaturge
  • Type II Everhart Resonator.A Resonator that does not require electricity or a thumaturge to generate EVE, however it produces only 5% of what a Type I Everhart Resonator would produce. On top of that, the Resonator is highly prone to malfunctions and errors.

AWD will supply the bombs and rocket. I'm sure you'll be able to provide a thaumaturge. The thaumaturge should activate the rocket and guide it to its target. Usually, we'd just have it track the EVE the target puts out, but from what we could gather from your observations, the bird doesn't give off any of it. If all goes well, 359 will be in pieces before we lose another operative to it.

And, I'm gonna be real with you, this is our last option. If you want to get rid of this bird, then you better hope this works. You and I both know we can't do anything more than this. We're far too close to population centres to use anything more anomalous than this. Command would never approve of it.

Status of Weapon-359-9: COMPONENTS GATHERED, DEPLOYED.

Addendum 359.5: Destruction of SCP-359 and Access to SCP-359-A

2017 Gamma-27 Log


Date: 23/01/2017

Mobile Task Force: AMTF Gamma-27

Subject: AMTF Gamma-27 was deployed to attempt to neutralize SCP-359 with Weapon-359-9. If SCP-359 was neutralized, a Department of Geology detachment stationed at Site-359 would be notified to begin drilling a wider entrance to SCP-359-A.

Additional Note: The log was recovered from G-1's bodycam. Zir vest was found at the entrance to SCP-359-A by a team sent to investigate. The team was sent after Gamma-27 failed to respond to any communications from Site-359. G-1 has yet to be located and has been officially declared as having gone AWOL.


Squad Lead: G-1
Squad Members: G-10, G-23, G-28


[BEGIN LOG]


G-1: Comms check, everyone.

G-23: Clear.

G-10: Clear.

G-28: Loud and clear.

G-1: How's the weapon, Two-Eight?

G-28: Looks good.

G-1: Great, let's get moving then.

[G-1 walks into the forest, with the rest of Gamma-27 following behind zir. G-23 and G-28 take turns carrying Weapon-359-9. After a short while, SCP-359 can be spotted over the treeline, inactive on its perch. The remains of past attempts to terminate it can be seen littered around it and the hole leading to SCP-359-A. The area around SCP-359 has also been rendered devoid of plant life, creating a small clearing.]

G-1: Eight, how long'd it take you to get the rocket ready?

G-28: Five, Six minutes. Shouldn't take too long.

G-1: Long enough for 359 to rock your shit and ruin this whole operation. Stay at the edge of the clearing with the weapon, and we'll keep it distracted long enough for you to do your thing. Ten, stay with Eight just in case. Two-Three, with me.

G-10: Aye-aye, captain.

[Gamma-27 nods as they follow G-1's order. G-28 places both of their hands on Weapon-359-9, channelling their EVE into the paraweapon. G-1 and -23 walk out into the clearing and aim their rifles at SCP-359. They each shoot a sizable amount of shots at SCP-359, activating the sculpture. Much like in past confrontations, SCP-359 outstretched its wings before launching itself into the sky. G-1 and -23 bolt into the forest, with SCP-359 following them from above the trees. The duo struggle to maintain their lead on SCP-359, but manage to do so.]

G-1: How's the rocket coming along, Eight?

G-28: Hit a small hiccup, but it shouldn't take much lon-

[Weapon-359-9 makes a loud sputtering noise as it attempts to power on, catching the attention of SCP-359. Seeing G-10 and -28 at the edge of the clearing, it turns and beings flying towards them. G-1 curses under zir breath and comes to a stop. Ze begin running after SCP-359, signalling for G-23 to follow.]

G-23: What the fuck happened?!

G-28: I don't know, the weapon shouldn't have done yet!

G-10: Fucking AWD…

G-1: That doesn't matter, start running.

G-28: And the weapon? WE can't just le-

G-1: Just fucking run!

[G-28 lets go of Weapon-359-9, severing the connection. G-10 grabs -28's wrist as they run away, knocking the weapon over as SCP-359 flies overhead. G-1 runs after SCP-359, hopping over the paraweapon and into the forest.]

G-1: Head back to the State Route, it won't follow us that far out! We can come back for the paraweapon later!

G-23: Hey guys, question.

G-1: What, Th-?

[G-1 turns zir head to look at G-23, only to see that she isn't behind zir.]

G-1: Three, where are you?

G-23: How much juice did you get in the Weapon, Eight?

G-28: Barely enough to get it to launch. W-why?

G-23: Just-

[G-23's mic picks up the noise of the Type-II Everhart Resonator being activated.]

G-23: -wondering.

G-1: I know what you're thinking, and that's not gonna work, Three. It'll still needs someone to guide it.

G-23: Mm… Ten, you know if the rocket's strong enough to carry someone?

G-10: Y-

G-1: No, it's not.

G-23: Shit, gotcha. I'll be with y'all in a bit.

G-10: Fuck! It shouldn't have followed us out here.

G-28: I thought it didn't go this far!

[The sounds of doors slamming and metal scraping against metal can be heard. The screams of G-10 and -28 are audible through their mics.]

G-1: Ten, Eight, what's the situation?!

[G-1 breaks through the treeline, bringing the State Route into view. SCP-359 is perched on the AMTF's fortified transport vehicle.Fortified transport vehicles (FTV) are vehicles used by AMTFs designed to withstand explosions, blunt force damage, and minor ontokinetic/thaumaturgic attacks. Due to the high cost and rarity of the materials used to manufacture them, FTVs are only produced and assigned to Task Forces when the situation demands it. , attempting to break through the glass with its beak. This also marks the farthest recorded distance SCP-359 has flown from its perch in defence of SCP-359-A. G-10 and -28 are presumably inside of the FTV.]

G-1: Hold on, I'm coming!

G-23: Don't, One. It'll just kill you.

[G-1 turns around, only to see that G-23 is still not there.]

G-1: Where the fuck are you, Three?

G-23: On my way.

[Hearing a noise, G-1 looks up. Something can be seen flying from the clearing in the direction of SCP-359. A soft, light blue aura can be seen around it. As it gets closer, G-1 realises what it is. Ze begins running towards the State Route in front of it.]

G-1: Oh god… Three, don't you fucking dare! That's an order!

G-23: [Laughter] I don't think you'll be able to write me up after this, ser.

[G-23 flies past G-1 on Weapon-359-9, barely managing to maintain her grip on it. Once it begins to near the State Route, G-23 pushes down on the tip of the weapon, aiming it at SCP-359.]

G-1: They're still in there, Three!

G-23: Wait, wh-

[Weapon-359-9 collides with SCP-359, detonating. The ensuing explosion engulfs both SCP-359 and the FTV. Large chunks of SCP-359's body come flying out of the explosion. A charred, yet still intact, FTV flies out as well, hitting the ground and rolling a bit before coming to a stop. G-1 drops to zir knees, witnessing the scene. Stifled sobs can be heard. After a moment, G-1 fumbles with and deactivates zir bodycam.]


[An unknown amount of time later, G-1 reactivates the bodycam. Ze is walking through the forest while carrying digging equipment, which ze presumably recovered from the FTV.]

G-1: I searched the car. Ten and Eight, they got burnt alive. Fucking Three… There had to be a better fucking way. Just needed that glorious blaze of glory… First Pi, and now this shit…

G-1: I'm heading to -A. I don't care if protocol states I need to call Geology down here to dig a hole and all that shit. I've lost too many fucking people for this, no way I'm not gonna be the first person to go in there.

[G-1 reaches the hole. Ze sets up the digging equipment, continuing to mumble under zir breath. After 5 minutes of tinkering with the device, it activates and begins digging.]

G-1: There. I'm going to get to that fucking hephaesium first. Gotta see for myself if it really was worth all of this fucking bullshit.

[A loud beep can be heard.]

G-1: Low battery. I'll turn it on when I'm down there.


[G-1 reactivates the bodycam, illuminating the dirt tunnel ze's crawling through. G-1's laboured breathing can be heard. Ze speak between pants.]

G-1: It's fucking… hot down here… I'm really.. close now.

[The tunnel widens up, allowing for G-1 to stand. A door can be seen at the end of the tunnel, presumably leading into SCP-359-A. Readings indicate the temperature around the door to be around 21°C.]

G-1: [Chuckle] There it fucking is. God, do you know how many people died, how much equipment was ruined, how much fucking money was spent getting to you? Oh, that metal better be fucking worth it.

[G-1 reaches for the door's handle. When ze tries to turn it, the handle pops off, falling onto the ground.]

G-1: One last challenge, huh? Can't stop me that fucking easily.

[G-1 backs away before ramming into the door, shoulder-first. Ze repeats this three times before the door creaks open. Almost immediately, a cacophony of sound erupts from behind the door. The cries of injured animals can be heard, objects falling and hitting the ground, metal cracking. After a short while, the noises began to stop, until it eventually became quiet. G-1 hesitantly grabs the side of the door, slowly opening it up.]

G-1: Oh..

goose.jpg
Still from G-1's bodycam.

[The door opens up to a subterranean ecosystem, heavily resembling the one above ground. Looking up reveals the sky, despite the fact SCP-359-A is several meters underground. In the distance, a body of water can be seen. From G-1's perspective, the structure seems endless.]

G-1: Did I..

[Throughout SCP-359-A, the statues of animals are present. Many of them were depicted in the process of mundane activities, while others seemed to be in a state of fear and panic. A majority of the statues depicting avian organisms were in mid-flight and seemed to have crashed into the ground.]

[All of the sculptures were covered in rust with the exception of their eyes. Their eyes could be seen still moving.]

G-1: [Silence]

[G-1 covers and turns off the bodycam.]

[END LOG]

Analysis of the sculptures within SCP-359-A revealed that they were all constructed purely from hephaesium, with the eyes having been made from silver. The current leading theory amongst SCP-359's research team is that SCP-359-A was home to an ecosystem consisting of animals constructed from hephaesium, and that the sudden exposure to outside air, and thus oxygen, resulted in the constructs near-instantly becoming rusted. Analysis of the plants within SCP-359-A revealed all of them to have been genetically modified. They were incapable of undergoing photosynthesis, but still capable of intaking oxygen.

lovers.jpg
Two hephaesium constructs located within SCP-359-A.

As the hephaesium had already been used to animate these sculptures, it is unharvestable by the Foundation. Despite this, the constructs were moved out of SCP-359-A and shipped to Area-34.

The remains of the deceased Gamma-27 members were recovered and received a proper funeral. The remains of SCP-359 were collected and shipped to Area-34 for storage. Site-359 is currently in the process of being decommissioned and its assets relocated to other Foundation facilities. SCP-359-A and the tunnel leading to it have been resealed, with a basic security perimeter established around it.

Reclassification of SCP-359 and SCP-359-A to Decommissioned is pending.

Unless otherwise stated, the content of this page is licensed under Creative Commons Attribution-ShareAlike 3.0 License