Culpeper-Edge

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
Derelict Ship

The crew comes out of hyperspace slightly off course in the midst of an asteroid belt, but they find a derelict ship which they board and investigate. Some armed droids make things messy, but the crew manages to liberate some cash before returning to their freighter before an Imperial patrol pulled them in for questioning.

View
Virtual Planet

We had six players Monday night, one with a new character added to the crew. After the droid CH-1 piloted the ship through an asteroid field and landed on the planet XT-17, the princess passenger was unloaded and delivery fee paid out. The newest crewmember of the ship, Allanon, brawled with the current captain, severely wounding Sin and sending her to the med bay under Doc Grabow’s supervision. Turns out the planet created an environment which matched any person’s thoughts, so Matwe went bat hunting in a local cave, Jovel the Bothan looked for things to steal, and the droid purchased some new technical upgrades. We all had a good time with a freeform sort of session.

View
Plants in Space

Heading toward a rebel space station, the crew came out of hyperdrive a bit short and ran into a rogue ship which was blasted to pieces and boarded—the crew liberated a few psychic plants, an eccentric botonist, and a pair of confused Trandoshans. Then, approaching the space station, they encountered an Imperial Star Destroyer which, after a battle was joined between the rebel faction on the space station and the Imperials, they seriously considered joining. But better sense prevailed, and they turned and headed back to the Wheel. Coming up short again on that hyperdrive jump, they discovered a strange hyperspace communication pod, and after tinkering with it, realized it had been lost in space for some time and was destined for the Wheel. Our session ended with the Sentinal docking at the Wheel and the crew preparing to seek out the president of the company which had a claim of ownership to the communications pod.

Then we played a game of Star Wars themed The Resistance.

View
Back to the Wheel

The crew makes it back to the Wheel for more shore leave, and “M” delivers the hyperspace comm pod to the president of Isotech with Seraph accompanying. The crew has a job—use the coordinates provided in the comm pod to trace the last known location of the ship Sa Naloor, to a planet on the very fringe of known space.

The crew takes the job, gears up, but just as they are about to pick up the Isotech protocol droid which is supposed to join them, a group of Rodians tries to stop them, and clearly another crew is after the same thing they are—after almost being blown apart in the hanger bay by another ship, the Sentinal punches out and sets a quick jump away from the station.

Finally in a relatively safe part of space, the crew sets a conservative course for the planet, arriving 72 hours later….

View
Cholganna

The crew sent down an exploration party to the main section of the hull of the wrecked ship SaNalaor in a narrow, overgrown river canyon on Cholganna. Some nexu attack and are driven off, mostly by Seraph’s grenades, and the crew returns to the ship to wait until the next dawn. But the ship of Rodians arrives in the system and ship fire is exchanged—the gunners manage to take out the engines and send it into a spin and the ship from the rival crew plummets planetward….

View
Reality Split at Cholganna
Alternate reality 1, Mike GM's a new party

So we have a good problem with Edge at Culpeper C&G on Monday nights. We have too many people coming and we are prepared to allow for more players. We have split the group into 2 separate, “alternate realities.” As we try to complete the same adventure with 2 separate parties GM’d by 2 different people, we have split the group and changed reality. In my reality the crew was preparing for their decent when three ships came out of hyperspace to attack the entire crew. We all came awake to TD preparing the ship for attack. The Yiyar clan sent more ships to find out what is going on and why their first ship has not reported back to them.
We were out-numbered and out-flanked, but one thing evened the odds quickly…M. He hacked the largest ship and opened all the doors and hatches. That ship was disabled and falling to the planet. The other 2 ships was still enough to shoot the Sentinel out of the sky. Not before Seraph tried to jump to the largest ship only to be struck by one of the other ships. He watched as the last Yiyar ship struck the cockpit and the Sentinel fell out of the sky. M was not done trying to save the ship. He fixed the engines and tried to get the autopilot to land the ship. However, despite his efforts, the ship crashed. Most of the crew was lost. M could not find Mia, Brace and Oke was dead. Kasteal’s last meal was a control panel. TD, the droid was able to be repaired with a limp arm, and Allanon is badly hurt with no Doctor to take care of his traumatic wounds. Seraph quickly dispatched the crew of the lone surviving ship. We now have a way off the planet, most of the crew is dead. Seraph must assume command of the desolated crew remaining. Lets not forget that IT-3PO was left on the ship when it exploded. Will Allanon survive to lead the crew, will they complete their mission. Who is left in the prison cell on the enemy’s ship? Many questions and more to be answered Monday, Feb. 24. Come join us or come watch.

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.