Chapter 44: Chrono bubble - 44
Aqua's POV - Tokyo, Japan
Good news: Lap pillows are awesome.
Bad news: I was getting a lot of stares while lying on Amy's lap on an outdoor bed inside a gazebo.
Another head pat made me calm down. Honestly, it's too heavenly here to bother moving. Let them stare! I know you gals want the same thing, I thought smugly my imaginary tail wagging a little as I basked in my comfort.
Thwack! A light karate chop landed on my head.
"Keep it calm," Amy said with a sigh.
"Fine," I replied, trying to stifle my grin.
Helena sat next to Amy, sulking visibly. She had just lost another game of rock-paper-scissors, which meant she wasn't the one being used as a lap pillow.
Back to what I was working on before they forced me into Amy's lap: Chrono Bubbles.
To be fair, having time acceleration, deceleration, and stasis capabilities is incredibly useful. The real challenge was figuring out how to project it at range which is not a problem really as I got Chronosphere after this to figure out.
Then there was that "larger on the inside" phenomenon—an absolute mess of calculations. To simplify: you create a space and shift its time to the moment it was first created. Both versions of the space now exist simultaneously in the same physical area. By creating a connection between the two—when the bubbles touch each other—you gain access to both spaces.
In theory, you could design a single building floor, make the elevator a separate entity, and create overlapping spaces for that floor ten times. This means the elevator could access 10 distinct "floors," all contained within the physical footprint of one real-world floor.
"How does each floor get additional space if it's just overlapping?" you ask? Simple: you shift one of the three spatial axes slightly so they're not perfectly overlapping but still connected. Voila!
Thanks to my experience using Unity on this—it feels a lot like copying and pasting objects in a simulation. To fix overlaps, you just move things to the side.
And that's how the fricking Paradox Engine works. That sci-fi monstrosity of a capital ship has interior space five times larger than its already massive exterior of 20 km. It has countless exits, hangars for fighter wings and bombers, room for MCVs, bases, infantry, vehicles, factories, and so much more.
Comparing this world's tech to other sci-fi universes, it's...unbalanced. Is that the right word?
Take Mass Effect or Halo. Sure, they have FTL travel using Eezo or Slipstream. But Red Alert verse? We have space extensions, time bubbles, and dual shield types (Chrono bubble, Iron curtain) that make us practically immune to damage.
If only this world had superior reactor technology, they could probably go interstellar. Right now, the biggest bottleneck is energy generation. And considering all the infighting and constant world wars, it's not like any faction here could build megastructures like Dyson spheres for extra energy.
Wait, didn't the Allies solve the energy issue when they created the Paradox Engine? Hmm… can't recall the exact details buried in the deep lore of the game.
With all this theory, I should be able to fit in a lot more equipment and tech on myself. Why focus on me? Because I want to fly, dammit! Diving underwater is cool, tactically viable, and all that, but it's so freaking slow! Why do I need to spend eight hours diving back from Japan to my main base? It's another six hours just to reach the Pearl Harbor base.
Well, now I can change that. With the Iron Curtain, I can technically create an artificial sun. But wait, isn't an artificial sun basically nuclear fusion? Would it even produce more energy?
I stretched again, pondering the possibilities.
"Stuck?" Helena asked, breaking my train of thought. I looked up from my cozy position on Amy's lap.
"Kinda. I'm going to need new reactor tech," I replied. "This world lacks exotic materials for advanced power generation."
"Ehh, so your artificial sun plan isn't working?" Helena asked, raising an eyebrow.
"Wasn't it you who suggested it?" I shot back.
"Anyway, it doesn't generate that much more energy than stacking four nuclear fusion reactors together. Especially if I want to miniaturize the sun into something small enough for practical use."
"So... we're going to need something bigger, like a black hole?" Helena mused.
"Too far-fetched. I don't even know if the Iron Curtain can handle the extreme gravity required to make that work," I replied, shaking my head.
"Zero-point energy?" Helena offered.
"That only works in Stellaris... Actually, how does that even work? I know it involves extracting the lowest energy state of an atom, leaving it at the same lowest state indefinitely, supposedly resulting in infinite energy."
Wait... that's just a feedback loop, isn't it? If I can manipulate time, I could theoretically create an infinite feedback loop. Or, better yet, an infinite replication loop for increasing energy output overtime!
"Helena, you're a genius!" I exclaimed, bolting upright as an idea struck me.
I started by setting up a single nuclear fusion reactor—a 3x3x3-meter cube—as the core. I'd deal with the energy parts for overlapping and resetting the chrono bubble later.
The setup was straightforward: one nuclear reactor outputting energy to a nanoswarm deployer. With a 25% efficiency rate for transmuting pure energy into nanoswarms, I calculated that four reactors would suffice. Scratch that—make it six reactors to ensure a positive energy output.
The energy replication box was done. Next, I added two control boxes: one to contain the whole thing within the Iron Curtain and another to initialize the chrono bubble. This bubble would continuously overlap the replication box, effectively looping it forever.
Stacking the two control boxes as a baseline, I ran a quick simulation to see how much space the overlapping chrono bubbles could generate.
The graph showed a low incline, a diagonal line. Perfect—manageable growth without exponential spikes. Unlike concave-up curves or steep 45-degree slopes, this setup wouldn't spiral out of control.
Now for the limits. If I wanted a 9x9x9-meter box for energy generation system and containment to overlap, how much alternate space could I get away with? I clicked the repeat button in my simulation app to test the stacking until it broke.
Twenty clicks in, I got lazy and automated the process, speeding it up by 10,000x. While waiting, I glanced outside the gazebo.
The sun was setting. Night was creeping in as the light around our resident area turn on, supports model who handle this base do a good jobs decorating.
Amy and Helena were staring at each other, sparks practically flying between them. Not literal sparks, of course—it just felt like that. What were they arguing about now?
*ding*
As I was about to ask, an error sound from my designer app.
"What the—?!" I muttered. I had never heard it make a sound before.
The screen went white. The white screen of death as the spinning wheel appear in the middle of the screen.
'Quick, before it shuts down!' I thought, scrambling to read the last displayed value.
9.22337×10¹⁸.
Wait… isn't that the 32-bit limit? No, 32-bit starts with 2. This must be the 64-bit limit, then!
Before I could do anything, the designer app auto-closed.
"…Well, that was anticlimactic," I muttered, slumping back onto Amy's lap.
Does this mean we're in a simulation? Or is this just the limit of the designer app? Either way, I'll need to scale the graph down to a value of 64-bit limit minus 5, just as a precaution. I also have to account for control boxes overlapping in space, leaving only three free bubbles—two for emergencies and one for a unique case where the reactor's structure might end up inside another bubble.
This could also serve as a slot for stasis fields or something with long-range effects.
Actually, I should probably cut off 100 as a rounding error. I really don't want to find out what happens when chrono bubbles overlap past the 64-bit limit—at least not before I figure out how to make universe-hopping work. Speaking of which, to pull that off, I'd need to travel back in time to a turning point. No idea when that is yet, but I'll need Scrin's tech to even attempt it.
And that's another timeline I want to play with. Imagine if I could one-up Kane and create my own cult that's just as popular. Wouldn't that be fun? But that's a plan for later.
"Master~ news from the MCVs," Helena said, snapping me out of my thoughts.
"Yes?" I replied, tilting my head to look at her.
"Coastal defenses are finished, Master~. The next step is city reconstruction. They're asking for permission to proceed since it overlaps with the Hokkaido training."
"Ah, that. Tell them that all of Hokkaido will be done last. You and Amy will wreck everything there first during training. Wait, coastal defenses are already built on Hokkaido?" I asked, shifting my position on Amy's lap slightly.
Helena nodded. "Yes, Master."
"I assume Avalon laser cannons are part of those defenses?"
Helena paused, likely checking with the MCVs, before nodding again. "Yes, Master."
I sighed. "I'll need to inform the Japanese generals about these installations, and make it clear that they're not part of the training exercises—otherwise, it'll be overkill."
As I stretched and gathered my thoughts, I said, "Well, you two might as well listen in. You're going to be the ones to crushed them and training them back up after all."
With that, I forcefully connected to the Allies' network again. How many times have I done this now? More than ten? They probably annoy by this a lot.
Japanese General Ironwood's POV - Somewhere near Mount Furano, Hokkaido, Japan
"Any news from the squads sent to inspect the construction?" I asked in a stern tone, rubbing my temples. The workload was overwhelming, especially as I tried to decipher why the Abyssals were building what they called 'Avalon Laser Cannon Turrets' across the mountains near the coast. Were they planning to box us in?
And that wasn't even counting the double line of pop-up turrets along the coastline.
"No news, sir!" the comms officer reported. At least the landlines and radios within the fog were still operational—somehow. Whatever the Abyssals used to create the fog could apparently be controlled to allow communications within its confined area.
Suddenly, static interference crackled across the main screen. I sighed, bracing myself for whatever this was going to be.
("General Ironwood.") The voice of the Abyssal Commander rang out.
It was voice-only this time, but the fact that she contacted me at all meant she had returned.
"Abyssal Commander," I replied. "Is this about the defensive towers popping up all over Hokkaido?" I asked bluntly. The reports from other commanders heading toward Hokkaido also mentioned encountering various coastal defenses along the way. If these installations were included in her planned training, it would drastically change how we approached the tests.
("Ah, yes. All Hokkaido defensive installations will be excluded from the test. They'll remain on the map, but they'll be inactive. I'm not so cruel as to let you face something capable of destroying a capital ship in one hit,") she clarified, her tone almost casual.
I let out a silent breath of relief as she continued.
("Also, civilian evacuations are scheduled for tomorrow. My faction needs to finish renovating the Aomori region—towns and cities around it—to handle Hokkaido's displaced population.")
That was… unexpectedly thorough of her.
("Hokkaido will be the last area to undergo a full upgrade. All city destruction will be permitted during training since we'll rebuild everything afterward. Training will begin in three days at most. Understood?")
"Yes, sir," I replied as the connection cut off and the screen returned to normal.
"Call our scouting squads back," I ordered, turning to face the map of our base.
"Commander Rijin and Commander Teso have joined the operation and are currently setting up in Sapporo, General," another comms officer reported.
Good. With five commanders now stationed in Hokkaido, we should be able to hold out for at least two days during the exercise. From what little I knew of the Abyssal Commander's right and left hands, gleaned from the accounts of surviving GIs from Niigata, one was a sniper supported by drones, and the other was some sort of explosives expert.
Not exactly comprehensive intelligence, but I'd soon see how they performed firsthand.
The one small silver lining in all this chaos was that I wouldn't need to stick to the safest tactics. This was a live combat scenario, not a real invasion, which meant I could prioritize gathering intelligence. Granted, most of that intel would become outdated once the Abyssals rolled out new gear and equipment, but any advantage, however brief, would still be worth it.
Amy's POV
"Well, I'm done with that. You've got the map, and in three days, the training will begin," Aqua said, shifting her position slightly. She was using my lap as her pillow, her fingers busy navigating her designer app.
I smiled softly and patted her head a few more times before focusing on the 3D holographic map of Hokkaido.
Thirteen outposts and six major bases so far. With two more commanders still en route to Hokkaido, it looked like there'd eventually be around twenty outposts and eight major bases.
I glanced over at Helena. She tilted her head thoughtfully before speaking. "We should start from the bottom~," she suggested with a teasing lilt in her voice. "It's easier to clear them out grid by grid," she added, flashing me a mischievous grin.
I nodded in agreement. There was a lot of planning to do, especially while Aqua-chan was engrossed in her work with the chrono bubble.
"Let's start organizing," I said, rolling up my sleeves. Helena leaned closer to the map, ready to strategize, her usual excitement bubbling to the surface. This was going to be interesting.
Aqua's POV
Ah, more headpats. They always feel nice. I let myself enjoy the moment while I focused on rebuilding the template for the replication reactors. I set the replication cap to just 100 short of the 64-bit integer limit as a precaution, don't want my designer app to do another white screen of death.
The actual control boxes were designed as double-stacked L-shapes. The first control box measured 9x3x3 meters, starting from a basic reactor of just 1x1x1 meter. This box housed 27 reactors feeding directly into the Iron Curtain device.
One part down. Now for the second double-stacked L-shaped control box for the chrono bubble. Like the first, it was powered by 27 reactors. Together, these systems would generate enough energy to handle the initial 2 to 3 billion overlaps. To keep the system running, I allocated four replication reactors to fuel both devices per overlap cycle.
Let's do the math: a 9x9x9-meter overlapping system contains 729 reactors. With four reactors diverted to fuel the system, that leaves 725 for output. Wait—scratch that. It's actually 717 reactors since I need a nanoswarm deployer inside, which is a 3x2x2-meter unit, to maintain the replication process.
Considering nanoswarms exponentially increase building speed with more deployers, the energy output stabilizes around 700~ reactors per cycle. That's effectively infinite energy for now—at least until I figure out a failsafe for something as extreme as a blackhole reactor.
actually wait how much reactors do actually come out as nanoswarms transform energy to matter.. by itself already I just need to transform said nanoswarms which mostly carbon based to other matter.. so cut off 100 reactors for full energy to matter conversion.. huh so 610~ reactors as output still good enough.
Hold on. How efficient is the energy-to-matter conversion through the nanoswarms? Since the nanoswarms themselves are mostly carbon-based, I can transform their matter into other elements. Let's play it safe and allocate 100 reactors solely for energy-to-matter conversion. That leaves me with about 610 reactors of usable output. Still plenty.
To finalize the design, I placed one L-shaped control box in one corner of the frame and flipped another upside-down in the opposite corner. This setup gave me four energy outputs. I set the Iron Curtain boundaries along the reactor frame and configured the chrono bubble to start overlapping once construction was complete.
For safety, I added a setting to forcefully stop the bubble from continuing overlaps if it reached critical levels. Even if the system failed catastrophically, I trusted the Iron Curtain to contain the explosion. Sure, I'd lose energy, but an uncontrolled detonation that exceeded the power of a star exploding in one place? That's a planet-killer for sure.
With everything double-checked, I clicked the Create button.
[Abyssal Chrono Nuclear Reactors]
Cost: ($3,000 + (800 x 729 (Reactors))) x 10 (Wargirl)
Power: +2000 x 713 per replication
Hitpoints: 5000 + fixed 20000/s (Iron Curtain)
Prerequisite: MCV
Purpose: Power Production
Armor Class: [Chrono] Heavy Structure
Weapons: Nanoswarm deployers +1 per replication
Range: -
Additional Information: Constructs and repairs additional reactors. Estimated build time per overlap: 1 day. Build time decreases by half with each overlap.
"Oop," I muttered under my breath. "Okay... I think this is the first time I've created something I truly can't afford."
How much does this even cost? Six million? Yeah, around that. Way too expensive for a reactor. But then again, this is also capable of energy-to-matter conversion, so... maybe it balances out?
Still, I wondered how much cost was actually required for complete energy-to-matter conversion. Free resource generation would be a much better starting point.
I opened another template and copied the entire structure. Then, I removed 610 reactors from the design. This reduced the space needed for both overlapping and the Iron Curtain's protection.
The resulting structure was a 5x5x5 box—125 reactors in theory. But since the center space was allocated for a nanoswarm deployer, I adjusted the efficiency: 50% for resource generation and 50% for replication.
That left me with 113 reactors. I reassigned all 12 from the removed group to chrono control and Iron Curtain support, leaving one reactor as a temporary energy generator.
I hit Create again. If the cost scaled down similarly, this version should be far more affordable. This time, the goal wasn't power generation but resource production.
[Abyssal Chrono Matter Replication]
Cost: ($3,000 + (800 x 100 (Reactors))) x 10 (Wargirl)
Power: +10
Hitpoints: 5000 + fixed 20000/s (Iron curtain)
Prerequisite: MCV
Purpose: Resource Generation
Armor Class: [Chrono] Heavy Structure
Weapons: Nanoswarm deployers +1 each replication
Range: 4
Additional Information: Constructs and repairs additional units within overlapping space. Generates $500 per overlap every 10 seconds. Estimated build time per overlap: 8 hours. Build time decreases by half with each overlap.
"Slow… but worth it," I muttered. "If left alone long enough, it could produce millions every 10 seconds."
The price was now below a million—much more affordable. Starting out, something like this would've been a dream. The +10 energy, while minimal, was still useful for emergencies.
I looked up to see Amy and Helena engrossed in their work. Wait… were they designing something?
"Did we dig an underground base yet?" I wondered aloud as that my main method of getting million of resources. I spread my nanoswarms under the residential building. "Huh. Tunnel systems… but no base. Guess I'll need to dig deeper."
I built two standalone nanoswarm deployers at the bottom of the current elevator shafts. These would dig a kilometer down and create a 5x5 square-kilometer underground area for me. Why deployers, you ask? Last time I started a project like this, I fell asleep, and my nanoswarms stopped digging.
yawn
"Right on cue. The moment I think about sleep, I feel sleepy…" I murmured.
("Aqua-chan, can I fire my weapons at Moscow? I pretty sure Yuri is there and I will hunt him down for you") Artemis voice come through the comm.
"sure" I reply my brain already fry from making 2 blueprints involving time as I yawn again.
Amy heard that look at me and smile. "Go to sleep then Aqua-chan" she said as she slowly patting my head. Ugh, too comfy I thought as I close my eyes.