⊹ ࣪ ˖ NeverNottaCon ˖ ࣪ ⊹

I think it’s cool. But that doesn’t necessarily mean others will. Light spoilers beneath the cut for when the plot eventually gets to it but *cough*

TRANSFORMERS FANS. Specifically those into mtmte

your attention if I may… I’m writing a transformers fanfic (as my followers may know) that’s a continuation of Lost Light #25. I plan to write it as closely as I can to how it feels reading the comics, so, POV switching, no real focused on character aside from maybe following rodimus more often than anyone else, but your still going to get points where it focuses more on others than it did in Lost Light (for exmple: dratchet is going to have a few chapters where their POV(s) are shown more often than anyone else’s or rather they are the prominent POV(s))

this story will also introduce a couple of new characters and villians as well as as much worldbuilding as my silly little brain can figure out (magic crystals COUGH who said that…)

ANYWAYS.

yeah so I need to name it. Currently I have two names that I like, Last Light and AfterLight. If your a mtmte/LostLight obsessed freak like me or someone who just really likes megatron you’ll probably recognize the name AfterLight, it’s one of Megatrons poems.

“you flare, You flicker, You fade.”

“and in the end… all your tomorrows become yesterdays.”

I thought this name and the poem (or at least what pieces we got of it) was beautiful, and I think those lines sort of fit the fic in a way.

However, Last Light was the first name this fic had, it was kinda like an unfunny pun of “haha it’s like the Last LostLight story after issue #25” (not actually, obviously. There’s a ton of other post-#25 fics, but to this universe I’ve created specifically I meant. Ig) but that’s why I kind of wanted to change the name maybe, but I’m also kind of attached to it lol. I just don’t want people to think I’m referencing Megatrons purple lost light because that has like nothing to do with it…

but, that’s where y’all come in!!

I want YOU to help name my fic, also if you see all this stuff above and are like “WOW that’s a lot of reading” you can literally just skip it and pick what title you like better. Cool? Cool.

We’ve done lip biting to death... Let’s evolve.

so I did a thing.

Y'know how Tumblr and Ao3 got married? You know how it's a joke ship? Yeah so somehow my ADHD brain got so hyperfixated on it that somehow I made lore.

Basically, AO3 is known as archivist, but we'll call em AO3 for the sake of recognizability. AO3 was spawned in in this backrooms-like world that is his massive library of whatever-amount-of-books they said they had.

After they spawn in, they realize they have no memory of any past. The only thing they have is a bag and the orb of light that hangs above their head as a way to light up the area around them and see the fics. The orb of light isn't visible to other apps but others can see that light is emmited from the area surrounding AO3.

Anyways, enough about the light. The library is filled with "consumers" or "readers" but I think consumers sound scarier. We can call them readers when they acctually read.

When AO3 first comes across one of these "consumers" their first instinct is to protect themself by grabbing a book and threatening to hit the consumer.

However, instead of the consumer attacking AO3 like AO3 thought it would, AO3 discovers that the books-- or "fics" fascinate the consumers. The consumer, when faced with the fic, seemed to become much more docile.

