Friday, February 17, 2023

GrS 38:6:17: A Luke-warm greeting from dad


Well, colour me surprised, that did work. Vader tortured Luke's friends and next thing you know, he comes running... but oddly, from the direction of the Sluis sector. I mean, what was he doing out there?

But while we were waiting for Luke to arrive, Vader starts thinking about safe ways to transport force-capable people, and decides carbon-freezing might be the way to go. And of course, having some now-extraneous prisoners around, he decides he's going to test it on this Han Solo character. Surprisingly, he survived the process and word is Vader's going to give him to Boba Fett to collect some ransom or something. He's a wanted man!

So after that, apparently, Vader and Luke had a nice father-son chat, which ended when Vader cut off his kid's hand (you know, like you do), and then Luke flung himself into a gigantic air shaft when Vader offered him a spot at ruling the galaxy with him. Wow, over-dramatic at all, kid? Ever hear of a counter-offer? This family is not one for small, insignificant gestures, are they? Oh, you abandoned me before I was born and force-choked my mother? Well, I'll destroy your space station... Oh, you destroyed my space station, I'll cut your damn hand off! Oh, you cut my hand off and offered me a chance to rule the galaxy? (in that order, too!)... Well, I'll fling myself down this gigantic air shaft!

So Vader went away pretty annoyed with the whole thing... plus he had to give up his carbon-encased frozen Han Solo treat to Boba Fett. Not sure where Fett's going with him, but I'm sure wherever it is, he's laughing all the way to the bank. That Fett family have pocketed a lot of Republic and Imperial currency over the years.

Apparently Vader (and by extension all of us on the Executor) are heading out to take up residence on the new and improved Death Star II. This time, they're not even pretending to call it anything other than DEATH STAR. What a bunch of literalists.

Oh and get this--in spite of poor Bevel Lemelisk being executed for following Vader's instructions about that stupid thermal exhaust port, and essentially taking all the blame, clearly the Emperor knows it wasn't all Bevel's fault because he had him cloned to work on this new Death Star! But it hasn't all been sunshine and roses--Bevel has been executed and resurrected as a clone six more times during this construction. I sure hope he's sealed that thermal exhaust port this time.

[this marks the end of new material contemporaneous with The Empire Strikes Back... the next entry is the previously written Death Star II shield codes entry].

Thursday, February 16, 2023

GrS 38:6:10 Mutiny and a bounty

So, lots to update here. We went chasing off after that Millennium Falcon, in the Executor this time, Vader having shifted his command there now, along with the best from all divisions, which somehow mistakenly included me.

We were apparently so desperate to capture the Falcon that we followed them into an asteroid field... in the Executor. At first, I thought it was another stupid move from an Admiral with a death-wish, and that there was going to be another force-choking. But no, apparently it was on Vader's orders. Who flies a Super Star Destroyer into an asteroid field? Ah yes, asteroids... the icebergs of the sky. I suppose that's comets, but who's keeping track?

Fortunately, Vader eventually gave the order to retreat from the asteroid field... but not because it was unsafe, but because he had a call coming in from the Emperor. So we abandoned the chase of this super-important Falcon for cell reception?

So I don't know what the Emperor said, but Vader hired a bunch of bounty hunters to find this insignificant little freighter and among them, some bounty hunter named Boba Fett. Oh boy, do we have every member of that family on the payroll?

I don't know where he got them all from so quickly, but guess who had to process all these new access card requests in a rush for six new bounty hunters?

So just as I'm finishing that, and Vader has welcomed the bounty hunters aboard, Captain Needa aboard the Avenger reports that they've spotted the Falcon, so all these bounty hunters are not going to be needed, so I'm ordered to start decommissioning all their access badges.

And just as I'm finishing that, Captain Needa reports that they've lost the Falcon and he's coming over in a shuttle to personally apologize to Vader.

Okay, first of all, who does that? Secondly, why bother? If Vader wants to kill you, he can do it through the viewscreen... or is that only if he's on-board the same vessel? What's the range on that screen-based force choke? Does it only work on a closed circuit?

So after the obvious happened to Needa, because my office is near the main hangar, I got tasked with going to tell the poor shuttle pilot from the Avenger that his boss wouldn't be joining him for the return journey. I'm not sure who got put in charge aboard the Avenger.

Then we get all rigged for hyperspace because I guess Vader has given up on the Falcon? Seems out of character. But we make the jump and right as it ends, this Boba Fett character contacts Vader and says he's spotted the Falcon heading for Cloud City. I mean, did he wait until we'd made the jump to hyperspace? Is he just trying to irritate Vader? Hint: don't do that, even if you're a bounty hunter.

So next thing you know, we rush over to Cloud City, and Vader soon finds out that Luke is not on board. Now the plan, I hear, is to torture all the Falcon crewmembers... but not so that they can reveal where Luke is. Vader thinks Luke will "sense" this and come rushing to their rescue. Well, okay. He knows more about the Force than I do, but really? So now we're just twiddling our thumbs at Cloud City. At least I got some shore leave though. I just wish there was some shore around here.

Tuesday, January 31, 2023

GrS 38:6:7: Force projection

Wow, disaster is not the word.

First, Admiral Ozzel jumps the fleet way too close to Hoth itself, which meant they saw us immediately and threw up their planetary shield.

At the very least, Ozzel didn't have to live long with the consequences of his decision, because Vader force-choked Ozzel to death. Over a monitor link, no less! I didn't even know he could do that, that's terrifying. I better start screening my calls.

So because of this shield nonsense, instead of landing ground troops right at the base, we had to deploy the AT-AT units beyond the shield and then walk them to the shield generator.. and all this while coming under fire from those stupid T-47 speeders.

