The three virtues of a programmer: Laziness, Impatience, and Hubris. – Larry Wall

Difference between revisions of "UE2:Using the UT2004 mod system"

From Unreal Wiki, The Unreal Engine Documentation Site
Jump to: navigation, search
(getting there slowly)
Line 14: Line 14:
 
::C:\ut2004\'''YourMod\Textures'''<br>
 
::C:\ut2004\'''YourMod\Textures'''<br>
 
::C:\ut2004\'''YourMod\Sounds'''<br>
 
::C:\ut2004\'''YourMod\Sounds'''<br>
::C:\ut2004\'''YourMod\Music'''<br><br>
+
::C:\ut2004\'''YourMod\Music'''<br>
 +
 
 +
====Running the game using YourMod====
 +
:The mod system is accessed through the use of '''-mod=''' commandline switch<br>
 +
::C:\ut2004\ut2004.exe -mod='''YourMod'''<br>
 +
::C:\ut2004\unrealed.exe -mod='''your mod'''<br>
 +
 +
{{ambox|type=notice|text=I have found that in unreal ed it does not default to '''your mod's''' directories, so keep an eye on that when saving anything from maps or packages. If there is a way to fix this please let me know.}}<br>
  
 
===Setting Up Package Folders===
 
===Setting Up Package Folders===
Line 20: Line 27:
  
 
:For Unreal Script [[Legacy:Class|Classes]] you will need to first make the [[Legacy:Package|package]]'s folder and then the [[Legacy:Class|Classes]] folder. The following eg shows the package folders being '''YourModCode''' and '''YourModGUI''':<br>
 
:For Unreal Script [[Legacy:Class|Classes]] you will need to first make the [[Legacy:Package|package]]'s folder and then the [[Legacy:Class|Classes]] folder. The following eg shows the package folders being '''YourModCode''' and '''YourModGUI''':<br>
::C:\ut2004\'''YourMod\YourModCode\'''          '''<&ndash;''' ''UnrealScript package for your mod''
+
::C:\ut2004\'''YourMod\YourPackage\'''          '''<&ndash;''' ''UnrealScript package for your mod''
::C:\ut2004\'''YourMod\YourModCode\Classes'''  '''<&ndash;''' ''put you source code here''
+
::C:\ut2004\'''YourMod\YourPackage\Classes'''  '''<&ndash;''' ''put you source code here''
::C:\ut2004\'''YourMod\YourModGUI\'''          '''<&ndash;''' ''another UnrealScript Package''
+
::C:\ut2004\'''YourMod\YourModCode\'''          '''<&ndash;''' ''another UnrealScript Package''
::C:\ut2004\'''YourMod\YourModGUI\Classes'''<br><br>
+
::C:\ut2004\'''YourMod\YourModCode\Classes'''<br>
  
 
===EXEC Directive===
 
===EXEC Directive===
 
:Using the [[Legacy:Exec_Directive|Exec Directive]] you can also import assets such as [[Legacy:Sounds|sounds]] and [[Legacy:Texture|textures]] into a package file. You do this using both the [[Legacy:Exec_Directive|Exec Directive]] and the appropriate directories.<br>
 
:Using the [[Legacy:Exec_Directive|Exec Directive]] you can also import assets such as [[Legacy:Sounds|sounds]] and [[Legacy:Texture|textures]] into a package file. You do this using both the [[Legacy:Exec_Directive|Exec Directive]] and the appropriate directories.<br>
 
::C:\ut2004\'''YourMod\YourModCode\Sounds'''  <&ndash; put the sounds you wish to import into the package here <br>
 
