Polaris Sector Star Trek TMP Romulan ships addon

---

CREDITS: There are many models made by many people, I have added all the credits from them, if you think that you have not been credited or you have other question, please contact me at my own site Firefoxccmods.com

Special thanks to Mayor a Payne by its help with the conversion from some of the models and to ravagewolf by search all the info about the heroes and more information for the mod.

Star Fleet Command 3 Star Trek TOS Mod, most of the stuff from this mod has been added at the Star Wars Empire at War Forces of Corruption Star Trek TOS Mod with the permission of the creators. Because it has many things from individual creators, I have tried add most of the work from them. You can find other credits at this list.

-------------------------------------------------------------------------------------------------------------

Author: WickedZombie45

Demon Renegade Studios

Ship Name: Romulan Melak Warbird (Based on ship seen in Star Trek: New Worlds)

Notes: SFC 1, 2/OP, and SFC 3 versions are included. The sfc 1 and 2 models are in separate folders so if you wish to use them in their respective games, simply drop those into the ship's folder in place of the standard sfc3 version.
The brk (exploding model) mod file is compatible with all SFC versions.

Ship Class: CA

Race: Romulan Star Empire

Date: 6/8/2004

Contact info: wickedzombie45@aol.com

Model made/edited using: Lightwave 5.6, 3d Studio Max 3.1, Paint Shop Pro 7, Uview, Taldren's .mod plugin

Please note: This policy is open to change following developments concerning my work which may not have been an issue previously. I suggest you check back frequently in order to keep updated on the current policy status. Copies of the policy included with the files may not be as up-to-date as the one posted here.

I have no problem with kitbashes/alterations as long as the following procedures are followed:

1.) Everyone involved with the kitbash/modification is to be credited. That includes the original model author(s), anyone involved with the design (if different from the modeler), and the person who created the alteration. This will set up a history of the modifications and give credit to all involved.

2.) If a ship is to be converted to another game (Bridge Commander, Armada, Klingon Academy, etc.) I prefer being notified of any alterations to my work as most times the credits are not listed properly, the ships aren't converted correctly, etc.

3.) If the ship is to be released to the public, no parts from a restricted model are to be used. Some modelers don't want their work to be altered and I would expect everyone to respect that. If there is a part or parts that are restricted, I can possibly create a replacement for you to use.

4.) If the ship is to be released to the public, I would ask that you contact me first. This is to make sure you have the proper credits listed and to make sure no restricted parts are being used. On some occasions people have credited me for work that I have never seen before.

5.) Please do not post these models on other websites (with the exception of mod/dynaverse downloads, kitbashes, and conversions to other games). I prefer keeping my ships on a single site so I can better control their distribution and make sure the correct files are updated. I know this sounds rather strict but it becomes a bit tedious when trying to update a ship and having to contact dozens of other websites to inform them of the changes as well.

6.) If I grant permission for alterations to a single model, that is not to be interpreted as a base acknowledgment for further alterations/conversions/kitbashes/etc. to any other ship that I have created. Approvals of alteration requests apply only to individual ships, not all of them at once unless otherwise stated in my response.

7.) If you're going to use a ship in a mod, do not delete the readme file or remove it from the ship's folder. Various mod makers tend to do this and simply list the modders in one big readme. This tends to remove any clear source of credits for an individual ship and should the ship fall into other's hands, it creates more confusion. I don't include readmes just for tradition's sake and the purpose for them is to make sure there's a traceable credit history for whoever is involved in the ship's creation.

8.) All work on this site is property of the respective owners. If anyone attempts to steal or take credit for work they did not do, I will hunt you down and feed you to a pack of bloodthirsty wolves.

Are these following files/modifications included?

Model brks (exploding model)-yes
Textured-yes
Hardpoints/damage points-yes
Ship (mod) file-yes
SFC II illumination maps-yes
SFC 3 Compatable-yes

Star Trek, Star Fleet Command, Star Trek: Deep Space Nine, Star Trek: The Next Generation, Star Trek: Voyager, Star Trek: Enterprise (and the various logo devices used in them) are copyright Paramount Pictures, as are the characters, related images, and sound from the productions.

