New Republic TIE Fighter

[Bren]

[CRMcNeill]

[Bren]

[CRMcNeill]

[Bren]

[CRMcNeill]

[garhkal]

[shootingwomprats]

I saw in your write-up that the guided missile system is a part of the primary configuration. When the other modular systems are installed, is this removed?
_________________
Don Diestler
Host, Shooting Womp Rats
The D6 Podcast
http://d6holocron.com/shootingwomprats
@swd6podcast, Twitter

[CRMcNeill]

[CRMcNeill]

My original write-up for this fighter was for a post-ROTJ fighter produced by Seinar Fleet Systems and sold to the New Repubic government as a fleet defense fighter. However, a long time ago for the AOL SW-RPG group, I wrote up similar stats that put the ship in the Rebellion era. I have long since lost the write-up (along with several other rule-gems) to the villainous Darth Harddrivecrash, but the general premise (for those who wish to use this ship in the classic era) is:

-While Incom's X-Wing design team's famous defection made a bigger splash, there was also a lesser known series of defections from Seinar Fleet Systems, with many dissatisfied and disillusioned engineers joining the Alliance, sometimes out of shared beliefs and sometimes out of simply having no other safe place to go.

-At the same time, Alliance privateers were waging a war against Imperial shipping, with captured goods and supplies being filtered to the Alliance. Included in the captured goods and supplies were TIE fighters being shipped to fleet units, either as whole units or as components and other spare parts. However, since the Alliance did not field TIE fighters, the captured components were often sold in bulk on the black market, usually at minimal profit.

-The SFS defectors, however, decided to pool their knowledge of the TIE fighter series to design an inexpensive fighter that was a closer fit with Alliance fighter doctrine, constructed from captured TIE fighters and TIE parts. The concept was that this fighter would free up the Alliance's existing long-range fighters from short-range escort work, allowing them to perform the long range superiority, strike and recon missions to which they were better suited.

-The proposal was accepted on a trial basis by Alliance Command, and after the new fighter performed to expectations, it was subsequently given the Alliance's full backing, with all captured TIE components being forwarded to the SFS team for conversion and production into S-Wings.
_________________
"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

[Zarn]

.

.

[DougRed4]

Clever idea, Zarn!

You could even make the title:

Story Factor: TIEme in the Galaxy
_________________
Currently Running: Villains & Vigilantes (a 32-year-old campaign with multiple groups) and D6 Star Wars; mostly on hiatus are Adventures in Middle-earth and Delta Green

[CRMcNeill]

You could also specialize in TIEs in general, rather than one specific TIE model. With specialties, the best bang for your buck is to define the specialty as broadly as possible.

Or perhaps give characters a free specialization based on experience with a specific piece of equipment. Or if not free, maybe point matching of CP when spent to improve skill with something the character uses regularly (specific ship or weapon, or just specific type of ship).
_________________
"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]

I'm re-doing this as part of my stat project. Rather than a New Republic-era ship, the background is re-written to be something that entered Alliance service pre-Endor, as the result of defections of Sienar Fleet Systems personnel to the Alliance.


S-Wing Fleet Escort Starfighter

While the dramatic defection of Incom's X-Wing design team netted the Alliance their signature multi-role fighter model, a less-well-publicized series of defections is proving consequential as well. Over the course of several months, various members of Seinar Fleet Systems' TIE design bureau have come into Alliance service, as well, bringing with them a wealth of data on TIE design.

