I realized about halfway through the month that my April State of the Frontier post should have been the two year retrospective as that was the end of the first two years of the blog. Can I just say I can’t believe I’ve been going that long. This has been my most fruitful and long lived blogging streak. And it looks like it will be going for a while to come.
Since I missed the yearly retrospective last month, I think I’m just going to skip it for this year and try to remember to do one next year. There really isn’t that much to say. This is post 145 for the blog. Since we were at 72 at the end of the first year, we nearly doubled the number of posts in the second year which means I’ve been posting apace. And it seems that the audience is growing as the number of visitors, sessions, and page views grew by 45-75% depending on the metric. So more people are visiting the site which is great to see.
The focus of the blog has almost completely shifted over the past year from my original intent but the pendulum is starting to swing back now that I’m running a game again. More on that below.
Looking Back
This month was the first in a while that I didn’t have a new miniature model to share. With all the COVID-19 changes, I just haven’t had the time to sit down and work on models. I’ve actually been busier than before the pandemic.
We had the usual Detailed Frontier Timeline post at the beginning of the month which was followed by a two part article looking at the economics and logistics of starliners, first from a ship and passengers numbers perspective and then at the economics of a single ship. This kicked off an “Economics of Spaceflight” series that I intend to revisit occasionally in the future.
Behind the scenes I started up a new on-line game, “Skills for Hire.” This will be an episodic game with a different cast of characters each session to allow anyone available to play on a given night the chance to participate. The PCs are mercenaries working for Galactic Task Force, Incorporated and are assigned out to various jobs that GTF contracts for.
Which brings us to the last few posts of the month. Given the start of the game, I decided to showcase my game prep as blog entries, although after the game sessions are complete. To that end, I launched a series of posts with the “Skills for Hire” tag that will be outlining everything I’m creating and using for the game. I began with an introduction to the game and the impact it will have on the blog, then two creatures: the young sathodragon and the Pale mountain lion, and finally a write-up of the adventure and how it played out.
This will start a new style of posting going forward where there will be lots of little posts spaced out among the regular Tuesday posts. I may not post up all the write-ups of all the sessions, but I’ll try to get at least one in a month. And I’ll try to post the small bits like creatures, items, and locations. We’ll see how it goes. The write-up of the scenario was, I believe, the longest post I’ve done yet and it took a while to get it all written up.
Also behind the scenes I got the VM running my mail server moved over from the old server to the new one. So everything is now running on the new server and I can shut the old one off. Next up is to begin upgrading and improving the sites. Probably starting with my mail server as it is using a different technology (VMWare intead of Docker) than all the other sites and requires a bit more manual intervention in the case of a crash.
That was my month. Let’s look at what’s coming up.
Looking Forward
I’m hosting the RPG Blog Carnival in June. So there will be a post launching the month’s topic, Organizations, tomorrow on the first of the month so that all those participating in the blog carnival can get their cue for the month. This will take the place of the regular Tuesday post, which would normally be the first post of the month. Instead it will come the following week on the 9th. I’ll be talking about the True Yazira secret society in that kick-off post. Keep an eye on that post to links to other blogs taking about organizations created for their games and worlds. Most of the blog carnival posters write for fantasy settings and games but I’m sure the material created can be adapted to a sci-fi setting if you desire.
I’ve been asked about the stats and design of the HSS History’s Hope, so maybe this month I’ll whip up a more detailed description of that ship and post an updated map of their travels. They recently attempted a long jump and got lost again.
Beyond that, I don’t really know what I’ll be posting about. I’ll probably do a second organization to go with the theme of the blog carnival, probably on Galactic Task Force, Incorporated to go along with my game. And there will probably be several small posts related to the game and a scenario write up.
I’m planning on making the game sessions available as an audio podcast, and possibly videos, I just haven’t gotten everything in place for that yet so those will probably launch this month as well.
There are five Tuesdays this month with the last Tuesday being the last day of the month. That would normally be another one of these posts but since I’m hosting the blog carnival, that final post will be the wrap-up post for the carnival. I’ll do the State of the Frontier post on the first of July.
The other major thing happening behind the scenes is that June also means the start of editing on the next issue of the Frontier Explorer. I think a few of my blog posts might make it into the issue as articles this time around as they have been suggested by my co-editors. We’ll see.
There is also another FrontierSpace module in the works as I’ve been contacted about editing it and it’s almost about time for me to start writing my science nuggets for the Space Kids RPG.
Your Thoughts
Do you have any ideas or suggestions on things you’d like to see in the blog? Anything I’ve mentioned, you don’t want to see? Let me know in the comments below.
For the first session of the game, I wanted to keep things fairly simple as we’re still getting a feel for the format, and how much can be done in a single session. So we started with a fairly basic scenario, a young girl has gone lost in the mountains near her home and the PCs are hired out to find her (hopefully alive) and bring her home.
Long time readers of the blog, and those that listened to the beginning of the “A New Can of Worms” actual play, will recognize some of the setting and characters. I’ll start with an outline of the adventure, and then talk about the players and how they handled things.
Lost in the Mountains
Background
Alyssa Tinnett, a young woman in the village of Rosegard, went out “adventuring” in the region around the village after school last day-day. She took her “adventuring pack”, which included a small tent and sleeping bag, rations, water, rope, an all-weather blanket, and a pocket tool. She also took her sword, a gift from the yazirian Talnor at the Streel mine compound, which he has been teaching her how to use. She’s done this in the past and typically returns before it gets dark and the next night-day cycle starts. This time she didn’t return.
It’s late fall on Pale and as a farming village, the citizens are quite busy bringing in the harvest. Her parents and grandparents went out searching for her but were hampered by the darkness of the Pale night. They put out a job request to several mercenary companies in Point True and the contract was picked up by Galactic Task Force (GTF). The PCs were assigned to the job.
What happened
Alyssa’s Campsite. Click for larger image.
Her adventure started out like all her other ones. In this case, after playing in the woods with some of her friends for a while, she went north from the village while her friends returned home. She intended to check out the artificial dome that the sathar agent at the Streel compound was using as a drop point and then continue further north to the small canyon in the mountains to the north. She got to the small camping site that some of the older kids had once set up in the canyon and got her tent set up. After that, she shouldered her pack and started further up the canyon.
A short time later, she heard the sounds of something behind her but nothing was immediately visible. A few minutes later, she got to the top of a small rise in the canyon and looking back saw a pair of large bird creatures, something akin to a giant (1m tall) chicken. She recognized them as Nuks from some that had been killed around the village several months ago. With her way back to the campsite cut off, she began hurrying up the canyon looking for a place she could hide out.
The entrance to the cave. The ramp is about a 45 degree slope. Click for larger image.
After a while, she came to a steep rock formation that she thought that the nuks wouldn’t be able to scramble up and climbed to the top of it where she found the entrance to a cave. Exploring a bit into the cave, the slope on the inside was even steeper and extended nearly 100 meters into the mountain. Turning back to the entrance, she saw the nuks at the base of the slope. One of them jumped up trying to get at her but slipped back down. She retreated further into the cave but after a half hour and the nuks not leaving, she got bored and decided to do a little spelunking.
Carefully descending the steep interior slope, the cave opened up into a wide long cavern with some side passages branching off to the left. Following one of these side passages, she discovered another large cavern, although not as big as the first. However, as she moved out into the center of that cavern she must have disturbed something as she passed the entrance because there was a large crash and several tons of boulders tumbled down nearly completely blocking the entrance. There was a small opening, but too small for her to fit through.
After searching around for an hour or more, she couldn’t find any way out of this room back the way she had come. There was a passage to her left, and another straight ahead. The first was on her level but the second was up a 20 meter cliff that angled back out over the ground beneath it that she couldn’t find a way up. Exhausted, she curled up in her all-weather blanket and went to sleep, planning to continue looking for a way out in the morning.
Adventure Outline
The adventure consists of several small steps and encounters that I outlined as follows:
Area around Point True. The locations to the NE of Rosegard are locations from the A New Can of Worms game. Click image for larger version.
This occurs in the GTF headquarters at Point True. The PCs are given the basic information from the Background section above and allowed to requisition any equipment (within reason) that they feel they will need. They are told that they will receive their regular daily pay rate (20 cr/day for my new players) and a 100cr bonus each if the girl is found.
If none of the PCs ask for it, their handler issues them an radiophone in addition to any other gear they request. Once they have their gear, they are flown by aircar to Rosegard. As each aircar can take 3 PCs, there may be more than one. It’s a 30 minute aircar ride but a 4-5 hour drive. The aircar drivers will remain with the aircars at the city center while the PCs are out exploring.
Meeting with the family
This part of the adventure mostly occurs in the city hall building of Rosegard. As they land they are met by the mayor, Genio Washy, Alyssa’s parents, Larroy & Camryn Tinnett, and Alyssa’s grandparents, Steven & Janie Hite.
During this discussion they PCs can learn any of the “What happened” information that the parents might know as well as anything about Alyssa from her background. They know she went north as she told some of her friends and they told the parents when Alyssa didn’t return. They can also learn about the connection Alyssa has with Talnor from the Streel compound.
Tracking Alyssa
This bit of the adventure occurs in the valley surrounding Rosegard as depicted in the map below. I drew the map with Inkarte which doesn’t really have sci-fi assets so it has a bit more of a fantasy feel but I whipped this up in about 30 minutes (mostly relearning the interface as I haven’t used it in years). I then added the annotations in GIMP.
This is the referee version of the map with all the relevant locations marked. Click the image for a full sized version. There is a player version with none of the annotations as well.
The sathar dome is the natural place to start and the villagers can give exact coordinates for its location. It’s about 10 km from the village. The PCs can either walk there (a couple of hours) or have the aircar(s) drop them off (a few minutes). The dome itself is a light-weight, fiberglass pole frame, with a cloth covering. It looks like it was once naturally camouflaged but the grasses and such on it have died and it now stands out against the terrain. It is very light-weight and is about 3 meters in diameter. It is staked down to prevent blowing away but lifting it up reveals that there is nothing under it.
The terrain north of the sathar dome. Click for larger image.
Alyssa’s tracks are easy to find and the PCs can start tracking her north. The terrain is very wild and untouched as only the villagers occasionally come up here. There are small game trails in places and Alyssa seems to be following them and making for the small creeks running through the valley. She’s not trying to hide her tracks so they are relatively easy to follow as the paths have pockets of sand where the tracks are very visible. The waterways are 1-2 meters wide and at most a few tens of centimeters deep. They flow north to south on the map (into the valley from the canyons and then down out the bottom of the map).
Some time after the PCs leave the sathar dome, but before the reach the creek, they will encounter a young sathodragon. As they come up over a rise, it will be on another rise about 150-200 meters away. The sathodragon will see them and rush to attack. If it drops below 50 STA, it will try to retreat and escape.
Shortly after they cross the creeks for the first time, Alyssa’s tracks will be joined by those of two nuks. This will continue until they find her campsite and the destroyed tent with lots of nuk tracks around. As they follow her tracks from the campsite, the nuk tracks will continue to follow her prints.
A bit further on, she seems to become aware of the nuks behind her and the tracks indicate that she’s moving faster and at one point, as the path goes right along the edge of the creek, they vanish. She jumped sideways into the water and then went 20-30 meters upstream in the water before emerging. The nuk tracks are confused at this point but they eventually found her tracks upstream and continued to follow her.
Sometime after the campsite but before the PCs reach the cave entrance, they have an encounter with a pair of Pale mountain lions. On is waiting in ambush near the path and the other is another 20-30 meters up the mountain waiting to pounce as well. If either is reduced to less than half stamina, they will both retreat and try to flee.
Fighting the nuks
Eventually the PCs will arrive at the entrance to the cave. The two nuks are milling around here still not having given up the pursuit even though it’s been nearly 20 hours. When they see the PCs they will immediately rush to attack and will continue attacking until killed.
Exploring the cave
With the nuks dispatched, the PCs are now free to enter the cave. It should be obvious from the lack of tracks leading away and the fact that the nuks were hanging around trying to get up the slope, that Alyssa went in.
I based the cavern roughly on Carlsbad Caverns in Carlsbad, New Mexico. I downloaded a map of the Carlsbad Caverns and then modified it slightly for use in the game. The original map can be found here. Below is the map I used for the game with the relevant locations marked. I took some liberties with the elevations but otherwise used the map as is. If you’ve never been to Carlsbad, you have a long steep decent into the main cave. It’s fairly open in real life, and I closed it up in the adventure, but the blue path is the switchback path you take to get down to the bottom as it is very steep going straight down.
The map of the cave system. Click for full sized image.
As the PCs are exploring, remember that the only light they have is what they brought with them. They are not going to have large vistas and in some cases may not be able to see the other end of the cave.
If they are calling out as they explore, Alyssa will respond when they are by the cave-in location. There is a small opening, about 15-20 cm in diameter that they can look through and see her once she comes over to it. They will not be able to move the rocks as several of them are quite large (read tons). They can move some but not make the opening any bigger. Given time and effort, a dralasite without any gear could squeeze through the opening to get to her but she still can’t get out.
Alyssa will explain to the PCs about what happened and tell them about what looks like an exit at the top of the cliff on the other side of the room she is in. She hasn’t explored the large room in the upper left of the map yet as she will have just woken up when the PCs arrive.
Eventually, the PCs will find a way to the cliff face and can get her out. It’s 15-20 meters down and an overhang above the room floor where Alyssa is located. They will need to figure out a way to get down to her and get her back up (hopefully they brought rope).
Returning home
With Alyssa safe, the PCs just need to get back to Rosegard with her. If they think of it, they can simply call for the aircar(s) to pick them up. If they think to do this, the aircars will arrive in about 15 minutes and there is enough room for one to land at a time and load them up.
If they decide to hike back, they will have an encounter with either a quickdeath (from the AD rules) or a pack of lesser quickdeath. It’s up to you based on the abilities and strengths of the party. Obviously, their main objective should be to protect Alyssa. The quickdeaths will retreat if severely wounded or if one of the pack is killed.
Once returned, the village and family will be quite thankful. Alyssa will get a serious scolding from her parents. If the PCs wish to stay for the evening, there will be an impromptu celebration party in their honor. Several of the Streel mine employees, including Talnor, will come down for this. Talnor will also give Alyssa a talking to which she will appear to take more seriously than the warning from her parents. While a bit shaken by her ordeal, the resiliency of youth will quickly kick in erasing the worst of teh adventure and her natural xenophilia will kick in. She will spend a good portion of the party trying to talk to any of the non-human PCs and find out more about them, where they are from, etc.
Rewards
The PCs will get the 20cr of their pay and the 100cr each for returning Alyssa. In addition, there is a 250cr bounty on each nuk that they can split between the group. If they managed to kill the young sathodragon, that is worth another 1000cr to split between the PCs. Finally, if they managed to kill any quickdeaths, those carry a bounty of 2000cr each.
Of course they need documented proof to claim the rewards. Photographs of the corpses (taken with their chronocoms) will suffice. If they don’t have any documentation, the villagers are willing to send someone up to the locations the PCs give them to get pictures for them. GTF will give them the money immediately even though it will take a few days for the Pale government to issue the reward, which will then just go straight to GTF.
Additionally, the PCs should receive 1-3 XP for the adventure depending on how well they did.
How It Played Out
When I ran this, we had three PCs: Dhuggo (dralasite), Arzdran Garvox (yazirian), and Joey Rufus (humma). They picked up some weapons and gear at GTF HQ and headed out.
After meeting with the parents, they also talked with Alyssa’s friends that had been in the woods with her. After stern words from Joey to Alyssa’s folks about their parenting techniques, the team head up to the dome where they picked up Alyssa’s trail and started off. None of the PCs actually had a tracking skill but two of them had Scout as a secondary skill area so they only had minor penalties since the trail was easy to follow.
The fight with the sathodragon went fairly quickly, Joey used his jumping ability to good effect to get behind it and keep it at a distance while Arzdran and Dhuggo fired on it with their lasers. Wounded, the sathodragon fled into the trees and escaped leaving a trail of blood. The sathodragon didn’t do too well only scoring a single hit on Joey. Joey applied first aid to himself (he’s the medic) and was nearly back to full STA. They marked the spot and continued on. The idea was that if Alyssa’s trail ended and looked like the sathodragon had gotten her, they would come back and track it to its lair to try to find her body.
Continuing to follow Alyssa’s trail they found the nuk tracks and the destroyed tent. Getting a bit worried, they hustled on. Luckily, Joey made a INT roll and noticed the closer mountain lion waiting in ambush for them. Again employing his jumping racial ability, he sprung over the lurking cat landing a few meters beyond it and unloading into it with his laser rifle. Then he notice the one further up the mountain beyond him. He was now between them with his teammates some 20 meters away. However, startled by his jump, and wounded by the laser fire from Joey and Arzdran, the mountain lions decided this was too much work and bounded off, leaving the PCs alone.
The fight with the nuks didn’t go as well. As the creatures rushed the PCs, Arzdran got a shot off wounding one. Joey jumped over them again to the base of the slope up to the cave entrance. The wounded one went after Dhuggo (wielding his nightstick) and the other one turned around to go after Joey. The PCs were doing well, severely injuring the one attacking Dhuggo, but then Dhuggo got a little cocky and started showing off (the player said he started pointing to the mountains, Babe Ruth style, before making his attack) and missed horribly (rolled a 97). The nuk on the other hand didn’t miss and took a bite out of his arm. They managed to finish off the nuks but Dhuggo took a total of 30 STA damage and Joey was wounded a bit more.
As Arzdran examined the cave entrance and kept watch, Joey did a bit of rough field surgery getting Dhuggo patched up and back on his feet.
They then entered the cave and decided to go left once they got to the cave floor. So they almost immediately found the cave-in. Having been calling for Alyssa, she responded to them and they were able to talk to her through the rockfall. She told them about the cliff on the other side of the room she was in. As Joey and Arzdran set off further into the cave complex to try to find a route to her, Dhuggo passed Alyssa all his gear through the small opening and started squeezing his way through.
After taking some twists and turns the others found their way to the top of the cliff where they could see Dhuggo sitting and talking to Alyssa down below. Using rope they brought with them (they had asked about climbing gear back at the GTF HQ and I had told them they shouldn’t need it so I retconed them having it since the reason they didn’t have it was my fault), they hauled Alyssa and Dhuggo up and made their way back to the cave entrance where they called the aircar to come pick them up. It was a little tight with five in a vehicle built for four but Dhuggo and Alyssa were both small and so they made it work.
Getting back to the village, they learned about the bounty on the sathar creatures and one of the villagers offered to go back to where the nuks were to get pictures as proof. They stuck around for the impromptu celebration and the after a while, with a few hours to kill before the day was over and they needed to head back, had the aircar drive fly them up to where they had the fight with the young sathodragon.
Tracking it back to it’s lair, they tossed in a couple of doze grenades which knocked it out completely. They tied it up and called back to HQ to ask if they wanted the thing alive. Receiving an affirmative, they were told that a flying transport truck would be there in an hour to collect it and to hang tight. In the mean time the doze gas wore off and the creature struggled to get free but they had done a good job with the knots (I believe someone rolled a 01) and in its weakened state it couldn’t escape. Joey injected it with a StayDose to try to knock it out which seemed to work. Securing it in the bed of the airtruck when it arrived, they followed the truck back for a while to make sure everything was good an then flew ahead to base to get back home.
All told it took us about 3 hours to play through this.
Thoughts
That’s the adventure and how it played out. I’m still working on getting the audio and video of the game session on-line. So at some point in the future, you’ll be able to listen (or watch) how it ran.
What I’d be interested in is what you think about the information presented for running the adventure. How was the format? Would it be helpful to me organized differently? If you were running this, is there information you would want that wasn’t there? Are there details missing? On the flip side, did I include too much in places? Is there anything too constraining?
Tell me what you think and how I could improve these write-ups in the comments below.
This is a young sathodragon, the creature that the sathar use to make cybodragons. This young specimen doesn’t have the cybernetic implants. These sathodragons stand around 1 meter at the shoulder and are 2-3 meters long.
These creatures are offspring of the cybodragons that were seeded on Pale during the sathar invasion. A female sathodragon will lay a clutch of 3-7 eggs (1d5+2) but the first one to hatch will eat the others so these creatures are typically found alone as they are fairly territorial without sathar influence.
As with all sathar bioconstructs on Pale, there is a bounty by the Pale government for the killing and/or capture of sathodragons. The bounty for a young cybodragon offspring is 1,000 cr.
Type:
Medium Omnivore
Number:
1
Move:
Fast (60 m/turn)
Stamina:
120
Attack:
70 claws / 55 bite
Damage
3d10 claws / 4d10 bite
Special Attack:
None
Special Defense:
None
Native World:
Unknown, found on Volturnus and Pale in the Frontier. Typically found in the mountains, plains, and forested area of a world.
Iguana image by Rjcastillo. Click image for original file
The Pale mountain lion is a large feline-like creature similar to mountain lions on Earth. Typically 1.4-1.8 meters in length, these creatures stand about 1 meter at the shoulder. Stealth hunters, they like to ambush their prey and can move quietly through their native terrain. They typically hunt either singly or in pairs.
Their claws are toxic to most creatures. A successful attack that does damage injects a venom that is S5/T10 in strength. Antitox will neutralize the poison with a successful Neutralize Toxins skill check. The venom effect lasts for the first four successful attacks of an encounter, after which the creature must wait several hours for the venom to build back up.
Type:
Medium Carnivore
Number:
1-2
Move:
Fast (70 m/turn)
IM/RS:
8/75
Stamina:
100
Attack:
70 claws / 60 bite
Damage:
2d10 claws / 1d10 bite
Special Attack:
venomous claws – S5/T10 poison if claw successfully attacks
Last Wednesday (May 20th) I ran the first session of a new on-line Star Frontiers game. I’ve been itching to run a game again and I finally pulled the trigger on getting it started. We’ll see how long it lasts.
Game Background
Game Logo
The PCs are employees of Galactic Task Force, Incorporated whose slogan is “Secretaries to Mercenaries, we’ve got a place for you!” They are effectively a mercenary group with a wide range of skills that you can hire out for any kind of job. You can see a more detailed description on the Skills for Hire game page on my wiki.
The plan is to make the games very episodic with each adventure taking only a single session. The goal is to allow anyone that can make a given session the opportunity to play. Each session starts a new mission and it can be run with whoever is available that night. I wanted to accommodate as many players as possible, even if they can’t make every week.
I’m also recording the sessions and I’ll be posting them on-line. The video will go up on YouTube and I’ll be posting the audio-only version as a podcast here on this site (and will list it on various podcast sites as well). The video will be completely unedited and the audio minimally so. More on that when they go live.
Games are Wednesday at 8pm MDT and we play on Roll20. If you think you might want to play and are able to join, feel free to jump over to the Roll20 game page and join. Create a character (instructions on the wiki page) and join us for the next session.
Impact on the Blog
As part of this, I’m also going to return to some of the roots of this blog and be posting the various resources I create for the game as part of my prep. These will be fairly rough and not fully polished but should provide some nuggets you can use from the resources as well as small adventures you could potentially drop into your game if you desired.
This will most likely result in a fundamental shift in my posting schedule and style. Namely, if things go as planned, I’ll be posting more often and the average post length will be smaller as I break up all the information across several posts. For example, I created two new creatures for the first session and those will get posted up as small individual posts to make finding them in the future easier. Similarly, I’ll be posting location maps (when I create new places) as individual posts. Once all the pieces are up, I’ll post up a description of the full adventure linking to all the parts.
All of the posts related to this game will have the “Skills for Hire” tag applied to them in addition to any others. Which should make the easier to find. I’ll also preface the session summaries/game outlines with “Skills for Hire” in the title.
So consider this the first of these small posts. I’ll get the creatures up over the weekend and do the full adventure post as the regular Tuesday post next week. I won’t necessarily get everything posted every week. I just don’t have that much free time. But I’ll try to get the more interesting things up.
I also still plan to do more of the typical posts like I’ve been doing for a while. The timeline posts won’t go away, and I might get back to modeling. The starliner posts has me looking at my custom starship system again so maybe there will be a post soon about that as well.
Going Forward
We’ll see how this goes and if I can keep up this new pace of posting. If there is interest, I might also consider live-streaming the games, either on YouTube or Twitch. I’ll just have to check that my computer is up to it. It didn’t have any issue recording the session locally on Wednesday but I’ll have to see how streaming works.
Let me know if you have any questions or suggestions for things going forward.
Last week we looked a bit at the logistics of running a passenger transport system between the various worlds and saw that if you wanted daily flights between all the worlds, you’d need over 600 ships. And that would only give you 250 people moving between each world each day.
Now you can change that a bit by making the ships a bit larger or increase the passenger density. But it gave us a feel of what assumptions or changes you need to make to your setting if you want a certain level of interaction between the worlds. Or if you limit the number of ships and passengers, some ideas of what impacts that has on the culture and setting.
In this article, I am going to look at the financial side of the passenger transport business. We’ll start by actually designing our starliner to get an idea of costs and expenses, look at ticket prices, and decided if it is even worth it. Then we can talk a bit about other changes that we need to make, if any, to make this all make sense. Let’s get started. You might want to settle in. This one is a bit long.
Our Ship
If we’re going to look at economics, we’re going to need details on the ship. In the last article, I based everything on a HS 10 starliner. We’ll detail that ship out and look at its cost.
Hull and Engines
As a HS 10 ship, it will have three engines, which from the discussion last week, are atomic. I realize now that as a passenger liner, maybe we don’t need the power of the atomic engines and can get by with ion engines. Surprisingly, in the discussion that the previous post generated, no one mentioned that. It would also save on the overhaul time as ion engines don’t need that so the ship could be turned around in port more quickly. But for now, we’ll stick with the atomic engines.
Cabins
The next major question is how many of the various passenger berths we have of each class. We have a total of 250 berths. Journey class are the standard. Interestingly, the only safety requirement listed in the rules is that a spacesuit has to be provided. You don’t actually have to have lifeboats for everyone. First class berths are more expensive and require more cabin space, cargo space, and facilities for the passengers. And do need access to a lifeboat. Storage class cabins are cheaper for the passenger and have minimal storage space, but are more expensive to install in the ship, costing as much as a First Class cabin. With the standard starship construction rules, these tradeoffs really don’t affect the design of the ship other than the final cost as the system doesn’t really account for the space and facilities needed. So for this analysis, I’m going to roughly base these ships on our modern airlines, with most of the cabins of the base Journey Class category with a few First Class and some Storage Class. The breakdown will be 40 First class, 180 Journey Class, and 30 Storage Class.
Crew
The other major decision is the size of the crew. We will need to purchase cabins and life support for them as well. The rules give no guidance on this. Looking at cruise ships, it is about a 1-to-5 ratio, crew to passengers. Some of that, such as janitorial and maintenance work, will get automated away to robots on our star liner, but then we’ll need people to look after the robots as well. We’ll design the ship around a crew of 50. We’ll talk about the breakdown later when we have to figure out what they are paid.
Ship Vehicles
While we only need lifeboats for the First Class passengers, we’re going to have lifeboats for all of the passengers (except Storage Class, that’s just one of the hazards of the cheap fare, you are frozen and can’t get to a lifeboat) and the crew. And we will toss in 10 escape pods so not everyone has to make it to a lifeboat. As the final vehicles, we’ll add in 5 large (10 being) launches for shuttling people around between the station and ship, 2 small (4 being) launches for the crew’s use, and 2 workpods for ship maintenance.
Spacesuits
We are required to have spacesuits for all of our non-Storage Class passengers. Plus we’ll have them for the crew as well. Technically, each species has its own style of spacesuits adapted to their physiology. The rules, however, only distinguish between vrusk and non-vrusk as they are only really concerned with cost and the standard spacesuit is 1000 cr. while the vrusk suit is 1,500 as they require more material. If we assume that vrusk make up one quarter of the crew and passengers, and we build in a bit of buffer in the numbers to account for varying numbers of the different species, we’ll get 80 vrusk spacesuits and 220 non-vrusk ones. This is 300 total, which is exactly our crew and passenger count but remember that the 30 Storage Class passengers won’t be using one so we actually have 30 extra.
Robots
There will be a number of robots on board to handle things like cleaning, maintenance, some food production, etc. We’ll design the ship to have 50 robots, basically doubling the crew size. These will be a mix of level 3 and 4 service and maintenance robots, will possibly a small number of security robots. Overall the average cost of each robot will be 4,000 cr.
Other items
There are a number of other items that go into building the starship such as radios, intercoms, computers, portholes, Velcro boots for crew and passengers, toolkits, etc. We’ll add those in as appropriate and list the details in the final stats when presented in the next section:
PGCSS Prenglar Glory
Here are the full KH stats for the ship along with its price tag, fully fueled.
HS: 10 HP: 50 ADF: 3 MR: 3 DCR: 50 Engines: 3 Class B Atomic, 6 fuel pellets each
Communications Equipment: Videocom radio w/ 4 extra panels, Intercom system: 5 master panels, 400 standard panels, Subspace Radio Sensors: 400 Portholes, radar, camera system, starship astrogation suite Weapons: None Defenses: Reflective Hull Life support capacity: 500 beings, 200 days with full backup Passenger Accommodations: 40 First Class cabins, 180 Journey Class Cabins, 30 Storage Class cabins Crew Accommodations: 50 Journey class cabins Vehicles: 10 escape pods, 14 lifeboats, 2 workpods, 5 large launches, 2 small launches Computer Level: 4 (175 FP) Computer Program: Drive 5 (64), Life Support 1 (4), Alarm 3 (4), Computer Lockout 4 (8), Damage Control 3 (8), Astrogation 4 (24), Cameras 1 (1), Robot Management 4 (16), Information Storage 3 (8), Communications 2 (6), Installation Security 3 (12), Computer Security 4 (16), Maintenance 2 (4) Backup life support computer: Level 1 (4), Programs: Life support 1 (4) Robots: 50 level 3-4 maintenance, security, and service robots Other equipment: 220 non-vrusk spacesuits, 80 vrusk spacesuits, 300 velcro boots sets, 5 Engineer’s toolboxes, 10 sets of Magnetic shoes Cost: 5,658,000 Cr.
The Ship’s Crew
Now that we know the design of the ship, we need to decide on crew makeup. This will determine the wages owed as we operate the ship in the space lanes. This is going to be an approximate mix. The exact details may vary ship to ship but will give us a starting point to figuring out the operating costs when we get to that stage. The crew makeup I settled on, allowing for round-the-clock operations is:
2 Pilots – level 5 – necessary to operate a HS 10 vessel
2 Astrogators – level 3 – It’s an established route so these could be even lower level
2 Engineers – level 4 – as discussed last week for effecting the engine overhauls
4 Technicians – level 4 – assistants to the engineers and helping with on-board maintenance
4 Roboticists – level 4 – maintain the ship’s robots
11 other staff – level 2 – any other duties, entertainment, etc.
Now some of those, such as security, food services, and other could slosh around a bit depending on exactly want you want on the ship and what roles all those robots play, but this mix give us a starting point.
The Economics
Okay, with the ship squared away, let’s look at the income and expenses of running this ship.
For this analysis, we will be looking at a single jump. This means that we’ll be covering the 14 days from departure from one station until the ship is ready to depart the other one. The Knight Hawks rules are based around yearly or 40-day “months”. So we’ll often be scaling the values from the rules to cover just the 14 day period.
Let’s dive in.
Income
There is really only one source of income on a starliner, paying passengers. The KH Campaign Book, page 44, covers the operations of a starliner. We’ll start with the Spaceliner Bookings Table.
This table tells you how many of your berths a ship will fill traveling between different population worlds. Now to be honest, I believe that this table really represents the situation if there were lots and lots of travel available. If there is only a single ship flying between the two worlds each day, it will probably fill every berth every trip. And depending on the route, it might be higher than that given by the table. For example, traveling from Prenglar (high population) to Dixon’s Star (outpost) gives only a low fill percentage but in truth, most of those people are actually going to Truane’s Star (medium population) and so the ship would be fuller. But I’m going to leave those details as an exercise for you to do for your version of the Frontier. I’m going to take the table at face value here.
This ship is flying between Gran Quivera (Prenglar) and Triad (Cassidine), which are both high population worlds. According to the table the ship will fill 80+2d10 percent of its berths on any give trip. We’ll just deal with the average which is 91%. That means on an average trip we will fill 36 of our 40 First Class cabins, 164 of our 180 Journey Class cabins, and 27 of the 30 Storage Class berths. Sometimes it will be more, sometimes it will be less but that’s the number we’re going to use.
The jump from Prenglar to Cassidine is 7 light years. That means that a First Class ticket costs 1400 cr. A Journey Class ticket costs 700 cr. And a Storage Class ticket costs 210 cr. Given the number of berths being filled, that means that our income for any single jump is 170,870 cr.
That’s our gross ticket sales. We need to fit all of our expenses for a trip into that number. So let’s look at our expenses.
Expenses
First up is fuel. We have three atomic engines and each jump uses a fuel pellet in each engine. Since each fuel pellet costs 10,000 cr., each jump costs us 30,000 cr. in fuel.
The next obvious cost is the crew salaries. Daily wages for characters with spacecraft skills are given on page 54 of the KH Campaign book. Daily wages for characters with AD skills are given on page 60 of the AD Expanded Rules book. For the “other crew” line I just uses 10 cr. x level as their pay rate and for the food services crew I use 10 cr. x level+1. I’ve also ignored the fact that characters may have multiple skills and the pay rate is just based on their primary skill level. With the crew as detailed earlier, the daily cost for the entire crew is 3,690 credits. Which means for the 14 days of our trip, the crew wages come to 51,660 cr.
After those two, the next largest cost is maintenance. The ship has to spend 15-16 days in maintenance each 400-day year at the cost of 1,000 cr. per day. In 400 days, a ship can make 400/14= 28 trips 8 days left over. That means that we can make 27 trips a year. So each trip needs to save away 16000/27 = 593 credits to cover that expense at the end of the year. To be safe, and cover other unexpected maintenance costs, we’ll stash away 1500 cr. each trip.
We’ll also need to pay the crew during those 16 days as well so we need to save away a total of 59040 credits to cover wages. That means each trip needs to save 59040/27 = 2187 credits which we’ll round up to 2200.
Each trip consumes life support. According to the rules, refilling the life support system on the ship costs 15000 credits every 200 days or 75 credits a day. Thus our 14 days of operation use up 1050 credits worth of life support.
Another expense is an office at each end of the line where passengers can come to buy tickets. The rules state that this costs 500 credits per 40 days at each station or 12.5 credits a day. With two end points that’s 25 credits a day or 350 credits of expenses for the 14-day period. We need to squirrel way a bit of funds to cover the 16 days in maintenance but it’s not that much and we can assume it’s covered by the extra maintenance money we saved.
Finally, there are docking fees. Here we are going to use the number given on page 32 of the module SFKH1: The Dramune Run, where it says that the standard rate for docking fees is 2000 credits a month. Assuming that is the 40 day “month” we’ve been using, that works out to 50 credits a day or 250 credits for the 5 days in port during each run.
Tallying that all up, we get that the operating expenses for the ship total 86,810 credits for each leg of our run between Gran Quivera and Triad.
That seems pretty good. We’ve got just over 170,000 credits in income and just under 87,000 in expenses. Which is all well and good if there aren’t any taxes, and if the ship is paid for.
Now the rules don’t explicitly give rates for taxes, tariffs, and other fees associated with interstellar travel although they do talk about varying the rates for wages, docking fees, ticket prices, etc. that can affect the income or expenses for our ship. And in the AD rules, when talking about PC and NPC character wages, it says to assume half of all their income goes towards living expenses and talks about raising/lowering taxes to adjust the amount of money the PCs have. And local governments and the UPF need to get income from somewhere. I’m going to leave the taxes issue up to you for your campaign. But a corporate tax of say 5-10 percent of gross sales might not be unreasonable.
Paying for the ship
But now we come to the biggest expense, at least during the early years of operating the spaceliner. How did we pay for that ship in the first place? Maybe this is a mega-corp and they had a huge budget and could just pay for it outright. They still need to recoup the cost of the ship but at least don’t need to take out a loan. If it’s a smaller organization, they may have to get a loan for the cost of the ship, either in part or in full. Let’s look at those two scenarios. And we’re going to ignore taxes. Subtracting our expenses from our income, that leaves us with 84060 credits after each trip.
First, the mega-corp, paid in full option. Assuming every one of those net credits earned goes into paying back the cost of the ship (which from above is 5,658,000 credits), it would take 68 trips to pay off the value of the ship. At 27 trips a year, that’s two and a half years to recoup the cost of the ship. If there are unexpected costs, it will take longer.
Let’s look at a smaller organization that has to take a loan. Pager 42 of the KH Campaign book gives the monthly payment on a 10,000 credit loan amortized over a number of years from 1 to 20. Now, the game was written in late 70’s to early 80’s and the interest rates back then were high, on the order of 10-15% for low risk ventures. So the interest rates for starship loans, which are considered high risk, are set at 4% every 40 days or, over the 400 day year, an APR of 48%! That may seem a bit high, even by late 70’s standards and especially today, but we’ll go with it as that is what is in the rules. If you want to do the math and come up with a different interest rate for your setting, go for it.
We’ll start by looking at a 10-year loan. Using the table on page 42 and the cost of the ship from above, and assuming we finance the whole thing. The cost of the loan is 230,903 credits every 40 days or 80,816 credits every trip. We had 84060 credits left so that’s good, the net difference is still in the black at 3,244 credits. But we have to account for that 16-day maintenance period where we still have to pay the loan but aren’t making any income. The loan cost for that 16 days is 92,362 credits. Spread over the 27 trips in the year that comes to 3421 credits that need to be saved. Which puts us in the red by 177 credits. Considering we had a bit of buffer in our maintenance budget, to the tune of about 850 credits, we can cover that small deficit from that.
So that means, if we have a 10-year loan for the entire value of the ship, we can just break even if the ship operates continuously and don’t have any problems for a decade. It can be done, but it will be tight. But if we run into unexpected problems, we’re going to be in trouble. We could look at a longer loan, but beyond 10 years, it doesn’t really help. Even a 20-year loan only puts us at 1454 credits in the black each year but takes twice as long to pay off and we end up paying twice as much for the ship.
That’s just to break even, there are no profits beyond the wages for the crew so hopefully the owner is part of the crew or they get no money for the first decade. And that is the economics for a run between two high population worlds were we basically fill the entire ship each trip. On a run with fewer berths sold, there would issues on the scenario where the ship was financed. Also, if there are any taxes, we would really be in trouble. It looks like any fraction of the ship that can be paid for up front will make the operation be more financially stable.
Some Variations
This article gives you a baseline for operating your starliner. I will leave most of the variations up to you but look at one. Some of those variations include, but are not limited to, changing ticket prices, changing the mix of berths, shortening the time in port so you make an extra run or three each year, selling more (or less) of the berths, different crew expenses, and using ion engines instead of atomic engines. I’m just going to briefly look at the variation where we fill the ship completely every trip. Which may very well be the case if there is only a single flight each day between worlds.
In this case, the only real change is that have 13 more paying customers across all three berth classes. That means that our income goes up to 188,300 credits an increase of 17,430 credits. Since our expenses don’t actually depend on the number of passengers (the life support costs probably would, but we ignored that), that is all extra profit. In this case, we are now 17,253 credits in the black after each trip, assuming we keep the 10-year loan.
And that means we either have some profit for the owners and can save a bit for other unexpected expenses, or we can shorten the loan term a little bit. We were right at the bleeding edge as far as the loan went and were already in the point of diminishing returns with respect to lengthening the loan. With a full ship every trip, we could shorten the loan period from 10 years to 5 years and still have a 5,400 credit surplus. And reduce that actual amount we pay for the ship (principal and interest) by 57%, a savings of 9,921,303 credits, which is enough to buy almost 2 more ships! The total cost of the 10-year loan was just over 23 million credits, four times the cost of the ship. That interest rate is very expensive.
Conclusions
So, running a passenger liner between two high population worlds is doable. It might be tight for a few years (up to a decade) if you can’t pay for at least part of the ship up front and have to finance it, but it can be done. Runs between smaller worlds might not be possible using the table from the rules to determine the number of berths filled.
This also gives you as a setting designer some ideas of knobs to turn to tune things in your setting or describe what PCs see as passengers on one of these ships.
What did I miss? What other variations might we look at? Have you ever had PCs try to run a passenger liner? What happened? Share your thoughts in the comments below.
My Starship Construction in the Frontier post generated a lot of discussion in the Star Frontiers group on Facebook. In some of the discussion, the commenters seemed to be making the assumption that I wanted to increase the number of ships flying around and that my post was advocating for ways to do that. I actually don’t have a strong feeling one way or another. In fact, I’m much more in the camp of small numbers of ships.
What I’m really looking at, and am interested in figuring out, are the implications those small numbers have and whether or not it makes sense to increase the numbers. Or if you don’t, what that implies for the realities of life in the Frontier and how that impacts the player characters.
I’m interested in questions like, if you only have a small number of ships across the Frontier, what does that mean for interstellar commerce? What impacts does that have on interstellar travel? Who owns the ships? What do they cost? And questions like that.
Since that starship construction article came out, and the ensuing discussion, I’ve been thinking more and more about this and have decided to do a series of articles on the topic. They will all have the Economics of Spaceflight title and a similar tag. In this first article, I’m going to look at interstellar passenger travel.
From the Rules
Let’s start by looking at what the rules say about these ships, which it calls starliners, and interstellar travel. We’ll begin with the description given on page 6 of the Knight Hawks Campaign Book:
Spaceliners. HULL SIZE = 6-15. Spaceliners (passenger transports) are built in a wide variety of sizes. Modern spaceliners are fast, quiet ships, capable of providing the wealthy passenger with any conceivable luxury. Many of the older liners are smaller, somewhat decrepit vessels that promise only the fundamental requirements of life support. The number of passengers carried by a spaceliner is about 25 times the ship’s hull size. For example, a spaceliner with a hull size of 10 can carry 250 passengers. Engine durability varies as much as size on spaceliners. Some will require an overhaul after three jumps, while others will be able to make 8 or 10 interstellar trips without maintenance.
KH Campaign Book, p. 6
This gives us a bit of information right off the bat. First, we have the range of hull sizes for these types of ships and the number of passengers per hull size. I’ll have more to say on that latter concept later. It also seems to imply that there are a bunch of these flying around as it describes various generations of ships. Other bits, such as the comments on engine overhauls, tell us that they typically sport atomic engines (as ion drives don’t need overhauls) and indicate some of the properties of the Class B and C atomic engines which the rules haven’t covered yet if you’re just reading through the book.
In the original Alpha Dawn Expanded Rules book, pages 49 and 50 talk about they modes and costs of interstellar travel. It lists three “classes” of travel accommodations and their costs:
First Class – luxurious accommodations with the best rooms, food, and and best access to survival gear in the case of an emergency. 200 Credits per light year traveled.
Journey Class – This is the standard accommodations. 100 Credits per light year traveled.
Storage Class – In this class, you travel as frozen cargo. 30 Credits per light year traveled.
More details on the accommodation types are given on page 21 of the Knight Hawks Campaign Book.
Travel time is one of the areas where the Alpha Dawn (AD) and Knight Hawks (KH) rule sets conflict with one another. The AD rules say that interstellar travel occurs at the rate of one day per light year, while the KH rules, require 10 hours (one day’s work) per light year to plot out the jump, but actually making the jump takes 8.7 days regardless of the distance. Reconciling and clearing that up is a whole article in and of itself. We’ll save that for a future date. For this article, we’re going to assume that it takes 9 days to make a jump, regardless of the distance.
Of course that probably means the cost of a ticket should be fixed as the same number of resources go into making a jump regardless of the distance but for now we’ll go with the AD rules ticket costs.
If the PCs come into possession of a starliner, either via salvage, original constructions, or some other means, the KH Campaign Book (p. 44) provides guidance on what it costs to operate such a ship, how much of the ship is full on any given trip, and the risks involved. We’ll come back to those numbers later as well.
How Many Passengers – revisited
For this article, we’re going to be looking at a HS 10 passenger liner which falls in the middle of the range specified in the KH rules. According to the rules, this ship can carry 250 passengers. The question is, does this make sense?
A modern cruise ship, roughly the size of a HS 10 starliner.
Let’s look at some sources. A HS 10 ship is roughly the size of a modern, large cruise ship here on Earth. These ships typically hold up to 2800 passengers and 1200 crew, for a total of 4000 people, or 400 per hull size. But that’s the maximum capacity and typically means 4 people to a cabin. If you’ve ever been on a cruise ship, you know those cabins are small, typically 15-22 square meters. Now this is roughly the size of a Journey Class cabin on our starliner (16-24 square meters), the difference being that that size on our starliner is for a single being, not a group of four. That immediately means we need to cut our passenger estimate down by a factor of four putting us at about 700 passengers.
The other thing our starliner has to deal with, that a cruise ship doesn’t, it life support. On a cruise ship, air is free. And while there is probably some recycling of water, it’s not a closed loop with full filtering needed. And cruise ships tend to stop and replenish supplies every couple of days unless it’s a long trans-oceanic cruise. So they don’t carry a lot of food on board. In the Frontier, ships are typically designed to carry half a year of food and the systems to process the air, water, and waste onboard which eats up more space on the ship.
Then you have all the lifeboats, spacesuits, and other ship’s vehicles that our starliner has to have. Cruise ships have lifeboats but the passenger density on them is going to be higher than the ones on our starliner and the some of the lifeboats on cruise ships are inflatable. That’s not going to happen on a starship. Those eat up space as well.
Finally, a cruise ship has a lot of the upper decks exposed to air. That doesn’t count against it’s volume but provides a lot of communal space for the passengers. That space needs to exist on starliners as well but has to be enclosed within the hull.
Between the extra life support machinery, the communal space, and the ship’s vehicles, that could easily reduce the capacity of the ship by 30 to 70 percent depending on how you figure it. 250 passengers is just 36% of the 700 passenger number we had left above. It’s possibly at the low end, but reasonable.
Another point of comparison is the volume based rules I created for starship generation. In that system, which accounts for passageway, cabin space, and storage space, I designed a ship the same size as a HS 10 ship in the KH rules. It had a total of 100 First Class cabins, 1250 Journey class cabins, and 200 Storage class cabins. And that includes the cabins for the crew, the size of which the rules don’t address. For this I’ll assumed 50 of the Journey class cabins are for the (lots of robots on Frontier ships). So the total capacity is 1500 passengers, which is a little large. However, this system doesn’t currently account for communal space which could easily be as much or more than the space taken up by the cabins. So if we cut that number in half we’re back to 750 passengers, similar to our initial estimate from the cruise ship.
The bottom line is that while 250 is probably a bit low, it’s not unreasonable and the actual number might be only a factor of 2 or 3 higher. So we’ll go with 250 passengers for our analysis.
A Typical Journey
The Starliner
Okay, we have our ship, it carries 250 passengers. What does a typical journey look like? For this example, we’re going say this ship makes the run between Gran Quivera in the Prenglar system and Triad in the Cassidine system, a jump of 7 light years. We’ll look at the finances later, right now we are going to just look at logistics.
We’ll start the journey at the point when the ship is all loaded and ready to depart Gran Quivera for Triad. The first step is the jump to the Cassidine system. It takes just under 4.5 days to get to jump speed and the same amount of time to slow down. We’ll assume the total travel time is 9 days. In truth it could be up to 11 days depending on the orbital dynamics of the two systems and how accurate the jump is but we’ll go with 9 days.
After docking at the station around Triad, the ship has to do a number of housekeeping activities. First, the passengers have to disembark, then the interior of the ship needs to be cleaned. And new provisions need to be taken aboard. Then the passengers and the luggage for the next trip need to board.
Since this is a HS 10 ship, it has three Class B atomic engines. These engines require an overhaul after every three jumps. Since there are three engines, it makes sense to stagger the overhauls so that you do one after each jump. You’re always doing an overhaul each time in port, but you are only doing one and that make it reasonable. We’ll also top off the fuel pellets in the engine we’re doing the overhaul on. We’ll assume that the ship has two level 4 engineers on board that work alternating shifts so that maintenance and overhaul work can proceed around the clock to be as efficient as possible.
Let’s look at time scales. If a cruise ship can load or unload it’s 2800 passengers in a single day, I think it’s safe to assume that our 250 passengers can be loaded and unloaded in a single day as well. So that requires two days in port for those two operations. Refueling one engine takes on average 7 hours. The engine overhaul takes on average 38 hours. That’s a total of 45 hours of work. Assuming it is split between the two engineers, either working together on 10 hour shifts or around the clock on alternating shifts, that takes two and a quarter days. We’ll call it three to account for any variations and potential issues that come up. The provisioning and cleaning can occur while the engine work is happening. So our ship spends 5 days in port and then is ready for the return journey to Gran Quivera. So far we’re up to 14 days.
The trip back is exactly the same. It takes 9 days to make the jump, and another 5 days in port before it’s ready to leave. That is a total round trip time of 28 days.
The Shuttle
That’s the main part of the journey. You also need some way to get the passengers from the surface of the planet up to the station to board the starliner. That means you’re going to need a shuttle. For comparison, a Boeing 737 is about the size of a HS 2 ship. And it carries 175 people and their luggage. A Boeing 747 is about the size of a HS 3 ship and it carries 416 people plus luggage.
Now the trip up to the ship isn’t that long. As the Dutch astronaut Wubbo Ockels commented about his 1985 trip on the Space Shuttle Challenger:
Space is so close: It took only eight minutes to get there and twenty to get back.
That was at 3g and we probably want to be a little gentler on our passenger but it shouldn’t take more than a half hour to get into orbit and an hour back. They will need acceleration couches regardless and those take up a bit more room than a typical airline seat but not by much. It’s completely reasonable that a HS 3 shuttle can carry the 250 passengers for our space liner.
That means that we’ll need one shuttle at each system. If we let our spaceliner carry more than the 250 passengers, we’ll need more shuttles as well.
How Many Ships Do We Need?
With one ship, every 28 days we can move 250 beings from Gran Quivera to Triad and another 250 beings in the reverse direction. If this is the only ship running the route, there will only be a single trip once a month between the worlds. If you miss your flight, you’ll have to wait 28 days for the ship to be back. And if you want a round trip then you will spend at least 5 days in the destination system assuming you fly back out immediately when the ship leaves, otherwise it will be 33 days (or longer) after you arrive before you can catch a ship back.
Of course we can increase the frequency by adding more ships on the route. Let’s say we want a flight leaving every day. That’s easy enough. It’s a 28 day round trip for a single ship, you just need 28 ships and means you have a departure and arrival every day. And that allows you to move 250×28 or 7000 beings each way between the two systems in that same 28 day time period.
Regardless of how often you have interstellar departures (as long as it’s not more than once a day), your one shuttle can supply all of those ships. So even though you have 28 starliners, you only need a single shuttle at each system to handle the passenger traffic.
But that’s not the whole story. Each of those ships needs to have annual maintenance performed and that will take on average 15-16 days per ship. Which means once a year, each ships needs to be pulled out of rotation for one cycle to have it’s maintenance done. That means we need a spare ship to fill in while it’s out of commission. If you’re running a ship every day, you’ll actually need two spare ships to cover the gaps as the repair time on 28 ships is longer than a year and there will be some times when two ships are in maintenance. The shuttle needs annual maintenance as well, but that only takes on average 8-9 days as it is a smaller ship. If you only have 1-3 flights in that 28 day period, you can get away with a single shuttle and squeeze in its maintenance between runs, otherwise, you’ll need two of them to cover the maintenance periods.
My rendition of the AD star system map. Click for full size version.
That’s the numbers for a single system. There are 17 inhabited star systems on the AD map (not counting the Zebulon system) for a total of 19 jump routes. If there is a single flight along each route, once a month, you need a starliner for each leg plus a spare. And a shuttle in each system. That’s 55 ships. Of course that ignores the fact that some of the systems have two inhabited worlds (23 in all) and you’ll need more shuttles at those worlds and some ships to move passengers between the two planets in the system.
Now 55 ships (or 67 to account for the two world systems), isn’t too bad, but that is only a single trip every 28 days. If you want a daily trip between systems, you need 30×19 starliners (570 ships) plus 2×17 shuttles for a total of 604 ships. Again, accounting for the two planet systems, that’s another 6-12 shuttles and anywhere from 6 to 168 interplanetary starliners depending on how frequent you make the trips (6 shuttles and 6 ships for once every 28 days and 12 shuttles and 168 ships for daily trips).
With the starship construction centers only capable of supporting about 1500-2300 ships, we’re now looking at about one quarter to one half of the total ship capacity of the Frontier just to connect the worlds for a few hundred people moving between each system each day.
If you want more people moving between the worlds, you have several choices. First, you can make the passenger density higher and make each ship carry more. But that’s only realisticaly a factor of 2 or 3. As another option, you can make the starliners bigger. But remember, if the average ship size increases, the total number of ships the Frontier can support goes down. The final option is to increase the number of ships that the Frontier can support.
Implications
What this all means is that you have to make a decision about interstellar travel. If you have few ships, then trips are few and far between and not a lot of people will be traveling between worlds. Your characters should expect to spend months or years on a single world with all their adventures there, as getting tickets to move between worlds could be relatively rare depending exactly on how you structure it. It also probably means they won’t have their own ship as they are too rare.
Additionally, unless there are daily (or every other day) flights between each world, then it will take a long time to travel across the Frontier with layovers of several days to weeks in each system depending on the frequency and scheduling. If they are traveling between worlds, then there will be even longer spans of time (above the already long base travel times) between adventures and your plots need to account for those long time scales.
This article was focused simply on the logistics of travel and the number of ships it would take to support that. I didn’t even address the costs and economics of each individual flight. That will be part 1b at a future date.
What are your thoughts on the number and size of passenger liners? How do you handle it in your game? What other implications have you thought of that I didn’t cover? Let me know in the comments below.
This month sees the final leg of the trip for the remaining ships of the Discovery Squadron and it’s final disbanding, the HSS History’s Hope gets back on track on it’s exploration mission, avoiding it’s assailants in the YS01 system, and a new ship emerges from the Minotaur shipyards that will play a pivotal role in the history of the Frontier. Spacefleet also begins construction on the ships for Strike Force Meteor.
As always, you can follow along daily on the Star Frontiers Twitter feed if you don’t want to wait for the monthly summary. I’m a few days behind at the moment with my Twitter posting but I should get caught up in the next day or so.
Date (FY)
Events
61.051
– The Sathar starship construction center in the Liberty system completes 2 destroyers.
– Strike Force Nova jumps into the Zebulon system. They begin decelerating toward Volturnus.
– After much deliberation, the sathar high command decides to send two of its new cutter ships to the Kazak system to scout out the UPF and Rim forces there.
61.052
Construction begins on a new UPF assault carrier at the PGC shipyards (Gran Quivera, Prenglar). This is the first of the new ships commissioned for the new Strike Force Meteor group to be built around the battleship already under construction.
61.053
– Shakedown cruise complete, passengers begin loading onto the newest saurian Ark Ship.
– The HSS History’s Hope detects emissions from another ship in the YS01 system, assumed the be their previous assailant. However, the ship is far away on the other side of the system. They believe that they will be able to get out of the system before it could catch them, even if they were already detected.
61.054
Construction begins on a new Spacefleet light cruiser, part of the new Strike Force Meteor, at the CDC shipyards (Triad, Cassidine).
61.055
Strike Force Nova arrives at Volturnus (Zebulon). The two Truane’s Star militia assault scouts are released to return to their home system. They begin accelerating toward jump speed.
61.056
– Construction begins on two destroyers for Spacefleet’s new Strike Force Meteor at the Hentz (Araks) shipyards.
– Deceleration, plotting, and engine repairs complete, the HSS History’s Hope begins accelerating for their jump back to YS02. Signals from the other ship in the system change and it seems to be accelerating toward them. However, its distance makes an intercept nearly impossible.
61.057
– Construction begins on two frigates for Spacefleet’s new Strike Force Meteor at the Minotaur (Theseus) shipyards.
– Sathar cutters arrive in the outer reaches of the Kazak system and begin a slow deceleration as they gather data on the system.
61.058
Repairs at the PGC shipyard (Gran Quivera, Prenglar) restore capacity to 85%.
61.059
After several weeks of short intra system runs, the CDCSS Mystic embarks on its first interstellar journey shuttling several CDC managers to Fromeltar to meet with members of the new Groth Energy Corporation.
61.060
– The HSS History’s Hope makes the jump to YS02 without encountering the other ship which was still 1.3 AU away when the jump was made. They begin decelerating and plotting their next jump, which after more study of the astrographic data, will be back to YS03, a jump of 6 ly.
– Upon arrival in YS02, the HSS History’s Hope sends a subspace message back to Histran informing their organization of the presence of the hostile ship still in the YS01 system and their plans to continue onward. They YS01-YS02 jump data is not transmitted.
61.061
Construction begins on two assault scouts for Strike Force Meteor at the PGC shipyards (Gran Quivera, Prenglar)
61.062
Sathar starship construction center in OFS019 completes a cutter.
61.063
Sathar cutters in the outer Kazak system complete their deceleration and continue to collect data on the Rim forces in the system. They relay that Strike Force Nova seems to have departed the system.
61.064
The two Truane’s Star militia assault scouts arrive back at Pale station. The crews are given a three week leave while the ships are overhauled and repaired in the shipyard before rejoining regular patrol duties.
61.065
Memorial Services held in Valencia City (Clarion, White Light) for the crew of the Clarion Royal Marines frigate lost battling the sathar in the Zebulon system.
61.066
Sathar begin mobilization for final push into the Saurian system.
61.067
After 100 days all of the newly hatched Eorna infants are still alive and growing healthily.
61.068
CDCSS Mystic arrives at Groth Station (Fromeltar) without incident. Its maiden interstellar voyage went off without a hitch.
61.069
After months of data collection and analysis, scientists believe they have cracked the structure of the signals from OFS200. Some of them are voice transmissions in an unknown tongue that sounds similar to recordings of sathar voices.
61.070
The HSS History’s Hope successfully makes the jump from YS02 to YS03 and begin their deceleration and plotting of a jump back to YS02.
61.071
– Summer ends on Alcazzar. CDC begins pulling staff in preparation for the long winter.
– Construction begins on two assault scouts for Strike Force Meteor at the CDC shipyards (Triad, Cassidine)
61.072
With the release of the findings about the signals from OFS200, the Anti-Satharian League stage demonstrations outside the Council of Worlds and Spacefleet headquarters demanding an immediate attack on the system to eradicate the worms.
61.073
Loading complete, the sixth saurian Ark Ship departs the Sauria system in search of a new world away from the sathar.
61.074
After over a year of rebuilding and new ship construction, the sathar begin gearing up for final push on the Sauria system.
61.075
Sathar starship construction center in OFS138 completes a heavy cruiser.
61.076
Repairs of Triad Starship Construction Center bring it up to 90% capacity.
61.077
Construction of the CMS Flitter complete at the Minotaur (Theseus) shipyards. The ship begins its maiden voyage to its home system of White Light.
61.078
After spending ten days in port, the CDCSS Mystic loads passengers for a return trip to Triad (Cassidine). The CDC delegation remains on Groth (Fromeltar) to continue negotiations with the Groth Energy Corporation.
61.079
The UPFS Eleanor Moraes emerges from the Minotaur (Theseus) shipyard and begins a shakedown cruise as the final members of the crew begin to arrive in the system.
61.080
Repairs at the PGC shipyard (Gran Quivera, Prenglar) restore capacity to 90%.