These files are not supported or affiliated with Interplay Productions or Activision. 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! These files are freeware. They are not to be sold or used in any for-profit venture.

All works on this site are the intellectual property of their respective creators and are subject to legal protection under copyright. It is not to be used, altered, or redistributed without their consent.

-------------------------------------------------------------------------------------------------------------

Author: WickedZombie45

Demon Renegade Studios

Ship Name: Romulan Melak Warbird - TMP Style Retexture (Based on ship seen in Star Trek: New Worlds)

Notes: SFC 1, 2/OP, and SFC 3 versions are included. The sfc 1 and 2 models are in separate folders so if you wish to use them in their respective games, simply drop those into the ship's folder in place of the standard sfc3 version.
The brk (exploding model) mod file is compatible with all SFC versions.

Ship Class: CA

Race: Romulan Star Empire

Date: 8/8/2004

Contact info: wickedzombie45@aol.com

Model made/edited using: Lightwave 5.6, 3d Studio Max 3.1, Paint Shop Pro 7, Uview, Taldren's .mod plugin

Please note: This policy is open to change following developments concerning my work which may not have been an issue previously. I suggest you check back frequently in order to keep updated on the current policy status. Copies of the policy included with the files may not be as up-to-date as the one posted here.

I have no problem with kitbashes/alterations as long as the following procedures are followed:

1.) Everyone involved with the kitbash/modification is to be credited. That includes the original model author(s), anyone involved with the design (if different from the modeler), and the person who created the alteration. This will set up a history of the modifications and give credit to all involved.

2.) If a ship is to be converted to another game (Bridge Commander, Armada, Klingon Academy, etc.) I prefer being notified of any alterations to my work as most times the credits are not listed properly, the ships aren't converted correctly, etc.

3.) If the ship is to be released to the public, no parts from a restricted model are to be used. Some modelers don't want their work to be altered and I would expect everyone to respect that. If there is a part or parts that are restricted, I can possibly create a replacement for you to use.

4.) If the ship is to be released to the public, I would ask that you contact me first. This is to make sure you have the proper credits listed and to make sure no restricted parts are being used. On some occasions people have credited me for work that I have never seen before.

5.) Please do not post these models on other websites (with the exception of mod/dynaverse downloads, kitbashes, and conversions to other games). I prefer keeping my ships on a single site so I can better control their distribution and make sure the correct files are updated. I know this sounds rather strict but it becomes a bit tedious when trying to update a ship and having to contact dozens of other websites to inform them of the changes as well.

6.) If I grant permission for alterations to a single model, that is not to be interpreted as a base acknowledgment for further alterations/conversions/kitbashes/etc. to any other ship that I have created. Approvals of alteration requests apply only to individual ships, not all of them at once unless otherwise stated in my response.

7.) If you're going to use a ship in a mod, do not delete the readme file or remove it from the ship's folder. Various mod makers tend to do this and simply list the modders in one big readme. This tends to remove any clear source of credits for an individual ship and should the ship fall into other's hands, it creates more confusion. I don't include readmes just for tradition's sake and the purpose for them is to make sure there's a traceable credit history for whoever is involved in the ship's creation.

8.) All work on this site is property of the respective owners. If anyone attempts to steal or take credit for work they did not do, I will hunt you down and feed you to a pack of bloodthirsty wolves.

Are these following files/modifications included?

Model brks (exploding model)-yes
Textured-yes
Hardpoints/damage points-yes
Ship (mod) file-yes
SFC II illumination maps-yes
SFC 3 Compatable-yes

Star Trek, Star Fleet Command, Star Trek: Deep Space Nine, Star Trek: The Next Generation, Star Trek: Voyager, Star Trek: Enterprise (and the various logo devices used in them) are copyright Paramount Pictures, as are the characters, related images, and sound from the productions.

These files are not supported or affiliated with Interplay Productions or Activision. 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! These files are freeware. They are not to be sold or used in any for-profit venture.

All works on this site are the intellectual property of their respective creators and are subject to legal protection under copyright. It is not to be used, altered, or redistributed without their consent.

-------------------------------------------------------------------------------------------------------------

