Chapters (53)
- Cover
- Light of the Jedi
- Part One
- Chapter One
- Chapter Two
- Chapter Three
- Chapter Four
- Chapter Five
- Chapter Six
- Chapter Seven
- Chapter Eight
- Chapter Nine
- Chapter Ten
- Chapter Eleven
- Chapter Twelve
- Chapter Thirteen
- Chapter Fourteen
- Chapter Fifteen
- Chapter Sixteen
- Chapter Seventeen
- Chapter Eighteen
- Interlude
- Part Two
- Chapter Nineteen
- Chapter Twenty
- Chapter Twenty-one
- Chapter Twenty-two
- Chapter Twenty-three
- Chapter Twenty-four
- Chapter Twenty-five
- Chapter Twenty-six
- Chapter Twenty-seven
- Chapter Twenty-eight
- Chapter Twenty-nine
- Chapter Thirty
- Chapter Thirty-one
- Chapter Thirty-two
- Chapter Thirty-three
- Chapter Thirty-four
- Chapter Thirty-five
- Interlude
- Part Three
- Chapter Thirty-six
- Chapter Thirty-seven
- Chapter Thirty-eight
- Chapter Thirty-nine
- Chapter Forty
- Chapter Forty-one
- Chapter Forty-two
- Chapter Forty-three
- Chapter Forty-four
- Epilogue
- Acknowledgments
“Hetzal Prime happened to have a genius systems analyst in their Technology Ministry. He’s trying to build a network of navidroids…linking their processors together to use the data we have so far about the original disaster and all the Emergences. It’s not a sure thing. The problem seems to be getting enough droids to run the calculations.”
Marlowe and Vellis exchanged a quick glance—information passed between them, some unseen communication even Avar couldn’t detect.
“We can probably help with that,” Vellis said. “We have a proprietary set of algorithms we use to model likely hyperspace routes. If your analyst on Hetzal is interested, we can send a few of our navulators—hyperlane specialists—to help him refine his system.”
“Generally, we like to keep our trade secrets confidential,” Marlowe added, “but there are lives on the line.”
“Thank you very much,” Avar said. “That’s generous. We’ll put you in touch with the analyst—his name is Keven Tarr. I’m sure he’ll take any help he can get.”
“That’s not really why we’re here, though,” Elzar said.
“Oh?” Marlowe said, raising a thin eyebrow.
“It’s not just about stopping the Emergences. We want to make sure nothing like the Legacy Run ever happens again, and in order to do that, we need to know what caused it. Your family knows more about hyperspace than anyone, or so Senator Noor tells us. Do you have any theories?”
“Well, we’ve read the HoloNet reports, but they’re a little light on details. Do you have any additional information?”
Elzar reached into his tunic and produced a datachip, which he handed to Vellis.
“That’s everything we have so far. The Republic Transport Bureau’s personnel have analyzed the wreckage, and based on the wear patterns, it looks very much like the Legacy Run disintegrated in transit.”
“A collision?” Marlowe said.
“No,” Avar said. “It seems that the ship attempted to execute a maneuver that stressed its superstructure beyond its capabilities. I’m oversimplifying, but it seems to have ripped itself apart.”
Vellis and Marlowe were silent for a moment. Vellis set his glass down. Avar didn’t think he’d even tasted his drink.
“I’m sure you both know this, but the nature of hyperspace means that there is never any reason to maneuver at all. It’s empty. There’s nothing to hit. Routes are precisely calculated to ensure collisions like this are impossible.”
“We know that,” Elzar said. “Everyone knows that. But…something happened out there, and people continue to die and suffer across the Outer Rim. Pretending it’s impossible just wastes time.”
He pointed at the datachip Vellis was still holding.