![[identity profile]](https://www.dreamwidth.org/img/silk/identity/openid.png)
![[community profile]](https://www.dreamwidth.org/img/silk/identity/community.png)
1) Inferno has died, and Red Alert turns to Grapple for comfort, thinking it will help him to be intimate with someone who has a similar frame to Inferno.
2) Inferno has died and Firestar comes to Earth to take care of Red Alert while he grieves, since she promised Inferno she would take care of Red should anything happen to him.
3) It used to be common for those wanting to have their first experience at interfacing to seek out an older, more experienced mech or femme with the same or similar frame type so they could learn all about their hot spots.
Thus Grapple was Inferno's first.
4) All sparklings are born/created with attachment programming that allows them to bond with their creators or caregivers. When Megatron created the Stunticons, he thought he had omitted this, but Vector Sigma automatically corrected this as an oversight. Of course no one behaved very nurturingly towards the Stunticons, so the programming remained dormant.
Then some Autobots end up having to help out the injuried Stunties, and their caring behaviour triggers their attachment programming.
Motormaster, of course, attaches to Optimus Prime, Breakdown to Red Alert... not sure about the rest.
The attachment programming doesn't prevent them from harming the people they are attached to, but it does create feelings of wanting to recharge next to them, cuddle with them, and be close to them, and to be loved and nurtured by their surrogate creators in return.
As a side effect, the attachment programming also sends out signals to the surrogate creators that trigger their own creator protocols, so they get all broody and protective towards their 'offspring'.
Chaos ensues.
5) It seems to be firmly entrenched in fanon that, in the case of sparkbonding, if one partner dies the other one shortly follows.
However, what if there was a very important exception to this: the partner who was left behind did not die if they were carrying. Perhaps it is only when they are carrying at the time of death, and the body's programming to protect the new life cushions the shock? Or perhaps it applies to any spark-bonded pair who has sparklings who are too young to survive on their own?
In the case of carrying specifically being the catalyst, do they die once the sparkling/new spark has been removed from their bodies? Or, for more angst, are they compelled by some programming to raise the sparkling to maturity before succumbing?
What if after raising the sparkling their spark strengthens again, and they are strong enough to carry on by themselves?
What if they aren't?
How does the sparkling deal with knowing their creator will die when they are independent? Do they purposefully retard their development in an effort to keep their beloved parent with them longer?
6) What sparkbonding to a larger group meant a higher likelihood of survival if one of the partners was killed? Thus a trine could lose their third and possibly still live? Perhaps the likelihood of survival increases with the number of partners who are around to support each other in the case of a loss? Conversely, multiple losses, even in a larger group, are naturally even more painful and risky.
2) Inferno has died and Firestar comes to Earth to take care of Red Alert while he grieves, since she promised Inferno she would take care of Red should anything happen to him.
3) It used to be common for those wanting to have their first experience at interfacing to seek out an older, more experienced mech or femme with the same or similar frame type so they could learn all about their hot spots.
Thus Grapple was Inferno's first.
4) All sparklings are born/created with attachment programming that allows them to bond with their creators or caregivers. When Megatron created the Stunticons, he thought he had omitted this, but Vector Sigma automatically corrected this as an oversight. Of course no one behaved very nurturingly towards the Stunticons, so the programming remained dormant.
Then some Autobots end up having to help out the injuried Stunties, and their caring behaviour triggers their attachment programming.
Motormaster, of course, attaches to Optimus Prime, Breakdown to Red Alert... not sure about the rest.
The attachment programming doesn't prevent them from harming the people they are attached to, but it does create feelings of wanting to recharge next to them, cuddle with them, and be close to them, and to be loved and nurtured by their surrogate creators in return.
As a side effect, the attachment programming also sends out signals to the surrogate creators that trigger their own creator protocols, so they get all broody and protective towards their 'offspring'.
Chaos ensues.
5) It seems to be firmly entrenched in fanon that, in the case of sparkbonding, if one partner dies the other one shortly follows.
However, what if there was a very important exception to this: the partner who was left behind did not die if they were carrying. Perhaps it is only when they are carrying at the time of death, and the body's programming to protect the new life cushions the shock? Or perhaps it applies to any spark-bonded pair who has sparklings who are too young to survive on their own?
In the case of carrying specifically being the catalyst, do they die once the sparkling/new spark has been removed from their bodies? Or, for more angst, are they compelled by some programming to raise the sparkling to maturity before succumbing?
What if after raising the sparkling their spark strengthens again, and they are strong enough to carry on by themselves?
What if they aren't?
How does the sparkling deal with knowing their creator will die when they are independent? Do they purposefully retard their development in an effort to keep their beloved parent with them longer?
6) What sparkbonding to a larger group meant a higher likelihood of survival if one of the partners was killed? Thus a trine could lose their third and possibly still live? Perhaps the likelihood of survival increases with the number of partners who are around to support each other in the case of a loss? Conversely, multiple losses, even in a larger group, are naturally even more painful and risky.
no subject
Date: 2010-11-20 12:15 am (UTC)no subject
Date: 2010-11-20 02:17 am (UTC)no subject
Date: 2010-11-20 11:31 am (UTC)no subject
Date: 2010-11-20 02:45 am (UTC)5 - My first thought was that the carrying person would end up with a stronger than normal parent bond with their sparkling, that keeps them alive while the sparkling is alive, even after it's old enough it could survive on it's own. That could still cause issues in some sparklings, knowing they're the one keeping their parent alive.
The exception being if the parent bonds to someone new, then their spark is stablized by that bond and the parent bond can wane a bit.
Added plot idea: There's a pair of mechs in the Ark crew who are a parent child pair, held together by the parent's dependance on their family bond. Said parent constantly worries for his sparkling in battle, said sparkling worries even more that if he gets killed in a battle, it'll kill his carrier as well. Then there's the mech who wants to romance the parent...
Said parent constantly worries for his sparkling in battle...
Date: 2010-11-26 04:59 am (UTC)Great minds think alike!
Date: 2010-11-26 05:05 am (UTC)Also, it is probably obvious that the other mech is likely Jazz. While I'm not a dyed in the wool shipper of them, they're still a good pairing that I don't mind.
Re: Great minds think alike!
Date: 2010-11-26 06:08 am (UTC)no subject
Date: 2010-11-20 05:00 am (UTC)no subject
Date: 2010-11-20 12:05 pm (UTC)to No.1, Red would be srsly disapoint... imho. Such an angsty theme! *shivers* Poor bot, we put him into such misery all the time.
No.3: hehe. Grapple has no love from the fandom, time to make him tehh sex-machine!!
No.2: why im hating Firestar with a fervent passion? It would be a sadistic fic if i d happen to write it.
No.5: Dealing with sparkbond, those are good points... parent-child relationship wasnt really discovered by fanwriters.
no subject
Date: 2010-11-26 05:02 am (UTC)no subject
Date: 2010-11-26 05:03 am (UTC)