|
|
|
|
| Valiant class (1.0) - File Description |
|
Quality: 9
FunFactor: 10
Creativity: 10
Overall Rating: 9.7 |
Description:
After the failure of the initial Defiant prototype, and the subsequent destruction of many of the remaining Defiant class vessels in minor skirmishes with Dominion forces during the war, Starfleet decided to improve upon the design and make it easier to produce by cutting some of the extravagant features like ablative armor. The resulting vessel is 15% more combat worthy, and is 45% easier to produce. The Valiant class heavy escorts will begin to replace the Defiant class within the next 5 years. Class: Heavy Cruiser (CA).
| |
|
|
| | | Valiant class (1.0) - Screenshots | | Screenshots:
| |
|
| | | Valiant class (1.0) - Readme | | Readme File:
Name: Valiant Prototype
Race: Federation
ERA: DS9
Hull Designation: FDD+
Class: DESTROYER
Date :JAN 14TH 2002
Author : HOLLIS J WOOD & ATRA-HASIS
Email : RED_ROCK@CANADA.COM
Homepage: http://www.geocities.com/atrahasis1/index.html
Credits- BASED ON DESIGN BY PARAMOUNT
Model Created by: HOLLIS J WOOD & ATRA-HASIS
Textures by: ATRA-HASIS
Credit Request: If you distribute, post or share any of these models or alter them and subsequently distribute, post or share any of these models please be nice and give credit where credit is due. This readme should always accompany these models wherever they go. Is that too much to ask? I think not.
Model Breaks (brk.mod) established:YES – is from the Rick Knox Defiant, as has escape pods (added here by Chris Jones 2-17-02)
Textured: Yes/No (if yes, please include the texture files in the .zip) Yes
Polygons: 1957
Copyright Info: Thanks to the SFC community.
Copyright and Distribution Permissions
--------------------------------------
THIS PATCH IS NOT MADE, DISTRIBUTED, OR SUPPORTED BY INTERPLAY
TM & (C) INTERPLAY & PARAMOUNT PICTURES.
Copyright notices:
Star Trek, Star Fleet Command, 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 any 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 MISINTERPLAY 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),ññ Xÿ ´ ü¿0’÷¿ÿÿÿÿ¨ñ \J÷¿?ñ 99 Interplay Entertainment Corp. SFC Mission API and Star Trek: Starfleet Command are trademarks of Interplay Entertainment Corp. All Rights Reserved. | |
|
|
|
| Valiant class (1.0) - File Download Options |
|
Primary Download Locations:
|
|
|
|
|
| Valiant class (1.0) - User Comments |
|
|
The following comments are owned by the user that posted them. SFC3 Files is not responsible for their content.
Total comments: 8 | Last comment: 12-09-2007 at 16:14
...but the pulse phaser box on top of the bridge could be rounder. And what are those four projections on the front of the ship? Very good looking design, though. Fierce looking.
I don't buy that this ship would replace the Defiant cl***** ships. Part of the Defiant's strength is that she's small and therefore harder to hit. This ship is larger, and lacks the armor, so her survivability in a fight I expect would actually be less than the 'tough little ship'. In order to really be 42% cheaper than the Defiant cl***** to produce, she would have to be less capable, even given a higher technology level.
I'd consider her complimentary to the Defiant cl*****, not a replacement for it. If she's statted properly, she'll have 15% more firepower than the Defiant, but also be far less survivable, probably in the form of 42% fewer hitpoints.
Nice ship, but have got any specs for it
If one more ruddy person asks for specs i'm gonna flip my wig. MAKE EM YOURSELF!!!!
This ship rocks for a DD!! here are some suggested specs that work great. She can kill a station if she has support vehicles with her:
10 CL 1000 0 2000 5400 2200 3400 10000 571 Fed- LightCruiser5 valiant PrimaryHP:1:300_360:2:0_60:3:300_360:4:0_60: HeavyHP:
12:330_30:13:330_30:14:330_30:15:165_195 HullHP:1:2:3 BridgeHP:1:2 ship Min
es:3:12:3 Marines:6:12:6 Shuttles:1:2:1
Federation Fed-LightCruiser5 valiant valiant F-TRACTOR-I:3 F-TRANSPORTER-I:1 F-ARMOR-II:2 F-COMPUTER-IV:1 K-CLOAK-II:2 F-WARP-V:1 F-IMPULSE-II:2 F-THRUSTER-III:3 PULSE PHASER:1 PULSE PHASER:2 PULSE PHASER:3 PULSE PHASER:4 QUANTUM TORPEDO:12 PHOTON TORPEDO:13 PHOTON TORPEDO:14 OFFICER:ENGINEER: OFFICER:SECURITY: OFFICER:HELM: OFFICER:OPS: O
FFICER:TACTICAL: OFFICER:MEDICAL: F-SHIELD-III:1 F-SHIELD-III:2 F-SHIELD-III:4 F-SHIELD-III:3
meant to say CL
I agree with Tulmahk on the blocky part above the bridge. It would look cool with something akin to the sensor pod ontop of the nebula class but smaller or I was even thinking of a similar unit to the nose of the Valiant/defiant minus the bottom half part with the deflector array. I never liked the ideal of the bridge so easy to be targeted anyway. It isnt like they look out a winshield its a viewscreen. They should be more protected. At least the Akira has those shoulderpad ribs protecting her bridge somewhat. Overall the ship is friggin sweet looking.
I agree with Tulmahk; it was made pretty clear towards the middle, and more so towards the end of DS9 that the design issues had largely been worked out. This is the federations BoP and Dominion bug-ship; although comparing it to the bird of prey is ridiculous due to it's superior power and tech; it just kinda fills that role and definitely is a direct answer to those annoying bugs.
However I have to disagree with Tulmahk in that I see this more as a compliment/escort to the Sabre, not the defiant. They'd really just get over-shadowed by the awesome defiant.
And it's also important to remember that it was in fact, at first, brought out earlier than was intended. It wasn't that the prototype failed, it is that it was... a prototype.
When posting comments, you must follow these rules:- No "Yay I got First Post!" posts, no exceptions and no matter what other content the post has!
- No Pornographic Material. Any sexually oriented imagery or links to such content will not be tolerated.
- No Warez or Illegal Software. This includes linking to software, posting about it, and suggesting to get it.
- No Cursing or Swear words. We encourage you to use our comment sections as a forum to debate files, news, etc., but please use proper adjectives to express yourself. We will not tolerate abuse upon another member or author.
- No Attacks / Retaliation of any kind against a member, or group of members.
- Please do not advertise for other sites or forums here.
- Maximum of 3 smileys per regular member.
The high interactivity of this site should be considered a luxury, not a right. If you cannot follow these simple rules, you can and will be warned or banned from the comments, site or the entire network for any period of time.
Now enjoy yourself and behave!
|
|
|
|
