Woolf

I'm looking forward to it, though I hope they just get back to basics when it comes to ranks and what not. The ranking restrictions in BF2142/BF2 for server admins are extremely annoying and problematic... I think not including an 'official' ranking system in BF1943 would be the key to it's success. It wouldn't be hard for server admins to setup their own stats anyway.

If someone keeps crying cheater omg hax, we just tell them to shut it or leave. If they continue, we just give'em the boot. It keeps us from having to listen to them and let's our players know that we care about them, so everyone's happy. The accuser usually doesn't come back, heh.

My guess would be PHP with GD functions - search google for php create image, or search for the function imagecreate(). I say I "guess" because that's the method I use, and I assume the same that MaydaX uses, but it could be different.

When you hover over the first one or copy the link, you'll notice the dot dot dots rather than showtopic.php.

Don't mean to nag, but the "Home" button while on the forum goes to the forum homepage, instead of the main homepage. :(

Can't view the images for some reason.

BE CAREFUL WHEN USING THE SLOT NUMBER! I'd just like to mention that with Battlefield 2 and Battlefield 2142, the game/player slot number is different from the PunkBuster slot number. I haven't tested BF2 yet, but this definitely applies to BF2142, so I could only assume it will do the same in BF2. If you look in the player list tab in-game and see the - # by their name, that is their BF2/BF2142 slot ID. Their actual PunkBuster ID is one number higher. This is due to BF2/BF2142's slots starting at 0 while PunkBuster starts at 1. Also note there are two different commands for kicking by slot number. BF2/2142 Command: admin.kickplayer # PunkBuster command: pb_sv_kick # reason If you want to kick via PunkBuster, first issue a pb_pblist command. Find the slot number of the player you want to kick. As an example, let's say you want to kick someone with the PB slot number of 5. Type the following in the console: rcon exec pb_sv_kick 5 Hacking Player -- this would kick the person with the PB slot number of 5 for the reason of Hacking Player. Issuing the command exactly as above is for use in-game only. If you are issuing it via BF2CC, try exec pb_sv_kick 5 Hacking Player (without the "rcon" in front). To kick via the BF2/BF2142 Player Slot # (I would recommend THIS option as you can be absolute certain of the slot number, and you can easily see it in the player's tab) Find the slot number of the player you want in the players tab, as an example, we will kick the person with a slot number of 4. You would then issue: rcon admin.kickplayer 4 . You do not have the option of entering a reason using this command. Issuing it via BF2CC, type: admin.kickplayer 4 . I hope this helps. If it's too confusing, let me know and I'll revise it.

Your config file looks fine. Make sure the server is recognizing it though. To do that, restart your server. Then, after it has restarted, open up your FTP client and connect to your server. Navigate to the /pb/ folder, and then the /svlogs/ folder. Scroll to the bottom if needed, and open the last file there. The contents of the log file will contain all of your loaded server settings at the top. These log files are created every time you restart your server, so if your pbsv.cfg file is being loaded properly, the settings will match the one in the log file. Now, scroll through the settings and see if you can find PB UCON Profile added type=1 mask="64.27.21.46" name="pbbanshub", or something like that. If that line is not found before the settings end (Listening for HTTP PunkBuster Server (v1.659 | A1375 C2.057) Enabled Game Version [1.09.79.0]), then something's probably wrong with your config file. If you PM me your information (or ask me on Xfire [woolf2009]), I can try to help you out.

There's really not much PBBans can do to ban the offending player. All bans require hard evidence, either via streaming log files or screenshots. However, there are other ways to ban the guy. For one, try banning all the player names he uses. Names in BF2142 can't be as easily changed as GUIDs and what not. Mainly thanks to EA's user login system, which only allows five soldiers per account. Essentially, they'd have to delete/create a new soldier each time. I'm sure there's a way around it, but at least banning his player name should help. To ban his player name, use PunkBuster. Enter the following commands in either the BF2CC console or via RCON, or if you manage the PunkBuster files yourself, add it directly to the pbsv.cfg file: pb_sv_badname 0 MrPink pb_sv_badname is the command, 0 is the time in which the player is given before being kicked (in your case, it should be zero), and MrPink is the player name. Now PunkBuster will kick anyone with "mrpink" in their name (I believe it's case-INsensitive). I made a server manager program for BF2142 that has a permanent ban feature. Basically, it bans a player IP, PB GUID, keyhash, clan tag, and their player name. It makes it that much harder for them to join our server. Unfortunately, it's not something I'll be releasing to the public any time soon, so the pb_sv_badname via PunkBuster is your best bet.

I'm not sure about Quake4, but there's a similar bug in BF2142. Sometimes slot #17 doesn't show, and the player isn't recognized by PB at all - no screenshots can be requested and they can't be kicked. It's happened to me, so it's gotta be some sort of bug.

We have our COD4 servers using MorkEye and streaming to PBBans without any problems.

Most people like to dual stream to keep even more hackers off their servers. Sometimes servers only stream to one or the other, so not all the hackers are added to both sites. Dual streaming will ensure that anyone caught on either site will not be able to join your server. Personally, I don't dual stream because I don't like the extremely long ban list at PsB as well as their unupdated Md5 checks, both cause our servers to hang during startup and even crash at times. I have many other reasons as well, but I won't list them here. One thing I can say though: PBBans is the future of the world, so why go any other way? :D

Very nice. This could prove to be quite useful. B)

I haven't heard of any lag issues on any of our three streaming Auto-SS enabled COD4 servers. B)

You can do whatever you can manage to put in the code of the script. I suppose if you have PHP on your server you could manage the screenshots very extensively and even create an entire database on another site for it.