[msleeper]

I've looked at your code in Scripting (or wherever it's at) for the end of map stats and it is really cool. I don't particularly want to go that route for a few reasons, most of all because if someone leaves before a map is finished then they lose any progress they have made since then.

I myself ran into an issue of SQL transactions bogging down the game, and I have implimented a periodic update for Common Infected kills. Any Common Infected kills that a player gets are stored in a temporary array, and after a set period - 90 seconds by default - a single SQL query is made with the total amount for the past 90 seconds and the array is cleared. It also updates when a player disconnects and when a Safe House is reached, so that kills and points are not lost.

If you do have issues, let me know, but hopefully you shouldn't.

[teddyruxpin]

I was meant more that you could create a timer to check that netprop data every 5 seconds or so and collect the updated number vs having to capture and process every infected death event. In the end your getting what you need which is the total number of kills for the common infected and headshots against them.

I have this plugin running now on one host and will install it on 6 more here in the next 24 hours. All will share the same DB so the ranks will be spread across the hosts in more of a global style instead of per server.

http://stats.blacktusklabs.com/l4dstats/index.php

-Teddy

[msleeper]

What are the specs on your MySQL server? I am running 17 L4D servers running this plugin and 3 TF2 servers running TF2 stats (plus SQL Admins and SourceBans on all of them), and I have not had any issues. And my web/MySQL server is not remotely beefy at all.

[teddyruxpin]

Originally Posted by msleeper What are the specs on your MySQL server? I am running 17 L4D servers running this plugin and 3 TF2 servers running TF2 stats (plus SQL Admins and SourceBans on all of them), and I have not had any issues. And my web/MySQL server is not remotely beefy at all.

MySQL is running on the same host as the srcds are running on which is a Dual Woodcrest 3ghz with 4gb RAM and 73gb SAS disks and Win2k3. The web side is running on a small 64mb VM with CentOS and Apache. I do not suspect the hosts hardware I am using will have any sort of issue I was more concerned about the sheer number of events and updates that will be taking place for the common kill rates we see.

To put it in perspective where default is '30' common per rush I have it set to 100-200. For the 'rest' period between rushes I have it down from 60-90 seconds to 10-60 seconds and megamob sizes set to 250. It is very easy to mow down several hundred common zombies in a few seconds.

I am installing it now on the 6 other hosts and will be able to see how well it works by this time tommorow as the hosts are staying pretty full lately.

-Teddy

[ApocalypseDan]

Great Looking I have HLstatsX On My Sever and Yours Looks As If It Logs All relevnt Information Except Weapon logging it would be nice to see that as well
But Keep Up The Good Work Guys ;)

[Earl_CG]

Looks very promising guys. Looking forward to the Versus version.

[kingpin]

can this handle multiple servers (i.e. via -fork) or single server only?

[msleeper]

It can handle multiple instance servers (IE, Windows) or fork servers without any issue. I am running 4 fork servers without any problem at all.

[kingpin]

OS : ubuntu 8.04 - 64
sourcemod : 1.2.0-hg2534

tried with minimal plugin list i.e. :

• 01 "Sound Commands" (1.2.0-dev) by AlliedModders LLC
• 02 "Admin Help" (1.2.0-dev) by AlliedModders LLC
• 03 "Basic Chat" (1.2.0-dev) by AlliedModders LLC
• 04 "L4D Stats" (1.0.0) by msleeper
• 05 "Admin File Reader" (1.2.0-dev) by AlliedModders LLC
• 06 "Admin Menu" (1.2.0-dev) by AlliedModders LLC
• 07 "Basic Info Triggers" (1.2.0-dev) by AlliedModders LLC
• 08 "Tag Protection" (1.21) by InstantDeath
• 09 "Basic Commands" (1.2.0-dev) by AlliedModders LLC
• 11 "Advertisements" (0.5.5) by Tsunami
• 13 "Basic Votes" (1.2.0-dev) by AlliedModders LLC
• 14 "Basic Ban Commands" (1.2.0-dev) by AlliedModders LLC
• 15 "Anti-Flood" (1.2.0-dev) by AlliedModders LLC
• 16 "Basic Comm Control" (1.2.0-dev) by AlliedModders LLC
• 17 "Client Preferences" (1.2.0-dev) by AlliedModders LLC

and with expanded list (adding unscrambler, voteguard, gore etc.)

issue : plugin announces if there arent enough humans that its disabled. however if there are enough humans nothing responds ingame, rank or top10 doesnt respond and there are no kill announcements. the DB has no info in it, the players table stays empty.

I used the precompiled version attached AND also compiled one from source. still same issues. Console shows the following :

#01:Unknown command "sm_stats_enabled" #01:Unknown command "sm_stats_startpoints" #01:Unknown command "sm_stats_displaymode" #01:Adding master server 72.165.61.189:27011 #01:Adding master server 68.142.72.250:27011

DB conf :

"l4dstats" { "driver" "mysql" "host" "localhost" "database" "srcds" "user" "user" "pass" "****" }

I checked the username/password combo and it works fine outside of sourcemod/this plugin.

thank you.

[teddyruxpin]

Been running this a couple days now and got some basic info below with about 500 players in the database now and some amount of stats for each of them.

http://stats.blacktusklabs.com/l4dstats/maps.php

I was playing on one of the hosts last night and I was seeing some shuttering / choppiness whenever a large horde would come in and get mowed down by us. I am still trying to determine if this is just because of the sheer scale of the mobs or because of the processing of the events of them getting killed. I will do some play testing tonight with some other players and confirm.

Regardless the plugin provides some very nice and detailed stats. Love the web feature and the campaign stats above.

-Teddy