This readme is to be included with this ship at all times - Dynaverse mods are NO exception!

Author:

Model/Textures: WickedZombie45

Design: Atolm, Belly-Bird by Atolm

Demon Renegade Studios

Ship Name: R.I.S. Excidium - D7 Stormbird Class Cruiser

Notes: SFC 1, 2/OP, and SFC 3 versions are included. The sfc 1 and 2 models are in separate folders so if you wish to use them in their respective games, simply drop those into the ship's folder in place of the standard sfc3 version.
The brk (exploding model) mod file is compatible with all SFC versions.

Ship Class: Cruiser

Race: Romulan Empire

Date: 8/2/09

Contact info: wickedzombie45@aol.com

Model made/edited using: Lightwave 5.6, 3d Studio Max 3.1, Paint Shop Pro 7, Uview, Taldren's .mod plugin

Please note: This policy is open to change following developments concerning my work which may not have been an issue previously. I suggest you check back frequently in order to keep updated on the current policy status. Copies of the policy included with the files may not be as up-to-date as the one posted here.

I have no problem with kitbashes/alterations as long as the following procedures are followed:

1.) Everyone involved with the kitbash/modification is to be credited. That includes the original model author(s), anyone involved with the design (if different from the modeler), and the person who created the alteration. This will set up a history of the modifications and give credit to all involved.

2.) If a ship is to be converted to another game (Bridge Commander, Armada, Klingon Academy, etc.) I prefer being notified of any alterations to my work as most times the credits are not listed properly, the ships aren't converted correctly, etc.

3.) If the ship is to be released to the public, no parts from a restricted model are to be used. Some modelers don't want their work to be altered and I would expect everyone to respect that. If there is a part or parts that are restricted, I can possibly create a replacement for you to use.

4.) If the ship is to be released to the public, I would ask that you contact me first. This is to make sure you have the proper credits listed and to make sure no restricted parts are being used. On some occasions people have credited me for work that I have never seen before.

5.) Please do not post these models on other websites (with the exception of mod/dynaverse downloads, kitbashes, and conversions to other games). I prefer keeping my ships on a single site so I can better control their distribution and make sure the correct files are updated. I know this sounds rather strict but it becomes a bit tedious when trying to update a ship and having to contact dozens of other websites to inform them of the changes as well.

6.) If I grant permission for alterations to a single model, that is not to be interpreted as a base acknowledgment for further alterations/conversions/kitbashes/etc. to any other ship that I have created. Approvals of alteration requests apply only to individual ships, not all of them at once unless otherwise stated in my response.

7.) If you're going to use a ship in a mod, do not delete the readme file or remove it from the ship's folder. Various mod makers tend to do this and simply list the modders in one big readme. This tends to remove any clear source of credits for an individual ship and should the ship fall into other's hands, it creates more confusion. I don't include readmes just for tradition's sake and the purpose for them is to make sure there's a traceable credit history for whoever is involved in the ship's creation.

8.) All work on this site is property of the respective owners. If anyone attempts to steal or take credit for work they did not do, I will hunt you down and feed you to a pack of bloodthirsty wolves.

Are these following files/modifications included?

Model brks (exploding model)-yes
Textured-yes
Hardpoints/damage points-yes
Ship (mod) file-yes
SFC II illumination maps-yes
SFC 3 Compatable-yes

Star Trek, Star Fleet Command, Star Trek: Deep Space Nine, Star Trek: The Next Generation, Star Trek: Voyager, Star Trek: Enterprise (and the various logo devices used in them) are copyright Paramount Pictures, as are the characters, related images, and sound from the productions.

These files are not supported or affiliated with Interplay Productions or Activision. 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! These files are freeware. They are not to be sold or used in any for-profit venture.

All works on this site are the intellectual property of their respective creators and are subject to legal protection under copyright. It is not to be used, altered, or redistributed without their consent.

-------------------------------------------------------------------------------------------------------------

This readme is to be included with this ship at all times - Dynaverse mods are NO exception!

Author:

Model/Textures: WickedZombie45

Design: Atolm, Belly-Bird by Atolm