While the Alliance had little interest in the TIE (primarily because the fragile, short-ranged TIE didn't fit with current Alliance starfighter doctrine), this small group of engineers and designers gravitated together and pooled their respective talents to see if they could change the opinion of High Command.

The team set out to use TIE components to design a fighter that would fill a much needed niche in Alliance Starfighter Command: Fleet Escort. In the Alliance Fleet, this mission was performed by a mix of Clone Wars-era V-Wings and more modern long-range fighters. What was needed was a new fighter that could free up the long-range starfighters for strike missions, as well as supplementing and replacing the aging V-Wings. Since the standard Imperial TIE was already designed as a Fleet Escort fighter, the design team took that basic design and modified it for improved durability and versatility. They also incorporated a new wing panel design that greatly improved visibility and allowed the wing to fold for independent landings. They also managed to fit a small hyperdrive into an extension mounted to the rear of the cockpit, and include a life support system so that the pilot could wear a standard Alliance flight suit and helmet.

Alliance Fleet Command proved receptive to the idea for a variety of reasons, not least that they had a surplus of TIE spare parts in storage thanks to the Privateer program. In addition, former Imperial pilots who had defected to Alliance service were often already trained in TIEs, and could easily operate S-Wings with little or no training.

While production is slow, the S-Wing is entering service with the Alliance Fleet as quickly as possible. It's generally assigned in squadron-sized lots rather than individual ships, and while S-Wings and V-Wings may be based on the same ships, they are almost never found together in mixed squadrons.

Craft: FreiTek's A-TIE "S-Wing"
Type: Multi-Role Short-Range Starfighter
Scale: Starship (+6D)
Length: 6.2 meters
Skill: Starship Piloting: S-Wing
Crew: 1
Crew Skill:
Astrogation 3D
Gunnery 4D
Piloting 4D+1
Shields 4D
Sensors 4D
Cargo Capacity: 50 kilograms
Consumables: 2 days
Hyperdrive Multiplier: x2
Nav Computer: Limited (2 Jumps)
Maneuverability: 3D
Space: 8 (4D)
Atmosphere: 365; 1,050kph
Hull: 3D
Shields: 1D
Sensors:
Passive 20/0D
Scan 40/1D
Search 60/2D
Focus 3/3D
Weapons:
4 Laser Cannon (Fire-Linked)
Fire Arc: Front
Skill: Starship Gunnery
Fire Control: 2D
Range:
--Space: 1-3/12/25
--Orbital: 2km-6km/24km/50km
--Atmosphere: 100m-300m/1.2km/2.5km
Damage: 6D
Special Equipment: Modular Mission Packs:

Although the S-Wing uses the same basic fuselage as the TIE/ln, it lacks the older fighter's ventral heavy blaster cannon. This left extra space available for the installation of modular packs, each tailored to allow the S-Wing to perform specific missions. The modular packs can be swapped out and replaced with a different pack in less than 30 minutes (Easy Starfighter Repair, requiring 20+2D minutes).

RECON / FIRE CONTROL
Description: This pack augments S-Wing's existing sensors as follows:
Sensors:
Passive: 30/1D+2
Scan: 60/2D+1
Search: 90/3D+2
Focus: 6/5D
Target Designator:
-To Designate: Pilot must make an Easy Sensor Focus roll. The sensor lock can be dodged as if it were an attack.
-Bonus: +2D to one Fire Control of one friendly (or group of weapons, if properly coordinated). Can not stack bonuses by using multiple Target Designators.

ASSAULT
Description: This pack equips the S-Wing with a 4-round concussion missile launcher, usually loaded with guided missiles, which makes the S-Wing much more formidable in anti-starfighter combat.
Weapons:
1 Light Warhead Launcher
Fire Arc: Front
Skill: Starship Gunnery
Rate of Fire: 1
All Other Stats vary by Weapon Type
Capacity: 4. May select Light Missiles & Rockets from this list, depending on Availability.

INTERCEPTOR
Description: This pack equips the S-Wing with an auto-blaster. While underpowered, the cannon is highly accurate and is extremely useful for shooting down missiles and torpedoes, as well as engaging speeder craft and other small targets.
Weapons:
Autoblaster Cannon
Fire Arc: Front
Skill: Starship Gunnery
Fire Control: 3D
Range:
--Space: 1-8/25/40
--Orbital: 2km-16km/50km/80km
--Atmosphere: 100m-800m/2.5km/4km
Rate of Fire: 2D Auto-Fire
Damage: 3D

PURSUIT
Description: This pack equips the S-Wing with a dual ion cannon, allowing it to disable vessels for capture.
Weapons:
Dual Ion Cannon
Fire Arc: Front
Skill: Starship Gunnery
Fire Control: 3D
Range:
--Space: 1-3/7/16
--Atmosphere: 100m/300m/700m/1.6km
Damage: 4D (ionization)

RECOVERY
Description: This pack equips the S-Wing with a short-range grappling cable system that allows it to tow disabled ships (featured in Vision of the Future).
Weapons:
Grappling Cable Launcher
Fire Arc: Front
Skill: Starship Gunnery
Fire Control: 2D
Range:
--Space: 0-1/2/3
--Atmosphere: 0m-100m/200m/300m
Effect: On a successful hit, the S-Wing is linked to the target starship by a high-strength cable and fusion disk. The S-Wing can tow the cabled starship at the cost of reduced performance. For every 1D of Hull on the target, the S-Wing's Maneuverability is reduced 1D and its Speed by 2. Multiple S-Wings can grapple the target (each additional S-Wing reduces the penalty by one level, but increases Starfighter Piloting Difficulty levels by one). This can only be used against ships that are completely disabled, as the cable is not strong enough to be the rope in a tug-of-war if the targeted vessel restarts its engines and tries to escape.

FERRY
Description: This pack doubles the S-Wing's Consumables, allowing it to make longer flights. It is almost never used for combat missions' instead, it allows the S-Wing to self-deploy from one operational zone to another with the need for a transport vessel.
Consumables: 4 days

House Rule Notes:

SHIELD & SHIELD CONTROL: 1D @ 1D
VELOCITY MODIFIER: 2D Flight

Visual Differences from TIE/ln:

-Interceptor-style rectangular notches cut into leading edges of both wing panels, with TIE/ln laser cannon mounted on the gap's upper and lower edges, mated with Interceptor type targeting sensors at the base (on the wing root)

-Shield projectors mounted in hemispherical caps on the outside ends of the wing roots.

-Hyperdrive mounted in casing on rear of cockpit.

-On landing, the upper and lower halves of the wing panels fold outward 90 degrees and landing gear extends from the underside of the wing roots
_________________
"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