Filial Ties

Session 3

Mnub Drk, the sulustan Dark Jedi, told the group that they were the apprentices of the dark-jedi named Mathias Sendodge, and that they worshipped the man in the ice-coffin. He also told them that the fifth and last apprentice of Sendodge was somewhere on H.O.M.S. and that the only way to find Sendodge was to find a man named Dagoo Hes.

Waldo discovered that Dagoo Hes was a technician who worked for the CIS before the Miners of H.O.M.S. kicked the Trade Federation out. They also discovered that Dagoo Hes worked for the Hutt named Batto Kent.

CC-331 infiltrated the Hutt’s organization, only to learn that Dagoo Hes and Sendodge left for Nar Shadaa very recently. The Hutt sold them Sendodge’s old ship.

Due to a misunderstanding, the bartender of the local bar and a well-respected droid maker, Ralph Pangal and Rikoo Tannis were arrasted, tortured, and segregated by the clone CC-331 and the Shariff Waldo.

Hokala Pa-kar, who was in charge of H.O.M.S. after her husband left to help defend Geonosis for the republic, allowed an insurection to take place and broke trade agreements with the now unwelcome Republic.

Hokala, unwilling to allow things to devolve into violence, welcomed diplomacy with the Jedi Padawan Adashi Sincala, but when during the talks it was revealed that it was her who orchestrated the death of the man in the ice coffin things turned violent.

View
Session 2

The group finds on Drakhur’s body a key-card which leads to a private room she’d been squating in while not guarding the A.I. and Droid brain. There, in her room, they found co-ordinates to an unknown location on the planet below.

The group also found evidence that she was planning on meeting another Dark-Force user, a man named Nekon, on H.O.M.S.. The group set a trap for Nekon before he learned of Drakhur’s death, and took him by surprise. Nekon was meeting a large group of miners who showed force-potential and were being considered to be trained by their master, the Fallen Jedi Knight, Mathias Sendodge.

Yet more evidence from Nekon’s dead body poited toward the co-ordinates of a location on the planet below. The group took a ship and checked out the location, where they were attacked by two more Force Users who were using a bizare form of lightsaber which had many of the same qualities of the Neonis gas. The party accidently killed on of the dark-jedi, but another, a sulluston named Mnub Drk survived. They also found a man encased in solid frozen Neonis, a substance too cold to touch, which the dark-jedi seemed to be worshipping.

View
Session 1

Adashi, CC-331, and Kable arrive at HOMS, where they meet the violent politician and out-of-shape soldier named Kali-Kar, who leaves a bad taste in the party’s mouth, and the Rodian Sheriff of HOMS named Waldo. Waldo and Kali-Kar request the group’s request in isolating and removing a rogue A.I. running amock in the station’s mainframe.

Adashi makes contact with the Republic to review her standing orders while Kable checks out the station’s computer network. CC-331 and Waldo go to the miner’s dock to get a sample of the gas called Neonis.

When the A.I. shuts off the elevator CC-331 and Waldo were riding in, and begins firing at them with the elevator’s defense system, it is Kable who over-rides and isolates the A.I. long enough to trace it back to an abandonded security station on H.O.M.S..

Adashi, Waldo, Kable, and CC-331 locate the A.I., who’s physical computer body is being housed in a damaged but operational Droid Brain being guarded by a dark-side Force Adept. They group captures the Droid Brain and the rogue A.I., but they accidently kill the Force-Adept Drakhur as she attempts to escape.

View
Welcome to your Adventure Log!
A blog for your campaign

Every campaign gets an Adventure Log, a blog for your adventures!

While the wiki is great for organizing your campaign world, it’s not the best way to chronicle your adventures. For that purpose, you need a blog!

The Adventure Log will allow you to chronologically order the happenings of your campaign. It serves as the record of what has passed. After each gaming session, come to the Adventure Log and write up what happened. In time, it will grow into a great story!

Best of all, each Adventure Log post is also a wiki page! You can link back and forth with your wiki, characters, and so forth as you wish.

One final tip: Before you jump in and try to write up the entire history for your campaign, take a deep breath. Rather than spending days writing and getting exhausted, I would suggest writing a quick “Story So Far” with only a summary. Then, get back to gaming! Grow your Adventure Log over time, rather than all at once.

View

I'm sorry, but we no longer support this web browser. Please upgrade your browser or install Chrome or Firefox to enjoy the full functionality of this site.