Hyperspace & Astrogation Project

Whill · Posted: Fri Jul 10, 2020 9:14 pm Post subject:

Sure.

CRMcNeill · Posted: Sun Jul 12, 2020 11:59 am Post subject:

Stumbled across this here.

The Bissler · Commander Joined: 08 Jun 2016 Posts: 260

interesting thread!

I've had a few issues with Hyperdrive in the last few weeks, primarily to do with the adventure outline for Assault on Repair Station M13 from the Classic Campaigns supplement. In the outline, it says that there are TIEs in the Repair Station which fly off to deal with another Rebel attack in a neighbouring system.

This was problematic to me, partly because I know from game mechanics that TIEs don't have hyperdrive, but even more because Obi-Wan specifically talks about it in Episode IV (on the approach to the Death Star). So, instead, I decided that the TIEs would be scrambled to an orbiting space station that the Rebel NPCs would now attack. Problem fixed.

...except my PCs thought it would be a wonderful idea to attack the Repair Station before the Rebels attacked the orbiting space station. Now the PCs have to deal with the TIEs scrambling from the Repair Station on the ground AND those from the orbiting Space Platform. They are hopelessly outnumbered. Half of the team are on a YT-1300 providing an air assault, and the other half are running amok inside the installation. This is where it was left last week.

The team on the YT-1300 have been messaging me today asking if they can override the safety protocols on the hyperdrive so they can make the jump to hyperspace while in the planet's atmosphere - before the TIE reinforcements arrive. I know that this has precedent in Rogue One (the one moment that irked me in that film).

So, I've ruled that if they disable the hyperdrive protocols (Easy Languages to communicate with the ship's computer & Moderate Computer Programming roll to do so), then they can attempt a Astrogation Roll to try an inside atmosphere hyperdrive jump - but that the difficulty will be Heroic and so will likely require a Force Point to successfully achieve.

I'm hoping it's a compromise that will deter future reliance on this device to escape ship to ship combat.

CRMcNeill · Posted: Tue Jul 14, 2020 7:36 pm Post subject:

I have just the thing you're looking for.
_________________
"No set of rules can cover every situation. It's expected that you will make up new rules to suit the needs of your game." - The Star Wars Roleplaying Game, 2R&E, pg. 69, WEG, 1996.

The CRMcNeill Stat/Rule Index

The Bissler · Commander Joined: 08 Jun 2016 Posts: 260

CRMcNeill · Posted: Sat Dec 31, 2022 9:36 pm Post subject:

So, this has been on the back burner for a while, but I've been putting some thought into it re: the High-End / Low-End Navcomputer topic. As part of my stat upgrade, I've added the option of Shield Control Dice (as in, Fire Control, but for Shields). This in turn got me thinking of other ship systems that might benefit from "Control" dice, and then I remembered that I had already suggested it in the above link.

However, I've run into a small snag in the sense that adding Astrogation Control Dice to a stat also necessitates putting work in on the Hyperdrive project. Now, I had elsewhere suggested basing Astrogation Difficulty on how well traveled a route is, but the more I think about it, the more I think that the length of the jump itself also needs to be taken into account. As in, all other things being equal, a route that is 12 hours long should be more difficult to calculate than a route that is 4 hours long.

So, what I'm thinking is having the Base Astrogation Difficulty for a hyperspace jump be equal to the jump's hours in length, modified by the following multipliers for how well-traveled the route is:

Ships will then be assigned Astrogation Control dice (stacks with the crew's Astrogation skill on the Crew Skills section).

I'm also strongly considering throwing out the Maximum Jumps on the Limited Navcomputers and simply giving them penalties, like -1D for the X-Wing's 10-jump Limit, and -2D or 3D for the 2-jump limit on fighters like the A-Wing and B-Wing. On the other end of the spectrum, large ships like Star Destroyers and the like would be rated in the 3D or 4D range, representing their much greater computing and data storage capacity.

Nothing concrete at the moment, but I've been chewing on this for a while and wanted to get it written down.
_________________
"No set of rules can cover every situation. It's expected that you will make up new rules to suit the needs of your game." - The Star Wars Roleplaying Game, 2R&E, pg. 69, WEG, 1996.

The CRMcNeill Stat/Rule Index

Whill · Posted: Sat Dec 31, 2022 11:14 pm Post subject:

What problems with RAW do these house rules address?
_________________
*
Site Map
Forum Guidelines
Registration/Log-In Help
The Rancor Pit Library
Star Wars D6 Damage

CRMcNeill · Posted: Sat Dec 31, 2022 11:26 pm Post subject:

CRMcNeill · Posted: Sun Jan 01, 2023 7:16 pm Post subject:

Naturally, this is just a first draft, and the equation can be modified if testing or gameplay determines that the resulting Difficulty numbers are too high or too low.

EDIT: A less math-intensive approach would be to have jumps be one Difficulty level for every day of duration.

Duration in Days = Difficulty

_________________
"No set of rules can cover every situation. It's expected that you will make up new rules to suit the needs of your game." - The Star Wars Roleplaying Game, 2R&E, pg. 69, WEG, 1996.

The CRMcNeill Stat/Rule Index

CRMcNeill · Posted: Sun Jan 08, 2023 1:18 am Post subject:

A thought re what I posted here:

One of my biggest complaints about starfighters using hyperdrive rings is that, once the fighter has disconnected from the ring, the ring itself is vulnerable to attack, and the fighter is effectively tied to a single egress point that they have to return to (the ring's coordinates) in order to escape the system.

But what if the fighters in questioned are equipped with a smaller, slower hyperdrive in the x10 or x12 range, and use the hyperdrive booster ring to augment the much slower integrated hyperdrive? A fighter could easily drop out of hyperspace somewhere well outside sensor range of his destination, then use the slower integrated drive to enter the system itself. That way, he'll still have tactical freedom and mobility within the target system, and his hyperdrive booster ring will be a needle in a haystack for anyone other than the fighter pilot himself (since he's the one who parked it in the first place).

I'm thinking it also makes more sense as an interim technological step to have starfighter hyperdrives go "no hyperdrive" -> "slow internal hyperdrive supplemented by booster ring" -> "full capability internal hyperdrive" than it does for them to make the major technological leap that skips the middle step.

Anyway, that's my thought for the night.
_________________
"No set of rules can cover every situation. It's expected that you will make up new rules to suit the needs of your game." - The Star Wars Roleplaying Game, 2R&E, pg. 69, WEG, 1996.

The CRMcNeill Stat/Rule Index

	The Rancor Pit Forum Index -> House Rules	All times are GMT - 4 Hours Goto page Previous 1, 2, 3
Page 3 of 3