Klingon.lostexiles.net - User contributions [en]

Tuning SFC to play on modern hardware

2025-10-10T17:42:37Z

Firesoul: /* Woth dgVoodoo2 - manage non-existant 3D settings */

Note: this section was added on 2015-08-06. SFC2 is 15 years by now.
First some facts:
* SFC doesn't really optimize graphic output for better play
** no anti-aliasing nor anisotropic filtering
* SFC2 has been around for 15 years or more.
** based on Moore's law, that means the average computer is about 1000x more powerful/efficient at the same cost as it was back around Y2K.
* graphics drivers these days have great capabilities.

== Missing Windows Registry Entries ==

The following is for SFC2:OP. I did not research for EAW.

The game's installer was written in the 32-bit days, and did not account for 64-bit systems that supported 32-bit. To solve this, a couple of Registry entries need to be added so that other resources can find the game's installation.

This is needed for the additional installers like OP+'s, or the missionpacks.

Make a ''something.reg'' file, and change the directory paths I list to where your SFC install is. You need both entries. Double the backslashes (\\).
One's for 32-bit, the other is for 64-bit.

Then double-click on the file to import to your system. You need to be Administrator.

For example, if you installed SFC2:OP into ''D:\SFC\Starfleet Command Orion Pirates'' ..then..
----
[HKEY_LOCAL_MACHINE\SOFTWARE\Taldren\Starfleet Command Orion Pirates]
"Directory"="D:\\SFC\\Starfleet Command Orion Pirates"

[HKEY_LOCAL_MACHINE\SOFTWARE\WOW6432Node\Taldren\Starfleet Command Orion Pirates]
"Directory"="D:\\SFC\\Starfleet Command Orion Pirates"
----

== Modern DirectX compatibility ==

SFC2, whether it's SFC2:OP or SFC2:EAW, are built on DirectX7 or DirectX8. Current (this bit is written in 2025) DirectX is 12, but there's still some 11 around. It's incompatible.

There's a solution! Someone wrote a DirectX adapter. It's called dgVoodoo2.
See: [https://dege.freeweb.hu/dgVoodoo2/ https://dege.freeweb.hu/dgVoodoo2/]

To install dgVoodoo2, please follow their installation instructions as per their documentation. In my case, it was a matter of dropping the right files in the same folder/directory as starfleetop.exe and using their UI tool to configure how it should behave:

https://klingon.lostexiles.net/screenshots/dgvoodoo2_configure_example.png

== Consider the community patch/versions ==

Visit the Hot&Spicy forums, for SFC2:OP 2.5.6.4.
[https://hotandspicyforums.com/starfleet-command-2-orion-pirates-v2-564-august-20-t25292.html https://hotandspicyforums.com/starfleet-command-2-orion-pirates-v2-564-august-20-t25292.html]

== With dgVoodoo2 - manage non-existant 3D settings ==

SFC does not.. have.. anti-aliasing. I guess it's that old. However, dgVoodoo2 does provide a tab to manager/override/force some settings like Anti-Aliasing. You can also force the Resolution to use. If you're going to do that, you should use the Hot&Spicy build of SFC and match the resolution setting there too.
ie: a 16:9 resolution of 1920x1080

It's under the DirectX tab.

https://klingon.lostexiles.net/screenshots/dgvoodoo2_force_3d_settings.png

== With dgVoodoo2 - use ReShade ==

ReShade is a DX12 post-processor later for generating shaders and other modifications of your choice, to manipulate the generated image further. It's generic and is installed per-game at the DX12 level in the game's own directory.

ReShade project page: https://reshade.me/

Effectively, if you use dgVoodoo2, you convert to DX12, which can then pass through ReShade, then go to your modern video card's driver.

https://klingon.lostexiles.net/screenshots/with_dgVoodoo2__use_reshade.png

== Without dgVoodoo2 -- Aspect ratio and scaling ==

If you have a modern system like me, then you probably have a 16x9 ratio monitor. Mine is 2560x1440, and this monitor isn't current edge tech. SFC, SFC2:EAW and SFC:OP were all designed for 4:3 ratio monitors.

''The following are ALL 4:3 ratio resolutions...''
https://klingon.lostexiles.net/screenshots/20150807_EzINI_4x3_resolutions.png

This means you're probably playing SFC:OP with a stretched image. You can force the monitor to display the image scaled proportionally by adjusting your scaling and aspect ratio.

Note: my monitor could not, but my video card can. Thus:
https://klingon.lostexiles.net/screenshots/20150806_nvidia_settings_scaling_GPU_override.png

== Without dgVoodoo2 -- Manage 3D Settings ==

SFC does not have any 3D settings of importance. Your video card management tools might. In this example (mine), Nvidia drivers can have overrides based on what executable you're launching.

'''This is important: Make sure you select the SFC:OP executable for these settings!'''

Here's my suggestions:
* anti-aliasing
** don't touch FXAA Anti-aliasing. That just fuzzies up the image.
** otherwise go ahead, crank it up. I've set it to CSAA Anti-Aliasing with as much sampling possible.
** research! Go online and google up what anti-aliasing does.
* Anisotropic filtering
** affects crispness of textures
** also crank it up.
* texture quality
** set those to very high quality of course.
* test test test!
* enjoy!

https://klingon.lostexiles.net/screenshots/20150806_nvidia_settings_SFC_1.png
https://klingon.lostexiles.net/screenshots/20150806_nvidia_settings_SFC_2.png
https://klingon.lostexiles.net/screenshots/20150806_SFCOP_with_tweaked_settings.png

Tuning SFC to play on modern hardware

2025-10-10T17:39:56Z

Firesoul: /* With dgVoodoo2 - use ReShade */

Note: this section was added on 2015-08-06. SFC2 is 15 years by now.
First some facts:
* SFC doesn't really optimize graphic output for better play
** no anti-aliasing nor anisotropic filtering
* SFC2 has been around for 15 years or more.
** based on Moore's law, that means the average computer is about 1000x more powerful/efficient at the same cost as it was back around Y2K.
* graphics drivers these days have great capabilities.

== Missing Windows Registry Entries ==

The following is for SFC2:OP. I did not research for EAW.

The game's installer was written in the 32-bit days, and did not account for 64-bit systems that supported 32-bit. To solve this, a couple of Registry entries need to be added so that other resources can find the game's installation.

This is needed for the additional installers like OP+'s, or the missionpacks.

Make a ''something.reg'' file, and change the directory paths I list to where your SFC install is. You need both entries. Double the backslashes (\\).
One's for 32-bit, the other is for 64-bit.

Then double-click on the file to import to your system. You need to be Administrator.

For example, if you installed SFC2:OP into ''D:\SFC\Starfleet Command Orion Pirates'' ..then..
----
[HKEY_LOCAL_MACHINE\SOFTWARE\Taldren\Starfleet Command Orion Pirates]
"Directory"="D:\\SFC\\Starfleet Command Orion Pirates"

[HKEY_LOCAL_MACHINE\SOFTWARE\WOW6432Node\Taldren\Starfleet Command Orion Pirates]
"Directory"="D:\\SFC\\Starfleet Command Orion Pirates"
----

== Modern DirectX compatibility ==

SFC2, whether it's SFC2:OP or SFC2:EAW, are built on DirectX7 or DirectX8. Current (this bit is written in 2025) DirectX is 12, but there's still some 11 around. It's incompatible.

There's a solution! Someone wrote a DirectX adapter. It's called dgVoodoo2.
See: [https://dege.freeweb.hu/dgVoodoo2/ https://dege.freeweb.hu/dgVoodoo2/]

To install dgVoodoo2, please follow their installation instructions as per their documentation. In my case, it was a matter of dropping the right files in the same folder/directory as starfleetop.exe and using their UI tool to configure how it should behave:

https://klingon.lostexiles.net/screenshots/dgvoodoo2_configure_example.png

== Consider the community patch/versions ==

Visit the Hot&Spicy forums, for SFC2:OP 2.5.6.4.
[https://hotandspicyforums.com/starfleet-command-2-orion-pirates-v2-564-august-20-t25292.html https://hotandspicyforums.com/starfleet-command-2-orion-pirates-v2-564-august-20-t25292.html]

== Woth dgVoodoo2 - manage non-existant 3D settings ==

SFC does not.. have.. anti-aliasing. I guess it's that old. However, dgVoodoo2 does provide a tab to manager/override/force some settings like Anti-Aliasing. You can also force the Resolution to use. If you're going to do that, you should use the Hot&Spicy build of SFC and match the resolution setting there too.
ie: a 16:9 resolution of 1920x1080

It's under the DirectX tab.

https://klingon.lostexiles.net/screenshots/dgvoodoo2_force_3d_settings.png

== With dgVoodoo2 - use ReShade ==

ReShade is a DX12 post-processor later for generating shaders and other modifications of your choice, to manipulate the generated image further. It's generic and is installed per-game at the DX12 level in the game's own directory.

ReShade project page: https://reshade.me/

Effectively, if you use dgVoodoo2, you convert to DX12, which can then pass through ReShade, then go to your modern video card's driver.

https://klingon.lostexiles.net/screenshots/with_dgVoodoo2__use_reshade.png

== Without dgVoodoo2 -- Aspect ratio and scaling ==

If you have a modern system like me, then you probably have a 16x9 ratio monitor. Mine is 2560x1440, and this monitor isn't current edge tech. SFC, SFC2:EAW and SFC:OP were all designed for 4:3 ratio monitors.

''The following are ALL 4:3 ratio resolutions...''
https://klingon.lostexiles.net/screenshots/20150807_EzINI_4x3_resolutions.png

This means you're probably playing SFC:OP with a stretched image. You can force the monitor to display the image scaled proportionally by adjusting your scaling and aspect ratio.

Note: my monitor could not, but my video card can. Thus:
https://klingon.lostexiles.net/screenshots/20150806_nvidia_settings_scaling_GPU_override.png

== Without dgVoodoo2 -- Manage 3D Settings ==

SFC does not have any 3D settings of importance. Your video card management tools might. In this example (mine), Nvidia drivers can have overrides based on what executable you're launching.

'''This is important: Make sure you select the SFC:OP executable for these settings!'''

Here's my suggestions:
* anti-aliasing
** don't touch FXAA Anti-aliasing. That just fuzzies up the image.
** otherwise go ahead, crank it up. I've set it to CSAA Anti-Aliasing with as much sampling possible.
** research! Go online and google up what anti-aliasing does.
* Anisotropic filtering
** affects crispness of textures
** also crank it up.
* texture quality
** set those to very high quality of course.
* test test test!
* enjoy!

https://klingon.lostexiles.net/screenshots/20150806_nvidia_settings_SFC_1.png
https://klingon.lostexiles.net/screenshots/20150806_nvidia_settings_SFC_2.png
https://klingon.lostexiles.net/screenshots/20150806_SFCOP_with_tweaked_settings.png

Tuning SFC to play on modern hardware

2025-10-10T17:37:43Z

Firesoul:

Note: this section was added on 2015-08-06. SFC2 is 15 years by now.
First some facts:
* SFC doesn't really optimize graphic output for better play
** no anti-aliasing nor anisotropic filtering
* SFC2 has been around for 15 years or more.
** based on Moore's law, that means the average computer is about 1000x more powerful/efficient at the same cost as it was back around Y2K.
* graphics drivers these days have great capabilities.

== Missing Windows Registry Entries ==

The following is for SFC2:OP. I did not research for EAW.

The game's installer was written in the 32-bit days, and did not account for 64-bit systems that supported 32-bit. To solve this, a couple of Registry entries need to be added so that other resources can find the game's installation.

This is needed for the additional installers like OP+'s, or the missionpacks.

Make a ''something.reg'' file, and change the directory paths I list to where your SFC install is. You need both entries. Double the backslashes (\\).
One's for 32-bit, the other is for 64-bit.

Then double-click on the file to import to your system. You need to be Administrator.

For example, if you installed SFC2:OP into ''D:\SFC\Starfleet Command Orion Pirates'' ..then..
----
[HKEY_LOCAL_MACHINE\SOFTWARE\Taldren\Starfleet Command Orion Pirates]
"Directory"="D:\\SFC\\Starfleet Command Orion Pirates"

[HKEY_LOCAL_MACHINE\SOFTWARE\WOW6432Node\Taldren\Starfleet Command Orion Pirates]
"Directory"="D:\\SFC\\Starfleet Command Orion Pirates"
----

== Modern DirectX compatibility ==

SFC2, whether it's SFC2:OP or SFC2:EAW, are built on DirectX7 or DirectX8. Current (this bit is written in 2025) DirectX is 12, but there's still some 11 around. It's incompatible.

There's a solution! Someone wrote a DirectX adapter. It's called dgVoodoo2.
See: [https://dege.freeweb.hu/dgVoodoo2/ https://dege.freeweb.hu/dgVoodoo2/]

To install dgVoodoo2, please follow their installation instructions as per their documentation. In my case, it was a matter of dropping the right files in the same folder/directory as starfleetop.exe and using their UI tool to configure how it should behave:

https://klingon.lostexiles.net/screenshots/dgvoodoo2_configure_example.png

== Consider the community patch/versions ==

Visit the Hot&Spicy forums, for SFC2:OP 2.5.6.4.
[https://hotandspicyforums.com/starfleet-command-2-orion-pirates-v2-564-august-20-t25292.html https://hotandspicyforums.com/starfleet-command-2-orion-pirates-v2-564-august-20-t25292.html]

== Woth dgVoodoo2 - manage non-existant 3D settings ==

SFC does not.. have.. anti-aliasing. I guess it's that old. However, dgVoodoo2 does provide a tab to manager/override/force some settings like Anti-Aliasing. You can also force the Resolution to use. If you're going to do that, you should use the Hot&Spicy build of SFC and match the resolution setting there too.
ie: a 16:9 resolution of 1920x1080

It's under the DirectX tab.

https://klingon.lostexiles.net/screenshots/dgvoodoo2_force_3d_settings.png

== With dgVoodoo2 - use ReShade ==

ReShade is a DX12 post-processor later for generating shaders and other modifications of your choice, to manipulate the generated image further. It's generic and is installed per-game at the DX12 level in the game's own directory.

Effectively, if you use dgVoodoo2, you convert to DX12, which can then pass through ReShade, then go to your modern video card's driver.

== Without dgVoodoo2 -- Aspect ratio and scaling ==

If you have a modern system like me, then you probably have a 16x9 ratio monitor. Mine is 2560x1440, and this monitor isn't current edge tech. SFC, SFC2:EAW and SFC:OP were all designed for 4:3 ratio monitors.

''The following are ALL 4:3 ratio resolutions...''
https://klingon.lostexiles.net/screenshots/20150807_EzINI_4x3_resolutions.png

This means you're probably playing SFC:OP with a stretched image. You can force the monitor to display the image scaled proportionally by adjusting your scaling and aspect ratio.

Note: my monitor could not, but my video card can. Thus:
https://klingon.lostexiles.net/screenshots/20150806_nvidia_settings_scaling_GPU_override.png

== Without dgVoodoo2 -- Manage 3D Settings ==

SFC does not have any 3D settings of importance. Your video card management tools might. In this example (mine), Nvidia drivers can have overrides based on what executable you're launching.

'''This is important: Make sure you select the SFC:OP executable for these settings!'''

Here's my suggestions:
* anti-aliasing
** don't touch FXAA Anti-aliasing. That just fuzzies up the image.
** otherwise go ahead, crank it up. I've set it to CSAA Anti-Aliasing with as much sampling possible.
** research! Go online and google up what anti-aliasing does.
* Anisotropic filtering
** affects crispness of textures
** also crank it up.
* texture quality
** set those to very high quality of course.
* test test test!
* enjoy!

https://klingon.lostexiles.net/screenshots/20150806_nvidia_settings_SFC_1.png
https://klingon.lostexiles.net/screenshots/20150806_nvidia_settings_SFC_2.png
https://klingon.lostexiles.net/screenshots/20150806_SFCOP_with_tweaked_settings.png

Tuning SFC to play on modern hardware

2025-10-10T16:37:15Z

Firesoul: /* use dgVoodoo2 to manage non-existant 3D settings */

Note: this section was added on 2015-08-06. SFC2 is 15 years by now.
First some facts:
* SFC doesn't really optimize graphic output for better play
** no anti-aliasing nor anisotropic filtering
* SFC2 has been around for 15 years or more.
** based on Moore's law, that means the average computer is about 1000x more powerful/efficient at the same cost as it was back around Y2K.
* graphics drivers these days have great capabilities.

== Missing Windows Registry Entries ==

The following is for SFC2:OP. I did not research for EAW.

The game's installer was written in the 32-bit days, and did not account for 64-bit systems that supported 32-bit. To solve this, a couple of Registry entries need to be added so that other resources can find the game's installation.

This is needed for the additional installers like OP+'s, or the missionpacks.

Make a ''something.reg'' file, and change the directory paths I list to where your SFC install is. You need both entries. Double the backslashes (\\).
One's for 32-bit, the other is for 64-bit.

Then double-click on the file to import to your system. You need to be Administrator.

For example, if you installed SFC2:OP into ''D:\SFC\Starfleet Command Orion Pirates'' ..then..
----
[HKEY_LOCAL_MACHINE\SOFTWARE\Taldren\Starfleet Command Orion Pirates]
"Directory"="D:\\SFC\\Starfleet Command Orion Pirates"

[HKEY_LOCAL_MACHINE\SOFTWARE\WOW6432Node\Taldren\Starfleet Command Orion Pirates]
"Directory"="D:\\SFC\\Starfleet Command Orion Pirates"
----

== Modern DirectX compatibility ==

SFC2, whether it's SFC2:OP or SFC2:EAW, are built on DirectX7 or DirectX8. Current (this bit is written in 2025) DirectX is 12, but there's still some 11 around. It's incompatible.

There's a solution! Someone wrote a DirectX adapter. It's called dgVoodoo2.
See: [https://dege.freeweb.hu/dgVoodoo2/ https://dege.freeweb.hu/dgVoodoo2/]

To install dgVoodoo2, please follow their installation instructions as per their documentation. In my case, it was a matter of dropping the right files in the same folder/directory as starfleetop.exe and using their UI tool to configure how it should behave:

https://klingon.lostexiles.net/screenshots/dgvoodoo2_configure_example.png

== Consider the community patch/versions ==

Visit the Hot&Spicy forums, for SFC2:OP 2.5.6.4.
[https://hotandspicyforums.com/starfleet-command-2-orion-pirates-v2-564-august-20-t25292.html https://hotandspicyforums.com/starfleet-command-2-orion-pirates-v2-564-august-20-t25292.html]

== Aspect ratio and scaling ==

If you have a modern system like me, then you probably have a 16x9 ratio monitor. Mine is 2560x1440, and this monitor isn't current edge tech. SFC, SFC2:EAW and SFC:OP were all designed for 4:3 ratio monitors.

''The following are ALL 4:3 ratio resolutions...''
https://klingon.lostexiles.net/screenshots/20150807_EzINI_4x3_resolutions.png

This means you're probably playing SFC:OP with a stretched image. You can force the monitor to display the image scaled proportionally by adjusting your scaling and aspect ratio.

Note: my monitor could not, but my video card can. Thus:
https://klingon.lostexiles.net/screenshots/20150806_nvidia_settings_scaling_GPU_override.png

== use dgVoodoo2 to manage non-existant 3D settings ==

SFC does not.. have.. anti-aliasing. I guess it's that old. However, dgVoodoo2 does provide a tab to manager/override/force some settings like Anti-Aliasing. You can also force the Resolution to use. If you're going to do that, you should use the Hot&Spicy build of SFC and match the resolution setting there too.
ie: a 16:9 resolution of 1920x1080

It's under the DirectX tab.

https://klingon.lostexiles.net/screenshots/dgvoodoo2_force_3d_settings.png

== Without dgVoodoo2 -- Manage 3D Settings ==

SFC does not have any 3D settings of importance. Your video card management tools might. In this example (mine), Nvidia drivers can have overrides based on what executable you're launching.

'''This is important: Make sure you select the SFC:OP executable for these settings!'''

Here's my suggestions:
* anti-aliasing
** don't touch FXAA Anti-aliasing. That just fuzzies up the image.
** otherwise go ahead, crank it up. I've set it to CSAA Anti-Aliasing with as much sampling possible.
** research! Go online and google up what anti-aliasing does.
* Anisotropic filtering
** affects crispness of textures
** also crank it up.
* texture quality
** set those to very high quality of course.
* test test test!
* enjoy!

https://klingon.lostexiles.net/screenshots/20150806_nvidia_settings_SFC_1.png
https://klingon.lostexiles.net/screenshots/20150806_nvidia_settings_SFC_2.png
https://klingon.lostexiles.net/screenshots/20150806_SFCOP_with_tweaked_settings.png

Tuning SFC to play on modern hardware

2025-10-10T16:36:41Z

Firesoul:

Note: this section was added on 2015-08-06. SFC2 is 15 years by now.
First some facts:
* SFC doesn't really optimize graphic output for better play
** no anti-aliasing nor anisotropic filtering
* SFC2 has been around for 15 years or more.
** based on Moore's law, that means the average computer is about 1000x more powerful/efficient at the same cost as it was back around Y2K.
* graphics drivers these days have great capabilities.

== Missing Windows Registry Entries ==

The following is for SFC2:OP. I did not research for EAW.

The game's installer was written in the 32-bit days, and did not account for 64-bit systems that supported 32-bit. To solve this, a couple of Registry entries need to be added so that other resources can find the game's installation.

This is needed for the additional installers like OP+'s, or the missionpacks.

Make a ''something.reg'' file, and change the directory paths I list to where your SFC install is. You need both entries. Double the backslashes (\\).
One's for 32-bit, the other is for 64-bit.

Then double-click on the file to import to your system. You need to be Administrator.

For example, if you installed SFC2:OP into ''D:\SFC\Starfleet Command Orion Pirates'' ..then..
----
[HKEY_LOCAL_MACHINE\SOFTWARE\Taldren\Starfleet Command Orion Pirates]
"Directory"="D:\\SFC\\Starfleet Command Orion Pirates"

[HKEY_LOCAL_MACHINE\SOFTWARE\WOW6432Node\Taldren\Starfleet Command Orion Pirates]
"Directory"="D:\\SFC\\Starfleet Command Orion Pirates"
----

== Modern DirectX compatibility ==

SFC2, whether it's SFC2:OP or SFC2:EAW, are built on DirectX7 or DirectX8. Current (this bit is written in 2025) DirectX is 12, but there's still some 11 around. It's incompatible.

There's a solution! Someone wrote a DirectX adapter. It's called dgVoodoo2.
See: [https://dege.freeweb.hu/dgVoodoo2/ https://dege.freeweb.hu/dgVoodoo2/]

To install dgVoodoo2, please follow their installation instructions as per their documentation. In my case, it was a matter of dropping the right files in the same folder/directory as starfleetop.exe and using their UI tool to configure how it should behave:

https://klingon.lostexiles.net/screenshots/dgvoodoo2_configure_example.png

== Consider the community patch/versions ==

Visit the Hot&Spicy forums, for SFC2:OP 2.5.6.4.
[https://hotandspicyforums.com/starfleet-command-2-orion-pirates-v2-564-august-20-t25292.html https://hotandspicyforums.com/starfleet-command-2-orion-pirates-v2-564-august-20-t25292.html]

== Aspect ratio and scaling ==

If you have a modern system like me, then you probably have a 16x9 ratio monitor. Mine is 2560x1440, and this monitor isn't current edge tech. SFC, SFC2:EAW and SFC:OP were all designed for 4:3 ratio monitors.

''The following are ALL 4:3 ratio resolutions...''
https://klingon.lostexiles.net/screenshots/20150807_EzINI_4x3_resolutions.png

This means you're probably playing SFC:OP with a stretched image. You can force the monitor to display the image scaled proportionally by adjusting your scaling and aspect ratio.

Note: my monitor could not, but my video card can. Thus:
https://klingon.lostexiles.net/screenshots/20150806_nvidia_settings_scaling_GPU_override.png

=== use dgVoodoo2 to manage non-existant 3D settings ===

SFC does not.. have.. anti-aliasing. I guess it's that old. However, dgVoodoo2 does provide a tab to manager/override/force some settings like Anti-Aliasing. You can also force the Resolution to use. If you're going to do that, you should use the Hot&Spicy build of SFC and match the resolution setting there too.
ie: a 16:9 resolution of 1920x1080

It's under the DirectX tab.

https://klingon.lostexiles.net/screenshots/dgvoodoo2_force_3d_settings.png

== Without dgVoodoo2 -- Manage 3D Settings ==

SFC does not have any 3D settings of importance. Your video card management tools might. In this example (mine), Nvidia drivers can have overrides based on what executable you're launching.

'''This is important: Make sure you select the SFC:OP executable for these settings!'''

Here's my suggestions:
* anti-aliasing
** don't touch FXAA Anti-aliasing. That just fuzzies up the image.
** otherwise go ahead, crank it up. I've set it to CSAA Anti-Aliasing with as much sampling possible.
** research! Go online and google up what anti-aliasing does.
* Anisotropic filtering
** affects crispness of textures
** also crank it up.
* texture quality
** set those to very high quality of course.
* test test test!
* enjoy!

https://klingon.lostexiles.net/screenshots/20150806_nvidia_settings_SFC_1.png
https://klingon.lostexiles.net/screenshots/20150806_nvidia_settings_SFC_2.png
https://klingon.lostexiles.net/screenshots/20150806_SFCOP_with_tweaked_settings.png

Tuning SFC to play on modern hardware

2025-10-08T19:54:23Z

Firesoul: /* Modern DirectX compatibility */

Note: this section was added on 2015-08-06. SFC2 is 15 years by now.
First some facts:
* SFC doesn't really optimize graphic output for better play
** no anti-aliasing nor anisotropic filtering
* SFC2 has been around for 15 years or more.
** based on Moore's law, that means the average computer is about 1000x more powerful/efficient at the same cost as it was back around Y2K.
* graphics drivers these days have great capabilities.

== Missing Windows Registry Entries ==

The following is for SFC2:OP. I did not research for EAW.

The game's installer was written in the 32-bit days, and did not account for 64-bit systems that supported 32-bit. To solve this, a couple of Registry entries need to be added so that other resources can find the game's installation.

This is needed for the additional installers like OP+'s, or the missionpacks.

Make a ''something.reg'' file, and change the directory paths I list to where your SFC install is. You need both entries. Double the backslashes (\\).
One's for 32-bit, the other is for 64-bit.

Then double-click on the file to import to your system. You need to be Administrator.

For example, if you installed SFC2:OP into ''D:\SFC\Starfleet Command Orion Pirates'' ..then..
----
[HKEY_LOCAL_MACHINE\SOFTWARE\Taldren\Starfleet Command Orion Pirates]
"Directory"="D:\\SFC\\Starfleet Command Orion Pirates"

[HKEY_LOCAL_MACHINE\SOFTWARE\WOW6432Node\Taldren\Starfleet Command Orion Pirates]
"Directory"="D:\\SFC\\Starfleet Command Orion Pirates"
----

== Modern DirectX compatibility ==

SFC2, whether it's SFC2:OP or SFC2:EAW, are built on DirectX7 or DirectX8. Current (this bit is written in 2025) DirectX is 12, but there's still some 11 around. It's incompatible.

There's a solution! Someone wrote a DirectX adapter. It's called dgVoodoo2.
See: [https://dege.freeweb.hu/dgVoodoo2/ https://dege.freeweb.hu/dgVoodoo2/]

To install dgVoodoo2, please follow their installation instructions as per their documentation. In my case, it was a matter of dropping the right files in the same folder/directory as starfleetop.exe and using their UI tool to configure how it should behave:

https://klingon.lostexiles.net/screenshots/dgvoodoo2_configure_example.png

== Consider the community patch/versions ==

Visit the Hot&Spicy forums, for SFC2:OP 2.5.6.4.
[https://hotandspicyforums.com/starfleet-command-2-orion-pirates-v2-564-august-20-t25292.html https://hotandspicyforums.com/starfleet-command-2-orion-pirates-v2-564-august-20-t25292.html]

== Aspect ratio and scaling ==

If you have a modern system like me, then you probably have a 16x9 ratio monitor. Mine is 2560x1440, and this monitor isn't current edge tech. SFC, SFC2:EAW and SFC:OP were all designed for 4:3 ratio monitors.

''The following are ALL 4:3 ratio resolutions...''
https://klingon.lostexiles.net/screenshots/20150807_EzINI_4x3_resolutions.png

This means you're probably playing SFC:OP with a stretched image. You can force the monitor to display the image scaled proportionally by adjusting your scaling and aspect ratio.

Note: my monitor could not, but my video card can. Thus:
https://klingon.lostexiles.net/screenshots/20150806_nvidia_settings_scaling_GPU_override.png

== Manage 3D Settings ==

SFC does not have any 3D settings of importance. Your video card management tools might. In this example (mine), Nvidia drivers can have overrides based on what executable you're launching.

'''This is important: Make sure you select the SFC:OP executable for these settings!'''

Here's my suggestions:
* anti-aliasing
** don't touch FXAA Anti-aliasing. That just fuzzies up the image.
** otherwise go ahead, crank it up. I've set it to CSAA Anti-Aliasing with as much sampling possible.
** research! Go online and google up what anti-aliasing does.
* Anisotropic filtering
** affects crispness of textures
** also crank it up.
* texture quality
** set those to very high quality of course.
* test test test!
* enjoy!

https://klingon.lostexiles.net/screenshots/20150806_nvidia_settings_SFC_1.png
https://klingon.lostexiles.net/screenshots/20150806_nvidia_settings_SFC_2.png
https://klingon.lostexiles.net/screenshots/20150806_SFCOP_with_tweaked_settings.png

Tuning SFC to play on modern hardware

2025-10-08T17:32:15Z

Firesoul:

Note: this section was added on 2015-08-06. SFC2 is 15 years by now.
First some facts:
* SFC doesn't really optimize graphic output for better play
** no anti-aliasing nor anisotropic filtering
* SFC2 has been around for 15 years or more.
** based on Moore's law, that means the average computer is about 1000x more powerful/efficient at the same cost as it was back around Y2K.
* graphics drivers these days have great capabilities.

== Missing Windows Registry Entries ==

The following is for SFC2:OP. I did not research for EAW.

The game's installer was written in the 32-bit days, and did not account for 64-bit systems that supported 32-bit. To solve this, a couple of Registry entries need to be added so that other resources can find the game's installation.

This is needed for the additional installers like OP+'s, or the missionpacks.

Make a ''something.reg'' file, and change the directory paths I list to where your SFC install is. You need both entries. Double the backslashes (\\).
One's for 32-bit, the other is for 64-bit.

Then double-click on the file to import to your system. You need to be Administrator.

For example, if you installed SFC2:OP into ''D:\SFC\Starfleet Command Orion Pirates'' ..then..
----
[HKEY_LOCAL_MACHINE\SOFTWARE\Taldren\Starfleet Command Orion Pirates]
"Directory"="D:\\SFC\\Starfleet Command Orion Pirates"

[HKEY_LOCAL_MACHINE\SOFTWARE\WOW6432Node\Taldren\Starfleet Command Orion Pirates]
"Directory"="D:\\SFC\\Starfleet Command Orion Pirates"
----

== Modern DirectX compatibility ==

SFC2, whether it's SFC2:OP or SFC2:EAW, are built on DirectX7 or DirectX8. Current (this bit is written in 2025) DirectX is 12, but there's still some 11 around. It's incompatible.

There's a solution! Someone wrote a DirectX adapter. It's called dgVoodoo2.
See: [https://dege.freeweb.hu/dgVoodoo2/ https://dege.freeweb.hu/dgVoodoo2/]

To install dgVoodoo2, please follow their installation instructions as per their documentation. In my case, it was a matter of dropping the right files in the same folder/directory as starfleetop.exe and using their UI tool to configure how it should behave:

== Consider the community patch/versions ==

Visit the Hot&Spicy forums, for SFC2:OP 2.5.6.4.
[https://hotandspicyforums.com/starfleet-command-2-orion-pirates-v2-564-august-20-t25292.html https://hotandspicyforums.com/starfleet-command-2-orion-pirates-v2-564-august-20-t25292.html]

== Aspect ratio and scaling ==

If you have a modern system like me, then you probably have a 16x9 ratio monitor. Mine is 2560x1440, and this monitor isn't current edge tech. SFC, SFC2:EAW and SFC:OP were all designed for 4:3 ratio monitors.

''The following are ALL 4:3 ratio resolutions...''
https://klingon.lostexiles.net/screenshots/20150807_EzINI_4x3_resolutions.png

This means you're probably playing SFC:OP with a stretched image. You can force the monitor to display the image scaled proportionally by adjusting your scaling and aspect ratio.

Note: my monitor could not, but my video card can. Thus:
https://klingon.lostexiles.net/screenshots/20150806_nvidia_settings_scaling_GPU_override.png

== Manage 3D Settings ==

SFC does not have any 3D settings of importance. Your video card management tools might. In this example (mine), Nvidia drivers can have overrides based on what executable you're launching.

'''This is important: Make sure you select the SFC:OP executable for these settings!'''

Here's my suggestions:
* anti-aliasing
** don't touch FXAA Anti-aliasing. That just fuzzies up the image.
** otherwise go ahead, crank it up. I've set it to CSAA Anti-Aliasing with as much sampling possible.
** research! Go online and google up what anti-aliasing does.
* Anisotropic filtering
** affects crispness of textures
** also crank it up.
* texture quality
** set those to very high quality of course.
* test test test!
* enjoy!

https://klingon.lostexiles.net/screenshots/20150806_nvidia_settings_SFC_1.png
https://klingon.lostexiles.net/screenshots/20150806_nvidia_settings_SFC_2.png
https://klingon.lostexiles.net/screenshots/20150806_SFCOP_with_tweaked_settings.png

Tuning SFC to play on modern hardware

2025-10-08T17:19:01Z

Firesoul:

Tuning SFC to play on modern hardware

2025-10-08T17:13:56Z

Firesoul:

FireSoul's SFC:OP BootStrap list

2025-10-08T17:13:08Z

Firesoul:

So you want to know how I set up SFC:OP? Ok!

== Update your DirectX ==

Make sure you have the right DirectX support on your machine. The game itself was shipped with DirectX 8 installables. DO NOT USE THOSE, THEY ARE ANCIENT. If you're on Windows XP or older, use DirectX 9.0c.

That said, newer Windows was NOT shipped with DirectX support for ''older'' games. You'll need to run an updater from MicroSoft to do so. This installer/updater will examine your system's DirectX libraries, both old and new, and make sure you have all of them.
 See: https://www.microsoft.com/en-us/download/details.aspx?id=35

== Install SFC:OP ==

* Find your CD.
* Find your CD-Key.
* Install.

== Patch to SFC:OP 2.5.5.2 ==

* Download the patch.
** [https://klingon.lostexiles.net/sources_and_utils/patches/SFCOP_Patch_2500-2552.exe SFCOP_Patch_2500-2552.exe]
* Install the patch.

What, you don't have 2.5.0.0 but something else? See here: [[All SFC Patches and ServerKits]]

== Run the game to type the CD-Key ==

* Make sure you have your CD-Key on paper or something you can read from
** copy-paste won't work here
* just start it up, and type in your Key.
* exit the game when you're done.

== Install Latest OP+ ==

See: [[SFC:OP Plus Refit]]

* Get the latest OP+
** .. or whatever people are playing. I suggest the latest.
* Install it.

== Set up your preferences with EzINI ==

* get [https://klingon.lostexiles.net/sources_and_utils/EzINI.exe EzINI]
* run EzINI
* Select Orion Pirates (if necessary)
* set up your:
** graphics resolution
** show damage
** sound settings
** multiplayer game player name
** default multiplayer game name
** default difficulty level
** etc etc etc

=== My suggestions for EzINI settings===

* Video
** Resolution: 1024 x 768
* Audio
** Music Volume --- OFF
*** That's completely optional. You can leave it on if you want.
** Max Channels: 64 (max)
** Crew Sounds: Maximum
* Multiplayer
** Set up your Default Multiplayer Player Name
** Set up your Game Name
** OPTIONAL: click on Multiplayer Hidden Race
** OPTIONAL: click on Multiplayer Hidden BPV
* Misc
** Difficulty: Admiral
** turn ON Volley Information

== Install Co-Op Ace ==

See: [[Co-op Ace for SFC:EAW and SFC:OP]]

* Get the latest coopace
** Currently [https://klingon.lostexiles.net/sources_and_utils/coop-ace-4.0.exe Coopace 4.0]
* install it.

== Customize Co-Op Ace==

* run the Coop-Ace Customizer from your start menu
** Set the Difficulty to around 1.5
*** or whatever you prefer. I got 1.7 right now
** Set the AI Intelligence to Admiral
** Races: single
** uncheck all the pirates
*** up to you, but remember, pirates are weaker
** Turn ON 'Force selection of ships created in current era'
*** This will improve the gaming experience, especially since you've installer OP+
** Turn ON 'Use Enhanced Shiplist API Settings'

== Fests+ ==

See: [[Fests+ for SFC:OP]]

* download the [https://klingon.lostexiles.net/fests+/Fests+_11.exe Fests+] installer
* install it
* download the extra mission: [https://klingon.lostexiles.net/fests+/Mul_Battlefest+Intense.scr Battlefest+ Intense]
* install it
** Find your SFC install directory
** Hint! May be: ''C:\Program Files (x86)\Taldren Software Inc\Starfleet Command Orion Pirates''
** Go into Assets\Scripts\
** copy Mul_Battlefest+Intense.scr there

== Missions Refit pack ==

See: [[https://klingon.lostexiles.net/mediawiki/index.php?title=SFC:OP_Missions_Refit SFC:OP Missions Refit]]

* download the [https://klingon.lostexiles.net/Missions_Refit/SFCOP_MissionsRefit_15_20121022222638.exe SFCOP_MissionsRefit_15_20121022222638.exe] installer
* install it

== Set up a key to launch all the fighters ==

* Launch the game
* Click on the 'Hot Keys' Button
** never BEEN here, huh?!
* click on 'Weapons'
* put in a ket for Launch Fighters.
** I tend to use 'L' for it.
*** 'L' is usually the Defense panel shortcut, which I never use via HotKey.
* exit the game to make sure your settings change are saved

If you screwed up, no problem! Go pick up a fresh copy of [https://klingon.lostexiles.net/sources_and_utils/orig/op/25410/bindings.ini bindings.ini] from [[SFC-related missions, sources, patches and misc utilities]].

Note, 2015-08-08: changing bindings didn't stick for me on my Windows 7 machine. :-/ I had to edit the file manually with notepad. To do '''that''', I needed to grant myself access to the files.

for example:
https://klingon.lostexiles.net/screenshots/20150808_win7_grant_yourself_full_access.png

Then go edit the file directly with notepad. It's going to be in under your SFC game's install directory, as Assets\Specs\bindings.ini

The changes:
* "LaunchFighters= " to "LaunchFighters=L"
* "Defense=L" to "Defense= "
** That's: Defense=<space>

== Dynaverse 2 Directory Server Updater ==

The Dynaverse 2 Server list updater is optional: I don't know if there still are D2 servers for SFC:OP out there, but in case there are, you can use this:

* [https://www.dynaverse.net/downloads.php?id=56&game=SFC2%20OP#download D2 Directory Server Updater]
* Run it.

== Set up your FireWall(s) to play online ==

=== Gaming host's firewall (AKA Windows Firewall) ===

Open your Windows Firewall for SFC:OP on your gaming machine.
 Note: on Windows Vista and Windows 7, it's under ''"Windows Firewall"'', not ''"Windows Firewall and Advanced Security"''. You'll find an option called ''"Allow a program or feature through Windows Firewall"''. Click on that to see the list of applications and games allowed to go through your firewall. Allow ''"StarFleet Command Orion Pirates"''.

=== SFC networking ports used ===

Do you use a router? If so, you'll need to set up either a DMZ to your computer, or at least some portforward rules so that you can play SFC with others online. I'm sorry if I'm no help here in telling you HOW to do it because I don't know what you have.

Here are the ports to forward to your PC from the router:

* To join a game:
** port 47624, both TCP and UDP

* to host a game:
** port range: 2300-2400
** both TCP and UDP

* For SFC3
** port 6073, both TCP and UDP

* to run an SFC server
** ''(obviously optional)''
** port 27100, both TCP and UDP
** port 3306, both TCP and UDP
*** Scary! That's usually a MySQL server's port!
** port 15100, both TCP and UDP

=== Networking Ports for other related software ===

* to play on mplayer.com
** port range 8000-9000
** both TCP and UDP

* to play on GameSpy
** port 13139, both TCP and UDP

== Tuning SFC to play on modern hardware ==

* Please refer to this following mini-guide I wrote for myself:
** [[Tuning SFC to play on modern hardware ]]

== Visit the Dynaverse.net forums ==

* See :[https://www.dynaverse.net/forum/index.php https://www.dynaverse.net/forum/index.php]
** Best place to find players, new tools, whatever.

How to compile/build SFC2 EAW or OP Missions

2025-10-08T17:12:03Z

Firesoul:

== Software Pre-requirements ==

=== Windows 95/98/Me/NT/2000/XP 32bit ===

The StarFleet Command 2 games were compiled on a 32-bit host, which was quite normal for the days around 1999-2001. Compiling the missions scripts will require the same. Additionally, it's necessary to install certain support software onto this build environment. I do NOT recommend you use your primary computer to do this.

FireSoul's example:
I have a home PC with Windows Vista Home Premium 64, and thus decided not to use this as my build OS. I decided to look into using a Virtual Machine environment, setting up Windows XP SP3.

My Virtual Machine specs:
* VMWare Player
** Free for non-commercial use.
** See: [https://www.vmware.com/products/player/ https://www.vmware.com/products/player/]
** ALTERNATIVE: Virtual PC 2007

* 1.5GB of memory
** I could do with far less, but I also use 3DSMax R5 to create/modify my SFC 3D models

* 40 GB diskspace
** diskspace is cheap now-a-days. I have a 1TB drive in the main host.

* 2 CPU cores
** I have a Intel I7 Quad Core system. I decided to increase the number of cores in the VM from the default of 1 to 2 so that I can do other stuff while it compiles.

=== Microsoft Visual C++ 6.0 ===

It has to be Microsoft Visual C++ 6.0. Nothing else will work.

No .NET.
No "2005" or younger.

MSVC++ 6.0. Really. I wish you luck in your search! :)

==== Service Pack 5 for MSVC++ 6.0 ====

IMPORTANT! Do not use Service Pack 6!

I cannot legally redistribute SP5 on my site, but I definitely have kept a copy around. It is true that SP6 is far easier to find, but it will SCREW THINGS UP if you install it!

The filename is ''vs6sp5.exe''. It's 130 MB (136,410,832 bytes) in size.

Again, good luck!

=== EAW Scripting API ===

This is the part that links the sources to SFC2 EAW: the mission API. It will contain library files, c++ header files and some template mission scripts.

Be sure to follow the installation instructions!

* download: [https://klingon.lostexiles.net/sources_and_utils/SFC2_API_R1.3.zip SFC2_API_R1.3.zip]
* also see: [[SFC-related_missions,_sources,_patches_and_misc_utilities]]

=== OP API R2.2 - Scripting API ===

This is the part that links the sources to SFC OP: the mission API. It will contain library files, c++ header files and some template mission scripts.

Be sure to follow the installation instructions!

* download: [https://klingon.lostexiles.net/sources_and_utils/SFCOP_API_R2.zip SFCOP_API_R2.zip]
** Installation instructions: [[OP API R2.2 readme.txt]]
* also see: [[SFC-related_missions,_sources,_patches_and_misc_utilities]]

=== ShipList API ===

The game's own API is very unhelpful when it comes to making proper ship picks. I strongly recommend installing, understanding and using the ShipList API so that you can create better missions.

* download: [https://klingon.lostexiles.net/sources_and_utils/ShipList.20050118.zip ShipList.20050118.zip]
* also see: [[SFC-related_missions,_sources,_patches_and_misc_utilities]]

=== Other APIs.. maybe your own? ===

I made my own API kit in the hopes that it might help others. It includes OP R2.2 and a ShipList API revision from 2003.

* download:
** [https://klingon.lostexiles.net/sources_and_utils/FireSoul_EAW_build_env-20031117.zip FireSoul_EAW_build_env-20031117.zip]
** [https://klingon.lostexiles.net/sources_and_utils/FireSoul_OP_build_env-20031117.zip FireSoul_OP_build_env-20031117.zip]
* again, also see: [[SFC-related_missions,_sources,_patches_and_misc_utilities]]

== Installation Order ==

# the OS
# the OS's service packs
# all the OS's windows updates
# MSVC++ 6.0
# VC6's Service Pack 5
# the API
# the auxiliary APIs and mission scripts

== Setting up the API ==

See the API's own documentation.

'''IMPORTANT''': the API has some components that need to be manually installed on top of VC6++ SP5. Again, just follow the instructions in the included ''readme.txt''.

Fests+ for SFC:OP

2025-10-08T17:11:37Z

Firesoul:

Tired of the same ol' BattleFests? Sick of watching some enemy getting a XFF when you start with some poor early era FF? .. well.. this should solve your problems! The Fests+ package includes 4 mission scripts for SFC:OP. They are more intelligent than the original Fests scripts (no offense, dear author) and more focused.

== Fests+ 1.1 for OP ==

=== Downloads ===

* [https://klingon.lostexiles.net/fests+/Fests+_11.exe Fests+_11.exe]
** Installer, for SFC:OP
** size: 307KB
* [https://klingon.lostexiles.net/fests+/fests+_20040228.zip fests+_20040228.zip]
** sources
** size: 272KB

=== Scripts included ===

* BattleFest+
** 6 ships: from small to large
*** FF, DD/DW, CL, CA/NCA, BCH, DN
* BattleFestLite+
** 3 ships: FF, CA, DN
* TinyFest+
** 3 ships: FF, DD/DW, CL
* SlugFest+
** 3 ships: large ships: CA, BCH, DN.
** ''exception, in late era'': BCH, DN, BB!

=== What's different compared to the old BattleFests? ===

* The hullclasses have been expanded
** There are, like before, 6 ship classes in the battlefest:
*** Frigate
*** Destroyer
*** Light Cruiser
*** Heavy Cruiser
*** Heavy BattleCruiser
*** Dreadnought
** .. however, these classes have been expanded:
*** Frigate
*** Destroyer '''''AND''''' War Destroyers
*** Light Cruiser
*** Heavy Cruiser AND New Heavy Cruiser
*** Heavy BattleCruiser
*** Dreadnought

* The ships chosen will be Era-complient.
** X1 ships, like those in OP+, are grouped with the Advanced Era ships: there aren't enough of those.

* 2nd pass matching on ship selection failure
** If a ship class from a given era can't be selected, a close match will be selected. This will be from a smaller or larger class, or the same class from a near era.

* Late-era Slugfests are NASTY-FUN!
** If you decide to play a SlugFest+ in Late Era, the 3 ships chosen will be a BCH, DN and BB.

== BattleFest+Intense ==

Released: 2010-01-09.
(NO installer yet)

=== Downloads ===

* [https://klingon.lostexiles.net/fests+/Mul_Battlefest+Intense.scr Mul_Battlefest+Intense.scr]
** mission script. Goes into Assets\Scripts\
** size: 454KB
* [https://klingon.lostexiles.net/fests+/Mul_Battlefest+Intense.zip Mul_Battlefest+Intense.zip]
** source code
** size: 154KB

=== What's different? ===

Differences: You take a Bfest+, and..

* added 1 more hull class: Battleship
*** Frigate
*** Destroyer '''''AND''''' War Destroyers
*** Light Cruiser
*** Heavy Cruiser AND New Heavy Cruiser
*** Heavy BattleCruiser
*** Dreadnought
*** Battleship

* every selected player gets an AI partner of the same race (one they cannot control)
** ie:
*** in a 2-player game, 1 vs 1, it makes it a 2 vs 2.
*** in a 6-player game, FreeForAll (FFA), It will make it a 2 vs 2 vs 2 vs 2 vs 2 vs 2 game.
*** in a 6-player game, 3 vs 3, it makes it a 6 vs 6

SFC:EAW missions for SFC:OP

2025-10-08T17:10:50Z

Firesoul:

=== Recommendations ===

These are the ''stock'' recompiled EAW missions for SFC:OP. I '''strongly''' recommend using the Missions Refit versions along with OP+.
* [[SFC:OP Plus Refit]]
* [[SFC:OP Missions Refit]]

=== Packages ===
* NEW: See Missions Refit: [[SFC:OP_Missions_Refit]]
** All of the EAW missions rebuilt to properly use OP+, but also backwards compatible.
* OLD: [https://klingon.lostexiles.net/EAW_missions/EAW_Campaigns_for_OP-20030330.exe EAW_Campaigns_for_OP-20030330.exe]
** the SFC:EAW single player campaigns compiled for SFC:OP.
** size: 3.0 MB
*** Campaign files have been modified to include SFC:OP missions not present in SFC:EAW.
*** Includes the Sulu Missions
* [https://klingon.lostexiles.net/EAW_missions/Sulu_Bonus_missions_for_OP-20021124.zip Sulu_Bonus_missions_for_OP-20021124.zip]
** Sulu bonus missions, without the Sulu voice recordings.
** size: 735KB
* [https://klingon.lostexiles.net/sources_and_utils/EvilDave/NW_EAWtoOP_Campaigns.zip NW_EAWtoOP_Campaigns.zip]
** .MCT Campaign files for OP
** mixes EvilDave packages and EAW for OP campaigns, for the BEST single-player experience!
** [https://klingon.lostexiles.net/EAW_missions/howto_install_20030617.txt howto_install_20030617.txt]
*** instructions on how to install the single player campaigns mixed with the EvilDave missions. Updated: 20030617.

Co-op Ace for SFC:EAW and SFC:OP

2025-10-08T17:10:17Z

Firesoul:

== Introduction ==

In this multiplayer script up to 6 people confront a massive randomly generated enemy armada. The enemy is customizable my the game host through an external configuration program. The enemy's difficulty level, race, and hull class can be controlled. This script is absolutely excellent for race-specific training as well as team action training - plus it's a ton of fun!

''Note: This page originally lived at: http://khoromag.org/taldren/scripts/coopace.html . MagnumMan's site has been dead for a while now.''

== Downloads ==

=== Installer ===

Note: FireSoul has made a single installer that will install Co-op Ace for either EAW, OP, or both depending on which games you have installed on your computer. You only need to download and run this installer once even if you have both games.

* [https://klingon.lostexiles.net/sources_and_utils/coop-ace-4.0.exe coop-ace-4.0.exe]
** for both SFC:EAW and SFC:OP, size: 407KB
** note! source code lost!
** [https://klingon.lostexiles.net/sources_and_utils/Mul_CoopAce.scr Mul_CoopAce.scr]
*** in case the installer gives trouble.
*** copy it into Assets/Scripts/
*** it's not enough to host a game. You need a working coopcustomizer for that.

Note: New OSes, like Windows 10, 11
For the installer (and customizer executable) to work on newer OSes, you need to have the following Registry keys within your system:
(please adjust the target directory to your system's)

<nowiki>
[HKEY_LOCAL_MACHINE\SOFTWARE\Taldren\Starfleet Command Orion Pirates]
"Directory"="C:\\Users\\msliv\\Desktop\\SFC\\Starfleet Command Orion Pirates"
</nowiki>

<nowiki>
[HKEY_LOCAL_MACHINE\SOFTWARE\WOW6432Node\Taldren\Starfleet Command Orion Pirates]
"Directory"="C:\\Users\\msliv\\Desktop\\SFC\\Starfleet Command Orion Pirates"
</nowiki>

You also need to make sure the files in the SFCOP directory aren't set to read-only.

=== Sources and stuff ===

The sources to Coop-ace 4.0 are lost. sorry.

* [https://klingon.lostexiles.net/sources_and_utils/Mul_CoopAce.321.20040727.zip Mul_CoopAce.321.20040727.zip] size: 496k
** requires [https://klingon.lostexiles.net/sources_and_utils/ShipList.20031117.zip ShipList.20031117.zip] to build. Can be compiled for both EAW and OP.

== Reviews and comments ==

"'The Co-op' script developed for Starfleet Command II: Empires at War, is a must-have training tool for those who enjoy group actions within SFC2. Not only will it be useful for Dynaverse II and other 'Campaign' systems, but it's fun as hell to play to boot! With a completely configurable setup to enable anyone from the newbie first timer to hardend veteran, it's guaranteed to satisfy! Although it can be used for solo setup, it truly shines when you get a bunch of your buddies together for some old fashioned butt [sic] kicking fun." - Dennis Greene, aka SFCShadow, author of [https://www.amazon.com/gp/product/074400022X Star Trek Starfleet Command II: Empires at War Official Strategy Guide]

"MagnumMan has managed to not only master the scripting API, but deliver to us possibly the best player made script for SFC2, the Multiplayer Co-op Ace script." - RedHotChiliDog Guest Review, Black Ops Station.

"I would have to say that MagnumMan-iCoP has scored a huge hit with this script." - Captain Stoneyface, Black Ops Station.

"MagnumMan once again delivers in this script! Perfect for those nights when FFA just isnt enough - now the whole fleet can get gutted together ! Top notch Work!" - Admiral Frey_XC, [[https://www.xenocorp.net XenoCorp® Inc.]]

== Revision History ==

* 4.0
** January 24, 2005
** Features and work by FireSoul:
*** Much smaller installer.
** Lots of new options, better integration with add-on Ship Lists.

* 3.2.1
** July 27, 2004
** Features and work by FireSoul:
*** Improvements to game load strategy to reduce drops.
*** Automatic red alert after 8 seconds in.

* 3.2
** November 25, 2003
** Features and work by FireSoul:
*** Speed improvements! Faster load times.
*** Mod support directly in the OP customizer!
*** Maximum difficult ratio increased from 2.00 to 3.00.
*** Selectable AI enemy era.

* 3.0.1
** November 12, 2002
** Features and work by FireSoul:
*** Fixed an advanced era date range handling problem (OP only).

* 3.0.0
** October 17, 2002
** Features and work by FireSoul and Strafer:
*** Enhanced enemy fleet selection and generation.
*** Increased game stability.

* 2.6.3
** September 2, 2002
** Features and work by FireSoul:
*** Fixed problem where game started with no enemy ships in EAW if OP was not installed.
*** Fixed game startup sequence to reduce the number of drops.

* 2.6
** August 8, 2002
** Features and work by FireSoul:
*** Fixed early game end bug.
*** improved SpareParts calculations.
*** 'zombie' AI on host drops fixed.
*** Terrain: Dust Clouds added.
*** Terrain: Asteroid Belt improved.
*** Era-based enemies: now uses the game setting for era [OP Only]

* 2.5.2
** July 21, 2002
** Features and work by FireSoul:
*** Enemy Team selection optimized further.
*** Faster entry into the game (less crashes due to timeout).
*** Enemy ships would get no loadouts if enemy ships BPV after selection was '0' (no leftovers).
*** CoopAce for EAW loaded OP's coopace customizer settings.
*** New terrain. "Asteroid Belt".

* 2.5
** July 17, 2002
** Features and work by FireSoul:
*** More intelligent ship selection!
**** Ship selection is based on the years the latest ship in the fleet is available, not by era alone.
**** Hull sizes probabilities have been spread in a way to reflect fleets better: many small ships, some normal-sized ships, and few large-sized ships.
*** Enemy fleet loadouts and fighter upgrades implemented. (OP Only)
*** Fixed crashing problems.
*** Logfile written to C:\Coop.txt has more detail.
*** Capturing an enemy ship will cause it to self-destruct.
** Features and work by MagnumMan:
*** Combined EAW/OP installer.

* 1.5
** Mar 31 2001
*** Added era selection logic to ensure the enemy armada is picked from the correct era.
*** No more late era enemies in an early or middle era game, etc.

* 1.4
** Mar 15 2001
*** Added AI Intelligence setting.
*** Changed default difficulty to 1.1.

* 1.3
** Mar 12 2001
*** Fixed a bug where the game generated no enemies.
*** Fixed a bug where the game would not end if you captured an enemy ship.

* 1.2
** Mar 3 2001
*** Fixed a bug where the game ended prematurely if someone dropped.
*** Fixed a bug where the game would not end if the last player disengaged.
*** Fixed a bug where the game hangs on launch if more than 9 enemy ships are created.
*** Added a new feature to limit the enemy by specific races.
*** Added a new feature to limit the enemy by specific hull classes.
*** Added a new configuration program.
*** Added an installer.

* 1.1
** Feb 17 2001
*** Fixed a hanging problem when more than 3 or more people join.

* 1.0
** First Release.

== Known Bugs ==

=== EAW host changes effects on enemy carriers ===
* If there's a host change, carriers on the enemy team will generate new fighters to release. This is because there is no "mSetFighters" function in the SFC:EAW API.

=== Unable to determine the BPV of player fleets with loadouts ===

* The game itself has a bug making it impossible to determine the BPV of each player's fleet with loadouts. The BPV calculation is unfortunately based on the stock ship configurations without custom loadouts. You can compensate by raising the difficulty.
** OP Only: the loadouts for shuttles, spareparts and mines can be detected. However, the loadouts for drones and fighters cannot.

All SFC Patches and ServerKits

2025-10-08T17:09:12Z

Firesoul:

=== SFC(1) Patches ===

* [https://klingon.lostexiles.net/sources_and_utils/patches/sfc100-103.zip sfc100-103.zip] size: 4.5Mb
* [https://klingon.lostexiles.net/sources_and_utils/patches/sfc1021-103.zip sfc1021-103.zip] size: 1.5Mb

=== SFC:EAW Patches ===

* CURRENT, 2.0.3.6:
** [https://klingon.lostexiles.net/sources_and_utils/patches/SFC2Patch2002-2036.exe SFC2Patch2002-2036.exe] size: 23MB
** [https://klingon.lostexiles.net/sources_and_utils/patches/SFC2Patch2033-2036.exe SFC2Patch2033-2036.exe] size: 2.9MB

* 2.0.3.3
** [https://klingon.lostexiles.net/sources_and_utils/patches/SFC2Patch2002-2033.exe SFC2Patch2002-2033.exe] size: 24.5MB
** [https://klingon.lostexiles.net/sources_and_utils/patches/SFC2Patch2013-2033.exe SFC2Patch2013-2033.exe] size: 16.6MB
* 2.0.1.3
** [https://klingon.lostexiles.net/sources_and_utils/patches/SFC2Patch2002-2013.exe SFC2Patch2002-2013.exe] size: 23.6MB
** [https://klingon.lostexiles.net/sources_and_utils/patches/SFC2Patch2007-2013.exe SFC2Patch2007-2013.exe] size: 17.9MB
* 2.0.0.7
** [https://klingon.lostexiles.net/sources_and_utils/patches/SFC2Patch2002-2007.exe SFC2Patch2002-2007.exe] size: 24.5MB

=== SFC:OP Patches ===

* CURRENT, 2.5.5.2
** [https://klingon.lostexiles.net/sources_and_utils/patches/SFCOP_Patch_2500-2552.exe SFCOP_Patch_2500-2552.exe] size: 19.0MB
** [https://klingon.lostexiles.net/sources_and_utils/patches/SFCOP_Patch_2550-2552.exe SFCOP_Patch_2550-2552.exe] size: 1.9MB
* 2.5.5.0
** [https://klingon.lostexiles.net/sources_and_utils/patches/SFCOP_Patch_2500-2550.exe SFCOP_Patch_2500-2550.exe] size: 19.0MB
** [https://klingon.lostexiles.net/sources_and_utils/patches/SFCOP_Patch_25412-2550.exe SFCOP_Patch_25412-2550.exe] size: 1.9MB
* 2.5.4.1.2
** [https://klingon.lostexiles.net/sources_and_utils/patches/SFCOP_Patch_2500-25412.exe SFCOP_Patch_2500-25412.exe] size: 19.0MB
** [https://klingon.lostexiles.net/sources_and_utils/patches/SFCOP_Patch_2538-25412.exe SFCOP_Patch_2538-25412.exe] size: 1.9MB
** [https://klingon.lostexiles.net/sources_and_utils/patches/SFCOP_Patch_25410-25412.exe SFCOP_Patch_25410-25412.exe] size: 1.8MB
* 2.5.4.1.0
** [https://klingon.lostexiles.net/sources_and_utils/patches/SFCOP_Patch_2500-25410.exe SFCOP_Patch_2500-25410.exe] size: 19.0MB
** [https://klingon.lostexiles.net/sources_and_utils/patches/SFCOP_Patch_2538-25410.exe SFCOP_Patch_2538-25410.exe] size: 2.1MB
* 2.5.3.8
** [https://klingon.lostexiles.net/sources_and_utils/patches/SFCOP_Patch_2500-2538.exe SFCOP_Patch_2500-2538.exe] size: 19.0MB
** [https://klingon.lostexiles.net/sources_and_utils/patches/SFCOP_Patch_2525-2538.exe SFCOP_Patch_2525-2538.exe] size: 2.4MB
* 2.5.2.5
** [https://klingon.lostexiles.net/sources_and_utils/patches/SFCOP_Patch_2500-2525.exe SFCOP_Patch_2500-2525.exe] size: 21.0MB
** [https://klingon.lostexiles.net/sources_and_utils/patches/SFCOP_Patch_2501-2525.exe SFCOP_Patch_2501-2525.exe] size: 10.3MB

=== SFC2 Server kits ===

==== Latest Server Kits ====
* [https://klingon.lostexiles.net/sources_and_utils/SFC2Server2036.zip SFC2Server2036.zip]
** SFC:EAW 2.0.3.6 server kit (size: 12MB)
* [https://klingon.lostexiles.net/sources_and_utils/SFCOPServer2552_B36.zip SFCOPServer2552_B36.zip]
** SFC:OP 2.5.5.2 Beta36 server kit
** size: 15.8MB

==== Older Kits ====
* [https://klingon.lostexiles.net/sources_and_utils/SFCOPServer2550.zip SFCOPServer2550.zip]
** size: 25.3MB
* [https://klingon.lostexiles.net/sources_and_utils/SFCOPServer25412.zip SFCOPServer25412.zip]
** size: 25.3MB
* [https://klingon.lostexiles.net/sources_and_utils/SFCOPServer25410.zip SFCOPServer25410.zip]
** size: 25.3MB
* [https://klingon.lostexiles.net/sources_and_utils/SFCOPServer2538.zip SFCOPServer2538.zip]
** size: 15.8MB
** updated: 20030324

SFC-related missions, sources, patches and misc utilities

2025-10-08T17:06:33Z

Firesoul:

== SFC-related Sources, packages, patches and utilities ==

=== SFC Latest Patches and Serverkits ===

==== Latest Patches ====

* SFC:EAW, 2.0.3.6:
** [https://klingon.lostexiles.net/sources_and_utils/patches/SFC2Patch2002-2036.exe SFC2Patch2002-2036.exe]
*** size: 23MB
** [https://klingon.lostexiles.net/sources_and_utils/patches/SFC2Patch2033-2036.exe SFC2Patch2033-2036.exe]
*** size: 2.9MB

* SFC:OP, 2.5.5.2:
** [https://klingon.lostexiles.net/sources_and_utils/patches/SFCOP_Patch_2500-2552.exe SFCOP_Patch_2500-2552.exe]
*** size: 19.4MB
** [https://klingon.lostexiles.net/sources_and_utils/patches/SFCOP_Patch_2550-2552.exe SFCOP_Patch_2550-2552.exe]
*** size: 1.9MB

* SFC, 1.0.3
** [https://klingon.lostexiles.net/sources_and_utils/patches/sfc100-103.zip sfc100-103.zip] size: 4.5Mb
** [https://klingon.lostexiles.net/sources_and_utils/patches/sfc1021-103.zip sfc1021-103.zip] size: 1.5Mb

==== Latest ServerKits ====

* SFC:EAW 2.0.3.6 server kit
** [https://klingon.lostexiles.net/sources_and_utils/SFC2Server2036.zip SFC2Server2036.zip]
*** size: 12MB
* SFC:OP 2.5.5.2 Beta36 server kit
** [https://klingon.lostexiles.net/sources_and_utils/SFCOPServer2552_B36.zip SFCOPServer2552_B36.zip]
*** size: 15.8MB

=== Hidden Features and Easter Eggs ===

About patch 2.5.4.10, 2.5.4.12, 2.5.5.0, 2.5.5.2:
There are 2 hidden features introduced in 25410. This is how you use them.

==== New Arcs ====

Edit the shiplist and put in these arcs where you want them.
* FALX/FARX -> FAL/FAR + right down rear
* LSRF/RSLF -> LS+RF / RS+LF missing arcs
* RRP/RLP -> Rear plasma arcs good for some tugs and HDWs.
* LR -> L+R arc. Can be found on mythical Tholian Snare weapons.

In 2.5.5.2, more arcs were added:
* SFBL/SFBR -> L/R only

==== Switch to disable Engine Doubling ====

Disable Engine Doubling for all pirates. (Useful for Mods). Add ''AllowEngineDoubling=0'' to the ''[Network]'' section of the sfc.ini to disable engine doubling for all pirates.

==== Resetting your SFC:OP Registry entry for your CD-Key ====

Doing the following will cause SFC:OP to re-ask for the CDKey.

* Location: HKLM\\Software\\GameSpy\\CDKeys
** Key: StarfleetCommand2, set to "43", Hex.

Other links on this site:

* [[SFC:OP Plus Refit]]
** many many many (+5000!) added real SFB-based ships
* [[SFC:EAW missions for SFC:OP]]
** EAW missions sources and EAW campaigns compiled for SFC:OP

== SFC Sources: APIs, Mission Scripts ==

=== Development APIs ===

* [https://klingon.lostexiles.net/sources_and_utils/SFC2_API_R1.3.zip SFC2_API_R1.3.zip]
** SFC2:EAW API from Taldren, rev1.3 (size: 5.4mb)
* [https://klingon.lostexiles.net/sources_and_utils/SFCOP_API_R2.zip SFCOP_API_R2.zip]
** SFC2:OP API from Taldren, rev2.2 (size: 5.5mb)

These following files are in no way official packages. These files, zipped from my build environments on my harddrive, will not recieve support in any way. I make these files available to solve problems concerning compiling with either or both EAW and OP APIs on the same machine.

* [https://klingon.lostexiles.net/sources_and_utils/FireSoul_EAW_build_env-20031117.zip FireSoul_EAW_build_env-20031117.zip] (size: 8.7MB)
* [https://klingon.lostexiles.net/sources_and_utils/FireSoul_OP_build_env-20031117.zip FireSoul_OP_build_env-20031117.zip] (size: 9.1mb)
* [https://klingon.lostexiles.net/sources_and_utils/ShipList.20050118.zip ShipList.20050118.zip]
** modified ShipList API to allow access to fighters and PFs list generation. This modification from MagnumMan's SLAPI also contains Enhanced Shiplist support (OP+4.0 only, as far as I can tell). For OP, useful with mSetFighters function. (size: 570Kb) (Can be used with either API. It's smart enough to detect.)
* [https://klingon.lostexiles.net/sources_and_utils/firesoul_shiplist_support_perl_scripts.zip firesoul_shiplist_support_perl_scripts.zip]
** perl script I used to help me debug my OP+ shiplist. There are scripts in there to detect "???" for shipnames, refits and missing names for ship classes.

=== SFC1 mission sources ===

Entire package: [https://klingon.lostexiles.net/sources_and_utils/SFC1_scripts.zip SFC1_scripts.zip] size: 2.0MB
* [https://klingon.lostexiles.net/sources_and_utils/sfc1/Federation.zip Federation.zip] size: 204k
* [https://klingon.lostexiles.net/sources_and_utils/sfc1/Generic.zip Generic.zip] size: 236k
* [https://klingon.lostexiles.net/sources_and_utils/sfc1/Gorn.zip Gorn.zip] size: 164k
* [https://klingon.lostexiles.net/sources_and_utils/sfc1/Hydran.zip Hydran.zip] size: 116k
* [https://klingon.lostexiles.net/sources_and_utils/sfc1/Klingon.zip Klingon.zip] size: 220k
* [https://klingon.lostexiles.net/sources_and_utils/sfc1/Lyran.zip Lyran.zip] size: 168k
* [https://klingon.lostexiles.net/sources_and_utils/sfc1/Multiplayer.zip Multiplayer.zip] size: 100k
* [https://klingon.lostexiles.net/sources_and_utils/sfc1/Romulan.zip Romulan.zip] size: 216k
* [https://klingon.lostexiles.net/sources_and_utils/sfc1/Tutorial.zip Tutorial.zip] size: 212k
* [https://klingon.lostexiles.net/sources_and_utils/sfc1/Unique.zip Unique.zip] size: 156k

=== SFC2 Mission Sources ===

==== Taldren Mission Sources ====

* SFC2 EAW:
** [https://klingon.lostexiles.net/EAW_missions/SFC2_EAW_Scripts.zip SFC2_EAW_Scripts.zip]
*** Taldren's pristine sources for the SFC:EAW scripts
*** size: 8.4MB

* SFC2 OP:
** [https://klingon.lostexiles.net/sources_and_utils/OP_Scripts.zip OP_Scripts.zip]
*** Taldren's pristine sources for the SFC:OP scripts
*** size: 4.9MB

==== Sources to missions ported to SFC:OP ====

* [https://klingon.lostexiles.net/EAW_missions/eaw_campaigns_for_OP_Scripts-20030330.zip eaw_campaigns_for_OP_Scripts-20030330.zip]
** sources to the updated SFC:EAW missions, in an OP build environment. (size: 16.4mb)

=== CoopAce package and sourcecode ===

See: [[Co-op Ace for SFC:EAW and SFC:OP]]

=== Andros! package and sourcecode ===

* [https://klingon.lostexiles.net/sources_and_utils/Mul_Andros.scr Mul_Andros.scr]
** for SFC:OP with OP+ 4.1 size: 446464 Bytes
* [https://klingon.lostexiles.net/sources_and_utils/Mul_Andros_1_01.20110501.zip Mul_Andros_1_01.20110501.zip]
** for SFC:OP with OP+ 4.1 size: 103056 Bytes

=== Fests+ installer and sourcecode ===

See: [[Fests+ for SFC:OP]]

=== SFC:OP Models Tester ===

* Standard version, 1 race at a time:
** [https://klingon.lostexiles.net/sources_and_utils/models_testers/Ski_test_models.scr Ski_test_models.scr] size: 470kb (Version 1.23, 20040627)
** [https://klingon.lostexiles.net/sources_and_utils/models_testers/Ski_test_models-20040627.zip Ski_test_models-20040627.zip] size: 72kb (sources)
* Complete test version, all models tested in a single run:
** [https://klingon.lostexiles.net/sources_and_utils/models_testers/Ski_test_all_models.scr Ski_test_all_models.scr] size: 470kb (Version 1.00, 20040714)
** [https://klingon.lostexiles.net/sources_and_utils/models_testers/Ski_test_all_models-20040714.zip Ski_test_all_models-20040714.zip] size: 77kb (sources)
* Test all bases' models, all in a single run:
** [https://klingon.lostexiles.net/sources_and_utils/models_testers/Ski_test_bases_models.scr Ski_test_bases_models.scr] size: 470kb (Version 1.00, 20040714)
** [https://klingon.lostexiles.net/sources_and_utils/models_testers/Ski_test_bases_models-20040714.zip Ski_test_bases_models-20040714.zip] size: 90kb (sources)

=== EvilDave Missions ===
''(all files/links here updated on 20040112)''

* [https://klingon.lostexiles.net/sources_and_utils/EvilDave/EAWMissions.zip EAWMissions.zip]
** EvilDave missionpack for EAW (updated: 20031001 size: 11mb)
* [https://klingon.lostexiles.net/sources_and_utils/EvilDave/NW_OPMissions.exe NW_OPMissions.exe]
** Configurable EvilDave missionpack for OP (updated: 20040810 size: 4.1mb)
* [https://klingon.lostexiles.net/sources_and_utils/EvilDave/NW_EAWtoOP_Campaigns.zip NW_EAWtoOP_Campaigns.zip]
** Campaign (.MCT) files for BOTH EAW for OP single-player campaigns AND EvilDave missionpacks. (updated: 20030512 size: 25kb) (for OP only)
* [https://klingon.lostexiles.net/sources_and_utils/EvilDave/EDMissionSourceCode.zip EDMissionSourceCode.zip]
** Sources to EvilDave mission packs (updated: 20030228 size: 2.9mb)

=== Other Mission packages ===

* [https://klingon.lostexiles.net/sources_and_utils/TraceyG_OP_missions_v4-1.zip TraceyG_OP_missions_v4-1.zip]
** TraceyG's Missions for OP, version 4.1 (size: 2.5mb)
* [https://klingon.lostexiles.net/sources_and_utils/EEK-OP221.exe EEK-OP221.exe]
** Karnak's EEK missions v2.21, for OP (size: 7.2mb, updated 20041013)
* [https://klingon.lostexiles.net/sources_and_utils/EAW_campaigns+NW+TraceyG+EEK.zip EAW_campaigns+NW+TraceyG+EEK.zip]
** Single player .MCT files for complex campaigns. (size: 25kb)

== Misc Tools and Files ==

=== SFC Modeling tools ===

* [https://klingon.lostexiles.net/sources_and_utils/Modeling/SFC_mod_viewer.zip SFC Models viewer]
** Size: 228kb
* [https://klingon.lostexiles.net/sources_and_utils/Modeling/3DSMaxR3SFCImpExpPublicRelease.zip 3dsMax R3 SFC .MOD format plugin]
** Size: 52kb
* [https://klingon.lostexiles.net/sources_and_utils/Modeling/3DSMaxR4SFCImpExpPublicRelease.zip 3dsMax R4 (and R5) SFC .MOD format plugin]
** Size: 22kb
* [https://klingon.lostexiles.net/sources_and_utils/Modeling/SFC_tutorial-creating_break_models-DIVX.avi SFC_tutorial-creating_break_models-DIVX.avi]
** Size: 14mb, by Joker
* [https://klingon.lostexiles.net/sources_and_utils/Modeling/SFC_tutorial-texturing_and_illumination-DIVX.avi SFC_tutorial-texturing_and_illumination-DIVX.avi]
** Size: 32mb, by Joker

== Other/Misc SFC files ==

=== Other Useful Downloads ===

* [https://klingon.lostexiles.net/sources_and_utils/EzINI.exe EzINI.exe] v2.0
** size: 284Kb
* [https://klingon.lostexiles.net/sources_and_utils/ShipEditv30202.zip ShipEdit v3.02.02 for SFC:EAW]
** size: 6.3Mb
* [https://klingon.lostexiles.net/sources_and_utils/SE39902bPword.zip ShipEdit v3.99.02 beta]
** for SFC:OP
** Requires ShipEdit v3.02.02
** size: 2.6Mb
* [https://klingon.lostexiles.net/sources_and_utils/EAW_Sulu_Bonus_missions.zip EAW_Sulu_Bonus_missions.zip]
** Recompiled for SFC:OP
** size: 496k
* [https://klingon.lostexiles.net/sources_and_utils/Bonus.exe Bonus.exe]
** Taldren's Bonus missions for SFC:OP
** size: 65Kb
* [https://klingon.lostexiles.net/sources_and_utils/Comparator.exe Comparator.exe]
** MagnumMan's Shiplist Comparator for EAW and OP
** size: 163kb
* [https://klingon.lostexiles.net/sources_and_utils/GAW_Models.zip GAW_Models.zip]
** Additional models, released from Taldren
** size: 11.1mb

=== Original shiplist files available for download ===

* SFC:EAW 2036 original files:
** [https://klingon.lostexiles.net/sources_and_utils/orig/eaw/2036/shiplist.txt shiplist.txt] size: 816K
** [https://klingon.lostexiles.net/sources_and_utils/orig/eaw/2036/strings.txt strings.txt] size: 108K
** [https://klingon.lostexiles.net/sources_and_utils/orig/eaw/2036/ftrlist.txt ftrlist.txt] size: 12K
** [https://klingon.lostexiles.net/sources_and_utils/orig/eaw/2036/shipnames.txt shipnames.txt] size: 228K

* SFC:OP 25412, 2550 and/or 2552 original files:
** [https://klingon.lostexiles.net/sources_and_utils/orig/op/25412/shiplist.txt shiplist.txt] size: 1.1M
** [https://klingon.lostexiles.net/sources_and_utils/orig/op/25412/model.siz model.siz] size: 16K
** [https://klingon.lostexiles.net/sources_and_utils/orig/op/25412/strings.txt strings.txt] size: 128K
** [https://klingon.lostexiles.net/sources_and_utils/orig/op/25412/ftrlist.txt ftrlist.txt] size: 20K
** [https://klingon.lostexiles.net/sources_and_utils/orig/op/25412/shipnames.txt shipnames.txt] size: 332K

* SFC:OP 25410 original files:
** [https://klingon.lostexiles.net/sources_and_utils/orig/op/25410/shiplist.txt shiplist.txt] size: 1.1M
** [https://klingon.lostexiles.net/sources_and_utils/orig/op/25410/bpvdata.ini bpvdata.ini] size: 4.0K
** [https://klingon.lostexiles.net/sources_and_utils/orig/op/25410/model.siz model.siz] size: 16K
** [https://klingon.lostexiles.net/sources_and_utils/orig/op/25410/strings.txt strings.txt] size: 128K
** [https://klingon.lostexiles.net/sources_and_utils/orig/op/25410/quicktips.txt quicktips.txt] size: 128K
** [https://klingon.lostexiles.net/sources_and_utils/orig/op/25410/bindings.ini bindings.ini] size: 4.0K
** [https://klingon.lostexiles.net/sources_and_utils/orig/op/25410/ftrlist.txt ftrlist.txt] size: 20K
** [https://klingon.lostexiles.net/sources_and_utils/orig/op/25410/aaStrings.txt aaStrings.txt] size: 384K
** [https://klingon.lostexiles.net/sources_and_utils/orig/op/25410/shipnames.txt shipnames.txt] size: 332K

* SFC:OP 2538 original files:
** [https://klingon.lostexiles.net/sources_and_utils/orig/op/2538/shiplist.txt shiplist.txt] size: 1.1M
** [https://klingon.lostexiles.net/sources_and_utils/orig/op/2538/strings.txt strings.txt] size: 120K
** [https://klingon.lostexiles.net/sources_and_utils/orig/op/2538/ftrlist.txt ftrlist.txt] size: 20K
** [https://klingon.lostexiles.net/sources_and_utils/orig/op/2538/shipnames.txt shipnames.txt] size: 292K

* SFC:OP 2525 original files:
** [https://klingon.lostexiles.net/sources_and_utils/orig/op/2525/shiplist.txt shiplist.txt] size: 1.1M
** [https://klingon.lostexiles.net/sources_and_utils/orig/op/2525/strings.txt strings.txt] size: 120K
** [https://klingon.lostexiles.net/sources_and_utils/orig/op/2525/ftrlist.txt ftrlist.txt] size: 20K
** [https://klingon.lostexiles.net/sources_and_utils/orig/op/2525/shipnames.txt shipnames.txt] size: 292K

=== FireSoul's Screenshots ===

* [https://klingon.lostexiles.net/screenshots/woah.JPG woah.JPG]
** coopace development screenshot before the 32 AI ships limit was introduced. This was taken as proof that the script was now stable.

* [https://klingon.lostexiles.net/screenshots/1peace_OP_1.JPG 1peace_OP_1.JPG]
** ... Yes, the OP-compiled EAW campaigns work.

* [https://klingon.lostexiles.net/screenshots/1peace_OP_2.JPG 1peace_OP_2.JPG]
** .... really, they really do run on SFC:OP.

* [https://klingon.lostexiles.net/screenshots/OhMyESGs.png OhMyESGs.png]
** .. that was back in the days I was helping MagnumMan test his 'patch of day' for SFC:EAW. The point here was proof that being able to see the ESG ranges of the enemy was visible in a multiplayer game.

* [https://klingon.lostexiles.net/screenshots/challenge.JPG challenge.JPG]
** Ah memories.. .. I won against a R-CON+ with a ... F-NCL+ ... ?

* [https://klingon.lostexiles.net/screenshots/coopace-fighters1.JPG coopace-fighters1.JPG]
** at one point during coopace development, I was tring to get the AI to get free updated fighters. This is a screenshot of the success. (Please note I am running away really really fast.)

* [https://klingon.lostexiles.net/screenshots/coopace-fighters2.JPG coopace-fighters2.JPG]
** (THIS is what I was really running away from!)

* [https://klingon.lostexiles.net/screenshots/double-base-construction.gif double-base-construction.gif]
** Want to guarantee SB construction on a D2 server? It's been a long time since I've done this trick, but maybe this will still work?

* [https://klingon.lostexiles.net/screenshots/slot_2033.JPG slot_2033.JPG]
** THIS is the slot bug. I am FireSoul.. I am NOT strafer. bleh.

* [https://klingon.lostexiles.net/screenshots/tractored_plasma.jpg tractored_plasma.jpg]
** I caught this one during OP testing. A plasma was fired at a tractored MIRV. The mirv itself was invisible, this was proof that the object was actually absent: the plasma kept tracking an unhittable object. (Although it looks like a plasma being tractored.)

* [https://klingon.lostexiles.net/screenshots/where_is_mirv.jpg where_is_mirv.jpg]
** past MIRV bugs that had been fixed. Isn't being a tester fun?

* [https://klingon.lostexiles.net/screenshots/winex-shipedit.png winex-shipedit.png]
** The EagleEye ShipEdit program runs under WineX.

* [https://klingon.lostexiles.net/screenshots/winex_sfcop.png winex_sfcop.png]
** So does SFC:OP. WineX is by TransGaming Technologies, my ex-employer. WineX is called Cedega, today.

SFC:OP Missions Refit

2025-10-08T17:02:12Z

Firesoul:

== Introduction ==

When I finally released [[SFC:OP Plus Refit]], I decided to reward myself and play a single player campaign. I loaded up the latest [http://www3.telus.net/NuclearWessels/sfc/downloads/NWPack.exe mission pack] from NuclearWessels and gave it a shot.

Well, I quickly found myself frustrated with the game again.

Here are some of the issues I had with the game at this point:
# almost everything had slow drones
# everything had basic fighters
# the new Andromedan ships weren't being loaded up right.
# some missions had hardcoded ships.

.. note that I also encountered some problems with my own [[SFC:OP Plus Refit]] mod, which resulted in the release of version 4.1.1:
# the planets were still shooting themselves with their heavy weapons
# many monsters encountered had 0 crew/boarding parties and were boardable. (1 BP and captured!)

== Vision ==

Imagine loading a "Fleet Patrol" mission: destroy all enemies, or disengage if the enemy is too much for you. It's year 2285.3: you've got a L-BCHT with 4 upgraded PFs. You find yourself in-mission with 2 Klingon wingmen AI-controlled ships, and there's 3 Hydran ships in the distance.

As you close towards your enemy, both your allies and your enemy launch whatever fighters they have. Your Klingon friends launch their K-Lancer.IIIs. The Hydrans, a carrier-based race, have many many H-YellowJacket.IIIs and H-Hornet.IIs as are normally available during that year. You send out your L-PFLs in Harass, adding yet more confusion to the fray.

Your wingmen launch their drones and they are all fast speeds at that. One of the Hydran ships weasels, and its fighter-groups obliterates your destroyer-sized wingman in a single pass.

Then... from the far right... comes a M-aDMX Andromedan Dominatrix Dreadnought, friend to no one and intent on destroying everyone.

.. now that's a Patrol mission!

== Making it happen.. ==

I spent weeks trying to find work-arounds or fixes to these problems. Here's what I've found out:

=== Better in-mission created ship selection ===
* find better way to load up Bases, FRDs, cargo ships, etc. Do NOT use hard-coded ships because these things do get refits over time.
** use shiplist API, load shiplist from MetaAssets directory

=== Give the AI Upgraded fighters ===
* Give AIs better fighters. We cannot determine what fighters a ship has, but we can parse and load the fighterlist and assign era-correct fighters to AI-controlled teams.
** use ShipList API to load fighterlist, specifically from the MetaAssets directory.

=== Give the ships era-correct drone speeds ===
* If a ship was drafted, it'll have slow drones no matter what. However, if the ship was created in-mission and not drafted, the drone speeds will be era-correct. Solution: do not created drafted ships, create in-game only ships with same shipcodes as the drafted ships.
** Ships do NOT get cleaned up from the D2 map. The server's .gf files should be edited to turn on ship destruction and cycling to compensate.
*** see: MetaMap.gf, section [Census], MaxAIsToKillPerTurn parameter.
** if the drafted unit is a base, the mission creates a 'BOX' unit upon destruction WITH the base's drafted ID (aka MetaID) and immediately destroys it. This will be passed back to the D2 engine, multiplayer or not, that whatever had the Base's MetaID was destroyed which may result on base's removal from the D2 map.

=== Don't set-up a mission with a planet that is too big ===
* The planet model sizes are stored in model.siz. The idea is to set up the mission's code to load and parse model.siz, prepare a list of eligible planets that aren't too big and select one randomly from that list.
** ie: I need a Hydran Armed World, limited size.
** Why? Because the FRDs and Defense Platforms may be close to the planet. A large planet will make stuff collide (and thus destroyed) on mission start.

=== Andro tweaks ===
* Auto-detect Andros in the shiplist. If they are there, give them a chance to appear instead of Monsters or Orion pirates or whatever encounters NuclearWessels had originally set up.
** it's just a small chance.

== About the difficulty ==

Yes.. this pack is for everyone out there who play at Admiral Level Difficulty!

* Easy/Captain:
** drafted ships get slow drones (turns off workaround)
** All AI-controlled teams get stock/basic fighters.

* Medium/Commodore:
** drafted ships get ''ERA-CORRECT'' drone speeds.
** All AI-controlled teams still get stock/basic fighters.

* Hard/Admiral:
** drafted ships get ''ERA-CORRECT'' drone speeds.
** All AI-controlled teams fighters ''ARE UPGRADED''.

== What's included? ==

* .SCR Mission scripts, of course. All updated to the specs mentionned above.
** 30 generic missions, originally from NuclearWessels pack
** The ISC Campaign of Pacification missions (play as ISC)
** The Campaign against the ISC Pacification missions (play as the other empire races)
** The Mirak Campaigns (play as Mirak vs Lyran)
** The Mirak Campaigns (play as Klingon, Hydran or Lyran against the Mirak)
* .MCT campaign files for all normal races
* .MCT campaign files for pirate races
* .GF campaign configuration files to tweak stock campaign settings to something more enjoyable.

== Download ==

=== Missions Refit 1.5 ===

NOTE: This mission-pack works best with OP+ 4.1.1 .. at least so far. (as of 20110807) See: [[SFC:OP Plus Refit]]

* Installer: [https://klingon.lostexiles.net/Missions_Refit/SFCOP_MissionsRefit_15_20121022222638.exe SFCOP_MissionsRefit_15_20121022222638.exe] (5.3MB)

* Mission Sources:
** EvilDave missions: [https://klingon.lostexiles.net/Missions_Refit/Missions07.20121022.7z Missions07.20121022.7z] (1.7MB)
** EAW Campaign Mission Sources: [https://klingon.lostexiles.net/Missions_Refit/eaw_Scripts.20121022.7z eaw_Scripts.20121022.7z] (8 MB)
*** ISC Pacification Campaigns and Missions
**** both for and against, all campaigns just like in EAW.
*** Mirak Campaigns and Missions
**** both for and against, all campaigns just like in EAW.
** Needs ShipList API to compile: [https://klingon.lostexiles.net/sources_and_utils/ShipList.20050118.zip ShipList.20050118.zip]
** also see: [[SFC-related_missions,_sources,_patches_and_misc_utilities]]

SFC:OP Plus Refit

2025-10-08T17:01:29Z

Firesoul:

A mod for StarFleet Command : Orion Pirates patch version 2552

* [[OP+ Introduction]]
* [[OP+ Contents and Changes]]
* [[OP+ Statistics]]
* [[OP+ Conversion Rules]]
** conversion rules for ships, from SFB to SFC.
* [[OP+ and Test-Driven Development]]
* [[OP+ about the ship models]]
* [[OP+ FAQ]]
* [[OP+ Fair Use]]

=== Downloads ===

==== OP+ 4.1.1 ====
Released: 2011-08-07

Note: should be compatible with OP+ 4.1, despite in-game warnings. See [[OP+ Contents and Changes]] for differences.

* [https://klingon.lostexiles.net/OP_plusrefit/opplus_411_models_20110724175017.exe opplus_411_models_20110724175017.exe]
** size: 77mb

The installer above will require around 760mb for installation. This is the final release of OP+ 4.1.1.

* Installation Instructions: [https://klingon.lostexiles.net/OP_plusrefit/readme.txt readme.txt]
* Disclaimer: [https://klingon.lostexiles.net/OP_plusrefit/readme.txt readme.txt]

----

==== OP+ 4.1 ====
Released: 2011-06-10 (installer-only update, fully compatible with 2011-06-05 release)

* [https://klingon.lostexiles.net/OP_plusrefit/opplus_41_models_20110610085609.exe opplus_41_models_20110610085609.exe]
** size: 77mb

The installer above will require around 760mb for installation. This is the final release of OP+ 4.1. It's a repackaged release candidate 5 with an updated license.

* Installation Instructions: [https://klingon.lostexiles.net/OP_plusrefit/readme.txt readme.txt]
* Disclaimer: [https://klingon.lostexiles.net/OP_plusrefit/readme.txt readme.txt]

----

==== OP+ 4.0 ====
Released: 2005-01-01

* [https://klingon.lostexiles.net/OP_plusrefit/opplus_40_models.exe opplus_40_models.exe]
** includes models
** size: 63MB
* [https://klingon.lostexiles.net/OP_plusrefit/opplus_40_no_models.exe opplus_40_no_models.exe]
** size: 275KB

Mirror at ftp.xenocorp.net:
* [ftp://ftp.xenocorp.net/game_files/Star_Trek/starfleet_command/Starfleet_Command_OP/shiplists/opplus_40_models.exe opplus_40_models.exe]
* [ftp://ftp.xenocorp.net/game_files/Star_Trek/starfleet_command/Starfleet_Command_OP/shiplists/opplus_40_no_models.exe opplus_40_no_models.exe]

The "with models" installer above will require around 700mb for installation. The no models installer should require around 500mb.

* Installation Instructions: [https://klingon.lostexiles.net/OP_plusrefit/readme.txt readme.txt]
* Disclaimer: [https://klingon.lostexiles.net/OP_plusrefit/readme.txt readme.txt]

----

==== Coopace 4.0 ====

This shiplist works '''''GREAT!''''' with the CoopAce script version 4.0.

* [https://klingon.lostexiles.net/sources_and_utils/coop-ace-4.0.exe CoopAce 4.0 installer]

See: [[Co-op Ace for SFC:EAW and SFC:OP]]

==== Extra Reading Material ====

Available official storyline of the [https://www.starfleetgames.com/sfb/sfin/general_war.htm General War], straight from ADB, at [https://www.starfleetgames.com/ StarFleetGames.com].

How to compile/build SFC2 EAW or OP Missions

2025-10-08T16:06:16Z

Firesoul: /* Other APIs.. maybe your own? */

== Software Pre-requirements ==

=== Windows 95/98/Me/NT/2000/XP 32bit ===

The StarFleet Command 2 games were compiled on a 32-bit host, which was quite normal for the days around 1999-2001. Compiling the missions scripts will require the same. Additionally, it's necessary to install certain support software onto this build environment. I do NOT recommend you use your primary computer to do this.

FireSoul's example:
I have a home PC with Windows Vista Home Premium 64, and thus decided not to use this as my build OS. I decided to look into using a Virtual Machine environment, setting up Windows XP SP3.

My Virtual Machine specs:
* VMWare Player
** Free for non-commercial use.
** See: [http://www.vmware.com/products/player/ http://www.vmware.com/products/player/]
** ALTERNATIVE: Virtual PC 2007

* 1.5GB of memory
** I could do with far less, but I also use 3DSMax R5 to create/modify my SFC 3D models

* 40 GB diskspace
** diskspace is cheap now-a-days. I have a 1TB drive in the main host.

* 2 CPU cores
** I have a Intel I7 Quad Core system. I decided to increase the number of cores in the VM from the default of 1 to 2 so that I can do other stuff while it compiles.

=== Microsoft Visual C++ 6.0 ===

It has to be Microsoft Visual C++ 6.0. Nothing else will work.

No .NET.
No "2005" or younger.

MSVC++ 6.0. Really. I wish you luck in your search! :)

==== Service Pack 5 for MSVC++ 6.0 ====

IMPORTANT! Do not use Service Pack 6!

I cannot legally redistribute SP5 on my site, but I definitely have kept a copy around. It is true that SP6 is far easier to find, but it will SCREW THINGS UP if you install it!

The filename is ''vs6sp5.exe''. It's 130 MB (136,410,832 bytes) in size.

Again, good luck!

=== EAW Scripting API ===

This is the part that links the sources to SFC2 EAW: the mission API. It will contain library files, c++ header files and some template mission scripts.

Be sure to follow the installation instructions!

* download: [https://klingon.lostexiles.net/sources_and_utils/SFC2_API_R1.3.zip SFC2_API_R1.3.zip]
* also see: [[SFC-related_missions,_sources,_patches_and_misc_utilities]]

=== OP API R2.2 - Scripting API ===

This is the part that links the sources to SFC OP: the mission API. It will contain library files, c++ header files and some template mission scripts.

Be sure to follow the installation instructions!

* download: [https://klingon.lostexiles.net/sources_and_utils/SFCOP_API_R2.zip SFCOP_API_R2.zip]
** Installation instructions: [[OP API R2.2 readme.txt]]
* also see: [[SFC-related_missions,_sources,_patches_and_misc_utilities]]

=== ShipList API ===

The game's own API is very unhelpful when it comes to making proper ship picks. I strongly recommend installing, understanding and using the ShipList API so that you can create better missions.

* download: [https://klingon.lostexiles.net/sources_and_utils/ShipList.20050118.zip ShipList.20050118.zip]
* also see: [[SFC-related_missions,_sources,_patches_and_misc_utilities]]

=== Other APIs.. maybe your own? ===

I made my own API kit in the hopes that it might help others. It includes OP R2.2 and a ShipList API revision from 2003.

* download:
** [https://klingon.lostexiles.net/sources_and_utils/FireSoul_EAW_build_env-20031117.zip FireSoul_EAW_build_env-20031117.zip]
** [https://klingon.lostexiles.net/sources_and_utils/FireSoul_OP_build_env-20031117.zip FireSoul_OP_build_env-20031117.zip]
* again, also see: [[SFC-related_missions,_sources,_patches_and_misc_utilities]]

== Installation Order ==

# the OS
# the OS's service packs
# all the OS's windows updates
# MSVC++ 6.0
# VC6's Service Pack 5
# the API
# the auxiliary APIs and mission scripts

== Setting up the API ==

See the API's own documentation.

'''IMPORTANT''': the API has some components that need to be manually installed on top of VC6++ SP5. Again, just follow the instructions in the included ''readme.txt''.

How to compile/build SFC2 EAW or OP Missions

2025-10-08T16:06:08Z

Firesoul: /* ShipList API */

== Software Pre-requirements ==

=== Windows 95/98/Me/NT/2000/XP 32bit ===

The StarFleet Command 2 games were compiled on a 32-bit host, which was quite normal for the days around 1999-2001. Compiling the missions scripts will require the same. Additionally, it's necessary to install certain support software onto this build environment. I do NOT recommend you use your primary computer to do this.

FireSoul's example:
I have a home PC with Windows Vista Home Premium 64, and thus decided not to use this as my build OS. I decided to look into using a Virtual Machine environment, setting up Windows XP SP3.

My Virtual Machine specs:
* VMWare Player
** Free for non-commercial use.
** See: [http://www.vmware.com/products/player/ http://www.vmware.com/products/player/]
** ALTERNATIVE: Virtual PC 2007

* 1.5GB of memory
** I could do with far less, but I also use 3DSMax R5 to create/modify my SFC 3D models

* 40 GB diskspace
** diskspace is cheap now-a-days. I have a 1TB drive in the main host.

* 2 CPU cores
** I have a Intel I7 Quad Core system. I decided to increase the number of cores in the VM from the default of 1 to 2 so that I can do other stuff while it compiles.

=== Microsoft Visual C++ 6.0 ===

It has to be Microsoft Visual C++ 6.0. Nothing else will work.

No .NET.
No "2005" or younger.

MSVC++ 6.0. Really. I wish you luck in your search! :)

==== Service Pack 5 for MSVC++ 6.0 ====

IMPORTANT! Do not use Service Pack 6!

I cannot legally redistribute SP5 on my site, but I definitely have kept a copy around. It is true that SP6 is far easier to find, but it will SCREW THINGS UP if you install it!

The filename is ''vs6sp5.exe''. It's 130 MB (136,410,832 bytes) in size.

Again, good luck!

=== EAW Scripting API ===

This is the part that links the sources to SFC2 EAW: the mission API. It will contain library files, c++ header files and some template mission scripts.

Be sure to follow the installation instructions!

* download: [https://klingon.lostexiles.net/sources_and_utils/SFC2_API_R1.3.zip SFC2_API_R1.3.zip]
* also see: [[SFC-related_missions,_sources,_patches_and_misc_utilities]]

=== OP API R2.2 - Scripting API ===

This is the part that links the sources to SFC OP: the mission API. It will contain library files, c++ header files and some template mission scripts.

Be sure to follow the installation instructions!

* download: [https://klingon.lostexiles.net/sources_and_utils/SFCOP_API_R2.zip SFCOP_API_R2.zip]
** Installation instructions: [[OP API R2.2 readme.txt]]
* also see: [[SFC-related_missions,_sources,_patches_and_misc_utilities]]

=== ShipList API ===

The game's own API is very unhelpful when it comes to making proper ship picks. I strongly recommend installing, understanding and using the ShipList API so that you can create better missions.

* download: [https://klingon.lostexiles.net/sources_and_utils/ShipList.20050118.zip ShipList.20050118.zip]
* also see: [[SFC-related_missions,_sources,_patches_and_misc_utilities]]

=== Other APIs.. maybe your own? ===

I made my own API kit in the hopes that it might help others. It includes OP R2.2 and a ShipList API revision from 2003.

* download:
** [http://klingon.lostexiles.net/sources_and_utils/FireSoul_EAW_build_env-20031117.zip FireSoul_EAW_build_env-20031117.zip]
** [http://klingon.lostexiles.net/sources_and_utils/FireSoul_OP_build_env-20031117.zip FireSoul_OP_build_env-20031117.zip]
* again, also see: [[SFC-related_missions,_sources,_patches_and_misc_utilities]]

== Installation Order ==

# the OS
# the OS's service packs
# all the OS's windows updates
# MSVC++ 6.0
# VC6's Service Pack 5
# the API
# the auxiliary APIs and mission scripts

== Setting up the API ==

See the API's own documentation.

'''IMPORTANT''': the API has some components that need to be manually installed on top of VC6++ SP5. Again, just follow the instructions in the included ''readme.txt''.

How to compile/build SFC2 EAW or OP Missions

2025-10-08T16:06:00Z

Firesoul: /* OP API R2.2 - Scripting API */

== Software Pre-requirements ==

=== Windows 95/98/Me/NT/2000/XP 32bit ===

The StarFleet Command 2 games were compiled on a 32-bit host, which was quite normal for the days around 1999-2001. Compiling the missions scripts will require the same. Additionally, it's necessary to install certain support software onto this build environment. I do NOT recommend you use your primary computer to do this.

FireSoul's example:
I have a home PC with Windows Vista Home Premium 64, and thus decided not to use this as my build OS. I decided to look into using a Virtual Machine environment, setting up Windows XP SP3.

My Virtual Machine specs:
* VMWare Player
** Free for non-commercial use.
** See: [http://www.vmware.com/products/player/ http://www.vmware.com/products/player/]
** ALTERNATIVE: Virtual PC 2007

* 1.5GB of memory
** I could do with far less, but I also use 3DSMax R5 to create/modify my SFC 3D models

* 40 GB diskspace
** diskspace is cheap now-a-days. I have a 1TB drive in the main host.

* 2 CPU cores
** I have a Intel I7 Quad Core system. I decided to increase the number of cores in the VM from the default of 1 to 2 so that I can do other stuff while it compiles.

=== Microsoft Visual C++ 6.0 ===

It has to be Microsoft Visual C++ 6.0. Nothing else will work.

No .NET.
No "2005" or younger.

MSVC++ 6.0. Really. I wish you luck in your search! :)

==== Service Pack 5 for MSVC++ 6.0 ====

IMPORTANT! Do not use Service Pack 6!

I cannot legally redistribute SP5 on my site, but I definitely have kept a copy around. It is true that SP6 is far easier to find, but it will SCREW THINGS UP if you install it!

The filename is ''vs6sp5.exe''. It's 130 MB (136,410,832 bytes) in size.

Again, good luck!

=== EAW Scripting API ===

This is the part that links the sources to SFC2 EAW: the mission API. It will contain library files, c++ header files and some template mission scripts.

Be sure to follow the installation instructions!

* download: [https://klingon.lostexiles.net/sources_and_utils/SFC2_API_R1.3.zip SFC2_API_R1.3.zip]
* also see: [[SFC-related_missions,_sources,_patches_and_misc_utilities]]

=== OP API R2.2 - Scripting API ===

This is the part that links the sources to SFC OP: the mission API. It will contain library files, c++ header files and some template mission scripts.

Be sure to follow the installation instructions!

* download: [https://klingon.lostexiles.net/sources_and_utils/SFCOP_API_R2.zip SFCOP_API_R2.zip]
** Installation instructions: [[OP API R2.2 readme.txt]]
* also see: [[SFC-related_missions,_sources,_patches_and_misc_utilities]]

=== ShipList API ===

The game's own API is very unhelpful when it comes to making proper ship picks. I strongly recommend installing, understanding and using the ShipList API so that you can create better missions.

* download: [http://klingon.lostexiles.net/sources_and_utils/ShipList.20050118.zip ShipList.20050118.zip]
* also see: [[SFC-related_missions,_sources,_patches_and_misc_utilities]]

=== Other APIs.. maybe your own? ===

I made my own API kit in the hopes that it might help others. It includes OP R2.2 and a ShipList API revision from 2003.

* download:
** [http://klingon.lostexiles.net/sources_and_utils/FireSoul_EAW_build_env-20031117.zip FireSoul_EAW_build_env-20031117.zip]
** [http://klingon.lostexiles.net/sources_and_utils/FireSoul_OP_build_env-20031117.zip FireSoul_OP_build_env-20031117.zip]
* again, also see: [[SFC-related_missions,_sources,_patches_and_misc_utilities]]

== Installation Order ==

# the OS
# the OS's service packs
# all the OS's windows updates
# MSVC++ 6.0
# VC6's Service Pack 5
# the API
# the auxiliary APIs and mission scripts

== Setting up the API ==

See the API's own documentation.

'''IMPORTANT''': the API has some components that need to be manually installed on top of VC6++ SP5. Again, just follow the instructions in the included ''readme.txt''.

How to compile/build SFC2 EAW or OP Missions

2025-10-08T16:05:53Z

Firesoul: /* EAW Scripting API */

== Software Pre-requirements ==

=== Windows 95/98/Me/NT/2000/XP 32bit ===

The StarFleet Command 2 games were compiled on a 32-bit host, which was quite normal for the days around 1999-2001. Compiling the missions scripts will require the same. Additionally, it's necessary to install certain support software onto this build environment. I do NOT recommend you use your primary computer to do this.

FireSoul's example:
I have a home PC with Windows Vista Home Premium 64, and thus decided not to use this as my build OS. I decided to look into using a Virtual Machine environment, setting up Windows XP SP3.

My Virtual Machine specs:
* VMWare Player
** Free for non-commercial use.
** See: [http://www.vmware.com/products/player/ http://www.vmware.com/products/player/]
** ALTERNATIVE: Virtual PC 2007

* 1.5GB of memory
** I could do with far less, but I also use 3DSMax R5 to create/modify my SFC 3D models

* 40 GB diskspace
** diskspace is cheap now-a-days. I have a 1TB drive in the main host.

* 2 CPU cores
** I have a Intel I7 Quad Core system. I decided to increase the number of cores in the VM from the default of 1 to 2 so that I can do other stuff while it compiles.

=== Microsoft Visual C++ 6.0 ===

It has to be Microsoft Visual C++ 6.0. Nothing else will work.

No .NET.
No "2005" or younger.

MSVC++ 6.0. Really. I wish you luck in your search! :)

==== Service Pack 5 for MSVC++ 6.0 ====

IMPORTANT! Do not use Service Pack 6!

I cannot legally redistribute SP5 on my site, but I definitely have kept a copy around. It is true that SP6 is far easier to find, but it will SCREW THINGS UP if you install it!

The filename is ''vs6sp5.exe''. It's 130 MB (136,410,832 bytes) in size.

Again, good luck!

=== EAW Scripting API ===

This is the part that links the sources to SFC2 EAW: the mission API. It will contain library files, c++ header files and some template mission scripts.

Be sure to follow the installation instructions!

* download: [https://klingon.lostexiles.net/sources_and_utils/SFC2_API_R1.3.zip SFC2_API_R1.3.zip]
* also see: [[SFC-related_missions,_sources,_patches_and_misc_utilities]]

=== OP API R2.2 - Scripting API ===

This is the part that links the sources to SFC OP: the mission API. It will contain library files, c++ header files and some template mission scripts.

Be sure to follow the installation instructions!

* download: [http://klingon.lostexiles.net/sources_and_utils/SFCOP_API_R2.zip SFCOP_API_R2.zip]
** Installation instructions: [[OP API R2.2 readme.txt]]
* also see: [[SFC-related_missions,_sources,_patches_and_misc_utilities]]

=== ShipList API ===

The game's own API is very unhelpful when it comes to making proper ship picks. I strongly recommend installing, understanding and using the ShipList API so that you can create better missions.

* download: [http://klingon.lostexiles.net/sources_and_utils/ShipList.20050118.zip ShipList.20050118.zip]
* also see: [[SFC-related_missions,_sources,_patches_and_misc_utilities]]

=== Other APIs.. maybe your own? ===

I made my own API kit in the hopes that it might help others. It includes OP R2.2 and a ShipList API revision from 2003.

* download:
** [http://klingon.lostexiles.net/sources_and_utils/FireSoul_EAW_build_env-20031117.zip FireSoul_EAW_build_env-20031117.zip]
** [http://klingon.lostexiles.net/sources_and_utils/FireSoul_OP_build_env-20031117.zip FireSoul_OP_build_env-20031117.zip]
* again, also see: [[SFC-related_missions,_sources,_patches_and_misc_utilities]]

== Installation Order ==

# the OS
# the OS's service packs
# all the OS's windows updates
# MSVC++ 6.0
# VC6's Service Pack 5
# the API
# the auxiliary APIs and mission scripts

== Setting up the API ==

See the API's own documentation.

'''IMPORTANT''': the API has some components that need to be manually installed on top of VC6++ SP5. Again, just follow the instructions in the included ''readme.txt''.

How to compile/build SFC2 EAW or OP Missions

2024-01-01T18:23:55Z

Firesoul:

== Software Pre-requirements ==

=== Windows 95/98/Me/NT/2000/XP 32bit ===

The StarFleet Command 2 games were compiled on a 32-bit host, which was quite normal for the days around 1999-2001. Compiling the missions scripts will require the same. Additionally, it's necessary to install certain support software onto this build environment. I do NOT recommend you use your primary computer to do this.

FireSoul's example:
I have a home PC with Windows Vista Home Premium 64, and thus decided not to use this as my build OS. I decided to look into using a Virtual Machine environment, setting up Windows XP SP3.

My Virtual Machine specs:
* VMWare Player
** Free for non-commercial use.
** See: [http://www.vmware.com/products/player/ http://www.vmware.com/products/player/]
** ALTERNATIVE: Virtual PC 2007

* 1.5GB of memory
** I could do with far less, but I also use 3DSMax R5 to create/modify my SFC 3D models

* 40 GB diskspace
** diskspace is cheap now-a-days. I have a 1TB drive in the main host.

* 2 CPU cores
** I have a Intel I7 Quad Core system. I decided to increase the number of cores in the VM from the default of 1 to 2 so that I can do other stuff while it compiles.

=== Microsoft Visual C++ 6.0 ===

It has to be Microsoft Visual C++ 6.0. Nothing else will work.

No .NET.
No "2005" or younger.

MSVC++ 6.0. Really. I wish you luck in your search! :)

==== Service Pack 5 for MSVC++ 6.0 ====

IMPORTANT! Do not use Service Pack 6!

I cannot legally redistribute SP5 on my site, but I definitely have kept a copy around. It is true that SP6 is far easier to find, but it will SCREW THINGS UP if you install it!

The filename is ''vs6sp5.exe''. It's 130 MB (136,410,832 bytes) in size.

Again, good luck!

=== EAW Scripting API ===

This is the part that links the sources to SFC2 EAW: the mission API. It will contain library files, c++ header files and some template mission scripts.

Be sure to follow the installation instructions!

* download: [http://klingon.lostexiles.net/sources_and_utils/SFC2_API_R1.3.zip SFC2_API_R1.3.zip]
* also see: [[SFC-related_missions,_sources,_patches_and_misc_utilities]]

=== OP API R2.2 - Scripting API ===

This is the part that links the sources to SFC OP: the mission API. It will contain library files, c++ header files and some template mission scripts.

Be sure to follow the installation instructions!

* download: [http://klingon.lostexiles.net/sources_and_utils/SFCOP_API_R2.zip SFCOP_API_R2.zip]
** Installation instructions: [[OP API R2.2 readme.txt]]
* also see: [[SFC-related_missions,_sources,_patches_and_misc_utilities]]

=== ShipList API ===

The game's own API is very unhelpful when it comes to making proper ship picks. I strongly recommend installing, understanding and using the ShipList API so that you can create better missions.

* download: [http://klingon.lostexiles.net/sources_and_utils/ShipList.20050118.zip ShipList.20050118.zip]
* also see: [[SFC-related_missions,_sources,_patches_and_misc_utilities]]

=== Other APIs.. maybe your own? ===

I made my own API kit in the hopes that it might help others. It includes OP R2.2 and a ShipList API revision from 2003.

* download:
** [http://klingon.lostexiles.net/sources_and_utils/FireSoul_EAW_build_env-20031117.zip FireSoul_EAW_build_env-20031117.zip]
** [http://klingon.lostexiles.net/sources_and_utils/FireSoul_OP_build_env-20031117.zip FireSoul_OP_build_env-20031117.zip]
* again, also see: [[SFC-related_missions,_sources,_patches_and_misc_utilities]]

== Installation Order ==

# the OS
# the OS's service packs
# all the OS's windows updates
# MSVC++ 6.0
# VC6's Service Pack 5
# the API
# the auxiliary APIs and mission scripts

== Setting up the API ==

See the API's own documentation.

'''IMPORTANT''': the API has some components that need to be manually installed on top of VC6++ SP5. Again, just follow the instructions in the included ''readme.txt''.

How to compile/build SFC2 EAW or OP Missions

2024-01-01T18:23:02Z

Firesoul: /* OP API R2.2 - Scripting API */

== Software Pre-requirements ==

=== Windows 95/98/Me/NT/2000/XP 32bit ===

The StarFleet Command 2 games were compiled on a 32-bit host, which was quite normal for the days around 1999-2001. Compiling the missions scripts will require the same. Additionally, it's necessary to install certain support software onto this build environment. I do NOT recommend you use your primary computer to do this.

FireSoul's example:
I have a home PC with Windows Vista Home Premium 64, and thus decided not to use this as my build OS. I decided to look into using a Virtual Machine environment, setting up Windows XP SP3.

My Virtual Machine specs:
* VMWare Player
** Free for non-commercial use.
** See: [http://www.vmware.com/products/player/ http://www.vmware.com/products/player/]
** ALTERNATIVE: Virtual PC 2007

* 1.5GB of memory
** I could do with far less, but I also use 3DSMax R5 to create/modify my SFC 3D models

* 40 GB diskspace
** diskspace is cheap now-a-days. I have a 1TB drive in the main host.

* 2 CPU cores
** I have a Intel I7 Quad Core system. I decided to increase the number of cores in the VM from the default of 1 to 2 so that I can do other stuff while it compiles.

=== Microsoft Visual C++ 6.0 ===

It has to be Microsoft Visual C++ 6.0. Nothing else will work.

No .NET.
No "2005" or younger.

MSVC++ 6.0. Really. I wish you luck in your search! :)

==== Service Pack 5 for MSVC++ 6.0 ====

IMPORTANT! Do not use Service Pack 6!

I cannot legally redistribute SP5 on my site, but I definitely have kept a copy around. It is true that SP6 is far easier to find, but it will SCREW THINGS UP if you install it!

The filename is ''vs6sp5.exe''. It's 130 MB (136,410,832 bytes) in size.

Again, good luck!

=== EAW Scripting API ===

This is the part that links the sources to SFC2 EAW: the mission API. It will contain library files, c++ header files and some template mission scripts.

Be sure to follow the installation instructions!

* download: [http://klingon.lostexiles.net/sources_and_utils/SFC2_API_R1.3.zip SFC2_API_R1.3.zip]
* also see: [[SFC-related_missions,_sources,_patches_and_misc_utilities]]

=== OP API R2.2 - Scripting API ===

This is the part that links the sources to SFC OP: the mission API. It will contain library files, c++ header files and some template mission scripts.

Be sure to follow the installation instructions!

* download: [http://klingon.lostexiles.net/sources_and_utils/SFCOP_API_R2.zip SFCOP_API_R2.zip]
** Installation instructions: [[OP API R2.2 readme.txt]]
* also see: [[SFC-related_missions,_sources,_patches_and_misc_utilities]]

=== ShipList API ===

The game's own API is very unhelpful when it comes to making proper ship picks. I strongly recommend installing, understanding and using the ShipList API so that you can create better missions.

* download: [http://klingon.pet.dhs.org/sources_and_utils/ShipList.20050118.zip ShipList.20050118.zip]
* also see: [[SFC-related_missions,_sources,_patches_and_misc_utilities]]

=== Other APIs.. maybe your own? ===

I made my own API kit in the hopes that it might help others. It includes OP R2.2 and a ShipList API revision from 2003.

* download:
** [http://klingon.pet.dhs.org/sources_and_utils/FireSoul_EAW_build_env-20031117.zip FireSoul_EAW_build_env-20031117.zip]
** [http://klingon.pet.dhs.org/sources_and_utils/FireSoul_OP_build_env-20031117.zip FireSoul_OP_build_env-20031117.zip]
* again, also see: [[SFC-related_missions,_sources,_patches_and_misc_utilities]]

== Installation Order ==

# the OS
# the OS's service packs
# all the OS's windows updates
# MSVC++ 6.0
# VC6's Service Pack 5
# the API
# the auxiliary APIs and mission scripts

== Setting up the API ==

See the API's own documentation.

'''IMPORTANT''': the API has some components that need to be manually installed on top of VC6++ SP5. Again, just follow the instructions in the included ''readme.txt''.

How to compile/build SFC2 EAW or OP Missions

2024-01-01T18:22:41Z

Firesoul: /* EAW Scripting API */

== Software Pre-requirements ==

=== Windows 95/98/Me/NT/2000/XP 32bit ===

The StarFleet Command 2 games were compiled on a 32-bit host, which was quite normal for the days around 1999-2001. Compiling the missions scripts will require the same. Additionally, it's necessary to install certain support software onto this build environment. I do NOT recommend you use your primary computer to do this.

FireSoul's example:
I have a home PC with Windows Vista Home Premium 64, and thus decided not to use this as my build OS. I decided to look into using a Virtual Machine environment, setting up Windows XP SP3.

My Virtual Machine specs:
* VMWare Player
** Free for non-commercial use.
** See: [http://www.vmware.com/products/player/ http://www.vmware.com/products/player/]
** ALTERNATIVE: Virtual PC 2007

* 1.5GB of memory
** I could do with far less, but I also use 3DSMax R5 to create/modify my SFC 3D models

* 40 GB diskspace
** diskspace is cheap now-a-days. I have a 1TB drive in the main host.

* 2 CPU cores
** I have a Intel I7 Quad Core system. I decided to increase the number of cores in the VM from the default of 1 to 2 so that I can do other stuff while it compiles.

=== Microsoft Visual C++ 6.0 ===

It has to be Microsoft Visual C++ 6.0. Nothing else will work.

No .NET.
No "2005" or younger.

MSVC++ 6.0. Really. I wish you luck in your search! :)

==== Service Pack 5 for MSVC++ 6.0 ====

IMPORTANT! Do not use Service Pack 6!

I cannot legally redistribute SP5 on my site, but I definitely have kept a copy around. It is true that SP6 is far easier to find, but it will SCREW THINGS UP if you install it!

The filename is ''vs6sp5.exe''. It's 130 MB (136,410,832 bytes) in size.

Again, good luck!

=== EAW Scripting API ===

This is the part that links the sources to SFC2 EAW: the mission API. It will contain library files, c++ header files and some template mission scripts.

Be sure to follow the installation instructions!

* download: [http://klingon.lostexiles.net/sources_and_utils/SFC2_API_R1.3.zip SFC2_API_R1.3.zip]
* also see: [[SFC-related_missions,_sources,_patches_and_misc_utilities]]

=== OP API R2.2 - Scripting API ===

This is the part that links the sources to SFC OP: the mission API. It will contain library files, c++ header files and some template mission scripts.

Be sure to follow the installation instructions!

* download: [http://klingon.pet.dhs.org/sources_and_utils/SFCOP_API_R2.zip SFCOP_API_R2.zip]
** Installation instructions: [[OP API R2.2 readme.txt]]
* also see: [[SFC-related_missions,_sources,_patches_and_misc_utilities]]

=== ShipList API ===

The game's own API is very unhelpful when it comes to making proper ship picks. I strongly recommend installing, understanding and using the ShipList API so that you can create better missions.

* download: [http://klingon.pet.dhs.org/sources_and_utils/ShipList.20050118.zip ShipList.20050118.zip]
* also see: [[SFC-related_missions,_sources,_patches_and_misc_utilities]]

=== Other APIs.. maybe your own? ===

I made my own API kit in the hopes that it might help others. It includes OP R2.2 and a ShipList API revision from 2003.

* download:
** [http://klingon.pet.dhs.org/sources_and_utils/FireSoul_EAW_build_env-20031117.zip FireSoul_EAW_build_env-20031117.zip]
** [http://klingon.pet.dhs.org/sources_and_utils/FireSoul_OP_build_env-20031117.zip FireSoul_OP_build_env-20031117.zip]
* again, also see: [[SFC-related_missions,_sources,_patches_and_misc_utilities]]

== Installation Order ==

# the OS
# the OS's service packs
# all the OS's windows updates
# MSVC++ 6.0
# VC6's Service Pack 5
# the API
# the auxiliary APIs and mission scripts

== Setting up the API ==

See the API's own documentation.

'''IMPORTANT''': the API has some components that need to be manually installed on top of VC6++ SP5. Again, just follow the instructions in the included ''readme.txt''.

Fests+ for SFC:OP

2022-09-04T18:25:44Z

Firesoul: /* Downloads */

Tired of the same ol' BattleFests? Sick of watching some enemy getting a XFF when you start with some poor early era FF? .. well.. this should solve your problems! The Fests+ package includes 4 mission scripts for SFC:OP. They are more intelligent than the original Fests scripts (no offense, dear author) and more focused.

== Fests+ 1.1 for OP ==

=== Downloads ===

* [http://klingon.lostexiles.net/fests+/Fests+_11.exe Fests+_11.exe]
** Installer, for SFC:OP
** size: 307KB
* [http://klingon.lostexiles.net/fests+/fests+_20040228.zip fests+_20040228.zip]
** sources
** size: 272KB

=== Scripts included ===

* BattleFest+
** 6 ships: from small to large
*** FF, DD/DW, CL, CA/NCA, BCH, DN
* BattleFestLite+
** 3 ships: FF, CA, DN
* TinyFest+
** 3 ships: FF, DD/DW, CL
* SlugFest+
** 3 ships: large ships: CA, BCH, DN.
** ''exception, in late era'': BCH, DN, BB!

=== What's different compared to the old BattleFests? ===

* The hullclasses have been expanded
** There are, like before, 6 ship classes in the battlefest:
*** Frigate
*** Destroyer
*** Light Cruiser
*** Heavy Cruiser
*** Heavy BattleCruiser
*** Dreadnought
** .. however, these classes have been expanded:
*** Frigate
*** Destroyer '''''AND''''' War Destroyers
*** Light Cruiser
*** Heavy Cruiser AND New Heavy Cruiser
*** Heavy BattleCruiser
*** Dreadnought

* The ships chosen will be Era-complient.
** X1 ships, like those in OP+, are grouped with the Advanced Era ships: there aren't enough of those.

* 2nd pass matching on ship selection failure
** If a ship class from a given era can't be selected, a close match will be selected. This will be from a smaller or larger class, or the same class from a near era.

* Late-era Slugfests are NASTY-FUN!
** If you decide to play a SlugFest+ in Late Era, the 3 ships chosen will be a BCH, DN and BB.

== BattleFest+Intense ==

Released: 2010-01-09.
(NO installer yet)

=== Downloads ===

* [http://klingon.lostexiles.net/fests+/Mul_Battlefest+Intense.scr Mul_Battlefest+Intense.scr]
** mission script. Goes into Assets\Scripts\
** size: 454KB
* [http://klingon.lostexiles.net/fests+/Mul_Battlefest+Intense.zip Mul_Battlefest+Intense.zip]
** source code
** size: 154KB

=== What's different? ===

Differences: You take a Bfest+, and..

* added 1 more hull class: Battleship
*** Frigate
*** Destroyer '''''AND''''' War Destroyers
*** Light Cruiser
*** Heavy Cruiser AND New Heavy Cruiser
*** Heavy BattleCruiser
*** Dreadnought
*** Battleship

* every selected player gets an AI partner of the same race (one they cannot control)
** ie:
*** in a 2-player game, 1 vs 1, it makes it a 2 vs 2.
*** in a 6-player game, FreeForAll (FFA), It will make it a 2 vs 2 vs 2 vs 2 vs 2 vs 2 game.
*** in a 6-player game, 3 vs 3, it makes it a 6 vs 6

Fests+ for SFC:OP

2022-09-04T18:25:25Z

Firesoul: /* Downloads */

Tired of the same ol' BattleFests? Sick of watching some enemy getting a XFF when you start with some poor early era FF? .. well.. this should solve your problems! The Fests+ package includes 4 mission scripts for SFC:OP. They are more intelligent than the original Fests scripts (no offense, dear author) and more focused.

== Fests+ 1.1 for OP ==

=== Downloads ===

* [http://klingon.lostexiles.net/fests+/Fests+_11.exe Fests+_11.exe]
** Installer, for SFC:OP
** size: 307KB
* [http://klingon.lostexiles.net/fests+/fests+_20040228.zip fests+_20040228.zip]
** sources
** size: 272KB

=== Scripts included ===

* BattleFest+
** 6 ships: from small to large
*** FF, DD/DW, CL, CA/NCA, BCH, DN
* BattleFestLite+
** 3 ships: FF, CA, DN
* TinyFest+
** 3 ships: FF, DD/DW, CL
* SlugFest+
** 3 ships: large ships: CA, BCH, DN.
** ''exception, in late era'': BCH, DN, BB!

=== What's different compared to the old BattleFests? ===

* The hullclasses have been expanded
** There are, like before, 6 ship classes in the battlefest:
*** Frigate
*** Destroyer
*** Light Cruiser
*** Heavy Cruiser
*** Heavy BattleCruiser
*** Dreadnought
** .. however, these classes have been expanded:
*** Frigate
*** Destroyer '''''AND''''' War Destroyers
*** Light Cruiser
*** Heavy Cruiser AND New Heavy Cruiser
*** Heavy BattleCruiser
*** Dreadnought

* The ships chosen will be Era-complient.
** X1 ships, like those in OP+, are grouped with the Advanced Era ships: there aren't enough of those.

* 2nd pass matching on ship selection failure
** If a ship class from a given era can't be selected, a close match will be selected. This will be from a smaller or larger class, or the same class from a near era.

* Late-era Slugfests are NASTY-FUN!
** If you decide to play a SlugFest+ in Late Era, the 3 ships chosen will be a BCH, DN and BB.

== BattleFest+Intense ==

Released: 2010-01-09.
(NO installer yet)

=== Downloads ===

* [http://klingon.pet.dhs.org/fests+/Mul_Battlefest+Intense.scr Mul_Battlefest+Intense.scr]
** mission script. Goes into Assets\Scripts\
** size: 454KB
* [http://klingon.pet.dhs.org/fests+/Mul_Battlefest+Intense.zip Mul_Battlefest+Intense.zip]
** source code
** size: 154KB

=== What's different? ===

Differences: You take a Bfest+, and..

* added 1 more hull class: Battleship
*** Frigate
*** Destroyer '''''AND''''' War Destroyers
*** Light Cruiser
*** Heavy Cruiser AND New Heavy Cruiser
*** Heavy BattleCruiser
*** Dreadnought
*** Battleship

* every selected player gets an AI partner of the same race (one they cannot control)
** ie:
*** in a 2-player game, 1 vs 1, it makes it a 2 vs 2.
*** in a 6-player game, FreeForAll (FFA), It will make it a 2 vs 2 vs 2 vs 2 vs 2 vs 2 game.
*** in a 6-player game, 3 vs 3, it makes it a 6 vs 6

Co-op Ace for SFC:EAW and SFC:OP

2022-09-04T18:18:57Z

Firesoul: /* Installer */

== Introduction ==

In this multiplayer script up to 6 people confront a massive randomly generated enemy armada. The enemy is customizable my the game host through an external configuration program. The enemy's difficulty level, race, and hull class can be controlled. This script is absolutely excellent for race-specific training as well as team action training - plus it's a ton of fun!

''Note: This page originally lived at: http://khoromag.org/taldren/scripts/coopace.html . MagnumMan's site has been dead for a while now.''

== Downloads ==

=== Installer ===

Note: FireSoul has made a single installer that will install Co-op Ace for either EAW, OP, or both depending on which games you have installed on your computer. You only need to download and run this installer once even if you have both games.

* [http://klingon.lostexiles.net/sources_and_utils/coop-ace-4.0.exe coop-ace-4.0.exe]
** for both SFC:EAW and SFC:OP, size: 407KB
** note! source code lost!
** [http://klingon.lostexiles.net/sources_and_utils/Mul_CoopAce.scr Mul_CoopAce.scr]
*** in case the installer gives trouble.
*** copy it into Assets/Scripts/
*** it's not enough to host a game. You need a working coopcustomizer for that.

Note: New OSes, like Windows 10, 11
For the installer (and customizer executable) to work on newer OSes, you need to have the following Registry keys within your system:
(please adjust the target directory to your system's)

<nowiki>
[HKEY_LOCAL_MACHINE\SOFTWARE\Taldren\Starfleet Command Orion Pirates]
"Directory"="C:\\Users\\msliv\\Desktop\\SFC\\Starfleet Command Orion Pirates"
</nowiki>

<nowiki>
[HKEY_LOCAL_MACHINE\SOFTWARE\WOW6432Node\Taldren\Starfleet Command Orion Pirates]
"Directory"="C:\\Users\\msliv\\Desktop\\SFC\\Starfleet Command Orion Pirates"
</nowiki>

You also need to make sure the files in the SFCOP directory aren't set to read-only.

=== Sources and stuff ===

The sources to Coop-ace 4.0 are lost. sorry.

* [http://klingon.lostexiles.net/sources_and_utils/Mul_CoopAce.321.20040727.zip Mul_CoopAce.321.20040727.zip] size: 496k
** requires [http://klingon.lostexiles.net/sources_and_utils/ShipList.20031117.zip ShipList.20031117.zip] to build. Can be compiled for both EAW and OP.

== Reviews and comments ==

"'The Co-op' script developed for Starfleet Command II: Empires at War, is a must-have training tool for those who enjoy group actions within SFC2. Not only will it be useful for Dynaverse II and other 'Campaign' systems, but it's fun as hell to play to boot! With a completely configurable setup to enable anyone from the newbie first timer to hardend veteran, it's guaranteed to satisfy! Although it can be used for solo setup, it truly shines when you get a bunch of your buddies together for some old fashioned butt [sic] kicking fun." - Dennis Greene, aka SFCShadow, author of [http://www.amazon.com/gp/product/074400022X Star Trek Starfleet Command II: Empires at War Official Strategy Guide]

"MagnumMan has managed to not only master the scripting API, but deliver to us possibly the best player made script for SFC2, the Multiplayer Co-op Ace script." - RedHotChiliDog Guest Review, Black Ops Station.

"I would have to say that MagnumMan-iCoP has scored a huge hit with this script." - Captain Stoneyface, Black Ops Station.

"MagnumMan once again delivers in this script! Perfect for those nights when FFA just isnt enough - now the whole fleet can get gutted together ! Top notch Work!" - Admiral Frey_XC, [[http://www.xenocorp.net XenoCorp® Inc.]]

== Revision History ==

* 4.0
** January 24, 2005
** Features and work by FireSoul:
*** Much smaller installer.
** Lots of new options, better integration with add-on Ship Lists.

* 3.2.1
** July 27, 2004
** Features and work by FireSoul:
*** Improvements to game load strategy to reduce drops.
*** Automatic red alert after 8 seconds in.

* 3.2
** November 25, 2003
** Features and work by FireSoul:
*** Speed improvements! Faster load times.
*** Mod support directly in the OP customizer!
*** Maximum difficult ratio increased from 2.00 to 3.00.
*** Selectable AI enemy era.

* 3.0.1
** November 12, 2002
** Features and work by FireSoul:
*** Fixed an advanced era date range handling problem (OP only).

* 3.0.0
** October 17, 2002
** Features and work by FireSoul and Strafer:
*** Enhanced enemy fleet selection and generation.
*** Increased game stability.

* 2.6.3
** September 2, 2002
** Features and work by FireSoul:
*** Fixed problem where game started with no enemy ships in EAW if OP was not installed.
*** Fixed game startup sequence to reduce the number of drops.

* 2.6
** August 8, 2002
** Features and work by FireSoul:
*** Fixed early game end bug.
*** improved SpareParts calculations.
*** 'zombie' AI on host drops fixed.
*** Terrain: Dust Clouds added.
*** Terrain: Asteroid Belt improved.
*** Era-based enemies: now uses the game setting for era [OP Only]

* 2.5.2
** July 21, 2002
** Features and work by FireSoul:
*** Enemy Team selection optimized further.
*** Faster entry into the game (less crashes due to timeout).
*** Enemy ships would get no loadouts if enemy ships BPV after selection was '0' (no leftovers).
*** CoopAce for EAW loaded OP's coopace customizer settings.
*** New terrain. "Asteroid Belt".

* 2.5
** July 17, 2002
** Features and work by FireSoul:
*** More intelligent ship selection!
**** Ship selection is based on the years the latest ship in the fleet is available, not by era alone.
**** Hull sizes probabilities have been spread in a way to reflect fleets better: many small ships, some normal-sized ships, and few large-sized ships.
*** Enemy fleet loadouts and fighter upgrades implemented. (OP Only)
*** Fixed crashing problems.
*** Logfile written to C:\Coop.txt has more detail.
*** Capturing an enemy ship will cause it to self-destruct.
** Features and work by MagnumMan:
*** Combined EAW/OP installer.

* 1.5
** Mar 31 2001
*** Added era selection logic to ensure the enemy armada is picked from the correct era.
*** No more late era enemies in an early or middle era game, etc.

* 1.4
** Mar 15 2001
*** Added AI Intelligence setting.
*** Changed default difficulty to 1.1.

* 1.3
** Mar 12 2001
*** Fixed a bug where the game generated no enemies.
*** Fixed a bug where the game would not end if you captured an enemy ship.

* 1.2
** Mar 3 2001
*** Fixed a bug where the game ended prematurely if someone dropped.
*** Fixed a bug where the game would not end if the last player disengaged.
*** Fixed a bug where the game hangs on launch if more than 9 enemy ships are created.
*** Added a new feature to limit the enemy by specific races.
*** Added a new feature to limit the enemy by specific hull classes.
*** Added a new configuration program.
*** Added an installer.

* 1.1
** Feb 17 2001
*** Fixed a hanging problem when more than 3 or more people join.

* 1.0
** First Release.

== Known Bugs ==

=== EAW host changes effects on enemy carriers ===
* If there's a host change, carriers on the enemy team will generate new fighters to release. This is because there is no "mSetFighters" function in the SFC:EAW API.

=== Unable to determine the BPV of player fleets with loadouts ===

* The game itself has a bug making it impossible to determine the BPV of each player's fleet with loadouts. The BPV calculation is unfortunately based on the stock ship configurations without custom loadouts. You can compensate by raising the difficulty.
** OP Only: the loadouts for shuttles, spareparts and mines can be detected. However, the loadouts for drones and fighters cannot.

Co-op Ace for SFC:EAW and SFC:OP

2022-09-04T18:18:21Z

Firesoul: /* Installer */

== Introduction ==

In this multiplayer script up to 6 people confront a massive randomly generated enemy armada. The enemy is customizable my the game host through an external configuration program. The enemy's difficulty level, race, and hull class can be controlled. This script is absolutely excellent for race-specific training as well as team action training - plus it's a ton of fun!

''Note: This page originally lived at: http://khoromag.org/taldren/scripts/coopace.html . MagnumMan's site has been dead for a while now.''

== Downloads ==

=== Installer ===

Note: FireSoul has made a single installer that will install Co-op Ace for either EAW, OP, or both depending on which games you have installed on your computer. You only need to download and run this installer once even if you have both games.

* [http://klingon.lostexiles.net/sources_and_utils/coop-ace-4.0.exe coop-ace-4.0.exe]
** for both SFC:EAW and SFC:OP, size: 407KB
** note! source code lost!
** [http://klingon.lostexiles.net/sources_and_utils/Mul_CoopAce.scr Mul_CoopAce.scr]
*** in case the installer gives trouble.
*** copy it into Assets/Scripts/
*** it's not enough to host a game. You need a working coopcustomizer for that.

Note: New OSes, like Windows 10, 11
For the installer (and customizer executable) to work on newer OSes, you need to have the following Registry keys within your system:

<nowiki>
[HKEY_LOCAL_MACHINE\SOFTWARE\Taldren\Starfleet Command Orion Pirates]
"Directory"="C:\\Users\\msliv\\Desktop\\SFC\\Starfleet Command Orion Pirates"
</nowiki>

<nowiki>
[HKEY_LOCAL_MACHINE\SOFTWARE\WOW6432Node\Taldren\Starfleet Command Orion Pirates]
"Directory"="C:\\Users\\msliv\\Desktop\\SFC\\Starfleet Command Orion Pirates"
</nowiki>

You also need to make sure the files in the SFCOP directory aren't set to read-only.

=== Sources and stuff ===

The sources to Coop-ace 4.0 are lost. sorry.

* [http://klingon.lostexiles.net/sources_and_utils/Mul_CoopAce.321.20040727.zip Mul_CoopAce.321.20040727.zip] size: 496k
** requires [http://klingon.lostexiles.net/sources_and_utils/ShipList.20031117.zip ShipList.20031117.zip] to build. Can be compiled for both EAW and OP.

== Reviews and comments ==

"'The Co-op' script developed for Starfleet Command II: Empires at War, is a must-have training tool for those who enjoy group actions within SFC2. Not only will it be useful for Dynaverse II and other 'Campaign' systems, but it's fun as hell to play to boot! With a completely configurable setup to enable anyone from the newbie first timer to hardend veteran, it's guaranteed to satisfy! Although it can be used for solo setup, it truly shines when you get a bunch of your buddies together for some old fashioned butt [sic] kicking fun." - Dennis Greene, aka SFCShadow, author of [http://www.amazon.com/gp/product/074400022X Star Trek Starfleet Command II: Empires at War Official Strategy Guide]

"MagnumMan has managed to not only master the scripting API, but deliver to us possibly the best player made script for SFC2, the Multiplayer Co-op Ace script." - RedHotChiliDog Guest Review, Black Ops Station.

"I would have to say that MagnumMan-iCoP has scored a huge hit with this script." - Captain Stoneyface, Black Ops Station.

"MagnumMan once again delivers in this script! Perfect for those nights when FFA just isnt enough - now the whole fleet can get gutted together ! Top notch Work!" - Admiral Frey_XC, [[http://www.xenocorp.net XenoCorp® Inc.]]

== Revision History ==

* 4.0
** January 24, 2005
** Features and work by FireSoul:
*** Much smaller installer.
** Lots of new options, better integration with add-on Ship Lists.

* 3.2.1
** July 27, 2004
** Features and work by FireSoul:
*** Improvements to game load strategy to reduce drops.
*** Automatic red alert after 8 seconds in.

* 3.2
** November 25, 2003
** Features and work by FireSoul:
*** Speed improvements! Faster load times.
*** Mod support directly in the OP customizer!
*** Maximum difficult ratio increased from 2.00 to 3.00.
*** Selectable AI enemy era.

* 3.0.1
** November 12, 2002
** Features and work by FireSoul:
*** Fixed an advanced era date range handling problem (OP only).

* 3.0.0
** October 17, 2002
** Features and work by FireSoul and Strafer:
*** Enhanced enemy fleet selection and generation.
*** Increased game stability.

* 2.6.3
** September 2, 2002
** Features and work by FireSoul:
*** Fixed problem where game started with no enemy ships in EAW if OP was not installed.
*** Fixed game startup sequence to reduce the number of drops.

* 2.6
** August 8, 2002
** Features and work by FireSoul:
*** Fixed early game end bug.
*** improved SpareParts calculations.
*** 'zombie' AI on host drops fixed.
*** Terrain: Dust Clouds added.
*** Terrain: Asteroid Belt improved.
*** Era-based enemies: now uses the game setting for era [OP Only]

* 2.5.2
** July 21, 2002
** Features and work by FireSoul:
*** Enemy Team selection optimized further.
*** Faster entry into the game (less crashes due to timeout).
*** Enemy ships would get no loadouts if enemy ships BPV after selection was '0' (no leftovers).
*** CoopAce for EAW loaded OP's coopace customizer settings.
*** New terrain. "Asteroid Belt".

* 2.5
** July 17, 2002
** Features and work by FireSoul:
*** More intelligent ship selection!
**** Ship selection is based on the years the latest ship in the fleet is available, not by era alone.
**** Hull sizes probabilities have been spread in a way to reflect fleets better: many small ships, some normal-sized ships, and few large-sized ships.
*** Enemy fleet loadouts and fighter upgrades implemented. (OP Only)
*** Fixed crashing problems.
*** Logfile written to C:\Coop.txt has more detail.
*** Capturing an enemy ship will cause it to self-destruct.
** Features and work by MagnumMan:
*** Combined EAW/OP installer.

* 1.5
** Mar 31 2001
*** Added era selection logic to ensure the enemy armada is picked from the correct era.
*** No more late era enemies in an early or middle era game, etc.

* 1.4
** Mar 15 2001
*** Added AI Intelligence setting.
*** Changed default difficulty to 1.1.

* 1.3
** Mar 12 2001
*** Fixed a bug where the game generated no enemies.
*** Fixed a bug where the game would not end if you captured an enemy ship.

* 1.2
** Mar 3 2001
*** Fixed a bug where the game ended prematurely if someone dropped.
*** Fixed a bug where the game would not end if the last player disengaged.
*** Fixed a bug where the game hangs on launch if more than 9 enemy ships are created.
*** Added a new feature to limit the enemy by specific races.
*** Added a new feature to limit the enemy by specific hull classes.
*** Added a new configuration program.
*** Added an installer.

* 1.1
** Feb 17 2001
*** Fixed a hanging problem when more than 3 or more people join.

* 1.0
** First Release.

== Known Bugs ==

=== EAW host changes effects on enemy carriers ===
* If there's a host change, carriers on the enemy team will generate new fighters to release. This is because there is no "mSetFighters" function in the SFC:EAW API.

=== Unable to determine the BPV of player fleets with loadouts ===

* The game itself has a bug making it impossible to determine the BPV of each player's fleet with loadouts. The BPV calculation is unfortunately based on the stock ship configurations without custom loadouts. You can compensate by raising the difficulty.
** OP Only: the loadouts for shuttles, spareparts and mines can be detected. However, the loadouts for drones and fighters cannot.

Co-op Ace for SFC:EAW and SFC:OP

2022-09-04T18:15:54Z

Firesoul: /* Downloads */

== Introduction ==

In this multiplayer script up to 6 people confront a massive randomly generated enemy armada. The enemy is customizable my the game host through an external configuration program. The enemy's difficulty level, race, and hull class can be controlled. This script is absolutely excellent for race-specific training as well as team action training - plus it's a ton of fun!

''Note: This page originally lived at: http://khoromag.org/taldren/scripts/coopace.html . MagnumMan's site has been dead for a while now.''

== Downloads ==

=== Installer ===

Note: FireSoul has made a single installer that will install Co-op Ace for either EAW, OP, or both depending on which games you have installed on your computer. You only need to download and run this installer once even if you have both games.

* [http://klingon.lostexiles.net/sources_and_utils/coop-ace-4.0.exe coop-ace-4.0.exe]
** for both SFC:EAW and SFC:OP, size: 407KB
** note! source code lost!
** [http://klingon.lostexiles.net/sources_and_utils/Mul_CoopAce.scr Mul_CoopAce.scr]
*** in case the installer gives trouble.
*** copy it into Assets/Scripts/
*** it's not enough to host a game. You need a working coopcustomizer for that.

Note: New OSes, like Windows 10, 11
For the installer (and customizer executable) to work on newer OSes, you need to have the following Registry keys within your system:

<nowiki>
[HKEY_LOCAL_MACHINE\SOFTWARE\Taldren\Starfleet Command Orion Pirates]
"Directory"="C:\\Users\\msliv\\Desktop\\SFC\\Starfleet Command Orion Pirates"
</nowiki>

<nowiki>
[HKEY_LOCAL_MACHINE\SOFTWARE\WOW6432Node\Taldren\Starfleet Command Orion Pirates]
"Directory"="C:\\Users\\msliv\\Desktop\\SFC\\Starfleet Command Orion Pirates"
</nowiki>

You also need to make sure the files in the SFCOP directory aren't set to read-only.

=== Sources and stuff ===

The sources to Coop-ace 4.0 are lost. sorry.

* [http://klingon.lostexiles.net/sources_and_utils/Mul_CoopAce.321.20040727.zip Mul_CoopAce.321.20040727.zip] size: 496k
** requires [http://klingon.lostexiles.net/sources_and_utils/ShipList.20031117.zip ShipList.20031117.zip] to build. Can be compiled for both EAW and OP.

== Reviews and comments ==

"'The Co-op' script developed for Starfleet Command II: Empires at War, is a must-have training tool for those who enjoy group actions within SFC2. Not only will it be useful for Dynaverse II and other 'Campaign' systems, but it's fun as hell to play to boot! With a completely configurable setup to enable anyone from the newbie first timer to hardend veteran, it's guaranteed to satisfy! Although it can be used for solo setup, it truly shines when you get a bunch of your buddies together for some old fashioned butt [sic] kicking fun." - Dennis Greene, aka SFCShadow, author of [http://www.amazon.com/gp/product/074400022X Star Trek Starfleet Command II: Empires at War Official Strategy Guide]

"MagnumMan has managed to not only master the scripting API, but deliver to us possibly the best player made script for SFC2, the Multiplayer Co-op Ace script." - RedHotChiliDog Guest Review, Black Ops Station.

"I would have to say that MagnumMan-iCoP has scored a huge hit with this script." - Captain Stoneyface, Black Ops Station.

"MagnumMan once again delivers in this script! Perfect for those nights when FFA just isnt enough - now the whole fleet can get gutted together ! Top notch Work!" - Admiral Frey_XC, [[http://www.xenocorp.net XenoCorp® Inc.]]

== Revision History ==

* 4.0
** January 24, 2005
** Features and work by FireSoul:
*** Much smaller installer.
** Lots of new options, better integration with add-on Ship Lists.

* 3.2.1
** July 27, 2004
** Features and work by FireSoul:
*** Improvements to game load strategy to reduce drops.
*** Automatic red alert after 8 seconds in.

* 3.2
** November 25, 2003
** Features and work by FireSoul:
*** Speed improvements! Faster load times.
*** Mod support directly in the OP customizer!
*** Maximum difficult ratio increased from 2.00 to 3.00.
*** Selectable AI enemy era.

* 3.0.1
** November 12, 2002
** Features and work by FireSoul:
*** Fixed an advanced era date range handling problem (OP only).

* 3.0.0
** October 17, 2002
** Features and work by FireSoul and Strafer:
*** Enhanced enemy fleet selection and generation.
*** Increased game stability.

* 2.6.3
** September 2, 2002
** Features and work by FireSoul:
*** Fixed problem where game started with no enemy ships in EAW if OP was not installed.
*** Fixed game startup sequence to reduce the number of drops.

* 2.6
** August 8, 2002
** Features and work by FireSoul:
*** Fixed early game end bug.
*** improved SpareParts calculations.
*** 'zombie' AI on host drops fixed.
*** Terrain: Dust Clouds added.
*** Terrain: Asteroid Belt improved.
*** Era-based enemies: now uses the game setting for era [OP Only]

* 2.5.2
** July 21, 2002
** Features and work by FireSoul:
*** Enemy Team selection optimized further.
*** Faster entry into the game (less crashes due to timeout).
*** Enemy ships would get no loadouts if enemy ships BPV after selection was '0' (no leftovers).
*** CoopAce for EAW loaded OP's coopace customizer settings.
*** New terrain. "Asteroid Belt".

* 2.5
** July 17, 2002
** Features and work by FireSoul:
*** More intelligent ship selection!
**** Ship selection is based on the years the latest ship in the fleet is available, not by era alone.
**** Hull sizes probabilities have been spread in a way to reflect fleets better: many small ships, some normal-sized ships, and few large-sized ships.
*** Enemy fleet loadouts and fighter upgrades implemented. (OP Only)
*** Fixed crashing problems.
*** Logfile written to C:\Coop.txt has more detail.
*** Capturing an enemy ship will cause it to self-destruct.
** Features and work by MagnumMan:
*** Combined EAW/OP installer.

* 1.5
** Mar 31 2001
*** Added era selection logic to ensure the enemy armada is picked from the correct era.
*** No more late era enemies in an early or middle era game, etc.

* 1.4
** Mar 15 2001
*** Added AI Intelligence setting.
*** Changed default difficulty to 1.1.

* 1.3
** Mar 12 2001
*** Fixed a bug where the game generated no enemies.
*** Fixed a bug where the game would not end if you captured an enemy ship.

* 1.2
** Mar 3 2001
*** Fixed a bug where the game ended prematurely if someone dropped.
*** Fixed a bug where the game would not end if the last player disengaged.
*** Fixed a bug where the game hangs on launch if more than 9 enemy ships are created.
*** Added a new feature to limit the enemy by specific races.
*** Added a new feature to limit the enemy by specific hull classes.
*** Added a new configuration program.
*** Added an installer.

* 1.1
** Feb 17 2001
*** Fixed a hanging problem when more than 3 or more people join.

* 1.0
** First Release.

== Known Bugs ==

=== EAW host changes effects on enemy carriers ===
* If there's a host change, carriers on the enemy team will generate new fighters to release. This is because there is no "mSetFighters" function in the SFC:EAW API.

=== Unable to determine the BPV of player fleets with loadouts ===

* The game itself has a bug making it impossible to determine the BPV of each player's fleet with loadouts. The BPV calculation is unfortunately based on the stock ship configurations without custom loadouts. You can compensate by raising the difficulty.
** OP Only: the loadouts for shuttles, spareparts and mines can be detected. However, the loadouts for drones and fighters cannot.

Co-op Ace for SFC:EAW and SFC:OP

2022-09-04T01:40:46Z

Firesoul: /* Downloads */

== Introduction ==

In this multiplayer script up to 6 people confront a massive randomly generated enemy armada. The enemy is customizable my the game host through an external configuration program. The enemy's difficulty level, race, and hull class can be controlled. This script is absolutely excellent for race-specific training as well as team action training - plus it's a ton of fun!

''Note: This page originally lived at: http://khoromag.org/taldren/scripts/coopace.html . MagnumMan's site has been dead for a while now.''

== Downloads ==

Note: FireSoul has made a single installer that will install Co-op Ace for either EAW, OP, or both depending on which games you have installed on your computer. You only need to download and run this installer once even if you have both games.

* [http://klingon.lostexiles.net/sources_and_utils/coop-ace-4.0.exe coop-ace-4.0.exe]
** for both SFC:EAW and SFC:OP, size: 407KB
** note! source code lost!
** [http://klingon.lostexiles.net/sources_and_utils/Mul_CoopAce.scr Mul_CoopAce.scr]
*** in case the installer gives trouble.
*** copy it into Assets/Scripts/

* [http://klingon.lostexiles.net/sources_and_utils/Mul_CoopAce.321.20040727.zip Mul_CoopAce.321.20040727.zip] size: 496k
** requires [http://klingon.lostexiles.net/sources_and_utils/ShipList.20031117.zip ShipList.20031117.zip] to build. Can be compiled for both EAW and OP.

== Reviews and comments ==

"'The Co-op' script developed for Starfleet Command II: Empires at War, is a must-have training tool for those who enjoy group actions within SFC2. Not only will it be useful for Dynaverse II and other 'Campaign' systems, but it's fun as hell to play to boot! With a completely configurable setup to enable anyone from the newbie first timer to hardend veteran, it's guaranteed to satisfy! Although it can be used for solo setup, it truly shines when you get a bunch of your buddies together for some old fashioned butt [sic] kicking fun." - Dennis Greene, aka SFCShadow, author of [http://www.amazon.com/gp/product/074400022X Star Trek Starfleet Command II: Empires at War Official Strategy Guide]

"MagnumMan has managed to not only master the scripting API, but deliver to us possibly the best player made script for SFC2, the Multiplayer Co-op Ace script." - RedHotChiliDog Guest Review, Black Ops Station.

"I would have to say that MagnumMan-iCoP has scored a huge hit with this script." - Captain Stoneyface, Black Ops Station.

"MagnumMan once again delivers in this script! Perfect for those nights when FFA just isnt enough - now the whole fleet can get gutted together ! Top notch Work!" - Admiral Frey_XC, [[http://www.xenocorp.net XenoCorp® Inc.]]

== Revision History ==

* 4.0
** January 24, 2005
** Features and work by FireSoul:
*** Much smaller installer.
** Lots of new options, better integration with add-on Ship Lists.

* 3.2.1
** July 27, 2004
** Features and work by FireSoul:
*** Improvements to game load strategy to reduce drops.
*** Automatic red alert after 8 seconds in.

* 3.2
** November 25, 2003
** Features and work by FireSoul:
*** Speed improvements! Faster load times.
*** Mod support directly in the OP customizer!
*** Maximum difficult ratio increased from 2.00 to 3.00.
*** Selectable AI enemy era.

* 3.0.1
** November 12, 2002
** Features and work by FireSoul:
*** Fixed an advanced era date range handling problem (OP only).

* 3.0.0
** October 17, 2002
** Features and work by FireSoul and Strafer:
*** Enhanced enemy fleet selection and generation.
*** Increased game stability.

* 2.6.3
** September 2, 2002
** Features and work by FireSoul:
*** Fixed problem where game started with no enemy ships in EAW if OP was not installed.
*** Fixed game startup sequence to reduce the number of drops.

* 2.6
** August 8, 2002
** Features and work by FireSoul:
*** Fixed early game end bug.
*** improved SpareParts calculations.
*** 'zombie' AI on host drops fixed.
*** Terrain: Dust Clouds added.
*** Terrain: Asteroid Belt improved.
*** Era-based enemies: now uses the game setting for era [OP Only]

* 2.5.2
** July 21, 2002
** Features and work by FireSoul:
*** Enemy Team selection optimized further.
*** Faster entry into the game (less crashes due to timeout).
*** Enemy ships would get no loadouts if enemy ships BPV after selection was '0' (no leftovers).
*** CoopAce for EAW loaded OP's coopace customizer settings.
*** New terrain. "Asteroid Belt".

* 2.5
** July 17, 2002
** Features and work by FireSoul:
*** More intelligent ship selection!
**** Ship selection is based on the years the latest ship in the fleet is available, not by era alone.
**** Hull sizes probabilities have been spread in a way to reflect fleets better: many small ships, some normal-sized ships, and few large-sized ships.
*** Enemy fleet loadouts and fighter upgrades implemented. (OP Only)
*** Fixed crashing problems.
*** Logfile written to C:\Coop.txt has more detail.
*** Capturing an enemy ship will cause it to self-destruct.
** Features and work by MagnumMan:
*** Combined EAW/OP installer.

* 1.5
** Mar 31 2001
*** Added era selection logic to ensure the enemy armada is picked from the correct era.
*** No more late era enemies in an early or middle era game, etc.

* 1.4
** Mar 15 2001
*** Added AI Intelligence setting.
*** Changed default difficulty to 1.1.

* 1.3
** Mar 12 2001
*** Fixed a bug where the game generated no enemies.
*** Fixed a bug where the game would not end if you captured an enemy ship.

* 1.2
** Mar 3 2001
*** Fixed a bug where the game ended prematurely if someone dropped.
*** Fixed a bug where the game would not end if the last player disengaged.
*** Fixed a bug where the game hangs on launch if more than 9 enemy ships are created.
*** Added a new feature to limit the enemy by specific races.
*** Added a new feature to limit the enemy by specific hull classes.
*** Added a new configuration program.
*** Added an installer.

* 1.1
** Feb 17 2001
*** Fixed a hanging problem when more than 3 or more people join.

* 1.0
** First Release.

== Known Bugs ==

=== EAW host changes effects on enemy carriers ===
* If there's a host change, carriers on the enemy team will generate new fighters to release. This is because there is no "mSetFighters" function in the SFC:EAW API.

=== Unable to determine the BPV of player fleets with loadouts ===

* The game itself has a bug making it impossible to determine the BPV of each player's fleet with loadouts. The BPV calculation is unfortunately based on the stock ship configurations without custom loadouts. You can compensate by raising the difficulty.
** OP Only: the loadouts for shuttles, spareparts and mines can be detected. However, the loadouts for drones and fighters cannot.

FireSoul's SFC Materials

2020-12-10T21:29:33Z

Firesoul:

http://klingon.lostexiles.net/FSBanner.png

This site is composed of the following sub-components:

* [[SFC:OP Plus Refit]]
* [[SFC:OP Missions Refit]]
* [[SFC-related missions, sources, patches and misc utilities]]
** [[All SFC Patches and ServerKits]]
** [[Co-op Ace for SFC:EAW and SFC:OP]]
** [[SFC:EAW missions for SFC:OP]]
** [[Fests+ for SFC:OP]]
** [[How to compile/build SFC2 EAW or OP Missions]]
* [http://klingon.lostexiles.net/models/ Models for SFC:OP (and EAW) made or hosted by FireSoul]
* [[FireSoul's SFC:OP BootStrap list]]
** [[Tuning SFC to play on modern hardware]]

Also, here's a list of SFC-related links I keep around:

* [http://www3.telus.net/NuclearWessels/sfc/ NuclearWessels' Scripting Site]
* [http://www.xenocorp.net/ XC Site]
* [http://www.dynaverse.net/ Dynaverse.net]
** [http://www.dynaverse.net/forum/index.php Dynaverse.net Forums]
* [https://hotandspicyforums.com/ Hot&Spicy Forums - more SFC forums, patches]

Co-op Ace for SFC:EAW and SFC:OP

2020-09-26T00:47:40Z

Firesoul: /* Downloads */

== Introduction ==

In this multiplayer script up to 6 people confront a massive randomly generated enemy armada. The enemy is customizable my the game host through an external configuration program. The enemy's difficulty level, race, and hull class can be controlled. This script is absolutely excellent for race-specific training as well as team action training - plus it's a ton of fun!

''Note: This page originally lived at: http://khoromag.org/taldren/scripts/coopace.html . MagnumMan's site has been dead for a while now.''

== Downloads ==

Note: FireSoul has made a single installer that will install Co-op Ace for either EAW, OP, or both depending on which games you have installed on your computer. You only need to download and run this installer once even if you have both games.

* [http://klingon.lostexiles.net/sources_and_utils/coop-ace-4.0.exe coop-ace-4.0.exe]
** for both SFC:EAW and SFC:OP, size: 407KB
** note! source code lost!

* [http://klingon.lostexiles.net/sources_and_utils/Mul_CoopAce.321.20040727.zip Mul_CoopAce.321.20040727.zip] size: 496k
** requires [http://klingon.lostexiles.net/sources_and_utils/ShipList.20031117.zip ShipList.20031117.zip] to build. Can be compiled for both EAW and OP.

== Reviews and comments ==

"'The Co-op' script developed for Starfleet Command II: Empires at War, is a must-have training tool for those who enjoy group actions within SFC2. Not only will it be useful for Dynaverse II and other 'Campaign' systems, but it's fun as hell to play to boot! With a completely configurable setup to enable anyone from the newbie first timer to hardend veteran, it's guaranteed to satisfy! Although it can be used for solo setup, it truly shines when you get a bunch of your buddies together for some old fashioned butt [sic] kicking fun." - Dennis Greene, aka SFCShadow, author of [http://www.amazon.com/gp/product/074400022X Star Trek Starfleet Command II: Empires at War Official Strategy Guide]

"MagnumMan has managed to not only master the scripting API, but deliver to us possibly the best player made script for SFC2, the Multiplayer Co-op Ace script." - RedHotChiliDog Guest Review, Black Ops Station.

"I would have to say that MagnumMan-iCoP has scored a huge hit with this script." - Captain Stoneyface, Black Ops Station.

"MagnumMan once again delivers in this script! Perfect for those nights when FFA just isnt enough - now the whole fleet can get gutted together ! Top notch Work!" - Admiral Frey_XC, [[http://www.xenocorp.net XenoCorp® Inc.]]

== Revision History ==

* 4.0
** January 24, 2005
** Features and work by FireSoul:
*** Much smaller installer.
** Lots of new options, better integration with add-on Ship Lists.

* 3.2.1
** July 27, 2004
** Features and work by FireSoul:
*** Improvements to game load strategy to reduce drops.
*** Automatic red alert after 8 seconds in.

* 3.2
** November 25, 2003
** Features and work by FireSoul:
*** Speed improvements! Faster load times.
*** Mod support directly in the OP customizer!
*** Maximum difficult ratio increased from 2.00 to 3.00.
*** Selectable AI enemy era.

* 3.0.1
** November 12, 2002
** Features and work by FireSoul:
*** Fixed an advanced era date range handling problem (OP only).

* 3.0.0
** October 17, 2002
** Features and work by FireSoul and Strafer:
*** Enhanced enemy fleet selection and generation.
*** Increased game stability.

* 2.6.3
** September 2, 2002
** Features and work by FireSoul:
*** Fixed problem where game started with no enemy ships in EAW if OP was not installed.
*** Fixed game startup sequence to reduce the number of drops.

* 2.6
** August 8, 2002
** Features and work by FireSoul:
*** Fixed early game end bug.
*** improved SpareParts calculations.
*** 'zombie' AI on host drops fixed.
*** Terrain: Dust Clouds added.
*** Terrain: Asteroid Belt improved.
*** Era-based enemies: now uses the game setting for era [OP Only]

* 2.5.2
** July 21, 2002
** Features and work by FireSoul:
*** Enemy Team selection optimized further.
*** Faster entry into the game (less crashes due to timeout).
*** Enemy ships would get no loadouts if enemy ships BPV after selection was '0' (no leftovers).
*** CoopAce for EAW loaded OP's coopace customizer settings.
*** New terrain. "Asteroid Belt".

* 2.5
** July 17, 2002
** Features and work by FireSoul:
*** More intelligent ship selection!
**** Ship selection is based on the years the latest ship in the fleet is available, not by era alone.
**** Hull sizes probabilities have been spread in a way to reflect fleets better: many small ships, some normal-sized ships, and few large-sized ships.
*** Enemy fleet loadouts and fighter upgrades implemented. (OP Only)
*** Fixed crashing problems.
*** Logfile written to C:\Coop.txt has more detail.
*** Capturing an enemy ship will cause it to self-destruct.
** Features and work by MagnumMan:
*** Combined EAW/OP installer.

* 1.5
** Mar 31 2001
*** Added era selection logic to ensure the enemy armada is picked from the correct era.
*** No more late era enemies in an early or middle era game, etc.

* 1.4
** Mar 15 2001
*** Added AI Intelligence setting.
*** Changed default difficulty to 1.1.

* 1.3
** Mar 12 2001
*** Fixed a bug where the game generated no enemies.
*** Fixed a bug where the game would not end if you captured an enemy ship.

* 1.2
** Mar 3 2001
*** Fixed a bug where the game ended prematurely if someone dropped.
*** Fixed a bug where the game would not end if the last player disengaged.
*** Fixed a bug where the game hangs on launch if more than 9 enemy ships are created.
*** Added a new feature to limit the enemy by specific races.
*** Added a new feature to limit the enemy by specific hull classes.
*** Added a new configuration program.
*** Added an installer.

* 1.1
** Feb 17 2001
*** Fixed a hanging problem when more than 3 or more people join.

* 1.0
** First Release.

== Known Bugs ==

=== EAW host changes effects on enemy carriers ===
* If there's a host change, carriers on the enemy team will generate new fighters to release. This is because there is no "mSetFighters" function in the SFC:EAW API.

=== Unable to determine the BPV of player fleets with loadouts ===

* The game itself has a bug making it impossible to determine the BPV of each player's fleet with loadouts. The BPV calculation is unfortunately based on the stock ship configurations without custom loadouts. You can compensate by raising the difficulty.
** OP Only: the loadouts for shuttles, spareparts and mines can be detected. However, the loadouts for drones and fighters cannot.

OP+ Statistics

2019-09-13T23:11:45Z

Firesoul:

==== Compare of shiplists ====

* [https://klingon.lostexiles.net/OP_plusrefit/compare_40.txt compare_40.txt]: Compare between original OP 2552 shiplist, OP Plus Refit 4.0 shiplist
* [https://klingon.lostexiles.net/OP_plusrefit/compare_41.txt compare_41.txt]: Compare between original OP 2552 shiplist, OP Plus Refit 4.1 shiplist
* [https://klingon.lostexiles.net/OP_plusrefit/compare_40_to_41.txt compare_40_to_41.txt]: Compare between OP+ 4.0 and OP+ 4.1

==== Number of ships ====

* The original SFC:OP shiplist has 2370 ship entries.
* The OP Plus Refit 4.0 shiplist has 5958 ship entries.
* The OP Plus Refit 4.1 shiplist has 8299 ship entries.

{| border="1" cellspacing="0" cellpadding="2" align="center" style="text-align:center;" width="100%"
|-
!<big>RACE</big>
!<big>SFC:OP
v.2552</big>
!<big># ships in
OP+ 4.0</big>
!<big># ships in
OP+ 4.1</big>
|-
|Federation||185||433||587
|-
|Gorn||153||320||454
|-
|Hydran||159||459||515
|-
|ISC||153||348||462
|-
|Klingon||193||466||636
|-
|Lyran||221||520||634
|-
|Mirak||153||463||604
|-
|Romulan||180||394||573
|-
|Monster||20||20||38
|-
|Neutral||88||189||196
|-
|Orion||134||257||439
|-
|OrionBeastRaiders||105||269||391
|-
|OrionCamboro||90||258||410
|-
|OrionKorgath||98||264||431
|-
|OrionOrion||96||268||409
|-
|OrionPrime||90||252||365
|-
|OrionSyndicate||90||257||370
|-
|OrionTigerHeart||79||285||421
|-
|OrionWyldeFire||83||230||364
|}

OP+ Contents and Changes

2019-09-13T23:11:15Z

Firesoul:

== OP+ 4.1.1 Changes ==

=== Fixes: planet hardpoints, again ===

* the planet hardpoints weren't quite right, and the planets were still shooting themselves. I've increased the diameter a bit and it works better now.

=== Fixes: monsters with 'NT' flag: can't transport to them ===

* It was possible to instantly kill/win against a monster by transporting a single Boarding Party to it. I made the monsters non-transportable. This is kinda important for the BeastRaiders!

=== New: separate version of ftrlist.txt and shiplist.txt for single-player D2 ===

* All fighters are available until year '999' for normal multiplayer.. however, that's just silly and sad for a D2 experience. I've created a different version for the D2 experience where older fighters/PFs are phased out.
** to have different phase-out for the PFs, there has to be a different shiplist.txt file as well.

== OP+ 4.1 Changes ==

=== Orion Pirates: TOTAL REBOOT ===

The pirate ships have all been recreated from an templating system of my design.

* Pirate ship Templates
** I entered, from SFB SSDs, all the base pirate ships I want to use. These ships are mostly weaponless, in their pre-configured form.
* Weapons and Systems reference
** I coded the various allowed weapon costs and arcs based on SFB Annexes for option mounts:
*** Annexes #8B and #8H
*** ie: plasma with Swivel cost more than plasma without! Different arcs
*** ie#2: systems in mounts possible!
* I then spent weeks creating tons and tons of replacement pirate ships, all with ACCURATE BPV, arcs and weapons for their region of space!
** under test coverage!
** far more accurate!

The pirates are now accurate, complete and are far closer to accurate SFB rules. The majority of them are better than they used to be.

==== Power Boost, ''à la Taldren'' ====

Did you know the housekeeping costs in SFC are inflated? Yes! For example, if you have any tractors exist on your ship, 0.5 power is automatically put aside. And there are other costs beside that which I could not identify.

Normal costs:
* probe: 1.0
* transporters: 1.0 per 5

So. I have decided to take a AR from SFC-OP 2.5.5.2 and one from OP+ 4.1.. and compare them. Basically:

* the OP stock pirate has a probe. (as expected)
* the OP stock pirate has 2 APRs!

Further investigation has revealed that Taldren has indeed added power to its pirates. Thus, I have decided to do the same, since it looks like this extra power counteracts the expensive housekeeping and makes the pirate ships useful.

The power boosts are allocated by sizeclass:
* sizeclass 4: +1 APR, +2 BPV
** frigates, destroyers
* sizeclass 3: +2 APR, +4 BPV
** light cruisers, war cruisers, heavy cruisers, BCHs
* sizeclass 2: +4 APR, +8 BPV
** Dreadnoughts, battleships

==== No Probes ?! ====

Yes. No probes. As per the SFB SSD. Deal with it!

''(In fact, removing the ship's probe launcher improves the powercurve of the ship.)''

=== Ships from Module X1R (X-Ship Reinforcements) ===

More Official Full X-Ships!

* Advanced Technology War Cruisers (and variants)
* Advanced Technology War Destroyers (and variants)
* Advanced Technology PF Tenders and Carriers

=== Partial X Refits ===

Module X1R also provides very useful rules to do Partial Advanced Technology upgrades to any ship still in service. This counts as an extra refit for ALL ships in the game. These refits were put into place programmatically based on rules provided by ADB. I also re-used some of the previous X-Ship conversion rules for upgraded weapons and systems, as well as BPV costs.

The following systems get partial upgrades:
* Phasers
* APR power
* Drone Racks
* Plasma Torpedos
* Batteries
* limited distruptor upgrades (ranges only)

=== Ships from Module R11 (Support Ships) ===

Module R11 provides a few interesting classes of ships: support ships.
ie:

* Fast War Cruisers
* Transport Frigates
* Heavy New Heavy Cruiser Scouts
* Light PFTs
* Pods for Tugs: Scout, PF transport, fighter resupply
* Advanced Technology Fleet Repair Docks (FRX)

=== Ships from Module R12 (Unusual Ships) ===

More ships!

ie:
* Heavy War Cruisers experiments and prototypes
* Battle Frigate variants
* Various and many odd ships

=== No-fighter refit eliminated ===

No one liked it. It served no purpose. ... so I got rid of them. I also merged in the 'F'ighter refits: if the ship gets them, then the ship gets them without any other options.

ie:
* most/all Y180+ Lyrans will all be carrying PFs.
* Heavy War Destroyers

=== Shiplist swapper ===

I've included a shiplist swapper for those who are reluctant to switch away from OPPlus 4.0. In some cases, the concern is completely valid: uninstalling OP+ 4.0 will blow away customizations, such as custom models, etc.

To be able to do this, I've changed things so that all files install to ''opplus41/'' instead of just ''opplus/''. That means the OP+ 4.1 installer isn't overwriting OP+ 4.0.

==== Why a program? Why not a batch file? ====

The program fetches the install location of SFC:OP from the Registry. That means that if you installed it in D:\my_games\SFCOP\ , '''''it will still work'''''. Additionally, it asks for administrator privileges, just in case.

==== Where is it? How do I use it? ====

It's in the start menu, with links for OP+ 4.1.

https://klingon.lostexiles.net/OP_plusrefit/opplus_41_shiplist_swapper.png

See: [[OP+ 4.1 ShipList Swapper NSIS source code]]

=== Tugs as Freighters ===

Cargo-bearing tugs are now in the 'F'reighter class of ships: frees up room for more ships and allows for some interesting Convoy Raids.

=== Planets hardpoint fixes ===

* Work done by: Tus-XC, FireSoul
* Suggestion by: Dizzy

It's a sweeping fix. What is involved is that the shiplist for all the planets with weapons are redone and then the models themselves will have to be rehardpointed. The hardpoints are currently located anywhere from 5 to 7 range above and below the equator on the physical planet model itself, which obviously causes point defense weapons not to fire because if a ship approaches the equator, the point defense weapons are too far away to fire.

Make note that any weapon that ignores a fire arc should not be used on a planet as firing through the planet mesh occurs and the resulting sound collision from that fire is quite annoying. Below you will see the planet fire arc where HW1 is the front of the ship. HW1 stands for heavy weapon hardpoint 1 and is the 1st heavy weapon column in the shiplist. PH11 stands for the 11th phaser hardpoint and corresponds to the 11th weapon column in the shiplist.

* The Yellow arcs should be Ph3 hardpoints which should be present on '''''ALL''''' planets.
* The Blue are the Ph4's which should be standard on all armed planets.
* The Red should be heavy weapon hardpoints that should be on all armed planets.
* The Orange should be optional heavy weapon hardpoints.
* The rest shaded grey should be only used for homeworlds.
* Ph1/2's should not be used on planets as it would give the planet too many defensive phasers.

I do not remember testing to see if a planet can make use of defensive tractors vs drones. I think they do, and I would give

* all planets 6
* homeworlds 12

I am fuzzy on the artifex program and do not remember specifically which planets are referred to as colony world, core world and homeworld. If there are other designations artifex uses that the scripts and the map match up, it would be easy to simply use the existing planets as a reference and arm them from the stock taldren template using the fixes I have made.

https://klingon.lostexiles.net/OP_plusrefit/planet_arcs_v2.jpg

-- Dizzy,
[http://www.dynaverse.net/forum/index.php/topic,163390750.msg1123020912.html#msg1123020912 http://www.dynaverse.net/forum/index.php/topic,163390750.msg1123020912.html#msg1123020912]

=== Andros as Monsters ===

The idea is to implement random encounters with some early basic Andro ships. Nothing fancy: just use the more basic ships of each hull class and add them to the Monsters race.

==== PA Panels ====

PA Panels don't exist in SFC-OP. We're going to give the ships equivalent equipment based on their effects: shields, toughness and power to the ship.

* Shields
** PA panels are split into 2 hemispheres: front half and rear half.
** count the facing's PA panel.
** multiply by 3.5
** apply the result to each shield part of that hemisphere's facing.
*** ie: 10 forward PA's = 35 shields for numbers 6, 1 and 2

* Labs
** Labs enhance and determine shield regeneration in SFC-OP
** count total of PA panels
** multiply by 5/4 (or 1.25), round up.
** Add as labs in addition to any existing labs
*** ie: the Intruder starts with 6 labs and 14 PA Panels.
**** 6 + (round_up(14 * 1.25)) = 6 + 18 = 24 labs

* APRs
** count total of PA panels
** divide by 4, drop all fractions
** add as APRs in addition to any existing APRs
*** ie: the Intruder starts with 4 APR and 14 PA panels
**** 4 + floor(14 * 0.25) = 4 + 3 = 7 APRs

* No Hit&Runs possible
** Set the SpecialRole in the shiplist to 'NT'. This prevents any transporter activity against the Andro

==== Batteries ====

* Add batteries multiplied by 5. Increase the BPV by 2 per Andro battery (or per 5 added batteries).
** that's 0.5 BPV per extra hit the ship can take.

==== Displacement Device ====

The DisDev in SFB basically moves ships around like a big ass offensive transporter. It can also move friendly units around. We're simulating the DisDev by making the Andro ship more maneuverable.

* +1 HET bonus per DisDev
* +2 acceleration (12 instead of 10) if any DisDev are on the Andro ship

==== Tractor Repulsors ====

The TRBL and TRBH *do* exist in SFC-OP. Use it.

Additionally..
* +1 tractor per TRBL or TRBH.
* Add +1.5 BPV per tractor added.

==== Repair ====

* +2 DamCon Base (and +4 DamCon Max) per repair box on the ship.

==== Hangars ====

Hangars will be empty till the MWPs (fighter-like!) are available.

* MWPs appear in Y175
* They will be housed in the MotherShip hangars instead of SatShips
* The number of hangars and their size will determine their count.
** as per SFB: each MWP group has up to 18 units
** MWPs take 1/4 hangar space
** we're applying the SFB->SFC 2/3 rule
** the Devestator will have 2 groups
* the ship will have deck crews to the same count of MWPs before the 2/3 rule was applied.
** this is for fighter regen
* MTPs (2 TRBLs) will take up to 1/3 of the MWPs in a group, drop the fractions.
** MTP TRBL arc increased from FA to FH due to AI limitations
** TRBL have 2 shots
* ECM/ECCM bumped by 1. (they are supposed to be PFs, initially)

ie: an Intruder has 3 Hangars. That gives it 12 MWPs in SFB. After 2/3 is applied, we've got 8 MWPs for SFC. 6 of those (2 groups of 3) are MWPs, the other 2 are MTPs. The ship will have 12 deck crews.

==== Decoy SSU ====

Acts like a Wild Weasel. Appears in Y186.

* Added a shuttle to Andro ship. Just 1.
* This shuttle will very very very likely be used as a WW by the AI. ;)

==== Enhanced shiplist: Role ====

* role set to CustomRace1. This will be handy for scripts, if someone wants to code an Andro-only mission.

=== Mutiplayer Mission included: Andros! ===

This is a coopace-like mission where Andromedan ships are generated as opponents! The team picked will decide the difficulty.

* Team A: 1.0x player BPV for the Andro ships
* B: 1.5
* C: 2.0
* D: 2.5
* E: 3.0x player BPV for the Andro ships

NOTE! Drones and Fighters information cannot be properly retrieved by the game. It can only be SET. Stupid, I know!

== OP+ 4.0 Changes ==

=== Enhanced Shiplist ===
5 columns were added to the end of the shiplist (it's a text tab-delimited database). Since they're outside the range of the columns used by the game, they are ignored. However, mission scripts can use them by using a modified version of MagnumMan's ShipList API.

You can get this Enhanced ShipList API [[https://klingon.lostexiles.net/mediawiki/index.php?title=SFC-related_missions,_sources,_patches_and_misc_utilities#SFC_Sources:_APIs.2C_Mission_Scripts here]].

The added columns are:

* Enhanced Class Type -- Much like the already established ClassTypes, these have been expanded to cover many other hull types.
* Role -- Defines the ship's role. ie: Escort, Carrier, LineShip, ...
* Secondary Role -- Same data as Role. Used because some ships have multiple roles.
* Xtech -- A column dedicated to describing what level of technology. Currently has very little.
* ProductionAvailability -- Describes how much a ship of a class was built. NONE, UNIQUE, .. to MANY.

=== Module R9 -- The Ships That Never Were ===

ADB released an interesting module contain prototypes, conjectural or impossible ships. Many ships are good for use in SFC, but some didn't make the cut because they were either impossible in SFB in the first place (X-DNLs) or just plain wrong (Alliance Maulers). However.. there are many interesting other ships:

* DNWs -- War Dreadnoughts -- DNs created from CLs
* DNMs -- Medium Dreadnoughts -- DNHs built from DNLs
* Coalition Dreadnought Maulers -- conjectural designs
* Prototypes, some unique ships that were actually built

=== 4.0 Refit Spans and Revision ===

What I thought was a 2-year span before an unrefitted version of a ship is retired was actually 3: from the beginning of the beginning year, 0, to the end of year 2 spans 3 years. Solution: reduce the span by a year. Most refit overlaps have been thus shortened.

Additionally, I have eliminated this overlap for Y175 refits: too much junk was appearing in D2 ShipYards. The SFB data itself describes immediate refits at Y175, therefore the decision to do this was made easy.

Also, I have taken the time to review data from the SFB books and have reapplied some refits for all the races I could find. In many cases, many changes were warranted and have been applied. For example, the C9K is now far earlier than before.

=== Module R8 -- National Guard units ===

ADB has released Module R8 - National Guard Units. These units are police and homeworld protection units, usually upgraded from mothball status and refitted to current technology.

In this case, all races acquire rear-guard units to their lists, but are restricted in availability (on D2). Yes, they're kinda crappy but they could be used by scripters to make really interesting homeworld defense scenarios.

== OP+ 3.4 Changes ==

=== Massive automatically detected cleanups ===

I've spent much time programming and detecting problems through some common-sense. This resulted in a lot of hard work, but the rewards are many.

* Weapons are valid
* Weapon arcs are valid
* Weapons with arcs don't use a reload value
* weapons with reloads don't use arcs
* number of weapons are between 1 and 4.
* UIs used are valid
* all weapons in use match UIs: no weapons placed in a spot not used by UI.
* all HULLTYPE valid. ie: "DESTROYER"
* all CLASSTYPE valid. ie: "CA"
* PLaDs are not available before Y165

This should insure high quality gameplay and any errors previously undetected.

=== Implementation of G4.31: trading a bridge hit for a lab ===

I remembered a basic SFB rule during the data entry of module R8:

* (G4.3) Lab Substitutions
* (G4.31) Control Space: A ship without labs (...) can use one of its control spaces (G2.11) as a lab.

I have decided to implement this by changing all ships with no labs but more than 1 bridge boxes: add 1 lab, and remove 1 bridge. This will *directly* affect shield repairs since that's what SFC uses. I restricted myself to units where this made sense. (ie: not on PFs.)
Around 2000 ships were affected.

== OP+ 3.3 Changes ==

=== Major Ship Models Review ===

This isn't exactly a feature, however this work took 4 months to complete. All ship models introduced by the OP+ installer have been examined, and optimized at need. This would have affected much around 97% of the ships. Also, many ship models have been created with the intent to add them to OP+.
Optimizations:

* Levels of Details (LODs): All ships must have LODs where the original model's details remain intact on LOD1: closest.
* Improved break-mods: All ships will have break-mods with all the pieces looking complete. This took most of the 4 months to do. However, when a ship blows up, a player won't be looking through a piece and see the other side. A damage texture will be shown.
** Also, the break-mods usually won't be based on the main LOD. That would be a waste of resources and may lag the game.
* Many More Models: Where appropriate, models have been created to represent a class of ship which was misrepresented previously.

=== Strings.txt Tweaks ===

Strafer has taken it upon himself to review the names of ship classes and correct them. This took him about a week to do.

For example, a Lyran HDW would be listed as a "Heavy War Destroyer". Now it's listed as a "Top-Alleycat Heavy War Destroyer". There are many such changes, especially within the Gorns. Go take a look.

== OP+ 3.2 Changes ==

=== Fighterless Casual Carriers ===

In SFB, all carriers are shown with just its base BPV. Unless noted otherwise, fighters are *extra*. Of course, it doesn't make sense to have a dedicated carrier without fighters, but it *does* make sense to allow not having to pay for them if it's optional. This affects many Hydran ships, as well as some others through the shiplist. These ships will be recognizable by the 'n' appended at the end of the ship designation. These ships will be marked as "R"estricted. These ships shouldn't appear on the D2 since that's not how it works for there.

ie:
* The stock shiplist's H-SUI (a Taldren invention) costs 161 BPV.
* The OP+ H-SUI costs 167 BPV (stock fighter price leveled with other races).
* The OP+ 3.2 H-SUIn will cost 155 BPV and will have no fighters. Nothing is put in place to replace the fighters. The fighters are just not there: the player simply didn't pay for them.

=== More ISC fighter corrections ===

Some ISC .III fighters come out before the .II fighters. Dates have been fixed.
From:

I-Restitution.II 11
I-Writ.II 15
I-Tort.II 17
I-Caveat.II 17
I-Restitution.III 15
I-Writ.III 11
I-Tort.III 11
I-Caveat.III 15

To:

I-Restitution.II 11
I-Writ.II 11
I-Tort.II 15
I-Caveat.II 15
I-Restitution.III 15
I-Writ.III 15
I-Tort.III 17
I-Caveat.III 17

=== YLA adjustments to older ships within Advanced Era ===

As a D2 campaign progresses into the advanced era, whether it's online or single-player D2, there seemed to be a LOT of left-over ships that haven't been phased out when they really really should be out of the picture.

Adjusting the YLAs for these ships to be around year 45 (2308), just after all races have recieved introductions for the last of their X2 units, seems like a good time to make all the excess ships disapeer and make the campaign concentrate only to what should be leftover.

This one are for you folks who like to turn a D2 map to a single colour, whatever that colour is for your race. ;)

=== Hullclass and Hulltype reclassifications ===

Ships have been reclassified into their appropriate lists based on their weight (without pods) and # of engines. No, not BPV. Affected are many ships throughout the shiplist.

ie: Simple relocation example: F-NCM
The F-NCM was listed as "NEW_HEAVY_CRUISER" within the CL list. It has a movement cost of 1 and ~30 warps. I've moved it to the CA list with the other NCAs.

ie: Major adjustment example: HDWs.
The HDWs were listed as "WAR_DESTROYER" mostly within the FF list. They have a movement cost of 2/3 and ~24 warps. They've been moved to the CL list, reclassifying them as "LIGHT_CRUISER". They are, after all, heavier than a WAR_DESTROYER.

=== More freighters for all races ===

I've added many many freighters, for all races.

* repair freighters (large and small)
* exploration freighters (large and small)
* troop transport freighters (large and small)
* all freighters for pirates too.
** I've never heard of illegal operations that didn't have some legal front with legitimate operations.

=== Civilian Freighters for all races. (with new model) ===

.. and yet more freighters...

* Free Traders (for everyone)
* Free Traitors (for pirates)
* Free Trooper and Tanker (Marines-related units)
* Federation Express
** The Federation Express is a __CIVILIAN__ service. They have their own fleet of courier ships.

=== Armed Priority Transports ===

Another freighter variant. The APTs are fast, small, and neat little military couriers. All races used these. (with new model)

=== System Activity Maintenance Stations (SAMS) ===

Think as these as small platform stations. These are also used as a kind of listening post in far away systems where other tasks are needed, such as a research station above a planet. For these, I've created a model based on the xdp (Defense Platform) which should do nicely.

Note: They can have various base augmentation modules installed (Hospital, VIP quarters, cargo, sciences, etc..)

Note: Also, similar to the SAMS, I've added a N-CPL Civilian Commercial Platform which also uses the new model.

=== Civilian Base Stations ===

Much like the other Base Stations for all races, most/all races had civilian base stations. These did not have ph4s, and other mount points have some i lesser weapons.

=== X1 and X2 Bases ===

In some cases, I had to more or less feel my way around in the dark to create proper bases for all races in X1 and X2 era. I just didn't seem right that all races had bases of all kinds from beginning to late era, then when Advanced arrives, all's there is a X2-style SBX. Well. I renamed all the SBX to XSBs and added the following:

* BSX - X1 base stations
* BSXF(or P) - with Fighters/PFs.
* XBS
* XBSF/P
* BTX
* BTXF/P
* XBT
* XBTF/P
* SBX
* SBXF/P
* XSBF/P

=== Mobile Bases ===

All races used these as temporary repair and resupply stations during an offensive, or when a base was lost.

Its construction involves 2 specially-made habitable pods that tugs can carry for the center portion of the hull. These pods are accompanied by 4 normal-sized pods installed around. These 4 pods could be just about anything that fits, but normally would be some cargo pods, a repair pod and maybe something else (light battle pod? CVL pod?). Finally, 2 base augmentation modules are installed to fill in the blanks.

A convoy of tugs would normally be sufficient to build this base and set it up.

== OP+ 3.1 Changes ==

=== ISC Carriers now have same ratio of fighters ===

To smooth out the fighter payloads on ISC carriers, the 2/3rds rule for SFB->SFC fighter payloads has been applied to all ISC carriers. I've been told the 1:1 ratio for the carriers have been preserved to compensate for fighters that had no heavy weapons. Well.. Check out the next entry on this page..

=== ISC fighters now have increased hull/armor ===

To compensate with the reduction in fighter numbers noted above, the hull hit capacity on ISC fighters has been improved by 20%. In a group of 4 fighters, that is a tremendous improvement in survival.

=== Non-X2 MIRV loadout variants added ===

In a push to make SFC more SFB-like, conversion rules have been thought up to allow non-X2 ships to be equipped with MIRV racks. Such a conversion would increase the BPV of the ship by 20 BPV.

Conversion requirements:
SFB rules are percentage based on the # of drone spaces on racks. Since that cannot be applied to SFC, the # of racks, themselves is instead used for the count. MIRVs, or MW in SFB, are of a "Limited" type of drone, and has corresponding percentage rules. The percentages are the following:

* 10% of drones on non-Mirak/non-Kzinti, non-X ships can be of the "Limited" type.
* 20% of drones on Mirak/Kzinti can be of the "Limited" type.
* 20% of drones on X ships can be of the "Limited" type.

That means that on a non-X, non-Mirak ship, you need at least 10 droneracks to apply the conversion. (There is actually 1 ship that qualifies: Z-WAxDN1.)
On Mirak or X1 ships, each 5th rack can be converted to a MIRV rack, if the number of drone spaces on the ship is preserved. Usually, that means 2 B-racks become 1 MIRV-rack and 1 A-rack. (Each MIRV drone is similar to the double-space MW drone from SFB. Since a MIRV rack has 4 drones per reload, that means the rack is HUGE, sporting 8 drone spaces per reload. The B rack only has 6, so something has to be done to compensate)

=== ISC PPD ships have PPD mountpoint splits ===

ISC PPD mountpoints have been splits, much like many other weapons have been with this change.

=== Romulan Modular Dreadnought variants ===

The Romulan Modular Dreadnoughts have been populated in with their many compatible and SFB-complient variants. That's a LOT of available dreadnoughts for the Rommies, now.

The modules used are per SFB rules, and originate from the various SparrowHawk and SkyHawk configs. Some modules have been specifically mentionned as illegal,such as the mauler or J PLaS modules. Others are incompatible to the current game.

Dreadnoughts, with modular configs:

* R-DMH, DemonHawk: 2 SparrowHawk modules, 1 SkyHawk module
* R-OMH, OmniHawk Light Dreadnought: 2 SparrowHawk modules.
* R-MGH, MegaHawk Dreadnought: 2 SparrowHawk modules.

== OP+ 3.0 Changes ==

=== Ship Models ===

Models have been gathered and selected for use with OP+. In fact, they're included in the main package of the project. There is also a no_models version for those with no bandwidth or those who want to install their own sets of models.

== Previous Changes ==

=== Executable Installer ===

Thanks to NullSoft's NSIS, I now have an easy-to-use installer for this project. People usually have problems installing the shiplist properly, if they're to have any problems at all. Here's a nice screenshot:

https://klingon.lostexiles.net/OP_plusrefit/opplus_installer_22.jpg

This will have much greater implications in future versions of the shiplist, since I've always wanted to have 2 versions of the shiplist downloadable: 1 with models and 1 without. Aww well, you'll see when I mean when/if I do it.

Installer FAQ:

* Does the installer back-up the current shiplist files?
** Yes.
* Where are these files backed up to?
** In "opplus\backup" under your SFC:OP directory. The files in "opplus\" are the OP+ shiplist files themselves. Future OP+ versions will have more within this directory structure.

=== NCA-class Variants (from SFB module R10) ===

The coming of the New Heavy Cruisers meant cheaper effective replacements to the dwindling numbers of the venerable heavy cruisers. It's only common sense to also replace variants of said heavy cruisers with new heavy cruiser variants.

NCAs, NCFs, NCMs, NCCs, etc.. a whole array of NCA variants have been added to the OP+ shiplist in version 2.2, from SFB module R10.

=== CVP Patrol Carriers (from SFB module J2) ===

With no heavy weapons, these CWL-variants come with 12 fighters, based on 18 in SFB. These carriers are to be respected, despite their size. All fighter-based races recieve them.

=== CVD Interdiction Carriers (from SFB module J2) ===

Also with no heavy weapons, the Interdiction are modified CA-sized ships. their SFB version have 24 fighters, which gives them 16 in SFC. Basically, all races can have "H-CAV"-like ships now.

=== Implementation of the new arcs in patch 25410 ===

7 new arcs have been implemented in OP Patch version 2.5.4.10. These are:

* FALX/FARX -> FAL/FAR + right down rear
* LSRF/RSLF -> LS+RF / RS+LF missing arcs
* RRP/RLP -> Rear plasma arcs good for some tugs and HDWs.
* LR -> L+R arc used on the Hydran Fire Support Pallet

Also note the fixed LWX arc in SFC:OP 25410. It's been restored onto ships that use it as of OP+ version 2.2 .

=== "Real" Armed FRDs from SFB ===

The "Real" SFB-like FRDs have been added instead of the stock FRDs. These have weapons, usually 2 heavy weapons, 2 ph1/2s and 4 ph3s. They're not overly armed, but they should dismiss the "fodder" reputation the FRDs have in SFC.

=== PF Acceleration changed to 15 ===

Briefly said, the PFs were accelerating as quickly as a normal ship, which I found wrong. I changed it to the SFB standard of 15 per turn for all PFs and Interceptors.

=== Heavy Weapon mount splits ===

Many ships have been improved by splitting some number of weapons into many separate weapons. This will allow for different settings among the groupings, and more pseudos for the plasmas. Effectively, the affected ships seem more complete this way.

=== LWX arc workaround (arc fixed in 25410) ===

The LWX mount is simply broken. It is an arc which encompasses LS+RR. The closest replacement is the LS arc itself, since it overshoots by 10 degrees both in front and at rear. That means the LWX is only 20 degrees wider than the LS arc.

All ships with weapons which have the LWX arc, or HAD the LWX arc but have been replaced by RX or RAL/RAR arcs have been changed to LS/RS arcs.

NOTE: In OP 25410, the arc has been fixed, so restoration in the OP+ shiplist 2.2 has been applied.

=== Basic Hydran fighter KillerBee.I change to 2 BPV ===

BPV stands for "Battle Point Value" but what it really means is "how good a ship is in a fight." .. with that in mind, all the stock Hydran 1 BPV fighters have been increased to 2 BPV and the carriers have recieved appropriate BPV increase.

Hydrans, don't fret. While the carriers are more expensive, upgrading to a better fighter will be cheaper.

=== Ships with drones and special sensors will have 12 Drone Control ===

This was a good idea. I increased the DroneControl by 6 on any ship with both drones and special sensors. This will help out some drone cruisers which include these special sensors in their design for exactly that task.

NOTE: This works to a max of 12 DC only. Ships that have 12 DC already will remain at 12 DC. Sorry, buggy game.

=== Year Last Available date changes ===
A massive revision of the shiplist resulted in an across-the-board change of YLA dates. Expect ships to become unavailable when playing single-player or online D2 as refitted versions of ships replace the unrefitted ones.

ie:
The F-DN is introduced in 2248. It will disapeer in 2274, making way to the F-DN+ which is a major overhaul/refit of the ship. The F-DN+ appears in 2272, and will disapeer in 2277, making way to the F-DNG. The F-DNG appears in 2275 and remains for the rest of the game.

This is a major shiplist change introduced in version 2.0 of the shiplist.

=== Y175 drone refit and reloads changes ===

Around 2275, all empires have come through with new technologies allowing already-existing ships to improve their ordinance through a minor refit. The Y175 refit increases the number of available dronerack reloads, improves some AMDs and even allows better droneracks to be installed altogether on the various warships.

Many additional ships were added as a result of the 'fleshing out' caused by Y175 refits. These will be marked with a "R" code appended to the ship's codename. These refits involve upgrades from Drone-A racks to B or C-racks. All racks that had just 1 reload prior to 2275 will now have 2, and some that had 2 now have 3. ADD6s become ADD12s in most cases.

In some cases, it meant splitting the ship into 2 separate entries: before and after Y175. Appropriate BPV adjustments have been made. Specifically:

* 1 BPV for A-rack -> B-rack (1 reload to 2, change to B racks)
* Usually ADD6 before Y175, ADD12 after Y175.
* 1.5 BPV (round up total) per ADD6 -> ADD12
** ie: 3 BPV for 2 ADD6s -> ADD12s upgrade
* 0 BPV for A,B,C,G-racks already in place. (reload upgrade only)
* CX racks should have 3 reloads.
** C racks on X ships
* GX racks should have 3 reloads.
** G racks on X ships are really like B racks with 2 reloads. In OP+ 2.2, the GX racks have been replaced by B racks with 2 reloads on player demand. In versions 2.0 and 2.1c, the GX racks are G racks with 3 reloads

There are exceptions. For example, all the D5s came with ADD12s even before Y175. I did not bother making sure post Y175 had the best technologies available to them.

This is a major shiplist change introduced in version 2.0 of the shiplist.

=== "refit" and "refit base" changes ===

To improve the user-interface useability of the game, most incognito refits have been given a name.

ie, ISC ships:
* W refit: rear wing phaser3s.
* P refit: some Plasma-Gs were upgraded to PPDs.
* Y refit: some Plasma-Gs were upgraded to Plasma-Ss.
* Z refit: rear Plasma-Is were installed.

Also, to also an almost FAQ-necessary question, I added what the Monitor support pallet contains in the Refit field. I hope that helps.
ie, F-MONS, Refit: Labs Hull Cargo

This is a major shiplist change introduced in version 2.0 of the shiplist.

=== Re-classification of some ships ===

SFB calls the D5 ships "War Cruisers". These are bigger than the War Destroyers the shiplist was making them pass for. All D5s have been changed to the LIGHT_CRUISER hulltype. I also changed the Romulan version of the D5: R-KDR. The R-KDP is marked as CARRIER.

Similarly, the following ships have also been reclassified:

* R-KCR/R-KCRF: from HEAVY_CRUISER to HEAVY_BATTLECRUISER
* K-F6/R-KFR: from DESTROYER to WAR_DESTROYER
* H-CHC/H-CHA: from HEAVY_BATTLECRUISER to HEAVY_CRUISER

=== Commando ships set to "SPECIAL" ===

All commando ships have been set to "SPECIAL". I investigated their seemingly overwhelming presence in missions to only find that most Taldren-originated ships and all of mine had Commando ships as normal cruisers. This should solve the problem by removing them from standard gameplay. Too bad that also removes it from the D2 shipyards, but there were too many there too anyways.

=== Survey cruisers removed from "SPECIAL" class ===

Unlike commando ships, most survey ships can actually defend themselves nicely. They've been changed back to their respective hulltypes. Expect them in battle more often.

ie: F-GSC is a HEAVY_CRUISER type ship.

=== Lyran ships with INTs appearing way too early ===

Some Lyran ships were being introduced with PFs well too early. Some, like the L-CFF, could be purchased and used at around 2265. That's 12 years before the other races can even THINK of having interceptors.
I made sure no Lyran "F" or "T" variants would appear before 2276, thus balancing out their casual PFTs with the other PF-using races.

=== X1 Ships ===

During the Andromedan Invasion, new technology was developed and became available to all of the galactic forces. This was called "X-Technology" and was introduced in the form of refitted cruisers.

The X1 ships were added to the game for all the races involved. X1 ships start appearing around year 2292 and up from there. This is 10 years after SFB prototypes due to limitations of the game itself: Advanced Era does start until the 2290s.

All the X1 ships I could get my hands on were added, including those from Captains Logs I have access to. If I encountered incorrect X1 ships in the Shiplist entered by Taldren, I removed them. The real X1 ships seemed more.. .. ..appropriate: X1 ships were really more refits than anything. These replacements are quite visible in the compare.txt file as X1 ships with massive modifications. They're really replacements with the same name.

The Orion races get 3 variants for weaponry per X-ship class. I had to use my judgement for their loadouts. Perl scripting made this task possible.

Some of the plasma x-ships which would normally have Plasma-Ms have been fitted with Plasma-R in this shiplist. The charging costs are the same, and so are their ranges. Some ships have had their plasma-Ss downgraded to Plasma-Gs to compensate. When I could not compensate, I increased the BPV by 10 per Plasma-M to Plasma-R upgrade. I know it's a lot, but it feels about right.

ie: ISC I-CCX.
NOTE: In version 2.2, the PLaGs have been restored to PLaSes, and the BPV increased for the PLaRs as compensation instead.

In SFC, X1 ships do not benefit from enchanced loading methods for the heavy weapons, like in SFB. There is no easy way to calculate the difference in BPV this would have, therefore no changes have been done to X-ship BPVs regarding this matter. (Blame it on the higher contruction costs?)

I've decided to ignore the errata for the X1 ships BPV. This game was designed using the pre-errata rules for x-technology and therefore should use pre-errata BPV.

=== X2 Dates adjustments ===

Once the Andromedans were repulsed, more resources were devoted to design and manufacture of new classes of ships and weapons. These are known as the X2 ships, and are nothing like the ships previously seen.

It just didn't seem to make sense to have *ALL* X2 ships appear in 2300. There should be prototype introductions, as well as creation of various other hull types. Also, not all races create ships at the same time. There is a certain pattern to this: Federation is almost always first. The Klingons and Lyrans are usually not far behind. The Hydrans, Kzinti and Romulans tend to develop technology as a later response. The ISC and Gorns seem to be tardy in their development.

The new dates for the X2 ships should reflect this. None of the X2 ships were otherwise changed.

=== Light Dreadnoughts ===

Built early in the General War, the light dreadnoughts acted as heavy fast raiders. Production ceased as heavier "true" dreadnoughts proved to be a better allocation of available ressources.

The only races I saw having Light Dreadnoughts were the Gorn and the Klingon. That didn't seem right to me as all races have them. With 45 Warps, but a movement cost of only 1.25, these "Light Dreadnoughts" needed balance, and balance was found in the SFB material: everybody's got one.
The K-C5 and the G-DNL aren't alone anymore.

=== Early Dreadnoughts ===

Appearing at around 2250, early dreadnoughts were built as command ships with the weaponry of heavy cruisers, but with more staying power and energy. The technology of the day was insufficient to allow more appropriate weaponry on these massive new hulls. Most early dreadnoughts survived the General War and were converted to standard dreadnoughts.

Again, only a few races have DNEs in SFC:OP. All races are supposed to have them and they were all added accordingly.

NOTE:
SFB module R7 lists the F-DN as appearing in Y148, not Y167 as listed in previous SFB modules or SFC:OP. The date for the F-DN has been adjusted and this shipclass will act as the Fed's early dreadnought.

=== Additional Corrected Heavy Dreadnoughts ===

Heavy Dreadnoughts appeared as upgrade refits to the standard dreadnoughts. Heavy dreadnoughts are to dreadnoughts what command cruisers are to heavy cruisers.

Some of the Heavy Dreadnoughts already in the game didn't match the Heavy Dreadnoughts in the standard OP shiplist. Instead of removing the old ones, I've renamed the old dreadnoughts if necessary and kept them as well as adding the real ones from SFB into the game.

Renamed Taldren dreadnoughts:

* G-DNH -> G-DNHph (Heavy Phaser Dreadnought)
* L-DNH -> L-DNHE (Heavy ESG Dreadnought)

Renamed SFB dreadnoughts, added but conflicting with already existing Taldren dreadnoughts:

* F-DNH -> F-DNHadd

Imported DNH from EAW, because a problem was fixed there first:

* Z-DNH

=== Fast Cruisers ===

Mostly used as special units for reconnaissance and raid missions, these ships were seen as failed experiments from the dawn of the General War. Their increased warp power design proved unstable with the standard weaponry load of a normal heavy cruiser. Heavy weapons had to be removed, replaced instead by additional phaser array emitters.

As per SFB module R6, all races now have Fast Cruisers. Find Them. Use Them. They're fun. Note that these were usually prototypes and are normally marked as "R" for restricted ships.

=== Heavy War Destroyers ===

Smaller than previous war destroyers, the heavy war destroyers are an efficient late-war design intended as replacements for the many lost support and variant smaller ships. They tend to carry a few fighters on board for extra firepower, if their race's doctrine permits it. These ships were quite modular, allowing a shipyard to overhaul the ship to any needed variant.

The Heavy War Destroyers in SFC:OP aren't giving them justice. These ships are far superior than what the standard shiplist contains. In fact, the Fed HWD is missing 6 center warp!

SFB's R6 contains rules on how these ships are truly picked and designed. They're shown in their basic skeletal variant in the SSDs. There are still 'optional systems' mounts left unfilled, as well as Weapons Options mounts. These are known as "NWO" (Non-Weapon Option) and "WO" (Weapon Option) and it's up to the player to choose what these systems are based on available charts. The chosen system also increase the BPV of the ships.

I have created as many useful variants these ships can be 'morphed' into as possible. Most races have 3 battle configurations (the Gorn have 4). All have Commando, Escort, Exploration and Carrier/PF Tender variants. That's 7 ships added per race, much more if you count the many Orion weapon configs they may have.

NOTE: In OP+ 2.2, another variant has been added: Marine Assault. Basically, it's the maximum deployment of transporters on the HDWs, for maximum offensive effectiveness.

=== Tugs ===

Mostly used as priority military or government cargo transports, tugs are full-fledged starships with limited armament suitable for its mission. However,they are capable of carrying massive 'pods', which are not necessarily all cargo holds. Available pods vary widely. However, combat-related pods such as commando pods, carrier pods and battle pods allow the tug to actively participate in important battles.

I've added all cargo-carrying tugs variants for scenario generation purposes. The tugs with no pods are set as "Heavy Cruisers" or "Light Cruisers", depending on their size. The tugs with cargo pods attached are set as "Special", type "R", hulltype "Freighter". These will remain present in the game in case someone feels it's useful enough to create scenarios with them. They're also going to appear under the D2 if this shiplist is used.

Be careful to check the Movement Cost of the tug you wish to play. Some tugs are slow and heavy, and will not move quickly nor maneuver well at all. These restrictions are per SFB rules, and seem accurate. The slowest battle-worthy tugs in the game are the Federation F-BTV and F-CVTC. Try the F-CVTC with a full complement of 24 fighters. You'll just love it despite the slow speed (16 max?).

Tugs with self-defense pallets have not been added to the game, to avoid clutter and make room in the shiplist.
NOTE: The exceptions, Hydran H-TUGsdp and H-TUG+sdp, have 8 gatling phasers (ph-G). That made them interesting ships to play. The SD Pallet added 4 ph-G 360, so I couldn't resist adding them once it was pointed out to me.

Some of the BattleTugs are vicious ships and have been rated as "Heavy Battlecruisers". In the many games I have played with this shiplist, this decision was well justified.

=== Casual PF Tenders ===

By adding a clamp mechanism to a tractor beam system, practically any ship could be adapted to carry PFs into battle.

I've added many casual carriers to the shiplist, mostly with the intent of maintaning the balance. More precisely, the Gorn and Romulans were seriously lacking in the Carrier department, so I've made some logical additions.

Note: I started off by adding any Casual PFTs with the mechlinks already drawn onto the SSDs.

* G-CCHF
* G-BCHF
* G-BBF
* R-SPJF
* R-KEF
* R-KCRF
* R-KVLF
* R-K10RF
* R-KCNF

Also, almost all large Lyran ships are considered to be capable of Full PFT duty. These ships, starting from the L-BCH to largest, will now have a "T" varient (for tender) capable of carrying a full load of 4 PFs. The original "F" designs with 2 PFs will remain available.

* L-BCHT
* L-DNT
* L-DNLT
* L-DNHT
* L-BBT

Oh.. and BTW..
I took the liberty of adding "F" PFT variants of the Lyran X1 and X2 ships.
Be warned. *EVIL LAUGH!!*

=== Battle Carriers ===

Already capable warships, the BattleCruisers and Heavy BattleCruisers are actually refittable as carriers.

To balance the BCV category, Romulans and Gorns also needed BCVs. A couple of SFB ships had to be modified from their original SSDs to fit the role.
Specifically:

* R-TH (ThunderHawk)
** Normally carries 8 fighters, 2 shuttles and 6 PFs. Fighters have been completely removed to match Romulan no-PF philosophy in SFC:OP. 4 shuttle boxes have been added, increasing the number to 6. The BPV of the ship has been adjusted to compensate for the other 4 missing shuttleboxes.
* G-BCS
** Normally carries 6 fighters, 2 shuttles and 6 PFs. All fighterbays have been converted to shuttlebays. (Gorns with 8 shuttlebays are not unseen in this game.)

Both of the above-mentioned ships have been reduced to 4 PFs like all the other PFTs in the game.

=== BattleShip Carriers ===

BattleShip Carriers are true monsters. These flagships were heavily modified to carry large number of fighters to supplement their already vast firepower.

More BBVs have been added to the game. Specifically, the "I-BBV", "F-BBV", and "Z-BBV" now join the "H-MNV", "K-B10V" and "K-B11V".

PF-based races, such as the Gorn, Romulans and Lyrans, now have CasualPFTs for their BB classes.

The TigerHeart don't have any Dreadnoughts or Battleships. Read go check the SFC:OP manual about this.

=== Fast Resupply Frigates ===

These frigates were designed mostly as prioritive cargo transports between industrial and production centers and front-line carrier groups. Their cargo holds were specially designed for carrying replacement fighters and pseudo-fighters, as well as lodging replacement crews. In a pinch, they were also capable of acting as carrier escorts.

These are lightly armed cargo frigates used as fast freighters for carriers. The supply fighters and parts necessary for these carriers and are strategically important. Tactically, they suck, but I added them to the game anyways.

=== Monitors ===

Monitors are usually sent to defend planets, or to establish a military presence in a remote sector until a properly defended outpost can be established. They are very slow yet very powerful ships with enough firepower to induce caution within any would-be invader.

Like the above brief description states, they're slow but strong. Attacking them feels like you're charging to meet a slow yet nasty brute which has long enough arms to punch you and keep you back. Playing one is as difficult: you're slow with a max speed of 14 within SFC. Your fantastic phaser arcs will defend you nicely, but if you're overwhelmed and outmaneuvered, you're dead.

Almost all Monitors are identical, for all the races that have them. Here's a rundown of their base systems:

* Power: 27 total
** 6 Warps total, 3 on each side.
** 3 Impulse Power
** 18 APRs
** 8 Batteries
* 36 shields, all around
* 2 Transporters
* 4 Tractors
* 0 Labs
* 6 Hull
* Up to 6 shuttles

Monitors may carry a pallet. There are 3 pallets available. All pallets cost 15 BPV, fighters/PFs not included:

* Support Pallet
** 6 cargo, 6 hull, 6 lab (very useful for shield regen)
* Carrier Pallet (if applicable)
** 2 cargo, 9 fighters (12 fighters * 2/3 ratio)
* PFT Pallet (if applicable)
** 2 cargo, 6 mechlink tractors, 4 PFs (6 PFs * 2/3 ratio)

I did not enter any SCS Pallets nor the equivalent Federation Heavy Carrier Pallet. Why? The SCS pallets mix fighters and PFs. The Fed CVA pallet is the quivalent pallet but I didn't want to give them an advantage.

Please notice that I've used the Fed merchant ship skin/model for these ships. The merchant ships roughly but accurately look right for the part: big hull, with little itty-bitty warps sticking out the sides. (Compared to SFB SSDs)

=== Additional PFs ===

==== Escort PFs ====

Other PF variants were also designed. Some were to carry hypothetical fighters into battle. Others were to lay minefields. There were to be even commando and cargo-carrying PFs. But as a design proving to be much more successful than expected, the escort PFs were useful additions to any fleet.

The escort or phaser PFs had less heavy weapons, but more phasers or Plasma-D racks specially placed for defensive purposes. These ended up being cheaper to manufacture than the other PFs.

PF Variants can be found in the module K rulebook. There are cargo, commando, minelaying and escort PFs and all are official. For the purpose of this shiplist, the escort PFs sound like they've got the right scope in mind.
Evidence shows that Taldren's way of calculating a PF's BPV seems to have been to put it into the game, but always letting the insertion program calculate the BPV for them, with a balance of -5 BPV, for all PFs. I've done the same for the added Lyran, Gorn and Romulan escort PFs.

Most of these PFs will never become "drone bait". When I showed strafer these ships as potential additions (from module K) and how I would do it, all he told me was "I approve".

==== Lyran PFL ====

The standard L-PFL has been added. It's just like a L-PF+, but with the transporter, t-bomb and couple of marines. I used PFLs from the other races as templates.

==== StarHawk PFs ====

Following the modular design, the Romulans also have a series of PFs called the StarHawk PFs.

==== Brigand Interceptors and Bucaneer PFs (TigerHeart) ====

Since the TigerHeart only have small ships, it's fair to increase the roster with other existing PFs the pirates would normally use. I gave these PFs weapons as per the Orion Pirate weapon option mount rules, and weapon availability due to cartel location.

The drone-carring variants are particularly effective. But since the PFs don't have their own drone control (and its passed on to the mother ships), I installed OAKDISK (and paid the BPV for it) on all PF-carrying TigerHeart ship.

Find out more about the additional PFs.

=== Additional Orion hulltypes and classes ===

Many orion ships are missing from the game. To make things interesting, I took special interest to the Salvage cruisers and their variants. You see, the SAL variants include PFTs and CVLs which the Orion dearly need in light cruiser classes.

Also, I took the liberty to review all of the current pirate entries and design additional variants based on proper SFB rules: 70% of option mounts must take weapons/systems from local empire, 20% are from the "Operation Zone", and 10% may come from anywhere. I would like to think I just made things a little bit more interesting. Look for pirate ships with variants "0".
In all, hundreds of the additions may be attributed to the pirates.

=== Pirate fighters ===

In SFB, the pirates don't have their own fighters. They buy from their local empire's "black market" and equip themselves with such.

... however...

In SFC, they all have their own fighters, except for TigerHeart of course.

I took the liberty to copy fighters from the normal races to the pirate races of that region. That means that additionally to Taldren's design, they'll be able to use other fighters from their local region too. ie:

* Orion Pirates --> Federation fighters
* Korgath --> Klingon fighters
* Camboro --> Mirak fighters
* BeastRaiders --> Hydran
* Wyldefire --> ISC

Also, .. a new set of entries of fighters have been added to help some compatibility issues: "Neutral" race fighters. Normally, "Neutral" units are used in Taldren-written mission scripts for some specific tasks.

Namely:

* N-SH (Shuttles)
* N-PE
* N-IE
* N-HE
* N-AE
* N-PM
* N-IM
* N-HM
* N-AM
* N-PL
* N-IL
* N-HL
* N-AL

Note: the Syndicate (Gorn) and Prime (Romulan) cartels don't get local fighters. There are no local fighters to use as these empires have PFs.

==== Additional WYN hulltypes and classes ====

I went through the SFB material here and stuffed the shiplist with as many WYN ships I deemed appropriate. I put in the Auxiliary conversions, as well as the other donated or captured ships found.

Please note:

I didn't put in any Orions because they would inherit engine-doubling if I put the ship under any Pirate race. The WYN do not have engine doubling. I didn't bother with the WYN fish ships. At that point, you may as well give them their own race.

Here's a list of the WYN Ships in the OP+ shiplist, thanks to yet another perl handy-dandy script I wrote for myself:

K-WG2 - FF
K-WG2+ - FF
K-WE4 - FF
K-WE4+ - FF
L-WPBC - FF
L-WPBCF - FF
L-WAXPFS - FF
L-WLDD - CL
L-WLDD+ - CL
L-WLDDP - CL
L-WLDDR - CL
L-WLDDF - CL
L-WPBB - CL
L-WPBBF - CL
L-WAXBS1 - CA
L-WAXBS2 - CA
L-WAXBS3 - CA
Z-WAXC1 - FF
Z-WAXC2 - FF
Z-WAXC3 - FF
Z-WAXCC - FF
Z-WAXCC+ - FF
Z-WAXCV1 - FF
Z-WAXCV2 - FF
Z-WAXCV3 - FF
Z-WZFF - FF (See note: *)
Z-WZFF+ - FF (See note: *)
Z-WZDF - FF (See note: *)
Z-WAXCX1 - FF
Z-WAXCX2 - FF
Z-WAXCX3 - FF
Z-WFZX - FF
Z-WDW - CL (See note: *)
Z-WAXBC1 - CA
Z-WAXBC2 - CA
Z-WAXBC3 - CA
Z-WAXB1+ - CA
Z-WAXB2+ - CA
Z-WAXB3+ - CA
Z-WAXBV1 - CA
Z-WAXBV2 - CA
Z-WAXBV3 - CA
Z-WAXCVA - CA
Z-WACVA+ - CA
Z-WAXDN1 - DN
Z-WAXDN2 - DN

NOTE: * Not all above ships are new. Some were already in the OP 25410 shiplist. No WYN ships previously in shiplist have been removed. All are entered with the first letter "W", with HullClass "SPECIAL".

=== Adjustments to existing ships ===

==== The H-IC (and H-IC+) has 40 fighters in SFB. ====

Taldren's 2/3 fighters rule was broken for this ship, equipping it with only 16 fighters. Strafer wanted this to reflect the real power this ship is under SFB, so was modified to carry 24 fighters in SFC:OP, the 2/3 limit. The BPV was adjusted, don't worry.

==== The earlier versions of the R-KVL were added ====

They're listed as the R-WVL and the VUL+. These are equivalent to the eras the R-WE and the R-WB+ appeared. Try them. They're fun. Their BPV was increased to compensate for "cheese" factor and abuse, much like the R-KVL in the 2525 patch. We based our calculations from the latest SFB material containing the Vulture class: Y1, Early Years.

==== weapons moved to visible mountpoints ====

Some mountpoint manipulations have been done to allow use of previously 'hidden' weapons. With EagleEye Software's ShipEdit editor, it was a simple matter of browsing through the entire list, and move things around a bit.
ie: merge weapons of same type and arc here.. shuffle mountpoints there..

Also, some ships will appear with X-Ship UIs to allow all weapons to be useable/targettable.
ie: F-BTV

Note that for PFs, the editor was useless for viewing mountpoint locations. I had to figure out where the mountpoints were on my own. Please note that any phaser mounted on a HeavyWeapon point (mounts 1-10) will NOT charge the phaser capacitor. Let me share that information now:

https://klingon.lostexiles.net/OP_plusrefit/editor_lyran_pf.jpg
https://klingon.lostexiles.net/OP_plusrefit/editor_romulan_pf.jpg
https://klingon.lostexiles.net/OP_plusrefit/editor_gorn_pf.jpg

==== The Federation F-DN is now considered an Early Dreadnought ====

Its year of availability and retirement have been adjusted to 2248-2275. The F-DN+ comes out in 2272.

==== X1 and X2 dates have been changed ====

* Existing X1 ships' intruduction dates joined the other added X1 ships at around 2292-2297.
* X2 ships have been 'staggered' to emulate prototyping and introduction of the various ship classes. It didn't make sense to have all X2 ships appear at once at 2300.

==== shipnames, refits and base refitclass fixes ====

Some shipnames, refits and base refitclass were entered incorrectly in the shiplist.txt file. These changes are easy to spot with the compare.txt file. This is just a cosmetic change to allow proper strings.txt and shipnames.txt coverage.

==== Basic pirate fighters have been changed from PM to PE fighters ====

This will allow "early" carriers to carry "early" fighters.
ie: the SAL carrier variants "CVL" and "LVS".

==== Many ships from module R7 have been entered incorrectly. ====

They've all been revised (or added at all for that matter). R7 is called "Dreadnoughts at War" and covers the various yet unmentionned DNs and variants for the various races.
For more information, please visit the sections about Light Dreadnoughts, Heavy Dreadnoughts and Early Dreadnoughts.

==== TigerHeart's "CV" is a DN ====

TigerHeart's "CV" class has been moved to the DN class despite the fact that it's not a DN. Why? They don't *HAVE* a DN and that caused some problems for some multiplayer games on Gamespy and Local LAN.

==== Some carriers had insufficient or no deckcrews. ====
Fixed.

==== Some drone-equipped ships had insufficient drone control ====
Fixed.

==== B10 fixes ====

The B10 series weren't entered properly. The KBB UI did not have sufficient weapons slots to cover the entire ship. However, the KDN class does work fine for these ships and was adopted as the B10 variant UI. The Romulan K10R variants seem to be fine.

=== Shiplist Limits ===
Taldren has been kind enough to raise the limit of ships to 128. That's 128 ships PER hull class PER race. Believe it or not, I had well filled the previous limit of 64.

ie: There can be 128 Lyran frigates, 128 Lyran Light Cruisers, 128 Lyran Heavy Cruisers, etc.

OP+ Contents and Changes

2019-09-13T23:09:43Z

Firesoul: /* Executable Installer */

== OP+ 4.1.1 Changes ==

=== Fixes: planet hardpoints, again ===

* the planet hardpoints weren't quite right, and the planets were still shooting themselves. I've increased the diameter a bit and it works better now.

=== Fixes: monsters with 'NT' flag: can't transport to them ===

* It was possible to instantly kill/win against a monster by transporting a single Boarding Party to it. I made the monsters non-transportable. This is kinda important for the BeastRaiders!

=== New: separate version of ftrlist.txt and shiplist.txt for single-player D2 ===

* All fighters are available until year '999' for normal multiplayer.. however, that's just silly and sad for a D2 experience. I've created a different version for the D2 experience where older fighters/PFs are phased out.
** to have different phase-out for the PFs, there has to be a different shiplist.txt file as well.

== OP+ 4.1 Changes ==

=== Orion Pirates: TOTAL REBOOT ===

The pirate ships have all been recreated from an templating system of my design.

* Pirate ship Templates
** I entered, from SFB SSDs, all the base pirate ships I want to use. These ships are mostly weaponless, in their pre-configured form.
* Weapons and Systems reference
** I coded the various allowed weapon costs and arcs based on SFB Annexes for option mounts:
*** Annexes #8B and #8H
*** ie: plasma with Swivel cost more than plasma without! Different arcs
*** ie#2: systems in mounts possible!
* I then spent weeks creating tons and tons of replacement pirate ships, all with ACCURATE BPV, arcs and weapons for their region of space!
** under test coverage!
** far more accurate!

The pirates are now accurate, complete and are far closer to accurate SFB rules. The majority of them are better than they used to be.

==== Power Boost, ''à la Taldren'' ====

Did you know the housekeeping costs in SFC are inflated? Yes! For example, if you have any tractors exist on your ship, 0.5 power is automatically put aside. And there are other costs beside that which I could not identify.

Normal costs:
* probe: 1.0
* transporters: 1.0 per 5

So. I have decided to take a AR from SFC-OP 2.5.5.2 and one from OP+ 4.1.. and compare them. Basically:

* the OP stock pirate has a probe. (as expected)
* the OP stock pirate has 2 APRs!

Further investigation has revealed that Taldren has indeed added power to its pirates. Thus, I have decided to do the same, since it looks like this extra power counteracts the expensive housekeeping and makes the pirate ships useful.

The power boosts are allocated by sizeclass:
* sizeclass 4: +1 APR, +2 BPV
** frigates, destroyers
* sizeclass 3: +2 APR, +4 BPV
** light cruisers, war cruisers, heavy cruisers, BCHs
* sizeclass 2: +4 APR, +8 BPV
** Dreadnoughts, battleships

==== No Probes ?! ====

Yes. No probes. As per the SFB SSD. Deal with it!

''(In fact, removing the ship's probe launcher improves the powercurve of the ship.)''

=== Ships from Module X1R (X-Ship Reinforcements) ===

More Official Full X-Ships!

* Advanced Technology War Cruisers (and variants)
* Advanced Technology War Destroyers (and variants)
* Advanced Technology PF Tenders and Carriers

=== Partial X Refits ===

Module X1R also provides very useful rules to do Partial Advanced Technology upgrades to any ship still in service. This counts as an extra refit for ALL ships in the game. These refits were put into place programmatically based on rules provided by ADB. I also re-used some of the previous X-Ship conversion rules for upgraded weapons and systems, as well as BPV costs.

The following systems get partial upgrades:
* Phasers
* APR power
* Drone Racks
* Plasma Torpedos
* Batteries
* limited distruptor upgrades (ranges only)

=== Ships from Module R11 (Support Ships) ===

Module R11 provides a few interesting classes of ships: support ships.
ie:

* Fast War Cruisers
* Transport Frigates
* Heavy New Heavy Cruiser Scouts
* Light PFTs
* Pods for Tugs: Scout, PF transport, fighter resupply
* Advanced Technology Fleet Repair Docks (FRX)

=== Ships from Module R12 (Unusual Ships) ===

More ships!

ie:
* Heavy War Cruisers experiments and prototypes
* Battle Frigate variants
* Various and many odd ships

=== No-fighter refit eliminated ===

No one liked it. It served no purpose. ... so I got rid of them. I also merged in the 'F'ighter refits: if the ship gets them, then the ship gets them without any other options.

ie:
* most/all Y180+ Lyrans will all be carrying PFs.
* Heavy War Destroyers

=== Shiplist swapper ===

I've included a shiplist swapper for those who are reluctant to switch away from OPPlus 4.0. In some cases, the concern is completely valid: uninstalling OP+ 4.0 will blow away customizations, such as custom models, etc.

To be able to do this, I've changed things so that all files install to ''opplus41/'' instead of just ''opplus/''. That means the OP+ 4.1 installer isn't overwriting OP+ 4.0.

==== Why a program? Why not a batch file? ====

The program fetches the install location of SFC:OP from the Registry. That means that if you installed it in D:\my_games\SFCOP\ , '''''it will still work'''''. Additionally, it asks for administrator privileges, just in case.

==== Where is it? How do I use it? ====

It's in the start menu, with links for OP+ 4.1.

http://klingon.pet.dhs.org/OP_plusrefit/opplus_41_shiplist_swapper.png

See: [[OP+ 4.1 ShipList Swapper NSIS source code]]

=== Tugs as Freighters ===

Cargo-bearing tugs are now in the 'F'reighter class of ships: frees up room for more ships and allows for some interesting Convoy Raids.

=== Planets hardpoint fixes ===

* Work done by: Tus-XC, FireSoul
* Suggestion by: Dizzy

It's a sweeping fix. What is involved is that the shiplist for all the planets with weapons are redone and then the models themselves will have to be rehardpointed. The hardpoints are currently located anywhere from 5 to 7 range above and below the equator on the physical planet model itself, which obviously causes point defense weapons not to fire because if a ship approaches the equator, the point defense weapons are too far away to fire.

Make note that any weapon that ignores a fire arc should not be used on a planet as firing through the planet mesh occurs and the resulting sound collision from that fire is quite annoying. Below you will see the planet fire arc where HW1 is the front of the ship. HW1 stands for heavy weapon hardpoint 1 and is the 1st heavy weapon column in the shiplist. PH11 stands for the 11th phaser hardpoint and corresponds to the 11th weapon column in the shiplist.

* The Yellow arcs should be Ph3 hardpoints which should be present on '''''ALL''''' planets.
* The Blue are the Ph4's which should be standard on all armed planets.
* The Red should be heavy weapon hardpoints that should be on all armed planets.
* The Orange should be optional heavy weapon hardpoints.
* The rest shaded grey should be only used for homeworlds.
* Ph1/2's should not be used on planets as it would give the planet too many defensive phasers.

I do not remember testing to see if a planet can make use of defensive tractors vs drones. I think they do, and I would give

* all planets 6
* homeworlds 12

I am fuzzy on the artifex program and do not remember specifically which planets are referred to as colony world, core world and homeworld. If there are other designations artifex uses that the scripts and the map match up, it would be easy to simply use the existing planets as a reference and arm them from the stock taldren template using the fixes I have made.

http://klingon.pet.dhs.org/OP_plusrefit/planet_arcs_v2.jpg

-- Dizzy,
[http://www.dynaverse.net/forum/index.php/topic,163390750.msg1123020912.html#msg1123020912 http://www.dynaverse.net/forum/index.php/topic,163390750.msg1123020912.html#msg1123020912]

=== Andros as Monsters ===

The idea is to implement random encounters with some early basic Andro ships. Nothing fancy: just use the more basic ships of each hull class and add them to the Monsters race.

==== PA Panels ====

PA Panels don't exist in SFC-OP. We're going to give the ships equivalent equipment based on their effects: shields, toughness and power to the ship.

* Shields
** PA panels are split into 2 hemispheres: front half and rear half.
** count the facing's PA panel.
** multiply by 3.5
** apply the result to each shield part of that hemisphere's facing.
*** ie: 10 forward PA's = 35 shields for numbers 6, 1 and 2

* Labs
** Labs enhance and determine shield regeneration in SFC-OP
** count total of PA panels
** multiply by 5/4 (or 1.25), round up.
** Add as labs in addition to any existing labs
*** ie: the Intruder starts with 6 labs and 14 PA Panels.
**** 6 + (round_up(14 * 1.25)) = 6 + 18 = 24 labs

* APRs
** count total of PA panels
** divide by 4, drop all fractions
** add as APRs in addition to any existing APRs
*** ie: the Intruder starts with 4 APR and 14 PA panels
**** 4 + floor(14 * 0.25) = 4 + 3 = 7 APRs

* No Hit&Runs possible
** Set the SpecialRole in the shiplist to 'NT'. This prevents any transporter activity against the Andro

==== Batteries ====

* Add batteries multiplied by 5. Increase the BPV by 2 per Andro battery (or per 5 added batteries).
** that's 0.5 BPV per extra hit the ship can take.

==== Displacement Device ====

The DisDev in SFB basically moves ships around like a big ass offensive transporter. It can also move friendly units around. We're simulating the DisDev by making the Andro ship more maneuverable.

* +1 HET bonus per DisDev
* +2 acceleration (12 instead of 10) if any DisDev are on the Andro ship

==== Tractor Repulsors ====

The TRBL and TRBH *do* exist in SFC-OP. Use it.

Additionally..
* +1 tractor per TRBL or TRBH.
* Add +1.5 BPV per tractor added.

==== Repair ====

* +2 DamCon Base (and +4 DamCon Max) per repair box on the ship.

==== Hangars ====

Hangars will be empty till the MWPs (fighter-like!) are available.

* MWPs appear in Y175
* They will be housed in the MotherShip hangars instead of SatShips
* The number of hangars and their size will determine their count.
** as per SFB: each MWP group has up to 18 units
** MWPs take 1/4 hangar space
** we're applying the SFB->SFC 2/3 rule
** the Devestator will have 2 groups
* the ship will have deck crews to the same count of MWPs before the 2/3 rule was applied.
** this is for fighter regen
* MTPs (2 TRBLs) will take up to 1/3 of the MWPs in a group, drop the fractions.
** MTP TRBL arc increased from FA to FH due to AI limitations
** TRBL have 2 shots
* ECM/ECCM bumped by 1. (they are supposed to be PFs, initially)

ie: an Intruder has 3 Hangars. That gives it 12 MWPs in SFB. After 2/3 is applied, we've got 8 MWPs for SFC. 6 of those (2 groups of 3) are MWPs, the other 2 are MTPs. The ship will have 12 deck crews.

==== Decoy SSU ====

Acts like a Wild Weasel. Appears in Y186.

* Added a shuttle to Andro ship. Just 1.
* This shuttle will very very very likely be used as a WW by the AI. ;)

==== Enhanced shiplist: Role ====

* role set to CustomRace1. This will be handy for scripts, if someone wants to code an Andro-only mission.

=== Mutiplayer Mission included: Andros! ===

This is a coopace-like mission where Andromedan ships are generated as opponents! The team picked will decide the difficulty.

* Team A: 1.0x player BPV for the Andro ships
* B: 1.5
* C: 2.0
* D: 2.5
* E: 3.0x player BPV for the Andro ships

NOTE! Drones and Fighters information cannot be properly retrieved by the game. It can only be SET. Stupid, I know!

== OP+ 4.0 Changes ==

=== Enhanced Shiplist ===
5 columns were added to the end of the shiplist (it's a text tab-delimited database). Since they're outside the range of the columns used by the game, they are ignored. However, mission scripts can use them by using a modified version of MagnumMan's ShipList API.

You can get this Enhanced ShipList API [[http://klingon.pet.dhs.org/mediawiki/index.php?title=SFC-related_missions,_sources,_patches_and_misc_utilities#SFC_Sources:_APIs.2C_Mission_Scripts here]].

The added columns are:

* Enhanced Class Type -- Much like the already established ClassTypes, these have been expanded to cover many other hull types.
* Role -- Defines the ship's role. ie: Escort, Carrier, LineShip, ...
* Secondary Role -- Same data as Role. Used because some ships have multiple roles.
* Xtech -- A column dedicated to describing what level of technology. Currently has very little.
* ProductionAvailability -- Describes how much a ship of a class was built. NONE, UNIQUE, .. to MANY.

=== Module R9 -- The Ships That Never Were ===

ADB released an interesting module contain prototypes, conjectural or impossible ships. Many ships are good for use in SFC, but some didn't make the cut because they were either impossible in SFB in the first place (X-DNLs) or just plain wrong (Alliance Maulers). However.. there are many interesting other ships:

* DNWs -- War Dreadnoughts -- DNs created from CLs
* DNMs -- Medium Dreadnoughts -- DNHs built from DNLs
* Coalition Dreadnought Maulers -- conjectural designs
* Prototypes, some unique ships that were actually built

=== 4.0 Refit Spans and Revision ===

What I thought was a 2-year span before an unrefitted version of a ship is retired was actually 3: from the beginning of the beginning year, 0, to the end of year 2 spans 3 years. Solution: reduce the span by a year. Most refit overlaps have been thus shortened.

Additionally, I have eliminated this overlap for Y175 refits: too much junk was appearing in D2 ShipYards. The SFB data itself describes immediate refits at Y175, therefore the decision to do this was made easy.

Also, I have taken the time to review data from the SFB books and have reapplied some refits for all the races I could find. In many cases, many changes were warranted and have been applied. For example, the C9K is now far earlier than before.

=== Module R8 -- National Guard units ===

ADB has released Module R8 - National Guard Units. These units are police and homeworld protection units, usually upgraded from mothball status and refitted to current technology.

In this case, all races acquire rear-guard units to their lists, but are restricted in availability (on D2). Yes, they're kinda crappy but they could be used by scripters to make really interesting homeworld defense scenarios.

== OP+ 3.4 Changes ==

=== Massive automatically detected cleanups ===

I've spent much time programming and detecting problems through some common-sense. This resulted in a lot of hard work, but the rewards are many.

* Weapons are valid
* Weapon arcs are valid
* Weapons with arcs don't use a reload value
* weapons with reloads don't use arcs
* number of weapons are between 1 and 4.
* UIs used are valid
* all weapons in use match UIs: no weapons placed in a spot not used by UI.
* all HULLTYPE valid. ie: "DESTROYER"
* all CLASSTYPE valid. ie: "CA"
* PLaDs are not available before Y165

This should insure high quality gameplay and any errors previously undetected.

=== Implementation of G4.31: trading a bridge hit for a lab ===

I remembered a basic SFB rule during the data entry of module R8:

* (G4.3) Lab Substitutions
* (G4.31) Control Space: A ship without labs (...) can use one of its control spaces (G2.11) as a lab.

I have decided to implement this by changing all ships with no labs but more than 1 bridge boxes: add 1 lab, and remove 1 bridge. This will *directly* affect shield repairs since that's what SFC uses. I restricted myself to units where this made sense. (ie: not on PFs.)
Around 2000 ships were affected.

== OP+ 3.3 Changes ==

=== Major Ship Models Review ===

This isn't exactly a feature, however this work took 4 months to complete. All ship models introduced by the OP+ installer have been examined, and optimized at need. This would have affected much around 97% of the ships. Also, many ship models have been created with the intent to add them to OP+.
Optimizations:

* Levels of Details (LODs): All ships must have LODs where the original model's details remain intact on LOD1: closest.
* Improved break-mods: All ships will have break-mods with all the pieces looking complete. This took most of the 4 months to do. However, when a ship blows up, a player won't be looking through a piece and see the other side. A damage texture will be shown.
** Also, the break-mods usually won't be based on the main LOD. That would be a waste of resources and may lag the game.
* Many More Models: Where appropriate, models have been created to represent a class of ship which was misrepresented previously.

=== Strings.txt Tweaks ===

Strafer has taken it upon himself to review the names of ship classes and correct them. This took him about a week to do.

For example, a Lyran HDW would be listed as a "Heavy War Destroyer". Now it's listed as a "Top-Alleycat Heavy War Destroyer". There are many such changes, especially within the Gorns. Go take a look.

== OP+ 3.2 Changes ==

=== Fighterless Casual Carriers ===

In SFB, all carriers are shown with just its base BPV. Unless noted otherwise, fighters are *extra*. Of course, it doesn't make sense to have a dedicated carrier without fighters, but it *does* make sense to allow not having to pay for them if it's optional. This affects many Hydran ships, as well as some others through the shiplist. These ships will be recognizable by the 'n' appended at the end of the ship designation. These ships will be marked as "R"estricted. These ships shouldn't appear on the D2 since that's not how it works for there.

ie:
* The stock shiplist's H-SUI (a Taldren invention) costs 161 BPV.
* The OP+ H-SUI costs 167 BPV (stock fighter price leveled with other races).
* The OP+ 3.2 H-SUIn will cost 155 BPV and will have no fighters. Nothing is put in place to replace the fighters. The fighters are just not there: the player simply didn't pay for them.

=== More ISC fighter corrections ===

Some ISC .III fighters come out before the .II fighters. Dates have been fixed.
From:

I-Restitution.II 11
I-Writ.II 15
I-Tort.II 17
I-Caveat.II 17
I-Restitution.III 15
I-Writ.III 11
I-Tort.III 11
I-Caveat.III 15

To:

I-Restitution.II 11
I-Writ.II 11
I-Tort.II 15
I-Caveat.II 15
I-Restitution.III 15
I-Writ.III 15
I-Tort.III 17
I-Caveat.III 17

=== YLA adjustments to older ships within Advanced Era ===

As a D2 campaign progresses into the advanced era, whether it's online or single-player D2, there seemed to be a LOT of left-over ships that haven't been phased out when they really really should be out of the picture.

Adjusting the YLAs for these ships to be around year 45 (2308), just after all races have recieved introductions for the last of their X2 units, seems like a good time to make all the excess ships disapeer and make the campaign concentrate only to what should be leftover.

This one are for you folks who like to turn a D2 map to a single colour, whatever that colour is for your race. ;)

=== Hullclass and Hulltype reclassifications ===

Ships have been reclassified into their appropriate lists based on their weight (without pods) and # of engines. No, not BPV. Affected are many ships throughout the shiplist.

ie: Simple relocation example: F-NCM
The F-NCM was listed as "NEW_HEAVY_CRUISER" within the CL list. It has a movement cost of 1 and ~30 warps. I've moved it to the CA list with the other NCAs.

ie: Major adjustment example: HDWs.
The HDWs were listed as "WAR_DESTROYER" mostly within the FF list. They have a movement cost of 2/3 and ~24 warps. They've been moved to the CL list, reclassifying them as "LIGHT_CRUISER". They are, after all, heavier than a WAR_DESTROYER.

=== More freighters for all races ===

I've added many many freighters, for all races.

* repair freighters (large and small)
* exploration freighters (large and small)
* troop transport freighters (large and small)
* all freighters for pirates too.
** I've never heard of illegal operations that didn't have some legal front with legitimate operations.

=== Civilian Freighters for all races. (with new model) ===

.. and yet more freighters...

* Free Traders (for everyone)
* Free Traitors (for pirates)
* Free Trooper and Tanker (Marines-related units)
* Federation Express
** The Federation Express is a __CIVILIAN__ service. They have their own fleet of courier ships.

=== Armed Priority Transports ===

Another freighter variant. The APTs are fast, small, and neat little military couriers. All races used these. (with new model)

=== System Activity Maintenance Stations (SAMS) ===

Think as these as small platform stations. These are also used as a kind of listening post in far away systems where other tasks are needed, such as a research station above a planet. For these, I've created a model based on the xdp (Defense Platform) which should do nicely.

Note: They can have various base augmentation modules installed (Hospital, VIP quarters, cargo, sciences, etc..)

Note: Also, similar to the SAMS, I've added a N-CPL Civilian Commercial Platform which also uses the new model.

=== Civilian Base Stations ===

Much like the other Base Stations for all races, most/all races had civilian base stations. These did not have ph4s, and other mount points have some i lesser weapons.

=== X1 and X2 Bases ===

In some cases, I had to more or less feel my way around in the dark to create proper bases for all races in X1 and X2 era. I just didn't seem right that all races had bases of all kinds from beginning to late era, then when Advanced arrives, all's there is a X2-style SBX. Well. I renamed all the SBX to XSBs and added the following:

* BSX - X1 base stations
* BSXF(or P) - with Fighters/PFs.
* XBS
* XBSF/P
* BTX
* BTXF/P
* XBT
* XBTF/P
* SBX
* SBXF/P
* XSBF/P

=== Mobile Bases ===

All races used these as temporary repair and resupply stations during an offensive, or when a base was lost.

Its construction involves 2 specially-made habitable pods that tugs can carry for the center portion of the hull. These pods are accompanied by 4 normal-sized pods installed around. These 4 pods could be just about anything that fits, but normally would be some cargo pods, a repair pod and maybe something else (light battle pod? CVL pod?). Finally, 2 base augmentation modules are installed to fill in the blanks.

A convoy of tugs would normally be sufficient to build this base and set it up.

== OP+ 3.1 Changes ==

=== ISC Carriers now have same ratio of fighters ===

To smooth out the fighter payloads on ISC carriers, the 2/3rds rule for SFB->SFC fighter payloads has been applied to all ISC carriers. I've been told the 1:1 ratio for the carriers have been preserved to compensate for fighters that had no heavy weapons. Well.. Check out the next entry on this page..

=== ISC fighters now have increased hull/armor ===

To compensate with the reduction in fighter numbers noted above, the hull hit capacity on ISC fighters has been improved by 20%. In a group of 4 fighters, that is a tremendous improvement in survival.

=== Non-X2 MIRV loadout variants added ===

In a push to make SFC more SFB-like, conversion rules have been thought up to allow non-X2 ships to be equipped with MIRV racks. Such a conversion would increase the BPV of the ship by 20 BPV.

Conversion requirements:
SFB rules are percentage based on the # of drone spaces on racks. Since that cannot be applied to SFC, the # of racks, themselves is instead used for the count. MIRVs, or MW in SFB, are of a "Limited" type of drone, and has corresponding percentage rules. The percentages are the following:

* 10% of drones on non-Mirak/non-Kzinti, non-X ships can be of the "Limited" type.
* 20% of drones on Mirak/Kzinti can be of the "Limited" type.
* 20% of drones on X ships can be of the "Limited" type.

That means that on a non-X, non-Mirak ship, you need at least 10 droneracks to apply the conversion. (There is actually 1 ship that qualifies: Z-WAxDN1.)
On Mirak or X1 ships, each 5th rack can be converted to a MIRV rack, if the number of drone spaces on the ship is preserved. Usually, that means 2 B-racks become 1 MIRV-rack and 1 A-rack. (Each MIRV drone is similar to the double-space MW drone from SFB. Since a MIRV rack has 4 drones per reload, that means the rack is HUGE, sporting 8 drone spaces per reload. The B rack only has 6, so something has to be done to compensate)

=== ISC PPD ships have PPD mountpoint splits ===

ISC PPD mountpoints have been splits, much like many other weapons have been with this change.

=== Romulan Modular Dreadnought variants ===

The Romulan Modular Dreadnoughts have been populated in with their many compatible and SFB-complient variants. That's a LOT of available dreadnoughts for the Rommies, now.

The modules used are per SFB rules, and originate from the various SparrowHawk and SkyHawk configs. Some modules have been specifically mentionned as illegal,such as the mauler or J PLaS modules. Others are incompatible to the current game.

Dreadnoughts, with modular configs:

* R-DMH, DemonHawk: 2 SparrowHawk modules, 1 SkyHawk module
* R-OMH, OmniHawk Light Dreadnought: 2 SparrowHawk modules.
* R-MGH, MegaHawk Dreadnought: 2 SparrowHawk modules.

== OP+ 3.0 Changes ==

=== Ship Models ===

Models have been gathered and selected for use with OP+. In fact, they're included in the main package of the project. There is also a no_models version for those with no bandwidth or those who want to install their own sets of models.

== Previous Changes ==

=== Executable Installer ===

Thanks to NullSoft's NSIS, I now have an easy-to-use installer for this project. People usually have problems installing the shiplist properly, if they're to have any problems at all. Here's a nice screenshot:

https://klingon.lostexiles.net/OP_plusrefit/opplus_installer_22.jpg

This will have much greater implications in future versions of the shiplist, since I've always wanted to have 2 versions of the shiplist downloadable: 1 with models and 1 without. Aww well, you'll see when I mean when/if I do it.

Installer FAQ:

* Does the installer back-up the current shiplist files?
** Yes.
* Where are these files backed up to?
** In "opplus\backup" under your SFC:OP directory. The files in "opplus\" are the OP+ shiplist files themselves. Future OP+ versions will have more within this directory structure.

=== NCA-class Variants (from SFB module R10) ===

The coming of the New Heavy Cruisers meant cheaper effective replacements to the dwindling numbers of the venerable heavy cruisers. It's only common sense to also replace variants of said heavy cruisers with new heavy cruiser variants.

NCAs, NCFs, NCMs, NCCs, etc.. a whole array of NCA variants have been added to the OP+ shiplist in version 2.2, from SFB module R10.

=== CVP Patrol Carriers (from SFB module J2) ===

With no heavy weapons, these CWL-variants come with 12 fighters, based on 18 in SFB. These carriers are to be respected, despite their size. All fighter-based races recieve them.

=== CVD Interdiction Carriers (from SFB module J2) ===

Also with no heavy weapons, the Interdiction are modified CA-sized ships. their SFB version have 24 fighters, which gives them 16 in SFC. Basically, all races can have "H-CAV"-like ships now.

=== Implementation of the new arcs in patch 25410 ===

7 new arcs have been implemented in OP Patch version 2.5.4.10. These are:

* FALX/FARX -> FAL/FAR + right down rear
* LSRF/RSLF -> LS+RF / RS+LF missing arcs
* RRP/RLP -> Rear plasma arcs good for some tugs and HDWs.
* LR -> L+R arc used on the Hydran Fire Support Pallet

Also note the fixed LWX arc in SFC:OP 25410. It's been restored onto ships that use it as of OP+ version 2.2 .

=== "Real" Armed FRDs from SFB ===

The "Real" SFB-like FRDs have been added instead of the stock FRDs. These have weapons, usually 2 heavy weapons, 2 ph1/2s and 4 ph3s. They're not overly armed, but they should dismiss the "fodder" reputation the FRDs have in SFC.

=== PF Acceleration changed to 15 ===

Briefly said, the PFs were accelerating as quickly as a normal ship, which I found wrong. I changed it to the SFB standard of 15 per turn for all PFs and Interceptors.

=== Heavy Weapon mount splits ===

Many ships have been improved by splitting some number of weapons into many separate weapons. This will allow for different settings among the groupings, and more pseudos for the plasmas. Effectively, the affected ships seem more complete this way.

=== LWX arc workaround (arc fixed in 25410) ===

The LWX mount is simply broken. It is an arc which encompasses LS+RR. The closest replacement is the LS arc itself, since it overshoots by 10 degrees both in front and at rear. That means the LWX is only 20 degrees wider than the LS arc.

All ships with weapons which have the LWX arc, or HAD the LWX arc but have been replaced by RX or RAL/RAR arcs have been changed to LS/RS arcs.

NOTE: In OP 25410, the arc has been fixed, so restoration in the OP+ shiplist 2.2 has been applied.

=== Basic Hydran fighter KillerBee.I change to 2 BPV ===

BPV stands for "Battle Point Value" but what it really means is "how good a ship is in a fight." .. with that in mind, all the stock Hydran 1 BPV fighters have been increased to 2 BPV and the carriers have recieved appropriate BPV increase.

Hydrans, don't fret. While the carriers are more expensive, upgrading to a better fighter will be cheaper.

=== Ships with drones and special sensors will have 12 Drone Control ===

This was a good idea. I increased the DroneControl by 6 on any ship with both drones and special sensors. This will help out some drone cruisers which include these special sensors in their design for exactly that task.

NOTE: This works to a max of 12 DC only. Ships that have 12 DC already will remain at 12 DC. Sorry, buggy game.

=== Year Last Available date changes ===
A massive revision of the shiplist resulted in an across-the-board change of YLA dates. Expect ships to become unavailable when playing single-player or online D2 as refitted versions of ships replace the unrefitted ones.

ie:
The F-DN is introduced in 2248. It will disapeer in 2274, making way to the F-DN+ which is a major overhaul/refit of the ship. The F-DN+ appears in 2272, and will disapeer in 2277, making way to the F-DNG. The F-DNG appears in 2275 and remains for the rest of the game.

This is a major shiplist change introduced in version 2.0 of the shiplist.

=== Y175 drone refit and reloads changes ===

Around 2275, all empires have come through with new technologies allowing already-existing ships to improve their ordinance through a minor refit. The Y175 refit increases the number of available dronerack reloads, improves some AMDs and even allows better droneracks to be installed altogether on the various warships.

Many additional ships were added as a result of the 'fleshing out' caused by Y175 refits. These will be marked with a "R" code appended to the ship's codename. These refits involve upgrades from Drone-A racks to B or C-racks. All racks that had just 1 reload prior to 2275 will now have 2, and some that had 2 now have 3. ADD6s become ADD12s in most cases.

In some cases, it meant splitting the ship into 2 separate entries: before and after Y175. Appropriate BPV adjustments have been made. Specifically:

* 1 BPV for A-rack -> B-rack (1 reload to 2, change to B racks)
* Usually ADD6 before Y175, ADD12 after Y175.
* 1.5 BPV (round up total) per ADD6 -> ADD12
** ie: 3 BPV for 2 ADD6s -> ADD12s upgrade
* 0 BPV for A,B,C,G-racks already in place. (reload upgrade only)
* CX racks should have 3 reloads.
** C racks on X ships
* GX racks should have 3 reloads.
** G racks on X ships are really like B racks with 2 reloads. In OP+ 2.2, the GX racks have been replaced by B racks with 2 reloads on player demand. In versions 2.0 and 2.1c, the GX racks are G racks with 3 reloads

There are exceptions. For example, all the D5s came with ADD12s even before Y175. I did not bother making sure post Y175 had the best technologies available to them.

This is a major shiplist change introduced in version 2.0 of the shiplist.

=== "refit" and "refit base" changes ===

To improve the user-interface useability of the game, most incognito refits have been given a name.

ie, ISC ships:
* W refit: rear wing phaser3s.
* P refit: some Plasma-Gs were upgraded to PPDs.
* Y refit: some Plasma-Gs were upgraded to Plasma-Ss.
* Z refit: rear Plasma-Is were installed.

Also, to also an almost FAQ-necessary question, I added what the Monitor support pallet contains in the Refit field. I hope that helps.
ie, F-MONS, Refit: Labs Hull Cargo

This is a major shiplist change introduced in version 2.0 of the shiplist.

=== Re-classification of some ships ===

SFB calls the D5 ships "War Cruisers". These are bigger than the War Destroyers the shiplist was making them pass for. All D5s have been changed to the LIGHT_CRUISER hulltype. I also changed the Romulan version of the D5: R-KDR. The R-KDP is marked as CARRIER.

Similarly, the following ships have also been reclassified:

* R-KCR/R-KCRF: from HEAVY_CRUISER to HEAVY_BATTLECRUISER
* K-F6/R-KFR: from DESTROYER to WAR_DESTROYER
* H-CHC/H-CHA: from HEAVY_BATTLECRUISER to HEAVY_CRUISER

=== Commando ships set to "SPECIAL" ===

All commando ships have been set to "SPECIAL". I investigated their seemingly overwhelming presence in missions to only find that most Taldren-originated ships and all of mine had Commando ships as normal cruisers. This should solve the problem by removing them from standard gameplay. Too bad that also removes it from the D2 shipyards, but there were too many there too anyways.

=== Survey cruisers removed from "SPECIAL" class ===

Unlike commando ships, most survey ships can actually defend themselves nicely. They've been changed back to their respective hulltypes. Expect them in battle more often.

ie: F-GSC is a HEAVY_CRUISER type ship.

=== Lyran ships with INTs appearing way too early ===

Some Lyran ships were being introduced with PFs well too early. Some, like the L-CFF, could be purchased and used at around 2265. That's 12 years before the other races can even THINK of having interceptors.
I made sure no Lyran "F" or "T" variants would appear before 2276, thus balancing out their casual PFTs with the other PF-using races.

=== X1 Ships ===

During the Andromedan Invasion, new technology was developed and became available to all of the galactic forces. This was called "X-Technology" and was introduced in the form of refitted cruisers.

The X1 ships were added to the game for all the races involved. X1 ships start appearing around year 2292 and up from there. This is 10 years after SFB prototypes due to limitations of the game itself: Advanced Era does start until the 2290s.

All the X1 ships I could get my hands on were added, including those from Captains Logs I have access to. If I encountered incorrect X1 ships in the Shiplist entered by Taldren, I removed them. The real X1 ships seemed more.. .. ..appropriate: X1 ships were really more refits than anything. These replacements are quite visible in the compare.txt file as X1 ships with massive modifications. They're really replacements with the same name.

The Orion races get 3 variants for weaponry per X-ship class. I had to use my judgement for their loadouts. Perl scripting made this task possible.

Some of the plasma x-ships which would normally have Plasma-Ms have been fitted with Plasma-R in this shiplist. The charging costs are the same, and so are their ranges. Some ships have had their plasma-Ss downgraded to Plasma-Gs to compensate. When I could not compensate, I increased the BPV by 10 per Plasma-M to Plasma-R upgrade. I know it's a lot, but it feels about right.

ie: ISC I-CCX.
NOTE: In version 2.2, the PLaGs have been restored to PLaSes, and the BPV increased for the PLaRs as compensation instead.

In SFC, X1 ships do not benefit from enchanced loading methods for the heavy weapons, like in SFB. There is no easy way to calculate the difference in BPV this would have, therefore no changes have been done to X-ship BPVs regarding this matter. (Blame it on the higher contruction costs?)

I've decided to ignore the errata for the X1 ships BPV. This game was designed using the pre-errata rules for x-technology and therefore should use pre-errata BPV.

=== X2 Dates adjustments ===

Once the Andromedans were repulsed, more resources were devoted to design and manufacture of new classes of ships and weapons. These are known as the X2 ships, and are nothing like the ships previously seen.

It just didn't seem to make sense to have *ALL* X2 ships appear in 2300. There should be prototype introductions, as well as creation of various other hull types. Also, not all races create ships at the same time. There is a certain pattern to this: Federation is almost always first. The Klingons and Lyrans are usually not far behind. The Hydrans, Kzinti and Romulans tend to develop technology as a later response. The ISC and Gorns seem to be tardy in their development.

The new dates for the X2 ships should reflect this. None of the X2 ships were otherwise changed.

=== Light Dreadnoughts ===

Built early in the General War, the light dreadnoughts acted as heavy fast raiders. Production ceased as heavier "true" dreadnoughts proved to be a better allocation of available ressources.

The only races I saw having Light Dreadnoughts were the Gorn and the Klingon. That didn't seem right to me as all races have them. With 45 Warps, but a movement cost of only 1.25, these "Light Dreadnoughts" needed balance, and balance was found in the SFB material: everybody's got one.
The K-C5 and the G-DNL aren't alone anymore.

=== Early Dreadnoughts ===

Appearing at around 2250, early dreadnoughts were built as command ships with the weaponry of heavy cruisers, but with more staying power and energy. The technology of the day was insufficient to allow more appropriate weaponry on these massive new hulls. Most early dreadnoughts survived the General War and were converted to standard dreadnoughts.

Again, only a few races have DNEs in SFC:OP. All races are supposed to have them and they were all added accordingly.

NOTE:
SFB module R7 lists the F-DN as appearing in Y148, not Y167 as listed in previous SFB modules or SFC:OP. The date for the F-DN has been adjusted and this shipclass will act as the Fed's early dreadnought.

=== Additional Corrected Heavy Dreadnoughts ===

Heavy Dreadnoughts appeared as upgrade refits to the standard dreadnoughts. Heavy dreadnoughts are to dreadnoughts what command cruisers are to heavy cruisers.

Some of the Heavy Dreadnoughts already in the game didn't match the Heavy Dreadnoughts in the standard OP shiplist. Instead of removing the old ones, I've renamed the old dreadnoughts if necessary and kept them as well as adding the real ones from SFB into the game.

Renamed Taldren dreadnoughts:

* G-DNH -> G-DNHph (Heavy Phaser Dreadnought)
* L-DNH -> L-DNHE (Heavy ESG Dreadnought)

Renamed SFB dreadnoughts, added but conflicting with already existing Taldren dreadnoughts:

* F-DNH -> F-DNHadd

Imported DNH from EAW, because a problem was fixed there first:

* Z-DNH

=== Fast Cruisers ===

Mostly used as special units for reconnaissance and raid missions, these ships were seen as failed experiments from the dawn of the General War. Their increased warp power design proved unstable with the standard weaponry load of a normal heavy cruiser. Heavy weapons had to be removed, replaced instead by additional phaser array emitters.

As per SFB module R6, all races now have Fast Cruisers. Find Them. Use Them. They're fun. Note that these were usually prototypes and are normally marked as "R" for restricted ships.

=== Heavy War Destroyers ===

Smaller than previous war destroyers, the heavy war destroyers are an efficient late-war design intended as replacements for the many lost support and variant smaller ships. They tend to carry a few fighters on board for extra firepower, if their race's doctrine permits it. These ships were quite modular, allowing a shipyard to overhaul the ship to any needed variant.

The Heavy War Destroyers in SFC:OP aren't giving them justice. These ships are far superior than what the standard shiplist contains. In fact, the Fed HWD is missing 6 center warp!

SFB's R6 contains rules on how these ships are truly picked and designed. They're shown in their basic skeletal variant in the SSDs. There are still 'optional systems' mounts left unfilled, as well as Weapons Options mounts. These are known as "NWO" (Non-Weapon Option) and "WO" (Weapon Option) and it's up to the player to choose what these systems are based on available charts. The chosen system also increase the BPV of the ships.

I have created as many useful variants these ships can be 'morphed' into as possible. Most races have 3 battle configurations (the Gorn have 4). All have Commando, Escort, Exploration and Carrier/PF Tender variants. That's 7 ships added per race, much more if you count the many Orion weapon configs they may have.

NOTE: In OP+ 2.2, another variant has been added: Marine Assault. Basically, it's the maximum deployment of transporters on the HDWs, for maximum offensive effectiveness.

=== Tugs ===

Mostly used as priority military or government cargo transports, tugs are full-fledged starships with limited armament suitable for its mission. However,they are capable of carrying massive 'pods', which are not necessarily all cargo holds. Available pods vary widely. However, combat-related pods such as commando pods, carrier pods and battle pods allow the tug to actively participate in important battles.

I've added all cargo-carrying tugs variants for scenario generation purposes. The tugs with no pods are set as "Heavy Cruisers" or "Light Cruisers", depending on their size. The tugs with cargo pods attached are set as "Special", type "R", hulltype "Freighter". These will remain present in the game in case someone feels it's useful enough to create scenarios with them. They're also going to appear under the D2 if this shiplist is used.

Be careful to check the Movement Cost of the tug you wish to play. Some tugs are slow and heavy, and will not move quickly nor maneuver well at all. These restrictions are per SFB rules, and seem accurate. The slowest battle-worthy tugs in the game are the Federation F-BTV and F-CVTC. Try the F-CVTC with a full complement of 24 fighters. You'll just love it despite the slow speed (16 max?).

Tugs with self-defense pallets have not been added to the game, to avoid clutter and make room in the shiplist.
NOTE: The exceptions, Hydran H-TUGsdp and H-TUG+sdp, have 8 gatling phasers (ph-G). That made them interesting ships to play. The SD Pallet added 4 ph-G 360, so I couldn't resist adding them once it was pointed out to me.

Some of the BattleTugs are vicious ships and have been rated as "Heavy Battlecruisers". In the many games I have played with this shiplist, this decision was well justified.

=== Casual PF Tenders ===

By adding a clamp mechanism to a tractor beam system, practically any ship could be adapted to carry PFs into battle.

I've added many casual carriers to the shiplist, mostly with the intent of maintaning the balance. More precisely, the Gorn and Romulans were seriously lacking in the Carrier department, so I've made some logical additions.

Note: I started off by adding any Casual PFTs with the mechlinks already drawn onto the SSDs.

* G-CCHF
* G-BCHF
* G-BBF
* R-SPJF
* R-KEF
* R-KCRF
* R-KVLF
* R-K10RF
* R-KCNF

Also, almost all large Lyran ships are considered to be capable of Full PFT duty. These ships, starting from the L-BCH to largest, will now have a "T" varient (for tender) capable of carrying a full load of 4 PFs. The original "F" designs with 2 PFs will remain available.

* L-BCHT
* L-DNT
* L-DNLT
* L-DNHT
* L-BBT

Oh.. and BTW..
I took the liberty of adding "F" PFT variants of the Lyran X1 and X2 ships.
Be warned. *EVIL LAUGH!!*

=== Battle Carriers ===

Already capable warships, the BattleCruisers and Heavy BattleCruisers are actually refittable as carriers.

To balance the BCV category, Romulans and Gorns also needed BCVs. A couple of SFB ships had to be modified from their original SSDs to fit the role.
Specifically:

* R-TH (ThunderHawk)
** Normally carries 8 fighters, 2 shuttles and 6 PFs. Fighters have been completely removed to match Romulan no-PF philosophy in SFC:OP. 4 shuttle boxes have been added, increasing the number to 6. The BPV of the ship has been adjusted to compensate for the other 4 missing shuttleboxes.
* G-BCS
** Normally carries 6 fighters, 2 shuttles and 6 PFs. All fighterbays have been converted to shuttlebays. (Gorns with 8 shuttlebays are not unseen in this game.)

Both of the above-mentioned ships have been reduced to 4 PFs like all the other PFTs in the game.

=== BattleShip Carriers ===

BattleShip Carriers are true monsters. These flagships were heavily modified to carry large number of fighters to supplement their already vast firepower.

More BBVs have been added to the game. Specifically, the "I-BBV", "F-BBV", and "Z-BBV" now join the "H-MNV", "K-B10V" and "K-B11V".

PF-based races, such as the Gorn, Romulans and Lyrans, now have CasualPFTs for their BB classes.

The TigerHeart don't have any Dreadnoughts or Battleships. Read go check the SFC:OP manual about this.

=== Fast Resupply Frigates ===

These frigates were designed mostly as prioritive cargo transports between industrial and production centers and front-line carrier groups. Their cargo holds were specially designed for carrying replacement fighters and pseudo-fighters, as well as lodging replacement crews. In a pinch, they were also capable of acting as carrier escorts.

These are lightly armed cargo frigates used as fast freighters for carriers. The supply fighters and parts necessary for these carriers and are strategically important. Tactically, they suck, but I added them to the game anyways.

=== Monitors ===

Monitors are usually sent to defend planets, or to establish a military presence in a remote sector until a properly defended outpost can be established. They are very slow yet very powerful ships with enough firepower to induce caution within any would-be invader.

Like the above brief description states, they're slow but strong. Attacking them feels like you're charging to meet a slow yet nasty brute which has long enough arms to punch you and keep you back. Playing one is as difficult: you're slow with a max speed of 14 within SFC. Your fantastic phaser arcs will defend you nicely, but if you're overwhelmed and outmaneuvered, you're dead.

Almost all Monitors are identical, for all the races that have them. Here's a rundown of their base systems:

* Power: 27 total
** 6 Warps total, 3 on each side.
** 3 Impulse Power
** 18 APRs
** 8 Batteries
* 36 shields, all around
* 2 Transporters
* 4 Tractors
* 0 Labs
* 6 Hull
* Up to 6 shuttles

Monitors may carry a pallet. There are 3 pallets available. All pallets cost 15 BPV, fighters/PFs not included:

* Support Pallet
** 6 cargo, 6 hull, 6 lab (very useful for shield regen)
* Carrier Pallet (if applicable)
** 2 cargo, 9 fighters (12 fighters * 2/3 ratio)
* PFT Pallet (if applicable)
** 2 cargo, 6 mechlink tractors, 4 PFs (6 PFs * 2/3 ratio)

I did not enter any SCS Pallets nor the equivalent Federation Heavy Carrier Pallet. Why? The SCS pallets mix fighters and PFs. The Fed CVA pallet is the quivalent pallet but I didn't want to give them an advantage.

Please notice that I've used the Fed merchant ship skin/model for these ships. The merchant ships roughly but accurately look right for the part: big hull, with little itty-bitty warps sticking out the sides. (Compared to SFB SSDs)

=== Additional PFs ===

==== Escort PFs ====

Other PF variants were also designed. Some were to carry hypothetical fighters into battle. Others were to lay minefields. There were to be even commando and cargo-carrying PFs. But as a design proving to be much more successful than expected, the escort PFs were useful additions to any fleet.

The escort or phaser PFs had less heavy weapons, but more phasers or Plasma-D racks specially placed for defensive purposes. These ended up being cheaper to manufacture than the other PFs.

PF Variants can be found in the module K rulebook. There are cargo, commando, minelaying and escort PFs and all are official. For the purpose of this shiplist, the escort PFs sound like they've got the right scope in mind.
Evidence shows that Taldren's way of calculating a PF's BPV seems to have been to put it into the game, but always letting the insertion program calculate the BPV for them, with a balance of -5 BPV, for all PFs. I've done the same for the added Lyran, Gorn and Romulan escort PFs.

Most of these PFs will never become "drone bait". When I showed strafer these ships as potential additions (from module K) and how I would do it, all he told me was "I approve".

==== Lyran PFL ====

The standard L-PFL has been added. It's just like a L-PF+, but with the transporter, t-bomb and couple of marines. I used PFLs from the other races as templates.

==== StarHawk PFs ====

Following the modular design, the Romulans also have a series of PFs called the StarHawk PFs.

==== Brigand Interceptors and Bucaneer PFs (TigerHeart) ====

Since the TigerHeart only have small ships, it's fair to increase the roster with other existing PFs the pirates would normally use. I gave these PFs weapons as per the Orion Pirate weapon option mount rules, and weapon availability due to cartel location.

The drone-carring variants are particularly effective. But since the PFs don't have their own drone control (and its passed on to the mother ships), I installed OAKDISK (and paid the BPV for it) on all PF-carrying TigerHeart ship.

Find out more about the additional PFs.

=== Additional Orion hulltypes and classes ===

Many orion ships are missing from the game. To make things interesting, I took special interest to the Salvage cruisers and their variants. You see, the SAL variants include PFTs and CVLs which the Orion dearly need in light cruiser classes.

Also, I took the liberty to review all of the current pirate entries and design additional variants based on proper SFB rules: 70% of option mounts must take weapons/systems from local empire, 20% are from the "Operation Zone", and 10% may come from anywhere. I would like to think I just made things a little bit more interesting. Look for pirate ships with variants "0".
In all, hundreds of the additions may be attributed to the pirates.

=== Pirate fighters ===

In SFB, the pirates don't have their own fighters. They buy from their local empire's "black market" and equip themselves with such.

... however...

In SFC, they all have their own fighters, except for TigerHeart of course.

I took the liberty to copy fighters from the normal races to the pirate races of that region. That means that additionally to Taldren's design, they'll be able to use other fighters from their local region too. ie:

* Orion Pirates --> Federation fighters
* Korgath --> Klingon fighters
* Camboro --> Mirak fighters
* BeastRaiders --> Hydran
* Wyldefire --> ISC

Also, .. a new set of entries of fighters have been added to help some compatibility issues: "Neutral" race fighters. Normally, "Neutral" units are used in Taldren-written mission scripts for some specific tasks.

Namely:

* N-SH (Shuttles)
* N-PE
* N-IE
* N-HE
* N-AE
* N-PM
* N-IM
* N-HM
* N-AM
* N-PL
* N-IL
* N-HL
* N-AL

Note: the Syndicate (Gorn) and Prime (Romulan) cartels don't get local fighters. There are no local fighters to use as these empires have PFs.

==== Additional WYN hulltypes and classes ====

I went through the SFB material here and stuffed the shiplist with as many WYN ships I deemed appropriate. I put in the Auxiliary conversions, as well as the other donated or captured ships found.

Please note:

I didn't put in any Orions because they would inherit engine-doubling if I put the ship under any Pirate race. The WYN do not have engine doubling. I didn't bother with the WYN fish ships. At that point, you may as well give them their own race.

Here's a list of the WYN Ships in the OP+ shiplist, thanks to yet another perl handy-dandy script I wrote for myself:

K-WG2 - FF
K-WG2+ - FF
K-WE4 - FF
K-WE4+ - FF
L-WPBC - FF
L-WPBCF - FF
L-WAXPFS - FF
L-WLDD - CL
L-WLDD+ - CL
L-WLDDP - CL
L-WLDDR - CL
L-WLDDF - CL
L-WPBB - CL
L-WPBBF - CL
L-WAXBS1 - CA
L-WAXBS2 - CA
L-WAXBS3 - CA
Z-WAXC1 - FF
Z-WAXC2 - FF
Z-WAXC3 - FF
Z-WAXCC - FF
Z-WAXCC+ - FF
Z-WAXCV1 - FF
Z-WAXCV2 - FF
Z-WAXCV3 - FF
Z-WZFF - FF (See note: *)
Z-WZFF+ - FF (See note: *)
Z-WZDF - FF (See note: *)
Z-WAXCX1 - FF
Z-WAXCX2 - FF
Z-WAXCX3 - FF
Z-WFZX - FF
Z-WDW - CL (See note: *)
Z-WAXBC1 - CA
Z-WAXBC2 - CA
Z-WAXBC3 - CA
Z-WAXB1+ - CA
Z-WAXB2+ - CA
Z-WAXB3+ - CA
Z-WAXBV1 - CA
Z-WAXBV2 - CA
Z-WAXBV3 - CA
Z-WAXCVA - CA
Z-WACVA+ - CA
Z-WAXDN1 - DN
Z-WAXDN2 - DN

NOTE: * Not all above ships are new. Some were already in the OP 25410 shiplist. No WYN ships previously in shiplist have been removed. All are entered with the first letter "W", with HullClass "SPECIAL".

=== Adjustments to existing ships ===

==== The H-IC (and H-IC+) has 40 fighters in SFB. ====

Taldren's 2/3 fighters rule was broken for this ship, equipping it with only 16 fighters. Strafer wanted this to reflect the real power this ship is under SFB, so was modified to carry 24 fighters in SFC:OP, the 2/3 limit. The BPV was adjusted, don't worry.

==== The earlier versions of the R-KVL were added ====

They're listed as the R-WVL and the VUL+. These are equivalent to the eras the R-WE and the R-WB+ appeared. Try them. They're fun. Their BPV was increased to compensate for "cheese" factor and abuse, much like the R-KVL in the 2525 patch. We based our calculations from the latest SFB material containing the Vulture class: Y1, Early Years.

==== weapons moved to visible mountpoints ====

Some mountpoint manipulations have been done to allow use of previously 'hidden' weapons. With EagleEye Software's ShipEdit editor, it was a simple matter of browsing through the entire list, and move things around a bit.
ie: merge weapons of same type and arc here.. shuffle mountpoints there..

Also, some ships will appear with X-Ship UIs to allow all weapons to be useable/targettable.
ie: F-BTV

Note that for PFs, the editor was useless for viewing mountpoint locations. I had to figure out where the mountpoints were on my own. Please note that any phaser mounted on a HeavyWeapon point (mounts 1-10) will NOT charge the phaser capacitor. Let me share that information now:

http://klingon.pet.dhs.org/OP_plusrefit/editor_lyran_pf.jpg
http://klingon.pet.dhs.org/OP_plusrefit/editor_romulan_pf.jpg
http://klingon.pet.dhs.org/OP_plusrefit/editor_gorn_pf.jpg

==== The Federation F-DN is now considered an Early Dreadnought ====

Its year of availability and retirement have been adjusted to 2248-2275. The F-DN+ comes out in 2272.

==== X1 and X2 dates have been changed ====

* Existing X1 ships' intruduction dates joined the other added X1 ships at around 2292-2297.
* X2 ships have been 'staggered' to emulate prototyping and introduction of the various ship classes. It didn't make sense to have all X2 ships appear at once at 2300.

==== shipnames, refits and base refitclass fixes ====

Some shipnames, refits and base refitclass were entered incorrectly in the shiplist.txt file. These changes are easy to spot with the compare.txt file. This is just a cosmetic change to allow proper strings.txt and shipnames.txt coverage.

==== Basic pirate fighters have been changed from PM to PE fighters ====

This will allow "early" carriers to carry "early" fighters.
ie: the SAL carrier variants "CVL" and "LVS".

==== Many ships from module R7 have been entered incorrectly. ====

They've all been revised (or added at all for that matter). R7 is called "Dreadnoughts at War" and covers the various yet unmentionned DNs and variants for the various races.
For more information, please visit the sections about Light Dreadnoughts, Heavy Dreadnoughts and Early Dreadnoughts.

==== TigerHeart's "CV" is a DN ====

TigerHeart's "CV" class has been moved to the DN class despite the fact that it's not a DN. Why? They don't *HAVE* a DN and that caused some problems for some multiplayer games on Gamespy and Local LAN.

==== Some carriers had insufficient or no deckcrews. ====
Fixed.

==== Some drone-equipped ships had insufficient drone control ====
Fixed.

==== B10 fixes ====

The B10 series weren't entered properly. The KBB UI did not have sufficient weapons slots to cover the entire ship. However, the KDN class does work fine for these ships and was adopted as the B10 variant UI. The Romulan K10R variants seem to be fine.

=== Shiplist Limits ===
Taldren has been kind enough to raise the limit of ships to 128. That's 128 ships PER hull class PER race. Believe it or not, I had well filled the previous limit of 64.

ie: There can be 128 Lyran frigates, 128 Lyran Light Cruisers, 128 Lyran Heavy Cruisers, etc.

SFC:OP Plus Refit

2019-09-13T23:08:57Z

Firesoul:

A mod for StarFleet Command : Orion Pirates patch version 2552

* [[OP+ Introduction]]
* [[OP+ Contents and Changes]]
* [[OP+ Statistics]]
* [[OP+ Conversion Rules]]
** conversion rules for ships, from SFB to SFC.
* [[OP+ and Test-Driven Development]]
* [[OP+ about the ship models]]
* [[OP+ FAQ]]
* [[OP+ Fair Use]]

=== Downloads ===

==== OP+ 4.1.1 ====
Released: 2011-08-07

Note: should be compatible with OP+ 4.1, despite in-game warnings. See [[OP+ Contents and Changes]] for differences.

* [https://klingon.lostexiles.net/OP_plusrefit/opplus_411_models_20110724175017.exe opplus_411_models_20110724175017.exe]
** size: 77mb

The installer above will require around 760mb for installation. This is the final release of OP+ 4.1.1.

* Installation Instructions: [https://klingon.lostexiles.net/OP_plusrefit/readme.txt readme.txt]
* Disclaimer: [http://klingon.lostexiles.net/OP_plusrefit/readme.txt readme.txt]

----

==== OP+ 4.1 ====
Released: 2011-06-10 (installer-only update, fully compatible with 2011-06-05 release)

* [https://klingon.lostexiles.net/OP_plusrefit/opplus_41_models_20110610085609.exe opplus_41_models_20110610085609.exe]
** size: 77mb

The installer above will require around 760mb for installation. This is the final release of OP+ 4.1. It's a repackaged release candidate 5 with an updated license.

* Installation Instructions: [https://klingon.lostexiles.net/OP_plusrefit/readme.txt readme.txt]
* Disclaimer: [http://klingon.lostexiles.net/OP_plusrefit/readme.txt readme.txt]

----

==== OP+ 4.0 ====
Released: 2005-01-01

* [https://klingon.lostexiles.net/OP_plusrefit/opplus_40_models.exe opplus_40_models.exe]
** includes models
** size: 63MB
* [https://klingon.lostexiles.net/OP_plusrefit/opplus_40_no_models.exe opplus_40_no_models.exe]
** size: 275KB

Mirror at ftp.xenocorp.net:
* [ftp://ftp.xenocorp.net/game_files/Star_Trek/starfleet_command/Starfleet_Command_OP/shiplists/opplus_40_models.exe opplus_40_models.exe]
* [ftp://ftp.xenocorp.net/game_files/Star_Trek/starfleet_command/Starfleet_Command_OP/shiplists/opplus_40_no_models.exe opplus_40_no_models.exe]

The "with models" installer above will require around 700mb for installation. The no models installer should require around 500mb.

* Installation Instructions: [https://klingon.lostexiles.net/OP_plusrefit/readme.txt readme.txt]
* Disclaimer: [http://klingon.lostexiles.net/OP_plusrefit/readme.txt readme.txt]

----

==== Coopace 4.0 ====

This shiplist works '''''GREAT!''''' with the CoopAce script version 4.0.

* [https://klingon.lostexiles.net/sources_and_utils/coop-ace-4.0.exe CoopAce 4.0 installer]

See: [[Co-op Ace for SFC:EAW and SFC:OP]]

==== Extra Reading Material ====

Available official storyline of the [http://www.starfleetgames.com/sfb/sfin/general_war.htm General War], straight from ADB, at [http://www.starfleetgames.com/ StarFleetGames.com].

OP+ about the ship models

2019-09-13T23:06:52Z

Firesoul: /* View FireSoul's Model Collection */

=== Methods of model addition ===

I wanted to include a set of ship models to the project. I couldn't reliably do that until I started using the NSIS installer kit which allows me to script some actions, such as file install, directory copying, and file attribute manipulations. Thanks NullSoft. :)

OP+ 4.1 includes some 343 Models installed from the 3 different methods listed below. I invite you to download OP 4.1 and try it out for yourself. Feel free to replace any models you want. As long you don't change the other files, you'll be completely compatible to other OP+ 4.1 players.

Note: The installer will require over 750mb of space.

==== Model Replacement ====

This project's view is not to replace all the models that are already in the SFC:OP game. Instead, it is designed to enhance it and improve the gameplay experience. Many of the standard models are still being referenced by the shiplist.
Example: The standard FCA model is still used to represent the + refit u applied to Federation cruisers. Pre + refit ships are considered to be of TOS style, and have models to properly reflect that technology.

Below: a F-CAR+ (left) and a TOS-style F-CA (right)
https://klingon.lostexiles.net/OP_plusrefit/screenshots/op+30_FECA_and_FCA.JPG

==== Model Separation====

Sometimes, different models altogether were used. The current models with the stock game can be unflexible when trying to represent the variants that exist for certain ship classes.
Example: The Taldren KCL model is perfect if there was only D5 variants to worry about. Unfortunately, there's also the D5W variants and the LTT Tug variant (D5H).

Below: a K-D5W (left), a K-D5 (center) and a K-D5H (right) ..
https://klingon.lostexiles.net/OP_plusrefit/screenshots/op+30_D5_D5W_D5Hc1_smaller.jpg

Example: The Federation Dreadnought Line-Up
Below: a F-DN+ (left), a F-DN (center) and a F-DNG (right)
https://klingon.lostexiles.net/OP_plusrefit/screenshots/op+31_DN+_DN_DNG.JPG

==== Model Resizing ====

The 3rd method I've used to include new models.. is not by including models at all. By specifying a different size in Assets/Models/model.siz, and by copying the desired model from the Taldren stock, new ship models are generated.
Example: I didn't find Romulan purchased Klingon ships' models I liked better than Taldren's own. By copying the RCA stock model into RKR and RKCR models, I can control the sizes of the 2 new ones appropriately.

Below: a R-KR (left), a R-K7R (center) and a R-KCR (right) ..
https://klingon.lostexiles.net/OP_plusrefit/screenshots/op+30_KR_K7R_and_KRC.JPG

=== Other model tweaks ===

==== LODs (Levels of Detail) ====

In OP+, all models have been updated to guarantee having levels of details to reduce CPU load while playing the game. The idea is that if the ship is too far in gameplay, it can't be looked at properly anyhow.. .. so why waste CPU cycles? Some ships have well over 3000 polys on their primary LOD.

Example:
* LOD 1: 2316 polys
https://klingon.lostexiles.net/OP_plusrefit/kd5_lod1.JPG

* LOD 2: 1215 polys
https://klingon.lostexiles.net/OP_plusrefit/kd5_lod2.JPG

* LOD 3: 730 polys
https://klingon.lostexiles.net/OP_plusrefit/kd5_lod3.JPG

==== Break MODs ====

All ships should now have appropriate break models. They should all be detailed enough so that each piece doesn't have a missing portion where you can see through the entire piece (because there is no poly facing you).

Example, a piece from a F-FF:
https://klingon.lostexiles.net/OP_plusrefit/burke-break.jpg

=== View FireSoul's Model Collection ===

See: [https://klingon.lostexiles.net/models/ https://klingon.lostexiles.net/models/]

OP+ about the ship models

2019-09-13T23:06:37Z

Firesoul: /* Break MODs */

=== Methods of model addition ===

I wanted to include a set of ship models to the project. I couldn't reliably do that until I started using the NSIS installer kit which allows me to script some actions, such as file install, directory copying, and file attribute manipulations. Thanks NullSoft. :)

OP+ 4.1 includes some 343 Models installed from the 3 different methods listed below. I invite you to download OP 4.1 and try it out for yourself. Feel free to replace any models you want. As long you don't change the other files, you'll be completely compatible to other OP+ 4.1 players.

Note: The installer will require over 750mb of space.

==== Model Replacement ====

This project's view is not to replace all the models that are already in the SFC:OP game. Instead, it is designed to enhance it and improve the gameplay experience. Many of the standard models are still being referenced by the shiplist.
Example: The standard FCA model is still used to represent the + refit u applied to Federation cruisers. Pre + refit ships are considered to be of TOS style, and have models to properly reflect that technology.

Below: a F-CAR+ (left) and a TOS-style F-CA (right)
https://klingon.lostexiles.net/OP_plusrefit/screenshots/op+30_FECA_and_FCA.JPG

==== Model Separation====

Sometimes, different models altogether were used. The current models with the stock game can be unflexible when trying to represent the variants that exist for certain ship classes.
Example: The Taldren KCL model is perfect if there was only D5 variants to worry about. Unfortunately, there's also the D5W variants and the LTT Tug variant (D5H).

Below: a K-D5W (left), a K-D5 (center) and a K-D5H (right) ..
https://klingon.lostexiles.net/OP_plusrefit/screenshots/op+30_D5_D5W_D5Hc1_smaller.jpg

Example: The Federation Dreadnought Line-Up
Below: a F-DN+ (left), a F-DN (center) and a F-DNG (right)
https://klingon.lostexiles.net/OP_plusrefit/screenshots/op+31_DN+_DN_DNG.JPG

==== Model Resizing ====

The 3rd method I've used to include new models.. is not by including models at all. By specifying a different size in Assets/Models/model.siz, and by copying the desired model from the Taldren stock, new ship models are generated.
Example: I didn't find Romulan purchased Klingon ships' models I liked better than Taldren's own. By copying the RCA stock model into RKR and RKCR models, I can control the sizes of the 2 new ones appropriately.

Below: a R-KR (left), a R-K7R (center) and a R-KCR (right) ..
https://klingon.lostexiles.net/OP_plusrefit/screenshots/op+30_KR_K7R_and_KRC.JPG

=== Other model tweaks ===

==== LODs (Levels of Detail) ====

In OP+, all models have been updated to guarantee having levels of details to reduce CPU load while playing the game. The idea is that if the ship is too far in gameplay, it can't be looked at properly anyhow.. .. so why waste CPU cycles? Some ships have well over 3000 polys on their primary LOD.

Example:
* LOD 1: 2316 polys
https://klingon.lostexiles.net/OP_plusrefit/kd5_lod1.JPG

* LOD 2: 1215 polys
https://klingon.lostexiles.net/OP_plusrefit/kd5_lod2.JPG

* LOD 3: 730 polys
https://klingon.lostexiles.net/OP_plusrefit/kd5_lod3.JPG

==== Break MODs ====

All ships should now have appropriate break models. They should all be detailed enough so that each piece doesn't have a missing portion where you can see through the entire piece (because there is no poly facing you).

Example, a piece from a F-FF:
https://klingon.lostexiles.net/OP_plusrefit/burke-break.jpg

=== View FireSoul's Model Collection ===

See: [http://klingon.pet.dhs.org/models/ http://klingon.pet.dhs.org/models/]

OP+ about the ship models

2019-09-13T23:06:27Z

Firesoul: /* Model Resizing */

=== Methods of model addition ===

I wanted to include a set of ship models to the project. I couldn't reliably do that until I started using the NSIS installer kit which allows me to script some actions, such as file install, directory copying, and file attribute manipulations. Thanks NullSoft. :)

OP+ 4.1 includes some 343 Models installed from the 3 different methods listed below. I invite you to download OP 4.1 and try it out for yourself. Feel free to replace any models you want. As long you don't change the other files, you'll be completely compatible to other OP+ 4.1 players.

Note: The installer will require over 750mb of space.

==== Model Replacement ====

This project's view is not to replace all the models that are already in the SFC:OP game. Instead, it is designed to enhance it and improve the gameplay experience. Many of the standard models are still being referenced by the shiplist.
Example: The standard FCA model is still used to represent the + refit u applied to Federation cruisers. Pre + refit ships are considered to be of TOS style, and have models to properly reflect that technology.

Below: a F-CAR+ (left) and a TOS-style F-CA (right)
https://klingon.lostexiles.net/OP_plusrefit/screenshots/op+30_FECA_and_FCA.JPG

==== Model Separation====

Sometimes, different models altogether were used. The current models with the stock game can be unflexible when trying to represent the variants that exist for certain ship classes.
Example: The Taldren KCL model is perfect if there was only D5 variants to worry about. Unfortunately, there's also the D5W variants and the LTT Tug variant (D5H).

Below: a K-D5W (left), a K-D5 (center) and a K-D5H (right) ..
https://klingon.lostexiles.net/OP_plusrefit/screenshots/op+30_D5_D5W_D5Hc1_smaller.jpg

Example: The Federation Dreadnought Line-Up
Below: a F-DN+ (left), a F-DN (center) and a F-DNG (right)
https://klingon.lostexiles.net/OP_plusrefit/screenshots/op+31_DN+_DN_DNG.JPG

==== Model Resizing ====

The 3rd method I've used to include new models.. is not by including models at all. By specifying a different size in Assets/Models/model.siz, and by copying the desired model from the Taldren stock, new ship models are generated.
Example: I didn't find Romulan purchased Klingon ships' models I liked better than Taldren's own. By copying the RCA stock model into RKR and RKCR models, I can control the sizes of the 2 new ones appropriately.

Below: a R-KR (left), a R-K7R (center) and a R-KCR (right) ..
https://klingon.lostexiles.net/OP_plusrefit/screenshots/op+30_KR_K7R_and_KRC.JPG

=== Other model tweaks ===

==== LODs (Levels of Detail) ====

In OP+, all models have been updated to guarantee having levels of details to reduce CPU load while playing the game. The idea is that if the ship is too far in gameplay, it can't be looked at properly anyhow.. .. so why waste CPU cycles? Some ships have well over 3000 polys on their primary LOD.

Example:
* LOD 1: 2316 polys
https://klingon.lostexiles.net/OP_plusrefit/kd5_lod1.JPG

* LOD 2: 1215 polys
https://klingon.lostexiles.net/OP_plusrefit/kd5_lod2.JPG

* LOD 3: 730 polys
https://klingon.lostexiles.net/OP_plusrefit/kd5_lod3.JPG

==== Break MODs ====

All ships should now have appropriate break models. They should all be detailed enough so that each piece doesn't have a missing portion where you can see through the entire piece (because there is no poly facing you).

Example, a piece from a F-FF:
http://klingon.pet.dhs.org/OP_plusrefit/burke-break.jpg

=== View FireSoul's Model Collection ===

See: [http://klingon.pet.dhs.org/models/ http://klingon.pet.dhs.org/models/]

OP+ about the ship models

2019-09-13T23:06:18Z

Firesoul: /* Model Separation */

=== Methods of model addition ===

I wanted to include a set of ship models to the project. I couldn't reliably do that until I started using the NSIS installer kit which allows me to script some actions, such as file install, directory copying, and file attribute manipulations. Thanks NullSoft. :)

OP+ 4.1 includes some 343 Models installed from the 3 different methods listed below. I invite you to download OP 4.1 and try it out for yourself. Feel free to replace any models you want. As long you don't change the other files, you'll be completely compatible to other OP+ 4.1 players.

Note: The installer will require over 750mb of space.

==== Model Replacement ====

This project's view is not to replace all the models that are already in the SFC:OP game. Instead, it is designed to enhance it and improve the gameplay experience. Many of the standard models are still being referenced by the shiplist.
Example: The standard FCA model is still used to represent the + refit u applied to Federation cruisers. Pre + refit ships are considered to be of TOS style, and have models to properly reflect that technology.

Below: a F-CAR+ (left) and a TOS-style F-CA (right)
https://klingon.lostexiles.net/OP_plusrefit/screenshots/op+30_FECA_and_FCA.JPG

==== Model Separation====

Sometimes, different models altogether were used. The current models with the stock game can be unflexible when trying to represent the variants that exist for certain ship classes.
Example: The Taldren KCL model is perfect if there was only D5 variants to worry about. Unfortunately, there's also the D5W variants and the LTT Tug variant (D5H).

Below: a K-D5W (left), a K-D5 (center) and a K-D5H (right) ..
https://klingon.lostexiles.net/OP_plusrefit/screenshots/op+30_D5_D5W_D5Hc1_smaller.jpg

Example: The Federation Dreadnought Line-Up
Below: a F-DN+ (left), a F-DN (center) and a F-DNG (right)
https://klingon.lostexiles.net/OP_plusrefit/screenshots/op+31_DN+_DN_DNG.JPG

==== Model Resizing ====

The 3rd method I've used to include new models.. is not by including models at all. By specifying a different size in Assets/Models/model.siz, and by copying the desired model from the Taldren stock, new ship models are generated.
Example: I didn't find Romulan purchased Klingon ships' models I liked better than Taldren's own. By copying the RCA stock model into RKR and RKCR models, I can control the sizes of the 2 new ones appropriately.

Below: a R-KR (left), a R-K7R (center) and a R-KCR (right) ..
http://klingon.pet.dhs.org/OP_plusrefit/screenshots/op+30_KR_K7R_and_KRC.JPG

=== Other model tweaks ===

==== LODs (Levels of Detail) ====

In OP+, all models have been updated to guarantee having levels of details to reduce CPU load while playing the game. The idea is that if the ship is too far in gameplay, it can't be looked at properly anyhow.. .. so why waste CPU cycles? Some ships have well over 3000 polys on their primary LOD.

Example:
* LOD 1: 2316 polys
https://klingon.lostexiles.net/OP_plusrefit/kd5_lod1.JPG

* LOD 2: 1215 polys
https://klingon.lostexiles.net/OP_plusrefit/kd5_lod2.JPG

* LOD 3: 730 polys
https://klingon.lostexiles.net/OP_plusrefit/kd5_lod3.JPG

==== Break MODs ====

All ships should now have appropriate break models. They should all be detailed enough so that each piece doesn't have a missing portion where you can see through the entire piece (because there is no poly facing you).

Example, a piece from a F-FF:
http://klingon.pet.dhs.org/OP_plusrefit/burke-break.jpg

=== View FireSoul's Model Collection ===

See: [http://klingon.pet.dhs.org/models/ http://klingon.pet.dhs.org/models/]

OP+ about the ship models

2019-09-13T23:06:06Z

Firesoul: /* Model Replacement */

=== Methods of model addition ===

I wanted to include a set of ship models to the project. I couldn't reliably do that until I started using the NSIS installer kit which allows me to script some actions, such as file install, directory copying, and file attribute manipulations. Thanks NullSoft. :)

OP+ 4.1 includes some 343 Models installed from the 3 different methods listed below. I invite you to download OP 4.1 and try it out for yourself. Feel free to replace any models you want. As long you don't change the other files, you'll be completely compatible to other OP+ 4.1 players.

Note: The installer will require over 750mb of space.

==== Model Replacement ====

This project's view is not to replace all the models that are already in the SFC:OP game. Instead, it is designed to enhance it and improve the gameplay experience. Many of the standard models are still being referenced by the shiplist.
Example: The standard FCA model is still used to represent the + refit u applied to Federation cruisers. Pre + refit ships are considered to be of TOS style, and have models to properly reflect that technology.

Below: a F-CAR+ (left) and a TOS-style F-CA (right)
https://klingon.lostexiles.net/OP_plusrefit/screenshots/op+30_FECA_and_FCA.JPG

==== Model Separation====

Sometimes, different models altogether were used. The current models with the stock game can be unflexible when trying to represent the variants that exist for certain ship classes.
Example: The Taldren KCL model is perfect if there was only D5 variants to worry about. Unfortunately, there's also the D5W variants and the LTT Tug variant (D5H).

Below: a K-D5W (left), a K-D5 (center) and a K-D5H (right) ..
http://klingon.pet.dhs.org/OP_plusrefit/screenshots/op+30_D5_D5W_D5Hc1_smaller.jpg

Example: The Federation Dreadnought Line-Up
Below: a F-DN+ (left), a F-DN (center) and a F-DNG (right)
http://klingon.pet.dhs.org/OP_plusrefit/screenshots/op+31_DN+_DN_DNG.JPG

==== Model Resizing ====

The 3rd method I've used to include new models.. is not by including models at all. By specifying a different size in Assets/Models/model.siz, and by copying the desired model from the Taldren stock, new ship models are generated.
Example: I didn't find Romulan purchased Klingon ships' models I liked better than Taldren's own. By copying the RCA stock model into RKR and RKCR models, I can control the sizes of the 2 new ones appropriately.

Below: a R-KR (left), a R-K7R (center) and a R-KCR (right) ..
http://klingon.pet.dhs.org/OP_plusrefit/screenshots/op+30_KR_K7R_and_KRC.JPG

=== Other model tweaks ===

==== LODs (Levels of Detail) ====

In OP+, all models have been updated to guarantee having levels of details to reduce CPU load while playing the game. The idea is that if the ship is too far in gameplay, it can't be looked at properly anyhow.. .. so why waste CPU cycles? Some ships have well over 3000 polys on their primary LOD.

Example:
* LOD 1: 2316 polys
https://klingon.lostexiles.net/OP_plusrefit/kd5_lod1.JPG

* LOD 2: 1215 polys
https://klingon.lostexiles.net/OP_plusrefit/kd5_lod2.JPG

* LOD 3: 730 polys
https://klingon.lostexiles.net/OP_plusrefit/kd5_lod3.JPG

==== Break MODs ====

All ships should now have appropriate break models. They should all be detailed enough so that each piece doesn't have a missing portion where you can see through the entire piece (because there is no poly facing you).

Example, a piece from a F-FF:
http://klingon.pet.dhs.org/OP_plusrefit/burke-break.jpg

=== View FireSoul's Model Collection ===

See: [http://klingon.pet.dhs.org/models/ http://klingon.pet.dhs.org/models/]

OP+ about the ship models

2019-09-13T23:05:52Z

Firesoul: /* LODs (Levels of Detail) */

=== Methods of model addition ===

I wanted to include a set of ship models to the project. I couldn't reliably do that until I started using the NSIS installer kit which allows me to script some actions, such as file install, directory copying, and file attribute manipulations. Thanks NullSoft. :)

OP+ 4.1 includes some 343 Models installed from the 3 different methods listed below. I invite you to download OP 4.1 and try it out for yourself. Feel free to replace any models you want. As long you don't change the other files, you'll be completely compatible to other OP+ 4.1 players.

Note: The installer will require over 750mb of space.

==== Model Replacement ====

This project's view is not to replace all the models that are already in the SFC:OP game. Instead, it is designed to enhance it and improve the gameplay experience. Many of the standard models are still being referenced by the shiplist.
Example: The standard FCA model is still used to represent the + refit u applied to Federation cruisers. Pre + refit ships are considered to be of TOS style, and have models to properly reflect that technology.

Below: a F-CAR+ (left) and a TOS-style F-CA (right)
http://klingon.pet.dhs.org/OP_plusrefit/screenshots/op+30_FECA_and_FCA.JPG

==== Model Separation====

Sometimes, different models altogether were used. The current models with the stock game can be unflexible when trying to represent the variants that exist for certain ship classes.
Example: The Taldren KCL model is perfect if there was only D5 variants to worry about. Unfortunately, there's also the D5W variants and the LTT Tug variant (D5H).

Below: a K-D5W (left), a K-D5 (center) and a K-D5H (right) ..
http://klingon.pet.dhs.org/OP_plusrefit/screenshots/op+30_D5_D5W_D5Hc1_smaller.jpg

Example: The Federation Dreadnought Line-Up
Below: a F-DN+ (left), a F-DN (center) and a F-DNG (right)
http://klingon.pet.dhs.org/OP_plusrefit/screenshots/op+31_DN+_DN_DNG.JPG

==== Model Resizing ====

The 3rd method I've used to include new models.. is not by including models at all. By specifying a different size in Assets/Models/model.siz, and by copying the desired model from the Taldren stock, new ship models are generated.
Example: I didn't find Romulan purchased Klingon ships' models I liked better than Taldren's own. By copying the RCA stock model into RKR and RKCR models, I can control the sizes of the 2 new ones appropriately.

Below: a R-KR (left), a R-K7R (center) and a R-KCR (right) ..
http://klingon.pet.dhs.org/OP_plusrefit/screenshots/op+30_KR_K7R_and_KRC.JPG

=== Other model tweaks ===

==== LODs (Levels of Detail) ====

In OP+, all models have been updated to guarantee having levels of details to reduce CPU load while playing the game. The idea is that if the ship is too far in gameplay, it can't be looked at properly anyhow.. .. so why waste CPU cycles? Some ships have well over 3000 polys on their primary LOD.

Example:
* LOD 1: 2316 polys
https://klingon.lostexiles.net/OP_plusrefit/kd5_lod1.JPG

* LOD 2: 1215 polys
https://klingon.lostexiles.net/OP_plusrefit/kd5_lod2.JPG

* LOD 3: 730 polys
https://klingon.lostexiles.net/OP_plusrefit/kd5_lod3.JPG

==== Break MODs ====

All ships should now have appropriate break models. They should all be detailed enough so that each piece doesn't have a missing portion where you can see through the entire piece (because there is no poly facing you).

Example, a piece from a F-FF:
http://klingon.pet.dhs.org/OP_plusrefit/burke-break.jpg

=== View FireSoul's Model Collection ===

See: [http://klingon.pet.dhs.org/models/ http://klingon.pet.dhs.org/models/]

FireSoul's SFC:OP BootStrap list

2017-07-05T19:23:33Z

Firesoul:

So you want to know how I set up SFC:OP? Ok!

== Update your DirectX ==

Make sure you have the right DirectX support on your machine. The game itself was shipped with DirectX 8 installables. DO NOT USE THOSE, THEY ARE ANCIENT. If you're on Windows XP or older, use DirectX 9.0c.

That said, newer Windows was NOT shipped with DirectX support for ''older'' games. You'll need to run an updater from MicroSoft to do so. This installer/updater will examine your system's DirectX libraries, both old and new, and make sure you have all of them.
 See: http://www.microsoft.com/en-us/download/details.aspx?id=35

== Install SFC:OP ==

* Find your CD.
* Find your CD-Key.
* Install.

== Patch to SFC:OP 2.5.5.2 ==

* Download the patch.
** [http://klingon.lostexiles.net/sources_and_utils/patches/SFCOP_Patch_2500-2552.exe SFCOP_Patch_2500-2552.exe]
* Install the patch.

What, you don't have 2.5.0.0 but something else? See here: [[All SFC Patches and ServerKits]]

== Run the game to type the CD-Key ==

* Make sure you have your CD-Key on paper or something you can read from
** copy-paste won't work here
* just start it up, and type in your Key.
* exit the game when you're done.

== Install Latest OP+ ==

See: [[SFC:OP Plus Refit]]

* Get the latest OP+
** .. or whatever people are playing. I suggest the latest.
* Install it.

== Set up your preferences with EzINI ==

* get [http://klingon.lostexiles.net/sources_and_utils/EzINI.exe EzINI]
* run EzINI
* Select Orion Pirates (if necessary)
* set up your:
** graphics resolution
** show damage
** sound settings
** multiplayer game player name
** default multiplayer game name
** default difficulty level
** etc etc etc

=== My suggestions for EzINI settings===

* Video
** Resolution: 1024 x 768
* Audio
** Music Volume --- OFF
*** That's completely optional. You can leave it on if you want.
** Max Channels: 64 (max)
** Crew Sounds: Maximum
* Multiplayer
** Set up your Default Multiplayer Player Name
** Set up your Game Name
** OPTIONAL: click on Multiplayer Hidden Race
** OPTIONAL: click on Multiplayer Hidden BPV
* Misc
** Difficulty: Admiral
** turn ON Volley Information

== Install Co-Op Ace ==

See: [[Co-op Ace for SFC:EAW and SFC:OP]]

* Get the latest coopace
** Currently [http://klingon.lostexiles.net/sources_and_utils/coop-ace-4.0.exe Coopace 4.0]
* install it.

== Customize Co-Op Ace==

* run the Coop-Ace Customizer from your start menu
** Set the Difficulty to around 1.5
*** or whatever you prefer. I got 1.7 right now
** Set the AI Intelligence to Admiral
** Races: single
** uncheck all the pirates
*** up to you, but remember, pirates are weaker
** Turn ON 'Force selection of ships created in current era'
*** This will improve the gaming experience, especially since you've installer OP+
** Turn ON 'Use Enhanced Shiplist API Settings'

== Fests+ ==

See: [[Fests+ for SFC:OP]]

* download the [http://klingon.lostexiles.net/fests+/Fests+_11.exe Fests+] installer
* install it
* download the extra mission: [http://klingon.lostexiles.net/fests+/Mul_Battlefest+Intense.scr Battlefest+ Intense]
* install it
** Find your SFC install directory
** Hint! May be: ''C:\Program Files (x86)\Taldren Software Inc\Starfleet Command Orion Pirates''
** Go into Assets\Scripts\
** copy Mul_Battlefest+Intense.scr there

== Missions Refit pack ==

See: [[http://klingon.lostexiles.net/mediawiki/index.php?title=SFC:OP_Missions_Refit SFC:OP Missions Refit]]

* download the [http://klingon.lostexiles.net/Missions_Refit/SFCOP_MissionsRefit_15_20121022222638.exe SFCOP_MissionsRefit_15_20121022222638.exe] installer
* install it

== Set up a key to launch all the fighters ==

* Launch the game
* Click on the 'Hot Keys' Button
** never BEEN here, huh?!
* click on 'Weapons'
* put in a ket for Launch Fighters.
** I tend to use 'L' for it.
*** 'L' is usually the Defense panel shortcut, which I never use via HotKey.
* exit the game to make sure your settings change are saved

If you screwed up, no problem! Go pick up a fresh copy of [http://klingon.lostexiles.net/sources_and_utils/orig/op/25410/bindings.ini bindings.ini] from [[SFC-related missions, sources, patches and misc utilities]].

Note, 2015-08-08: changing bindings didn't stick for me on my Windows 7 machine. :-/ I had to edit the file manually with notepad. To do '''that''', I needed to grant myself access to the files.

for example:
http://klingon.lostexiles.net/screenshots/20150808_win7_grant_yourself_full_access.png

Then go edit the file directly with notepad. It's going to be in under your SFC game's install directory, as Assets\Specs\bindings.ini

The changes:
* "LaunchFighters= " to "LaunchFighters=L"
* "Defense=L" to "Defense= "
** That's: Defense=<space>

== Dynaverse 2 Directory Server Updater ==

The Dynaverse 2 Server list updater is optional: I don't know if there still are D2 servers for SFC:OP out there, but in case there are, you can use this:

* [http://www.dynaverse.net/downloads.php?id=56&game=SFC2%20OP#download D2 Directory Server Updater]
* Run it.

== Set up your FireWall(s) to play online ==

=== Gaming host's firewall (AKA Windows Firewall) ===

Open your Windows Firewall for SFC:OP on your gaming machine.
 Note: on Windows Vista and Windows 7, it's under ''"Windows Firewall"'', not ''"Windows Firewall and Advanced Security"''. You'll find an option called ''"Allow a program or feature through Windows Firewall"''. Click on that to see the list of applications and games allowed to go through your firewall. Allow ''"StarFleet Command Orion Pirates"''.

=== SFC networking ports used ===

Do you use a router? If so, you'll need to set up either a DMZ to your computer, or at least some portforward rules so that you can play SFC with others online. I'm sorry if I'm no help here in telling you HOW to do it because I don't know what you have.

Here are the ports to forward to your PC from the router:

* To join a game:
** port 47624, both TCP and UDP

* to host a game:
** port range: 2300-2400
** both TCP and UDP

* For SFC3
** port 6073, both TCP and UDP

* to run an SFC server
** ''(obviously optional)''
** port 27100, both TCP and UDP
** port 3306, both TCP and UDP
*** Scary! That's usually a MySQL server's port!
** port 15100, both TCP and UDP

=== Networking Ports for other related software ===

* to play on mplayer.com
** port range 8000-9000
** both TCP and UDP

* to play on GameSpy
** port 13139, both TCP and UDP

== Tuning SFC to play on modern hardware ==

* Please refer to this following mini-guide I wrote for myself:
** [[Tuning SFC to play on modern hardware ]]

== Visit the Dynaverse.net forums ==

* See :[http://www.dynaverse.net/forum/index.php http://www.dynaverse.net/forum/index.php]
** Best place to find players, new tools, whatever.

SFC-related missions, sources, patches and misc utilities

2017-07-05T19:22:33Z

Firesoul:

== SFC-related Sources, packages, patches and utilities ==

=== SFC Latest Patches and Serverkits ===

==== Latest Patches ====

* SFC:EAW, 2.0.3.6:
** [http://klingon.lostexiles.net/sources_and_utils/patches/SFC2Patch2002-2036.exe SFC2Patch2002-2036.exe]
*** size: 23MB
** [http://klingon.lostexiles.net/sources_and_utils/patches/SFC2Patch2033-2036.exe SFC2Patch2033-2036.exe]
*** size: 2.9MB

* SFC:OP, 2.5.5.2:
** [http://klingon.lostexiles.net/sources_and_utils/patches/SFCOP_Patch_2500-2552.exe SFCOP_Patch_2500-2552.exe]
*** size: 19.4MB
** [http://klingon.lostexiles.net/sources_and_utils/patches/SFCOP_Patch_2550-2552.exe SFCOP_Patch_2550-2552.exe]
*** size: 1.9MB

* SFC, 1.0.3
** [http://klingon.lostexiles.net/sources_and_utils/patches/sfc100-103.zip sfc100-103.zip] size: 4.5Mb
** [http://klingon.lostexiles.net/sources_and_utils/patches/sfc1021-103.zip sfc1021-103.zip] size: 1.5Mb

==== Latest ServerKits ====

* SFC:EAW 2.0.3.6 server kit
** [http://klingon.lostexiles.net/sources_and_utils/SFC2Server2036.zip SFC2Server2036.zip]
*** size: 12MB
* SFC:OP 2.5.5.2 Beta36 server kit
** [http://klingon.lostexiles.net/sources_and_utils/SFCOPServer2552_B36.zip SFCOPServer2552_B36.zip]
*** size: 15.8MB

=== Hidden Features and Easter Eggs ===

About patch 2.5.4.10, 2.5.4.12, 2.5.5.0, 2.5.5.2:
There are 2 hidden features introduced in 25410. This is how you use them.

==== New Arcs ====

Edit the shiplist and put in these arcs where you want them.
* FALX/FARX -> FAL/FAR + right down rear
* LSRF/RSLF -> LS+RF / RS+LF missing arcs
* RRP/RLP -> Rear plasma arcs good for some tugs and HDWs.
* LR -> L+R arc. Can be found on mythical Tholian Snare weapons.

In 2.5.5.2, more arcs were added:
* SFBL/SFBR -> L/R only

==== Switch to disable Engine Doubling ====

Disable Engine Doubling for all pirates. (Useful for Mods). Add ''AllowEngineDoubling=0'' to the ''[Network]'' section of the sfc.ini to disable engine doubling for all pirates.

==== Resetting your SFC:OP Registry entry for your CD-Key ====

Doing the following will cause SFC:OP to re-ask for the CDKey.

* Location: HKLM\\Software\\GameSpy\\CDKeys
** Key: StarfleetCommand2, set to "43", Hex.

Other links on this site:

* [[SFC:OP Plus Refit]]
** many many many (+5000!) added real SFB-based ships
* [[SFC:EAW missions for SFC:OP]]
** EAW missions sources and EAW campaigns compiled for SFC:OP

== SFC Sources: APIs, Mission Scripts ==

=== Development APIs ===

* [http://klingon.lostexiles.net/sources_and_utils/SFC2_API_R1.3.zip SFC2_API_R1.3.zip]
** SFC2:EAW API from Taldren, rev1.3 (size: 5.4mb)
* [http://klingon.lostexiles.net/sources_and_utils/SFCOP_API_R2.zip SFCOP_API_R2.zip]
** SFC2:OP API from Taldren, rev2.2 (size: 5.5mb)

These following files are in no way official packages. These files, zipped from my build environments on my harddrive, will not recieve support in any way. I make these files available to solve problems concerning compiling with either or both EAW and OP APIs on the same machine.

* [http://klingon.lostexiles.net/sources_and_utils/FireSoul_EAW_build_env-20031117.zip FireSoul_EAW_build_env-20031117.zip] (size: 8.7MB)
* [http://klingon.lostexiles.net/sources_and_utils/FireSoul_OP_build_env-20031117.zip FireSoul_OP_build_env-20031117.zip] (size: 9.1mb)
* [http://klingon.lostexiles.net/sources_and_utils/ShipList.20050118.zip ShipList.20050118.zip]
** modified ShipList API to allow access to fighters and PFs list generation. This modification from MagnumMan's SLAPI also contains Enhanced Shiplist support (OP+4.0 only, as far as I can tell). For OP, useful with mSetFighters function. (size: 570Kb) (Can be used with either API. It's smart enough to detect.)
* [http://klingon.lostexiles.net/sources_and_utils/firesoul_shiplist_support_perl_scripts.zip firesoul_shiplist_support_perl_scripts.zip]
** perl script I used to help me debug my OP+ shiplist. There are scripts in there to detect "???" for shipnames, refits and missing names for ship classes.

=== SFC1 mission sources ===

Entire package: [http://klingon.lostexiles.net/sources_and_utils/SFC1_scripts.zip SFC1_scripts.zip] size: 2.0MB
* [http://klingon.lostexiles.net/sources_and_utils/sfc1/Federation.zip Federation.zip] size: 204k
* [http://klingon.lostexiles.net/sources_and_utils/sfc1/Generic.zip Generic.zip] size: 236k
* [http://klingon.lostexiles.net/sources_and_utils/sfc1/Gorn.zip Gorn.zip] size: 164k
* [http://klingon.lostexiles.net/sources_and_utils/sfc1/Hydran.zip Hydran.zip] size: 116k
* [http://klingon.lostexiles.net/sources_and_utils/sfc1/Klingon.zip Klingon.zip] size: 220k
* [http://klingon.lostexiles.net/sources_and_utils/sfc1/Lyran.zip Lyran.zip] size: 168k
* [http://klingon.lostexiles.net/sources_and_utils/sfc1/Multiplayer.zip Multiplayer.zip] size: 100k
* [http://klingon.lostexiles.net/sources_and_utils/sfc1/Romulan.zip Romulan.zip] size: 216k
* [http://klingon.lostexiles.net/sources_and_utils/sfc1/Tutorial.zip Tutorial.zip] size: 212k
* [http://klingon.lostexiles.net/sources_and_utils/sfc1/Unique.zip Unique.zip] size: 156k

=== SFC2 Mission Sources ===

==== Taldren Mission Sources ====

* SFC2 EAW:
** [http://klingon.lostexiles.net/EAW_missions/SFC2_EAW_Scripts.zip SFC2_EAW_Scripts.zip]
*** Taldren's pristine sources for the SFC:EAW scripts
*** size: 8.4MB

* SFC2 OP:
** [http://klingon.lostexiles.net/sources_and_utils/OP_Scripts.zip OP_Scripts.zip]
*** Taldren's pristine sources for the SFC:OP scripts
*** size: 4.9MB

==== Sources to missions ported to SFC:OP ====

* [http://klingon.lostexiles.net/EAW_missions/eaw_campaigns_for_OP_Scripts-20030330.zip eaw_campaigns_for_OP_Scripts-20030330.zip]
** sources to the updated SFC:EAW missions, in an OP build environment. (size: 16.4mb)

=== CoopAce package and sourcecode ===

See: [[Co-op Ace for SFC:EAW and SFC:OP]]

=== Andros! package and sourcecode ===

* [http://klingon.lostexiles.net/sources_and_utils/Mul_Andros.scr Mul_Andros.scr]
** for SFC:OP with OP+ 4.1 size: 446464 Bytes
* [http://klingon.lostexiles.net/sources_and_utils/Mul_Andros_1_01.20110501.zip Mul_Andros_1_01.20110501.zip]
** for SFC:OP with OP+ 4.1 size: 103056 Bytes

=== Fests+ installer and sourcecode ===

See: [[Fests+ for SFC:OP]]

=== SFC:OP Models Tester ===

* Standard version, 1 race at a time:
** [http://klingon.lostexiles.net/sources_and_utils/models_testers/Ski_test_models.scr Ski_test_models.scr] size: 470kb (Version 1.23, 20040627)
** [http://klingon.lostexiles.net/sources_and_utils/models_testers/Ski_test_models-20040627.zip Ski_test_models-20040627.zip] size: 72kb (sources)
* Complete test version, all models tested in a single run:
** [http://klingon.lostexiles.net/sources_and_utils/models_testers/Ski_test_all_models.scr Ski_test_all_models.scr] size: 470kb (Version 1.00, 20040714)
** [http://klingon.lostexiles.net/sources_and_utils/models_testers/Ski_test_all_models-20040714.zip Ski_test_all_models-20040714.zip] size: 77kb (sources)
* Test all bases' models, all in a single run:
** [http://klingon.lostexiles.net/sources_and_utils/models_testers/Ski_test_bases_models.scr Ski_test_bases_models.scr] size: 470kb (Version 1.00, 20040714)
** [http://klingon.lostexiles.net/sources_and_utils/models_testers/Ski_test_bases_models-20040714.zip Ski_test_bases_models-20040714.zip] size: 90kb (sources)

=== EvilDave Missions ===
''(all files/links here updated on 20040112)''

* [http://klingon.lostexiles.net/sources_and_utils/EvilDave/EAWMissions.zip EAWMissions.zip]
** EvilDave missionpack for EAW (updated: 20031001 size: 11mb)
* [http://klingon.lostexiles.net/sources_and_utils/EvilDave/NW_OPMissions.exe NW_OPMissions.exe]
** Configurable EvilDave missionpack for OP (updated: 20040810 size: 4.1mb)
* [http://klingon.lostexiles.net/sources_and_utils/EvilDave/NW_EAWtoOP_Campaigns.zip NW_EAWtoOP_Campaigns.zip]
** Campaign (.MCT) files for BOTH EAW for OP single-player campaigns AND EvilDave missionpacks. (updated: 20030512 size: 25kb) (for OP only)
* [http://klingon.lostexiles.net/sources_and_utils/EvilDave/EDMissionSourceCode.zip EDMissionSourceCode.zip]
** Sources to EvilDave mission packs (updated: 20030228 size: 2.9mb)

=== Other Mission packages ===

* [http://klingon.lostexiles.net/sources_and_utils/TraceyG_OP_missions_v4-1.zip TraceyG_OP_missions_v4-1.zip]
** TraceyG's Missions for OP, version 4.1 (size: 2.5mb)
* [http://klingon.lostexiles.net/sources_and_utils/EEK-OP221.exe EEK-OP221.exe]
** Karnak's EEK missions v2.21, for OP (size: 7.2mb, updated 20041013)
* [http://klingon.lostexiles.net/sources_and_utils/EAW_campaigns+NW+TraceyG+EEK.zip EAW_campaigns+NW+TraceyG+EEK.zip]
** Single player .MCT files for complex campaigns. (size: 25kb)

== Misc Tools and Files ==

=== SFC Modeling tools ===

* [http://klingon.lostexiles.net/sources_and_utils/Modeling/SFC_mod_viewer.zip SFC Models viewer]
** Size: 228kb
* [http://klingon.lostexiles.net/sources_and_utils/Modeling/3DSMaxR3SFCImpExpPublicRelease.zip 3dsMax R3 SFC .MOD format plugin]
** Size: 52kb
* [http://klingon.lostexiles.net/sources_and_utils/Modeling/3DSMaxR4SFCImpExpPublicRelease.zip 3dsMax R4 (and R5) SFC .MOD format plugin]
** Size: 22kb
* [http://klingon.lostexiles.net/sources_and_utils/Modeling/SFC_tutorial-creating_break_models-DIVX.avi SFC_tutorial-creating_break_models-DIVX.avi]
** Size: 14mb, by Joker
* [http://klingon.lostexiles.net/sources_and_utils/Modeling/SFC_tutorial-texturing_and_illumination-DIVX.avi SFC_tutorial-texturing_and_illumination-DIVX.avi]
** Size: 32mb, by Joker

== Other/Misc SFC files ==

=== Other Useful Downloads ===

* [http://klingon.lostexiles.net/sources_and_utils/EzINI.exe EzINI.exe] v2.0
** size: 284Kb
* [http://klingon.lostexiles.net/sources_and_utils/ShipEditv30202.zip ShipEdit v3.02.02 for SFC:EAW]
** size: 6.3Mb
* [http://klingon.lostexiles.net/sources_and_utils/SE39902bPword.zip ShipEdit v3.99.02 beta]
** for SFC:OP
** Requires ShipEdit v3.02.02
** size: 2.6Mb
* [http://klingon.lostexiles.net/sources_and_utils/EAW_Sulu_Bonus_missions.zip EAW_Sulu_Bonus_missions.zip]
** Recompiled for SFC:OP
** size: 496k
* [http://klingon.lostexiles.net/sources_and_utils/Bonus.exe Bonus.exe]
** Taldren's Bonus missions for SFC:OP
** size: 65Kb
* [http://klingon.lostexiles.net/sources_and_utils/Comparator.exe Comparator.exe]
** MagnumMan's Shiplist Comparator for EAW and OP
** size: 163kb
* [http://klingon.lostexiles.net/sources_and_utils/GAW_Models.zip GAW_Models.zip]
** Additional models, released from Taldren
** size: 11.1mb

=== Original shiplist files available for download ===

* SFC:EAW 2036 original files:
** [http://klingon.lostexiles.net/sources_and_utils/orig/eaw/2036/shiplist.txt shiplist.txt] size: 816K
** [http://klingon.lostexiles.net/sources_and_utils/orig/eaw/2036/strings.txt strings.txt] size: 108K
** [http://klingon.lostexiles.net/sources_and_utils/orig/eaw/2036/ftrlist.txt ftrlist.txt] size: 12K
** [http://klingon.lostexiles.net/sources_and_utils/orig/eaw/2036/shipnames.txt shipnames.txt] size: 228K

* SFC:OP 25412, 2550 and/or 2552 original files:
** [http://klingon.lostexiles.net/sources_and_utils/orig/op/25412/shiplist.txt shiplist.txt] size: 1.1M
** [http://klingon.lostexiles.net/sources_and_utils/orig/op/25412/model.siz model.siz] size: 16K
** [http://klingon.lostexiles.net/sources_and_utils/orig/op/25412/strings.txt strings.txt] size: 128K
** [http://klingon.lostexiles.net/sources_and_utils/orig/op/25412/ftrlist.txt ftrlist.txt] size: 20K
** [http://klingon.lostexiles.net/sources_and_utils/orig/op/25412/shipnames.txt shipnames.txt] size: 332K

* SFC:OP 25410 original files:
** [http://klingon.lostexiles.net/sources_and_utils/orig/op/25410/shiplist.txt shiplist.txt] size: 1.1M
** [http://klingon.lostexiles.net/sources_and_utils/orig/op/25410/bpvdata.ini bpvdata.ini] size: 4.0K
** [http://klingon.lostexiles.net/sources_and_utils/orig/op/25410/model.siz model.siz] size: 16K
** [http://klingon.lostexiles.net/sources_and_utils/orig/op/25410/strings.txt strings.txt] size: 128K
** [http://klingon.lostexiles.net/sources_and_utils/orig/op/25410/quicktips.txt quicktips.txt] size: 128K
** [http://klingon.lostexiles.net/sources_and_utils/orig/op/25410/bindings.ini bindings.ini] size: 4.0K
** [http://klingon.lostexiles.net/sources_and_utils/orig/op/25410/ftrlist.txt ftrlist.txt] size: 20K
** [http://klingon.lostexiles.net/sources_and_utils/orig/op/25410/aaStrings.txt aaStrings.txt] size: 384K
** [http://klingon.lostexiles.net/sources_and_utils/orig/op/25410/shipnames.txt shipnames.txt] size: 332K

* SFC:OP 2538 original files:
** [http://klingon.lostexiles.net/sources_and_utils/orig/op/2538/shiplist.txt shiplist.txt] size: 1.1M
** [http://klingon.lostexiles.net/sources_and_utils/orig/op/2538/strings.txt strings.txt] size: 120K
** [http://klingon.lostexiles.net/sources_and_utils/orig/op/2538/ftrlist.txt ftrlist.txt] size: 20K
** [http://klingon.lostexiles.net/sources_and_utils/orig/op/2538/shipnames.txt shipnames.txt] size: 292K

* SFC:OP 2525 original files:
** [http://klingon.lostexiles.net/sources_and_utils/orig/op/2525/shiplist.txt shiplist.txt] size: 1.1M
** [http://klingon.lostexiles.net/sources_and_utils/orig/op/2525/strings.txt strings.txt] size: 120K
** [http://klingon.lostexiles.net/sources_and_utils/orig/op/2525/ftrlist.txt ftrlist.txt] size: 20K
** [http://klingon.lostexiles.net/sources_and_utils/orig/op/2525/shipnames.txt shipnames.txt] size: 292K

=== FireSoul's Screenshots ===

* [http://klingon.lostexiles.net/screenshots/woah.JPG woah.JPG]
** coopace development screenshot before the 32 AI ships limit was introduced. This was taken as proof that the script was now stable.

* [http://klingon.lostexiles.net/screenshots/1peace_OP_1.JPG 1peace_OP_1.JPG]
** ... Yes, the OP-compiled EAW campaigns work.

* [http://klingon.lostexiles.net/screenshots/1peace_OP_2.JPG 1peace_OP_2.JPG]
** .... really, they really do run on SFC:OP.

* [http://klingon.lostexiles.net/screenshots/OhMyESGs.png OhMyESGs.png]
** .. that was back in the days I was helping MagnumMan test his 'patch of day' for SFC:EAW. The point here was proof that being able to see the ESG ranges of the enemy was visible in a multiplayer game.

* [http://klingon.lostexiles.net/screenshots/challenge.JPG challenge.JPG]
** Ah memories.. .. I won against a R-CON+ with a ... F-NCL+ ... ?

* [http://klingon.lostexiles.net/screenshots/coopace-fighters1.JPG coopace-fighters1.JPG]
** at one point during coopace development, I was tring to get the AI to get free updated fighters. This is a screenshot of the success. (Please note I am running away really really fast.)

* [http://klingon.lostexiles.net/screenshots/coopace-fighters2.JPG coopace-fighters2.JPG]
** (THIS is what I was really running away from!)

* [http://klingon.lostexiles.net/screenshots/double-base-construction.gif double-base-construction.gif]
** Want to guarantee SB construction on a D2 server? It's been a long time since I've done this trick, but maybe this will still work?

* [http://klingon.lostexiles.net/screenshots/slot_2033.JPG slot_2033.JPG]
** THIS is the slot bug. I am FireSoul.. I am NOT strafer. bleh.

* [http://klingon.lostexiles.net/screenshots/tractored_plasma.jpg tractored_plasma.jpg]
** I caught this one during OP testing. A plasma was fired at a tractored MIRV. The mirv itself was invisible, this was proof that the object was actually absent: the plasma kept tracking an unhittable object. (Although it looks like a plasma being tractored.)

* [http://klingon.lostexiles.net/screenshots/where_is_mirv.jpg where_is_mirv.jpg]
** past MIRV bugs that had been fixed. Isn't being a tester fun?

* [http://klingon.lostexiles.net/screenshots/winex-shipedit.png winex-shipedit.png]
** The EagleEye ShipEdit program runs under WineX.

* [http://klingon.lostexiles.net/screenshots/winex_sfcop.png winex_sfcop.png]
** So does SFC:OP. WineX is by TransGaming Technologies, my ex-employer. WineX is called Cedega, today.

SFC:OP Missions Refit

2017-07-05T19:21:36Z

Firesoul:

== Introduction ==

When I finally released [[SFC:OP Plus Refit]], I decided to reward myself and play a single player campaign. I loaded up the latest [http://www3.telus.net/NuclearWessels/sfc/downloads/NWPack.exe mission pack] from NuclearWessels and gave it a shot.

Well, I quickly found myself frustrated with the game again.

Here are some of the issues I had with the game at this point:
# almost everything had slow drones
# everything had basic fighters
# the new Andromedan ships weren't being loaded up right.
# some missions had hardcoded ships.

.. note that I also encountered some problems with my own [[SFC:OP Plus Refit]] mod, which resulted in the release of version 4.1.1:
# the planets were still shooting themselves with their heavy weapons
# many monsters encountered had 0 crew/boarding parties and were boardable. (1 BP and captured!)

== Vision ==

Imagine loading a "Fleet Patrol" mission: destroy all enemies, or disengage if the enemy is too much for you. It's year 2285.3: you've got a L-BCHT with 4 upgraded PFs. You find yourself in-mission with 2 Klingon wingmen AI-controlled ships, and there's 3 Hydran ships in the distance.

As you close towards your enemy, both your allies and your enemy launch whatever fighters they have. Your Klingon friends launch their K-Lancer.IIIs. The Hydrans, a carrier-based race, have many many H-YellowJacket.IIIs and H-Hornet.IIs as are normally available during that year. You send out your L-PFLs in Harass, adding yet more confusion to the fray.

Your wingmen launch their drones and they are all fast speeds at that. One of the Hydran ships weasels, and its fighter-groups obliterates your destroyer-sized wingman in a single pass.

Then... from the far right... comes a M-aDMX Andromedan Dominatrix Dreadnought, friend to no one and intent on destroying everyone.

.. now that's a Patrol mission!

== Making it happen.. ==

I spent weeks trying to find work-arounds or fixes to these problems. Here's what I've found out:

=== Better in-mission created ship selection ===
* find better way to load up Bases, FRDs, cargo ships, etc. Do NOT use hard-coded ships because these things do get refits over time.
** use shiplist API, load shiplist from MetaAssets directory

=== Give the AI Upgraded fighters ===
* Give AIs better fighters. We cannot determine what fighters a ship has, but we can parse and load the fighterlist and assign era-correct fighters to AI-controlled teams.
** use ShipList API to load fighterlist, specifically from the MetaAssets directory.

=== Give the ships era-correct drone speeds ===
* If a ship was drafted, it'll have slow drones no matter what. However, if the ship was created in-mission and not drafted, the drone speeds will be era-correct. Solution: do not created drafted ships, create in-game only ships with same shipcodes as the drafted ships.
** Ships do NOT get cleaned up from the D2 map. The server's .gf files should be edited to turn on ship destruction and cycling to compensate.
*** see: MetaMap.gf, section [Census], MaxAIsToKillPerTurn parameter.
** if the drafted unit is a base, the mission creates a 'BOX' unit upon destruction WITH the base's drafted ID (aka MetaID) and immediately destroys it. This will be passed back to the D2 engine, multiplayer or not, that whatever had the Base's MetaID was destroyed which may result on base's removal from the D2 map.

=== Don't set-up a mission with a planet that is too big ===
* The planet model sizes are stored in model.siz. The idea is to set up the mission's code to load and parse model.siz, prepare a list of eligible planets that aren't too big and select one randomly from that list.
** ie: I need a Hydran Armed World, limited size.
** Why? Because the FRDs and Defense Platforms may be close to the planet. A large planet will make stuff collide (and thus destroyed) on mission start.

=== Andro tweaks ===
* Auto-detect Andros in the shiplist. If they are there, give them a chance to appear instead of Monsters or Orion pirates or whatever encounters NuclearWessels had originally set up.
** it's just a small chance.

== About the difficulty ==

Yes.. this pack is for everyone out there who play at Admiral Level Difficulty!

* Easy/Captain:
** drafted ships get slow drones (turns off workaround)
** All AI-controlled teams get stock/basic fighters.

* Medium/Commodore:
** drafted ships get ''ERA-CORRECT'' drone speeds.
** All AI-controlled teams still get stock/basic fighters.

* Hard/Admiral:
** drafted ships get ''ERA-CORRECT'' drone speeds.
** All AI-controlled teams fighters ''ARE UPGRADED''.

== What's included? ==

* .SCR Mission scripts, of course. All updated to the specs mentionned above.
** 30 generic missions, originally from NuclearWessels pack
** The ISC Campaign of Pacification missions (play as ISC)
** The Campaign against the ISC Pacification missions (play as the other empire races)
** The Mirak Campaigns (play as Mirak vs Lyran)
** The Mirak Campaigns (play as Klingon, Hydran or Lyran against the Mirak)
* .MCT campaign files for all normal races
* .MCT campaign files for pirate races
* .GF campaign configuration files to tweak stock campaign settings to something more enjoyable.

== Download ==

=== Missions Refit 1.5 ===

NOTE: This mission-pack works best with OP+ 4.1.1 .. at least so far. (as of 20110807) See: [[SFC:OP Plus Refit]]

* Installer: [http://klingon.lostexiles.net/Missions_Refit/SFCOP_MissionsRefit_15_20121022222638.exe SFCOP_MissionsRefit_15_20121022222638.exe] (5.3MB)

* Mission Sources:
** EvilDave missions: [http://klingon.lostexiles.net/Missions_Refit/Missions07.20121022.7z Missions07.20121022.7z] (1.7MB)
** EAW Campaign Mission Sources: [http://klingon.lostexiles.net/Missions_Refit/eaw_Scripts.20121022.7z eaw_Scripts.20121022.7z] (8 MB)
*** ISC Pacification Campaigns and Missions
**** both for and against, all campaigns just like in EAW.
*** Mirak Campaigns and Missions
**** both for and against, all campaigns just like in EAW.
** Needs ShipList API to compile: [http://klingon.lostexiles.net/sources_and_utils/ShipList.20050118.zip ShipList.20050118.zip]
** also see: [[SFC-related_missions,_sources,_patches_and_misc_utilities]]

SFC:OP Plus Refit

2017-07-05T19:20:30Z

Firesoul:

A mod for StarFleet Command : Orion Pirates patch version 2552

* [[OP+ Introduction]]
* [[OP+ Contents and Changes]]
* [[OP+ Statistics]]
* [[OP+ Conversion Rules]]
** conversion rules for ships, from SFB to SFC.
* [[OP+ and Test-Driven Development]]
* [[OP+ about the ship models]]
* [[OP+ FAQ]]
* [[OP+ Fair Use]]

=== Downloads ===

==== OP+ 4.1.1 ====
Released: 2011-08-07

Note: should be compatible with OP+ 4.1, despite in-game warnings. See [[OP+ Contents and Changes]] for differences.

* [http://klingon.lostexiles.net/OP_plusrefit/opplus_411_models_20110724175017.exe opplus_411_models_20110724175017.exe]
** size: 77mb

The installer above will require around 760mb for installation. This is the final release of OP+ 4.1.1.

* Installation Instructions: [http://klingon.lostexiles.net/OP_plusrefit/readme.txt readme.txt]
* Disclaimer: [http://klingon.lostexiles.net/OP_plusrefit/readme.txt readme.txt]

----

==== OP+ 4.1 ====
Released: 2011-06-10 (installer-only update, fully compatible with 2011-06-05 release)

* [http://klingon.lostexiles.net/OP_plusrefit/opplus_41_models_20110610085609.exe opplus_41_models_20110610085609.exe]
** size: 77mb

The installer above will require around 760mb for installation. This is the final release of OP+ 4.1. It's a repackaged release candidate 5 with an updated license.

* Installation Instructions: [http://klingon.lostexiles.net/OP_plusrefit/readme.txt readme.txt]
* Disclaimer: [http://klingon.lostexiles.net/OP_plusrefit/readme.txt readme.txt]

----

==== OP+ 4.0 ====
Released: 2005-01-01

* [http://klingon.lostexiles.net/OP_plusrefit/opplus_40_models.exe opplus_40_models.exe]
** includes models
** size: 63MB
* [http://klingon.lostexiles.net/OP_plusrefit/opplus_40_no_models.exe opplus_40_no_models.exe]
** size: 275KB

Mirror at ftp.xenocorp.net:
* [ftp://ftp.xenocorp.net/game_files/Star_Trek/starfleet_command/Starfleet_Command_OP/shiplists/opplus_40_models.exe opplus_40_models.exe]
* [ftp://ftp.xenocorp.net/game_files/Star_Trek/starfleet_command/Starfleet_Command_OP/shiplists/opplus_40_no_models.exe opplus_40_no_models.exe]

The "with models" installer above will require around 700mb for installation. The no models installer should require around 500mb.

* Installation Instructions: [http://klingon.lostexiles.net/OP_plusrefit/readme.txt readme.txt]
* Disclaimer: [http://klingon.lostexiles.net/OP_plusrefit/readme.txt readme.txt]

----

==== Coopace 4.0 ====

This shiplist works '''''GREAT!''''' with the CoopAce script version 4.0.

* [http://klingon.lostexiles.net/sources_and_utils/coop-ace-4.0.exe CoopAce 4.0 installer]

See: [[Co-op Ace for SFC:EAW and SFC:OP]]

==== Extra Reading Material ====

Available official storyline of the [http://www.starfleetgames.com/sfb/sfin/general_war.htm General War], straight from ADB, at [http://www.starfleetgames.com/ StarFleetGames.com].

FireSoul's SFC Materials

2017-07-05T19:18:50Z

Firesoul:

http://klingon.lostexiles.net/FSBanner.png

This site is composed of the following sub-components:

* [[SFC:OP Plus Refit]]
* [[SFC:OP Missions Refit]]
* [[SFC-related missions, sources, patches and misc utilities]]
** [[All SFC Patches and ServerKits]]
** [[Co-op Ace for SFC:EAW and SFC:OP]]
** [[SFC:EAW missions for SFC:OP]]
** [[Fests+ for SFC:OP]]
** [[How to compile/build SFC2 EAW or OP Missions]]
* [http://klingon.lostexiles.net/models/ Models for SFC:OP (and EAW) made or hosted by FireSoul]
* [[FireSoul's SFC:OP BootStrap list]]
** [[Tuning SFC to play on modern hardware]]

Also, here's a list of SFC-related links I keep around:

* [http://www3.telus.net/NuclearWessels/sfc/ NuclearWessels' Scripting Site]
* [http://members.fortunecity.com/sfcspacedock/index.htm SFC2 War Refit Spacedock]
* [http://www.xenocorp.net/ XC Site]
* [http://www.dynaverse.net/ Dynaverse.net]
** [http://www.dynaverse.net/forum/index.php Dynaverse.net Forums]
* [http://www.strategyplanet.com/sfc/omega/fleetdock13/ FleetDock 13]

SFC:EAW missions for SFC:OP

2016-06-28T18:34:59Z

Firesoul: /* Packages */

=== Recommendations ===

These are the ''stock'' recompiled EAW missions for SFC:OP. I '''strongly''' recommend using the Missions Refit versions along with OP+.
* [[SFC:OP Plus Refit]]
* [[SFC:OP Missions Refit]]

=== Packages ===
* NEW: See Missions Refit: [[SFC:OP_Missions_Refit]]
** All of the EAW missions rebuilt to properly use OP+, but also backwards compatible.
* OLD: [http://klingon.pet.dhs.org/EAW_missions/EAW_Campaigns_for_OP-20030330.exe EAW_Campaigns_for_OP-20030330.exe]
** the SFC:EAW single player campaigns compiled for SFC:OP.
** size: 3.0 MB
*** Campaign files have been modified to include SFC:OP missions not present in SFC:EAW.
*** Includes the Sulu Missions
* [http://klingon.pet.dhs.org/EAW_missions/Sulu_Bonus_missions_for_OP-20021124.zip Sulu_Bonus_missions_for_OP-20021124.zip]
** Sulu bonus missions, without the Sulu voice recordings.
** size: 735KB
* [http://klingon.pet.dhs.org/sources_and_utils/EvilDave/NW_EAWtoOP_Campaigns.zip NW_EAWtoOP_Campaigns.zip]
** .MCT Campaign files for OP
** mixes EvilDave packages and EAW for OP campaigns, for the BEST single-player experience!
** [http://klingon.pet.dhs.org/EAW_missions/howto_install_20030617.txt howto_install_20030617.txt]
*** instructions on how to install the single player campaigns mixed with the EvilDave missions. Updated: 20030617.

SFC:EAW missions for SFC:OP

2016-06-28T18:30:10Z

Firesoul:

=== Recommendations ===

These are the ''stock'' recompiled EAW missions for SFC:OP. I '''strongly''' recommend using the Missions Refit versions along with OP+.
* [[SFC:OP Plus Refit]]
* [[SFC:OP Missions Refit]]

=== Packages ===

* [http://klingon.pet.dhs.org/EAW_missions/EAW_Campaigns_for_OP-20030330.exe EAW_Campaigns_for_OP-20030330.exe]
** the SFC:EAW single player campaigns compiled for SFC:OP.
** size: 3.0 MB
*** Campaign files have been modified to include SFC:OP missions not present in SFC:EAW.
*** Includes the Sulu Missions
* [http://klingon.pet.dhs.org/EAW_missions/Sulu_Bonus_missions_for_OP-20021124.zip Sulu_Bonus_missions_for_OP-20021124.zip]
** Sulu bonus missions, without the Sulu voice recordings.
** size: 735KB
* [http://klingon.pet.dhs.org/sources_and_utils/EvilDave/NW_EAWtoOP_Campaigns.zip NW_EAWtoOP_Campaigns.zip]
** .MCT Campaign files for OP
** mixes EvilDave packages and EAW for OP campaigns, for the BEST single-player experience!
** [http://klingon.pet.dhs.org/EAW_missions/howto_install_20030617.txt howto_install_20030617.txt]
*** instructions on how to install the single player campaigns mixed with the EvilDave missions. Updated: 20030617.

FireSoul's SFC:OP BootStrap list

2015-08-09T00:45:40Z

Firesoul: /* Set up a key to launch all the fighters */

So you want to know how I set up SFC:OP? Ok!

== Update your DirectX ==

Make sure you have the right DirectX support on your machine. The game itself was shipped with DirectX 8 installables. DO NOT USE THOSE, THEY ARE ANCIENT. If you're on Windows XP or older, use DirectX 9.0c.

That said, newer Windows was NOT shipped with DirectX support for ''older'' games. You'll need to run an updater from MicroSoft to do so. This installer/updater will examine your system's DirectX libraries, both old and new, and make sure you have all of them.
 See: http://www.microsoft.com/en-us/download/details.aspx?id=35

== Install SFC:OP ==

* Find your CD.
* Find your CD-Key.
* Install.

== Patch to SFC:OP 2.5.5.2 ==

* Download the patch.
** [http://klingon.pet.dhs.org/sources_and_utils/patches/SFCOP_Patch_2500-2552.exe SFCOP_Patch_2500-2552.exe]
* Install the patch.

What, you don't have 2.5.0.0 but something else? See here: [[All SFC Patches and ServerKits]]

== Run the game to type the CD-Key ==

* Make sure you have your CD-Key on paper or something you can read from
** copy-paste won't work here
* just start it up, and type in your Key.
* exit the game when you're done.

== Install Latest OP+ ==

See: [[SFC:OP Plus Refit]]

* Get the latest OP+
** .. or whatever people are playing. I suggest the latest.
* Install it.

== Set up your preferences with EzINI ==

* get [http://klingon.pet.dhs.org/sources_and_utils/EzINI.exe EzINI]
* run EzINI
* Select Orion Pirates (if necessary)
* set up your:
** graphics resolution
** show damage
** sound settings
** multiplayer game player name
** default multiplayer game name
** default difficulty level
** etc etc etc

=== My suggestions for EzINI settings===

* Video
** Resolution: 1024 x 768
* Audio
** Music Volume --- OFF
*** That's completely optional. You can leave it on if you want.
** Max Channels: 64 (max)
** Crew Sounds: Maximum
* Multiplayer
** Set up your Default Multiplayer Player Name
** Set up your Game Name
** OPTIONAL: click on Multiplayer Hidden Race
** OPTIONAL: click on Multiplayer Hidden BPV
* Misc
** Difficulty: Admiral
** turn ON Volley Information

== Install Co-Op Ace ==

See: [[Co-op Ace for SFC:EAW and SFC:OP]]

* Get the latest coopace
** Currently [http://klingon.pet.dhs.org/sources_and_utils/coop-ace-4.0.exe Coopace 4.0]
* install it.

== Customize Co-Op Ace==

* run the Coop-Ace Customizer from your start menu
** Set the Difficulty to around 1.5
*** or whatever you prefer. I got 1.7 right now
** Set the AI Intelligence to Admiral
** Races: single
** uncheck all the pirates
*** up to you, but remember, pirates are weaker
** Turn ON 'Force selection of ships created in current era'
*** This will improve the gaming experience, especially since you've installer OP+
** Turn ON 'Use Enhanced Shiplist API Settings'

== Fests+ ==

See: [[Fests+ for SFC:OP]]

* download the [http://klingon.pet.dhs.org/fests+/Fests+_11.exe Fests+] installer
* install it
* download the extra mission: [http://klingon.pet.dhs.org/fests+/Mul_Battlefest+Intense.scr Battlefest+ Intense]
* install it
** Find your SFC install directory
** Hint! May be: ''C:\Program Files (x86)\Taldren Software Inc\Starfleet Command Orion Pirates''
** Go into Assets\Scripts\
** copy Mul_Battlefest+Intense.scr there

== Missions Refit pack ==

See: [[http://klingon.pet.dhs.org/mediawiki/index.php?title=SFC:OP_Missions_Refit SFC:OP Missions Refit]]

* download the [http://klingon.pet.dhs.org/Missions_Refit/SFCOP_MissionsRefit_15_20121022222638.exe SFCOP_MissionsRefit_15_20121022222638.exe] installer
* install it

== Set up a key to launch all the fighters ==

* Launch the game
* Click on the 'Hot Keys' Button
** never BEEN here, huh?!
* click on 'Weapons'
* put in a ket for Launch Fighters.
** I tend to use 'L' for it.
*** 'L' is usually the Defense panel shortcut, which I never use via HotKey.
* exit the game to make sure your settings change are saved

If you screwed up, no problem! Go pick up a fresh copy of [http://klingon.pet.dhs.org/sources_and_utils/orig/op/25410/bindings.ini bindings.ini] from [[SFC-related missions, sources, patches and misc utilities]].

Note, 2015-08-08: changing bindings didn't stick for me on my Windows 7 machine. :-/ I had to edit the file manually with notepad. To do '''that''', I needed to grant myself access to the files.

for example:
http://klingon.pet.dhs.org/screenshots/20150808_win7_grant_yourself_full_access.png

Then go edit the file directly with notepad. It's going to be in under your SFC game's install directory, as Assets\Specs\bindings.ini

The changes:
* "LaunchFighters= " to "LaunchFighters=L"
* "Defense=L" to "Defense= "
** That's: Defense=<space>

== Dynaverse 2 Directory Server Updater ==

The Dynaverse 2 Server list updater is optional: I don't know if there still are D2 servers for SFC:OP out there, but in case there are, you can use this:

* [http://www.dynaverse.net/downloads.php?id=56&game=SFC2%20OP#download D2 Directory Server Updater]
* Run it.

== Set up your FireWall(s) to play online ==

=== Gaming host's firewall (AKA Windows Firewall) ===

Open your Windows Firewall for SFC:OP on your gaming machine.
 Note: on Windows Vista and Windows 7, it's under ''"Windows Firewall"'', not ''"Windows Firewall and Advanced Security"''. You'll find an option called ''"Allow a program or feature through Windows Firewall"''. Click on that to see the list of applications and games allowed to go through your firewall. Allow ''"StarFleet Command Orion Pirates"''.

=== SFC networking ports used ===

Do you use a router? If so, you'll need to set up either a DMZ to your computer, or at least some portforward rules so that you can play SFC with others online. I'm sorry if I'm no help here in telling you HOW to do it because I don't know what you have.

Here are the ports to forward to your PC from the router:

* To join a game:
** port 47624, both TCP and UDP

* to host a game:
** port range: 2300-2400
** both TCP and UDP

* For SFC3
** port 6073, both TCP and UDP

* to run an SFC server
** ''(obviously optional)''
** port 27100, both TCP and UDP
** port 3306, both TCP and UDP
*** Scary! That's usually a MySQL server's port!
** port 15100, both TCP and UDP

=== Networking Ports for other related software ===

* to play on mplayer.com
** port range 8000-9000
** both TCP and UDP

* to play on GameSpy
** port 13139, both TCP and UDP

== Tuning SFC to play on modern hardware ==

* Please refer to this following mini-guide I wrote for myself:
** [[Tuning SFC to play on modern hardware ]]

== Visit the Dynaverse.net forums ==

* See :[http://www.dynaverse.net/forum/index.php http://www.dynaverse.net/forum/index.php]
** Best place to find players, new tools, whatever.