Example Configurations

The next thing to point out is that you can do almost all the configuration in the .ini file but sometimes it is more efficient to set things via the startup command (I’ll go through that later).  An example would be I could set the goal frag limit for DM in the config file but then if I want to make it higher because I want to play instagib, for example,  I have to change the config file.  If I set the goal score via the startup command then all I have to do is save all my different startup commands and run them when I want to change the behavior a little bit.  We will get into the details of the startup command later, for now I’ll go over some example ini configurations.

NOTE: When I refer to a ‘section’ in the ini file, what I’m saying is the name in brackets…using the server info step below as an example I would refer you to the section [Engine.GameReplicationInfo]

Once you have the defaultgame.ini file open there are a few things you’ll want to change.  Some are not mandatory but you’ve made it this far, lets do it right.

1)      Server info

[Engine.GameReplicationInfo]

ServerName="Welcome to WOPR-UT3PC1!"

ShortName="UT3 Server"

MessageOfTheDay="Have Fun!"

[Engine.DecalManager]

DecalLifeSpan=30.0

2)      Map Cycles

In the [UTGame.UTGame] section there will be several lines that by default look like this:

+GameSpecificMapCycles=(GameClassName="UTDeathmatch",Maps=("DM-Arsenal","DM-Sanctuary","DM-Deck","DM-Defiance","DM-Deimos","DM-Diesel","DM-Gateway","DM-HeatRay","DM-RisingSun","DM-Sentinel","DM-ShangriLa"))

+GameSpecificMapCycles=(GameClassName="UTTeamGame",Maps=("DM-Arsenal","DM-Sanctuary","DM-Deck","DM-Defiance","DM-Deimos","DM-Diesel","DM-Gateway","DM-HeatRay","DM-RisingSun","DM-Sentinel","DM-ShangriLa"))

+GameSpecificMapCycles=(GameClassName="UTCTFGame_Content",Maps=("CTF-Coret","CTF-Hydrosis","CTF-Reflection","CTF-Vertebrae","CTF-OmicronDawn","CTF-Strident"))

+GameSpecificMapCycles=(GameClassName="UTOnslaughtGame_Content",Maps=("WAR-Downtown","WAR-SinkHole","WAR-Dusk","WAR-Islander","WAR-Avalanche","WAR-MarketDistrict","WAR-OnyxCoast","WAR-Powersurge","WAR-Serenity","WAR-FloodGate","WAR-Torlan"))

+GameSpecificMapCycles=(GameClassName="UTBetrayalGame",Maps=("DM-Arsenal","DM-Sanctuary","DM-Deck","DM-Defiance","DM-Deimos","DM-Diesel","DM-Gateway","DM-HeatRay","DM-RisingSun","DM-Sentinel","DM-ShangriLa"))

+GameSpecificMapCycles=(GameClassName="UTGreedGame_Content",Maps=("CTF-Coret","CTF-Hydrosis","CTF-Reflection","CTF-Vertebrae","CTF-OmicronDawn","CTF-Strident","VCTF-Corruption","VCTF-Necropolis","VCTF-Suspense"))

+GameSpecificMapCycles=(GameClassName="UTDuelGame",Maps=("DM-Arsenal","DM-Sanctuary","DM-Deck","DM-Defiance","DM-Diesel","DM-RisingSun","DM-Sentinel","DM-ShangriLa"))

+GameSpecificMapCycles=(GameClassName="UTVehicleCTFGame_Content",Maps=("VCTF-Containment","VCTF-Corruption","VCTF-Necropolis","VCTF-Suspense","VCTF-SandStorm","VCTF-Kargo"))

You can tell which line refers to which gametype by the GameClassName in the code above.

UTDeathmatch=Deathmatch

UTTeamGame=Team Deathmatch

UTCTFGame_Content=Capture the Flag

UTOnslaughtGame_Content=Warfare

UTBetrayalGame=Betrayal

UTGreedGame_Content=Greed

UTDuelGame=Duel

UTVehicleCTFGame_Content=Vehicle Capture the Flag

