crispy-art-on-fire

[crispy-art-on-fire]

Liking character is fun until you think about them and you just have to stare at nothing for a few minutes because of how tragic

And mauybe you are almost crying but you are having fun

[crispy-art-on-fire]

woahhhh megatron be looking pretty, acting like an evil little guy but fine as hell (I’m sorry lmao)

He's so fine and for what.

[crispy-art-on-fire]

Crispy when I find you…..

Oh? Just for making him cry?

[crispy-art-on-fire]

Metal_Bar.mp3

Accurate

[crispy-art-on-fire]

[Previous]

I will give that an E grade on dealing with the break up well.

One more comic left of this act! After that I shall prick my finger on a spinning needle and fall into a sleep of 100 years before act 2.

[crispy-art-on-fire]

Is it common for nervous carriers to acidently cause the sire's coding be be wonky if they themselves are paranoid? Like i get the blitz did it to prime on purpose, but could it happen on accident?

Yep! When a Carrier is suitably stressed the Sire coding will be on alert regardless if there is any dangers.

I have been thinking of making like a B-Side to the Carrier!Optimus fic where it follows Team Prime and how they can tell Optimus' deteriorating state by Blitzwing's behavior. But the main fic is like 7000 words and I got 10 scenes left to write so we'll see if I'll ever get around to it.

[crispy-art-on-fire]

Man this art is mid *walks away with an art shaped lump in my jacket*

