PDA

View Full Version : Unable to set up private password


Navy
04-25-2004, 04:30 AM
Hi,

We have started a new gamehosting company for mohaa and everything works fine untill the private server demand.
It seems that when we are setting up an private server it can't be protected with an password. Every server is running on an separate ip with its own cfg files. The main cfg file is called server file with at the end executing an Objective cfg file for the public server, this works great.
But when it is an private server it would execute an private.cfg file with the pass but this doesn;t work.

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

Example server cfg:
//Set the cvars in this file for your server!
// Public Info

exec "public.cfg"

// General Settings

seta sv_fps "20"
seta sv_timeout "120" //amount of time before assuming a disconnected state
seta sv_precache "1"
seta sv_fps "20" //max frame rate to clients - increasing will raise pings
seta sv_maxRate "9000"
seta sv_maxclients "17"
seta g_maxGameClients "0"
seta sv_privateClients "17"
seta sv_allowDownload "1"
seta sv_reconnectlimit "3"
seta sv_zombietime "1"
seta g_inactivity "180"
seta g_forcerespawn "30"
seta g_syncronousclients "0"
seta sv_chatter "1"

// Server Network Settings

set net_ip "213.197.58.203"
set sv_flood_waitdelay "10" //not too sure on this, possibly time before flooder is allowed to type again (default)
set sv_flood_persecond "4" //messages per second to be considered a flood ?? (default)
set sv_flood_msgs "4" // ?? (default)

net_noipx "1" //Disallows IPX connections, TCP only (network protocol)

// Logs

seta g_log "logs/games.log"
seta logfile "1"
seta g_logsync "0"

// Extras

seta sv_maxPing "300"
seta sv_minPing "0"
seta sv_floodProtect "1"

// Server Passwords

seta rconPassword "xxxxx"
seta sv_privatePassword "xxxxx"
seta password "xxxxx" // Player password


// Game Type Settings - ATTN-May be overwritten by MOH config file below
// Set the type of game: 1=Deathmatch 2= Team match 3 = OBJ 4 = Roundbased

seta g_gametype "4"
seta timelimit "20"
seta fraglimit "0"
seta cheats "0"
// seta capturelimit "6"
seta sv_gamespy "1" // Show our server in gamespy

// Game Play Default Settings
//seta g_gravity "800"
//seta g_knockback "1000"
//seta g_quadfactor "3"
//seta g_speed "320"
//seta g_weaponRespawn "5"
//seta g_weaponTeamRespawn "30" //respawn time in seconds for team games
//seta dmflags "0" // 8 (no falling damage) 16 (fixed FOV) 32 (no footsteps)

// Match Settings

seta g_doWarmup "1"
seta g_warmup "20"

// Team Preferences
seta g_teamAutoJoin "0"
seta g_teamForceBalance "1"
// seta g_friendlyFire "0"
seta g_teamdamage "0" // FF on or Off 1 = on

// Voting
seta g_allowVote "0"

// Start the Maprotatin/Game
// seta sv_maplist "dm/mohdm1 dm/mohdm2 dm/mohdm3 dm/mohdm4 dm/mohdm2 dm/mohdm1 dm/mohdm5 dm/mohdm6 dm/mohdm7"
// map dm/mohdm2

// Exec MOHAA specific game setup
// Can exec any of the 4 configs team/round/object/ffa
exec private.cfg

// writeconfig q3config.cfg // doesnt seem to be necessary in moh?
// wait

// Banned Players
seta g_filterBan "1"
exec "banned.cfg"

----------------------------------------------------
Example private cfg:


// ATTENTION: CLANSERVERS SHOULD BE PASSWORD-PROTECTED AT ALL TIMES!


// General Server Info Settings

seta sv_hostname "xxxxxxxxxxxxxxxxx"
// Map rotation
seta sv_maplist "obj/obj_team1" //Standaard objective maplist
//seta sv_maplist "dm/mohdm2 dm/mohdm3 dm/mohdm4 dm/mohdm6 dm/mohdm7" //Standaard DM maplist
// Server Settings


cheats 0
timelimit 20 // Round time (in minutes)
seta g_allowjointime "5"
seta g_allowvote "1"
seta g_gametype "4"
// Gametype
// "1" = DM,
// "2" = Team DM
// "3" = Round-based match
// "4" = Objective game
seta g_teamdamage "0" // Friendly fire (1 is on, 0 is off)
seta g_teamForceBalance "0"
seta sv_gamespy "1" //* Show our server in gamespy
// Master Server Settings
seta sv_master1 "mohmaster.2015.com"
seta sv_master2 "master0.gamespy.com"
seta sv_master3 "master1.gamespy.com"
// Start with the map rotation
map obj/obj_team1
//map dm/mohdm1

------------------------------------------------
So my question is what is wrong?
Server is running on a dual proc 2.6 ghz xenon
Ram 2gb
connection glassfiber internal 100mbit
If somebody can help us out we will be very grateful.
Tnx in advance
Navy

Paratrooper
04-26-2004, 06:55 AM
Are you using MOHAA RUnner to create these cfg's? I couldnt get it to work when I was using that but when I edited the cfg myself it worked fine.

SNYPE
04-26-2004, 09:28 AM
I dont use that methid to make servers private, I have heard that it is unreliable and does not always work.
Why not just set sv_privateclients equal to sv_maxclients in your Private cfg? That way everyone will need to use the PrivatePassword in order to join the server.

GaSplat
04-26-2004, 11:31 PM
Your server.cfg is the only place you are setting the password. private.cfg is setting gametypes and map rotation and master servers (which is unlikely to change for a private server, but hey, do what feels right).

i pulled these from your server.cfg:

seta sv_maxclients "17"
seta sv_privateClients "17"

seta sv_privatePassword "xxxxx"
seta password "xxxxx" // Player password

According to this, everyone should need your private password since you have no public slots (privateClients come out of the maxclients). The regular password is useless since their are no public slots to use it. This is basically what Snype is suggesting. The players will simply have to use whatever you set as a privatePassword for their password (clients do not set privatePassword, they set password using whichever one you have told them to use).

Here is an example of how to set a 17 slot server that is password protected for 15 slots, and uses a privatePassword for the 2 private slots.

seta sv_maxclients "17"
seta sv_privateClients "2"
seta sv_privatePassword "privateOne"
seta password "anyOne" // Player password

Now in the player's client, if they use the password "anyOne" they will get into one of the 15 slots that are open.

If they use the password of "privateOne" they will get into either of the two private slots. Note that on the client you do not set privatePassword. Just password (using the same word as the server has for privatePassword) in order to get into a private slot. Using the private slot and privatePassword also works well with non-password protected servers to "guarentee" a slot for password holders. With a password protected server, if both private slots are already full, they may have to try the regular password to get in - not sure, have rarely used both private passwords and regular passwords at the same time.