An FPS Server guide for developers It's not rocket science and to be honest, most if not all of these features have been around for some time. However we keep seeing new games released, with a lot of these basic features missing. Click here to view the list of features we've been asking for since 2001
Please use this thread to leave feedback or be part of the continued discussion on what admins need to run a successful game server.
I've been informed that the gerbil that keeps the site running is about to retire of old age and my server is EOL.
I'll be moving over to a newer box in the coming weeks so you may see some downtime while the DNS propagates IP addresses throughout the different DNS servers across the world.
As we get closer I'll have more info on when to expect the move. While we don't experience any speed issues or even down times. I don't want the site to be off line because they can't find replacement hardware or another gerbil
Who knows we may even update the forums to the latest version of vB4.1.10 (which I've been playing around with and testing for the past 2+ years - lets just say vBulletin is just getting around to making the software useable )
One of our members sent me a link to the following job posting over at Monster.se
Role overview:
In our continued effort to keep our games free from cheating, we are now looking for an Internet savvy administrator.
The administrator will compose an absolutely vital function to secure the online experience our games represent by actively be a part of the community and keep up to date with the current cheat exposure. The administrator will also own the analytical work with our player behavior data to keep our leaderboards and game play filled with fair play.
- More information and to apply check out this link
Josh from PMOH sends word that they are setting up a server this weekend to play some good old classic Medal of Honor Allied Assault
PMoH and MoHAA's 10th Anniversary Celebration Weekend!
Hey Everyone!
So, Allied Assault turned 10 last weekend, and this weekend Planet Medal of Honor turns 10. So in honor of both, we're playing Allied Assault all weekend.
Below are the servers we'll be using and what's going to be going on.
So first off starting at 12:00pm PST Saturday I'll be streaming MOHAA SP at http://www.twitch.tv/dontcallmekelso. So click to watch, I'll be talking while I play, maybe answer some questions, maybe give something away.
Second we've got a whole boatload of server thanks to Clanwarz.
94.46.240.48:12203 - San Jose (I'll be on this one the most)
82.96.64.112:12203 - Chicago
72.26.198.21:12203 - NY
216.246.110.231:12203 - Germany
205.234.167.132:12203 - Spain
109.70.148.121:12203 - UK
We also have a TS3 server for everyone to hop on!
chicago.clanwarz.com:1108
- I'll be on there later
"Just as we thought the hacking issue with Battlefield 3 couldn’t get any worse, it now appears it has just that: in order to prove their point against PunkBuster, the cheaters and hackers over at ArtificialAiming have banned over 150 Battlefield 3 players by using a PunkBuster exploit. A forum post claims:
"In 2011 we hit them with a mass ban wave and now were are banning real players from battlelog while ggc-stream is totally unaware. We have framed 150+ bf3 players alone"
"There are numerous threads over at Battlelog about this issue, where innocent players have been banned. The issue has to do with PBBans and GGC — third party services that run on the vast majority of Battlefield 3 game servers.
DICE have stated that they’re looking into the issue, but at this point, hackers have pretty much gotten control of the game. And just to make matters worse, innocent players can now be banned with what appears to be a simple command and the user’s BF3 GUID."
Server R18 had a crashbug in it. We have resolved it, and will soon send out server R19 to the RSPs.
A few RSPs will be trialling the server during this evening/morning. The new server update will begin rollout with all RSPs during Tuesday if no gotchas are found.
Changelog
Fixed the most common server crash. The story behind this one is fairly convoluted:
When a player begins the process of joining a server, the server will begin buffering some kinds of information in anticipation of the player completing the loading & joining phase. However, players sometimes get stuck in the loading screen. This makes the server buffer more and more info for that player. A side effect of this is a temporary resource leak in the game server. The leak is immediately restored if the server changes map, or the player completes loading, or the player shuts down the game client. However if a player manages to remain stuck for 30+ minutes in loading on a server with lots of activity and the server doesn’t end the round, then the server could run out of the particular resource – it would then crash.
The new server version will forcibly disconnect clients which are threatening to exhaust that particular resource. With this change in place, we do not know of anything that would make high-ticket servers less stable than normal-ticket servers.
Long banlists will not crash the server.
The banlist supports up to 10.000 entries now. This limit can be raised in the future.
The banList.list command has been modified to return at most 100 entries at a time (similar to how BC2 PC’s banList.list command works).
Any administrative tools will need to be updated to be able to see more than the first 100 entries.