Demon Renegade Studios

Ship Name: R.I.S. Adversarius - Sparrowhawk Class Cruiser

Notes: SFC 1, 2/OP, and SFC 3 versions are included. The sfc 1 and 2 models are in separate folders so if you wish to use them in their respective games, simply drop those into the ship's folder in place of the standard sfc3 version.
The brk (exploding model) mod file is compatible with all SFC versions.

Ship Class: Cruiser

Race: Romulan Empire

Date: 12/7/08

Contact info: wickedzombie45@aol.com

Model made/edited using: Lightwave 5.6, 3d Studio Max 3.1, Paint Shop Pro 7, Uview, Taldren's .mod plugin

Please note: This policy is open to change following developments concerning my work which may not have been an issue previously. I suggest you check back frequently in order to keep updated on the current policy status. Copies of the policy included with the files may not be as up-to-date as the one posted here.

I have no problem with kitbashes/alterations as long as the following procedures are followed:

1.) Everyone involved with the kitbash/modification is to be credited. That includes the original model author(s), anyone involved with the design (if different from the modeler), and the person who created the alteration. This will set up a history of the modifications and give credit to all involved.

2.) If a ship is to be converted to another game (Bridge Commander, Armada, Klingon Academy, etc.) I prefer being notified of any alterations to my work as most times the credits are not listed properly, the ships aren't converted correctly, etc.

3.) If the ship is to be released to the public, no parts from a restricted model are to be used. Some modelers don't want their work to be altered and I would expect everyone to respect that. If there is a part or parts that are restricted, I can possibly create a replacement for you to use.

4.) If the ship is to be released to the public, I would ask that you contact me first. This is to make sure you have the proper credits listed and to make sure no restricted parts are being used. On some occasions people have credited me for work that I have never seen before.

5.) Please do not post these models on other websites (with the exception of mod/dynaverse downloads, kitbashes, and conversions to other games). I prefer keeping my ships on a single site so I can better control their distribution and make sure the correct files are updated. I know this sounds rather strict but it becomes a bit tedious when trying to update a ship and having to contact dozens of other websites to inform them of the changes as well.

6.) If I grant permission for alterations to a single model, that is not to be interpreted as a base acknowledgment for further alterations/conversions/kitbashes/etc. to any other ship that I have created. Approvals of alteration requests apply only to individual ships, not all of them at once unless otherwise stated in my response.

7.) If you're going to use a ship in a mod, do not delete the readme file or remove it from the ship's folder. Various mod makers tend to do this and simply list the modders in one big readme. This tends to remove any clear source of credits for an individual ship and should the ship fall into other's hands, it creates more confusion. I don't include readmes just for tradition's sake and the purpose for them is to make sure there's a traceable credit history for whoever is involved in the ship's creation.

8.) All work on this site is property of the respective owners. If anyone attempts to steal or take credit for work they did not do, I will hunt you down and feed you to a pack of bloodthirsty wolves.

Are these following files/modifications included?

Model brks (exploding model)-yes
Textured-yes
Hardpoints/damage points-yes
Ship (mod) file-yes
SFC II illumination maps-yes
SFC 3 Compatable-yes

Star Trek, Star Fleet Command, Star Trek: Deep Space Nine, Star Trek: The Next Generation, Star Trek: Voyager, Star Trek: Enterprise (and the various logo devices used in them) are copyright Paramount Pictures, as are the characters, related images, and sound from the productions.

These files are not supported or affiliated with Interplay Productions or Activision. 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! These files are freeware. They are not to be sold or used in any for-profit venture.

All works on this site are the intellectual property of their respective creators and are subject to legal protection under copyright. It is not to be used, altered, or redistributed without their consent.

-------------------------------------------------------------------------------------------------------------

This readme is to be included with this ship at all times - Dynaverse mods are NO exception!

Author:

Model/Textures: WickedZombie45

Design: Atolm

Demon Renegade Studios

Ship Name: Romulan Ra'Kholh Class Strikehawk Heavy Cruiser

