Operation Womp Rat

It's Just like shootin' womp rats.

Make some noise!

Rebel Command assigned the team a brutally simple task. Cause a diversion, so as to allow another team to investigate a facility under the control of General Weiss.

“If they send any calls for help – good! If they don’t, then you aren’t making enough noise,” the teams commander informed the squad.

Having cleared the facility and barricaded the doors, the team prepared to hold out long enough for the other mission to succeed.

The first wave of Imperials crashed against the barricades and fell easily enough. Even the E-Web Engineer failed to inflict much damage. “No problem,” Fenn said with a grin. “We got this.”

Then an explosion rocked the bunker. Stormtroops poured out of the woods, and an E-Web gunner burst through one of the blocked doors and started laying down fire. The Imperials quickly began securing rooms, as the team desperately tried to hold on for just a few more minutes.

The team’s commander comlinks that the other team is on the way out. The squad figures if they can just hold out a bit longer, any extra diversion would make their escape easier. But then, in disbelief, Mak watches as the terrifying figure of Darth Vader, himself, strides in through the carnage.

Imperial forces charge into the compound, and the team is unable to hold them back any longer. But they are hopeful the time they bought the other strike team will be enough, and disengage, carrying out their wounded.

After being extracted, the team learns from their commander that the other team’s raid was successful. Weiss is developing a weapon that makes Rebel High Command very nervous. She’s sure your team will be called upon soon to find out more…

Contacting an informant of ill repute

A distress call was received by Rebel High Command. An informant of ill repute, Weyn Jarl, swears he has acquired sensitive information regarding Imperial troop movements.

Jarl has proven untrustworthy in the past, but his information could be useful, could even be worth the risk that trusting him represents…

The team departed for Tatooine with all due haste. Mak recovered en route. As they approached, they picked up a desperate transmission from Jarl.

“Uh. can you guys hurry up? I’m in some trouble here…” Jarl’s voice was weak. And that was hours ago. Unfortunately, by the time the team arrived, Imperial forces were crawling throughout the area, likely searching for the same information for which the Rebel strike force had come.

Repeated attempts to contact Jarl proved fruitless. The Rebels approached the meeting place, only to find it surrounded by Imperial forces. At least the doors were still locked, but the Imperial troopers were accompanied by some Trandoshan Hunters and a fierce Nexu.

As the Rebels engaged the Nexu and the Trandoshans, the Imperials set themselves to entering the building. The E-Web Engineer made quick work of the northernmost door, and the Imperials flooded inside.

The Nexu leapt over Gaarkhan and growled as he slashed at Mak. As the rest of the team engaged the raging cat-beast, Gaarkhan raced forward to smash the Stormtroopers. Unfortunately, the door now open, the E-Web Engineer slung his cannon around, and rained fire down upon the battling wookie. The combined fire of the Troopers and the tripod brought the wookie down.

The Rebels, though, dealt with the Nexu and Trandoshans, and were ready to move in as the Imperials attempted to move the probe droid data core to safety out of Rebel hands. Although a fierce firefight ensued, the arrival of a second Nexu, commanded by a veteran Imperial Officer, proved too much for the Rebels. Diala made a valiant last effort to secure the data core, but, in the end, the Imperials made their escape, and our heroes had to withdraw….

Introduction

Arriving at the outpost, the Rebels open fire upon the troops standing guard. The team suspects the Imperials knew they were coming and they were walking into a trap. But all the same, with the signal continuing to broadcast, there just wasn’t time for a more subtle approach.

As the Rebels blasted their way into the compound, they were met by fierce fire from an E-Web Engineer. Mak Eshka’rey rushed forward to draw the cannon’s fire, allowing his teammates time to close in and finish off the turret. Unfortunately, Mak collapsed under fire and was unable to continue.

The Imperials reinforced the shielding on the terminals, and the Rebels raced against the clock. Only one terminal remained, and as Gaarkhan closed in to silence the beacon, a lone Probe Droid appeared from the command room, momentarily increasing the terminal’s shields. The Wookie swung, but despite a resounding strike, the beacon did not fail.

Imperial soldiers poured out of the forest on all sides; the beacon had done its job, and the Rebels were forced to run, carrying Mak with them.

With so many of the Imperial survivors getting organized, Rebel ground troops would surely have their hands full in the coming days.

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.