Life has been a bit crazy recently and I haven’t posted anything for a couple of weeks but progress is being made. I should be getting several post up over the next couple of weeks. We start this month off with an NPC that you might encounter while traveling in the outback on Pale, Carlos Kildare. The Death at Rosegard adventure features an opportunity for the PC’s to meet and possibly work with Carlos. That interaction will be detailed in a different post but for now, here is his description and stats.
Carlos Kildare
Quickdeath hunter
Carlos was born on Minotaur but emigrated to Pale when the planet was first colonized. He is a first-wave colonist but has become a bit of curmudgeon as he has aged. Carlos is the classic “been there, done that and got the scars to prove it” sort of character that you might meet around the Frontier.
He grew up in Point True and was present when the sathar landed at the outset of the First Sathar War. He joined the Aletheia Resistance Band and fought the alien invaders for the duration of the war. With the defeat of the sathar fleets in space and material support from the Pan Galactic Corporation, the government of Pale inducted all the resistance fighters into ad hoc army formations. Carlos attained the rank of sergeant in one of these rag tag militia formations but left the military after the sathar infantry were wiped out on Pale.
Since that time he’s done well collecting bounties on sathar attack monsters that were let loose during the war. He uses a modified Snow Panther track vehicle (stats below) to get around. For a time right after the war, there was a glut of bounty hunters seeking quick cash but the pickings have become slim and only a few hardcore hunters remain in the business. Carlos had his crew quit after a recent run of bad luck and is seeking extra hands for his team.
He has also recently been diagnosed with a nearly inoperable cancer. He could allow the doctors to attempt to treat it but the “cure” will leave him weak and change little or nothing. He would rather spend his time going after bounties and may have a bit of a death wish.
Stats
Human, Male
Age: 140 STR/STA: 45/55 DEX/RS: 60/60 INT/LOG: 35/40 PER/LDR: 35/50 PS: +3, IM: +6, Ranged: Beam 70%, Projectile 50%, Melee: 53% PSA: Military Skills: Beam weapons 4, Melee weapons 3, Projectile weapons 2, Technician 2 Equipment: Military Skeinsuit, Sonic Disruptor & power belt, Machete, chronocom, ID, sun goggles, and military issue parka and snow pants. Equipment stowed in the Snow Panther: 2 holo projectors and a type 3 parabattery, a kerosene powered type 1 generator, five 5 gallon jerry cans (for kerosene), 3 electro stunners, two pikes (pole arms), 4 solvaway, 5 tangler grenades, 5 frag grenades, 1 auto rifle, a dozen 20 SEU clips and 6 auto rifle clips, survival food & water, a single wire electric fence (100 m long with 20 SEU clip- acts as a stun stick if anything touches the wire), a depleted med kit (enough Biocort and supplies to perform first aid twice as well as 4 doses of anti-tox), and a half depleted tech kit (50% chance the kit is missing the part you need for the current skill check).
The Snow Panther is a tracked working vehicle designed for the bitter cold of the planet Pale’s environment. Most that are used in the outback are optimized to be lived in with fold down cots, a small camp stove and a space heater. With a full complement of passengers, it can be a bit crowded but is still workable.
Kildare’s Snow Panther has been modified with a roof hatch and the roof has a low railing running around the roof. There is also a winch and swing arm for lifting heavy objects to the roof as well as a power port that connects to the parabattery. On the sides and back of the vehicle is a folding catwalk with railing that is just wide enough for one person to walk on. While the cat walk is deployed it is possible to walk on it entirely around the vehicle (but off the ground) except in front.
Note: The generator will operate for four hours on five gallons of fuel. It has a full tank and the jerry cans are full so the generator can be run for a total of 24 hours producing 500 SEU/hour. The snow panther uses 1 SEU/kilometer to travel. The life support systems and cook stove use 2 SEU/day.
One of the encounters the PCs have while investigating the murder at the mining facility near Rosegard is a run-in with a new Sathar bio-construct, the Sathar Poison Squirrel. Based on a native Pale species, this bio-construct is new in the Frontier, having only been released in the last year or so. The PCs will be one of the first to encounter it. Here is the description and stats for both the native Pale Tailless Squirrel and the Sathar Poison Squirrel.
Pale Tailless Squirrel
The Pale Tailless Squirrel is a small rodent, native to Pale remarkably similar to squirrels of the human homeworld but lacking the signature big bushy tail. They can be found all over Pale in any temperate, tropical, and even some arctic climates.
Pale Tailless Squirrels range in color from light tans and greys to nearly snow white depending on their environment. They are generally skittish and shy away from members of the Frontier races although may approach if there is a chance of free food. If cornered these creatures will fight but their small mouths and jaws, primarily designed for eating vegetation and nuts, do not do much damage (1d5 pts).
Pale Tailless Squirrel
STA:
10
RS:
70
Move:
Medium (30m/turn)
Size:
small
#Appearing:
1d2
Attack:
50
Damage:
1d5
Sathar Poison Squirrel
This is a sathar bio-construct based on the native Pale Tailless Squirrel. This is a new creature in the Frontier that has just been released in the last year or so and is starting to invade the ecosystem. It was engineered in sathar biolab somewhere on Pale. Although first seen near the village of Rosegard, the bio-lab in question is not near that village.
The Sathar version is more gregarious and will be much more likely to approach members of the Frontiers species. It is more playful than the native version but will inevitably try to bite, typically fingers or toes. While the bite only does 1d5 points worth of damage like the native creature, unlike the native squirrel, the bite is highly poisonous. The Sathar Poison Squirrel’s bite contains a S4/T20 poison. A successful STA check results in half damage. Standard Anti-Tox will treat the poison if properly administered.
Pale Tailless Squirrel (left) compared to a Sathar Poison Squirrel (right). The only immediate difference is the faint pale stripe down the back of the Sathar Poison Squirrel which is not always obvious.
Physically, they are nearly identical to the native species. The most noticeable difference is that the bio-construct has a stripe of fur down its back that is slightly paler than the rest of the fur. The native species does not have this stripe. If examined closely there are other small details that set it apart from the native version such as stronger jaws, sharper teeth, slightly more hook like claws on its toes, and a stronger musculature.
Sathar Poison Squirrel
STA:
20
RS:
70
MV:
Medium (30m/turn)
Size:
small
#Appearing:
1d2
Attack:
60
Damage:
1d5
Special Attack:
poisonous bite, S4/T20, current STA check for half damage.
Traveling through hyperspace ain’t like dusting crops, boy!
Han Solo, Star Wars
While a little out of context (Han was actually referring to astrogation calculations), the quote still applies – faster than light (FTL) travel is not just a walk in the park.
In this post, I want to look at a mechanic for FTL induced illness, which I’ll be calling Void Sickness. The name comes because I created this mechanic for my Star Frontiers games where FTL travel is accomplished by traveling through “The Void” or “Void Jumping”. In that game, you accelerate up to speed (1% the speed of light) and then make a nearly instantaneous transition into and out of the Void to cross many light years. The rules are a little vague on the actual duration but I’ve always used 1 second per light year. When you re-emerge you are in a new star system (hopefully your destination if you got the astrogation correct).
But what happens physiologically when you make the transition? You are entering, even if it is briefly, a dimension your body wasn’t designed for. It’s natural that your body may have an adverse reaction to the transition.
During the Jump
First there is the physical manifestations during the brief time in the Void. I always describe this as a confusion of the senses. You can feel colors, hear tastes, see sound, etc. And it could be different for different species or even individuals within a species. I often use this picture to describe the visual sensations.
But what I want to talk about today is what happens after you exit the Void.
Aftereffects
Many games don’t worry about this. They just assume that the PCs and others can experience FTL travel with no worries or side effects. And that is absolutely fine. If having potentially negative consequences of FTL travel is not something you want in your game, then you don’t have to have it. But if you do, this is a possible mechanic you can use.
In my case, I wanted to add a potential downside to FTL travel that starts out fairly benign and uncommon but becomes worse the more and more you travel. Until it possibly reaches a point that you simply don’t want to make any more interstellar trips unless you absolutely have to. Here’s what I came up with.
Void Sickness
Void Sickness is not an uncommon effect of FTL travel and some people are more susceptible to it than others. But even if you are susceptible to it, it doesn’t affect you on every trip. It is also a condition that worsens, with both increased susceptibility and symptoms, the more times you engage in FTL travel.
I’ll present this as a percentage based system (since that is what Star Frontiers, which I originally developed it for, uses) but you can easily convert this to a d20 or other system if you want.
Original Version
This is the original version of Void Sickness I developed. It’s actually pretty harsh, I’ll present a much milder version below.
To see if you are susceptible to Void Sickness you need to make a check against your Stamina (or CON or the equivalent from your system). Since STA in Star Frontiers typically ranges from 30-70, you make a STA+20 check the first time you make a Void Jump. If you make the roll, you do not suffer from Void Sickness on this trip and your base chance to avoid Void Sickness on all other jumps starts at 95% (i.e. if you roll a 95 or lower on d100 you are not sick).
If you fail this roll, you are susceptible to Void Sickness. You suffer from the sickness on this trip and your base chance to avoid it on future trips is equal to your STA score. Thus you are much more likely to succumb to it in the future.
On all future FTL trips, you make a roll against your resistance score. If you succeed, you do not suffer from Void Sickness for that trip. If you fail, you do suffer and your resistance score is reduced by one.
The impact of the Void Sickness is determined by the amount you failed your roll. The difference between your roll and your resistance score determines both the strength of the effect and its duration. This value becomes the penalty you suffer on all skill and ability checks and it lasts for that many hours.
For example: Drod, a dralasite, has a STA of 50 and is making his first interstellar trip. He checks for his susceptibility to Void sickness by rolling a d100 and rolls an 76 which is 6 points higher than this initial check (50+20 = 70). He is susceptible to Void Sickness and going forward his resistance score is only 50. For this trip he suffers a relatively mild case and only has a -6 modifier to his skills and abilities for the next 6 hours. If on a future trip,if he were to fail the resistance roll again, his resistance would drop to 49.
A Milder Form
In its original form, the Void Sickness is something that everyone will succumb to eventually if they take enough interstellar trips and if you have a string of bad luck, you could succumb to it fairly quickly. If you want the effect to be fairly rare, and slower acting when someone does have it, you can use the following variation. With this form, it is probably something the PCs will never have to deal with but you could have Void Sickness in your campaign as setting material to use on NPCs.
In this form, the base chance the first time you make a jump is a flat 95% on a d100. If you roll less than that you don’t have the sickness and never will. You never have to roll again. If you do fail the roll, you have a mild case this time (you are not going to fail by more than 5 points) and your resistance roll going forward is equal to whatever you rolled this time. (i.e. if you rolled a 98, your resistance chance for all future trips starts at 98). The effects and increase in susceptibility are as before.
Mitigations
If the occurrence of this illness is common, there will probably be a number of ways to deal with it from drugs that boost your immunity to other drugs that mitigate the effects. If the occurrence is more rare, there may only be drugs to mitigate symptoms and there may not be anything specifically for Void Sickness but only the use of regular drugs to treat the symptoms. Here are some that I use in my game. All these are required to be administered by someone with the Medic skill.
VoidBoost
Cost: 25 credits
VoidBoost is designed to improve a being’s immunity and resistance to Void Sickness. If administered prior to the Void Jump, VoidBoost raises the recipient’s resistance to Void Sickness by 20 to a maximum of 95%. Only a single dose of VoidBoost can be administered for any given trip. Additional doses have no effect.
Most starliners stock this medication for their passengers. It is either provided for free as part of the passage fare or at a discounted cost.
VoidBlock
Cost: 40 credits
VoidBlock is a broad spectrum medicine designed to reduce the effects of the symptoms of Void Sickness. It has no effect on the duration. It works by reducing the penalty to ability and skill checks due to Void Sickness. VoidBlock reduces the negative modifier associated with Void Sickness by 1d10+10 for 20 hours. No more than one dose can be taken in a 20 hour period. Any doses taken beyond the first in that time automatically have no effect. VoidBlock cannot be taken in conjunction with VoidReduce. If it is, neither drug has any effect.
Most starliners stock this medication for their passengers. It is either provided for free as part of the passage fare or at a discounted cost.
VoidReduce
Cost: 35 Credits
Void Reduce is designed to reduce the duration of the effects of Void Sickness. It has no effect on they actual impact of the symptoms. A dose of VoidReduce decreases the duration of Void Sickness by 1d10+10 hours. Only one dose of VoidReduce can be taken for any given occurrence of Void Sickness. Any additional doses automatically have no effect. VoidReduce cannot be take in conjunction with VoidBlock. If it is, neither drug has any effect.
Most starliners stock this medication for their passengers. It is either provided for free as part of the passage fare or at a discounted cost.
Other Medications
Depending on your game system there may be other medications already in the game that can mitigate some of the effects of Void Sickness. You can make a judgement based on the effects of the drugs in your game. For Star Frontiers, I allow the following:
Biocort – one dose of Biocort reduces the duration of Void Sickness by 1d5+5 hours. Only one dose of Biocort can be applied for a given occurrence of Void Sickness. If administered with VoidBlock or VoidReduce, Biocort has no effect.
Stimdose – one dose of Stimdose reduces the effects of Void sickness by 1d5+5 for 10 hours. Only one dose of Stimdose can be administered in a 20 hour period as per the standard rules. If administered with VoidBlock or VoidReduce, Stimdose has no effect.
Neutrad (from Zeb’s Guide) – one dose of Neutrad reduces the effects of Void Sickness by 1d5 points and its duration by 1d5 hours. Only one dose of Neutrad can be administered for any given case of Void Sickness. However, if administered with any other medication, none of the other medications have any effect.
Side note: Due to the way Neutrad affects Void Sickness, scientists believe that Void Sickness is some form of temporary radiation poisoning but the exact form of radiation is unknown and not reproducible outside of a Void jump. Many companies contract with ships to carry small micro experiments that run during the Void jump in an attempt to understand the cause of this illness.
Converting to Other Systems
Adapting this to another system is fairly straightforward.
If you want to use this in a d20 or 3d6 based system, You could simply multiply the relevant ability score by 3, 4, or 5 to get the initial base percentage for Void Sickness resistance if you wanted to keep with the d100 percentage system outlined. The multiplier would depend on how likely you want the occurrence to be but by default I’d use 4 as that maps the closest to the ability score range that I designed against. In any other system just use a suitable modifier.
If you don’t want to use the percentage based system but use the core mechanic from your system, simply reduce the percentage by the appropriate multiplier. e.g. for a d20 based system simply divide the resistance chance by five (and subtract that from 20 for a roll-over success system like D&D to get the target number.) Penalties can still be just the difference between the roll and the target and the duration becomes the difference times the modifier used. If you are using a 3d6 system the percentages don’t map as closely but it still works. The net effect would be for a slower initial deterioration followed by a very rapid final decline. If you are using a game with a dice pool system, a little more work would be required to convert the mechanic.
The hardest part to adapt would be the slow deterioration of the resistance chance. Instead of a reduction on every failure, you could implement a reduction after every N failures, where N is probably the multiplier used elsewhere. Or you could require a CON (or equivalent) check each time they suffer from Void Sickness. If they fail, their resistance weakens. If they succeed, their resistance doesn’t change.
Final Thoughts
I created this illness primarily as background flavor for my setting. It’s not something I ever expect the PCs to suffer from. Unless they want to. If the PC’s background is such that they would have taken interstellar trips before the game starts, I give them the option to automatically select susceptibility if they want or to just roll. It was more designed as something that NPCs could suffer from and that the PCs would have to deal with in that manner. I also intended to use in some of the stories I was writing at the time (and that I may someday get back to).
Have you ever done anything similar in your games? Does this sound like something you might use in the future? Share your ideas, suggestions, and thoughts in the comments below.
In part 2, we ended with the final version of the hull model for the Scavenger Transport and all that was left was to add in some of the details, most notably the doors and other bits that extended through the hull. After that, it is just “decorations” to add a little character.
Finishing the Physical Model
Adding in the bay doors was straightforward. They are just basically rectangles after all. For the smaller shuttle and workpod bay doors toward the back on the lower level, I added a split vertically down the middle for the doors to open and swing outward on the sides. For the larger cargo and runabout bay doors, I decided that they would open top and bottom so the seam detail runs horizontally. In the case of the cargo bay doors, the lower portion of the door can double as a loading ramp if necessary.
Next I wanted to break up the hull a bit so it wasn’t so plain and I created a little triangular design that I placed on the lower and middle decks for and aft of the ion cannon as well as on the wings. I then added a cylindrical structure on either side of the second level. Next, I added a bit of a domed structure on top of the runabout bay. Finally I created some large (2m diameter) portholes and placed them on the back of the ship on deck two between the cargo bay and runabout bay. These are positions to be in the rec room at the back of that level and the two cabins back there as well.
Back of the ship with the bay doors and portholes. You can also see some of the other details mentioned earlier.
At this point I was looking at the model and thinking it was looking pretty good and then I realized: I forgot to add in all the bits and pieces that stick out through the hull! Again these were fairly straightforward as they are fairly simple shapes. I tweaked the block that was the sensor array extension as it was sticking too far out. The rocket launcher (deck 1, starboard side) may get some tubes added to it for the missiles to launch out of in the future, but for now, I just left it as a solid block. I also rounded the edges of the airlock a bit.
Speaking of the airlock, after adding it in, I realized it was really poorly placed. It’s right up against the wing and behind the front part of the engine. Luckily the wing didn’t overlap it at all. I didn’t even consider it’s placement when I made the wing so I was lucky I didn’t have to go back and tweak that. It probably would have been better to put it on the lower level toward the front of the ship. I guess the engineers weren’t thinking too hard about how the engines were going to be placed when they designed the fuselage :-). However, its poor placement gives a bit of flavor and something to hassle the crew with (and for them to grumble about). It truth, it’s more of a backup measure anyway since the ship isn’t designed to actually dock at stations but rather pull up next to them and transfer via the shuttles and open cargo bay doors. So in practice it’s only a minor annoyance.
Once I had these last structures added, the ship was all done.
3D Printing
With the physical model done, it was time to start testing out 3D prints. I started with a simple small, low resolution print. This was done at 0.2mm/layer and at the native scale of the model (1/1000 scale). It only took about 50 minutes.
You can definitely see the print layers on the model. There are also hints of the details on the body, wings and engines although the size of the features are such that they just don’t show up at at this scale. This particular print was done with the bottom of the ship on the build plate. That may not be the best way to print as we’ll see in a minute.
Since it look good enough small, it was time to scale it up. The next print was a 1/500th scale print, double the size of this one. Again I printed at 0.2mm/layer and with the bottom of the ship on the build plate. Although this time I switched to white plastic. Here’s a picture of that print, together with the smaller black print, our trusty quarter, and a Star Frontiers Assault Scout model at the same scale as the larger print. This print took about 5 and a half hours
If you look closely at the larger print, you can still see the layer lines although since the print is bigger, they are not as pronounced. You can also see the turrets on the laser battery print at this scale. They were just too tiny to print on the smaller scale. You’ll also notice that the assault scout model in the back looks super smooth. That is because it was printed at 0.1mm/layer and was printed standing up.
So that’s the next thing to try. My 7-year-old son really liked the ship and wanted an orange one (that’s his favorite color). Since I have a spool of orange filament for my printer just to print things for him, I swapped out the white for orange, flipped the model on it’s back, and started a 0.1mm/layer print. Here is the result, five and quarter hours later:
The surface on this one is much cleaner. That is partially due to the smaller print layers and partially due to the orientation of the layers relative to the model, but more of the latter. A 0.2mm print in this orientation would look pretty good too. The bigger difference, however, is the backs and undersides of the models. Let’s take a look at those. Here are the undersides:
The lighting could be better but you’ll notice that the bottoms of the wings and engines on the white model are really rough. That is partially due to the fact that I didn’t completely clean them up but also due to the nature of 3D printing. Since each layer has to be placed on the layer below, if you have a floating bit of your model with nothing under it, the printer prints support material to get up to that that point where it can start printing the model. So in the white model, a bunch of support material had to be printed to support the engines and wings. Most of that will clean off with some effort using an sharp knife and sandpaper (and my Dremel) but it’s not completely clean. On the orange model, we don’t have that problem and the engines and wings look really good and there was nothing to remove. However …
the back of the orange print has some issues. Granted the back of the white one isn’t the best, as you can see some issues with the layers of the print being slightly misaligned (I need to re-tighten the belts that drive the print head or slow down the print). However, you can see the detail of the bay doors and the portholes (barely, they should probably have been a bit thicker for printing).
On the orange print, this was the side toward the build plate and so had to have supports to the parts of the model that were suspended. In this case that is the back of the engine and wing as well as parts of the back of the ship. The bits on the engine and wings again are not completely cleaned up but they are flat surfaces in is orientation and much smaller surfaces as well. They will be much easier to clean up than the rough sections on the white print.
The back of the ship is a different matter. The surfaces of the cargo and runabout bay doors were the only parts actually touching the build plate. The rest of the back of the ship and the portholes were raised slightly. Because of that the printer had to lay down support material. However, because they were only slightly raised (like one or two 0.1mm layers), there really wasn’t that much room to print support material and it is all fused together. It could probably be cleaned up with some work but it would be pretty tough.
Finally I did a last print at the higher 0.1mm/layer resolution with the ship on it’s bottom (same orientation as the white print) just so see how that higher resolution affected the look.
As you can see, the to surfaces are much cleaner in this print. In fact, I would be very satisfied with that print surface on the model. Here’s the bottoms and backs:
Those bottom surfaces are still fairly rough although I think they are better on the higher resolution print. The back of the higher resolution print is definitely cleaner.
I think the print with the ship on it’s back is still the better way to go, but barely. It’s a tough call and I could be convinced otherwise. To address the problem with the support material on the back of the ship, I have a couple of options. One is to just remove all the surface features on the back of the ship completely. That would give a flat surface to print and would eliminate the problem but you would lose the details on that part of the unpainted model (you could always paint them back on). Another option would be to just eliminate the portholes. There is enough relief to the doors that you could trim the support material from around them. The rest of the back of the ship might be a bit rough but it is an easily accessible area to sand and clean up. The final option would be to increase the relief on everything, both the doors and the portholes, so that there is a bit more space there making the support material easier to clean off. I haven’t decided which route I’ll take yet but I’ll probably do some experimenting to try out the different options.
Going Forward
My Patreon supporters have already received a copy of the model file as it currently exists (that’s one of the perks of being a supporter). At some point I’ll put the model up for purchase for those that would like to get a copy (That will be on DrivethruRPG and either here or my New Frontier Games website). I’ll also make 3D printed models available. That will come once I’m comfortable with the way the prints are coming out.
The next step for the model is to back to the digital model and paint it so it can be used in 3D renders. I need to add textures and materials to the model to give it color and life. However, I’m going to put that bit on hold for bit as it’s not really needed for the module (and I want to go over the Blender tutorial on how to do all of that stuff. I have some experience from the assault scout but it was very trial and error). So this project will probably go on hold for a few weeks while I work on some other bits and pieces.
Bill is also working on the final versions of the deck plans and I’ll post a copy of those once they are available.
Let me know if you have any questions, comments, or suggestions below.
More progress on the ship model. If you haven’t read part one of this series, that describes how I laid out a model of the interior of the ship as a skeleton to build the hull around. In this post, I’ll actually start building the ship out. Let’s dive right in.
Try 1
I started by pulling the skeleton model I exported from OpenSCAD into Blender. The first thing I noticed is that Blender likes to work on really small scales. The model isn’t that big, only about 50mm long, half that wide and tall but it was was huge in the default view port. I had to zoom way back.
(If the text on that image looks a little small, that’s because its a screen capture of my entire 4k monitor’s screen. It’s a 43″ screen so I work at full resolution for maximum screen space.)
With that loaded, I can start forming the hull around it. It all starts with a cube. I created a cube the height of the cargo bay and then stretched, extruded, and molded it to fit around all the rooms and sections of the lowest level. Once that was done, I extruded part of the top of that level up to form the basis of the hull around the middle deck and then stretched and molded it to properly fit. Finally I did the same thing for the uppermost layer.
In modeling the hull, I had it extending out beyond the bay doors on the sides and back so that they were inset from the hull slightly. The circular bridge area on the upper deck was modeled as a separate piece.
With the hull done, I created a model for the ion cannon and the laser battery and placed them in their appropriate positions on the model. When I was done, it looked like this.
It looks pretty good. But for some reason, I just didn’t like it. I think a big part of it was that it felt too smooth. I could have turned that down a bit but I still didn’t like the shape. There were bits of the hull that just looked weird up close and had somewhat strange geometries. One was the the bit of hull on the left and right side of the bridge “window” area. If you look closely at the image, you can see that it dips back down between the outer edge of the hull and the bridge proper. There were some other areas like that on the back of the ship and around the hanger bay doors as well.
So like all good prototypes, I threw it out and started over. The only thing I kept was the bridge, the laser battery, and the ion cannon.
Try 2
With a little more experience under my belt, I decided to start over and try again. I kept the original version around in case try 2 was worse but I didn’t expect it to be. This time around I decided that instead of trying to do the hull as a single piece of geometry, that I would break it up in to connecting pieces. While I had originally planed to do five pieces (one for each deck and two for the spaces between decks), I ended up only doing two overlapping pieces as you’ll see below.
This time around I decided to make the outer hull on the back and side be flush with the cargo, shuttle, workpod, and runabout bay doors. I’ll probably add a bit of overhang to those but that detail will be added to the exterior instead of built into the basic hull shape.
Again I started with the bottom of the ship. The process was the same but I made some different design decisions. I also was much more careful about coordinates when pushing, squeezing, extruding, and scaling parts of the hull. There were a number of times that I realized I had done something wrong and destroyed my symmetry. Each time that happened, I went back and fixed it. This is something that I didn’t do on the first attempt. I probably should have worked on just half the ship and mirrored it but it seemed to make more sense at the time to do it the way I did. (I also should have taken more screenshots as I was working on the model to show the stages but I didn’t. I’ll try to be better next time.)
Regardless, I created a lower deck model that I was much happier with than the first one. Once that was done, I started a second section of the hull and modeled everything on the second level except raising it to the full four meter height of the room containing the machinery for the ion cannon or the area that would connect the engineering spaces to the engines proper. The former would be done as part of the connection between deck 2 and 3 and the latter when I actually modeled the engines.
Once I was happy with the second deck it was time to connect the two. My original plan had been to created a completely separate piece of geometry to make the connection but sitting here with the two pieces in front of me, I decided to just extend the top of the lower deck and form it into the shape I wanted. So I extruded the bits under the second deck up and got to shaping the hull. In the end I didn’t just stop this modeling at the bottom of deck 2 but because of some of the feature that I wanted to continue extending, parts were modeled all the way up to the top of the second deck. Satisfied with that, it was time to move on to deck 3.
Again, the original plan was a separate piece of geometry but since this level was fairly simple, I decided to just extend the top of level 2 upward. I was several hours into the project at this point and feeling comfortable with the tools so it went fairly quickly.
Since the bridge area, laser battery, and ion cannon were already done, I just had to turn them on. Doing so made me realize that the area where the cannon was attached felt a little two boxy so I tweaked the design a bit there. I also needed to tweak the geometry around the bridge to expose a bit more of it. With that done, I ended up with this model for my second attempt.
You’ll notice that this one is much blockier than that first one. In that first attempt I had already applied some smoothing filters before exporting the image. I had not yet done so on this one and had first planned on leaving this one as is. I thought this looked pretty good so I even exported this as a 3D model and did a small test print.
I was quite happy how the print turned out. The barrels on the laser battery were too small to print at this scale (1/1000) but otherwise it looked pretty good.
However, looking at the actual model some more I decided I didn’t like it so faceted. Plus if you look at the back of the ship, there is that little bit of contouring that is pushing in a bit. That section fills the space between the doors for the shuttle and workpod bays. I decided that I wanted that to be a feature that ran all the way up the ship.
So I went back into the model and started tweaking. First I modified bottom part of the upper deck geometry to continue running that feature all the way up the aft portion of the ship. This was actually fairly easy as at this point in the ship, the outer edge of the hull is well beyond the interior walls. After that was added, I started smoothing out the surface and adding edges and features in where I wanted the model to have sharp edges. I ended up with the following model.
The one thing that adding the smoothing did was somewhat highlight the fact that it is two different pieces of geometry. You can see a slight seam between the two pieces in the area under the ion cannon. It runs around the front of the ship and back to the point just in front of the bulge mid-ship on the lower deck (that bulge is the location of the reflec screen on this side of the ship) where it turns upward to the top of the second deck.
This seam is not visible in the unsmoothed version as it is an artifact of the extra facets added to the geometry to make it smooth. It’s something I’ll need to clean up. I haven’t decided exactly how I’m going to do it but I have two options. One is to go in and tweak the geometry so that the two pieces (with the smoothing) line up better. That is actually what I did on the back half of the ship. You can’t see the seam back there. The other is to put surface details, such as pipes, equipment, etc. that run over that area of the ship to mask the region affected. It will probably end up being a combination of those options in the end but that is for later.
The other thing you can’t see in this image is that there is a bit of hull under the lower deck. It actually extends about a half a meter below the deck but it is beveled inward so it doesn’t really show up in the angle of this view. And the bit that is visible (just below the front of the bow and below the parts jutting out a little on the side) are in shadow from the lighting. This extension allows for some machinery and piping beneath the hull and the addition of landing pads as well.
Now that the outer hull is done, it’s time to add the engines.
The Engines
I didn’t really have any ideas for a design on the engines, I just knew they needed to be big and were going to be outboard on either side of the ship. So what I decided to do was use the engines depicted on that map at the end of the last post as a model. I imported that image into Blender to use as a reference and got to work. Here it is again.
I’m going to match the silhouette of those engines at the top and bottom. In this case, I am only going to model one engine and then mirror it to the other side of the ship.
The engine design is fairly simple. It’s mainly a cylinder with a spherical cap at the front and an exhaust cone at the back. Plus some decorations along the side. I made a couple of variations on this image for the model. First, the exhaust cone at the back is symmetrical on my model I might go back and add that curve to it later but for now I left it alone. I also added some tori around the exhaust cone section of the ship reminiscent of the ribbing on current day rocket engines.
Image of the test firing of a Space Shuttle main engine. (click image to link to original on Wikimedia).
I also added one around the connection point between the cylinder and the sphere at the front of the engine (to mask the seam that shows up there when I applied the smoothing 🙂 ).
For those bits of geometry sticking out on the sides, I modeled them as extensions that ran a little more than half way around the engine instead of all the way around.
To connect the engines to the ship, I created some simple swept forward “wings”. All of these pieces were then smoothed and added to the model. With that done, I had the final model of the base hull ready to go.
What’s Next
Now that the base hull is done, it’s time to add the details. That will be the subject of the next post. First up will be those bits of the interior rooms that actually extend beyond the hull. On the side face in these images, the grapple launcher extends a bit out of the bow of the ship. On the other side we have the rocket battery launcher on deck 1 and the sensor array and airlock on deck two.
After that, I need to add in all the bay doors on decks one and three. That will complete the full basic structure of the ship. At this point I’m going to do another 3D print. At the small scale that I used for the first test print, that is all the detail that might show up. Any other smaller details would only show up on a larger print.
Once those final necessary features are added on, I’ll go through and add some other details and features to break up the completely smooth surfaces just a little as well as some recessed landing gear on the bottom of the ship. While the ship doesn’t normally dock or land on planets, it is capable of landing on smaller, very low gravity objects so I need to add that feature in.
So what do you think about the design? Any additional features you think should be included? Let me know in the comments below.
Now that the basic deck plans are done, I want to make a 3D model of the ship. I’m going to be posting this as a series of small articles as I work on the model so you can see the bits and pieces as they happen. Let’s get started.
I’m going to be trying something new for this model. Well, new for me at least. I’m going to attempt to create the model in Blender. I’ve used Blender a bit in the past but only to add materials and textures to an existing model that I created somewhere else. Never to completely create the model from scratch. In the past I’ve done all my models in another program called OpenSCAD. It has some features that I really like (as described in this post on the Arcane Game Lore Blog). But it also is fairly simple and I’d like to have the extra control an options available in Blender. If you want to see some of the other things I’ve created, check out the 3D Models category here on the Expanding Frontier. That includes several posts I’ve made on the subject.
So we’ll see how this goes. I’ve been working through a Blender fundamentals tutorial on Pluralsight and feel comfortable with the basics that I think I’ll need to create this model. If all else fails, I can fall back on OpenSCAD. In truth I’ll be using both of those tools in this project since I can export objects from OpenSCAD into Blender. So for parts and pieces that make more sense to create in OpenSCAD, I’ll be using that.
The Skeleton
For this ship, the first step was to lay out all the interior pieces in their proper size and position. This is what I’m calling the skeleton of the ship. Once that is done, I can build the hull around the interior structure so that it is all properly contained.
This is one of those cases where OpenSCAD is just going to be so much easier to use then Blender. Since we’re talking about adding in basic geometric shapes in very specific, defined positions, the programming interface to OpenSCAD that allows me to specify the position and dimensions of basic shapes like cubes, cylinders, and spheres is exactly what I need.
I work on these models at 1/1000 scale. The default units in OpenSCAD are millimeters so I just use the sizes of the rooms in meters as my values in the functions. This naturally gives me that scale. I can always scale it up (or down) later as needed. For tabletop minis to be used in a tactical game, I typically create the model at 1/3000 scale so I just have to scale the final model by 1/3. For display models, I can scale it to anything I want.
Deck 1
To begin, I just pulled up the deck plan for deck 1 (the lower deck, see this post) to use as a reference. OpenSCAD needs an origin so I selected the center of the grid to be (0,0) in the horizontal directions and the bottom of the deck to be 0 in the vertical direction. I could just have easily selected the lower left of the deck plan but thinking ahead, I knew I would want the origin on the center-line when I got into Blender so I chose appropriately. I then just started adding in boxes to represent the various rooms in the ship.
The cargo bay is 6 meters tall. The little side rooms off of it are not quite as tall ranging from 3-5 meters in height. The forward section of this deck has 3 meter tall rooms. And the elevator shaft connecting this deck to the upper one can be extended 10 meters up to intersect the middle deck. Here’s what things look like after adding in this first deck.
On the left is the OpenSCAD code. On the right is the actual render of the code as a 3D model. The large block sticking up high in the middle is the elevator shaft to the next level up.
Deck 2
On the first level, I added in each room individually. On the middle level, there are a lot of rooms that are adjacent forming large blocks. These areas I just added as single large bits as there was no need to make them all individual. This model I’m creating is just really a sort of wire-frame and will not be part of the final model. It’s more of a guide. The room for the Ion Cannon machinery is 4m tall instead of the standard 3m and is so represented in the model. Here’s the model after this deck has been added.
Those little bits sticking out on the sides are the access tunnels to the engines. Those might very well change as I start modeling but for now, I’m just reproducing what’s on the sketches I drew. Somewhere out there will be engines. Again the bit sticking up is the elevator shaft to the next level.
Deck 3
Finally we need to add in the upper deck. This one has the 6m high runabout bay aft with all the other decks being 3m in height including the round bridge area. Again this deck has a bunch of adjacent rooms that form large blocks. In fact, it only took three shapes to model this: the large block for the runabout bay, a cylinder for the bridge, and an block connecting the two to represent the other rooms. Here’s the model with deck 3 added.
Nothing really exciting here. Although now you can see how the ship sort of tapers toward the middle and the back as you go up to the higher levels.
Weapons
Finally, I wanted to add in the exterior weapons: the Ion Cannon and the Laser Battery. So I went in and modeled those to scale and put them on the ship. Having these exterior elements will help me to get the hull placed properly. With the weapons added, I now have a completed model of the interior of the ship as well as some of the exterior features I need to account for. Here’s the final model.
Making the weapons was kind of fun. I may just export those out to use in Blender. It depends on how hard it is to make the tori around the barrels.
And Done (for now)
Now that the model is done, I can create an actual 3D object and export it for use in Blender. That’s it for this segment of the modelling process. Next time I’ll pull this skeleton model into Blender and start shaping the actual hull around it.
Let me know if you have any questions, comments, or suggestions in the comment section below.
I’ve been working on the antagonist’s ship for the Ghost Ship Osiris module and now have the basic ship design down. This is a larger vessel, used by Thrawl and his scavenger crew to collect materials around the frontier and transport them for sale. It’s relatively well armed and with the larger crew, can even take on smaller vessels if it wants to. I still haven’t come up with an actual name for Thrawl’s specific instance of this ship but am simply calling the general ship type the Scavenger Transport. In this post I’ll talk about how I designed the ship.
It starts by deciding exactly the roll the ship is to play. I knew I wanted it to have a large cargo area, a bigger than normal crew (to provide muscle in scavenging operations), be relatively well armed, and relatively fast for a vessel of its size. The last bit is because in the module, it needs to be on par speed-wise with the PCs’ ship. And a fast, armed ship isn’t too bad for a crew that works a bit on the shady side of the law. Also the ship has to be able to carry a smaller personal runabout for the captain, again needed for plot reasons.
Given that basic plan, I sat down with the FrontierSpace rules and started picking out systems and features of the ship. Now to be honest, I had a bit of behind the scenes help as Bill has created a spreadsheet to use for basic ship design that helps a lot. That tool is not generally available but I believe Bill is working on a more detailed starship generation system that the basics provided in the core rules. In any case, I was able to determine all of the ships systems, components, and statistics using the spreadsheet. Using that information, I created a basic ship characteristic sheet.
There’s no picture of the ship yet as I haven’t completely designed it and don’t know what it looks like. But now that we have the specifications for the ship, we can start working on the deck plans.
Initial sketches
As I do with most of my ship designs, I start with paper and pencil. I have a nice little Moleskin graph paper notebook that I use to sketch out ideas and designs in so I started by drawing a side and top view of roughly what I wanted the ship to look like. It can be seen here in the upper left of this scan of two of the pages from the notebook (Note: on this an all other images in this post, you can click on them to get them at their full resolution).
Scan of two page of my design notebook showing the rough sketch of the ship (top and side views) plus whats on each deck (on the left) and the lower deck sketch on the right
The initial plan was to have three decks, each smaller than the one below forming a somewhat pyramidal or wedge shape. The larger box in the back that spans the upper two levels was to be the hangar for the runabout. The lower level would be taller than the other levels as it contains the cargo bay.
Once I had the basic outline, I started mapping out what I wanted each level to contain. I basically went through all the specifications and figured out which deck the machinery, storage, and hardware would be for each of those systems. You can see that list in the middle of the first page.
The basic breakdown was this:
Level 1 (bottom) – Cargo bay, shuttles and workpods, and many of the ship’s weapons and defenses along with other bulky systems such as life support and power storage.
Level 2 (middle) – Crew quarters and living space, sensors, ion cannon, engineering and tech spaces
Now that I had the basic plan, it was time to start getting into details. I started with the lower, largest level which can be seen on the second page of the scan above. On limitation of working in my notebook (which is 8.25×5 inches, 5 squares to the inch) is that there is only so much space to draw in. I probably should have sketched at 2m/square but did the sketch at 1m/square.
I stared by working out the cargo bay size. Assuming that one CU from the game rules is about a cubic meter, I figured out how big the cargo bay needed to be (see the notation on the left page) give that the bay itself was 6m in height. From there I started adding in the other features that were supposed to be on the ship.
After I finished this deck I compared it to the top view sketch that I created. I realized that the width matched pretty well assuming that the sketch was done at 3m/square except that the detailed sketch was 6m too short. So I made a note about that (on the upper right) to remind me to stretch it out a bit when I finally got down to drawing it. With the lower level done and an approximate scale, I started in on the next two levels.
The middle (left) and upper (right) decks of the Scavenger Transport, to scale with the initial, lower deck
I actually skipped deck 2 to start and did the upper deck first. The reason for this is that I needed to know where the deck access would be so I could connect everything up. I knew I wanted the bridge at the front of the deck spanning the entire width and the runabout hanger at the back. The Laser Battery is actually mounted at the top of the ship so I put it in the center of the deck. I wanted a conference/meeting room off the bridge that was also connected to the captain’s suite. Picking the left side for the conference room determined where the Captain’s Suite would be. That put the elevator on the right and I added in the main computer, some life support space and small toilet off the bridge. This deck was done.
On deck two, I knew I wanted to put the crew cabins and living area in the back of the ship and the working areas center and forward. I actually started this level by putting in the two elevators (one to the deck below and one to the deck above) so I knew how the rest of the design had to work around them.
Next I added in the engineering spaces around where I wanted the engine access tunnels to be. Then came the location of the Ion Cannon (which extends out the front of this deck, not shown) at the front of the deck and then just started filling in details.
Also you might notice that I don’t have the roundabout hanger extending down into deck 2. It would have filled the space where the rec room is and a bit more. That was because as I was doing the sketches, I didn’t look back at my side view (the deck sketches were done several weeks after I made that side view sketch) and I completely forgot that that was my intention. So I decided to just extend it up more instead of down, making the ship even more pyramidal in shape.
Now, if you’re paying attention, you may have noticed that I forgot a fairly important feature that any good spaceship needs. (I probably forgot several but one is definitely going to be added in). Can you spot it? I’ll call it out when I get to drawing up the level it occurs on.
Slightly more detailed drawings
With the sketches done, it is time to start in on final drawings. I do my drawings in Inkscape and if these were going to be the final plans for this ship, they would end up with much more detail that you’ll see here. However, I knew that for this ship at least, I would be sending of the drawings to Bill to create the final version. The reason is that he has a specific style that he has used for ships in FrontierSpace that I can’t quite recreate yet. He had already done the PCs’ ship for this module in that style so I needed him to do the final drawings to match. More on this later. But that means that all I really need to do is get a good working drawing with the spaces mapped out for him to work from.
I like do do these drawings at 50 pixels per meter and 100 dpi. This is mainly due the fact that I started doing maps in Inkscape to digitally recreate some of the original Star Frontiers maps and those maps were all a two squares per inch. Give the preponderance of virtual table tops and the need for maps for those systems, I should probably shift to 70 pixels per square since that seems to be the default for those systems. However, since Inkscape is a vector drawing program, it’s really easy to scale the final map up (by 40%) to reach the desired scale. So I’ll probably stick with what I’m using since the math is easier.
Anyway, I start by laying down a grid. I know how big the ship is going to be so I create an image that is big enough to hold the ship plus 1 square larger on each side. Inkscape has a great extension to draw grids (Extension->Render->Grids->Cartesian Grid) so just use that to make the base grid:
Next I import the scans of my sketches and place them on a layer behind the grid. I have to rotate and scale the sketches so that they match the grid I just created. The sketch for the cargo deck looks like this:
You’ll notice that the sketch doesn’t go all the way to the end of the grid. Remember I said I needed to stretch it out? The final grid is larger than the sketch to accommodate that.
Next we lay in the outer hull. This is done on a separate layer. In the final drawings, the hull will probably have some final thickness and shape to it but for now, It’s just going to enclose the space where the rooms and passages will be. Some may stick out slightly but it provides the overall shape.
Starting a new layer, I turn off the gray fill on the hull (so I can see the sketch, I could also just play with the opacity if I wanted) and start drawing in the rooms and adding doors. Once that is all done, I turn the gray fill on the hull back on (I’ve also turned off the sketch in the background.)
Now, if I were working on the final versions, I’d next go in and add details to all the rooms: consoles, chairs, desks, beds, whatever the room required to show it’s use and function. However, as I’m just sketching out space, this is good enough for now. So we add some labels to indicate what the rooms are:
Now that deck one is finished, it’s time to do deck 2. This is where I realized I was missing something important. Besides the ship bays and the cargo doors, there’s no way to get in and out of the ship. I seem to have forgotten the airlock. Now originally I was going to just run a passage and airlock through the side of the ship near the dining room/galley in the space labeled food storage, but as I started drawing the plans I realized I had more room over by the sensors than I thought based on the sketch and was able to add it in there. The final deck two looks like this:
On this deck, the sensor and airlock extend outside the edges of the hull boundary I drew. This ship isn’t designed for atmospheric flight so that’s not a big deal. I also added in the barrel of the ion cannon I didn’t add in the engine areas, just a small passage headed out to them. The engine compartment will probably actually start right on the edge of this map or just off it. They aren’t all that far away from the ships.
From looking at these plans, you may have noticed that there seems to be an awful lot of life support and food storage space. That is intentional. If you look back at the ship stat sheet, you notice that it has expanded life support. The ship is designed to be able to spend a long time out in space without returning to port so it needs lots of space to store food, air, and water as it doesn’t have a complete recycling system, only a partial one.
Finally, the top deck. This one’s not that interesting, just a bunch of rooms with a small passage connecting them.
Finally we need a cross section view that shows how all these things are placed in relation to each other vertically. As I said before, the cargo bay and the runabout hangar are going to be taller than the rest of the rooms on the ship, each with a 6m tall ceiling (most of the rooms off the cargo bay will be this height as well). The other rooms are going to be 3m in height.
The other decision I had to make was how much space to place between the decks. When I’m building ships for Star Frontiers, I typically use 2m between decks. However, for this ship, I decided that the minimum spacing would be 1m (you’ll see why I say minimum in a minute). That gives room for piping, duct work, machinery and such between the levels. That’s also what that big 2x3m area in the middle of the living quarters section is for, to allow for connections between the lower and upper levels.
With that in mind, I drew a rough side view of the ship and placed the decks, elevator shafts and other bits in there relative positions:
You can see in the front of the ship, there is a lot of space between the lower deck and the deck above. That’s why the 1m was only a minimum. You can also see the laser battery there at the top. The outline of the ship at this point is really rough and I’ll updated it later once I have all the details.
Next Steps
With the basic plans done, I’ve sent them off to Bill to get the final treatment. He was quite excited to see the ship and get to work on the plans so hopefully I’ll have those back relatively soon. I’ll post them when he sends them to me. In case you haven’t seen his deck plan style, here’s the PCs’ ship from the game in Bill’s FrontierSpace style.
I now have the original drawing for this particular ship so I’ll be working in the future to be able to match it for future drawings.
My plan at this point is to start producing a 3D model of the ship. With the basic plans and design done, I can start working on a model that accurately reflects it’s shape. There will be a bit of back and forth between me and Bill as I work on this so that the outline on the deck plans and the model match. Expect the next big post in this series to be on the creation of that model. I’ve been working on brushing up my Blender skills as I’m going to attempt to create the model with that software instead of OpenSCAD which I’ve used for all my models in the past. I like the programmatic aspect of OpenSCAD but Blender provides much more flexibility. However, I might do a hybrid approach like I did with the Assault Scout model I used in the Assault Scout Technical Manual.
So there you go. A new ship. It can actually be used as is in your games if you want. Everything from here on out is details. Let me know if you have any questions, comments, or suggestions in the comment section below.
What follows is player background information for the Death at Rosegard adventure. This is information that it is assumed the PCs would know from living in the Frontier and on the planet Pale where the adventure takes place. It covers a bit bit of history, planetary data, and socio-political information.
The adventure is written as if it takes place after the first sathar incursion into the Frontier but before the Second Sathar War begins. As such, instead of referring to the initial sathar invasion as the First Sathar War as is common in the rule books, the text refers to it as the Great Sathar War since there hasn’t been a second one yet. Expeptions occur when providing GM information designed to help modify the adventure for a different time period.
History
Pale is a new old planet. It was first colonized 176 years before the founding of the United Planetary Federation. It had a medium population before the Great Sathar War that led to the founding of the UPF. At that time Point True had a population of several hundred thousand inhabitants.
During the war every major population center other than Point True, as well as most minor population centers were destroyed by orbital bombardment. Even small villages and farmstead were destroyed by aerial bombing. There is basically just a big crater at the location of every city, town, village, or farm that existed before the invasion. In Point True, the old military base was nuked leaving several large craters and damage to remaining structures but the rest of the city was left relatively intact. There are still signs of the Sathar occupation that can be seen throughout the older portions of Point True.
The sathar were in the process of exporting the inhabitants off-world when the Frontier forces arrived and the sathar were defeated and driven off. Many thousands of the inhabitants of Point True were taken away in sathar ships and have never been heard from since.
After the war, the planet rebounded, partially due to the influx of people coming to help rebuild and partially due to aggressive development by Streel Corporation (known as Streele Mining Corp before the war). At the time of the adventure, about 40-50 years after the invasion, the population has grown to nearly its pre-war level. While the population is predominantly human, there is a significant representation of the other three major Frontier races. The racial breakdown is 46% human, 23% Yazirian, 18% Dralasite, and 13% Vrusk. However, since the war, the population is much more concentrated around Point True. Some portions of the planet are still completely uninhabited.
Planetary Rotation and Timekeeping
Pale orbits its primary, Truane’s Star, in the outer portions of the star’s habitable zone. This causes the average temperature on Pale to be fairly low resulting in cold and severe winters and cool summers. Pale is also a slightly smaller world with a surface gravity of only 0.9 g.
In addition to the cool weather, Pale rotates very slowly on its axis, completing one revolution every 55 standard hours. As such the local population has divided the day into four working time periods:
Day-day: Corresponds to the 13 hours starting roughly 1 hour after sunrise on the planet’s vernal equinox at Point True. This is the typical working time when the sun is up.
Day-night: This corresponds to the next 14 hour period and is typically a rest period although the sun is still shining. Because this rest period occurs during daylight hours, all houses on Pale have windows or curtains allowing rooms to be completely “blacked out” to simulate darkness and nighttime even though the sun is still up.
Night-day: This is the 13 hour work period occurring during the local night. Since this is a time of major work and transportation, all the streets and buildings of Pale are well lit to provide a semblance of daylight during this work period. When seen from orbit, the cities and towns of Pale in the Night-day part of the cycle blaze with light.
Night-night: This is the final 14 hour rest period that occurs during the local night time.
The extra hour is added in to either the Day-day or Night-day period depending on the season, the hour being added to the Day-day in the summer when the days are longer and the Night-day in the winter when the nights are longer.
Typical work periods are 10 hours long during the Day-day and Night-day periods although there are many graveyard and swing shift positions that run during other hours.
Sathar Presence on the Planet
As part of their invasion, the sathar seeded the biosphere around the planet, especially around Point True, with a number of their bio-constructs and attack monsters. Despite efforts to clean up after the war, some of these creatures are still loose on the planet. While quickdeaths and slithers are the most common, there are also a few other creatures that can be encountered when ranging away from the population centers. There are even still some cybodragons (and their descendants) running around although the cyber features are no longer functional due to lack of power. There are bounties for the elimination of these creatures paid for by the Pale government.
In addition to sathar bio-constructs, there are rumored to be some small pockets of sathar still living on the planet. These are remnants from the sathar army that was driven off and mostly destroyed when the planet was liberated. They survive by foraging and by hypnotizing and controlling members of the population to provide food and materials as needed. It is unknown how many of these sathar still survive and how active they are but the numbers range from a few dozen to several hundreds.
While rare, it is still possible to find some sathar technology from the war. It is rarely intact or functioning but any such finds are almost immediately collected by Star Law as soon as the discovery becomes known.
Politics and Corporations
Streel is by far the dominant force on the planet. After the war, Hilo Headrow took over Steele Mining and expanded its operations – first on Pale and then across the Frontier. While Streel doesn’t officially control the government, the government and its policies are fairly favorable towards the company and it is rumored that a majority of the government’s officials are “owned” by Streel in one way or another. Despite the potential negative aspects of this situation, Streel’s touch on the government is surprisingly light-handed given the tactics the company employs elsewhere around the Frontier. Much of the work of the government is environmentally sound and intelligent. Thoughtful practices are put into place that benefit all companies on the planet not just Streel. In fact, the planet is strong on fostering new ideas and companies.
While Streel is the dominant player, Pan Galactic Corporation still has a sizeable presence and even dominates in a few areas on the planet’s surface. In addition, a number of new emerging corporations have offices and operations on the planet. Names like StarPlay, WarTech, TransTravel, and Universal Households are becoming more common.
Miscellaneous GM Notes
The adventure takes place during the events of Laco’s War, the corporate war between Streel and PGC. While that conflict actually has no impact on the adventure, it should be kept in mind when PCs are interacting with outside agents. There is some tension between to two corporations.
Most of the other corporations listed in either the Knight Hawks Campaign Book or Zebulon’s Guide to the Frontier exist at this point although they are not yet considered mega-corps. Only Streel and PGC currently have that status. That said, they are growing and their presence is being felt on Pale.
By the time of the Second Sathar War, the population has rebounded to its pre-war level and is pushing into the heavy population category. If you set the adventure at another time period, adjust the size/number of towns and the population accordingly.
That’s it for the general background. I have a whole other section of background and detail information on the village of Rosegard itself but that will be another post. Feel free to share your thoughts on the planetary background in the comments below.
Okay, now that I have the basic outline for the three projects, it’s time to get started working on them. I will most likely be jumping back and forth between the three projects, although my intention is to put a bit more effort into the Ghost Ship Osiris project simply because that’s one I’m working on with someone else and not just for the Patreon. If you have preferences, let me know in the comments.
My plan initially is to spend at least 15-30 minutes each day working on something related to these three projects. Hopefully that will translate into some sort of significant post each week. In addition, there may be other small posts here and there commenting on what I’m working on. The posts will typically be to present maps or materials created but may also include tutorials or descriptions of processes and how I created stuff.
I haven’t yet decided when I’m going to post but most likely the major posts will occur mid-week. It might be spotty here the first few weeks as I get going but hopefully I’ll build up a rhythm as I get under way. Any minor posts will occur as I think of them. From the Patreon, I’m on the hook for at least one major post (>2000 words) a month. If you took all three of the outline posts together, that would have hit that word count, but those don’t count. That post will probably come in a couple of weeks, toward the end of the month.
Streel is by far the dominant force on the planet. After the war, Hilo Headrow took over Steele Mining and expanded its operations – first on Pale and then across the Frontier. While Streel doesn’t officially control the government, the government and its policies are fairly favorable towards the company and it is rumored that a majority of the government’s officials are “owned” by Streel in one way or another. Despite the potential negative aspects of this situation, Streel’s touch on the government is surprisingly light-handed given the tactics the company employs elsewhere around the Frontier. Much of the work of the government is environmentally sound and intelligent. Thoughtful practices are put into place that benefit all companies on the planet not just Streel. In fact, the planet is strong on fostering new ideas and companies.
Okay, now that I have the basic outline for the three projects, it’s time to get started working on them. I will most likely be jumping back and forth between the three projects, although my intention is to put a bit more effort into the 
Unlock with Patreon