PDA

View Full Version : Server Error on Game Browser


Kanuval
05-04-2004, 12:23 PM
My clan has been running serveral call of duty servers and have always had a population problem on one of them. Now that we have closed all of the except one it's time to find out whats going wrong. When we have a group of lets say 6 players on the server and someone else comes to join us, they say the server browser shows either 0 or 1 player on the server. That would explain why we can never get players to join anymore, the server looks empty.

Our server is located at 207.202.48.76:28960

Could someone either verify the player number issue or suggest might be wrong/how to fix it? If anyone has a clue how to fix this and needs more info I can post the configs here.

HOLYMirvic
05-04-2004, 03:44 PM
The number of players that will show in the game browser, depends on the number of public slots you have in your config file.
eg. 10 public slots and 5 private will show only a 10 player server, and if 5 players go in but use the password it will show 0/10 in the game browser, even if there are 5 players on it. So how about trying to join without the password, have you tried that?

Anex
05-04-2004, 03:45 PM
Are they connecting to private slots?

Private slots are not shown in the in-game brower so it's possible even people connected to private slots are not shown. Have one player connect to a private slot, 2 connect to a public slot, then check your server in the in-game browser and see what it shows.

HOLYMirvic
05-04-2004, 03:47 PM
Didn't I just say that? :P

Anex
05-04-2004, 07:31 PM
Guess we were typing at roughly the same time...only a minute apart from each other :!:

I like mine better though :P

HOLYMirvic
05-04-2004, 07:48 PM
LMAO :wink:

Kanuval
05-18-2004, 09:38 PM
Been away for awhile on business, sorry not to reply sooner. On the server I don't have any private slots set up, and we don't use any passwords. The browser shows our 0/16 player count even if its 2 members and 1 public guy. Is there something that would cause it to not refresh properly in the config or some other setup? This problem has been stumping everyone I know and it's a fairly recent thing because I know for a fact that the # used to show correctly.