|
Installation NB. Dont forget in the UT2004.ini file to add... [Engine.GameEngine] ServerPackages=UT2Vote57 The following files need to go in the UT2004 System folder: UT2Vote57.u UT2Vote57.int UT2Vote57.ucl UT2Vote57.ini UT2Vote57.ini.lix - (for Linux only) UT2Vote57 needs to be added as the only Mutator in your Server startup commandline as UT2Vote handles all the mutators once it is loaded, so its best to not have any commands in start up except multihome if needed or specifying ini= or as some server companys insist maxplayers= as UT2Vote takes over the command options. Single Server ucc server CTF-Maul?Game=xGame.xCTFGame?Mutator=UT2Vote57.UT2VoteX etc.. Multi Servers ucc server CTF-Maul?Game=xGame.xCTFGame?Mutator=UT2Vote57.UT2VoteXMulti etc.. The Multiserver system will create new configs in the Server.ini file or the configs can be copied and pasted from the UT2VoteXMulti.txt file. You also need to add UT2Vote57 as a Serverpackage in the servers UT2004.ini file although UT2Vote57 will add itself now if it cannot find itself in the Serverpackages. [Engine.GameEngine] ServerPackages=UT2Vote57 Brief Setup UT2Vote requires this information to be entered at the following places: ServerMuts= Mutators that will be common to ALL games must go in here. These mutators will apply to ALL games ALL the time EXCEPT in a ClanMatch. Basically the Mutators that you would normal add in the Startup commandline, should now go here For example: ServerMuts=ServerBots2.ServerBots,UnrealGame.MutLowGrav,XGame.MutNoAdrenaline Note: A Mutators ClassName can be found in the .ucl file supplied with the mutator. Should you require the Mutators to be more flexible, it would be better to add them in the Mutators= section in the GameType= strings instead of here. ServerLine= Any commandline commands that you need for all games should go here, for example: ServerLine=?AdminName=Admin?AdminPassword=xxxxx?Translocator=True Any commands entered here will take priority and over ride the GameType Commands= Like the ServerMuts, these commands will apply to ALL games ALL of the time EXCEPT during a ClanMatch. VoteAdminPass= This is the Main Admin password and will give this Admin full rights to accessing anything in UT2Vote. ClanAdminPass= This password is for Clan Leaders who can setup the server for a dedicated ClanMatch. This Admin will not have access to the general Admin settings of the server. GamePassword= If the Games on your server requires ALL players to logon with a Game Password, that password should be entered here. DefaultGameName= Whatever you choose to be your Server DefaultGame needs to be entered here. If you leave it blank, UT2Vote will enter the game from which your Server first starts up in. Example: DefaultGameName=Capture the Flag When players have all left your server and it is not in a default state, UT2Vote will switch your server to this Default Game State. When UT2Vote first starts when your server starts, this game and its DefaultMap will be loaded. DefServername= Enter the name of your server here. Although UT2Vote can change this ingame, should there be an error, it will default back to this name. You are now ready to startup your Server. Once your server is running, join the Game and login as Admin: Mutate UT2VoteLogin (the VoteAdminPass) Press the Map Menu Hotkey (normally set on the ScrolLock and/or Home Key) and once the menu is up, click on the Admin button and you will start seeing the world at your fingertips. NB.. Almost all Admin changes will need a level restart. |
|
The UT2Vote57.ini file
Ini file information and configurations Select a Setting Header |
|
[UT2Vote57.UT2VoteConfigs]
[UT2Vote57.UT2VoteVoting] [UT2Vote57.UT2VoteIniOnly] NB.. The following settings are Ini file settings only and fall under the heading: NewMapButnText= This is for Admin option to change the text on the NewMaps button The information in the [UT2Vote57.UT2VoteNewMaps] can then be tailored for other purposes. NewMapMenuText= When the NewMaps button above is clicked, this information will display on the menu heading bStandardServer=True This will enable your server to be displayed as a Standard Server bDisplayRec If set to True it will display when a Demo recording starts. bSortOpinion If set to True, this will display the Voted maps in Opinion order rather than Voted order. bDisMapCon If set to True, then when a Map Menu is called, the clients Console will not be cancelled. bNoClientWarn If set to True, Players will not receive a warning notice when logging onto UT2Vote the first time and their client settings have not been done. bNoPlayerMute=False This will disable muting of players by the VoteAdmin. BanMinLevs= The minimum amount of levels players can be kick banned for. BanMaxLevs= The mmaximum amount of levels players can be kick banned for. bDetectUTComp=False If set to True, then some things will be disabled in UT2Vote. bMapChecks (used to be bMinMaxMaps) If this is set to True then the game will check to see if the selected map is suitable for the current number of players as defined. As from 5.5 the GoalScore and/or the TimeLimit for any given map can also be changed. Should any of the options =0 it will be ignored and the server default used. [UT2Vote57.UT2VoteMapCheck] CheckMap=(MapName="DM-Smallmap",MinPlayers=0,MaxPlayers=4,GoalScore=10,TimeLimit=10) CheckMap=(MapName="CTF-Hugemap",MinPlayers=10,MaxPlayers=32,GoalScore=30,TimeLimit=20) NB. Only maps using the currrent games MapPrefix= will be used and all AltMapPrefix= ignored. bMapCheckSpecs=False When using the [UT2Vote57.UT2VoteMapCheck] and this is True, Spectators will be added to the MaxPlayer count. bUseRandomMap=False If set to True, then when a vote times out and the vote fails, UT2Vote will choose a Random map from the Server maps folder or List instead of the Default map. bGameRepeatLimit=False If set to True, the Games will only be votable every alternate Game voted. MapListSort=0 0 = Alphabetical A - Z listings. 1 = Alphabetical Z - A listings. 2 = Random selection on each level. 3 = As in list - best if UseMapList=True bNoCenterMessage=False When set to True, Players will not receive UT2Vote message in the center of the screen during a game. This was added as players complained the message hid the crosshair. bSpectatorSpy=True this allows players to set their ClientMenu options so as to be notified if a Spectator is viewing them.
[UT2Vote57.UT2VotePackages] [UT2Vote57.UT2VoteMapCheck] If bMapChecks=True then the game will check to see if the selected map is suitable for the current number of players as defined. As from 5.5 the GoalScore and/or the TimeLimit for any given map can also be changed. Should any of the options =0 it will be ignored and the server default used. [UT2Vote57.UT2VoteMapCheck] CheckMap=(MapName="DM-Smallmap",MinPlayers=0,MaxPlayers=4,GoalScore=10,TimeLimit=10) CheckMap=(MapName="CTF-Hugemap",MinPlayers=10,MaxPlayers=32,GoalScore=30,TimeLimit=20) NB. Only maps using the currrent games MapPrefix= will be used and all AltMapPrefix= ignored. [UT2Vote57.UT2VoteGameSwitch] SwitchToGame=(SwitchHour=12,GameName="DeathMatch",ClassName="",DoSwitch=True) SwitchToGame=(SwitchHour=15,GameName="Capture the Flag",ClassName="",DoSwitch=True) At 12:00 if DoSwitch=True then DeathMatch will become your DefaultGameName and the server will switch to it 3 minutes later if there are no players on the server. The same will happen with xCTFGame at 15:00 You can have up to 16 GameSwitches per day. [UT2Vote57.UT2VoteNewMaps] NewMap=(MapName="DM-Whatever") Admin can add mapnames here which will display in the NewMaps Menu. Normally only the latest maps on the server should go here. NB... Make sure the spelling is correct as these maps are voteable by players. [UT2Vote57.UT2VoteKickBan] BanPlayer=(NickName="Whatever",UniqueID="4230fdb7a6cafda49fed3f4200fa97cc",IPaddrs="123.123.123.123",Levels=5) This section is used internally and stores all the information from Players that have been kicked off, or voted off your server. The only time you will set anything manually here is if you want to ban someone on a permanent basis by setting Levels=111 [UT2Vote57.UT2VoteMapInfo] This is used internally by UT2Vote [UT2Vote57.UT2VoteMapsVoted] This is used internally by UT2Vote |
|
UT2Vote57 [UT2Vote57.ClanSetup] This section basically explains what a ClanLeader needs to do to setup a ClanMatch.
Setup |
|
UT2Vote57 UT2Vote Server Messages
[UT2Vote57.UT2VoteMessages] |
|
UT2Vote57 Clientside configuration settings
In the User.ini file you will see the followingand are all available in the ClientMenu Other Client Options VoteMenu KeyBind Click this button to set a keybind for activating UT2VoteMenu on any key you wish. ClanReady KeyBind Click this button to set a keybind for activating Ready at the end of a Clan Warmup. Spectator Mode Click this button to switch to spectator mode. Demo Click this button to start a Clientside Demo of the current game. |
|
UT2Vote57 Adding extra Games Adding extra Games [UT2Vote57.UT2VoteGameTypes] bSortGameList=False This will sort the ini files GameList alphabetically. Here every game, whether default or custom will be setup all in one line and can be individually configured. Actually only the initial creation needs to be done here and the rest can be done with the ingame AdminMenu. When creating another Game entry, just copy and paste any one of them then go and change the necessary configurations. There are a few that need to be done in the UT2Vote57.ini file before you setup the rest in the AdminMenu, although you can do the whole lot here if you so wish. UT2Vote Game Rules You can add games (up to 50) but cannot remove the default games. UT2Vote needs these default GameTypes for its reference. Here I will give an example of how to create a new Game and go through each setting in detail. A typical GameType configuration looks like this: (all in one line) GameType=(GameName="Capture the Flag",HideVote=False,Clan=True,RequiredPlayers=2, MapLimits=0,ServerName="None",UseMapList=False,DefaultMap="CTF-Chrome", MapPrefix="CTF",AltMapPrefix="",GameClass="XGame.xCTFGame",Mutators="None", Commands="?GoalScore=5?TimeLimit=20?MinPlayers=2?MaxPlayers=17?MaxSpectators=2 ?Translocator=True?Weaponstay=True?BalanceTeams=True?ForceRespawn=False ?PlayersMustBeReady=False?Difficulty=5?GameStats=False?GameSpeed=1.00?FF=0?NumBots=3") So lets say we have just copied and pasted that line and want to change it to DeathBall. The actual length of the GameName depends on how many games you can fit into UT2Vote... let me explain. The way in which UT2Vote sends the information to the client is different to most. UT2Vote can send a maximum of 440 characters to the Clients GameMenu so.... Lets take a name like "Capture the Flag" which has 16 characters. So if all the games had 16 characters that would be 440 / (16 + 1) the + 1 is the comma that seperates each game. This means UT2Vote can handle 25 games. Any others would be dumped. Fortunately most games have short names and you can call it what you like. Please Note: no commas or fullstops are allowed in a GameName. So in our example GameName="Death Ball" If however it is set to True, UT2Vote will hide the Game in the Game Menu. In our example HideVote=False This should be set to False for all DeathMatch type Games in our example lets say RequiredPlayers=4 as DeathBall is boring with only 2 players. In our example lets make it MapLimits=1 In our example we will call it ServerName="JoeSoap's Deathball Game" In our case we set it to UseMapList=False Here you set the name of a default map that UT2Vote will use if this gametype is selected to do an auto defaultgame switch. In our example we use DefaultMap="DB-Cube" In our example it will be MapPrefix="DB" AltMapPrefix= Any other MapPrefix can be added here seperated by a comma, should other maps wish to be played with this game type. ie.. AltMapPrefix="CTF,DOM,ONS,BR" If the AltMapPrefix= is set to the same Prefix as the standard MapPrefix= then the game will hold 500 maps. A maximum of 250 maps will be devided amongst the number of prefixes given here. Its only a pity that Modders don't mention there Game or Mutator ClassNames in their Readme files.... such a pity Some things to remember about a ClassName is it will ALWAYS be 2 names seperated by a dot. The best way to find a Game, Mod or Mutators ClassName is to look in the .ucl file that comes with that Mod. Game=(ClassName=DeathBall.DB_Deathball,GameName= etc etc.. ) What you are interested, in all cases is the part between the Name= and the very next ',' comma. In this case it is DeathBall.DB_Deathball It is of paramount importance that you have this ClassName correct else you will not only crash UT2Vote but you will without a doubt crash your whole server as well, so if you are not 100% sure, either write to the author of the Mod or just dump the mod. In our example it will be GameClass="DeathBall.DB_Deathball" Please Note.. nowhere ever do you enter UT2Vote in as a Mutator anywhere as it will see to that itself. If you dont want any Mutators with this game leave it as "" or "None" In our example lets leave it as Mutators="None" GoalScore= This is the fraglimit, goals or the number of flags needed to win the game. TimeLimit= This is the max timelimit allowed for the game. If set to 0, the game will continue till the GoalScore is reached. MinPlayers= This mainly refers to Bots on a server. If set to 2 means if there is only one player, he will play with a Bot. When a second player joins the game, the Bot will leave and the players carry on. If set to 0, no Bots will be allowed. MaxPlayers= The total number of players allowed on a server. MaxSpectators= The total number of Spectators allowed on a server. Translocator= Set to True or False, depends if this game uses the Translocator or not. If True the Translocator will be used. WeaponStay= Set to True or False, if set to False this game will have its weapons dissapear when picked up and respawned a while later. BalanceTeams= Set to True or False, if True and a Team type game, UT2004 will try and balance the teams equally otherwise the players need to do it manually themselves which is sometimes better as UT always screws it up :) ForceRespawn= Set to True or False, if True then when a player dies he will immediately be respawn. PlayersMustBeReady= Set to True or False, if True then everyone needs to click their Fire button to indicate they are ready before a game can start. Difficulty= Set between 1 and 7, this is the skill level that the Bots will play at. GameStats= Set to True or False, self explanatory, but if you want Bots on your server, set it to False. GameSpeed= The speed of the game set as 1.00 upto 2.00. FF= FriendlyFire setting for TeamGames and can be from 0.0 to 1.0 NumBots= This only effects a local Instant Action game and has no effect on a server. It is basically the number of Bots you want to play with. AirControl Should an Admin wish to change a games AirControl then just add the option in the GameType string. In the GameType= string, if ?AirControl= is not present, UT2Vote will default the AirControl to 0.35 which is the UT2004 default. If the ?AirControl= is added UT2Vote will use that, and if ?AirControl=0 then UT2Vote will not adjust or use the AirControl in any way whatsoever and basically ignore it. However, this adjusting process happens everytime the player respawns after dying. If you do not want the AirControl touched in any way, and let the game control it, then add ?AirControl=0 to the GameType= commandline. Extras There are several other commands you can just add on to the end if you like, but just remember to seperate each one with a ? (question mark) and keep them within the "" (quotes). All these commands are available for the Admin in the UT2Vote AdminMenu to change at any time they wishe. For new games and ClassNames Download GameMake3 |
|
UT2Vote57 Adding extra Mutators Adding extra Mutators [UT2Vote57.UT2VoteMutators] bSortMutsList=True This will sort the ini files Mutator list alphabetically. To add Custom made Mutators to UT2Vote you need to copy and paste the example given and just change necessary parameters. Here I will give an example of the Sniper Arena Mutator. After copying and pasting you will have: Mutator=(FriendlyName="None",HideVote=False,MutClassName="None.None",Voted=False) FriendlyName="None" First you enter a Friendly name for the Mutator - keep it as short as possible as it has to fit in the Menu. In our case we call it FriendlyName="Sniper Arena" HideVote= Self explanatory, if set to False then it will appear in the Mutator Menu and players can vote for it. If however it is set to True, it will be hidden from the Mutator Menu. MutClassName="None.None" The Mutator Class Name can always be found in the .ucl file that comes with a Mutator. Mutator=(ClassName=SniperArena.MutSniperArena,GroupName= etc etc...) Voted=False Please leave this alone, as it is used internally by UT2Vote as an indication whether it has been voted for or not. Serverpackages Just a reminder here, all Mutators that appear in the ServerMuts= MUST be declared in the UT2004.ini ServerPackages= or added to the [UT2Vote57.UT2VotePackages]section. |
|
UT2Vote57 Undocumented Stuff BonusVehicles To get the BonusVehicles for Onslaught working in UT2Vote. Because the maps with Bonus Vehicles share the same name, UT2Vote now has some Ghost maps. These maps must have a Map Prefix of ECE- So all the maps that have Bonus vehicle capability, rename them to ECE- instead of the normal ONS- maps. You can have both running also for instance: ONS-ArcticStrongHold ECE-ArcticStrongHold Now just set the AltMapPrefix="ECE" in the GameString for Onslaught. AltMapPrefix There is aAltMapPrefix= in every GameType string. This gives the Admin the option of having a different type of game map in each gametype. AltMapPrefix="CTF" in a DeathMatch game will also show all CTF maps in the Vote menu. If the AltMapPrefix= is set to the same Prefix as the standard MapPrefix= then the game will hold 500 maps. If this is blank or has another prefix then there will be a maximum of 250 maps for each prefix. A maximum of 250 maps will be devided amongst the number of prefixes given here. Reserved Admin Spectator Should the server be full, an Admin can send a command from WebAdmin reserving a special Slot for himself. This will allow him to enter the game regardless: In the WebAdmin console, remove the say command and: UT2Vote ?AdminSpec=nickname This will allow an Admin into the game, and close the 'hole' when he leaves. Escape Key bug This is the bug where the Escape key does not work in custom games. If you want UT2Vote to handback the Escape key to Custom games, then add to the GameType= Command string: ?CustomGame=True This will tell UT2Vote not to block the Escape key. This will also help when thawing players in 3SPNs Freon game. NB... It is not advisable to do this for standard UT2004 games. Player Banning It is possible to ban a Player even if he has left the server. The Players nickname will appear in the list below a heading: --- Players already left --- Do and Donots -TF-Maul Mapnames DefaultGameName= ServerMuts= ServerLine= |
|
UT2Vote57 Changes in 5.7 Changes and Fixes in UT2Vote57 Map Count Fixed the problem where the last map (250) was left out. Clan Maps Fixed problem with Clan Map sorting. Fixed problem with ClanSetup menu monitoring paused game. Fixed problem where clan map download timer expired prematurely. Admin Game Settings Fixed the problem where the Admin could not correctly set the options in the AdminGame Menu. Admin Leaving Server Fixed the problem where the Admin was not removed from the Admin list when leaving a Server. Tickrate Added ?Tickrate= option to each GameType string to adjust server tickrate. Top 10 Maps Increased to a maximum of 30 maps depending on mapname length. WaitForLevel This option has been put back in the IniOnly section and is used for slower servers that tend to dump their players if the level takes to long to changeover. Default is 60, but if difficulties are experienced, this should be incresed to 90. Spectator Spying. This is a new feature which has been added both Serverside and Clientside. When enabled on both sides and a Spectator is viewing a player, that Player will be notified via a message on his/her screen that they are being viewed. When the Spectator switches their view to another player, the previous player will also be notified that he/she is no longer being viewed by that particular player. Settings [UT2Vote57.UT2VoteIniOnly] bSpectatorSpy=True If the Admin sets this serverside setting as False all Spectator Spying will be disabled regardless of the Clientside settings. ClientMenu Allow Spy Messages Here the player has the option of checking or unchecking this option. If unchecked no messages will appear should a spectator be viewing this player. |
|
Message Coloring Colors are in the format of R (Red) . G (Green) . B (Blue) . A (Brightness) Some examples of color settings are as follows:
For more colors see: http://www.tayloredmktg.com/rgb/ NB.. Any errors entered and the Message Color will revert to Silver : 200.200.200.255 |