Notes: SFC 1, 2/OP, and SFC 3 versions are included. The sfc 1 and 2 models are in separate folders so if you wish to use them in their respective games, simply drop those into the ship's folder in place of the standard sfc3 version.
The brk (exploding model) mod file is compatible with all SFC versions.

Ship Class: Heavy Cruiser

Race: Romulan Empire

Date: 12/12/10

Contact info: wickedzombie45@aol.com

Model made/edited using: Lightwave 5.6, 3d Studio Max 3.1, Paint Shop Pro 7, Uview, Taldren's .mod plugin

Please note: This policy is open to change following developments concerning my work which may not have been an issue previously. I suggest you check back frequently in order to keep updated on the current policy status. Copies of the policy included with the files may not be as up-to-date as the one posted here.

I have no problem with kitbashes/alterations as long as the following procedures are followed:

1.) Everyone involved with the kitbash/modification is to be credited. That includes the original model author(s), anyone involved with the design (if different from the modeler), and the person who created the alteration. This will set up a history of the modifications and give credit to all involved.

2.) If a ship is to be converted to another game (Bridge Commander, Armada, Klingon Academy, etc.) I prefer being notified of any alterations to my work as most times the credits are not listed properly, the ships aren't converted correctly, etc.

3.) If the ship is to be released to the public, no parts from a restricted model are to be used. Some modelers don't want their work to be altered and I would expect everyone to respect that. If there is a part or parts that are restricted, I can possibly create a replacement for you to use.

4.) If the ship is to be released to the public, I would ask that you contact me first. This is to make sure you have the proper credits listed and to make sure no restricted parts are being used. On some occasions people have credited me for work that I have never seen before.

5.) Please do not post these models on other websites (with the exception of mod/dynaverse downloads, kitbashes, and conversions to other games). I prefer keeping my ships on a single site so I can better control their distribution and make sure the correct files are updated. I know this sounds rather strict but it becomes a bit tedious when trying to update a ship and having to contact dozens of other websites to inform them of the changes as well.

6.) If I grant permission for alterations to a single model, that is not to be interpreted as a base acknowledgment for further alterations/conversions/kitbashes/etc. to any other ship that I have created. Approvals of alteration requests apply only to individual ships, not all of them at once unless otherwise stated in my response.

7.) If you're going to use a ship in a mod, do not delete the readme file or remove it from the ship's folder. Various mod makers tend to do this and simply list the modders in one big readme. This tends to remove any clear source of credits for an individual ship and should the ship fall into other's hands, it creates more confusion. I don't include readmes just for tradition's sake and the purpose for them is to make sure there's a traceable credit history for whoever is involved in the ship's creation.

8.) All work on this site is property of the respective owners. If anyone attempts to steal or take credit for work they did not do, I will hunt you down and feed you to a pack of bloodthirsty wolves.

Are these following files/modifications included?

Model brks (exploding model)-yes
Textured-yes
Hardpoints/damage points-yes
Ship (mod) file-yes
SFC II illumination maps-yes
SFC 3 Compatable-yes

Star Trek, Star Fleet Command, Star Trek: Deep Space Nine, Star Trek: The Next Generation, Star Trek: Voyager, Star Trek: Enterprise (and the various logo devices used in them) are copyright Paramount Pictures, as are the characters, related images, and sound from the productions.

These files are not supported or affiliated with Interplay Productions or Activision. 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! These files are freeware. They are not to be sold or used in any for-profit venture.

All works on this site are the intellectual property of their respective creators and are subject to legal protection under copyright. It is not to be used, altered, or redistributed without their consent.

-------------------------------------------------------------------------------------------------------------

This readme is to be included with this ship at all times - Dynaverse mods are NO exception!

Author:

Model/Textures: WickedZombie45

Design: Atolm

Demon Renegade Studios

Ship Name: R.I.S. Astra Volantis - Sunhawk class Bird of Prey

Notes: SFC 1, 2/OP, and SFC 3 versions are included. The sfc 1 and 2 models are in separate folders so if you wish to use them in their respective games, simply drop those into the ship's folder in place of the standard sfc3 version.
The brk (exploding model) mod file is compatible with all SFC versions.

Ship Class: Light Cruiser

Race: Romulan Empire

Date: 9/29/08