Awh :( I guess I'm not your taste- HEY!

[crispy-art-on-fire]

Okay this was originally supposed to be a wholesome ask about carrier Optimus getting taken care of by his team but now I'm curious on if there's some kind of social taboo among cybertronians on making bots that the carrier is in an entirely platonic/familial relationship with a sire? Or anything like that

Maybe it differs depending on what part of cybertron a bot is from or frame type? The culture and traditions of transformers have always been a lot more interesting to me then how they work on a technical level

I'm sorry if this doesn't make much sense I'm a bit slow

No there isn't any taboo about it. There is a recognized need and purpose for a Sire so the personal relationship between Carrier and Sire. Shockwave and Jazz for example while they have queerplatonic feelings for each other basically Jazz offered to be a Sire because Shockwave wanted to have a sparkling, they're not officially together or anything.

If we consider taboos sexual reproduction is looked down upon in general because of its coding being from an older time. It doesn't help that most success comes from a pairing of very different frames which creates new unclassified frames. As a society which rely almost solely on asexual reproduction, in which the sparkling appears as an almost copy of their 'mold', it has been very easy to standardize and control it while sexual reproduction is basically the opposite of control.

I'll get into it more at a later date once I finally bite the bullet and write about TFA Asexual Reproduction which ironically enough is a lot heavier topic with how it intersects with the politics of Autobot society and functionalism.

Also familiar relationships are discouraged as a rule. The societal expectations are still that when a sparkling loses their handle they are to be put in the system as a worker with Caretaker(s) becoming an unrelated third party. Family between people is an alien concept to most Cybertronians.

[crispy-art-on-fire]

Oh my god?? You can not say ‘I have thoughts on carrier and sire coding’ and not share them!!

TFA Carrier and Sire coding

Basically an extension of my Cybertronian Reproduction headcanon going more into the mental changes of the process.

Note that this is different from Caretaker coding, which involves actually caring for the sparkling. Carrier/Sire coding is only active during the pregnancy.

TW for discussions around death, child death, postpartum depression and psychosis. Now to get into it:

The coding lies dormant in most Cybertronians while the requirements of its activation are not met. Though its not an universal rule as some people don't have it or have removed it from its processor, the latter being much more common during the Great War as high stress would often pose more of a risk than a gain.

Carrier coding is activated once the sparkling drops into the gestational chamber as it will have met the requirement of a viable pregnancy. The purpose of this code is to keep check of the sparkling's vitals and ensure a healthy development of the sparkling and ensuring the carrier remains safe.

Meanwhile Sire coding is activated once the a Cybertronian is recognized as the Sire by the Carrier or requests to be the Sire. This will then link the programs together and the Carrier programming will be able to sent information to the Sire. The purpose of the Sire coding is to ensure the safety of the Carrier and be able to provide for them. There is no limit on how many Sires a Carrier can have.

The most common ways Carrier coding will manifest is through cravings and passivity. Cravings, as touched upon in the reproduction part, is to ensure intake of metals required for healthy sparkling development. The coding will send commands for specific metals and the processor interprets it through cravings.

For passivity it has to do with the secondary goal: Protecting the Carrier and Sparkling. Often when carrying the Carrier will rarely if ever leave designated safe areas, such as familiar places or nest, and will spend most of their time resting to conserve fuel and avoid risky behavior. The more stress a Carrier is under the more severe this risk avoidance gets, isolating from anything that is not the Sire(s). Carriers forced into risky or harmful situations they cannot avoid if stressed enough will execute any command to get out of it.

This leads to a Carrier Code Override: When a Carrier is dying as a last resort the Carrier program will take over and force any nearby Cybertronian to have their Sire coding active. Radically shifting priorities to protect the Carrier and Sparkling regardless of prior feelings or affiliations. Because of this during the war it was set in place that Carriers were not to be harmed by either side and research went into being able to disable this type of programming.

For Sires there are three main modes of acting: Providing, Guarding and Comfort. With the Carrier program providing the needs of the Carrier the Sire will respond subconsciously to these needs and feel stressed out when they cannot preform the tasks. The more built up the Carrier's needs are the more space they will take up in the Sire's processor. A Sire is also unable execute thoughts or actions that will harm the Carrier as the coding will delete those commands.

Providing is self explanatory, a Sire will get commands to give metals, fuel and transfluid to the Carrier. Often this will take priority over the Sire's own needs.

Comfort is the one way the Sire coding communicates to the Carrier coding. Signaling that a Carrier is safe and reducing stress or distress. It also makes Sires more prone to physical affection to further soothe the Carrier. In high stress situations a Sire can be bordering on clingy. Having the Sire coding force a Carrier to calm has a more tranquilizing effect than actually reducing stress.

The Guarding part of the code makes it so that the Sire cannot leave the Carrier undefended for long periods of time. In peaceful times this can manifest as anxiousness at being seperated and a need to 'check in' at the Carrier's status. During times of conflict or high stress this manifests as aggression, inability to leave the Carrier, and frequent threat displays.

This leads into Sire Code Override, which is often engages after a Carrier has been under a lot of stress over a long period of time before being triggered by a failure of the Sire. Most common the trigger is the Carrier being hurt but it can also be starvation. Once the override is engaged the Sire will prioritize the health and safety of the Carrier over all else and stop being able to understand anything that doesn't have to do with this task.

Carrier/Sire Code Overrides goes away on their own after the Carrier is safe.

If a Carrier dies a Sire during an override can try to transfer the sparkling into their own gestational chamber and become the new Carrier. This is rarely successful.

Carrier and Sire coding disengages once the sparkling is removed from the gestational chamber. However this sometimes isn't the end of it in cases of Carrier/Sire code corruption. This leaves the coding engaged but in a warped state as there's no longer any newspark to track. How exactly this corruption manifests depends on the person but there are some common classifications.

In Carriers the corruption has the most potential for damage. Type A corruption leaves the Carrier coding still engaged as if it still is incubating a sparkling, but as there is no reading of the sparkling the coding will automatically go into emergency mode in trying to divert all the Carrier's energy into keeping the non existent newspark alive. The Carrier with a Type A corruption experiences fatigue, lethargy, and apathy as well as having a harder time seeing the actual sparkling as 'theirs' or having Caretaker coding unable to engage.

Type B corruption is focused on the newborn sparkling. As the programming is meant for when the sparkling is still inside of the Carrier, the corruption allowing it to persist will sent errors and bad information to the Carrier about their sparkling and the state of their body. Sparkling's behavior will come across as wrong or unnatural to the Carrier as the preprogrammed expectations are unmet or subverted. The Carrier may also get commands to force the sparkling back into the gestational chamber or prevent them from 'acting out'. The sense of wrongness also extends to the former Sire as, assuming the coding disengaged as normal, the Carrier programming will no longer recognize them. This can translate to the Carrier believing that the people around them has been replaced and distrust even close friends. If not treated Type B corruption can lead to the death of the Sparkling, from the Carrier's own servos or from neglect.

In Sires the corruption often manifests as a more severe continuation of previous behaviors and before diagnosed can be mistaken as 'over protectiveness'. The lack of signals from the Carrier program causes the Sire to manually check up on the Carrier and sparkling near constantly and find it hard to be able to separate from either. If the Carrier died and the Sire Coding corrupts it can leave the Sire in a permanent state of Override and without intervention will attempt to care for the Carrier until offlining.

Code Corruption can be treated in numerous ways: Though software patches, were one downloads additional programming in order to correct the misconceptions or put in guard rails to prevent the worst case scenarios (these can also get their own glitches to look out for). Disabling the program, a solution good if one isn't planning to be a repeat Carrier/Sire as if the coding is reengaged it might still be in its corrupted state. Waiting under supervision as the processor itself with time clears up the errors. Or removing the program completely, allowing no risk of repeat corruption but also without ability to monitor if one is a future Carrier/Sire.

Attempts to modify the source coding itself has found that errors and corruption are more likely to occur.

[crispy-art-on-fire]

It's done. I beat it up and it's here. I apologize for taking literal months.

https://archiveofourown.org/works/69622516

SCREAMING AAAAAAAAAAAAAAAUFG. ITS SO GOOD. Blitzwing's confession had me kicking my feet and giggling and I want to pick up Optimus like a chew toy and shake him around. That ambiguous/open ending wasn't kidding!!!!

[crispy-art-on-fire]

You take requests?? Well, well, well, I saw a lot of wonderful pregnant optimus, and a lot of talk about how Blitzwing would be as a carrier.. but I don't think you've drawn them as a carrier yet. Indulge me, please 🙏

Blitzwing didn't actually have such a hard time carrying, both of his bigger size and Team Prime being much better captors. Mentally however Blitzwing was mostly in pure survival mode.

While officially surrendered he wasn't going to go through with it (because who can trust Autobots?) and so used Optimus' sire coding to override his better judgement to help them escape.

I HAVE A BASIC PLOT FOR THIS FIC BUT I HAVE PLOTS FOR A LOT OF THINGS- Anyway in this timeline Blitzwing and Optimus don't talk anymore bc Optimus attacked his friends before Ratchet could disable his sire coding and in the chaos Blitzwing escaped.

[crispy-art-on-fire]

your comics are such a bomb!! Please keep them coming!! I love your blitzprime ❤️

Thank you! I currently am working on the next comic which is trying to kill me but that's usual with action scenes. Have a sneak peak that's probably incomprehensible.

[crispy-art-on-fire]

Hello, I've been watching your blog for a long time and I'm interested in your universe. But I have a request, can I copy a moment from your Comic?

Do you mean like a panel redraw? If so yeah go ahead so long as you credit me and @ me, I'd love to see it! :]

[crispy-art-on-fire]

[Previous] [Next]

The team talks about it. More lighthearted in comparison to the surrounding content I really enjoyed adding some humor into it.

I was wondering if I was going to make this or the next comic first but settled on this so the next two comics have a more spiraling feeling. But yeah! Hellish for my brain to need to include the team all the time and so forcing me to draw multiple characters but I think its important to show that Team Prime is like, friends.

[crispy-art-on-fire]

Sad lil blitzwing in that last post was adorable please make him experience more emotional agony

You will be very happy in three comics :)

