Unreal Wiki - User contributions [en]

Legacy:UnrealEd Console

2009-07-02T15:23:32Z

GreatEmerald: /* StaticMesh Commands */

Commands for [[Legacy:UnrealEd 3|UnrealEd 3]]'s [[Legacy:Console Bar|Console Bar]]. See also [[Legacy:UnrealEd 2 Console|UnrealEd 2 Console]].

[[Image:Legacy_interface.Ed3.console.png|center|UnreaEd 3 console bar]]

The commands can be entered either upper case or lower case. The list of previously used commands (in the current session) are saved in a drop down list, that can be conveniently re-selected (Click >> Enter), so commonly used commands can be quickly re-activated. Be sure that the correct object is selected before entering command. Also, tool bar buttons can be user created for any of the commands listed here. Many of these commands are seldom used, but can be handy when making large scale systemic alterations to a level (numerous repeat operations).

Commands can be bound to [[Legacy:Custom Toolbox Buttons|Custom Toolbox Buttons]] or keys. See [[Legacy:Binding Editor Commands|binding editor commands]]. See also [[Legacy:UnrealEd Interface|UnrealEd interface]].

Look for lines in Editor.log that start with "Cmd:" to find out about more possibly interesing console commands.

==Actor Commands==
; ACTOR REPLACE : beware of this adding extra properties you don't want! See [http://forums.beyondunreal.com/showthread.php?threadid=146410 146410]

==Brush Commands ==
; BRUSH MERGEPOLYS : Merge coplanar polygons on a brush
; BRUSH SEPARATEPOLYS : Separate coplanar polygons on a brush

==Fluid Commands ==
; FLUID REBUILD : ?

==Light Commands ==
; LIGHT APPLY SELECTED= CHANGED= : Rebuild lights

==Map Commands ==
; MAP SENDTO SWAP : Swap order of TWO SELECTED brushes
; MAP SAVEPOLYS FILE= MERGE= : Seems to be exporting the polys only
; MAP CHECK : Tools -> Check Map for errors
; MAP SCALE FACTOR= ADJUSTLIGHTS= SCALESPRITES= SCALELOCATIONS= SCALECOLLISION= : Tools -> Scale Map

==Paths Commands ==
; PATHS REVIEW : Tools -> Review paths

===Select Commands ===
; ''MAP SELECT ADDS'' : selects all additive brushes in the map
; ''MAP SELECT FIRST'' : select the first created brush in the level
; ''MAP SELECT LAST'' : select the last created brush in the level
; ''MAP SELECT NONSOLIDS'' : selects all nonsolid brushes in the map
; ''MAP SELECT SEMISOLIDS'' : selects all semisolid brushes in the map
; ''MAP SELECT SUBTRACTS'' : selects all subtractive brushes in the map
; ''SELECT NONE'' : Deselect any and all selected actors (it is a common error to inadvertently select an actor when moving mouse across one of the view screens).

; ''ACTOR SELECT ALL'' : selects all brushes / actors within the map
; ''ACTOR SELECT DELETED ???'' :
; ''ACTOR SELECT INSIDE'' : selects all brushes / actors within the builder brush
; ACTOR SELECT INVERT : inverts the state of selected to unselected or vise versa
; ACTOR SELECT NONE : deselect the selected actors
; ''ACTOR SELECT OFCLASS CLASS=<CLASS>'' : selects all actors of a class
; ''ACTOR SELECT OFSUBCLASS CLASS=<CLASS>'' : selects all actors of a class or subclasses. Eg use with "TournamentWeapon" to select all weapons.

==StaticMesh Commands ==
; STATICMESH FROM SELECTION PACKAGE= NAME= GROUP= : Converts brush to static mesh
; STATICMESH TO BRUSH : Converts staticmesh to brush
; STATICMESH REBUILD : Rebuilds the Static Mesh, which is currently selected in the 3D viewport.
; STATICMESH ALLREBUILD : ?
; STATICMESH SMOOTH : Rebuilds the Static Mesh, which is currently selected in the 3D viewport, and makes it smoother. Very useful when converting [[Brush]]es to [[Static Mesh]]es.
; STATICMESH UNSMOOTH : Rebuilds the Static Mesh, which is currently selected in the 3D viewport, and makes it sharper. Useful when the Static Mesh is too smooth.
; STATICMESH SAVEBRUSHASCOLLISION: Save selected brush as collision for staticmesh

==Poly Commands==
; POLY BEVEL DEPTH= BEVEL= : Context Menu -> Bevel
; POLY EXTRUDE DEPTH= : Context Menu -> Extrude
; POLY SET SETFLAGS= : Set polyflags
; POLY SET CLEARFLAGS= : Clear polyflags
; POLY SET TEXTURE= : Set Texture

==Stat Commands==
; LSTAT : Lightmap stats
; STAT ''foo'' : display different statistics about the display, where ''foo'' is one of...
;* ALL – toggles display of all categories
;* ANIM – toggles animation statistics display
;* AUDIO – toggles audio statistics display
;* DEFAULT – Resets all displays to default visibility
;* FPS – toggles framerate statistics display
;* GAME – toggles game statistics display
;* HARDWARE – toggles hardware statistics display
;* HISTOGRAPH – toggles histograph statistics display
;* LIGHT – toggles dynamic light statistics display
;* MATINEE – toggles matinee statistics display
;* NET – toggles network statistics display
;* NONE – turns off all displays
;* RENDER – toggles rendering statistcs display
;* RESET – same as DEFAULT
;* XBOXMEM – toggles XBox memory statistics display

"POLY TEXSCALE" and "POLY TEXPAN" work. ([[Legacy:TexAlign|TexAlign]] Works in UED3 :))

==No longer works ==

Commands from UEd 2 that don't work in 3. Anyone know if there are new equivalents?

* POLY TEXINFO
* POLY TEXALIGN FLOOR and POLY TEXALIGN WALLDIR

==Related Topics ==
* [[Legacy:UnrealEd Interface|UnrealEd Interface]]

[[Category:Legacy Mapping|{{PAGENAME}}]]

User:GreatEmerald

2009-05-27T11:12:55Z

GreatEmerald: ;)

Talk:Typecasting

2009-05-27T11:11:39Z

GreatEmerald: /* Legacy */ new section

== vector->bool conversion ==

Meh, yes, that was obvious, wasn't it? Next time, comment on the talk page, please. —[[User:Wormbo|Wormbo]] 09:57, 26 December 2008 (UTC)

== Legacy ==

There's a [[Legacy:Typecasting]] and this page. Shouldn't one be changed to a redirect to another one? Probably Legacy to here? --[[User:GreatEmerald|GreatEmerald]] 11:11, 27 May 2009 (UTC)

Legacy talk:InputKeyMap

2009-02-07T20:54:50Z

GreatEmerald: Bad formatting

This page seems to have lost formatting for some reason (probably code tags or too many columns). This should be rewritten I guess. --[[User:GreatEmerald|GreatEmerald]] 20:54, 7 February 2009 (UTC)

UnrealScript

2009-01-20T17:48:42Z

GreatEmerald: 19, not 18

:''See [[UnrealScript overview]] for all Unreal Wiki topics about learning and using UnrealScript.''

'''UnrealScript''' is the [[Unreal Engine]]'s [[wp:scripting language|scripting language]]. It is a [[wp:strongly-typed|strongly-typed]], [[wp:object-oriented|object-oriented]] programming language very similar to [[wp:Java (programming language)|Java]] and [[wp:C++|C++]]. If you want to learn UnrealScript, you should make yourself familiar with the fundamental concepts of object-oriented programming. It definitely helps already to know another programming language, preferably one that is strongly-typed and object-oriented as well.

==Anatomy of an UnrealScript source file==
A typical UnrealScript source file might look similar to the following example from [[Unreal Tournament 2004|UT2004]]:
<uscript line>
class DMRosterBeatTeam extends xDMRoster;

/*
* Roster for deathmatch levels.
* Each level has its own roster.
* This special roster subclass is used to populate an enemy team with the
* player's selected teammates.
*/

// called immediately after spawning the roster class
function Initialize(int TeamBots)
{
local GameProfile GP;
local int i, j;

GP = Level.Game.CurrentGameProfile;
if ( GP == none ) {
Log("DMRosterBeatTeam::Initialized() failed. GameProfile == none.");
return;
}

// create roster entries for single player's teammates
for ( i=0; i<GP.PlayerTeam.Length; i++ )
{
j = Roster.Length;
Roster.Length = Roster.Length + 1;
Roster[j] = class'xRosterEntry'.Static.CreateRosterEntryCharacter(GP.PlayerTeam[i]);
}

// remaining team-specific info, might be used in menus at some point
TeamName = GP.TeamName;
TeamSymbolName = GP.TeamSymbolName;

super.Initialize(TeamBots);
}

defaultproperties
{
TeamName="Death Match"
TeamSymbolName="TeamSymbols_UT2003.Sym01"
}
</uscript>
As you can see, UnrealScript is a [[wp:curly brace programming language|curly brace programming language]]: blocks of code are enclosed in curly braces. Each code statement is either followed by a block or terminated by a semicolon.

