As noted earlier, due to the difficulty of transporting very large monitors between systems, it is often easier to construct them in-system using whatever materials and technologies are available. This makes planetoid hulls a popular choice for systems with planetoid belts.
T20 Fighting Ships (2003) suggests another approach: “Many monitors are also constructed from obsolete capital ships that have been sold by the Imperial Navy. Take an out of date cruiser, strip the fuel tanks and jump drives out of them and you have much more room to fit in weaponry and the like. Many governments take this route instead of building their own from scratch, and they have their uses.”
This is a pretty interesting idea, and would certainly be applicable to Magyar sector, which lags behind the rest of the Imperium in technology level. The Tiananmen-class battleship, introduced in T20 Fighting Ships, is a good candidate for this treatment. A 350,000-ton, TL13 Imperial ship in wide use during the Rim War, this design is large and formidable enough to justify a reclamation project—and the tech level is within reach of several high population worlds.
As far as I know there are no published designs of such a large monitor, though they are mentioned in canon. T20FS notes that “The Imperial Navy has at least one squadron of Supermonitors, massing upwards of 750,000 tons, deployed to defend Capital, but as a rule very large ‘Battle’ monitors are uncommon.”
Curious, I broke out Mongoose Traveller 2e High Guard and converted the T20 Tiananmen. Then I undertook a refit using the magic of spreadsheets, removing the jump drive and fuel tanks. The results look pretty impressive: such a battle monitor would be a serious deterrent to would-be invaders.
The Tiananmen-class in Magyar
The Tiananmen-class battleship originated in Gateway sector in the early 900s, but the design quickly spread throughout the Imperium and was still in wide use when the Solomani Rim War broke out. Several megacorporations won contracts to produce new Tiananmens in significant numbers for the war.
When Imperial Admiral Miiri Elixabeth Kemper launched her invasion of Magyar sector, she commanded two units anchored by Tiananmens: the 2677th and 2542nd Colonial BatRons. Both squadrons had been raised by individual worlds in the Domain of Ilelish and partially subsidized by the Imperium as part of a wartime program to encourage shipbuilding. The resulting units were then seconded to the Imperial Navy and deployed as auxiliaries.
Two Tiananmens from these Rim War forces are currently in service in Magyar, though in very different roles. The Bastion of Ley is the flagship of the Anise (Magyar 2904 A8419B7–E) navy, while the Shanape, transformed into a battle monitor, leads the system defense force of Gerwalk (Magyar 2631 C100941-D). Both Gerwalk and Anise are fortress worlds: Imperial strategists expect such worlds to form vital islands of resistance in the event of a Solomani Confederation invasion.
The Bastion of Ley
The Bastion of Ley, usually just called the Bastion, is a Tiananmen-class battleship named for the world in Ley sector now called Olegansimen (Ley 2227 B6489A6-C). The planetary navy of Kees (Zarushagar 2937) commissioned the Bastion, which was laid down at the Ling Standard yards on 253-993 with her first flight on 100-998.
After an abbreviated shakedown, the battleship was assigned to the 2677th Colonial BatRon and dispatched to reinforce Daibei sector on 192-998. Midway through 999 the 2677th was transferred to Diaspora, where the Imperial Navy had begun steadily advancing rimward toward the heart of the Confederation. The 2677th initially garrisoned captured worlds, but as the pace of the offensive picked up, the Bastion found itself brought closer and closer to the front lines. The 2677th fought a difficult action at Eberly (Diaspora 2130) and was then was part of the bloody but decisive assault on Alki (Diaspora 1136), which opened up a line to the Solomani Rim.
However, instead of following Admiral Adair’s drive toward the Vegan District, the 2677th was assigned to the 9th Provisional Battle Fleet, a penetration fleet intended to raid deep into enemy territory. The 9th pivoted into Ultima subsector and besieged Darrukesh (Solomani Rim 0106). While most of the 9th Fleet pressed into Magyar sector, the 2677th Colonial BatRon was left behind to garrison Darrukesh for several months until reinforcements arrived. The 2677th then rejoined the fleet at Asrow (Magyar 3006).
The 2677th fought with great distinction at the First Battle of Fornorb, when the Confederation surprised the Imperials and forced a rout. There the Bastion suffered serious damage screening Timarin battle riders of the 4932nd Colonial BatRon that were trying remount their battle tender. Two of the Bastion’s sister Tiananmens were lost during the battle, one with all hands aboard. The 2677th was withdrawn to Anise for repairs and reinforcements; the Bastion was still in drydock when the Armistice was declared.
Following the war the Navy purchased the Bastion from Kees and assigned the battleship to the Gadarur District occupation force. In 1055 the battleship was purchased by the Anise Navy, where it served until 1070 before undergoing a major overhaul. In 1077 the Bastion was recommissioned and today is the flagship of the Anise navy and anchor of the Anise Colonial BatRon. Anise possesses one of the most powerful colonial navies in the subsector. The formidable Mirama Naval Base is directly owned and operated by Anise, but also berths major elements of the Imperial 20th Subsector Fleet, which lacks a base in Anise subsector. The colonial and Imperial navies drill together extensively.
Hull Points 256,667
Crew Captain, Officer x191, Pilot x3, Astrogator x1, Fighter Crew x194, Engineer x670, Maintenance x233, Medic x16, Gunner x682, Administrator x117
Maintenance Cost MCr16.260 per month
Purchase Cost MCr195,115
| TL13 | Tons | Costs (MCr) | |
|---|---|---|---|
| Hull | 350,000 tons, Streamlined | - | 21,000 |
| Reinforced | - | 10,500 | |
| Armor | Crystaliron, Armor:10 | 43,750 | 15,750 |
| Radiation Shielding | - | 8,750 | |
| M-Drive | Thrust 5 | 17,500 | 35,000 |
| J-Drive | Jump 4 | 35,005 | 52,508 |
| Power Plant | Fusion (TL12), Power 267,000 | 17,800 | 17,800 |
| Fuel Tanks | 4 weeks operation, J-4 | 141,780 | - |
| Bridge | 60 | 1,750 | |
| Computer | Core 80/fib | - | 143 |
| Sensors | Improved (Distributed Arrays) | 9 | 13 |
| Countermeasures Suite | 2 | 4 | |
| Enhanced Signal Processing | 2 | 8 | |
| Weapons | Spinal - meson (TL13) | 40,500 | 13,200 |
| Medium Bay (particle beam) x100 | 10,000 | 4,000 | |
| Small Bay (missile) x200 | 10,000 | 2,400 | |
| Double Turret (beam laser/sandcaster) x400 | 400 | 500 | |
| Point Defense Battery (Type II) x20 | 400 | 200 | |
| Ammunition | Missile Storage (8,640 missiles) | 720 | - |
| Sandcaster Barrels (4,320 barrels) | 216 | - | |
| Screens | Meson Screen x10 | 100 | 200 |
| Nuclear Damper x10 | 100 | 100 | |
| Armored Bulkheads | Bridge | 6 | 1 |
| Command Bridge | 8 | 2 | |
| Maneuver Drive | 1,750 | 350 | |
| Meson Screen | 10 | 2 | |
| Nuclear Damper | 10 | 2 | |
| Power Plant | 1,780 | 356 | |
| Sensors | 1 | - | |
| Craft | Full Hangar | 10,000 | 2,000 |
| Heavy Fighter (50 tons) x74 | - | 3,162 | |
| Modular Cutter (50 tons) x20 | - | 206 | |
| Shuttle (95 tons) x2 | - | 46 | |
| Systems | Briefing Room x10 | 40 | 5 |
| Command Bridge | 80 | 2,625 | |
| Fuel Processor (141,780 tons per day) | 7,089 | 354 | |
| Launch Tubes (50 tons) | 500 | 750 | |
| Medical Bay x6 | 24 | 12 | |
| Repair Drones | 3,500 | 700 | |
| Staterooms | Standard x1,154 | 4,616 | 577 |
| High x1 | 6 | 1 | |
| Software | Maneuver/0 | - | - |
| Intellect | - | 1 | |
| Evade/3 | - | 3 | |
| Jump Control/4 | - | 0.4 | |
| Fire Control/5 | - | 10 | |
| Auto Repair/2 | - | 10 | |
| Library | - | - | |
| Common Areas | 1,156 | 116 | |
| Cargo | 1,080 | - |
The Shanape
The Shanape, named after a high-population world in Ley sector, was built by Ling Standard for the Arlumer (Ilelish 0510) navy. The ship was laid down on 006-993 and its first flight was 227-999. The Shanape was sent to Diaspora sector as part of the 2542nd Colonial BatRon on 355-999.
In 1000 the 2542nd was transferred to the Imperial 4th Provisional Battle Fleet, which was commanded by Admiral Kemper herself. The Shanape followed Kemper’s drive through Ultima subsector, seeing its first action at Darrukesh (Solomani Rim 0106). The battleship was held back from the Battle of Idu, but then supported the 9th’s first rates in a major engagement at Austa (Magyar 2503), where the Shanape found itself swarmed by SDBs after two Imperial CruRons were shattered in the assault on the mainworld. The 2542nd held fast, buying time for Kemper’s second task force to enter the fray. The battleship then followed other elements of the 9th in lightning raids on Milenky (Magyar 2603), Amunet (Magyar 2507), Volund (Magyar 2607), Nosret (Magyar 2807), and Bilox (Magyar 2905).
Following the War the Shanape was transferred to the Imperial occupation forces for Fugue District, headquartered at Asorret (Magyar 2923). In 1051 the Shanape was placed in ordinary. In 1076 the battleship was set to be scrapped when it was sold to Gerwalk (Magyar 2631). Gerwalk supports its own colonial navy with a base on Pertinax (F200672-8); elements include the 1438th Colonial BatRon and the 2056th Colonial CruRon. The Shanape then underwent a major refit: the jump drive, fuel tanks, and power plant were removed and a new TL13 meson accelerator spinal, the largest available, was installed. The resulting battle monitor was recommissioned on 330-1083. Sometimes affectionately called the Tiananmonitor, the Shanape is a prominent and formidable presence in the Gerwalk system.
Hull Points 256,667
Crew Captain, Officer x298, Pilot x3, Fighter Crew x600, Engineer x411, Maintenance x233, Medic x25, Gunner x1,598, Administrator x117
Maintenance Cost MCr17.542 per month
Purchase Cost MCr210,505
| TL13 | Tons | Costs (MCr) | |
|---|---|---|---|
| Hull | 350,000 tons, Streamlined | - | 21,000 |
| Reinforced | - | 10,500 | |
| Armor | Crystaliron, Armor:13 | 56,875 | 20,475 |
| Radiation Shielding | - | 8,750 | |
| M-Drive | Thrust 6 | 21,000 | 42,000 |
| Power Plant | Fusion (TL12), Power 332,000 | 22,133 | 22,133 |
| Fuel Tanks | 16 weeks operation | 8,856 | - |
| Bridge | 60 | 1,750 | |
| Computer | Core 80/fib | - | 143 |
| Sensors | Improved (Distributed Arrays) | 9 | 13 |
| Countermeasures Suite | 2 | 4 | |
| Enhanced Signal Processing | 2 | 8 | |
| Weapons | Spinal - meson (TL13) | 67,500 | 22,000 |
| Large Bay (particle beam) x160 | 80,000 | 19,200 | |
| Medium Bay (missile) x400 | 40,000 | 16,000 | |
| Double Turret (beam laser/sandcaster) x600 | 600 | 750 | |
| Point Defense Battery (Type II) x50 | 1,000 | 500 | |
| Ammunition | Missile Storage (8,640 missiles) | 720 | - |
| Sandcaster Barrels (12,960 barrels) | 648 | - | |
| Screens | Meson Screen x10 | 100 | 200 |
| Nuclear Damper x10 | 100 | 100 | |
| Armored Bulkheads | Bridge | 6 | 1 |
| Command Bridge | 8 | 2 | |
| Fuel Tanks | 886 | 177 | |
| Maneuver Drive | 2,100 | 420 | |
| Meson Screen | 10 | 2 | |
| Nuclear Damper | 10 | 2 | |
| Power Plant | 2,213 | 443 | |
| Sensors | 1 | - | |
| Craft | Full Hangar | 30,000 | 6,000 |
| Heavy Fighter (50 tons) x274 | - | 11,708 | |
| Modular Cutter (50 tons) x20 | - | 206 | |
| Shuttle (95 tons) x2 | - | 46 | |
| Systems | Briefing Room x10 | 40 | 5 |
| Command Bridge | 80 | 2,625 | |
| Fuel Processor (8,860 tons per day) | 443 | 22 | |
| Launch Tubes (50 ton) | 1,000 | 1,500 | |
| Medical Bay x9 | 36 | 18 | |
| Repair Drones | 3,500 | 700 | |
| Staterooms | Standard x1,793 | 7,172 | 897 |
| High x1 | 6 | 1 | |
| Software | Maneuver/0 | - | - |
| Intellect | - | 1 | |
| Evade/3 | - | 3 | |
| Fire Control/5 | - | 10 | |
| Auto Repair/2 | - | 10 | |
| Library | - | - | |
| Common Areas | 1,795 | 180 | |
| Cargo | 1,080 | - |
Copyright Information
The Traveller game in all forms is owned by Far Future Enterprises. Copyright © 1977 – 2021 Far Future Enterprises. Traveller is a registered trademark of Far Future Enterprises. Far Future permits web sites and fanzines for this game, provided it contains this notice, that Far Future is notified, and subject to a withdrawal of permission on 90 days notice. The contents of this site are for personal, non-commercial use only. Any use of Far Future Enterprises’s copyrighted material or trademarks anywhere on this web site and its files should not be viewed as a challenge to those copyrights or trademarks. In addition, any program/articles/file on this site cannot be republished or distributed without the consent of the author who contributed it.
Materials produced by Digest Group Publications (DGP) are copyright © Roger Sanger. Any use of Digest Group Publications’ copyrighted material or trademarks anywhere on this Web site and its files should not be viewed as a challenge to those copyrights. Usage is intended to follow the guidelines announced by Roger Sanger on the Traveller Mailing List for preserving the overall Traveller milieu.
No comments:
Post a Comment