Change the maps in the list to be as you want them, keeping in mind that the first one in the list will have top priority in the map vote.  For example if Deck is first in the list and Sentinal is second and there is one vote for each, Deck wins.  You MUST leave the + in front of each line.  The + allows a variable to be set multiple times in the same section without being overwritten.  If you don’t understand what I just said don’t worry about it…just leave the + there and everything will be fine!

Real world example: My duel server has the following for a map cycle:

+GameSpecificMapCycles=(GameClassName="UTDuelGame",Maps=("DM-Deck","DM-ShangriLa","DM-Sentinel","DM-Diesel","DM-RisingSun","DM-Defiance"))

3)      Map Vote

In the section above we went through a mapcycle which is different than mapvote.  The map cycle simply defines which maps are available and what their priority is.  If you want to allow map voting make sure in the [UTGame.UTGame] section you have the following :

bAllowMapVoting=true

4)      Other options  (optional and NOT recommended for most users)

The above is really all that I configure in my ini files.  I do the rest of my configuration in the startup command.  However if you want to fiddle with more of the variables have at it…but check out the startup commands section first so you can see how I do it, you may want to do it my way as well. 

The following info may help if you decide you want to do more configuration in the ini file itself.  The below is optional info and is not recommended.  Also it should be noted that not all variables within the ini files work on PS3.  Some things are only configurable on the PC or 360 version, so keep that in mind.  Most variables are self explanatory but if unsure a quick Google search will uncover it for you.

The [UTGame.UTGame] section has most of the variables in it.  This is sort of the base section that applies to the other sections unless otherwise defined there…I know that’s a little confusing so here’s an example.

If I had bAllowMapVoting=false in [UTGame.UTGame] but then further down in [UTGame.UTTeamGame] I had bAllowMapVoting=true.  The expected result would be that the only game mode that would use mapvote is TDM.

-----------------------------------------------------------------------------------------

 

Create a Gamespy account

 

Before we can startup our newly configured server we need to create a Gamespy account.  There is a utility to do this that we have to run from the command line.

 

• Click Start, then Run

 

 

• Type: cmd
• Click ok

 

• you should now have a window that looks like this:

• We now need to change directories to where the UT3 server software is installed = your <install path>. The example below is showing where I installed it.   If you left the default path during the installation it is C:\Program Files\Unreal Tournament 3 (Dedicated), You would type: cd Program Files\Unreal Tournament 3 (Dedicated)\Binaries

 

1)      Now we can use the account creation script.  The example below is:

 

createaccount ut3yourname ut3yourpassword something@something.com

Createaccount test1234 password1234 test@gmail.com

 

Keep in mind that what you use as your username will be what people see as the server name in the game browser.

 

The email address need not be valid.  I have my real email address on my duel server and have never gotten any email from it so I’m not sure what this is here for.  Maybe just another way to verify the account…not sure.

 

 

The image below reflects what a successful account creation message should look like.  If the creation fails most of the time it is because the user name is already taken, so just pick another name and try again. You may use the same email address and password for all Gamespy accounts you create.  For multiple accounts, it's easiest to simply change the username.

 

 

Startup Commands

 

Ok so we’re finally ready to start up the server.  We just need to decide on our final config options.  You need to be in <install path>\Binaries in your command line window. 

 

So lets just dive right in, first example is what my duel server startup command looks like: (all on one line)

 

UTGame server DM-Sentinel?game=UTGame.UTDuelGame?bWeaponStay=true?numplay=2?Difficulty=4?minnetplayers=1?maxplayers=4?GoalScore=10?TimeLimit=10?forcerespawn=1?allowkeyboard=1?GamePassword= -log=WOPR-UT3PC1_DedicatedServer.log -seekfreeloading -login=test1234 -password=password123 -email=test@gmail.com

 

Lets break this down:

 

UTGame server – startup in server mode

server DM-Sentinel – first map to play will be Sentinal

game=UTGame.UTDuelGame – This is a duel game

bWeaponStay=true – Supposed to make weapons stay instead of respawn.  Doesn’t work currently.

numplay=2 – This tells the server to add 1 bot if only one player is in the server.

