| |
| |
|
|
| new stuff | older stuff | | | wait a minute | i can't wait |
|
Rules for running a Medal of Honor: Allied Assault multiplayer server 1. Type normally. This means not using "u" or "ur" or "welcome 2 my server." Typing in shorthand gives you the appearance that you don't give a fuck about what people do in your server. 2. Know how to use the console effectively. Learning how to use the "clientkick" command is pivotal. Some other useful commands include "status," "ban," "cvarlist," "cmdlist," and "set." 3. Kick laggers. Laggers ruin the experience for everyone else on your server. If you feel compassionate towards one with an archaic dial-up 56K modem, at least ask them to reconnect; sometimes it solves connection problems. 4. Kick racists. You should also kick sexist, homophobic, and religiously discriminatory clients. There is no place for discrimination in a game, even a WWII one. 5. Kick shotgunners. The only use for a shotgun is to teach a noob in what direction to shoot. Otherwise, it's useless. No range, no power. Only skilless freaks use this weapon. 6. Set a realistic player limit. Setting your server to accept 16 connections while on a cable modem is a death sentence, both to you and your clients. You will waste bandwidth, and waste the time of your clients. Here's a little chart that I think will work for your player limits: Dial-up: Don't run a server. Get with the program and get broadband, Amish-boy. 7. Always run a dedicated server. If the admin is playing alongside of his clients, it slows down the game a lot. If you want to run a server, always run it dedicated; none of this "admin is also a client with a 0 ping" bullshit. 8. Find a server rental place. Paying for a server is by far the best way to run without lag. If you have free access to a DS3 line, even better! Set up a server and make a clan. So there you have it: how to run a Medal of Honor, Allied Assault multiplayer server. |
Work hours: (Week of 09.05.04 - 15.05.04)
|