* Line 1 contains the mandatory [[class declaration]]. This file contains a class with the name [[UE2:DMRosterBeatTeam (UT2004)|DMRosterBeatTeam]]. The [[extends clause]] specifies that this class [[wp:Inheritance (computer science)|inherits]] attributes, methods and other class members from a class with the name [[UE2:xDMRoster (UT2004)|xDMRoster]], which is said to be the "super class" or "parent class" of DMRosterBeatTeam.
* Lines 3 to 8 are an example for a [[Comments#Block comments|block comment]]. The important parts here are the characters <code>/*</code> on line 3 and <code>*/</code> on line 8. Everything between them is ignored by the UnrealScript compiler.
* Line 10 contains another type of comment, an end-of-line comment or just [[Comments#Line comments|line comment]]. Outside of block comments this type of comment starts with the characters <code>//</code> and continues to the end of the same line. As with block comments, everything on the line following the double slashes is ignored by the compiler.
* Line 11 contains a [[Function declarations|declaration]] for an [[instance function]]. The function's name is specified to be "Initialize" and the function has one parameter of type [[types#int|int]] called "TeamBots". The block of code on lines 12 to 35 is the function's "body". Some functions do not have a body. The declaration of those functions is terminated by a semicolon instead.
* The line 13 declares a local variable of [[Types#Object|type]] [[UE2:GameProfile (UT2004)|GameProfile]], a class defined elsewhere, and gives it the name "GP". The variable is initially empty.
* Line 16 assigns a value to the local variable "GP" so it no longer is empty. To determine the value, the function accesses the variable "Level". This variable is not declared here, but in a parent class of DMRosterBeatTeam. The object referenced by "Level" has a variable of its own, called "Game", whose contained object in turn has a variable called "CurrentGameProfile". The content of that variable is assigned to our local "GP" variable.
* On line 17 there's an [[If statement]] with a block of code that ends on line 20. That block of code is only executed if the expression in the parentheses following the keyword ''If'' returns the value ''True''. The ''If'' condition checks, whether the content of the local "GP" variable equals the special value ''None'', which simply means "empty".
* Lines 18 and 19 are only executed if the condition (here: "GP is empty") is true. So, if GP is empty, first the function with the name "Log" is called to write a message to the log file, then the [[Return statement]] exits the function. In this case the code after the ''If'' block will not be executed. In other cases the ''If'' block might not contain a ''Return'' and code execution would continue after the ''If'' block.
* On line 23 there's a typical [[For loop]] that iterates over a [[dynamic array]]. The code on lines 25 to 27 is executed for each element of the "PlayerTeam" array in the object stored in the local "GP" variable. Notice how the ''If'' statement on line 17 ensured that "GP" actually contains an object.
* Line 34 calls another version of the "Initialize" function, that was declared in a parent class of DMRosterBeatTeam, passing on the TeamBots parameter. This call tells us, that the "Initialize" function of the DMRosterBeatTeam class actually [[wp:Method overriding (programming)|overrides]] a function with the same name in its parent class xDMRoster or another parent class further up the class hierarchy.
* Lines 37 to 41 are the [[defaultproperties]] block. This block defines default values for class variables. Both "TeamName" and "TeamSymbolName" are inherited from a parent class.

{{navbox unrealscript}}

Array

2008-12-15T18:42:11Z

GreatEmerald: Fixed the link.

#REDIRECT [[Legacy:Dynamic Array]]

Legacy talk:Brush Sinking

2008-11-30T17:56:16Z

GreatEmerald:

== Flickering surfaces? ==

This method doesn't create flickering surfaces? I mean, the engine should get quite confused, there are two textures to render at the same spot. Just like with movers, you can't use this method with them. Any explanations? --GreatEmerald

:Well, brush sinking creates fixed BSP geometry, so there aren't two surfaces to display, but only one. The Unreal Engine doesn't have any flickering problems with BSP because it always displays the last brush's (as per brush order) surfaces. Mover's aren't part of the BSP tree, so the engine needs to figure out their drawing order dynamically, which causes flickering. If you look closely, you will find brush sinking in all generations of the Unreal Engine. It's even used on VCTF-Suspense in UT3! —[[User:Wormbo|Wormbo]] 11:24, 30 November 2008 (UTC)

::Interesting! But then why didn't epic sink the floor tiles on Na Pali Haven map in Unreal 1, near the gate? Instead, they used non-solid sheets that disappear after rebuilding! --[[User:GreatEmerald|GreatEmerald]] 13:12, 30 November 2008 (UTC)

::No idea. Maybe they weren't aware of this trick back when they designed the Unreal levels. There is an amazingly low number of UT maps using this as well. I've ported the [[brush sinking]] tutorial to the main name space now, btw. —[[User:Wormbo|Wormbo]] 14:39, 30 November 2008 (UTC)

:::Ooh, nice. Though some more maps could be given as examples, like DM-Gothic for UT99 or ONS-Torlan for subtractive sinking. --[[User:GreatEmerald|GreatEmerald]] 17:56, 30 November 2008 (UTC)

Legacy talk:Brush Sinking

2008-11-30T13:12:32Z

GreatEmerald:

Legacy talk:Brush Sinking

2008-11-30T13:12:02Z

GreatEmerald:

Legacy talk:Brush Sinking

2008-11-29T23:59:16Z

GreatEmerald: Flickering surfaces?

UE2:UnrealEd Tip of the Day

2008-10-18T16:39:58Z

GreatEmerald: New page: These tips were taken directly from UnrealEd's 3.0 (Unreal II build) Tip of the Day initialisation files. They all start with the words "Did you kno...

These tips were taken directly from UnrealEd's 3.0 ([[Legacy:Unreal 2|Unreal II]] build) Tip of the Day [[Legacy:INI File|initialisation files]]. They all start with the words "Did you know?".

*You can add brushes with CTRL+A and subtract them with CTRL+S?
*If you right click the "Add Mover" button you can select from a menu of mover types?
*If you right click the "Add Volume" button you can select from a menu of volume types?
*If you right click the toolbar at the top of a viewport, a menu will appear allowing you to control the appearance of that viewport?
*You can toggle the drawing of static meshes with the "W" key?
*You can toggle the drawing of actors with the "H" key?
*You can toggle the drawing of the builder brush with the "B" key?
*You should wear pants while building levels?
*You shouldn't make Shaders that reference themselves?

UE3 talk:UnrealEd Tip of the Day

2008-10-18T16:29:39Z

GreatEmerald: /* UE2 tips? */

Nice page, Wormbo. Fine job. :) --[[User:SuperApe|SuperApe]] 23:17, 29 September 2008 (UTC)

== UE2 tips? ==

What about UE2 UnrealEd tips of the day? There are a few in all UE2 games (UnrealEdTips.ini). Just that this is marked as UE3? --[[User:GreatEmerald|GreatEmerald]] 19:16, 17 October 2008 (UTC)

It's marked as UE3 because it ''is'' UE3. ;-) Just create a corresponding page for them: [[UE2:UnrealEd Tip of the Day]] — [[User:Wormbo|Wormbo]] 07:33, 18 October 2008 (UTC)

:Oh :D But then why there is a section "Unreal Tournament 3"? I mean, all UE3 editors should have the same tips? --[[User:GreatEmerald|GreatEmerald]] 16:29, 18 October 2008 (UTC)

Legacy talk:Setting Up UnrealScript

2008-10-18T16:28:17Z

GreatEmerald:

==Remake Scripting Environment section?==
The ''Choose a scripting environment'' section is quite ugly now. There are countless ways to set it up - not only 4 like it looks like now. Things like [http://unreal.student.utwente.nl/ UnCodeX online source] is a very nice alternative to actually having to get the UnCodeX program itself. [[MonkeyBuild]] could also be mentioned as a good alternative to UMake. And also it could then be converted to a usual, non-legacy page. --[[User:GreatEmerald|GreatEmerald]] 19:12, 17 October 2008 (UTC)

All the pages in the "Legacy" namespace should be remade for the regular namespaces. — [[User:Wormbo|Wormbo]] 07:34, 18 October 2008 (UTC)

:Indeed, but it's a hell loads of data that needs to be remade... And, as it's said in [[Unreal Wiki:Namespaces]], you can't just copy over stuff... So it's even more to do. Yet I could convert some if I had some free time. --[[User:GreatEmerald|GreatEmerald]] 16:28, 18 October 2008 (UTC)

UE3 talk:UnrealEd Tip of the Day

2008-10-17T19:16:41Z

GreatEmerald: /* UE2 tips? */ new section

Legacy talk:Setting Up UnrealScript

2008-10-17T19:12:40Z

GreatEmerald: New page: ==Remake Scripting Environment section?== The ''Choose a scripting environment'' section is quite ugly now. There are countless ways to set it up - not only 4 like it looks like now. Thing...

Legacy:Application

2008-10-17T19:01:40Z

GreatEmerald: /* Compilers */ Mentioned MonkeyBuild

This page lists '''applications''' which are useful for working with the [[Legacy:Unreal Engine|Unreal engine]]. Some have been designed specifically for this purpose, some we just recommend as handy to have.

This page is a forward index, split into sub-pages by type. For a flat list of all pages about applications, see [[:Category:Legacy Application]].

See also [[Legacy:Third-Party Components|Third-Party Components]] for external components that can be added to maps.

==Bundled ==

Bundled in with [[Legacy:UT2003|UT2003]]:
* [[Legacy:UnrealEd 3|UnrealEd 3]], of course (older [[Legacy:UnrealEd Versions|UnrealEd Versions]] with older games)
* [[Legacy:Maya|Maya]]
* [[Legacy:UDebugger|UDebugger]]
* [[Legacy:UPaint|UPaint]] - Make skins in 3D! Buggy though :(
* [[Legacy:Ucc|Ucc]] – Unreal's general-purpose command line application.

==Third party==
* [[Legacy:Mapping Application|Mapping Application]]
* [[Legacy:Modelling Application|Modelling Application]]
* [[Legacy:Model Conversion Application|Model Conversion Application]]
* [[Legacy:Graphics Application|Graphics Application]]
* [[Legacy:IDE|IDE]]
* [[Legacy:Text Editor|Text Editor]]
* [[Legacy:Documentation Tool|Documentation Tool]]

''suggest more grouping pages''

===Compilers ===

* [[Legacy:UMake|UMake]] – Wrapper tool for "ucc make" with a bunch of additional convenience options
* [[MonkeyBuild]] – Sequencer for "ucc make" and other UnrealScript development tasks

===Documentation ===
* [[Legacy:UClasses|UClasses]] – Stand-alone Unreal class browser.
* [[Legacy:UnCodeX|UnCodeX]] – Class browser and document generator
* [[Legacy:UnDox|UnDox]]
* [[Legacy:UnDox Revisited|UnDox Revisited]]

===Tools ===
* [[Legacy:CVS|CVS]]
* [[Legacy:Umod Wizard|umod Wizard]] – Creates UMod installers.
* [[Legacy:UnrVarpu|UnrVarpu]] – C++ class library (sources included) for decoding Unreal packages

==Text Editors ==

see [[Legacy:Text_Editor|Text_Editor]]

==Coding utilities ==

==Music utilities ==
* [[Legacy:ModPlug Tracker|ModPlug Tracker]] – Tool to edit/create Unreal's .umx files.

==Sound Editing/Recording tools ==
* [[Legacy:GoldWave|GoldWave]]

==General utilities ==
* [[Legacy:Ucc|Ucc]] – Unreal's general-purpose command line application.
* [[Legacy:Umod Wizard|umod Wizard]] – Creates UMod installers.
* [[Legacy:UMod Browser|UMod Browser]] – Extract the contents of any Unreal Modules (UMOD)
* [[Legacy:UMOD Extractor|UMOD Extractor]] – Extract the contents of a UMod.
* [[Legacy:UT Package Tool|UT Package Tool]] – Examine and decompile the contents of a UT package.
* [[Legacy:UT2Kx Regcheck|UT2Kx Regcheck]] – Add and manage your UT2k3 win-registry-keys
* [[Legacy:Unreal Tournament 3 Tweaker|Unreal Tournament 3 Tweaker]]

==Wheeee! ==
* [[Legacy:Capturing Unreal Video|Capturing Unreal video]]

See http://w3.one.net/~darkon/cgi-bin/shire-wiki.cgi?UnrealTournament for a perl script that synchronizes map lists.

==Comments==

===This index===

It's got to the point where we have SO MANY pages for apps on this wiki. There's official stuff like UPaint, homemade like Umake and UnCodeX, stuff that's not really Unreal related but that we recommend as useful... basically, this [[MeatBall:ForwardIndex]] is becoming too hard to maintain; and it's getting too long to digest. So maybe we should switch to a reverse index and create [[:Category:Legacy Application]]. Keep forward indexes for specific areas, such as [[Legacy:Texture Editing Program|Texture Editing Program]], or [[Legacy:UnrealScript Editors|UnrealScript Editors]]. Any thoughts on this?

Mych: [[Legacy:Application|Application]] might have subpages, for that matter.

'''Tarquin:''' here's my plan:

====1. type pages====

Specialized forward indexes for different types of app, such as
* [[Legacy:Texture Editing Program|Texture editing program]]
* [[Legacy:IDE|IDE]]
* [[Legacy:Text Editor|Text Editor]]
* [[Legacy:Model Editor|Model editor]]

... and so on. These names can be easily back-linked from pages for specific apps:

: foo is an [[Legacy:IDE|IDE]] bla bla bla

====2 parent page====

This page remains a parent page that leads to the above type pages. any apps that don't get listed on a type page stay here.

====3 reverse index====

Use [[:Category:Legacy Application]] so we can generate a flat list of all applications discussed on the wiki

How does that sound?

'''Tarquin:''' no opinions? I'll take that as a unanimous yes then

'''Wormbo:''' Sounds good to me, so if you need an explicit "yes", you got mine. :)

'''Ch3z:''' Those Type Pages maybe need a sufix like, "TextureEdit_Apps", "IDE_Apps", "TextEdit_Apps", "ModelEdit_Apps", "ModelConvert_Apps"? Or maybe a prefix?

'''Bob_The_Beheader:''' I've noticed when adding a program to the [[Legacy:Graphics_Application|Graphics_Application]] page, some of the programs already listed don't have there own page, and therefore can't be listed on the [[Legacy:Category_Application|Category_Application]] page. Should seperate pages be made for these apps, or are users expected to follow the link to the [[Legacy:Application|Application]] page?

'''Tarquin:''' Depends if there's anything interesting to say about the app. is [[Legacy:Application|Application]] not prominent enough?

'''Bob_The_Beheader:''' Tarquin is what ive just done with adding the link to the Text Editor page what you are talking about for Type Pages in step one?

Legacy:Compiling With UCC

2008-10-17T18:59:18Z

GreatEmerald: Mentioned MonkeyBuild

'''UCC''' is the [[Legacy:UnrealScript|UnrealScript]] compiler. This page explains how to compile with the '''ucc make''' command. As an alternative, you may want to consider using tools like [[Legacy:UMake|UMake]] or [[MonkeyBuild]], which makes the whole thing much simpler. If you are a cygwin geek, you might like use [[Legacy:GnuMake|GnuMake]].

==Compiling==

So, you've spent some time lovingly crafting your mod using well laid out, commented, and maintainable Unreal Script. You have done the decent thing and placed your .uc class files in /UnrealTournament/YourModPackage/Classes. The big moment approaches - will it compile first time?

Well, there's only one way to find out, and that's to do it. At the very least you need to edit your [[Legacy:Game Ini File|Game Ini File]] and add your package name to the list of editable packages. Search the ini file for a list of lines starting with EditPackages. Add your package to the bottom of the list like so:

EditPackages=YourModPackage

Save the changes. You will now be able to compile your mod using the following command:

ucc make

By default this command examines all of the EditPackages lines searching for packages which have no corresponding .u (a compiled package file) files and attempts to compile them. If you have previously built YourModPackage and you have updated the code the build command will not recompile your package unless your first delete it. It's well worth creating a small batch file to do this for you, e.g.

cd C:\UnrealTournament\System
del YourModPackage.u
ucc make

One of the things that's really easy to forget is the [[Legacy:INT File|INT file]] associated with your new package. This file defines the public classes in the package. Look in any of the [[Legacy:INT File|INT file]]s for examples of this. Remember to include the ''[Public]'' directive at the top of the file though or your mod won't be visible in the UT front end. It's worth keeping a copy of your [[Legacy:INT File|INT file]] in the /UnrealTournament/YourModPackage directory so you don't lose it and always have an up to date version.

==Tips==

To reduce compile time, create the following:
* An ini file, named for example MyProject.ini. Copy UnrealTournament.ini or UT2003.ini and only include those EditPackages entries that your classes depend on.

* Make a batch file that reads: <tt>ucc make ini=MyProject.ini</tt>

Note that to see output you'll still have to run it from the command prompt. ([[Legacy:UMake|UMake]] does all that automatically for you and stores an .ini file called make.ini in your project directory.)

===Batch File===

When I still used UCC Make I made a batch file that looked like this:
COPY MyMod.U *.U_Backup
DEL MyMod.U
UCC MAKE
PAUSE

This backs up your U file, deletes it, recompiles it, and then PAUSE, "press any key to continue". This combined with the INI said above here could make a very nice way to compile.

===Mod System Batch File for ut2k4===

Last Updated: 15 January 2006

Easy to adjust to any mod just input the unreal tournament 2004 directory, the mod name and the package and your off.

If you want to add extra packages just copy the lines containing %package1% or package1 and replace them with %package2% or package2.

<uscript>
:init
@echo Off
set utk4dir="Your Unreal 2k4 Dir"
set utk4sysdir=%utk4dir%system\

set modname="Your Mod Name"
set moddir=%utk4dir%%modname%
set modbakdir=%moddir%SysBak\
set modlogdir=%moddir%System\logs\

set package1="Your Package Here"
goto bak

:bak
md %modbakdir%
md %modlogdir%
copy %moddir%*.ucl %modbakdir%*.ucl
copy %moddir%*.int %modbakdir%*.int
copy %moddir%*.u %modbakdir%*.u
echo //-----------------------Old Files Backed Up!------------------------
goto del

:del
del /q %utk4sysdir%%Package1%.* > nul
del /q %moddir%%Package1%.* > nul
echo //-----------------------Echo Old Files Deleted!----------------------
goto make

:make
%utk4dir%UCC.exe make -mod=%modname%
copy %utk4dir%ucc.log %modlogdir%%modname%_ucc.log
echo //---------------------------*.u Complete!----------------------------
goto make&int

:make&int
%utk4Dir%UCC.exe dumpint -mod=%modname% %moddir%%package1%.u
copy %utk4sysdir%ucc.log %modlogdir%%modname%_int.log
copy %utk4sysdir%%package1%.int %moddir%%package1%.int
del %utk4sysdir%%package1%.int
del %utk4sysdir%ucc.log
echo //--------------------------*.int Complete!---------------------------
goto make&ucl

:make&ucl
%utk4Dir%UCC.exe exportcache -v -mod=%modname% %moddir%%Package1%.u
copy %utk4sysdir%ucc.log %modlogdir%%modname%_ucl.log
del %utk4sysdir%ucc.log
echo //--------------------------*.ucl Complete!---------------------------
goto end

:end
echo //--------------------------Make Complete!---------------------------
</uscript>

===Another ucc batch file===

Displays time and result of last compilation, updates window title, restarts with single key press.

<uscript>
@echo off
:start
title COMPILING :: MyProject
CLS

Copy UCC_MyProject.log UCC_MyProject_OLD.log

del MyProject.u

ucc make -INI=MyProject.ini -LOG=UCC_MyProject.log
if errorlevel 1 goto end

title OK :: MyProject
findstr /c:"Log file closed" UCC_MyProject.log

echo.
pause
goto start

:end
title ERROR :: MyProject
findstr /c:"Log file closed" UCC_MyProject.log

echo.
pause
goto start
</uscript>

==Related Topics==
* [[Legacy:Setting Up UnrealScript|Setting Up UnrealScript]]
* [[Legacy:Compiler Errors|Compiler Errors]]
* [[Legacy:UMake|UMake]] – convenient "ucc make" wrapper tool.
* [[MonkeyBuild]] – another tool for easier script compiling
* [[Legacy:Set Up Package Folders|Set Up Package Folders]]
* [[Legacy:UT2k4 Default.Ini|UT2k4 Default.ini]] – Using Default.ini to Compile with mod Support.
* [[Legacy:Commandlet|Commandlet]]

==Discussion==

'''Xaklse:''' Very useful, thanks! But I had many problems with your first batch example. In case anyone has problems with it, here goes my batch file. Mine includes a custom key binding and exports cache to a single file.

<uscript>
:init
@echo Off
set utk4dir=C:\UT2004\
set utk4sysdir=%utk4dir%System\

set modname=AshuraDarkReign
set moddir=%utk4dir%%modname%\
set modsysdir=%moddir%System\
set modbakdir=%moddir%SYSBAK\

set package1=AshuraDarkReign
set package2=ADRGame
set package3=ADRMonsters
goto bak

:bak
md %modbakdir%
copy %modsysdir%*.ucl %modbakdir%*.ucl
copy %modsysdir%*.int %modbakdir%*.int
copy %modsysdir%*.u %modbakdir%*.u
echo //------------------------Old Files Backed Up!------------------------
goto del

:del
del /q %modsysdir%%package1%.* > nul
del /q %modsysdir%%package2%.* > nul
del /q %modsysdir%%package3%.* > nul
echo //-------------------------Old Files Deleted!-------------------------
goto make

:make
%utk4sysdir%UCC.exe make -mod=%modname%
copy %utk4sysdir%ucc.log %modbakdir%%modname%_ucc.log
echo //---------------------------*.u Complete!----------------------------
goto make&int

:make&int
%utk4sysdir%UCC.exe dumpint -mod=%modname% %modsysdir%%package1%.u
%utk4sysdir%UCC.exe dumpint -mod=%modname% %modsysdir%%package2%.u
%utk4sysdir%UCC.exe dumpint -mod=%modname% %modsysdir%%package3%.u
copy %utk4sysdir%ucc.log %modbakdir%%modname%_int.log
copy %utk4sysdir%%package1%.int %modsysdir%%package1%.int
copy %utk4sysdir%%package2%.int %modsysdir%%package2%.int
copy %utk4sysdir%%package3%.int %modsysdir%%package3%.int
del %utk4sysdir%%package1%.int
del %utk4sysdir%%package2%.int
del %utk4sysdir%%package3%.int
del %utk4sysdir%ucc.log
echo [Public]>>%modsysdir%%package1%.int
echo Object=(Class=Class,MetaClass=XInterface.GUIUserKeyBinding,Name=AshuraDarkReign.ADRKeyBindings)>>%modsysdir%%package1%.int
echo //--------------------------*.int Complete!---------------------------
goto make&ucl

:make&ucl
%utk4sysdir%UCC.exe exportcache -a -mod=%modname% %package1%.u %package1%.ucl
%utk4sysdir%UCC.exe exportcache -a -mod=%modname% %package2%.u %package1%.ucl
%utk4sysdir%UCC.exe exportcache -a -mod=%modname% %package3%.u %package1%.ucl
echo //--------------------------*.ucl Complete!---------------------------
goto end

:end
copy %utk4sysdir%ucc.log %modbakdir%%modname%_ucl.log
del %utk4sysdir%ucc.log
echo //-----------------------COMPILATION COMPLETED!-----------------------
pause
</uscript>

[[:Category:Legacy Tutorial]]

[[Legacy:Caetgory Toolchain|Caetgory Toolchain]]
[[Category:Legacy Tutorial|{{PAGENAME}}]]

Legacy:Ucc

2008-10-17T18:56:55Z

GreatEmerald: Mentioned MonkeyBuild

'''UCC''' stands for Unreal Commandline Client or something like that. This is the console application that compiles .uc [[Legacy:UnrealScript|UnrealScript]] files into .u [[Legacy:Package|package]]s.

You can use it "by hand" in a windows console / DOS box, but it's not terribly user-friendly. We recommend you use one of these tools instead:

* [[Legacy:UMake|UMake]]
* [[MonkeyBuild]]
* The multi-purpose [[Legacy:UClasses|UClasses]]
* Write batch files (.bat) for running UCC.

==ucc under Linux ==

The Linux version of [[Legacy:UT2003|UT2003]] comes with an executable called ucc, but it's missing the make functionality and a lot of other bits which make the Windows version so useful for developers. Under Linux, it's just the server executable. So what if you want to develop UnrealScript under Linux? Well, if you have a Windows install of UT2003 available, it's simple... just run it under WineX. Make sure your WineX drive configuration matches that which your Windows install of UT2003 is expecting, and it should work just fine. This is not the place to tell you how to configure WineX, check its documentation for that. Nothing non-standard is required, however.

Ok, just to clarify, when I say "WineHQ", I mean the version of Wine available from http://www.winehq.com/ (as opposed to WineX, from http://www.transgaming.com).

UT2003 for Windows installs under either WineHQ or WineX, although with WineX it crashed near the end for me when it tried to update DirectX without asking me first. UCC runs fine under WineX, either the Transgaming binary or one built from their CVS source. WineHQ doesn't work well with UCC, make seems to hang indefinitely, but not at the same place every time (sometimes it will even complete successfully). If you use WineX to play games, you may want to use WineHQ to install UT2003, or back up the registry and system files from your WineX installation, because UT2003 tries to install DirectX without prompting first (at least, this is what happened to me). UT2003 itself doesn't seem to rely on anything in the registry, it just need the files in place, so if you use WineHQ just to install it, you can then safely move the UT2003 directory elsewhere. I symlinked mine from my .wine directory to my home directory, and that seems to work fine, too. Also, I've had trouble with updates via WineHQ or WineX - the last one, 2186, seemed to install fine, but didn't actually install the files. It looks like for this one, at least, you can unzip the .exe file and install the unpacked files over your existing UT2003 directory - this is what I had to do before I could compile a mutator that uses the GUIUserKeyBinding class. Also, if you have UT2003 for linux installed on the same machine, you can make the files that are the same in both hardlinks from your Wine UT2003 directory to to linux one - use cmp or md5sum to find the identical files. This can save you almost all of the space wasted by two UT2003 installs, since almost all of it is the same, except for the executables and a few other files which use very little space. If I didn't put you to sleep, go enjoy building your mods under Linux. :-)

==Related Topics ==
* [[Legacy:Compiling With UCC|Compiling with UCC]]
* [[Legacy:Running A Dedicated Server With UCC|Running a Dedicated Server with UCC]]
* UCC [[Legacy:Commandlet|Commandlet]]s
* [[Legacy:Setting Up UnrealScript|Setting Up UnrealScript]] – compiling basics

==Discussion==

'''Trystan:''' I need to install RedHat on my box again. What exactly comprises ucc? Is it possible to bundle up the required ucc files and make them available to folks who want to work under Linux? Would Epic permit this? It's got to be a great deal smaller than installing all of UT2003 on a Windows partition. I think I'm going to go install RedHat and find out..

'''Wormbo:''' Commandlets like MakeCommandlet or [[Legacy:BatchExportCommandlet|BatchExportCommandlet]] are components of UnrealEd and stored in .dll files. I highly doubt that Linux folks can use them.

'''El Muerte TDS:''' well the only difficult part in porting the any editor stuff is UnrealEd itself (because of the MFC), I don't ''think'' the make and export commandlets would be that difficult.

'''Mychaeel:''' I found even porting a C++ program from gcc to MSVC++ to be a non-trivial task. I could imagine that doing it the other way around isn't much less of a hassle...

'''Trystan:''' I was more concerned with the possibility of taking Win32 ucc, all the related and necessary files, putting them in a tar/gzipped file and allowing them to be downloaded separately from anything else. The basic thought being that this would free a Linux developer from having a Windows partition solely for UT2K3 development. We would need Epic's permission to make those files available. That ucc would still require Wine/WineX but most Linux distributions have associated Win32 executables with the Wine executable anyway.

'''El Muerte TDS:''' Ryan Gordon replied to my email, here's what he had to say: ''ucc make is broken at the moment, the rest is untested, and it adds 15 minutes to the build time to include it. It should be there in the future, but it's low priority.''

'''MeltDown:''' Take a look at PyUClasses at http://www.unrealtower.org/downloads/26. It can use Wine and ucc.exe to compile mods for UT. See http://www.unrealtower.org/documentation/pyuclasses/ for more information.

'''Conzar:''' Any status on the windows files to be packaged up? I copied all the .dlls and .exe files in System from the UT2K4 dvd into my System directory and have some compile errors while using ucc.exe.
cedega UCC.exe make

Can't find 'intAActorexecAddToPackageMap' in 'Engine.dll'

History: UPackage::GetDllExport <- UFunction::Bind <- UField::PostLoad <- UStruct::PostLoad <- UFunction::PostLoad <- UObject::ConditionalPostLoad <- (Function Engine.Actor.AddToPackageMap) <- PostLoadObjects <- UObject::EndLoad <- UObject::StaticLoadObject <- (Core.Class Editor.EditorEngine NULL) <- UEngine::Init <- UEditorEngine::InitEditor <- UMakeCommandlet::Main

'''Wormbo:''' Never copy only .DLLs or only .Us, they only work if the same versions are used.

'''DarthDevilous:''' Why is there a ''UCC for Linux'' bit here as well as [[Legacy:Using_UCC_Under_Linux|here]]?

'''Tarquin:''' No idea. someone should merge them.

'''EricBlade:''' Anyone have any specific knowledge on using "ucc master" to create an install program? There are docs on UDN, but they don't seem too helpful if you don't already know what you're doing with it.

[[Category:Legacy Application|{{PAGENAME}}]]

MonkeyBuild

2008-10-17T18:55:14Z

GreatEmerald: New page: '''MonkeyBuild''' is a free tool for UnrealScript developers that simplifies compilation, testing and publishing (publishing only in Unreal Engine 3). It works i...

'''MonkeyBuild''' is a free tool for UnrealScript developers that simplifies compilation, testing and publishing (publishing only in [[Legacy:Unreal_Engine_3|Unreal Engine 3]]). It works in all versions of the Unreal Engine and with most games (even those which are not from the Unreal series).

This tool is a sequencer, which can create and save sequence scripts that can be later executed in a single click. Although it's primary use is UnrealScript compilation ([[Legacy:Ucc|UCC]] make without the need of a batch file or command prompt), MonkeyBuild can do a lot more - like, automatically delete or back up old files, run the game with the mutator on for testing and open the log afterwards; it can also do even UnrealScript unrelated tasks, such as moving files and opening programs. It can also cook projects in [[Unreal Tournament 3]].

The program already comes with a set of example scripts to help you get started and automatically tries to detect any Unreal Engine games installed on the computer.

Created by Free Monkey Interactive.

:[http://free-monkey.com/main/monkeybuild.php Download the latest MonkeyBuild version here.]

==Functions==
These are the types of sequences that can be used in MonkneyBuild:

*Execute - runs any program you specify with any arguments you want. MonkeyBuild can wait until the program ends before continuing with the sequence.
*Wait - adds a delay of the specified length.
*Delete File(s) - deletes a specified file or a group of files (using wildcards).
*Copy File(s) - copies a specified file or a group of files to a specified destination.
*Move File(s) - moves a specified file or a group of files to a specified destination.
*Compile Scripts (MAKE) - Compiles scripts using the UCC Make command. Additional arguments can be added.
*Conform Packages - Runs a "conform" command to make one UnrealScript package network compatible with an older version of the same package. Note that MonkeyBuild will halt sequences if this command is not successful (for example, if one of the files cannot be found).
*Cook Packages (UE3 only) - Cooks Unreal Engine 3 packages to optimize them and allow them to be played on a console.
*Run Game - Runs the executable for the selected game. MonkeyBuild will wait until you exit the game before performing any more commands.
*Run Server - Runs a server for the selected game. Can be used to [[Legacy:Launch_A_Local_Netgame|launch local netgames]].

Legacy:ZoneInfo

2008-09-15T18:07:26Z

GreatEmerald: Really only with EAX

{{classbox| [[Legacy:UT2004|UT2004]] :: [[Legacy:Actor|Actor]] >> [[Legacy:Info|Info]] >> ZoneInfo (Package: Engine)}}

The built-in Unreal class for defining properties of [[Legacy:Zone|zone]]s. If you place one ZoneInfo actor in a zone you have partioned, the ZoneInfo defines the properties of the zone. Zones without a ZoneInfo actor take their properties from the [[Legacy:LevelInfo|LevelInfo]] actor.

This may seem obvious, but after adding a new ZoneInfo actor, the map geometry must be rebuilt for that actor's properties (e.g. ZoneLight) to take effect. Aftwards, you can change the ZoneInfo properties without rebuilding.

See [[Legacy:Zoning|zoning]] for more on working with zones, and [[Legacy:Map Optimization|Map Optimization]] in general, and [[Legacy:ZoneInfo (UT)|ZoneInfo (UT)]] for the UT version of this class.

==Properties==

===ZoneInfo Group ===
; bool bClearToFogColor : Clear to fog color if distance fog is enabled. Use this to prevent HOM effects in the distance fog. Disable this if your distance fog end is never seen
; bool bDistanceFog : There is distance fog in this zone. See [[Legacy:Distance Fog|Distance Fog]].
; bool bSoftKillZ : 2000 units of grace for KillZ unless land.
; bool bTerrainZone : There is terrain in this zone.
; float KillZ : Any actor falling below this height falls out of the world. For [[Legacy:Pawn|Pawn]]s this means they die, other actors usually get destroyed. The [[Legacy:LevelInfo|LevelInfo]]'s KillZ shows as a red line in side-view orthogonal [[Legacy:UnrealEd Viewport|UnrealEd Viewport]]s.
; eKillZType KillZType : Specifies the type of KillZ effect to apply.
; string LocationName (localized) : A description of this zone. This is what appears on the scoreboard in team games as the location of players. You can use [[Legacy:Volume|Volume]]s to create descriptions for a part of a zone.
; name ZoneTag : Used only in combination with a [[Legacy:ZoneTrigger|ZoneTrigger]]. All other actors and engine features use the Tag.

===ZoneLight Group ===

See [[Legacy:Zonelight|Zonelight]] for more on this.
; byte AmbientBrightness :
; byte AmbientHue :
; byte AmbientSaturation :
; float DistanceFogBlendTime :
; color DistanceFogColor : The color of the Distance Fog.
; float DistanceFogEnd : The distance from the player in which the distance fog completly obscures the world.
; float DistanceFogStart : The distance from the player in wich the distance fog starts to obscure the world.
; [[Legacy:Texture|Texture]] EnvironmentMap :
; float TexUPanSpeed :
; float TexVPanSpeed :

===ZoneSound Group ===
; [[Legacy:I3DL2Listener|I3DL2Listener]] ZoneEffect ([[Legacy:Editinline|editinline]]) : Environmental sound settings used in this zone. This will only have an effect if the game uses 3D hardware audio with EAX.

===ZoneVisibility Group ===
; bool bLonelyZone : This zone is the only one rendered when viewing from inside this zone. This zone is never rendered if viewing from another zone. This also includes skyboxes, so an outdoor level with only one zone plus a skybox should ''not'' use this.
; array<[[Legacy:ZoneInfo|ZoneInfo]]> ManualExcludes ([[Legacy:Editinline|editinline]]) : Used for manually specifying zones that are never visible from this zone. This is highly useful for framerate optimization if there are zones in your map that in theory need to be rendered, but are practically not visible from any point of this zone.

===UnrealScript-Only Properties ===
; vector AmbientVector :
; [[Legacy:SkyZoneInfo|SkyZoneInfo]] SkyZone : Optional sky zone containing this zone's sky.
; array<[[Legacy:TerrainInfo|TerrainInfo]]> Terrains (const) :

==Methods ==

===Iterator Functions ===
; ZoneActors (class<[[Legacy:Actor|Actor]]> BaseClass, out [[Legacy:Actor|Actor]] Actor) : Iterates through all actors in this zone.

===Other Functions===
; LinkToSkybox ( ) [simulated] : This function is called from <tt>PreBeginPlay</tt> and initialises the link to the Sky Zone for this zone. The [[Legacy:SkyZoneInfo|SkyZoneInfo]] object linked to is determined by the detail settings on the client machine (if there is more than one).
; ActorEntered ([[Legacy:Actor|Actor]] Other) : This event fires whenever an actor enters the zone. It is responsible for posting any event specified by the <tt>ZonePlayerEvent</tt> property by calling the <tt>Trigger</tt> function. The function also applies any zone physics to objects with physics of <tt>PHYS_Projectile</tt> or objects of type [[Legacy:Effects|Effects]].
; ActorLeaving ([[Legacy:Actor|Actor]] Other) : This event fires whenever an actor leaves the zone. It is responsible for posting any event specified by the <tt>ZonePlayerEvent</tt> property by calling the <tt>UnTrigger()</tt> function.

==Known Subclasses==
* [[Legacy:LevelInfo|LevelInfo]]
* [[Legacy:SkyZoneInfo|SkyZoneInfo]]
* [[Legacy:WarpZoneInfo|WarpZoneInfo]]

==Related Topics==
* [[Legacy:Map Optimization|Map Optimization]]
* [[Legacy:Zone|Zone]] / [[Legacy:Zoning|Zoning]]
* [[Legacy:Iterator|Iterator]] functions
* [[Legacy:Volume|Volume]] class

[[Category:Legacy Class (UT2003)|{{PAGENAME}}]]
[[Category:Legacy Class (UT2004)|{{PAGENAME}}]]

Unreal

2008-09-13T22:09:12Z

GreatEmerald: New page: {{softredirect|Liandri:Unreal}}

Unreal 2 Expanded Multiplayer

2008-09-13T22:08:40Z

GreatEmerald: New page: {{softredirect|Liandri:EXpanded MultiPlayer}}

Template:Softredirect

2008-08-16T14:11:10Z

GreatEmerald: Fixed link

[[Image:Redirectltr.png|#REDIRECT ]][[{{{1}}}]] This page is a [[Wikipedia:WP:Soft redirect|soft redirect]].<includeonly>[[Category:Soft redirects|{{PAGENAME}}]]</includeonly>

Legacy:Unreal 2

2008-07-12T11:52:06Z

GreatEmerald: versions

{|

|-
|'''''Developer(s)'''''
|Legend Entertainment
|-
|'''''Publisher'''''
|[http://www.atari.com/ Atari]
|-
|'''''Release Date'''''
|Febuary 2003
|-
|'''''Supported Platform(s)'''''
|Windows Xbox
|-
|'''''Official Web Site'''''
|http://www.unreal2.com/
|-
|'''''Demo'''''
|[http://download.beyondunreal.com/27880 Windows]
|-
|'''''Latest Patch'''''
|Version '''2001''' – 25th March 2003 [http://download.beyondunreal.com/27879 Windows]
|-
|'''''Unreal Engine Version'''''
|[[Unreal Engine Versions/2
|Unreal Engine 2.0]]
|-
|'''''UnrealEd Version'''''
|[[UnrealEd Versions
|UnrealEd 3]]
|}

==Description==

'''Unreal II: The Awakening''' is a first-person shooter video game, designed initially only for a single-player campaign. The game is part of the Unreal series.

It is set in a different part of the universe to Unreal; according to the Epic timeline is set somewhere in or before the year 2251, whether it is a true prequel or sequel is debated as there is conflicting evidence. It has a different bestiary of weapons, enemies, allies, environments, items, locations, and more. The main tie in is the appearance of the dreaded Skaarj aliens from the series.

===Other Games in the Series===
* [[Legacy:Unreal 1|Unreal 1]]

==System Requirements==
; Operating System : Windows 98/ME/2000/XP

; CPU : Pentium III or AMD Athlon 733MHz processor (*Pentium® or AMD 1.2 GHz or greater RECOMMENDED)

; Memory : 256 MB RAM (384 MB RAM or greater RECOMMENDED)

; Hard Disk Space : 3 GB Free

; CD ROM or CD/DVD ROM : 8x

; Audio System : Windows® compatible sound card (NVIDIA® nForce or other motherboards/soundcards containing the Dolby® Digital Interactive Content Encoder required for Dolby Digital audio.) Sound Blaster® Audigy(tm) series sound card RECOMMENDED

; Video System : 32 MB NVIDIA GeForce2 MX or better (64 MB NVIDIA GeForce3/ATi Radeon 8500 or better recommended). DirectX version 8.1 (included) or higher.

; Multiplayer : An Internet connection is not required to play this game. However, files created with Unreal Editor may be shared and/or downloaded. An internet connection and a 33.6kbps or faster modem (cable/DSL recommended) is required for sharing and downloading.

; Dual-Core Performance Note : This game, along with most older Unreal games, does not run well on dual-core systems with power management. Check with your processor maker for a patch or utility to fix this. An AMD patch can be found [http://www.amd.com/us-en/Processors/TechnicalResources/0,,30_182_871_9706,00.html here] under Dual-Core Optimizer.

==Downloads==

===Patches/Updates===
* [http://download.beyondunreal.com/27879 Version 2001 (Windows)]

===Other===
* [http://www.beyondunreal.com/main/u2/u2essential.php BeyondUnreal's Essential Unreal 2 Files]

==Useful Information==

===New Features of Unreal 2===

====AI Scripting====

Allows a level designer to script various AI events. Scripts are held in the Scripts/ directory where U2 is installed. The main advantage is that you don't have to use UnrealScript or load up UnrealEd to work with the scripts.

[[Legacy:AI Scripting|AI Scripting]]

====Dialog Engine====

This allows "spoken" interaction with NPCs. Arguably, dialog was not used to full effect in the game, but arbitratily complex dialog can be constructed due to integration with the AI scripting.

[[Legacy:Dialog|Dialog]]

====User Interface====

Legend developed their own User Interface/HUD system, presumably for flexibility, and of course speed, because they implemented smooth fades. They've used a kind of Component Object Model, where a given UI is made out of various containers and UI pieces.

The UIs are defined in text UI scripts, with pretty simple syntax. They are located in the UIScripts/ subdirectory.

The system is implemented via UIConsole, which is more-or-less an interface to a number of static functions which are the interface to the native C++ code. Interaction between UnrealScript and the UI is acheived by sending events to the UI, and in the opposite direction via the CodeMonkey class.

The UIScripts appear to completely specify the layout of the UI, and any events that require a response. Appearance is determined by textures in '''UIResT.utx'''.

[[Legacy:User Interface|User Interface]]

==Related Topics==
* [[Legacy:Unreal Engine Versions/2|Unreal Engine 2.0]]

==Discussion==

[[Category:Legacy Game|{{PAGENAME}}]]

Legacy:Mapping For VCTF

2008-06-22T15:53:08Z

GreatEmerald: /* Discussion */

'''Vehicle Capture the Flag (VCTF):''' Two teams both have a movable flag that's planted on an immobile flag base. A team scores a point by getting both flags to their home flag base. This is an extention of the Capture the Flag gametype for [[Legacy:UT2004|UT2004]] with the primary difference being vehicle support. Flying Vehicles may not carry the flag and translocator use is prohibited by default. ''It's strongly recommended that mappers review [[Legacy:Mapping For CTF|Mapping for CTF]] as well.''

==Design considerations==

===Layout===

An obviousbly linear layout (straight from RedFlagBase to BlueFlagBase) is very easy to make when you have a gametype with only two game objectives and the long range/fast movement of vehicles. Try to spread out (branch out) the routes between flags; spreading the field out and offering more variety in routes to and from the enemy flag. Otherwise, an obvious bottleneck or 'choke spot' will present itself, making flag capture difficult if not impossible; but definately frustrating to play, due to lack of variety.

That said, vehicles almost demand layouts of considerable size. Pedestrians should feel somewhat "stranded" in remote places in your map without a vehicle. (See ITEM PLACEMENT for pedestrian remedies)

Vehicles also add firepower and armor to each Team. Therefore, the route to the flag should be appropriately difficult. Defenses of all kinds are encouraged to help make the Capture challenging. (walls, doors, gates, turrets, custom shields, etc.)

===Item Placement===

The flagbases should be inaccessible by larger vehicles, either by structure, barrier or pedestal. Otherwise, players and bots will ride a tank or leviathan on top of their flag to defend and camp on it.

Neutral vehicles placed in the center can add to gameplay by providing a "soft" gameObjective; a place Teams want to control. Neutral (non-flying) vehicles placed near flagbases allow enemies to make quick getaways.

With large layouts, pedestrians can feel stranded out in remote locations. Offer them alternative travel to key points with JumpPads, Teleporters, Movers, etc. in those locations.

===Vehicles===

Remember: By default, flying vehicles cannot carry the flag. Also, someone riding on top of any vehicle can pick up the flag without getting off the vehicle (the Manta is excellent for this).

VehicleFactories will not spawn vehicles in a VCTF map until the gametype is set in LevelInfo to <tt>xGame.XVehicleCTFGame</tt> and both FlagBases are placed.

ONSVehicles(Factories) will spawn by automatically setting the TeamNumber to match that of the nearest GameObjective (Flag). Try the custom [[Legacy:TeamVehicleFactory|TeamVehicleFactory]] for greater control over aspects of vehicle spawning.

===Botplay===

Bots will not use vehicles until a proper CTF bot path network is set, with an AssaultPath set to each flag and at least one WHITE (widest) path connects the two flags. The vehicle spawn points must also be accessible to these wide pathways with their own WHITE paths.

Neutral controllers, controlling bots, turrets, etc., will attack Red and Blue Team members equally. They will ignore other Neutral controllers, as if Neutral was it's own Team. (Team 255)

==Creating a VCTF Map ==

This is a list of critical elements needed to create a simple VCTF map.
* Modify LevelProperties->LevelInfo->DefaultGametype to <tt>xGame.xVehicleCTFGame</tt>.
* A big enough space for vehicles and/or flying vehicles.
* Place two [[Legacy:XRealCTFBase|xRealCTFBase]]s, ones for Red and Blue teams. These must be accessible to a RoadPathNode path network. (see the '''Botplay''' section above)
* Place player starts (set <tt>PlayerStart.TeamNum</tt>s: 0=red, 1=blue)
* Place an [[Legacy:AssaultPath|AssaultPath]] near each flag (line of sight is good) for the attacking team.
* Place VehicleFactory actors where you want vehicles to spawn. Set the direction you want them to start in. The TeamNumber for the vehicles will be set automatically when using ONSVehicleFactories; whichever gameobjective is closer; the red flag or the blue flag. By using custom actors like the [[Legacy:TeamVehicleFactory|TeamVehicleFactory]], you can set the TeamNumber yourself. (0=red, 1=blue, 255=none or neutral)
* When placing [[Legacy:RoadPathNode|RoadPathNode]]s, keep the paths wide (white) between nodes for large ground vehicles and especially along the paths to the flags. Keep these spaced over 512 or 1024 apart because vehicles are not as agile as players on foot; they need to make wider turns. Try to keep the number of pathnodes even on each team's side of the map. There must be at least one white path connecting the flags to the path network, but more paths are recommended.
* Place [[Legacy:FlyingPathNode|FlyingPathNode]]s (between 1024 and 2048 apart) about 1024 to 2048 above the ground. Don't bother making fine or complicated pathing for flying vehicles, with momentum carrying them, they need to make very wide turns, rises and dives.

==Tips==

===Vehicle Pathing for VCTF ( by Toonces T. Cat )===

A few key points to note in the construction of a VCTF level.

* Using an [[Legacy:AssaultPath|AssaultPath]] after the last [[Legacy:RoadPathNode|RoadPathNode]] that vehicles can reach works, and works well, but introduces new and even more complex issues into the equation. Someone else mentioned it in another thread, but what good is it to have your bot grab the flag and then not have a vehicle available when it returns to the RoadPathed area of the map? The best bet is to have the flag in an area where it can make a double (bi-directional) white connection to one or more RoadPathNodes.

* Think vertical and you can have your cake and eat it too. I have created a second elevated level that is pathed just for foot use and it also connects to both flags and, even though the bots use it, it does not preclude them from using the vehicles as well. In fact, combos are very possible as I have seen them use the overhead route to get the flag and then jump into a Tank or a Hell Bender that one of their team-mates is using and hitch a ride home...

* The translocator definitely should be allowed in the game-type. The bots commonly chase a team-mate's vehicle with it and will jump on-board in mid-toss...It is extremely cool to watch them do this... ('''SuperApe''': Toonce's is talking about ignoring the default rules for VCTF that disallow Translocators. This could be done by placing a custom actor (subclass of [[Legacy:XPickUpBase|xPickUpBase]]) and specifying a XWeapon.Transpickup as it's Powerup. See also [http://forums.unrealplayground.com/showthread.php?t=24029 this thread] ('''GreatEmerald''': ''Note: dead link - any replacement?'').)

* When the flag is in a vehicle accessible area, elevate it above the floor on some type of base that the bots can climb on foot, but not in a vehicle. I am using an octagonal base that is about 256 units in diameter and about 40 units high. It has 4 narrow stairwells cut into it (one on every other side) that the bots can use. It is high enough to stop a vehicle (except for the Leviathan), but not so high that the nearby RoadPathNodes cannot make a good path connection.

Why do you need this? Because the bots playing defense will pile into a Goliath and camp the flag if they can get on top of it...and I mean literally ON TOP of it. An enemy bot cannot get to it to take the flag if they are there. This is a workaround of sorts, but it is an effective one as even if they are using a Tank, if the attacker engages them, another bot can come up form behind and take the flag...I've watched it a dozen times.

* As I said above, the 40 unit high barrier will not stop a Leviathan...Hence, tip #5 is do not path the Leviathans if you have them in your level. If a Masterful bot gets into one of them with a couple of his pals, the other team is in big trouble. It's better to keep them out the Leviathans unless a human is driving it. ('''GreatEmerald''': If you need a Leviathan, though, you can set some RoadPathNodes' properties, under Navigation Point, bNoSuperSize to True to keep Leviathans out of some trouble. This way you can also make a defensive Leviathan by setting bNoSuperSize properties only to those nodes that are close to flags, although bots might not want to go in. You might also path everything normally, add an AssaultPath somewhat away from the flag and make all next PathNodes/RoadPathNodes bNoSuperSize to make bots use Leviathans, but not spam with them.)

* RoadPathNodes can be further cleaned up by changing the MaxRoadDistance value in the properties. The default distance is ten thousand. This can create ALL KINDS of unwanted clutter. In the top orthographic view measure between the nodes that you want to connect using SHIFT+MIDDLEMOUSE to bring up the ruler and adjust the nodes accordingly.

==FAQ==

Frequently asked questions and common problems while mapping for VCTF.

* ''Where is the VehicleCTF gametype in the UT2004 menu?''

The VehicleCTF gametype will not show up in the list of available gametypes until at least one VCTF map is placed in the Maps directory. (Filename syntax is : '''VCTF-Foo''')
* ''Vehicles aren't spawning''

You must modify LevelProperties->LevelInfo->DefaultGametype to <tt>xGame.xVehicleCTFGame</tt> and have both the Red and Blue team FlagBases set in the map. After that, Vehicle Factories will spawn vehicles.
* ''Bots won't use the vehicles''

There must be at least one fully connected path from one flag to the other and at least one of these paths must be solidly '''white''' all along the route. This will indicate to bots that they can use a vehicle to reach their goal along that path. The VehicleFactories will also have to be connected to at least one of these routes with a white path.
* ''Bots only use the shortest path to the enemy flag and back''

Use of an AssaultPath close to and within line of sight of the target flag will help bots reach their goal, but to encourage bots to use more of the layout, use other AssaultPaths that meet up to that goal. See [[Legacy:AssaultPath|AssaultPath]] and [[Legacy:Bot Pathing|Bot Pathing]].

==External Links==
* [http://forums.unrealplayground.com/showthread.php?t=23758 Unreal Playground Forum: Mapping for VCTF]
* [http://blitz.unrealplayground.com/tutorials/bots.html Blitz's Advanced Bot Pathing Tutorial]

==Related Topics==
* [[Legacy:Topics On Mapping|Topics on Mapping]]
* [[Legacy:Mapping For CTF|Mapping for CTF]]
* [[Legacy:Pathing For Vehicles|Pathing For Vehicles]]
* [[Legacy:Pathing 2k4 Flying Vehicles|Pathing 2k4 Flying Vehicles]]
* [[Legacy:Map Flow|Map Flow]]
* [[Legacy:Gametype|Gametype]]
* [[Legacy:Vehicle|Vehicle]] – Parent class for all vehicles in UT2004
* [[Legacy:Vehicles|Vehicles]] – Vehicle main topic

==Discussion==

'''SuperApe''': Created. Most borrowed from the external link I wrote a while ago. Toonce's vehicle pathing comments added from [[Legacy:Pathing For Vehicles|Pathing for Vehicles]] and edited slightly. [[Legacy:XVehicleCTFGame|xVehicleCTFGame]], [[Legacy:RoadPathNode|RoadPathNode]], [[Legacy:FlyingPathNode|FlyingPathNode]], [[Legacy:SpecialVehicleObjective|SpecialVehicleObjective]] pages added and other misc links changed. ([[Legacy:NavigationPoint|NavigationPoint]] subclass list, etc.)

'''[[User:GreatEmerald|GreatEmerald]]''': Saw some interesting bot behaviour when spectating a VCTF match with 2 bots. I used AssaultPaths. So when a bot with a vehicle got to one, it left the vehicle, took the flag and... Acted randomly. Usually, bots enter the vehicle with which they came, then instantly exit. Some times though, they enter the vehicle, drive in it for a few seconds and leave it. And the other times bots enter the vehicle and drive nicely. When the bots get back on foot, they can use their own vehicles near their base. Strangely, bots with flags enter the vehicle, and again, some times they drive, and some times they just leave the vehicle. Another strange addition is when a bot with a flag tries to return their own flag. One time a bot in a tank killed a bot flag carrier, then drove very near the dropped flag, returned it, then continued on foot, decided to get into the tank again, ran back and stood near the vehicle, but didn't enter. Another bot that was carrying the flag on foot killed another flag carrier (it was on foot too), ran away from its own flag, decided to return it, returned it, ran back to the AssaultPath and again tried to capture the enemy flag. Any explanation on what's happening and what to do?

[[Category:Legacy Mapping|{{PAGENAME}}]]

Legacy:Pathing For Vehicles

2008-06-22T14:55:10Z

GreatEmerald: /* Additional VCTF (VehicleCTF) Level Tips by Toonces T. Cat */

The common use of vehicles in [[Legacy:UT2004|UT2004]] prompts mappers to take precautions and add special navigation paths for maps that include vehicles. Once properly connected to the network, bots will use the vehicles to travel on the special paths for road and sky navigation. Proper connection to the botpath network includes a complete path connection (one where each path is white, indicating the widest path) from vehicle spawn point to game objective.

'''Note:''' The main focus on this page began with Vehicle CTF, but these concepts apply to pathing for all vehicle gametypes.

===Parking Spots===

Vehicles are large and difficult to navigate in tight spaces. Vehicles too close to obstacles like map layout elements, decorative objects, or other vehicles will be hard for bots to get into and navigate with. When placing paths nodes that vehicles might use, make sure there is a lot of room to leave each spawn spot and be aware of areas (like PowerNodes) where bots and players will want to exit the vehicle, do something and get back in. Often gridlock can occur if RoadPaths are too close together near such areas. Nodes used to find and enter larger vehicles (like HellBenders or larger) should be away from the center of the vehicle (like towards the driver's side door), otherwise bots will get stuck trying to enter.

===RoadPathNodes===

RoadPathNodes define safe and easy places for ground-based vehicles to navigate. Because vehicles take up much more space than players, RoadPathNodes could always be connected by WHITE path nodes; detnoting the widest path available. It should be noted, however, that driving bots will use normal PathNodes as well, as long as they are wide enough. See also [[Legacy:RoadPathNode|RoadPathNode]]s.

===FlyingPathNodes===

FlyingPathNodes indicate clear paths through the sky for flying vehicles. See also [[Legacy:Pathing 2k4 Flying_Vehicles|Pathing 2k4 Flying_Vehicles]] and [[Legacy:FlyingPathNode|FlyingPathNode]]s.

==Vehicle (VCTF) Pathing Info by Toonces T. Cat ==

The prime directive here is the K.I.S.S. principle...Keep It Simple Stupid! The more complex and meandering you make the [[Legacy:RoadPathNode|RoadPathNode]] routing, the worse the bots will drive and the less likely it is that they will directly attack the other base.

In normal ''pedestrian'' gametypes, sometimes more is better with PathNodes to ensure that the bots can get everywhere on the level. Not so with vehicles. Just lay down the RoadPathNodes where you need the bots to drive the vehicles and nowhere else. The simpler and the more straight-forward the layout of the nodes, the better.

One huge problem with this is that the default range setting on a RoadPathNode is 10,000 [[Legacy:UU|UU]] (Unreal Units). If you put them down without adjusting this property, they will connect all over the level and the bots will go nuts and likely never reach the objective. I don't know any shortcuts for doing this other than to place 4 or 5 RPNs and then set their range and build the paths. If you get two-way pathing for all the Nodes, then you are in good shape. If they make connections you did not intend for them to make, then reduce the distance until they drop the connection. If they do not connect as a two-way point, then shorten it up a bit until they do. Sound tedious? Yeah it is, but the end result is well worth the trouble.

----

Here's a screenie of the editor to show you what it should look like:

[[Image:Legacy_VehiclePathing.jpeg|center|''Road Pathing on VCTF-Strip Mine'']]

----

Here's is Steve Polge's summation of the rest of it:

{{innerbox|
"The larger vehicles require white (or forced vehicle) paths connected to the objective (flag base) and all assault paths. If the vehicle can't get all the way to the objective, make sure they can get to the assault paths for the objective, and then they'll continue on foot.

Also, objectives have a VehiclePathName property. If you can't get a vehicle path all the way to the objective, set the VehiclePathName to the name (under the object tab) of the nearest NavigationPoint that vehicles can reach.

If you need to force paths for vehicles, you'll need to check bVehicleDestination in the destination NavigationPoint properties, and then add a forced path in the normal manner.

}}

The bottom line is that if you do not have an all white path between the objectives, the bots will not play the game properly. As Steve states above, if the bots can't reach the objective in the vehicle, then you'll have to use an assault Path to get them there. His instructions are spot-on. Follow them carefully and it will work for you.

The other instructive thing I learned from this lengthy exercise is that very few existing CTF levels will make for really good VCTF maps if you plan to use bots. I suppose you can jack an ONS map and convert it, but remember that the main deal in VCTF is they have to do the following:

# Get in a vehicle and drive as close as possible to the objective.
# Exit the vehicle and grab the objective.
# Make their way back to the vehicle with the objective and get into it.
# Drive back to their own base with the objective.
# Get out of the vehicle and make the capture.

That is not what happens in ONS and the A.I. in the maps is not set-up to facilitate it happening. If you use a base ONS map, dump the existing A.I. and start building it from scratch. I haven't even begun to mess with the FlyingPathNodes, but as you can't carry the flag in either a Raptor or a Manta, who cares? I put some into a level and they connected and it seemed to work okay as long they covered the map with their connections...Here's another tip, though, wait to do the FlyingPathNodes until you're just about 100% done with the RoadPathNodes. Once they are in place, with View Paths enabled, the map looks like an explosion in an orange spaggetti factory...i.e. - You can't see a thing after that.

==Additional VCTF (VehicleCTF) Level Tips by Toonces T. Cat==

I have discovered a few additional key points to note in the construction of a VCTF level:

#Using an [[Legacy:AssaultPath|AssaultPath]] after the last RoadPathNode that vehicles can reach works, and works well, but introduces new and even more complex issues into the equation. Someone else mentioned it in another thread, but what good is it to have your bot grab the flag and then not have a vehicle available when it returns to the RoadPathed area of the map? The best bet is to have the flag in an area where it can make a double (bi-directional) white connection to one or more RoadPathNodes.
#Think vertical and you can have your cake and eat it too. I have created a second elevated level that is pathed just for foot use and it also connects to both flags and, even though the bots use it, it does not preclude them from using the vehicles as well. In fact, combos are very possible as I have seen them use the overhead route to get the flag and then jump into a Tank or a Hell Bender that one of their team-mates is using and hitch a ride home...
#The Teleporter definitely needs to be in the game-type. The bots commonly chase a team-mate's vehicle with it and will jump on-board in mid-toss...It is extremely cool to watch them do this...
#When the flag is in a vehicle accessible area, elevate it above the floor on some type of base that the bots can climb on foot, but not in a vehicle. I am using an octagonal base that is about 256 units in diameter and about 40 units high. It has 4 narrow stairwells cut into it (one on every other side) that the bots can use. It is high enough to stop a vehicle (except for the Leviathan), but not so high that the nearby RoadPathNodes cannot make a good path connection. (''Why do you need this? Because the bots playing defense will pile into a Goliath and camp the flag if they can get on top of it...and I mean literally ON TOP of it. An enemy bot cannot get to it to take the flag if they are there. This is a workaround of sorts, but it is an effective one as even if they are using a Tank, if the attacker engages them, another bot can come up form behind and take the flag...I've watched it a dozen times.'')
#As I said above, the 40 unit high barrier will not stop a Leviathan...Hence, tip #5 is do not path the Leviathans if you have them in your level. If a Masterful bot gets into one of them with a couple of his pals, the other team is in big trouble. It's better to keep them out the Leviathans unless a human is driving it. ('''GreatEmerald''': If you need a Leviathan, though, you can set some RoadPathNodes' properties, under Navigation Point, bNoSuperSize to True to keep Leviathans out of some trouble. This way you can also make a defensive Leviathan by setting bNoSuperSize properties only to those nodes that are close to flags, although bots might not want to go in. You might also path everything normally, add an AssaultPath somewhat away from the flag and make all next PathNodes/RoadPathNodes bNoSuperSize to make bots use Leviathans, but not spam with them.)
#RoadPathNodes can be further cleaned up by changing the MaxRoadDistance value in the properties. The default distance is ten thousand. This can create ALL KINDS of unwanted clutter. In the top orthographic view measure between the nodes that you want to connect using SHIFT+MIDDLEMOUSE to bring up the ruler and adjust the nodes accordingly.

==External Links==
* [http://blitz.unrealplayground.com/tutorials/bots.html Blitz's Advanced Bot Pathing Tutorial]

==Related Topics==
* [[Legacy:Bot Support|Bot Support]] – Main topic
** [[Legacy:Bot Pathing|Bot Pathing]] – Concepts and elements of a bot path network
*** [[Legacy:Basic Bot Pathing|Basic Bot Pathing]] – A tutorial on basic bot pathing
* [[Legacy:Pathing 2k4 Flying Vehicles|Pathing 2k4 Flying Vehicles]]
* [[Legacy:Mapping For AS (UT2004)|Mapping for AS (UT2004)]]
* [[Legacy:Mapping For ONS|Mapping for ONS]]
* [[Legacy:Mapping For VCTF|Mapping for VCTF]]

==Discussion==

'''(relaying Toonces' sentiments):''' I hope this is helpful to everyone!

'''SuperApe:''' Thank you, Toonces! You da Cat!

'''SuperApe:''' Edit. Additional VCTF Notes added. Somebody should write up a VehicleCTF or VCTF page. EDIT: I will post the important stuff here on the wiki soon (after VCTF contest is over): [http://forums.unrealplayground.com/showthread.php?t=23758 Mapping for VCTF].

'''King Mango''' Going to look for the proper place to post this, but in the meantime, to enable xloc in a VCTF game check [http://forums.unrealplayground.com/showthread.php?t=24029 this thread] at Unreal Playground. ('''SuperApe:''' I think I got it up there now.)

'''Tarquin:''' Use the # wiki markup for numbered lists please :)

'''Erdrik:''' This is very help for pathing vehicles for VCTF, but I was wondering about Onslaught. ''Edit:'' doh, Assultpaths work in Onslaught as well, my bad :p

'''SuperApe:''' Temporarily copying VCTF information to [[Legacy:Mapping For VCTF|Mapping for VCTF]] before I remove it from here.

'''Lucy:''' The main problem I'm having with VCTF pathing is that the bots will get in a vehicle and immediately get out. On the rare occasion they stay in the vehicle, they will not drive it anywhere and just stay in place.

'''SuperApe:''' This is a common pathing problem, akin to bots getting "stuck". In this case, the bot knows the vehicle is desirable, but the destination isn't clear, so it jumps back out or sits there. In real terms, this means the paths from the vehicle (spawn point) all the way to the enemy flag are not all white (the widest) paths. Added Blit'z Pathing Tut in External Links, which includes this explanation on the "white road":

{{innerbox| ''In other words, think of this as a single, white road that connects to each vehicle and each objective. Bots will only understand how to reach objectives if there is a white route from the vehicle they just hopped into to the objective they're seeking. If this route doesn't exist, then the bot will abandon the vehicle and proceed on foot.''

}}

'''LionsPhil:''' Aww. Am I so wrong for feeling sorry for bots who have found a shiny tank to play with, but can't work out where to take it? ;)

[[Category:Legacy Mapping|{{PAGENAME}}]]

Legacy:Mapping For VCTF

2008-06-22T14:53:54Z

GreatEmerald: /* Vehicle Pathing for VCTF ( by Toonces T. Cat ) */