Topic: Looking at those pesky .SCR files  (Read 1999 times)

0 Members and 1 Guest are viewing this topic.

Offline Roychipoqua_Mace

  • Lt.
  • *
  • Posts: 786
  • Gender: Male
Looking at those pesky .SCR files
« on: February 23, 2008, 04:51:00 pm »
Is there a simple way to view te .scr script files in OP? I would like to open up "Mul_4Tourneyfest.scr" so that I can see what ships are used by all the races in the tourneyfest multiplayer mission. Would be helpful to see if some races get gypped with a loser ship before actually flying the mission in a real battle w/ PvP.

So far, I've tried Textpad, which is usually pretty good about decoding things, but I just got a bunch of code. Nothing helpful like
Fed Frigate: FFG
Fed Destroyer: DDG
etc.

Or if you know of a list that just gave all the classes. Any help would be appreciated.

Offline Pestalence_XC

  • "The Terminator"
  • Commander
  • *
  • Posts: 2636
  • Gender: Male
  • "The Terminator" Pestalence_XC, Xenocorp
Re: Looking at those pesky .SCR files
« Reply #1 on: February 23, 2008, 08:19:21 pm »
You need Microsoft Visual C++ 6.0 with Sp5 or Sp6 and the Scripting Source files that are included in the game.. plus you have to have knowledge of C++..
"You still don't get it, do you?......That's what he does. That's all he does! You can't stop him! It can't be bargained with. It can't be reasoned with. It doesn't feel pity, or remorse, or fear. And it absolutely will not stop, ever, until you are dead!"

Member :
Xenocorp / Dynaverse.net Moderator & Beta Test Team
SFC 4 Project QA Coordinator
Taldren Beta Test Team
14 Degrees East Beta Test Team
Activision Visioneers SFC 3 Beta Test Team

Offline Rod ONeal

  • D.Net Beta Tester
  • Commander
  • *
  • Posts: 3592
  • Gender: Male
Re: Looking at those pesky .SCR files
« Reply #2 on: February 24, 2008, 02:23:56 am »
You can't actually open the .scr files. As Pestalence says, you need Microsoft Visual C++ 6.0, the scripting API and the source code for the script. You could then make changes to the original source and compile your own .scr files. With some C++ knowledge.
If Romulans aren't cowards, then why do they taste like chicken?

Offline Bonk

  • Commodore
  • *
  • Posts: 13298
  • You don't have to live like a refugee.
Re: Looking at those pesky .SCR files
« Reply #3 on: February 24, 2008, 05:44:30 am »
The ships used in Tourneyfest and Tourneyfest lite, are listed below.

Looking at the source for Mul_4Tourneyfest, I find this:

Code: [Select]
const char* gClassNames[kNumActiveRaces][kNumShips] =
{
//Avg BPV 72 100 120 133 185 235
// Federation
{ "F-FFG", "F-DDG", "F-NCL", "F-CAR", "F-BCJ", "F-DNG" },

// Klingon
{ "K-F5", "K-FWK", "K-AD5", "K-D7B", "K-C7", "K-C8K" },

// Romulan
{ "R-K4RB", "R-K5LB", "R-KFR", "R-SPA+", "R-KRCS", "R-CON" },

// Lyran
{ "L-FFP", "L-DWP", "L-CW+", "L-CA+", "L-BCH", "L-DNP+"},

// Hydran
{ "H-CRU", "H-DWH", "H-RN+", "H-LC", "H-OV", "H-ID" },

// Gorn
{ "G-DD+", "G-BDL", "G-CLF", "G-CC", "G-BCH", "G-DNF" },

// ISC
{ "I-FF", "I-DDGZ", "I-CLW", "I-CLY", "I-CAZ", "I-DN" },

// Mirak
{ "Z-DF", "Z-DWL", "Z-MDC+", "Z-BC", "Z-BCH", "Z-DN+" },

// OrionOrion
{ "X-DWS2", "X-CR1", "X-BR2", "X-CA+1", "X-BC2", "X-DN3" },

// OrionKorgath
{ "Y-LRS+2", "Y-CR1", "Y-MR2", "Y-CA+3", "Y-BC2", "Y-DN3" },

// OrionPrime
{ "P-LRS1", "P-DBR1", "P-MR2", "P-CA+3", "P-CA+2", "P-DN1" },

// OrionTigerHeart
{ "T-LR+2", "T-DBR3", "T-MR3", "T-CA+3", "T-DCR2", "T-CV3" },

// OrionBeastRaiders
{ "B-LRS+2", "B-CR+1", "B-BR1", "B-CA+3", "B-BRH2", "B-DN3" },

// OrionSyndicate
{ "S-LRS1", "S-DBR1", "S-MR2", "S-CA3", "S-BC1", "S-DN1" },

// OrionWyldeFire
{ "W-LR+2", "W-DBR1", "W-MR2", "W-CA3", "W-CA+3", "W-DN2" },

// OrionCamboro
{ "C-LRS+2", "C-DBR1", "C-BR3", "C-CA3", "C-BC3", "C-DN1" },
};


And for Mul_6TourneyfestLite:

Code: [Select]
const char* gClassNames[kNumActiveRaces][kNumShips] =
{
//Avg BPV 72 133 235
// Federation
{ "F-FFG", "F-CAR", "F-DNG" },

// Klingon
{ "K-F5", "K-D7B", "K-C8K" },

// Romulan
{ "R-K4RB", "R-SPA+", "R-CON" },

// Lyran
{ "L-FFP", "L-CA+", "L-DNP+"},

// Hydran
{ "H-CRU", "H-LC", "H-ID" },

// Gorn
{ "G-DD+", "G-CC", "G-DNF" },

// ISC
{ "I-FF", "I-CLY", "I-DN" },

// Mirak
{ "Z-DF", "Z-BC", "Z-DN+" },

// OrionOrion
{ "X-DWS2", "X-CA+1", "X-DN3" },

// OrionKorgath
{ "Y-LRS+2", "Y-CA+3", "Y-DN3" },

// OrionPrime
{ "P-LRS1", "P-CA+3", "P-DN1" },

// OrionTigerHeart
{ "T-LR+2", "T-CA+3", "T-CV3" },

// OrionBeastRaider
{ "B-LRS+2", "B-CA+3", "B-DN3" },

// OrionSyndicate
{ "S-LRS1", "S-CA3", "S-DN1" },

// OrionWyldeFire
{ "W-LR+2", "W-CA3", "W-DN2" },

// OrionCamboro
{ "C-LRS+2", "C-CA3", "C-DN1" },
};

I believe the source for the stock scripts is in the scripting api:
http://www.khoromag.org/taldren/scripting_api/SFCOP_API_R2.zip
You can use notepad or wordpad to read the script source files and dig out information like this without the need for a VC install (it will not work with VC8+/Express anyway, only the old VC6SP5).
« Last Edit: February 24, 2008, 06:45:34 am by Bonk »

Offline Roychipoqua_Mace

  • Lt.
  • *
  • Posts: 786
  • Gender: Male
Re: Looking at those pesky .SCR files
« Reply #4 on: February 24, 2008, 10:06:19 am »
Thanks Pestalence and Rod ONeal for the info regarding scripts. I don't have C++ 6.0 or any knowledge of scripting, so it probably would be a bad idea to mess around with them.

Thanks Bonk for the list of ships and the API source link. This is exactly what I was looking for!