The Mech Touch novel Chapter 3148

Chapter 3148: Growth Framework

The moment Ves came up with the concept of a two-stage or evolvable companion spirit, it was as if lightning had struck his body.

The potential of this idea was a lot greater than a regular companion spirit. Instead of deciding everything on behalf of the recipient from the start, Ves could just create a more open-ended spiritual product and allow the user to choose from one of several different specializations in the future!

"In fact, this idea can be applied to more than just a companion spirit!"

Ves even felt it could be applied to mechs as well as many other applications with spiritual components.

He could already imagine a future where he incorporated this novel concept in a versatile mech like the Bright Warrior Mark III. While there was no denying the mech had to be bland from the start in order to ensure maximum compatibility with different kinds of mech pilots, as they grew from continual use, that might slowly change.

Along with slowly becoming more adapted to their assigned mech pilots, the next-generation Bright Warriors would also be accumulating energy for a breakthrough. Once a given mech gathered enough energy, the pilot could choose to initiate a breakthrough, allowing the user to choose and lock in a particular spiritual specialty or advantage that complimented the person's fighting style the best!

"Still… it's a bit premature to apply it on any mechs."

He immediately recognized several problems with this particular arrangement. First, mechs were rarely the exclusive property of any mech pilot. It was customary to reassign mech pilots from one mech to another one when situations changed.

This meant that it was not entirely practical to apply this tiered evolution concept to mass production models. The only way this arrangement would make sense was if the owners of the mechs deliberately adopted a long-term pairing approach, essentially turning mechs and mech pilots into married couples that lasted for at least a decade.

Ves could implement this easily enough in the Larkinson Army, but he wasn't entirely sure if this was the right strategy to adopt for his troops. As a mech designer, Ves frequently designed new mech and better mechs. Since the founding of the clan, the oldest Larkinson mech pilots already had to switch their mechs several times as newer and better machines became available.

"Ugh, all of this is too complicated. I'll just talk to General Verle about it in our next meeting."

The most relevant part about the evolvable companion spirit concept was that he could easily apply it to his children and other people for that matter.

The only real limitation he had to take into account was the spiritual capacity of the recipient.

While Ves could attempt to create a living spiritual construct that was stuffed with powerful abilities, that would increase its spiritual weight to a point where it could easily crush any person's spirituality if he tried to merge them together!

The good news was that his unborn child's spirituality was stronger than normal, most likely due to her lineage along with his own active intervention.

The bad news was that she was only strong in relative terms. She was still a rather small collection of cells at the moment and had many months of gestation ahead. Even if she was born and grew up into an active toddler, it was highly unlikely that her spirituality would match that of himself.

"She's too young."

Just like mech design, Ves could not possibly add everything in his wish list into a single mech design. He had to plan the capabilities of his next companion spirit extremely carefully in order to add what was necessary while leaving out as little bloat as possible.

"It's like designing a third-class mech again…" Ves depressingly said. "No, it's worse. It's like designing a fourth-class mech that is only a quarter the size of a normal machine!"

Fourth-class mechs officially didn't exist, but it was a popular colloquial term that a lot of people used to describe a mech built way below standards.

If that was the only issue, then Ves could still work something out, but the fact that he had to slim his product down by a huge amount was especially painful!

Fortunately, Ves was not completely out of options. As a mech designer who played around with the concept of growth in several different occasions, he already had a good approach in mind.

"Instead of creating a strong and functional companion spirit right out of the bat, I'll create a seed instead!"

This approach reminded him of the biotech industry's method of production. Ves could never forget how the biomech designers of the Life Research Association literally grew their mechs as if they were cloned bodies.

The key to doing this was to artificially synthesize a biological seed. This ball of flesh and bone was not a functional mech but contained the core structure as well as the growth instructions of a biomech.

By placing these biomech eggs in giant nutrient pools, their biological programming would automatically extract useful materials from the culture medium and slowly grow the seed into a biomech.

While there were pros and cons to this alternate method of production, it was a viable and proven approach that seemed to work well for the Lifers.

"I can just copy this approach and apply it to my companion spirit!"

In fact, he was already doing something similar with his own spiritual products, though he did not explicitly think about it. Therefore, he didn't need to make too many changes.

He just had to condense his initial creation into a small and tiny spiritual seed before planting it in someone's spirituality. That person's spirit would essentially act as the culture medium in this case and would channel useful nutrients in the form of spiritual energy and possibly other intangible resources in order to allow the seed to bloom into a powerful companion spirit over time.

There were several potential ways that this could go wrong, though.

"What if the relationship between the two becomes parasitic instead of symbiotic?"

Verify captcha to read the contentVerify