Oh, and guess what? The T-47 speeders had harpoons, because of course they did, and before you know it, they're circling our walkers, tying up their legs and knocking them over. Eventually, General Veers destroyed the shield generator and then we landed some troops directly, but in the meantime, a slew of Rebel transports escaped.

Why didn't we surround the planet and blockade it? Are we seriously not even as smart as the Trade Federation when they conquered Naboo?

The stated purpose of this attack was to destroy the Rebel base on Hoth, but I'm pretty sure the real reason was for Vader to capture this Luke kid. And we didn't succeed at that either.

Now Vader is intent on chasing this Millennium Falcon ship. He says it's the same one that infiltrated the Death Star, so he's convinced his kid is aboard. How? I don't know, the Force or something.

Sunday, January 29, 2023

GrS 38:6:4: Vipered out


Well, it seems I was wrong. Incom can indeed manage to destroy just about everything.

I spent ages looking through the limited accounting records that remain and found a few tantalizing references to orders of tow cable rope. I'm worried that these T-47 speeders may be equipped with harpoons and tow cables.

I suggested we deploy the Elite AT-AT units with the saw blades built into the legs, but apparently there's no budget... because guess what, we spent it all on Viper probe droids

This battle's going to be a disaster.

Saturday, January 28, 2023

GrS 38:6:3: Luke Snowcrawler


So apparently there's an energy shield protecting this Rebel base on Hoth, so Vader can't work his preferred tactic of bombarding it from space with the fleet.

Someone has decided that deploying AT-ATs onto the planet beyond the energy field, then walking them all the way to the shield generator makes the most sense. I know they're equipped with heavy lasers but they're still going to be sitting ducks.

At least someone listened to me for once, so we've been working like mad to strengthen the armor. Apparently the Rebels on Hoth have got a number of Incom T-47 airspeeders, modified for the cold climate. So this armor should protect the walkers against the blasters on that vehicle. But it will make the walkers even slower!

I better do some more research on these T-47 speeders just in case. Avoid any surprises. We have a bunch of data from Incom from the failed buyout, and I'm sure there's some prototype blueprints in there at least. They can't have managed to destroy everything.

Thursday, January 26, 2023

GrS 38:6:1: Hoth-tile environment

Word is going around that Vader has finally tracked down the location of Luke Skywalker, almost 3 years after the Death Star was destroyed. He, and the bulk of the Rebel forces, are camped out on the sixth planet of the Hoth system, a world comprised entirely of snow and ice.

What is with this Skywalker family and their fascination with single-biome planets? Is it because Vader was born on Tatooine (a total desert planet)? And then the big fight on Mustafar (a lava planet). And then he spent years on Coruscant (the "city" planet).

Or maybe it's just a Jedi thing. They only like single-biome places. Hah. Wouldn't it be funny if we could find all the remaining hidden Jedi (if any) by simply exploring all the single-biome planets in the galaxy? Let's see what's first in the database... huh, Dagobah. Swamp planet. Never heard of it. What's next? Endor's forest moon. Huh.

Now, to be fair, it's not just the Jedi. We Separatists are guilty of it too. Look at Geonosis--full desert.

Actually, it's everywhere. Look at Kashyyyk, the Wookiee planet. All trees. Or Kamino. All ocean.

That's odd actually. Almost all the major planets I've written about in this journal have been involved in major world events and they're almost ALL single biome, except maybe Naboo. That's odd. Do the mysterious forces that drive the galaxy just not like variety? It's almost like the creators of the universe couldn't be bothered to invent brilliant diverse planets and just opted for one-planet, one-biome. Hah. Laziness on the part of the creator. That's an amusing thought!

Saturday, January 21, 2023

GrS 38:1:5: The Search for Skywalker

Vader's got my whole department working on a new mission profile for a bunch of probes he wants to send out, all over various sections of the galaxy. He is still, if you can believe it, looking for Luke Skywalker.

All we have in stock to work with are these stupid Viper probe droids made by Arakyd Industries. It's got 5 manipulator arms, a blaster cannon, encrypted communications, and a whole host of sensors. It's great if you want to, you know, actually probe a planet for minerals or something but if you want to discreetly poke around and find out if the Rebel Luke Skywalker is hiding on said planet, you might as well paint it bright yellow and have it dance on top of a red ball organ singing "The Empire's looking for you, kid".

And Vader wants to deploy thousands of these things--he's already said he plans to exhaust our supply, so he's working to pull more in from every ship in the fleet, and he's got Arakyd working overtime to make more. And guess what, because we have to program them all ourselves, they're going through my budget. They cost 14,500 credits each! That's going to kill any chance of a bonus this year! I guess I can kiss goodbye to the idea of a visit back to Bothawui for Empire Day.

Thursday, January 19, 2023

GrS 38:1:1: Happy New Year

Well, happy new year! GrS 38 is here, or perhaps I should call it 3 ABY. Hmm, no, no I shouldn't.

Actually, according to this stupid battle droid I've got here that I installed this date translator into, 3 ABY won't actually start until GrS 38:3:8 because the Battle of Yavin occurred only on GrS 35:3:7. And it only took ten minutes to work that all out!

Oh nuts, it heard me say "work that all out" and now it's giving me the logic tables for how it arrived at its decision. Oh goodness I hate Baktoid Combat Automata.

[ Editor's note: we are now detouring into new territory. Previously, the journal, when I first wrote it years ago, jumped from GrS 36:3:1 to GrS 39:1:5, and the construction of Death Star II, skipping The Empire Strikes Back. So this is all new material, never before seen being created as we go, some 13 years later. I don't know how many entries I'll have covering this stuff, we'll see how it goes.]