Developer Blogs


RE: Kuat Drive Yards

FROM: The Shroud
TO: Shroud SF-5
RE: Kuat Drive Yards

These select journal entries were logged by Shroud SF-4 in advance of the mounting situation concerning Kuat Drive Yards. I present them to you now in an effort to educate and inform.


21.7 // Kuat City //
Observation of embedded Imperial asset K-33 continues. Recent marriage into the Kuat family further integrates K-33 into the planet’s political power structure. Appointment to Kuat Drive Yards oversight panel imminent.

Analysis: K-33 seeks influence over KDY, but not direct power. K-33 will attain the ability to funnel further Imperial assets into KDY for sabotage or seizure. Effect on Shroud interests: negligible.

24.3 // Kuat City //
Imperial asset K-33 now shuttles regularly to KDY, often gone for several days at a time. Relationship with family strained as a result. Spouse has confided deep concerns regarding K-33’s ambitions to close relatives.

Analysis: K-33 has raised suspicion and created doubt. No longer viable as a recruitable Shroud asset, but further observation warranted as KDY remains one of the Galactic Republic’s most important partners.

24.8 // Kuat Drive Yards //
Relocated to KDY as K-33 has taken up permanent residence in KDY Governor Quarters. K-33 insistent on heading KDY security oversight. Leveraging Kuat family ties with great regularity.

Analysis: Unsure if K-33 still on mission or thirsty for power. Too eager either way. Not a very good agent, but could prove useful as a unwitting collaborator. Will find out soon.

25.1 // Kuat Drive Yards //
Initial contact made under guise of shipyard administrator concerned with lax security. Appealed to K-33’s ego. Promises to walk me through all security measures as an act of reassurance.

Analysis: Access to KDY security network should provide ample opportunity for compromise. Liberation of newly manufactured capital ships for our network likely to follow.

25.2 // Kuat Drive Yards //
Transmission between K-33 and Sith Empire successfully intercepted for the first time. Point of contact: Adm. Ranken, Forward Command. K-33 suggests a single defensive station is key to subverting all KDY security protocols.

Analysis: Imperial (covert?) attack on KDY imminent. Imperial asset underestimated. Meeting tomorrow to go over security. Will ramp up plans to liberate craft in advance of Forward Command’s arrival.

25.3 // Kuat Defensive Station //
K-33 found me out. Says I was too eager to get on station. Took a Vibroknife to the back. Will encrypt and transmit logs in hopes you receive this. Data on Imperial intentions should still prove useful.

Analysis: Won’t be much longer now. Sorry for failing you.


I’ve since splintered and sold the information provided by SF-4 through numerous intermediaries for the SIS to obtain--at a steep price--and piece back together. The Republic is now formulating a plan to counter the Empire’s actions, deploying fleets and squadrons of fighters to strategic locales. This should keep both sides sufficiently occupied and less concerned with the affairs of those such as myself and my organization.

But let me be clear: our good fortune is in spite of Shroud SF-4’s actions; NOT because of them. If I have sent you out for observation, you are to OBSERVE. Nothing more.

Assuming I have your full understanding, I am sending you to the Kuat Defensive Station where Shroud SF-4 perished. You are to find and dispose of his body and belongings, and then survey all movements on the station. I suspect it won’t be long before KDY is awash with Imperial and Republic forces at one another’s throats, and it would serve me well to know who comes out on top.

That is all.