Once the consumer comes in contact with the fic, the consumer turns into a more of a "character" which aligns with the fic. (Note: not any character from the fandom but just something that matches the fandoms world y'know what I mean? Like how people make personas yeah?)

How did AO3 know what the fic was about? Shhhh.... Don't question ao3. Maybe they mind read books.

Anywho, later, AO3 discovers that they were a bit off. In order to find keep the consumers/readers happy, he must find their fandoms fics and hand them some.

So, while doing this they're also on a search for an "everything fic" so they can keep themselves protected at all times, and keep the consumers satisfied until they find the right fic.

And yes.

They do find it.

Were pretending that exists for now because I don't know if it actually does. I don't think it does. But authors never fail to amaze me.

Anyways. When AO3 gets the hang of their job, they find that they enjoy doing it. They enjoy making these consumers-- no. readers-- happy. They enjoy making the readers happy.

And later on, after a long while, they stumble upon the edge of their library, and find that they can leave to other backrooms-like spaces. One being twitters.

Twitter though, in more current times, has been going through this-- corruption. It has AO3 and other apps concerned, and ready to distance themselves. But mostly, they miss who Twitter used to be, or atleast-- some of who they used to be.

Once AO3 enters, they stumble across someone already with Twitter. Someone... Familiar. Someone they feel like they know from somewhere, but they're not sure where...

Tumblr?

Here's my character designs for them btw :3

ALSO AO3 doing all this in turn creates a positive feedback loop because the more they organize the more they see new books appearing, unorganized, laying around in the aisles. This is because the more they organize the more content there is to inspire "writers" which are somewhat like consumers but better at hiding (I'll draw them eventually). These books usually already have tags though that were drawn into the inside of the fics cover, so at least AO3 doesn't have to bother with that part.

This is a work in progress to be expanded on as I get the time to research stuff, but I figure this would be a handy list to have floating around somewhere! 

Putting my medical secretary skills to use, lmao.

—

Achilles Virus - Coding Based / Cognitive Affective 

Created by Shockwave, alters a bot’s perception; Seems to have the ability to prevent certain analytical processes from being engaged. Used to prevent others from being able to analyse weaknesses in individuals connect to Decepticon High Command. 

Resolution of this virus is unclear; It is presumed a counter-virus is available. 

—

Alchemical Virus - Category of Physical Illnesses 

Refers to any illnesses in which the compositional properties of any metalloid elements or materials used in the construction of Cybertronian forms may be altered by chemical or other transmutative means, resulting in a variety of deleterious effects (such as armour or structural elements becoming brittle). 

—

Atrophosia - Degenerative Physical Condition 

Similar to Cybercrosis (below), but the initial onset of symptoms appears to be triggered by exposure to organic lifeforms; No further detail available as to mechanism of illness or if progression/symptoms may vary significantly or present along a different timeline etc. compared to Cybercrosis. 

—

Combat Fatigue - Psychological and Physical Condition

Presents in Cybertronians typically in older age ranges among enlisted bots. The onset of symptoms is primarily psychological, with disinterest in performing duties or other regular activities or other depressive behaviours, with a strong avoidant behavioural element resulting in self-isolation. 

Cause may be related to a bot having experienced multiple complex traumas, and physical symptoms of fatigue may be difficult to differentiate diagnostically from signs of regular old age in Cybertronians or form fatigue. 

—

Corrodia Gravis - Degenerative Physical Condition 

A “wasting” type illness in which rust gradually consumes all metalloid components of a Cybertronian’s frame construction. 

As this was named after myasthenia gravis, it may indicate that this is disease may be caused by a malfunction of a bot’s self-repair nanites, as this would pair with MG being an auto-immune condition in human beings. 

It may be the case that CG is caused by self-repair nanites functioning incorrectly and not identifying rust as something to continually self-repair, thus allowing for the accumulation of rust systemically or multi-systemically to develop over time, although this is conjecture. 

—

Cybonic Plague - Infectious / Degenerative Disease

Manufactured as a bioweapon for use by the Decepticons, this appears to be a fomite (surface/contact) transmissible illness in which the frame and possibly processor as well begin to physically degrade at an accelerated rate. 

Known physical symptoms of illness include a rust-like degradation of outer armour and possibly internal systems as well, with slowed speech or cognitive processes indicating more advanced or multi-systemic illness, typically towards later stages. 

—

Cy-virus - Infectious Disease 

Not much detail available; Appears to cause hyper-aggression or lack of inhibition (or both) in those infected. 

This may suggest that the virus affects certain parts of the processor while leaving other systems alone for the most part, as this resembles certain types of brain damage in human beings in particular sections of the brain which may result in loss of self-awareness, self-control, or behaviour change. 

—

Cybercrosis - Degenerative Disease (Can be physical and/or mental) 

Cybercrosis occurs when a spark is no longer able to sustain consistent energy levels, with a persistent gradual decrease in total energy output over time. 

Symptoms are primarily physical with initial onset seemingly often being syncope (fainting) due to low energy causing emergency system shut-down, with more advanced symptoms varying based on which systems of the body are most affected as energy is re-routed to sustain basic functions while overall energy continues to decrease. 

Common symptoms include chemical degradation of one’s innermost energon, and difficulty or inability to transform into alt-mode (or back into root mode). 

Processor functions may also be impacted, with memory processes being notably energy intensive, and thus more likely to be affected in later stages of illness. 

Nearly all cases are fatal, with few notable exceptions. 

—

Energon Discharge Virus - Physical Illness 

This virus results in a “sneeze” like symptomatic presentation, in which the ventilation systems of a bot begin to malfunction and accumulate an overcharge of energy directly routed from the spark, resulting in bursts of expended energy with each “sneeze” like ventilation system misfire. 

If left untreated, these bursts of expended spark energy as well as the overall strain caused by excess energy being routed away from other systems of the body may result in emergency stasis being triggered as a way to conserve as much energy as possible. It may be fatal if left unresolved. 

Treatment requires the administering of a counter-virus, which will then resolve the ventilation system error and resolve the faulty energy routing. 

—

Gold Plastic Syndrome - Degenerative Disease 

Typically occurring in older bots, although it has been noted to occur in younger bots on occasion, this illness compromises the physical integrity of metalloids forming the armour and joints in particular, although it has also been known to occur internally or multi-systemically depending on the overall frame construction of a given individual. 

This illness is noted to primarily afflict bots with gold pigment nanites, and although the exact nature of the disease is unknown and may have several individual or overlapping contributory causes, there is likely a materials component involving certain metalloid compositions of the frame and/or armour. 

GPS is gradually degenerative in most cases, although in some individuals it is known to have presented as an immediately acute brittleness affecting structural components as well as external frame elements such as armour or any modifications where applicable. 

GPS is fatal, although life span and quality of life may be increased somewhat by remaining in root mode (or alt mode as may be appropriate in certain cases), with medical stasis being a potential option towards later stages of the illness– Although this will not change the ultimate outcome. 

—

Hate Plague - Infectious Disease / Psychoactive Condition 

An aerosolised transmissible disease caused by spores of an unclear composition, those infected develop hyper-aggressive tendencies, lack of inhibition or self-control, and hyper-fixation on other individuals whom they may be able to recognise or have had prior familiarity with. 

The only known cases of recovery from Hate Plague were cured via unclear means, with direct intervention from the Matrix of Leadership. As such, this condition is still considered largely untreatable, and preventative measures are advised. 

—

Metal Fatigue - Degenerative Physical Condition 

An ailment of older bots, this is a relatively common condition in which the metalloid components of the body begin to weaken naturally over time. 

Stress fractures may be a common initial presentation of illness, with outcomes varying based on the severity of metal fatigue and based on which components or systems may be most affected. 

—

Photodegradation - Degenerative Physical Condition 

After prolonged direct exposure to certain types of light source, pigment bonded nanites may suffer gradual chemical decomposition, resulting in a chronic discolouring of a bot’s frame or armour. 

While this is a non-critical illness, it may affect a bot’s psychological or emotional state over time based on severity, and appropriate support should be provided as needed on an individual basis. 

—

Primus Apotheosis - Psychological Condition 

Classified as a Cybertronian Personality Disorder, PA is a condition in which a bot may develop an obsessive interest in any given Prime, which may evolve into obsessive behaviour or thought patterns. 

Common signs of PA include frame alterations to more closely resemble a Prime physically, or altering one’s speech patterns to reflect those of a Prime. 

Psychotherapy and other therapeutic support should be provided on a case by case basis. 

—

Red Rust - Artificially Engineered / Infectious / Degenerative Virus 

Spread by fomite (surface) transmission, Red Rust infection presents asymptomatically until a bot transforms into alt/root mode.

At that point, the virus becomes active in the body, and begins to either weaken structural elements inside the frame or causes fluid cross-contamination via some other means within the body, resulting in the coolant, anti-rusting agents, and dispersants within the fuel lines becoming inert. 

This also results in a chemical breakdown of these materials inside the body, resulting in a corrosion effect, presenting as a bright red rust in the form of thick, red liquid (compared to copper coloured flakes of rust). 

There may or may not be a rust accelerant which is produced as a result of the chemical alterations the virus causes in the body, or if the virus itself may encourage the rapid formation of accumulative rust damage or other similar effect, which would account for the simultaneous internal and external symptom presentation– Although this is unclear. 

—

Rust Rash - Acute Physical Condition 

Rust Rash primarily occurs when a bot has an allergic reaction to a fuel component, although it has also been observed in bots with an overall poor state of repair as well as in those who may be chronically low on recharge or otherwise have overtaxed self-repair nanites, thus allowing for rust to accumulate. 

Rust Rash can be resolved once the source of any inflammation is addressed. 

—

Servo Rust - Physical Condition 

SR refers to an accumulation of rust particularly occurring within the joints and mechanisms of the servos; This is typically an isolated form of rust accumulation, although it may present in addition to any multi-systemic rust infection.

While treatable, SR may present a chronic risk if not addressed and resolved in a timely and thorough manner. It may be notoriously difficult to completely eradicate in more complex presentations, so medical aid may be necessary. Follow up is recommended. 

—

Space Barnacle  - Parasitic Infection 

Space Barnacles generally attack space ships rather than individuals, however circumstances may occur in which a barnacle may seek out the high energy outputs of Cybertronians as a potential secondary fuel source. 

In such a case, a barnacle may then attach itself to the frame of a bot, and leech a significant enough amount of energy that processor functions are impacted, resulting in erratic and potentially aggressive behaviour. 

The best treatment is prevention; Ensure cargo doors etc. on any vessel are secured appropriately and perform routine compartmental scans. Space Barnacles may be vulnerable to heat, contact with liquids, or blunt impact. 

—

Spark Attack - Physical Illness 

A spark attack seems to present primarily in two forms:

-A spark can surge energy output acutely, thus expending more energy than can be immediately re-regulated, resulting in spark damage. Emergency stasis may then be engaged as a reflexive response, to prevent any further damage to the spark.

-A spark can begin to cycle rapidly, thus causing de-regulation of the spark’s internal rhythm (similar to tachycardia in human beings), resulting in a gradual spooling down of the spark which will then eventually cease producing enough energy to operate key systems of the body. 

Resuscitation and medical monitoring may be required to restore spark rate equilibrium and ensure energy output can be safely and appropriately sustained. 

Prognosis may vary based on extent of any spark damage, as well as other individual factors. Spark support may be necessary 

—

Transformation Paralysis (Mode Lock) - Multiple Possible Causes

When incurred by external device (such as a gear disruptor), Mode Lock may be treated by removing the individual from the vicinity of any such device until fully out of range, at which time the transformation cog can be safely tested under medical supervision. 

When naturally occurring (origin non-external), Mode Lock may have multiple potential causes, physical or psychological. 

Individual assessment is required to determine potential causes, with various treatments or additional support such as therapeutic care being provided as needed. 

—

Zero Point - Physical Injury 

A zero point occurs most commonly after blunt force trauma or impact injury to the helm or torso, resulting in a disruption of energy flow from the spark to the various other systems of the body. 

As a zero point is notoriously difficult to detect and cannot be effectively treated, it is often the case that once spark flow becomes restricted to a severe enough degree, a state of stasis is engaged automatically in an effort to preserve system energy.

This state of stasis can then be self-sustained or sustained with medical stasis support for some extended period of time, until the energy flow from the spark is no longer sufficient enough to maintain any remaining spark-frame connection, at which time death occurs. 

There are cases of spontaneous recovery from zero point type injuries including during the stasis stage, however it is not understood how this recovery occurs. 

—

This is not a 100% complete list, but I gotta to go work now, lol.