::C:\ut2004\'''YourMod\YourModCode\Sounds'''  <&ndash; put the sounds you wish to import into the package here <br>
::C:\ut2004\'''YourMod\YourModCode\Textures'''  <&ndash; put the textures you wish to import into the package here <br><br>
+
::C:\ut2004\'''YourMod\YourModCode\Textures'''  <&ndash; put the textures you wish to import into the package here <br>
 +
 
 +
{{ambox|type=notice|text=When working with large amounts of assets it might be alittle overwhelming to do this by hand through unrealed. Now alot of the time unrealed will let you import multiple files at once but sometimes it is much easier done on the command line. It free's up valuable memory that can be used to get the process done quicker without the overhead of the full editor open.}}
  
 
===INI Files===
 
===INI Files===
:*[[Legacy:UT2k4Mod.Ini|UT2k4Mod.Ini]] - We start to get into how to setup '''your mod''' to be accessed from the community panel in [[Legacy:UT2004|UT2004]].
+
:[[Legacy:UT2k4Mod.Ini|UT2k4Mod.Ini]] - We start to get into how to setup '''your mod''' to be accessed from the community panel in [[Legacy:UT2004|UT2004]].
:*[[Legacy:UT2k4 Default.Ini|UT2k4 Default.Ini]] - This will show you how to setup '''your mod's default.ini''' file so you can use it to compile. <br><br>
+
:This file should be place in the following directory:<br>
 +
::C:\ut2004\'''YourMod'''
 +
:[[Legacy:UT2k4 Default.Ini|UT2k4 Default.Ini]] - This will show you how to setup '''your mod's default.ini''' file so you can use it to compile.
 +
:This file should be place in the following directory:<br>
 +
::C:\ut2004\'''YourMod\System'''<br>
  
 
===LOG Files===
 
===LOG Files===
Line 42: Line 55:
 
:All other secondary log files (such as ucc.log) will still be created in:<br>
 
:All other secondary log files (such as ucc.log) will still be created in:<br>
 
::C:\ut2004\System<br>
 
::C:\ut2004\System<br>
 
===Running the game with the mod system===
 
:The mod system is accessed through the use of '''-mod=''' commandline switch<br>
 
::C:\ut2004\ut2004.exe -mod='''your mod'''<br>
 
::C:\ut2004\ucc.exe -mod='''your mod'''<br>
 
::C:\ut2004\unrealed.exe -mod='''your mod'''<br>
 
 
{{ambox|type=notice|text=I have found that in unreal ed it does not default to '''your mod's''' directories, so keep an eye on that when saving anything from maps or packages. If there is a way to fix this please let me know.}}<br><br>
 
  
 
==Commandlet's==
 
==Commandlet's==
:*[[Legacy:Commandlet|Commandlet]]s can be very useful to UScripters, providing automated tasks so you dont have to repetativly do things by hand,
+
[[Legacy:Commandlet|Commandlet]]s can be very useful to UScripters, providing automated tasks so you dont have to repetativly do things by hand.
  
{{ambox|type=notice|text=Starting with the latest patch, UT2004 can correctly locate and use .int and .ucl files stored in your mod's System directory (or in the case of .ucl whichever directory is specified by the CacheRecordPath array). But, it does require some work on your part.}}<br><br>
+
{{ambox|type=notice|text=Starting with the latest patch, UT2004 can correctly locate and use .int and .ucl files stored in your mod's System directory (or in the case of .ucl whichever directory is specified by the CacheRecordPath array). But, it does require some work on your part.}}
  
 
===Make===
 
===Make===
:*[[Legacy:Compiling_With_UCC|Compiling With UCC]] - Lastly to round things off we take a look at how to compile using '''ucc.exe'''
+
:[[Legacy:Compiling_With_UCC|Compiling With UCC]] - Lastly to round things off we take a look at how to compile using '''ucc.exe'''
  
{{ambox|type=notice|text=The mod system is accessed through the use of '''-mod=''' commandline switch
+
====Compiling YourMod====
C:\ut2004\ucc.exe ''make'' -mod='''your mod'''}}
+
:The mod system is accessed through the use of '''-mod=''' commandline switch<br>
 +
::C:\ut2004\ucc.exe ''make'' -mod='''YourMod'''
 +
:This will Compile all *.UC files found in your Package directories to:
 +
::C:\ut2004\'''YourMod\System'''<br>
  
 
===DumpInt===
 
===DumpInt===
:[[Legacy:INT_File|INT Files]] are used for [[Legacy:Localization|Localization]], '''INT''' being an acronym for international english.  
+
:[[Legacy:DumpIntCommandlet|DumpIntCommandlet]] - will always create the new .int files in the game's System directory. This is an unfortunate outcome, but changing it would have proven difficult at this time.  
  
:[[Legacy:DumpIntCommandlet|DumpIntCommandlet]] - will always create the new .int files in the game's System directory. This is an unfortunate outcome, but changing it would have proven difficult at this time.<br><br>  
+
:[[Legacy:INT_File|INT Files]] are used for [[Legacy:Localization|Localization]], '''INT''' being an acronym for international english.<br>
 +
 
 +
====Dumping Int's for YourMod's Packages====
 +
:The mod system is accessed through the use of '''-mod=''' commandline switch<br>
 +
::C:\ut2004\ucc.exe ''dumpint'' -mod='''YourMod''' C:\ut2004\'''YourMod\System\YourPackage.u'''
 +
::C:\ut2004\ucc.exe ''dumpint'' -mod='''YourMod''' C:\ut2004\'''YourMod\System\YourModCode.u'''<br>
  
 
===ExportCache===
 
===ExportCache===
The Export Cache [[Legacy:Commandlet|commandlet]] is one example of this. These can also be used to provide language support for various nations.
+
:The Export Cache [[Legacy:Commandlet|commandlet]] is one example of this. These can also be used to provide language support for various nations.
  
:*[[Legacy:ExportCacheCommandlet|ExportCacheCommandlet]] - will create the .ucl files in the first directory found in the CacheRecordPath array. Using the trick above, you can force it to use your directory, but that’s un supported. As a general rule, you will have to hand copy these files in to their proper place. Sorry.<br><br>  
+
:[[Legacy:ExportCacheCommandlet|ExportCacheCommandlet]] - will create the .ucl files in the first directory found in the CacheRecordPath array. Using the trick above, you can force it to use your directory, but that’s un supported. As a general rule, you will have to hand copy these files in to their proper place. Sorry.
 +
 
 +
====Exporting Cache for YourMod's Packages====
 +
:The mod system is accessed through the use of '''-mod=''' commandline switch<br>
 +
::C:\ut2004\ucc.exe ''exportcache'' -v -mod='''YourMod''' C:\ut2004\'''YourMod\System\YourPackage.u'''
 +
::C:\ut2004\ucc.exe ''exportcache'' -v -mod='''YourMod''' C:\ut2004\'''YourMod\System\YourModCode.u'''<br><br>
  
 
==Custom Characters==
 
==Custom Characters==
Line 90: Line 108:
 
:*[[Legacy:UPL_File|UPL_File]]
 
:*[[Legacy:UPL_File|UPL_File]]
 
:*[[Legacy:Defining_SpeciesTypes|Defining_SpeciesTypes]]<br><br>
 
:*[[Legacy:Defining_SpeciesTypes|Defining_SpeciesTypes]]<br><br>
 
==Advanced Importing==
 
 
[[Legacy:Exec_Directive|Exec_Directive]]
 
When working with large amounts of assets it might be alittle overwhelming to do this by hand through unrealed. Now alot of the time unrealed will let you import multiple files at once but sometimes it is much easier done on the command line. It free's up valuable memory that can be used to get the process done quicker without the overhead of the full editor open.<br><br>
 
  
 
==See Also==
 
==See Also==
Line 102: Line 115:
 
:*[[Legacy:Mod_Authoring|Mod Authoring]]
 
:*[[Legacy:Mod_Authoring|Mod Authoring]]
  
[[Category:Programming_tutorials]]
+
[[Category:Legacy_Tutorial]]

Revision as of 19:58, 27 April 2008

These basic procedures will show you how the unreal engine works with directories and how to setup your modification so it will use the mod system. This will keep your modification seperate to UT2004 and allow you to work with greater ease and effiency on bigger mods. Personally I always use this as it keeps my base directory free from clutter although if you are working on something smaller like a mutator or gametype you may not need to use this. The best use for this is in total conversion situations where you modification will take up alot of room and have many package's.

Basic Setup

For all of the following we will assume your Base Directory is C:\ut2004\

Mod System Directory Structure

Engine_Directory_Structure - First we'll start with a rundown of the unreal engines directory structure.
your mod being the name of the modification, your mods directory structure would look like this:
C:\ut2004\YourMod\
C:\ut2004\YourMod\System
C:\ut2004\YourMod\Help
C:\ut2004\YourMod\Maps
C:\ut2004\YourMod\Textures
C:\ut2004\YourMod\Sounds
C:\ut2004\YourMod\Music

Running the game using YourMod

The mod system is accessed through the use of -mod= commandline switch
C:\ut2004\ut2004.exe -mod=YourMod
C:\ut2004\unrealed.exe -mod=your mod


Setting Up Package Folders

Set Up Package Folders - Then we examine how to setup package's so you can compile.
For Unreal Script Classes you will need to first make the package's folder and then the Classes folder. The following eg shows the package folders being YourModCode and YourModGUI:
C:\ut2004\YourMod\YourPackage\ <– UnrealScript package for your mod
C:\ut2004\YourMod\YourPackage\Classes <– put you source code here
C:\ut2004\YourMod\YourModCode\ <– another UnrealScript Package
C:\ut2004\YourMod\YourModCode\Classes

EXEC Directive

Using the Exec Directive you can also import assets such as sounds and textures into a package file. You do this using both the Exec Directive and the appropriate directories.
C:\ut2004\YourMod\YourModCode\Sounds <– put the sounds you wish to import into the package here
C:\ut2004\YourMod\YourModCode\Textures <– put the textures you wish to import into the package here

INI Files

UT2k4Mod.Ini - We start to get into how to setup your mod to be accessed from the community panel in UT2004.
This file should be place in the following directory:
C:\ut2004\YourMod
UT2k4 Default.Ini - This will show you how to setup your mod's default.ini file so you can use it to compile.
This file should be place in the following directory:
C:\ut2004\YourMod\System

LOG Files

Log Warnings
Log File
When running with the -mod= commandline switch .log files will be place in the following directory:
C:\ut2004\YourMod\System
All other secondary log files (such as ucc.log) will still be created in:
C:\ut2004\System

Commandlet's

Commandlets can be very useful to UScripters, providing automated tasks so you dont have to repetativly do things by hand.

Make

Compiling With UCC - Lastly to round things off we take a look at how to compile using ucc.exe

Compiling YourMod

The mod system is accessed through the use of -mod= commandline switch
C:\ut2004\ucc.exe make -mod=YourMod
This will Compile all *.UC files found in your Package directories to:
C:\ut2004\YourMod\System

DumpInt

DumpIntCommandlet - will always create the new .int files in the game's System directory. This is an unfortunate outcome, but changing it would have proven difficult at this time.
INT Files are used for Localization, INT being an acronym for international english.

Dumping Int's for YourMod's Packages

The mod system is accessed through the use of -mod= commandline switch
C:\ut2004\ucc.exe dumpint -mod=YourMod C:\ut2004\YourMod\System\YourPackage.u
C:\ut2004\ucc.exe dumpint -mod=YourMod C:\ut2004\YourMod\System\YourModCode.u

ExportCache

The Export Cache commandlet is one example of this. These can also be used to provide language support for various nations.
ExportCacheCommandlet - will create the .ucl files in the first directory found in the CacheRecordPath array. Using the trick above, you can force it to use your directory, but that’s un supported. As a general rule, you will have to hand copy these files in to their proper place. Sorry.

Exporting Cache for YourMod's Packages

The mod system is accessed through the use of -mod= commandline switch
C:\ut2004\ucc.exe exportcache -v -mod=YourMod C:\ut2004\YourMod\System\YourPackage.u
C:\ut2004\ucc.exe exportcache -v -mod=YourMod C:\ut2004\YourMod\System\YourModCode.u

Custom Characters

You may want to add custom characters or even custom species type to your total conversion, lucky there is a simple way to set it up. Its called the Unreal Player List.

See Also