Next you must have Microsoft Visual C++ Express 2008 (2005 will work with the x86sdk added but 05 isn’t available any longer).  It is a free download from Microsoft that you can download from here:

http://www.microsoft.com/express/download/

Install it with all default settings.

Next you must have the Legacy Mission Editor.  Any info posted on this site will be for Version 1.04c of the Modified Legacy Mission Editor that I created based on the Original release by Bethesda.  Here are two links for the 1.4c release.  If you happen to be using the Ultimate Universe Mod Version 1.5 (or higher) you will already have the 1.4c Mission Editor installed.

http://www.ultimateuniversemod.net/download.php?view.23

http://legacy.filefront.com/file/Muldrfs_Modified_Legacy_Mission_Editor;94180

—-

If your using a 64bit version of windows be it Windows XP Pro x64, Vista 64bit or Windows 7 you will have to change the path to the C++ Compiler.  The Default path is “C:\Program Files\Microsoft Visual Studio 9.0\VC\bin” you must change it to “C:\Program Files (x86)\Microsoft Visual Studio 9.0\VC\bin”.  To do this goto the “Edit” menu on the Legacy Mission Editor and then “Configuration” and change the path there.  For Windows XP or Vista 32 bit leave it at the default.

Also for Any version of Windows Vista or Windows 7 you MUST use “Run as Administrator” or it work properly or be able to compile missions.  To do this you must right click on the icon and pick “Run as Administrator” or change the Properties on the icon and set it to always run as administrator.  If you turn off “UAC” or “User Account Control” in Vista/Windows7 you shouldn’t have to do this.

—-

Congratulations once those are installed you should be good to go as far as required software goes.   To test if it’s working properly open the Legacy Mission Editor and select the Tkm01 (first mission on the list) and click on “Build Mission” on the menu at the top.  You should get 3 “Output” Windows with various text in.  The first two are displays of some various info on the .scp and .rul files when they are parsed, they are rarely used.  The third and final window is for the actual compile.  You should get an output similar to this:

—–

C:\Program Files (x86)\Bethesda Softworks\Star Trek Legacy\missions\tkm01>call “C:\Program Files (x86)\Microsoft Visual Studio 9.0\VC\bin\vcvars32.bat”

C:\Program Files (x86)\Bethesda Softworks\Star Trek Legacy\missions\tkm01>”C:\Program Files (x86)\Microsoft Visual Studio 9.0\Common7\Tools\vsvars32.bat”
Setting environment for using Microsoft Visual Studio 2008 x86 tools.

C:\Program Files (x86)\Bethesda Softworks\Star Trek Legacy\missions\tkm01>cl.exe tkm01s.cpp /O2 /Ob1 /I “..\..\Include” /D “WIN32″ /D “NDEBUG” /D “_WINDOWS” /D “_WINDLL” /D “_CRT_SECURE_NO_WARNINGS” /GF /FD /EHsc /MT /Gy /W3 /nologo /c /errorReport:prompt
tkm01s.cpp

C:\Program Files (x86)\Bethesda Softworks\Star Trek Legacy\missions\tkm01>link.exe tkm01s.obj /OUT:”tkm01s.dsl” /INCREMENTAL:NO /NOLOGO /DLL /SUBSYSTEM:WINDOWS /IMPLIB:”tkm01s.lib” /MACHINE:X86 /ERRORREPORT:PROMPT kernel32.lib user32.lib gdi32.lib winspool.lib comdlg32.lib advapi32.lib shell32.lib ole32.lib oleaut32.lib uuid.lib odbc32.lib odbccp32.lib
Creating library tkm01s.lib and object tkm01s.exp

C:\Program Files (x86)\Bethesda Softworks\Star Trek Legacy\missions\tkm01>cl.exe tkm01r.cpp /O2 /Ob1 /I “..\..\Include” /D “WIN32″ /D “NDEBUG” /D “_WINDOWS” /D “_WINDLL” /D “_CRT_SECURE_NO_WARNINGS” /GF /FD /EHsc /MT /Gy /W3 /nologo /c /errorReport:prompt
tkm01r.cpp

C:\Program Files (x86)\Bethesda Softworks\Star Trek Legacy\missions\tkm01>link.exe tkm01r.obj /OUT:”tkm01r.drl” /INCREMENTAL:NO /NOLOGO /DLL /SUBSYSTEM:WINDOWS /IMPLIB:”tkm01r.lib” /MACHINE:X86 /ERRORREPORT:PROMPT kernel32.lib user32.lib gdi32.lib winspool.lib comdlg32.lib advapi32.lib shell32.lib ole32.lib oleaut32.lib uuid.lib odbc32.lib odbccp32.lib “tkm01s.lib”

———–

You will see my output shows “Program Files (x86)” because I’m using 64bit Windows 7 to compile the mission.  If there are any Errors listed then you mission won’t have compiled properly.  But troubleshooting those potential errors is for another post.  If you get this output without errors your ready to start getting into the basics of scripting.

I’ll be posting some basic scripting info hopefully in the near future.  Then I’ll look into posting on various topics.  I have also written another application for Mission Editing and compiling and be posting info about it.  I prefer to use it and haven’t used the Legacy Mission Editor itself in quite awhile.

The focus of this blog will be as a modding info resource for the game Star Trek Legacy by Bethesda Softworks that was released for Star Trek’s 40th Anniversary.  I plan to mostly focus on information on creation of Scripted Missions, but I’m sure I’ll be posting other bits of info on other modding subjects.

When will I get to it?  I don’t know.  How much info will be here?  I don’t know.  Guess we will wait and see how this takes off.  Good luck modding Legacy.