Ep1 - "Got A Klik?" - Closed
Jun 19, 2012 14:25:33 GMT -5
Post by Deleted on Jun 19, 2012 14:25:33 GMT -5
::No, Starscream doesn't know.:: Knock Out felt pretty confident in that assumption. Given that Barricade was still alive and all.
On the other hand, he almost laughed at Barricade's assumptions about his spark-related expertise. ::I'm sure that tracking a quantum-bond is theoretically possible, but sparkwork is very much NOT my specialty. I can't do it. A quantum engineer, perhaps....::
The diagnostic came back clean, and one last touch of the welder had the hardware in place. More quick-cool and it was solid. Not pretty, and likely to crack if Barricade needed to use it in the next cycle, but solid.
Knock Out dared the distraction of opening up to the general comm channels as he sent along the patches to find and update Barricade's weapons subroutines. He caught Barricade's name at least three times in as many kliks. Starscream was not one to listen to such things, but with that level of chatter, it wasn't going to be long before he heard something.
The software diagnostic came back clean, and Knock Out sent a minor completed/good to go ping to Barricade, then considered next steps. He wasn't going to touch the processor issues, and the flail was out of the question right now, but a blade would take almost no time. As for the spark....
Knock Out tapped a claw on the berth slowly in thought. He felt rather like he was doing neurosurgery with a hammer and chisel, but there was no time for subtlety. Or proper consultation of his hodge-podge of texts. Or TACT. ::I CAN, however, give you a sparkline inhibitor software patch. It will baffle your systems from most of the data your spark sensors are sending. Cut off the pain, but likely also make it impossible for you to sense anything along the alignment bond. This will...hmm. If you were uninjured, I wouldn't recommend it, as your programming has grown somewhat accustomed to the bond data and cutting that off is a wonderful way to drive an aligned insane. But there are extenuating circumstances, and having it online for a few cycles should be fine.::
On the other hand, he almost laughed at Barricade's assumptions about his spark-related expertise. ::I'm sure that tracking a quantum-bond is theoretically possible, but sparkwork is very much NOT my specialty. I can't do it. A quantum engineer, perhaps....::
The diagnostic came back clean, and one last touch of the welder had the hardware in place. More quick-cool and it was solid. Not pretty, and likely to crack if Barricade needed to use it in the next cycle, but solid.
Knock Out dared the distraction of opening up to the general comm channels as he sent along the patches to find and update Barricade's weapons subroutines. He caught Barricade's name at least three times in as many kliks. Starscream was not one to listen to such things, but with that level of chatter, it wasn't going to be long before he heard something.
The software diagnostic came back clean, and Knock Out sent a minor completed/good to go ping to Barricade, then considered next steps. He wasn't going to touch the processor issues, and the flail was out of the question right now, but a blade would take almost no time. As for the spark....
Knock Out tapped a claw on the berth slowly in thought. He felt rather like he was doing neurosurgery with a hammer and chisel, but there was no time for subtlety. Or proper consultation of his hodge-podge of texts. Or TACT. ::I CAN, however, give you a sparkline inhibitor software patch. It will baffle your systems from most of the data your spark sensors are sending. Cut off the pain, but likely also make it impossible for you to sense anything along the alignment bond. This will...hmm. If you were uninjured, I wouldn't recommend it, as your programming has grown somewhat accustomed to the bond data and cutting that off is a wonderful way to drive an aligned insane. But there are extenuating circumstances, and having it online for a few cycles should be fine.::