ToH Age of Rebellion

Sixth Session
Humor and skulduggery

Last game, we were ordered to find out who was responsible for the droid attack.

There was a modified restraining bolt from TTC on all of the affected droids, which seems like our best lead.

Teagan is in the Quimar Sector, and has a huge business in protocol droids. Teagan Tech Consortium just released its new model, a soft-shelled protocol droid marketed as a human-like android. The main race are the “short and mysterious Devon”, and their hearing mechanism is completely different from most species.

We navigate there uneventfully, and the spaceport seems disproportionately large for the planet – perhaps an attempt to bring in large cargo ships. Also, only natives and a LOT of droids around. A loooooot. 

We get to TTC, and a very helpful salesperson is… very puzzled by our request. He is able to verify that the “restraining” bolt we have is one of their products, but had been modified post-manufacture by its customer. A minor bribe, and we get the name of the buyer – Kwymar Automation LTD, here on Teagan. 

Kwymar is carefully groomed to appear deserted, but there are subtle clues that the place is active. Tuka and the sneaky sorts get inside, and see on the security system that the captain that sold us the droids had picked them up from Kwymar.

We infiltrate the warehouse, noisily, and sneak into attack position. A protocol droid orders us to come out with our hands up, and we settle for coming up with weapons drawn. We start shooting -blindly. And NOBODY manages to nail their perception check. “Holy shit, they have a rancor!” “That’s not a rancor, it’s a Sarlacc!” “You’re both wrong – it’s A FUCKING AT-AT!” We can’t see shit, but we still shoot well – and obliterate 4 protocol droids. The last remaining one has a full C-3PO hissy fit and freaks out running towards a very shiny shuttlecraft.

A zany chase ensues, with the droid running for the shuttle, Cado running after the droid, and Rys running after them both… meeting a squad of 5 Stormtroopers who were coming down the ramp to aid the droids.

There’s a heated shootout, and things get REALLY hairy when reinforcements come in – although the tide turns again when the first mate flees with the shuttle, the goods, and his pride. But we do capture the captain of the crew that sold us the droids. Except she’s not really a pirate, she’s an Imperial lieutenant in Intelligence – Hura Kogler, daughter of legendary Imperial Intelligence officer Hyndis Kogler. Her father will kill us if he catches us, so we take her with us!

We get a lot of useful data, and Alliance High Command rewards us with congratulations and commendations. And no money! No, we get money. 750 credits, most of us get +10 Duty, and +15XP.

View
Fifth Session
Cleanup in the Hangar Bay

We come in on the squad landing an escape pod in the aft hangar bay, crushing a number of the renegade droids in the process. The black hole looms close – we need to move fast. 

3 of the 5 droid shipping containers are here, lots of droids milling about. 

We try to send out a couple grenades, then burst out.

We manage to get Yan and Dir Lop into the Y-wing. Yan fires the Y-wing’s forward-mounted cannon, taking out the tactical droid, and adding a bunch of structural holes to the shuttle it was sanding near. The rest of the droids go down quickly, although the Captain is concussed, and the engineering techs are liberated

The team heads to the Engine Room. We find more protocol droids holding the techs there hostage, and quickly take them down.

The engine room techs start trying to get the ship turned around and AWAY FROM THE BLACK HOLE

The ship takes a short hyperspace jump, and then pauses a while to recombobulate. The Captain summons us to her bedside in Med-Bay, and orders us to find out what happened.

Yan and (Kari) investigate the droid parts, and find out they had a modified behavior governor chip, similar to older networked combat droid models – possibly why they were so responsive to the tactical droid. They had a manufacturing facility on the planet Teagan.  Yan and (Kari) also manage to cobble together parts into a fully functional, factory-stock astromech droid, R2J6, aka Jade.

View
Fourth Session
When Droids Attack!

