Klingon TMP D-8C Command Cruiser
The Klingon D8C command cruiser
explanation from Federation Spaceflight Chronology - The Klingon Empire by Richard E. Mandel:
"BAT’LETH CLASS
DATE FIRST OBSERVED BY FEDERATION: 2275
During the Four Years War the Klingon battleship Bat’leth was heavily damaged in a fierce fight with Federation starships. By the time it managed to disengage and escape its command boom was so badly shot up as to be unsalvageable. The House that owned it tried to get another B-1 boom as a replacement, but none were available due to the strains of the war on the Klingon economy. Its owner, not wanting to lose the power and prestige that came with its only capital ship, subsequently refitted it with a D-6 command boom and sent it back into the fray. This had two immediate effects. First, it made the Bat’leth the most easily recognizable ship in the whole of the Klingon fleet at the time. Second, its “pocket battleship” configuration would go on to inspire two new Klingon starship classes, the massive C-series dreadnoughts and this one.
The D-8C is a modernized version of the old Bat’leth configuration fitted with the latest in Klingon starship technology. Although its appearance is similar to that of its unique predecessor, it is in fact made up entirely of D-8 K’t’inga class battlecruiser technology. It still suffers the same warp field deficiencies as its Jul’kar predecssor, limiting its top potential speed; however, the Klingons have found an interesting way to make up for this deficiency. The centerline engine of a D-8C is normally not used for propulsion except in emergency situations. Instead, its main purpose appears to be to keep the D-8C’s shields at full power so it will remain protected while on attack. This makes the D-8C an extremely dangerous opponent for all but the most powerful of Star Fleet’s current starships.
Bat’leth class command cruisers normally serve as the lead ship in a standard three-ship Klingon “wolf pack” squadron configuration. In these cases it is almost always accompanied by two K’t’inga class battlecruisers. On at least one occasion, however, one of the wing ships turned out to be an uprated D-7V carrier and on another a Bat’leth was accompanied by two D-6D drone cruisers. Rarely will a Bat’leth be encountered by itself due to the value placed on these “pocket battleships” by the lesser Houses."
User submitted review from Terradyhne
Title :Klingon TMP D-8C Command Cruiser
Filename :Klingon D8C Bat'Leth Terradyhne.zip
Date :28/02/2008
Author :Terradyhne
Email :Terradyhne@gmx.de
Homepage :http://www.terradyhne-yards.de
Credits :Model Design: ???
Model Concept: Terradyhne
Textures: Terradyhne
Conversion: Max 3
Description of the Modification:
-------------------------------
Klingon TMP D-8C Command Cruiser
******
email me at Terradyhne@gmx.de if you have any questions.
Copyright and Distribution Permissions
--------------------------------------
THIS PATCH IS NOT MADE, DISTRIBUTED, OR SUPPORTED BY INTERPLAY TM & (C) INTERPLAY & TALDREN & Activision & PARAMOUNT PICTURES.
Copyright notices:
Star Trek, Star Fleet Command,Star Trek:Armada 1/2, Star Trek: Deep Space Nine, Star Trek: The Next Generation, Star Trek: Voyager (and the various logo devices used in them) are copyright Paramount Pictures, as are the characters, related images, and sound from the productions.
LEGAL STUFF: This file is not supported or affiliated with Interplay Productions. While most who have used these files have had no problems, we will not be held accountable for any damage done to your computer by use of these files or techniques. USE AT YOUR OWN RISK! This file is freeware. It is not to be sold.
Copyrights
User-created missions contain source-code that is the property of Interplay Productions and Quicksilver Software. In addition, Star Trek is a property of Paramount Pictures. Star Fleet Battles is the property of ADB, Inc. You may not sell user-created missions commercially. You should respect the rights of the property owners. Missions created based on Star Fleet Battles material must be marked "Based on copyrighted material by ADB, Inc."in the documentation or mission briefing. ADB also requests that these missions not be placed on "out of network" SFB web-sites.
SOFTWARE USE LIMITATIONS AND LIMITED LICENSE
Any Star Trek: Starfleet Command mission (each, a "Mission", and collectively, "Missions") created using the Star Trek: Starfleet Command Mission API ("SFC Mission API") is intended solely for your personal, noncommercial home entertainment use. You may not decompile, reverse engineer, or disassemble SFC Mission API or any Mission, except as permitted by law. Interplay Entertainment Corp. ("Interplay") retains all rights and title in SFC Mission API and the Missions including all intellectual property rights embodied therein and derivatives thereof. SFC Mission API and the Missions, including, without limitation, all code, data structures, characters, images, sounds, text, screens, game play, derivative works and all other elements may not be copied (except as provided below), sold, rented, leased, distributed (except as provided below), used on pay-per-play, coin-op or other for-charge basis, or for commercial purpose. You may make copies of SFC Mission API and any Mission for your personal, noncommercial home entertainment use and to give to friends and acquaintances on a no cost, noncommercial basis. This limited right to copy or provide public access to the SFC Mission API and the Missions expressly excludes any copying, access or distribution of SFC Mission API and the Missions on a commercial basis, including, without limitation, bundling SFC Mission API or any Mission with any other product or service, selling SFC Mission API or any Mission, and any giveaway in connection with another product or service. Any permissions granted herein are provided on a temporary basis and can be withdrawn by Interplay at any time. All rights not expressly granted herein are reserved. No technical support from either Interplay or Quicksilver Software, Inc. ("Quicksilver") shall be available for SFC Mission API or any Mission.
INTERPLAY AND QUICKSILVER DISCLAIM ALL WARRANTIES, EXPRESS OR IMPLIED, RELATING TO SFC MISSION API AND THE MISSIONS (INCLUDING WITHOUT LIMITATION, MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT), AND NEITHER INTERPLAY NOR QUICKSILVER SHALL HAVE ANY RESPONSIBILITY OR LIABILITY REGARDING SFC MISSION API AND THE MISSIONS, INCLUDING, WITHOUT LIMITATION, ANY RESPONSIBILITY OR LIABILITY REGARDING USE OR OPERABILITY OF SFC MISSION API AND THE MISSIONS. YOU ASSUME ALL RISK OF LOSS IN CHOOSING TO USE SFC MISSION API AND THE MISSIONS.
SFC Mission API and all Missions © 1999 Interplay Entertainment Corp. SFC Mission API and Star Trek: Starfleet Command are trademarks of Interplay Entertainment Corp. All Rights Reserved.
You may not sell user-created missions commercially.
You should respect the rights of the property owners.
You have to ask for permission if you want to use one of this in any mod.
-----------------------------------------------------------------------------------------------------------------
how to install??
ships odf goes into odfships folder
tgas go into texturesrgb folder
sods go into SOD folder
add this to any shipyard odf buildlist:
buildItemxx = "shipname" (XX = 01-12) (shipname = ships odf name)
add this to the tech1.tt:
shipname.odf 0 (shipname = ships odf name)
and add this to gui global.spr:
b_shipname gbshipname 0 0 64 64 (shipname = ships odf name)
you have to ask me for permission to convert my models to any other games.
| Version | 1.0 | Author | Terradyhne | Website | Website  |
| Downloads | 1,054 | Size | 1,000.25 KB | Created | 2008-02-29 |
Comments
the aforementioned C series dreadnoughts, I can remember from Starfleet Command 1,2, and OP