Contact info: wickedzombie45@aol.com

Model made/edited using: Lightwave 5.6, 3d Studio Max 3.1, Paint Shop Pro 7, Uview, Taldren's .mod plugin

Please note: This policy is open to change following developments concerning my work which may not have been an issue previously. I suggest you check back frequently in order to keep updated on the current policy status. Copies of the policy included with the files may not be as up-to-date as the one posted here.

I have no problem with kitbashes/alterations as long as the following procedures are followed:

1.) Everyone involved with the kitbash/modification is to be credited. That includes the original model author(s), anyone involved with the design (if different from the modeler), and the person who created the alteration. This will set up a history of the modifications and give credit to all involved.

2.) If a ship is to be converted to another game (Bridge Commander, Armada, Klingon Academy, etc.) I prefer being notified of any alterations to my work as most times the credits are not listed properly, the ships aren't converted correctly, etc.

3.) If the ship is to be released to the public, no parts from a restricted model are to be used. Some modelers don't want their work to be altered and I would expect everyone to respect that. If there is a part or parts that are restricted, I can possibly create a replacement for you to use.

4.) If the ship is to be released to the public, I would ask that you contact me first. This is to make sure you have the proper credits listed and to make sure no restricted parts are being used. On some occasions people have credited me for work that I have never seen before.

5.) Please do not post these models on other websites (with the exception of mod/dynaverse downloads, kitbashes, and conversions to other games). I prefer keeping my ships on a single site so I can better control their distribution and make sure the correct files are updated. I know this sounds rather strict but it becomes a bit tedious when trying to update a ship and having to contact dozens of other websites to inform them of the changes as well.

6.) If I grant permission for alterations to a single model, that is not to be interpreted as a base acknowledgment for further alterations/conversions/kitbashes/etc. to any other ship that I have created. Approvals of alteration requests apply only to individual ships, not all of them at once unless otherwise stated in my response.

7.) If you're going to use a ship in a mod, do not delete the readme file or remove it from the ship's folder. Various mod makers tend to do this and simply list the modders in one big readme. This tends to remove any clear source of credits for an individual ship and should the ship fall into other's hands, it creates more confusion. I don't include readmes just for tradition's sake and the purpose for them is to make sure there's a traceable credit history for whoever is involved in the ship's creation.

8.) All work on this site is property of the respective owners. If anyone attempts to steal or take credit for work they did not do, I will hunt you down and feed you to a pack of bloodthirsty wolves.

Are these following files/modifications included?

Model brks (exploding model)-yes
Textured-yes
Hardpoints/damage points-yes
Ship (mod) file-yes
SFC II illumination maps-yes
SFC 3 Compatable-yes

Star Trek, Star Fleet Command, Star Trek: Deep Space Nine, Star Trek: The Next Generation, Star Trek: Voyager, Star Trek: Enterprise (and the various logo devices used in them) are copyright Paramount Pictures, as are the characters, related images, and sound from the productions.

These files are not supported or affiliated with Interplay Productions or Activision. 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! These files are freeware. They are not to be sold or used in any for-profit venture.

All works on this site are the intellectual property of their respective creators and are subject to legal protection under copyright. It is not to be used, altered, or redistributed without their consent.

-------------------------------------------------------------------------------------------------------------

TOS ships

D-7, D-7A, D-7R

Model/Textures by ATRA-HASIS (atrahasis1@hotmail.com) - Geocities.com

Credits: Some mesh components borrowed from Moonraker's Ktinga model.

TMP & TNG ships

KTinga, KTingaR, Qonos One, KTingaTNG

Model/Textures by WickedZombie45 (wickedzombie45@aol.com) - Nightsoftware.com

Script for the Romulan Torpedo by edtheborg

All convertions/hardpoints/sounds by Zambie Zan (alexandre.marques@gmail.com)

-------------------------------------------------------------------------------------------------------------
=======================================================================================

Copyright and Distribution Permissions
--------------------------------------
THIS PATCH IS NOT MADE, DISTRIBUTED, OR SUPPORTED BY INTERPLAY TM & (C) INTERPLAY & TALDREN & 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 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.