We meet with General Kraken via holo-communicator back on the Shadow Raptor. We’re thanked for our job(“You don’t know how badly we needed those droids.” We’re to be sent back to Arda 1, when the ship scrambles and its hyperdrive engages.

When the engines silence, the protocol droid in the room attacks us. We dog pile it, and then its head gets slagged. It was one of the droids that WE brought… And we’re locked in.

Before Yan can call to the bridge, it calls us, and a Lt. Hastings tells us that things are OK-ish… No, they’re not. We’re in a slow but uncontrolled descent towards a black hole, and life support + the engines are currently disabled. We also hear the ship become seized by the rest of the droids, in the game of the Galactic Empire…

The Captain calls us, and tells us the ship CANNOT enter Imperial hands. Yan rolls very well on engineering, and at least makes a good guess on how to repair Life Support, as a primary objective. Others – re-enable engines, disable Comms array, evacuate vessel, or if need be scuttle. 

Sneakily we sneak to the turbolifts, which don’t work, then down the ladders to Life Support. Dirlop deactivates the droids we find there, and we free the LS engineers. Reese patches them up, and the rest of the team works on getting the life support back online. We do it, although it’s not a great job, then begin the long climb up to Comms. 

In Secondary Comms, we disable one and blow up another droid. The general alarm/abandon ship notification is triggered, the comms folks are told to evacuate, and… we see a Y-wing shooting at the escape capsules. Tuka and Yan hack an R2 unit to talk the Y-wings into returning to hangar.

The crew get really fired up, and Leeroy Jenkins Primary Comms. They mostly die, but take out a few droids in the process. We are able to eliminate the rest of the droids, and get our distress signal out. The techs are EXTREMELY reluctant to destroy the Comms Array, but they are willing to arm up and barricade themselves inside. 

We see a droid take an escape pod to the aft section, where the engines are, and this gives us an idea. Yan pilots the pod, landing it on some unloader droids, but also noticed that the black hole outside is getting UNCOMFORTABLY CLOSE.

View
Third Game
Wretched hives, droid thieves, and us.

We all suit up and meet with General Niall.

Yan Tovis checks in with Rebel Intelligence and gives them solid info on the best pieces of the Death Star to go looking for, and where they might have ended up. Sie’lar is the intelligence guy I spoke to.

The others hang out in the Canteen, gambling and telling stories, and making connections with other Rebels.

In the morning, Major Yalor(who greeted us when we arrived) comes to find us, and lets us know that our ship is going to take a while to fix – that damage was significant. A couple days later, we’re summoned. We are to go meet with the Shadow Raptor, which is likely a ship.

The Spinster’s Loom, a shuttle, will be picking us up shortly.

We eventually rendezvous with the Shadow Raptor, which is the Alliance’s intelligence frigate for this sector. When we board, we’re greeted by Tay Coomsay, a Bosph.

Captain Hylo Sortuli welcomes us aboard. She’s a Mirialan. There’s a transmission waiting for us, so we retire to a conference room. General Airen Cracken greets us, telling us we’re being dispatched to acquire a large lot of Imperial droids from the privateer crew that… liberated them from an Imperial depot. Our budget is $4m credits. Shyndi Oglerk, Captain of the Contispex Crusader, is our contact. She’s a young human who recently took to piracy. She does have an Alliance letter of marque, so should be fairly trustworthy.

The intelligence came from Hammer Station, although it should not be linked to the Rebel Alliance yet. 

We end up at a place called Port Tooga, which is controlled by Shoola Hutt. Eventually, inevitably, we end up at a cantina called the Barvy Harpy.

Tuka defuses a concentration with an angry, drunk Woke, who then goes after OTHER people, setting off a big bar brawl. We meet Shyndi, and her first mate, Cog. 

There are negotiations, and Shyndi has a visible, angry reaction to the news that the Death Star has been destroyed.

The deal is completed(we saved the rebellion $300k!), we take ownership of the bots, slave the tug to the Spinster’s Loom, and take off for the Shadow Raptor.

+15 XP for everyone!

View
Second Session
Lasers.... In.... Spaaaaaaaaaace!

We are in the Jade Dragon, our YT-1300, escorting the Bright Hope away from Yavin-4, when a small wing of TIE fighters from a Ganzati-class carrier fly in.

Piloting goes well, and two TIE fighters experience rapid unscheduled disassembly events. 

We attempt to go to hyperspace, to find that last game, when Yan(Dave) checked the hyperdrive… she missed something. Hyperdrive no work!

More TIE fighters join the great debris field in the sky, and after some SERIOUS hijinks, we get the backup drive into gear.

Yan ends up repairing the hyperdrive, and 3 hull damage.

XP awarded! +10 for everyone.

Bennet, Jim, and Kari get +2 Duty Points.

We make it to Arda I base, check in with our contacts, and get assigned to quarters.

View
First Session
View
Welcome to your campaign!
A blog for your campaign

Wondering how to get started? Here are a few tips:

1. Invite your players

Invite them with either their email address or their Obsidian Portal username.

2. Edit your home page

Make a few changes to the home page and give people an idea of what your campaign is about. That will let people know you’re serious and not just playing with the system.

3. Choose a theme

If you want to set a specific mood for your campaign, we have several backgrounds to choose from. Accentuate it by creating a top banner image.

4. Create some NPCs

Characters form the core of every campaign, so take a few minutes to list out the major NPCs in your campaign.

A quick tip: The “+” icon in the top right of every section is how to add a new item, whether it’s a new character or adventure log post, or anything else.

5. Write your first Adventure Log post

The adventure log is where you list the sessions and adventures your party has been on, but for now, we suggest doing a very light “story so far” post. Just give a brief overview of what the party has done up to this point. After each future session, create a new post detailing that night’s adventures.

One final tip: Don’t stress about making your Obsidian Portal campaign look perfect. Instead, just make it work for you and your group. If everyone is having fun, then you’re using Obsidian Portal exactly as it was designed, even if your adventure log isn’t always up to date or your characters don’t all have portrait pictures.

That’s it! The rest is up to your and your players.

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.