PartiCard class Battle Rider
| PartiCard class Battle Rider | |
|---|---|
| Type: BRV Very Light Battle Rider | |
| Category | ACS |
| Size | 100 Tons |
| Hull Configuration | Planetoid Hull |
| Streamlining | Unstreamlined Hull |
| Tech Level | TL–12 |
| Engineering | |
| Computer | Model/4/bis |
| Jump | J- |
| Maneuver | 6 G |
| Fuel Treatment | none |
| Armaments | |
| Hardpoints | 1 |
| Offensive | 1 particle beam bay |
| Accommodations | |
| Staterooms | |
| Personnel | |
| Crew | 0 |
| High/Mid Passengers | |
| Payload | |
| Cargo | 4.5 Tons |
| Fuel tank | 1 Tons |
| Carried craft | repair drones |
| Construction | |
| Construction Time | 1.5 Months |
| Origin | Third Imperium |
| Manufacturer | Zhunastu Shipbuilding |
| Year Operational | 257 |
| Price | |
| Cost | MCr87.4 |
| Statistics | |
| Quick Ship Profile | BRV-AU60 |
| Universal Ship Profile | VTE-C1806U-ER |
| Images | |
| Blueprint | Yes |
| Illustration | No |
| Source | |
| Also see | Battle Rider, PartiDeck class Battle Tender |
| Canon | Unpublished, fan design |
| Designer | Adrian Tymes |
| Era | Vargr Campaigns |
| Reference | Fan: Adrian Tymes |
| Designed with Mongoose Traveller High Guard rules, but portable to other versions | |
The PartiCard class Battle Rider is a military battle rider and a drone warship.
Description[edit]
The PartiCard class Battle Rider is a small drone built around a particle beam bay weapon. Its purpose is to destroy Adventure Class Ships from a distance, preferably further away than they can fire back. Its main weakness is missiles, as it lacks any defenses of its own; four PartiCards are intended to operate with a PartiDeck class Battle Tender that can provide point defense and electronic warfare. It is not intended to tangle with Battle Class Ships or larger, and will often prove ineffective in such a battle.
It can also serve as a system defense boat for light defense against individual raiders or small raiding fleets, simply floating in weapon's range of but well away from some point of interest. Any approaching party can usually be outrun; anyone changing course to intercept without very good reason (usually backed up by stand-down orders from the drone's commander) can be assumed hostile and destroyed from a distance.
Image Repository[edit]
Not available at this time.
General Description & Deck Plans[edit]
- Deck Plans for a PartiCard and its PartiDeck class Battle Tender.
Basic Ship Characteristics[edit]
Following the Imperial Navy and IISS Universal Ship Profile and data, additional information is presented in the format shown here. [1]
| Basic Ship Characteristics [2] | ||
|---|---|---|
| No. | Category | Remarks |
| 1. | Tonnage / Hull | Tonnage: 100 tons (standard). 1350 cubic meters. Unstreamlined Planetoid Hull.
|
| 2. | Crew | Crew: None. Virtual Pilot and Gunner provided by software. |
| 3. | Performance | Acceleration: 6-G maneuver drive installed.
|
| 4. | Electronics | Model/4/bis ship computer. |
| 5. | Hardpoints | 1 hardpoint. |
| 6. | Armament | 1 particle beam bay weapon. |
| 7. | Defenses | None. Designed to be defended by other spacecraft. |
| 8. | Craft | Repair drones. No vacc suits or Rescue Balls usually carried, as no crew is normally aboard. |
| 9. | Fuel Treatment | It is not equipped with a fuel purification plant or fuel scoops. |
| 10. | Cost | MCr87.4 (no architect's fees, those having long since been paid). MCr78.66 in quantity. |
| 11. | Construction Time | 1.5 months standard, 1 in quantity. |
| 12. | Remarks | A simple, automated dealer of death from long range. |
History & Background (Dossier)[edit]
Originally conceived of as the "teeth" for PartiDeck class Battle Tenders (see that article for their origin) - able to go forth, engage an enemy, and either destroy it or die for low cost should the enemy prove unexpectedly formidable - PartiCards have found a second life as simple automated system defense boats. They provide just enough defense to take out the occasional pirate while being easily blown away by any true battle fleet, assuming one does not possess its shutdown codes. Thus, it is often given in this role to systems that need light defenses but might grow independent if given a measure of true power. Many such systems are unable to provide for the maintenance of even a TL-12 drone; supplying this maintenance can be another leash on those systems' aspirations.
Class Naming Practice/s & Peculiarities[edit]
Ship Interior Details: Being a drone, there is not much of an interior to speak of, save for the cargo bay in the rear which is typically loaded with spare parts for the repair drones to make field repairs with - though any PartiCard that is taking damage is usually fleeing, as the computer can not handle combat and repairs at the same time. To save on costs, the interior does not even have artificial gravity.
PartiCards are named for their host installation, be it a PartiDeck, space station, or whatever. For instance, the PartiCards on the PartiDeck named Hoyle are named Hoyle 1 through Hoyle 4.
Selected Variant Types & Classes[edit]
3 Representative Very-Light-Battle-Rider (BRV) Classes[edit]
References[edit]
| This article has metadata. |
|
This ship was designed using Mongoose 2nd ship design rules.
|
- Author: Adrian Tymes
- ↑ Timothy B. Brown. Fighting Ships (Game Designers Workshop, 1981), 10.
- ↑ Timothy B. Brown. Fighting Ships (Game Designers Workshop, 1981), 10.