[crispy-art-on-fire]

Do you think they can have a healthy relationship? The closest one is wings ig i cant see anything toxic about how he treats optimus other than being a bit cold at times. Blitz is completely obsessed ( and maybe codependent) with optimus which isn't healthy and we saw how things went with zing. Just a thought (also i do want optimus and blitzwing to get back together and maybe go to therapy)

Yeah they could definitely could have made it work. A thing I enjoy about tragedies is that you can spot moments where they could have avoided this but understand why they couldn't see a way out.

If it's about BlitzOp in general and not just my comic then the answer is still yes because their lack of dynamic in canon makes it free game playing with them like dolls. You can give them their happy ending <3 Make them go to therapy.

[crispy-art-on-fire]

So there isn't really a good character for this in tfa, but i just have this little scene stuck in my head now.

So some other con cought wind of the 'fling' and decided its non of their business.

But then they see blitzwing crying, so they go out, kidnap optimus, and drop him in front of blitzwing like, "I dont know what you did, but you WILL apologize."

So now optimus is wrangling with the fact he made blitzwing cry while also being judged for it, while blitzwing can't decide if he wants to laugh at the absurdity of the situation or keep crying.

THIS IMAGE WAS TOO FUNNY TO ME. Genuinely I think this would have fixed the timeline. Unfortunately Blackarachnia and Blitzwing aren't friends so she doesn't have a reason to check in if his relationship has exploded yet.