Difficulty=4 – The difficulty of the bot, starting at 0 for Novice.

minnetplayers=1 – says there should be at least 1 real (non bot) player for the game to start.

maxplayers=4 – The maximum amount of real players that can join

GoalScore=10 – number of frags to win

TimeLimit=10 – time limit ;)

forcerespawn=1 – forces the player  to respawn.

allowkeyboard=1 – enables keyboard and mouse support.

GamePassword= - when blank there is no password.  If you define a password the server will be locked.

-log=WOPR-UT3PC1_DedicatedServer.log – I renamed my log file because I have several servers and want to keep track of which log is for which server.

-seekfreeloading – tells gamespy what account type you have.

-login=test1234 – your user name you created earlier.

-password=password123 – your password created earlier

-email=test@gmail.com – the email address on this account

 

Note that all parameters related to the actual match are separated by question marks (?), while server parameters are added with dashes (-). All dash parameters need to be listed last/after the question mark parameters.

 

 

 

Other examples of startup commands:

 

instagib Duel:

UTGame2 server DM-Deck?ServerDescription=105000110000115000116000097000?game=UTGame.UTDuelGame?Mutator=UTGame.UTMutator_Instagib?bWeaponStay=true?numplay=2?Difficulty=4?vsbots=0?minnetplayers=1?maxplayers=4?GoalScore=15?TimeLimit=10?forcerespawn=1?allowkeyboard=1?GamePassword= -log=WOPR-UT3PC2_DedicatedServer.log -seekfreeloading login=test1234 -password=password123 -email=test@gmail.com

 

Pure DM:

UTGame2 server dm-Deck?numplay=4?Difficulty=5?forcerespawn=1?allowkeyboard=1?vsbots=0?minnetplayers=1?maxplayers=8?GoalScore=35?TimeLimit=30?forcerespawn=0?allowkeyboard=1?GamePassword= -log=WOPR-UT3PC2_DedicatedServer.log -seekfreeloading login=test1234 -password=password123 -email=test@gmail.com

 

Insta DM:

UTGame2 server dm-Deck?ServerDescription=105000110000115000116000097000103000105000098000058000032000109000109000109000109000032000103000105000098000108000101000116000115000?Mutator=UTGame.UTMutator_Instagib?numplay=4?Difficulty=4?forcerespawn=1?allowkeyboard=1?minnetplayers=1?maxplayers=8?GoalScore=35?TimeLimit=30?forcerespawn=0?allowkeyboard=1?GamePassword= -log=WOPR-UT3PC2_DedicatedServer.log -seekfreeloading login=test1234 -password=password123 -email=test@gmail.com

 

You may notice that 2 of the above commands have a couple extra variables when compared to the first example.  One of them is ServerDescription and the other is Mutator.

 

ServerDescription is useful for adding more information to the server name in the browser.  Take the first example, normally it would just show up as test1234 but with the addition of the description field I’ve added ‘insta’.  There is a webpage that will make the conversion from plain ASCII text to the code you see as 105000110000115000116000097000.   http://www.iamgaming.com/UT3ServDesc.asp - Use the iAMGaming.com Description Generator found here.  

 

Second is the Mutator.  This obviously is how you enable a mutator, the names for all the mutator classes are in the appendix along with some other helpful definitions.  For multiple mutators separate each of them with a comma like so:

 

mutator=UTGame.UTMutator_Instagib,UTGame.UTMutator_LowGrav

 

 

As you can see there several values that I change on a regular basis within my startup commands so for me it made more sense to change configuration via the startup command as opposed to having to change multiple variables in the ini file every time I wanted to change my style.  However if you intend on hosting the same configuration every time then it may make more sense to put most of your settings in the ini file.  The minimum required fields to start up a server is:

 

UTGame.exe server dm-arsenal? Game=UTGame.UTDeathmatch -login=ut3yourname –password=ut3yourpassword –seekfreeloading

 

All the other variables I’ve used in my examples can be placed in the [UTGame.UTGame] section of the DefaultGame.ini.

-----------------------------------------------------------------------------------------

Appendix