https://wiki.tripwireinteractive.com/api.php?action=feedcontributions&user=Christian+Schneider&feedformat=atomTripwire Interactive Wiki - User contributions [en]2024-03-28T19:19:01ZUser contributionsMediaWiki 1.40.0https://wiki.tripwireinteractive.com/index.php?title=RO2_Dedicated_Server&diff=781RO2 Dedicated Server2012-05-23T16:46:03Z<p>Christian Schneider: /* Downloading the Red Orchestra 2: Heroes of Stalingrad Dedicated Server */</p>
<hr />
<div>== Downloading and Running the SteamCMD Update Tool ==<br />
<br />
# Download the SteamCMD Update Tool:<br />
#* [http://blog.counter-strike.net/wp-content/uploads//2012/04/steamcmd.zip Windows Installer]<br />
# Extract the contents to a directory (Windows example: C:\SteamCmd\). <br />
#: ''Do not extract the contents of the updater tool to the regular Steam Client folder or to a folder that has the older HLDSUpdateTool program.''<br />
# Launch SteamCmd<br />
:: NOTE: To automate this process for future updates, see [[#Automating SteamCmd]].<br />
## Open a command prompt in that directory and start SteamCmd<br />
##* Windows: Type '''steamcmd'''<br />
#:: ''The program will automatically update and enter you in to a '''Steam>''' prompt. Type '''help''' for more information.''<br />
# Log in with your Steam Account. We recommend server admins set up a server steam account for this process.<br />
:: ''You must log out of the regular Steam client in order to properly log in to SteamCMD Update Tool (if you use your personal steam account)<br />
login username password<br />
: 4a. If you receive a Steam Guard error, check your e-mail for your access code and execute the following commands (you'll only need to do this once):<br />
set_steam_guard_code yourcodehere<br />
login username password<br />
: 5. You should see a message stating that you have successfully logged in with your account.<br />
<br />
=== Downloading the Red Orchestra 2: Heroes of Stalingrad Dedicated Server ===<br />
: This describes the process of updating the CS:GO dedicated server application. These steps are required every time the game is updated. To automate this process for future updates, see [[#Automating SteamCmd]].<br />
<br />
: 1. If you aren't proceeding from the previous set of instructions, first launch '''SteamCmd'''.<br />
<br />
: 2. At the '''Steam>''' prompt, set your CS:GO Dedicated Server install directory. <br />
<br />
: Examples:<br />
: Absolute Path:<br />
force_install_dir c:\RO2Server\<br />
<br />
: Up one folder:<br />
force_install_dir ..\RO2Server\<br />
<br />
: In the Steam Command folder:<br />
force_install_dir .\RO2Server\<br />
<br />
: 3. Install or Update RO2.<br />
: If this is your first time installing or if you are trying to verify the integrity of the server files:<br />
app_update 212542 validate<br />
<br />
: If this is simply an update to an existing RO2 dedicated server:<br />
app_update 212542<br />
<br />
: If Tripwire is currently running a beta update of the dedicated server files:<br />
app_update 212542 -beta "branch name"<br />
Where "branch name" is the current beta branch. Currently there is one live dedicated server beta branch:<br />
beta <br />
<br />
: 4. Once finished, type '''quit''' at the '''Steam>''' prompt to properly log off of the Steam servers.<br />
<br />
=== Automating SteamCmd ===<br />
<br />
There are two ways to automate SteamCmd.<br />
<br />
: 1. Add commands to the command line. Example:<br />
<br />
SteamCmd +login user password +force_install_dir ./ro2_ds +app_update 212542 validate<br />
<br />
: 2. Create a script.<br />
<br />
:: a. Put your SteamCmd commands in a text file. Example:<br />
<br />
// update_ro2_ds.txt<br />
//<br />
login user password<br />
force_install_dir ./ro2server<br />
app_update 212542 validate<br />
exit<br />
<br />
:: b. Run SteamCmd with the +runscript option. Example:<br />
SteamCmd +runscript ro2_ds.txt<br />
<br />
== Starting the Server ==<br />
<br />
Classic Casual:<br />
start .\Binaries\win32\rogame te-Apartments?minplayers=0?maxplayers=32? -seekfreeloadingserver<br />
<br />
<br />
= Advanced Configuration =<br />
<br />
Configuring your new Red Orchestra 2: Heroes of Stalingrad server will be very similar to those who have set up any Unreal Engine 3 server (such as UT 3). However to those who are from other engines such as IdTech and Source there are many differences, which we'll cover here. Those who are also looking for specific sever config settings will likely find what they are looking for below.<br />
<br />
=== rogame.ini ===<br />
<br />
''The rogame.ini file can be found under \ROGame\Config\''<br />
<br />
This file controls all the various game elements that can be configured by admins in Red Orchestra 2: Heroes of Stalingrad. From game modes such as Classic or Action to spectating options and death cams, everything can be set up to the admins liking from this file.<br />
<br />
First admins will want to configure this file to update the WebAdmin, server password and other settings that you do have access to. Here is an example of a very simple ROGame.ini settings admins will want to change first:<br />
<br />
: [Engine.AccessControl]:<br />
AdminPassword= "thisisapassword111" // Admins can set any alpha numeric set of characters to create the password<br />
GamePassword= "thisisapassword222" // Admins can set any alpha numeric set of characters to create the password <br />
<br />
: [Engine.GameReplicationInfo]:<br />
ServerName= "Red Orchestra Server" // This is the displayed server name to all players and the server browser<br />
<br />
: [ROGame.ROGameInfo]:<br />
RoundStartScreenTime= "8" // The time at which players will spawn into the game before pre-start time ends. Valid entries are in seconds.<br />
bLANServer= "false" // Set to true if you only want to create a LAN server.<br />
<br />
bBalanceTeams=true - Turn on team balancing.<br />
bAutoBalanceTeamsOnDeath=true - This will only work if bBlanaceTeams=true. It will balance teams only when an player is available to switch teams while dead.<br />
MaxTeamDifference=2 - This will only work if bBalanceTeams=true. It is the maximum size the game will let teams become out of balance.<br />
<br />
RoundLimit=2 - This setting controls how many times a map will be played. Example entries: 1, 2, X where x is 3 and over (best out of x rounds will be played ex: 2/3).<br />
EndOfMapDelay=45.000000 - This setting controls how long the map will wait at the end of a match before switching to the next map<br />
<br />
GameDifficulty=1.0 - This settings controls the bot difficulty if bots are on the server.<br />
<br />
bUseReadySystem=false - This setting globally configures the use of the ready up system. Maps will not start until both teams ready up.<br />
<br />
MaxHeroes16Player=2 - The amount of hero slots per team on a 16 player server.<br />
MaxHeroes32Player=3 - The amount of hero slots per team on a 32 player server.<br />
MaxHeroes64Player=5 - The amount of hero slots per team on a 64 player server.<br />
<br />
bEnableBattlefieldCommissions=true - Enables or disables players recieving in game Battlefield commissions to grab a contested role.<br />
<br />
ServerAdvertisementMessages= - What is written here is printed out in game to all players in the chat window<br />
ServerAdvertisementInterval=30 - How often in seconds the Advertisement Message is sent to the chat area<br />
<br />
MinNetPlayers=1 - How many human players must be on the server before a round will start<br />
<br />
FriendlyFireKillLimit=6 - How many unforgiven TK's a player can have before the server will kick him. <br />
FriendlyFireDamageLimit=800.000000 - How much damage a player can deal to friendlies before being kicked<br />
FriendlyFireScale=1.000000 - Global friendly fire scale. Accepted values are between 0 and 1. 1 being full damage.<br />
FriendlyFireArtilleryScale=1.000000 - Artillery friendly fire scale. Accepted values are between 0 and 1. 1 being full damage.<br />
FriendlyFireExplosiveScale=1.000000 - Grenade and other explosive friendly fire scale. Accepted values are between 0 and 1. 1 being full damage.<br />
FriendlyFireArtilleryPunishScale=0.100000 - How much damage is returned to the user who cased friendly fire via artillery. FF punishment must be on for this to work.<br />
FriendlyFireExplosivePunishScale=0.500000 - How much damage is returned to the user who caused friendly fire via grenade. FF punishment must be on for this to work.<br />
FriendlyFirePunishment=1 - Does the player receive damage for damaging team mates. Accepted values are 0 and 1. 1 is no punishment.<br />
bEnableTeamKillForgiving=true - Allows players to forgive TK's in game by typing NP after being killed.<br />
<br />
FriendlyPlayerNames=2<br />
<br />
PunkbusterServerProfile=2<br />
<br />
bEnableMapVoting=true<br />
MapVotingTime=30.000000<br />
bEnableKickVoting=true<br />
bAnonymousVoteKicking=False<br />
KickVotingTime=30.000000<br />
bEnableRoleVoting=true<br />
RoleVotingTime=30.000000<br />
bUseScoreAsVoteWeight=false<br />
bAllowMidGameVoting=false<br />
MidGameVotingPercentage=50.000000<br />
EndGameVotingPercentage=50.000000<br />
MapRepeatLimit=0<br />
<br />
bEnableVOIP=true<br />
bDisablePublicVOIPChannel=false<br />
bDisablePublicTextChat=false<br />
bEnableDeadToDeadVOIP=true<br />
bPartitionSpectators=true<br />
bPositional3DVOIP=false<br />
bPositional3DVOIPAllHear=false<br />
<br />
RealismLevel=0 - This sets the gamemode for the server. 0 - Realism, 1 - Action, 2 - Classic, 3 - Custom.<br />
SpectatingMode=0<br />
<br />
ReinforcementTimeScale=1.000000<br />
<br />
MinimumHonor=0 - The minimum player honor required to join the server.<br />
MaximumHonor=100 - The maximum player honor required to join the server<br />
<br />
BannerLink=http://www.heroesofstalingrad.com/ServerAd/RO2_ServerTest.png - This is the banner image displayed to players who enter your server.<br />
ClanMotto=Welcome to our Red Orchestra 2 server! - The title message on the welcome page for players who enter your server.<br />
ClanMottoColor=(B=0,G=0,R=0,A=255) - Allows you to color the text of the Clan Motto<br />
ServerMOTD=This is our message of the day ...@nl@@nl@Please enjoy your time on our server@nl@@nl@@nl@This is the last line - Message of the day on the welcome screen. @nl creates a new line<br />
ServerMOTDColor=(B=0,G=0,R=16,A=255) - Allows you to color the text of your MOTD<br />
WebLink=www.redorchestra2.com - Clickable web link on the welcome page.<br />
WebLinkColor=(B=0,G=0,R=16,A=255) - Allows you to change the color of your web link.<br />
<br />
bUseMapList=True - This sets the server to use a custom map list you specify instead of the entire default map list.<br />
<br />
==== Maps ====<br />
<br />
Maps can be set to run by gametype and amount of rounds played. The following is an example map list that can be put in your rogame.ini:<br />
<br />
GameMapCycles=(Maps=("TE-Apartments","FF-Barracks","CD-Station","TE-Spartanovka","TE-CommissarsHouse","CD-RedOctoberFactory","TE-Gumrak","FF-Station","CD-PavlovsHouse","TE-RedOctoberFactory","CD-Barracks","TE-Station","CD-FallenFighters","FF-GrainElevator","TE-Barracks","CD-CommissarsHouse","TE-FallenFighters","CD-Gumrak","CD-Apartments","TE-GrainElevator","CD-GrainElevator","TE-PavlovsHouse","CD-Spartanovka"),RoundLimits=(1,1,1,2,1,3,1,1,1,1,1,2,1,1,1,1,1,1,1,1,1,1,2,3))<br />
<br />
The first part specifies the exact maps and their game types, while the round limits section (which has to match the number of maps in the cycle) determines how many rounds you want each map to play.<br />
<br />
== Setting Up Web Admin ==<br />
<br />
To enable webadmin:<br />
Open ROWeb.ini. In the [IpDrv.WebServer] section set<br />
bEnabled=true<br />
<br />
By default webadmin will listen on port 8080 on the IP of the game server using, but you'll want to customize this port for multiple servers on the same IP. To change this, open ROweb.ini and modify the following line:<br />
ListenPort=8080<br />
<br />
Admins will now be able to log into their servers web admin panel. They can do by either connecting via a local address (if the server is local) or web address (the servers IP) followed by the port. They can use any of their favorite modern internet browsers such as Chrome, Firefox, and IE. An example of what to put in the address bar of the browser is:<br />
192.168.0.100:8080<br />
<br />
They will be presented with a login screen. The default user is: Admin. The password will be whatever was set as the admin pass in rogame.ini. If no admin pass was set, the admin will not be able to log in.<br />
<br />
<br />
<br />
=== Setting up multiple web admins ===<br />
<br />
Open ROWebAdmin.ini and add the following under [WebAdmin.WebAdmin]:<br />
AuthenticationClass=WebAdmin.MultiWebAdminAuth<br />
<br />
Start the server once to generate a new ROMultiAdmin.ini. Now you can either add new admin names and passwords from within the Web Admin itself, or you can add them manually in the file. To do so add the following information for each admin under [Admin MultiAdminData] in ROMultiAdmin.ini<br />
DisplayName= "AdminNameHere" // Punctuation does matter for these names<br />
Password= "123" // Any alpha numeric set of characters will work here<br />
Order= "DenyAllow"<br />
bEnabled= "True" // This enables this admin<br />
<br />
=== How To Use Web Admin ===<br />
Go to [[Web_Admin|web admin]] to find out more details on how to use the system.<br />
<br />
<br />
<br />
[[Category:Red_Orchestra_2_Heroes_Of_Stalingrad]]</div>Christian Schneiderhttps://wiki.tripwireinteractive.com/index.php?title=RO2_Dedicated_Server&diff=780RO2 Dedicated Server2012-05-23T16:45:26Z<p>Christian Schneider: /* Downloading the Red Orchestra 2: Heroes of Stalingrad Dedicated Server */</p>
<hr />
<div>== Downloading and Running the SteamCMD Update Tool ==<br />
<br />
# Download the SteamCMD Update Tool:<br />
#* [http://blog.counter-strike.net/wp-content/uploads//2012/04/steamcmd.zip Windows Installer]<br />
# Extract the contents to a directory (Windows example: C:\SteamCmd\). <br />
#: ''Do not extract the contents of the updater tool to the regular Steam Client folder or to a folder that has the older HLDSUpdateTool program.''<br />
# Launch SteamCmd<br />
:: NOTE: To automate this process for future updates, see [[#Automating SteamCmd]].<br />
## Open a command prompt in that directory and start SteamCmd<br />
##* Windows: Type '''steamcmd'''<br />
#:: ''The program will automatically update and enter you in to a '''Steam>''' prompt. Type '''help''' for more information.''<br />
# Log in with your Steam Account. We recommend server admins set up a server steam account for this process.<br />
:: ''You must log out of the regular Steam client in order to properly log in to SteamCMD Update Tool (if you use your personal steam account)<br />
login username password<br />
: 4a. If you receive a Steam Guard error, check your e-mail for your access code and execute the following commands (you'll only need to do this once):<br />
set_steam_guard_code yourcodehere<br />
login username password<br />
: 5. You should see a message stating that you have successfully logged in with your account.<br />
<br />
=== Downloading the Red Orchestra 2: Heroes of Stalingrad Dedicated Server ===<br />
: This describes the process of updating the CS:GO dedicated server application. These steps are required every time the game is updated. To automate this process for future updates, see [[#Automating SteamCmd]].<br />
<br />
: 1. If you aren't proceeding from the previous set of instructions, first launch '''SteamCmd'''.<br />
<br />
: 2. At the '''Steam>''' prompt, set your CS:GO Dedicated Server install directory. <br />
<br />
: Examples:<br />
: Absolute Path:<br />
force_install_dir c:\RO2Server\<br />
<br />
: Up one folder:<br />
force_install_dir ..\RO2Server\<br />
<br />
: In the Steam Command folder:<br />
force_install_dir .\RO2Server\<br />
<br />
: 3. Install or Update RO2.<br />
: If this is your first time installing or if you are trying to verify the integrity of the server files:<br />
app_update 212542 validate<br />
<br />
: If this is simply an update to an existing RO2 dedicated server:<br />
app_update 212542<br />
<br />
: If Tripwire is currently running a beta update of the dedicated server files:<br />
app_update 212542 -beta "branch name"<br />
Where "branch name" is the current beta branch. Currently there is a dedicated server beta branch:<br />
beta <br />
<br />
: 4. Once finished, type '''quit''' at the '''Steam>''' prompt to properly log off of the Steam servers.<br />
<br />
=== Automating SteamCmd ===<br />
<br />
There are two ways to automate SteamCmd.<br />
<br />
: 1. Add commands to the command line. Example:<br />
<br />
SteamCmd +login user password +force_install_dir ./ro2_ds +app_update 212542 validate<br />
<br />
: 2. Create a script.<br />
<br />
:: a. Put your SteamCmd commands in a text file. Example:<br />
<br />
// update_ro2_ds.txt<br />
//<br />
login user password<br />
force_install_dir ./ro2server<br />
app_update 212542 validate<br />
exit<br />
<br />
:: b. Run SteamCmd with the +runscript option. Example:<br />
SteamCmd +runscript ro2_ds.txt<br />
<br />
== Starting the Server ==<br />
<br />
Classic Casual:<br />
start .\Binaries\win32\rogame te-Apartments?minplayers=0?maxplayers=32? -seekfreeloadingserver<br />
<br />
<br />
= Advanced Configuration =<br />
<br />
Configuring your new Red Orchestra 2: Heroes of Stalingrad server will be very similar to those who have set up any Unreal Engine 3 server (such as UT 3). However to those who are from other engines such as IdTech and Source there are many differences, which we'll cover here. Those who are also looking for specific sever config settings will likely find what they are looking for below.<br />
<br />
=== rogame.ini ===<br />
<br />
''The rogame.ini file can be found under \ROGame\Config\''<br />
<br />
This file controls all the various game elements that can be configured by admins in Red Orchestra 2: Heroes of Stalingrad. From game modes such as Classic or Action to spectating options and death cams, everything can be set up to the admins liking from this file.<br />
<br />
First admins will want to configure this file to update the WebAdmin, server password and other settings that you do have access to. Here is an example of a very simple ROGame.ini settings admins will want to change first:<br />
<br />
: [Engine.AccessControl]:<br />
AdminPassword= "thisisapassword111" // Admins can set any alpha numeric set of characters to create the password<br />
GamePassword= "thisisapassword222" // Admins can set any alpha numeric set of characters to create the password <br />
<br />
: [Engine.GameReplicationInfo]:<br />
ServerName= "Red Orchestra Server" // This is the displayed server name to all players and the server browser<br />
<br />
: [ROGame.ROGameInfo]:<br />
RoundStartScreenTime= "8" // The time at which players will spawn into the game before pre-start time ends. Valid entries are in seconds.<br />
bLANServer= "false" // Set to true if you only want to create a LAN server.<br />
<br />
bBalanceTeams=true - Turn on team balancing.<br />
bAutoBalanceTeamsOnDeath=true - This will only work if bBlanaceTeams=true. It will balance teams only when an player is available to switch teams while dead.<br />
MaxTeamDifference=2 - This will only work if bBalanceTeams=true. It is the maximum size the game will let teams become out of balance.<br />
<br />
RoundLimit=2 - This setting controls how many times a map will be played. Example entries: 1, 2, X where x is 3 and over (best out of x rounds will be played ex: 2/3).<br />
EndOfMapDelay=45.000000 - This setting controls how long the map will wait at the end of a match before switching to the next map<br />
<br />
GameDifficulty=1.0 - This settings controls the bot difficulty if bots are on the server.<br />
<br />
bUseReadySystem=false - This setting globally configures the use of the ready up system. Maps will not start until both teams ready up.<br />
<br />
MaxHeroes16Player=2 - The amount of hero slots per team on a 16 player server.<br />
MaxHeroes32Player=3 - The amount of hero slots per team on a 32 player server.<br />
MaxHeroes64Player=5 - The amount of hero slots per team on a 64 player server.<br />
<br />
bEnableBattlefieldCommissions=true - Enables or disables players recieving in game Battlefield commissions to grab a contested role.<br />
<br />
ServerAdvertisementMessages= - What is written here is printed out in game to all players in the chat window<br />
ServerAdvertisementInterval=30 - How often in seconds the Advertisement Message is sent to the chat area<br />
<br />
MinNetPlayers=1 - How many human players must be on the server before a round will start<br />
<br />
FriendlyFireKillLimit=6 - How many unforgiven TK's a player can have before the server will kick him. <br />
FriendlyFireDamageLimit=800.000000 - How much damage a player can deal to friendlies before being kicked<br />
FriendlyFireScale=1.000000 - Global friendly fire scale. Accepted values are between 0 and 1. 1 being full damage.<br />
FriendlyFireArtilleryScale=1.000000 - Artillery friendly fire scale. Accepted values are between 0 and 1. 1 being full damage.<br />
FriendlyFireExplosiveScale=1.000000 - Grenade and other explosive friendly fire scale. Accepted values are between 0 and 1. 1 being full damage.<br />
FriendlyFireArtilleryPunishScale=0.100000 - How much damage is returned to the user who cased friendly fire via artillery. FF punishment must be on for this to work.<br />
FriendlyFireExplosivePunishScale=0.500000 - How much damage is returned to the user who caused friendly fire via grenade. FF punishment must be on for this to work.<br />
FriendlyFirePunishment=1 - Does the player receive damage for damaging team mates. Accepted values are 0 and 1. 1 is no punishment.<br />
bEnableTeamKillForgiving=true - Allows players to forgive TK's in game by typing NP after being killed.<br />
<br />
FriendlyPlayerNames=2<br />
<br />
PunkbusterServerProfile=2<br />
<br />
bEnableMapVoting=true<br />
MapVotingTime=30.000000<br />
bEnableKickVoting=true<br />
bAnonymousVoteKicking=False<br />
KickVotingTime=30.000000<br />
bEnableRoleVoting=true<br />
RoleVotingTime=30.000000<br />
bUseScoreAsVoteWeight=false<br />
bAllowMidGameVoting=false<br />
MidGameVotingPercentage=50.000000<br />
EndGameVotingPercentage=50.000000<br />
MapRepeatLimit=0<br />
<br />
bEnableVOIP=true<br />
bDisablePublicVOIPChannel=false<br />
bDisablePublicTextChat=false<br />
bEnableDeadToDeadVOIP=true<br />
bPartitionSpectators=true<br />
bPositional3DVOIP=false<br />
bPositional3DVOIPAllHear=false<br />
<br />
RealismLevel=0 - This sets the gamemode for the server. 0 - Realism, 1 - Action, 2 - Classic, 3 - Custom.<br />
SpectatingMode=0<br />
<br />
ReinforcementTimeScale=1.000000<br />
<br />
MinimumHonor=0 - The minimum player honor required to join the server.<br />
MaximumHonor=100 - The maximum player honor required to join the server<br />
<br />
BannerLink=http://www.heroesofstalingrad.com/ServerAd/RO2_ServerTest.png - This is the banner image displayed to players who enter your server.<br />
ClanMotto=Welcome to our Red Orchestra 2 server! - The title message on the welcome page for players who enter your server.<br />
ClanMottoColor=(B=0,G=0,R=0,A=255) - Allows you to color the text of the Clan Motto<br />
ServerMOTD=This is our message of the day ...@nl@@nl@Please enjoy your time on our server@nl@@nl@@nl@This is the last line - Message of the day on the welcome screen. @nl creates a new line<br />
ServerMOTDColor=(B=0,G=0,R=16,A=255) - Allows you to color the text of your MOTD<br />
WebLink=www.redorchestra2.com - Clickable web link on the welcome page.<br />
WebLinkColor=(B=0,G=0,R=16,A=255) - Allows you to change the color of your web link.<br />
<br />
bUseMapList=True - This sets the server to use a custom map list you specify instead of the entire default map list.<br />
<br />
==== Maps ====<br />
<br />
Maps can be set to run by gametype and amount of rounds played. The following is an example map list that can be put in your rogame.ini:<br />
<br />
GameMapCycles=(Maps=("TE-Apartments","FF-Barracks","CD-Station","TE-Spartanovka","TE-CommissarsHouse","CD-RedOctoberFactory","TE-Gumrak","FF-Station","CD-PavlovsHouse","TE-RedOctoberFactory","CD-Barracks","TE-Station","CD-FallenFighters","FF-GrainElevator","TE-Barracks","CD-CommissarsHouse","TE-FallenFighters","CD-Gumrak","CD-Apartments","TE-GrainElevator","CD-GrainElevator","TE-PavlovsHouse","CD-Spartanovka"),RoundLimits=(1,1,1,2,1,3,1,1,1,1,1,2,1,1,1,1,1,1,1,1,1,1,2,3))<br />
<br />
The first part specifies the exact maps and their game types, while the round limits section (which has to match the number of maps in the cycle) determines how many rounds you want each map to play.<br />
<br />
== Setting Up Web Admin ==<br />
<br />
To enable webadmin:<br />
Open ROWeb.ini. In the [IpDrv.WebServer] section set<br />
bEnabled=true<br />
<br />
By default webadmin will listen on port 8080 on the IP of the game server using, but you'll want to customize this port for multiple servers on the same IP. To change this, open ROweb.ini and modify the following line:<br />
ListenPort=8080<br />
<br />
Admins will now be able to log into their servers web admin panel. They can do by either connecting via a local address (if the server is local) or web address (the servers IP) followed by the port. They can use any of their favorite modern internet browsers such as Chrome, Firefox, and IE. An example of what to put in the address bar of the browser is:<br />
192.168.0.100:8080<br />
<br />
They will be presented with a login screen. The default user is: Admin. The password will be whatever was set as the admin pass in rogame.ini. If no admin pass was set, the admin will not be able to log in.<br />
<br />
<br />
<br />
=== Setting up multiple web admins ===<br />
<br />
Open ROWebAdmin.ini and add the following under [WebAdmin.WebAdmin]:<br />
AuthenticationClass=WebAdmin.MultiWebAdminAuth<br />
<br />
Start the server once to generate a new ROMultiAdmin.ini. Now you can either add new admin names and passwords from within the Web Admin itself, or you can add them manually in the file. To do so add the following information for each admin under [Admin MultiAdminData] in ROMultiAdmin.ini<br />
DisplayName= "AdminNameHere" // Punctuation does matter for these names<br />
Password= "123" // Any alpha numeric set of characters will work here<br />
Order= "DenyAllow"<br />
bEnabled= "True" // This enables this admin<br />
<br />
=== How To Use Web Admin ===<br />
Go to [[Web_Admin|web admin]] to find out more details on how to use the system.<br />
<br />
<br />
<br />
[[Category:Red_Orchestra_2_Heroes_Of_Stalingrad]]</div>Christian Schneiderhttps://wiki.tripwireinteractive.com/index.php?title=Template:Pre2&diff=747Template:Pre22012-05-22T00:29:38Z<p>Christian Schneider: Created page with "<pre style="white-space:-moz-pre-wrap; white-space:-pre-wrap; white-space:-o-pre-wrap; white-space:pre-wrap; word-wrap:break-word;">{{{1}}}</pre>"</p>
<hr />
<div><pre style="white-space:-moz-pre-wrap; white-space:-pre-wrap; white-space:-o-pre-wrap; white-space:pre-wrap; word-wrap:break-word;">{{{1}}}</pre></div>Christian Schneiderhttps://wiki.tripwireinteractive.com/index.php?title=Tripwire_Interactive_Wiki:Copyrights&diff=438Tripwire Interactive Wiki:Copyrights2012-03-22T20:17:45Z<p>Christian Schneider: /* Trademarks */</p>
<hr />
<div>== Tripwire Interactive Wiki: Terms of Use ==<br />
<br />
The Official Tripwire Interactive Wiki is an online, public collaboration of information about [http://www.tripwireinteractive.com/ Tripwire Interactive]'s video game library which includes, [http://www.heroesofstalingrad.com Red Orchestra 2] and [http://www.killingfloorthegame.com Killing Floor]. Any information found on this website is created by the voluntary efforts of individual players and groups working to develop a comprehensive information resource for all ''[[Tripwire Interactive]]'' fans to use and enjoy. “Tripwire Interactive”, as used in these Terms of Use, means Tripwire Interactive, LLC. and its successors and assigns.<br />
<br />
This website is an open wiki. It allows anyone who has signed up to the wiki to create and alter its articles and content. Please note that articles and information found within this wiki have not necessarily been reviewed by members of the ''[[Tripwire Interactive]]'' development team, or any employees of Tripwire Interactive, . <br />
<br />
Although much of the information presented on the Official Tripwire Interactive Wiki will be accurate and up-to-date, Tripwire Interactive cannot guarantee the validity and quality of the information. It should be understood that the content of any article may be modified or changed at any time by any member of the community. It should also be understood that any wiki page has a risk of becoming vandalized or improperly altered by users. <br />
<br />
To maintain a sense of community on this user-contributed resource, it is encouraged that any user encountering improper, offensive, or otherwise incorrect information simply take the time to edit the article in question and correct the problem. If any situations arise that warrant further involvement, they should be reported directly to the Official Tripwire Interactive Wiki moderators for review. <br />
<br />
<br />
=== Contributions, Licenses & Assignments ===<br />
<br />
Each contributor to the Official Tripwire Interactive Wiki represents that the contributor’s contribution is original and does not infringe upon the intellectual property rights of any third party, and the contributor agrees to license or assign it as follows:<br />
<br />
Any contributor hereby assigns all right, title, and interest, including without limitation all intellectual property rights, to that any contribution they make to the Official Tripwire Interactive Wiki to Tripwire Interactive, LLC. and its successors and assigns (collectively “Tripwire Interactive”) and it shall be deemed the property of Tripwire Interactive (This enables Tripwire Interactive to use such contributions in its games). <br />
<br />
Contributors to the Official Tripwire Interactive Wiki may also post content obtained from Killing Floor, Red Orchestra, Red Orchestra 2, its websites, manuals and guides, concept art and renderings, press and fansite kits, and other such copyrighted material that Tripwire Interactive has made available to the general public, to the Official Tripwire Interactive Wiki. Such content is not licensed pursuant to the [http://www.gnu.org/copyleft/fdl.html GFDL] and all right, title and interest in and to such content and contributions posted within or to the Feedback Namespace shall remain with Tripwire Interactive, as applicable.<br />
<br />
By using the Official Tripwire Interactive Wiki, each contributor agrees that any contribution the contributor makes is provided voluntarily and freely with no right to or expectation of content preservation or compensation from Tripwire Interactive. None of Tripwire Interactive's, or any of their respective employees, agents or representatives, is responsible if any contributor should change, edit, modify, or remove any information that a contributor has posted on the Official Tripwire Interactive Wiki. <br />
<br />
<br />
=== No Formal Developer Reviews ===<br />
<br />
While members of the Tripwire Interactive development team can and do access the Official Tripwire Interactive Wiki, it should be understood that all articles cannot be officially reviewed at all times. Our community of editors use resources such as the Special:Recentchanges and Special:Newpages feeds to monitor new and changing content. <br />
<br />
It should be clearly understood that the Official Tripwire Interactive Wiki is not consistently reviewed by official Tripwire Interactive developers. While all Tripwire Interactive employees may correct errors or engage in casual peer review, they have no legal duty to do so and thus all information read here is without any implied warranty of accuracy for any purpose or use whatsoever. Due to open community access to the Official Tripwire Interactive Wiki, even articles that have been reviewed by official employees of Tripwire Interactive may later have been edited inappropriately, changing their original content. <br />
<br />
None of the contributors, sponsors, administrators, developers or anyone else connected with the Official Tripwire Interactive Wiki in any way whatsoever can be held responsible for the appearance of any inaccurate or libelous information or for your use of the information contained in or linked from these Web pages. <br />
<br />
<br />
=== Trademarks ===<br />
<br />
Any of the trademarks, service marks, collective marks, design rights, personality rights, or similar rights that are mentioned, used, or cited in an Official Tripwire Interactive Wiki article are the property of their respective owners. Their use here does not imply that you may use them for any other purpose other than for the same or a similar informational use as contemplated by the original authors of these articles under the GFDL licensing scheme. <br />
<br />
Unless otherwise stated, the Official Tripwire Interactive Wiki is neither endorsed nor affiliated with any of the holders of any such rights, and as such Tripwire Interactive cannot grant any rights to use any otherwise protected materials. Your use of any such or similar incorporeal property is at your own risk. <br />
<br />
It should be understood that Tripwire Interactive®, the Tripwire Interactive logo's, Killing Floor and the Killing Floor logo, Red Orchestra® and the Red Orchestra family of logo's, tripwireinteractive.com, redorchestragame.com, killingfloorthegame.com, heroesofstalingrad.com, redorchestra2.com and all associated logos and designs are trademarks or registered trademarks of Tripwire Interactive LLC.</div>Christian Schneiderhttps://wiki.tripwireinteractive.com/index.php?title=MediaWiki:Copyright&diff=372MediaWiki:Copyright2012-03-22T17:26:19Z<p>Christian Schneider: </p>
<hr />
<div>wiki.tripwireinteractive.com's content is available under $1.</div>Christian Schneiderhttps://wiki.tripwireinteractive.com/index.php?title=Tripwire_Interactive&diff=321Tripwire Interactive2012-03-20T21:08:46Z<p>Christian Schneider: /* A History */</p>
<hr />
<div>==Welcome to the Tripwire Interactive Wiki==<br />
<br />
This wiki is here to be a helpful tool to the various Tripwire Interactive game communties as a centralized location to find out information about the games that they enjoy. It also will hopefully serve as a repository of information to modders, so they may never have to search through a forum for obscure information again.</div>Christian Schneiderhttps://wiki.tripwireinteractive.com/index.php?title=Tripwire_Interactive&diff=29Tripwire Interactive2012-02-14T20:18:09Z<p>Christian Schneider: /* Getting started */</p>
<hr />
<div>==Welcome to the Tripwire Interactive Wiki==<br />
<br />
This wiki is here to be a helpful tool to the various Tripwire Interactive game communties as a centralized location to find out information about the games that they enjoy. It also will hopefully serve as a repository of information to modders, so they may never have to search through a forum for obscure information again.<br />
<br />
<br />
==A History==<br />
<br />
<br />
<br />
'''MediaWiki has been successfully installed.'''<br />
<br />
Consult the [//meta.wikimedia.org/wiki/Help:Contents User's Guide] for information on using the wiki software.</div>Christian Schneiderhttps://wiki.tripwireinteractive.com/index.php?title=Tripwire_Interactive&diff=28Tripwire Interactive2012-02-14T20:17:48Z<p>Christian Schneider: /* Getting started */</p>
<hr />
<div>==Welcome to the Tripwire Interactive Wiki==<br />
<br />
This wiki is here to be a helpful tool to the various Tripwire Interactive game communties as a centralized location to find out information about the games that they enjoy. It also will hopefully serve as a repository of information to modders, so they may never have to search through a forum for obscure information again.<br />
<br />
<br />
==A History==<br />
<br />
<br />
<br />
'''MediaWiki has been successfully installed.'''<br />
<br />
Consult the [//meta.wikimedia.org/wiki/Help:Contents User's Guide] for information on using the wiki software.<br />
<br />
== Getting started ==<br />
* [//www.mediawiki.org/wiki/Manual:Configuration_settings Configuration settings list]<br />
* [//www.mediawiki.org/wiki/Manual:FAQ MediaWiki FAQ]</div>Christian Schneider