Jump to content

Welcome to Steams România @ Since 2006
Register now to gain access to all of our features. Once registered and logged in, you will be able to create topics, post replies to existing threads, give reputation to your fellow members, get your own private messenger, post status updates, manage your profile and so much more. If you already have an account, login here - otherwise create an account for free today!

Bun venit pe Steams România @ Since 2006

Bun venit pe Steams România @ Since 2006, pentru a avea full acces la forum te rugam sa te inregistrezi.
Ai mai multe motive pentru care sa te inregistrezi:
  • Acces la un forum structurat in parametri profesionali
  • Sansa de a da sau a primi like din partea membriilor
  • Sansa de a face parte din echipa steams
  • Alaturarea unei comunitati de viitor
Inregistreaza-te gratuit, acum!

In caz ca aveti probleme cu activarea/crearea/conectarea contului de pe forum lasati-ne un mesaj aici
Guest Message by DevFuse
 

Submitter

SUPPORT TOPIC File Information

  • Submitted: Jan 14 2013 07:29 AM
  • Last Updated: Mar 07 2013 03:21 AM
  • File Size: 11.93MB
  • Views: 2092
  • Downloads: 34

Download PsychoStats 3.2

* * * * * 1 Votes
PsychoStats PsychoStats 3.2 psychostats-nightly psychostats-nightly.zip psychostats3.2



Screenshots

Introduction

There are several ways to install PsychoStats and choosing the correct process depends on a few factors like where your game server and web server are located. A very common setup is to have a game server running on one machine at a game hosting provider and a web server on another machine in a remote location hosted by another company. While this is a very common setup it is also one of the most confusing for new users. This type of setup will be explained in detail after the basic necessities are explained in the following chapters.

This installation guide has been designed as a walk through. Start at the top and work your way all the way down to the bottom. If a chapter discuses something that you do not need simply skip it and move on to the next chapter.

Minimum Requirements

Before you try installing PsychoStats you need to make sure your system meets the minimum requirements as outlined here. Any software or server that is not above the versions shown here are unsupported. How to install this software will be explained in the next couple of chapters.

These requirements are the bare minimum that ensure PsychoStats will work properly on your system. If you attempt to use older versions you run the risk of stats updates crashing or invalid statistics from being recorded. Users having problems with the software that are running older versions of these requirements can not be supported.

Required Server Software

  • Web server (usually Apache or IIS)
  • PHP v4.3 or any version higher.
  • MySQL v4.1.11 or any version higher.

Windows

Linux

Required Perl modules

  • DBI (v1.4 or higher)
  • DBD::mysql (v3.0002 or higher)

Optional Perl modules

  • Net::FTP - This is only required if you need to download logs from a remote FTP server (chances are this will be installed by default with your version of Perl).
  • Net::SFTP - This is only required if you need to download logs via an SFTP server (secure SSH file transfer protocol).

Optional Perl modules for Heatmaps

These modules are only required if you want to generate Heatmaps for your map statistics.

  • GD
  • XML::Simple

Installing Perl on Windows

Perl is required in order for PsychoStats to work. If you try to run stats.pl and Perl is not installed on your system then all you'll see is a Notepad window open with the source code of the file. Which is completely useless to you. So read on my fearless readers!

This chapter is for users who wish to run PsychoStats on their Windows machines. If you will be running on a Linux server then you can skip to the next chapter, after all if you're on a Linux server that doesn't have Perl installed then your server has some serious issues and you need take a sledgehammer and 'fix' it.

For users that have a separate game and web server more details on where to install what will be explained later. But for now, the basics of how to get ActivePerl installed will be explained below.

Download ActivePerl

First things first. You need to download a copy of ActivePerl (hint hint! click that link!).

On that download page you'll see a lot of choices to choose from and it can be quite confusing. The Windows downloads are closer to the bottom of the list. The image to the right shows what it might look like. The highlighted entry is the one you want to download if you're running a standard version of Windows. If you're running a 64bit version of Windows, then obviously download the 64bit version of ActivePerl instead.

You want the 'MSI' package shown and not the AS package because the Windows AS package provides NO uninstall functionality, and is recommended only if you are unable to install ActivePerl using the MSI installer.

Install ActivePerl

Double-click the file you downloaded and start the installation for ActivePerl. Installation is easy, just accept all defaults, there isn't much you can customize in the ActiveState installation anyway. After it finishes installing I recommend rebooting your computer once before proceeding. Don't worry, I'll be here.

Now that you have Perl installed you'll need to make sure the required Perl modules are also installed. Lucky for you this is very simple. Read on to the next chapter!

Install Perl modules with the PPM GUI

ActivePerl (as of v5.8) comes with a GUI that allows you to easily search and install modules, as seen to the right. Click on the image to the right to view the full size image. The screenshot has been annotated with numbers depicting the order of what to click to install the modules. If the GUI is not your style, then see the next chapter for details on installing the modules using the command line ppm program that comes with ActivePerl.

Order of steps to perform in the screenshot

  1. 1. Select 'uninstalled modules' button
  2. 2. Type in the module name
  3. 3. Highlight the module to install
  4. 4. Select the 'add to install' button
  5. 5. And finally, click the 'run' button to have the modules installed.

Install modules from DOS prompt

Even the PPM GUI can be a little confusing to some users, so ActivePerl has an alternate method to install modules from your DOS prompt which is probably even easier than using the GUI. All it takes is a single command for each module.

Go to your "Start" menu on your Taskbar, then click on "Run" and in the run window that opens type in "cmd". This will open an empty DOS window. Now type in the following commands in order:

  1. ppm install DBI
  2. ppm install DBD-mysql

Example output:

C:\Documents and Settings\Timmy>ppm install DBD-mysql
Downloading DBD-mysql-3.0002...done
Unpacking DBD-mysql-3.0002...done
Generating HTML for DBD-mysql-3.0002...done
Updating files in site area...done
 14 files installed

Your Web Server

In order to view your PsychoStats player web site you'll need a web server capable of displaying the pages. Almost any web server will suffice but it must have PHP v4.3+ (with the MySQL extension enabled). This documentation will not go into detail on how to enable these extensions, the PHP documentation is very detailed, so please visit the links.

If you already have a web host then you're in good shape and chances are your web site already supports PHP and MySQL. If you're not sure you can ask your hosting provider.

If, however, you will be running the web site off of your home machine, or another server that you maintain and it doesn't already have a web server running you will need to install one. Whether you're on Windows or Linux, I highly suggest installing Apache. Using IIS on Windows has a few quirks that cause a lot of problems for PsychoStats working properly on some systems (mainly user permissions that are confusing).

If someone would like to contribute detailed instructions on properly setting up IIS, please feel free to fill out this documentation with the steps required. But please keep the formatting in sync with the rest of the document.

Before you get too deep in how to install Apache on your server there's a better way to handle this. There's a simple way to get Apache, MySQL and PHP all installed with a single click of a button (ok, maybe a few clicks of a button). A premade Windows system that runs Apache, MySQL and PHP is called a WAMP (Windows ApacheMySQL PHP). The wonderful folks over at the wampserver.com (french) web site (english) have pre-packaged up an entire software suite that combines all of the latest software with a single Install Wizard that installs and sets it all up for you.

It even includes a nice little "systray" utility that allows you to manage the various server configurations and enabling extensions w/o modifying any configuration files directly. The Wamp Server also comes packaged with some useful utilities, like phpMyAdmin which allows you to administer your MySQL database from a web interface. And don't worry, The WAMP Server doesn't install any spyware or annoyware :-).

Your Database Server

If you've installed the Wamp Server that was described in the previous chapter, or if your web host already provides access to the MySQL server then you can skip this and move on to the next chapter.

If you did not install the Wamp Server and you do not already have a MySQL database running then you'll need to install MySQL on your web server. This documentation will not go into detail on how to install MySQL from scratch since the MySQL documentation has a great Installation document in place already.

Once you have MySQL up and running you can proceed to the next chapter.

Creating a MySQL user

This chapter is not required for everyone. It depends on how your MySQL server is setup. If you have a web host that provides MySQL access for you chances are they've provided a user and a database already, in which case you can skip ahead to the next chapter. For users that are not sure, then read on.

Note: This chapter is very streamlined, a lot of users will already have MySQL users available and will not have to create a user themselves.

MySQL is a multi-user database that allows a virtually unlimited number of users to connect to it at the same time. Each user has their own privileges to the server, some users will only be able to access certain databases or even certain tables within a database, while other users may have full "root" access to all databases. Users in a virtual hosting environment will most likely have limited user access to a single database provided by the web host.

If you have the proper 'root' access to create a new user it is strongly suggested to add a user just for PsychoStats. This is a security measure so that if the PsychoStats user is ever compromised by a malicious user they would only have access to the PsychoStats database and not other databases that might be on the system.

If you have phpMyAdmin, which comes with the WampServer or can be downloaded from the officialphpMyAdmin website, then follow the steps below to add a user.

  • Login to phpMyAdmin and on the main page click on "Privileges" near the bottom. That will show a list of the current users in the database.
  • Below the user list click on "Add a new User".
  • On the next screen, in the "Login Information", you'll enter a User name and password. Also, you'll notice a field labeled "Host". For the average user you'll want to leave that set to 'Any host'. This will allow PsychoStats to connect with that user from anywhere in the world. If this setting was set to "Local" then the user would only be able to connect to the database if the connection originates from the server itself (so, from your game server which might be next door or 1/2 way around the world, you wouldn't be able to connect to the database).
  • Leave the rest of the input fields on this page at their defaults and click on the "Go" button at the bottom. This will add the user and refresh the page. But now there will be more options below for the user.
  • In the section "Database-specific privileges" (about 1/2 way down the page) you'll want to enter the name of the database that you'll be using for your PsychoStats installation. Or if you already have a database setup just select it from the pulldown menu then click the "Go" button.
  • On the next page select all the check boxes (you can leave the checkboxes in the 'Administration' section blank) that are shown and click "Go".

Creating a MySQL user manually

If you do not have phpMyAdmin or another GUI tool to access the server but you do have access to the standard 'mysql' command line client then you can use the following queries to add a new user to the system. Be sure to change the appropriate with your personal information before issuing the query.

CREATE USER ''@'%' IDENTIFIED BY '

';

GRANT USAGE ON *.* TO ''@'%';

GRANT ALL PRIVILEGES ON ``.* TO ''@'%';

In case line 3 above does not work try the following:

GRANT ALL ON .* TO ''@'%';

Installing PsychoStats (part 1)

Installing the PsychoStats software is very easy, a web based "Install Wizard" will guide you through the steps needed to get the database setup and initial configuration defaults in place. But first you need to put PsychoStats on your web site.

When you unzipped PsychoStats onto your computer it created a directory resembling: psychostats3.0.0 (where 3.0.0 is the current major, minor and revision). Inside that directory will be lots of files and sub-directories with a structure similar to the list below (some optional files and directories have been omitted from this listing).

  • PsychoStats3.0.0
    • \lib
    • \upload
    • stats.pl
    • stats.cfg


All of these files make up the required set of files for PsychoStats to work. For now, the directory you're interested in is upload. The upload directory is the entire web front-end for PsychoStats, these files are what allow you to view your stats online. The contents of this directory need to be copied over to your web server. A common place is a sub-directory called stats within your website root directory. Below are examples for Windows and Linux of how you would copy this directory to your web site.

IIS on Windows

If you're running the IIS web server the document root is usually something like: c:\Inetpub\wwwroot. Thats the directory where you want to copy the PsychoStats upload directory into. However, the real directory may be somewhere different for your system and can be found by opening up the Website in your IIS Admin Console and looking at the web site properties. The 'Home Directory' tab will have the path of where your website directory is located.

Step-by-Step

  • Browse to the PsychoStats directory from the archive you unzipped.
  • Right click on the upload directory and select "Copy".
  • Browse to the document root of your website (ie: c:\Inetpub\wwwroot or wherever it it on your system).
  • Right click somewhere in the window of that directory and select "Paste". The files should copy over in a few seconds.

You should now have the upload directory copied into your web server document root. You probably don't want that directory to stay with the name of upload. So rename it to something more meaningful like stats. You can right click on the directory and select "Rename" to change the name.

So in the end you should have a directory of something like: c:\Inetpub\wwwroot\stats and in that directory will be all the PHP files and sub-directories that make up the PsychoStats website.

Apache on Linux

Apache is generally the web server of choice for Linux users. The document root of the website can be almost anywhere on the system. Some common locations include: /usr/local/apache/htdocs, /usr/www/htdocs, ~/public_html. Consult your web server configuration or your web host support for information on where your document root is.

To copy the files to your website do this:

First change your directory to where the PsychoStats archive was untar'd. Then do the commands below. Be sure to use real paths to where you want the files copied and not the path shown below.

mkdir /path/to/document/root/stats
cp -rf upload/* /path/to/document/root/stats

Change the stats directory name to whatever you want it to be.

Upload to remote server

If your web server is being hosted somewhere else you'll need to upload the contents of the upload directory to it using your normal FTP client (or SFTP for certain hosts). This is a standard affair and I will not go into detail. If you don't know what FTP is or how to use it, you can ask a friend or seek help in the forums. This documentation is not the place to explain FTP.

Running the Install Wizard

Once you have PsychoStats uploaded to your web server you're ready to run the installation wizard which will complete your Installation of PsychoStats (you'll still need to setup the stats.pl to run, described in the following chapters).

I'll assume you copied or uploaded the PsychoStats upload files to a directory called "stats" on your web server document root. All you have to do now is browse to the /stats/install/index.php URL with your browser pointing to your website. The installation wizard will guide you through the rest of the installation. For example, You might end up browsing to an URL like: http://example.com/stats/install/index.php

That should open the Install Wizard. From here, just follow the directions and answer the questions that it asks you.

IIS and Windows file permissions

If after the installation you browse to your PsychoStats homepage and see only Smarty Error messages, then perform the following tasks:

  • Browse to a folder where PsychoStats keeps its compiled templates (Default: ps_themes_compiled)
  • Right-click that folder and choose Properties
  • Go to the Security tab
  • Click the user "Internet Guest Account" (Notice: The user name may be different if you changed your IIS settings)
  • Check the box "Allow: Full Control" to assign all needed permissions to that folder for IIS.
  • Click Apply and then OK

You can now refresh the PsychoStats page in your browser and finally see it working correctly.

Initial configuration

Once the install is complete you will have a fully functional PsychoStats website on your server. Although, for the moment, it will be empty and not have any players. The first thing you should do is open the Administrator Control Panel (ACP) and look around at the configuration settings. The first thing you need to configure is a valid logsource. A logsource defines where your game server logs are located and how to read them. Without this, you will not have any stats.

See the section on Setting up a logsource for more information.

Installing PsychoStats (part 2)

At this point you should have a fully functional PsychoStats website up and running on your web server. You should be able to browse to the various pages within the stats (but there won't be any players yet) and you should have a logsource configured. And hopefully you've looked at other settings and have tweaked them as needed for your own personal tastes.

Now you need to install the stats.pl portion of PsychoStats onto your machine. The stats.pl (and related files) make up the 'back-end' of PsychoStats. This is the part that actually runs and populates your database with statistics from the game logs. These files can be put almost anywhere, on your web server, the game server, your home machine, or another remote server 1/2 way around the world. A lot of users are confused when they get to this part of the installation. So, to try and make it easier on you follow the questions below and find the question that relates to your setup.

  • A user says ...
    • "My game server and web server are on the same machine and are not on my home machine"
      • Answer: Upload the stats.pl, stats.cfg and lib directory to the game server.
    • "My game server and web server are remote but I want to run PsychoStats on my home machine."
    • Answer: Make a copy of the stats.pl, stats.cfg and lib directory on your home computer. Put them into a PsychoStats directory (it doesn't matter where). I suggest something like "c:\psychostats".
    • Answer: Upload the stats.pl, stats.cfg and lib directory to the game server. You will have a home directory, just upload the files into a psychostats directory within your home directory. Do not put the files inside your web site directory (ie: public_html, or cgi-bin).
    • Answer: Upload the stats.pl, stats.cfg and lib directory to the part of the webhost that is not accessible to the web. Usually this is the home directory, just upload the files into a psychostats directory within your home directory. Do not put the files inside your web site directory (ie: public_html, or cgi-bin).
    • "My game server is on a remote machine and I want to run stats.pl on the game server."
    • "My game server and my webhost are on a remote machine and I'm not sure/ don't care where to put stats.pl"

Configure the stats.cfg file

The stats.cfg file is a very small configuration file that simply holds some basic settings on how to connect to your database. All other settings for PsychoStats are stored in the database itself and can be changed by logging into your stats website and going to the ACP.

Make sure you edit the stats.cfg with the proper settings for your database. The table below shows the settings available. Remember, you're configuring these settings based on where your database server is in relation to the stats.pl. So if your database is on another remote machine you'll need to setup the 'dbhost' to point to the remote hostname or IP address.

A common problem with remote databases is improper user permissions that do not allow you to connect to the database. Another common problem is most free web hosting providers will block remote database connections to their servers which make it impossible to run the stats.pl on a different machine.

Setting Default Purpose dbtype mysql Specify the type of DB to use dbhost localhost Hostname or IP of the DB server (localhost for the same machine) dbport   Port for the DB server. Leave blank for server default dbname psychostats Name of the database to use dbuser   Username to connect as. Leave blank for none dbpass   Password for authentication. Leave blank for none dbtblprefix ps_ Prefix to use for all tables related to PsychoStats. ps_ is a good default.

 

Running PsychoStats

At this point you have run the 'Install Wizard' from your browser and the database is fully setup and you can view your empty player stats online. Now it's time to finally generate some stats!

How to run stats.pl depends on what type of system you are on. We'll step through the various ways below.

Linux SSH Shell

If your host allows SSH connectivity, simply login and change to the psychostats directory where you put the files, then simply run the stats.pl from the prompt:

./stats.pl -v

Note the added command line option '-v'. This enables 'verbose' mode and will cause some extra feedback while the stats are processing. This is recommended the first time you run it so you can see what is happening.

If you have streaming logs enabled, you may want to use screen to start stats.pl, since the process never actually ends and the user may need to log out. Once screen is installed, simply run it with these parameters:

screen -A -m -d -S ScreenName /ps_installation_dir/stats.pl -v &

Notice that you are not actually running a script, so you can run this command from anywhere. You may replace 'ScreenName' by whatever name you want for the screen and make sure that 'ps_installation_dir' is the full path to stats.pl. To resume (or enter) the screen, simply type:

screen -r ScreenName

To exit (or log off) a screen, use the key combination:

Ctrl+a+d

Windows Server

If your running PsychoStats on your home Windows machine or on a remote host that allows remote desktop connectivity, simply open the folder where PsychoStats is. If you have the 'scripts' sub-directory inside your PsychoStats folder go there and double click on 'psychostats.bat'. That will run the stats.pl in 'verbose' mode and will pause the window so it doesn't close immediately. This will allow you to view any errors that may occur.

Alternatively, just double click on the stats.pl icon directly, however you will not see any output and the window will close immediately after stats.pl is finished. This makes it more difficult to see error messages that occur. However, if you suspect there are errors occuring you can view the stats.log file in the directory (if it doesn't exist then no fatal errors occurred).

Automatic Scheduling of PsychoStats

Now that you've run the stats.pl at least once and have confirmed that you are getting statistics on your website you'll most likely want to setup PsychoStats to run automatically. PsychoStats does not have built in functionality to run itself. So in order to do this you need to use either the Windows Task Scheduler, or Linux CRON depending on which system you're running on.

Windows Task Scheduler

The Windows Task Scheduler is very limited but it will at least let you run PsychoStats on a daily basis. This means you can not run hourly updates. There are other software packages out there for Windows that let you schedule jobs more frequently.

You'll find the Windows Scheduler in your Start menu under the following tree: Programs -> Accessories ->System Tools -> Scheduled Tasks

Screenshots will be added later... For now, use your imagination. Add 'perl.exe' as the application to run on a 'daily' basis. At the end of the Schedule Wizard select the checkbox to 'Open advanced properties for this task when I finish'. When that window opens add the path of your stats.pl to the end of the perl.exe thats already present. Then save.

Linux CRON

CRON is very easy to setup, but there are various ways to set it up depending on your hosting provider. For instance, cPanel has a GUI built in that lets you create a cronjob very easily from your web browser, but other systems may have to do it from their shell. Both will be outlined below.

CRON setup via cPanel

cPanel has a GUI to setup CRON as shown in the screenshot to the left. This is a very easy way to schedule PsychoStats to run automatically. Simply view the screenshot as a guide and setup the time of day that you want to run the stats.pl. Most users will schedule the stats.pl to run every hour and that is a decent recommendation to make here. Maps are generally 30-60 minutes long so every hour allows a single map or 2 to be processed at each update. It's entirely up to you how often you want to update. But I do not recommend anything more frequent than 15 minutes. If you try to update too much you'll end up with multiple stats.pl processes trying to update the same files and your stats will break.

 

Manual CRON setup

Manual cron setup is easy, but requires that you have shell access to your server. This means you must SSH to the server first. From there you can use the 'crontab' command to add an entry to run automatically. When you run 'crontab -e' it will open up your default editor (for most this will be 'vi' or 'nano'). You simply enter a line of text resembling the example below, save the file and exit. The example below shows a cronjob that would run every hour at the top of the hour. Make sure you change the path to where your stats.pl is actually located.

0 * * * * /home/xxxxxxxx/psychostats/stats.pl

Each number or asterix (*) represents a time. There are 5 ways to customize the time when a cronjob will run, outlined below. Some more advanced details have been left out to keep this simple. Search the Internet for more detailed explanations if you need it. For the most part you'll only ever use the first 2 fields in the cronjob entry.

  • The first number represents the MINUTE that the cronjob will fire. An * means every minute. Between 0 .. 59
  • The second * represents the HOUR that the cronjob will fire. An * means every hour. Between 0 .. 23.
  • The third * represents the DAY of the MONTH that the cronjob will fire. An * means every day. Between 1 .. 31.
  • The fouth * represents the MONTH that the cronjob will fire. An * means every month. Between 1 .. 12
  • The fifth * represents the WEEK day that the cronjob will fire. An * means every day. Between 0 .. 7

So, if you look at our previous example, we said run at minute ZERO, every hour, every day, every month, on each day of the week. So it runs ONCE every hour (since minute 0 will only be true once per hour.

If we wanted to run stats.pl every 30 minutes we could use a slightly more advanced entry:

*/30 * * * * /home/xxxxxxxx/psychostats/stats.pl

or (this would do the same thing):

0,30 * * * * /home/xxxxxxxx/psychostats/stats.pl

All done

Congratulations, You're all done. You should have a fully functional PsychoStats installation that will automatically update itself.


What's New in Version 3.2 (See full changelog)

  • Version 3.2
  • * Fixed to run with php5 and mysql5
  • Version 3.1.1 (...)
  • * Fixed halflife::parseprops to properly parse player names in event parameters
  • that have double quotes (") in their name.
  • * TF2: Team 'pointcaptured' old style events will once again give bonus points
  • to players (along with the newer style of the event
  • * TF2: double bonus points for player 'dominations' are no longer given.
  • * Fixed typo de_interno to de_inferno in heat.xml
  • * Fixed a couple minor issues in the installer.
  • * Implemented Halflife GUNGAME support.
  • * Implemented Call of Duty 4 support.
  • * Implemented Soldat support.
  • * Enhanced HTML output with GZIP support.
  • * Fixed Feeder::stream support to properly process halflife log streams.
  • Version 3.1 (05/01/2008)
  • * Implemented CMS and plugin architecture in the PHP front-end.
  • * Recoded theme routines to be more robust and tolerant.
  • * Redesigned default theme template. XHTML compliant and easier to maintain.
  • (pre-3.1 themes are NOT backwards compatible!)
  • * Log state routines have been recoded and made more accurate.
  • * Logsources have been recoded and have their own config table.
  • * Events code has been recoded and have their own config table.
  • * Events can be configured via the ACP and new event code can be dropped into
  • the 'Events' directory if users wish to add new event handlers w/o modifying
  • existing code. Wiki doc's will need to be updated (yuk)
  • * Implemented -maxlogs, -maxlines command line options to allow stats updates
  • to exit early. This will help systems under resource restraints.
  • * Split plr_ids table (name,ipaddr,steamid) into 3 separate tables to make
  • queries against these fields easier and less confusing.
  • * Removed 'headshotdeaths' stat since its not very reliable to track.
  • * Player events with a steamid of STEAM_ID_PENDING are completely ignored now.
  • * CMS security: Implemented defense against CSRF exploits.
  • * CMS security: Implemented separate admin login for ACP pages.
  • * Removed ps_config_layout table and combined all config related stuff
  • into ps_config. Also added 'label' field.
  • * daily awards are now created (along with monthly and weekly).
  • * Removed 'auto' section of config as it's no longer needed. Daily updates
  • (all maxdays decay activity players clans ranks awards) are performed
  • automatically by stats.pl based on new 'daily' settings in the config.
  • * DB routines are more robust and will attempt to reconnect if a query fails.
  • * Implemented Team Fortress 2 support.
  • * Roles can now have mod based stats.
  • * Reduced code required for mod sub-classes, which makes it easier to add new
  • support for game mods.
  • * Recoded class_PS.php to be a real class with sub-classes for game:mods.
  • * Overhauled the overview page with lots of useful charts and a google map.
  • * Implemented backend Spatial stats.
  • * BUG: Fixed name changes when tracking by name (names were not being separated).
  • * Implemented Heatmaps (uses spatial stats)
  • * Added default-blue skin.
  • * Updated player profile display in the default theme to be a bit more pleasing to
  • the eyes. And added a link to a players SteamID profile page on steamcommunity.com.
  • * Fixed DOD flag caps.
  • * Added theme install wizard to ACP for automatic download and installation of new themes.
  • * 1 million and 1 tweaks and fixes and other things I've forgotten. See the full
  • timeline on http://www.psychostats.com/trac/psychostats/timeline/
  • Version 3.0.6 beta (2007-05-01)
  • * Fixed query.html: rcon commands would not work.
  • * Fixed function.sortheader.php: removed hardcoded themes path.
  • * Fixed class_theme.php: "Cannot break/continue 1 level" error.
  • * Fixed admin/servers.php: Incorrect integer value: '' for column 'idx'
  • * Fixed PQ modtype for 'hl2dm'. returns 'hldm' instead.
  • * Added module version check for DBD:mysql. v3.0002 or higher is required.
  • * Fixed 'Connection Closed' errors while downloading from FTP log sources.
  • Version 3.0.5 beta (2007-03-10)
  • * Fixed "constant CACHE_FILE_GROUP already defined" errors
  • * Fixed PS::Config->set(); would not set sub vars (var.subvar = value)
  • * Fixed event plrtrigger 'address'; would not track player IP addresses
  • + Implemented game support for halflife:natural (Natural Selection)
  • * Bug #8 fixed (I hope). "Duplicate entry in 'plr_ids' table"
  • * Bug #9 fixed. "Only variables can be passed by reference in imgcommon.php"
  • + Added a couple of batch files for Windows users. These are just
  • shortcuts for a couple of common tasks for stats.pl.
  • + Added 'dod_teamscore' event so that win/loses for non-source DOD servers
  • will properly track for players and maps.
  • + Added 'round_win' event trigger for 'dod' servers.
  • + Directory structure has changed a bit to try and make it less confusing
  • for users. The 'upload' directory contains all files meant to be uploaded to
  • a website (this used to be called 'web'). Everything else stays local.
  • + The 'live servers' configuration has been moved into it's own table to
  • make it easier to manage.
  • * Fixed bug with installer on step 1. Incorrectly saying mysql 4.1.11 was
  • too low when in fact it's the minimum.
  • + Fixed stats update from crashing when no regex clantags are defined.
  • * Fixed 'czero' servers in the live server view to show maps correctly.
  • * Fixed 'white screen' problems on certain pages when run on PHP5.
  • * Corrected 'kill_streak' and 'death_streak' calculation in awards.
  • * Fixed team detection for players w/o the need for 'joined_team' events.
  • * Fixed player bonuses. Bonus points were not actually being added to skill.
  • * Fixed load_clan_members(); SQL query was not optimized properly and causes
  • the 'edit clan' page to be very slow with large member lists.
  • * Fixed 'weaponstats' accuracy triggers for Natural Selection. Event wasn't
  • being delegated properly.
  • * Fixed player BANS. Bans didn't work at all. They do now. :)
  • * Fixed infinite loop in Feeder::* when an error occurs downloading a file.
  • Version 3.0.4 beta (2007-02-10)
  • + Added clean module detection to stats.pl to show 'pretty' errors
  • if a non-standard module is not present or if Perl is too old.
  • * Tweaked some events in Game/halflife.pm
  • * Fixed language encoding problem in certain parts of the theme.
  • (UTF8 characters were not encoded correctly).
  • * Fixed smarty plugin function.mapimg.php. It was causing infinite
  • loops on some systems due to bad file paths.
  • * Fixed a DB query that greatly affected the load times of the main
  • player index and possibly other listings on the stats web pages.
  • * Fixed some player stats from not being saved properly. This would cause
  • some players to have slightly lower stats than what the logs actually reflect.
  • * A couple more tweaks to the Installer that adds more logic for minimum
  • requirements and less confusion when tables already exist.
  • * DOD player bonuses have been added to the default config and confirmed
  • working.
  • * Updated DOD theme pieces to include some missing DOD specific information.
  • Version 3.0.3 beta (2007-02-03)
  • * Recoded the Install wizard to remove some confusion during the database
  • initialization step. Also made step 6 (compiled themes) more robust to
  • allow users to change the path and have better permission checking.
  • Version 3.0.2 beta (2007-02-02)
  • * Fixed 'notice' errors on install pages.
  • * Fixed 'Field 'logo' has no default value' when updating stats for certain
  • versions of MySQL.
  • + Changed default settings for a few config variables. Like disabling
  • warnings for unknown events and enabling partial week awards.
  • Version 3.0.1 beta (2007-02-02)
  • * Unknown column 'lastdecay' in 'field list' -- Error fixed. the database
  • schema included in the previous release was missing this field.
  • Version 3.0.0 beta (2007-02-02)
  • * Not all features and changes have been mentioned below *
  • + Recoded object hierarchy to be scalable, easily sub-classed and to separate
  • functionally. Lots of work went into the recoding and structure, too many
  • to list here.
  • + All configuration is stored in the database with the exception of basic
  • DB settings in the stats.cfg. This will allow for 100% web based GUI setup.
  • + logsource's can be local directories, or remote FTP or SFTP sites
  • (Note: SFTP requires Net::SSH::Perl to be installed).
  • + Implemented player/clan 'profile' support. If stats are reset players
  • and clans will retain their personal profiles when the stats are recreated.
  • + Implemented full UTF-8 support. This requires MYSQL v4.1+
  • + Implemented Real-Time clantag detection for players.
  • + Implemented Real-Time 'most used' player name selection.
  • + Implemented better state persistence for log scanning so logs are only
  • scanned once for each source configured.
  • + Implemented a better 'kill skill' calculation. Still using the ELO method
  • however, a players total online time is now taken into account. The more
  • online time you have the less points you give/receive for kills.
  • * Re-coded the DB stats routines (again). They are now simplier, and about
  • 15% faster than before.
  • + Implemented IP to Country lookups. The players country flag will be shown
  • in player listings within the stats. Flag images credit goes to
  • http://flags.blogpotato.de/
  • + Implemented 'user' profile support. Users are registered and linked to a
  • player for login. The user system is flexable and will allow for easier
  • integration within existing sites.
  • + Implemented extensible admin controls. New admin 'controls' can be dropped
  • into place w/o any changes in existing PHP code.
  • + Enhanced "Live server view" to allow multiple servers all on 1 page and
  • w/o causing the page to 'lag out'. RCON queries are also allowed for admins.
  • + Enhanced player searching to match on player IP's and name aliases.
  • + Implemented uploadable plr/clan icon support. Upload from users computer
  • or from another URL.
  • + Implemented player session histories. Each player has their previous
  • online sessions saved and can be viewed separately from their overall
  • stats. A 'session' is the length of time the player was logged in, even
  • between map changes.
  • + Removed some logic from the default theme to make it a little less complex
  • on some pages.
  • + Implemented an advanced admin config editor. The admin config editor is
  • dynamic and very easy to use. New settings in the database are automatically
  • discovered by the editor w/o any changes to the themes or other code.
  • + Implemented several more Admin Control Panel features, like logsource
  • editing and other tweaks.
  • + Implemented a 'daily' process trigger for stats updates. Daily processes
  • are generally run once, or possibly several times a day to calculate certain
  • stats, ranks, trim histories or clean up the clan listings.
  • + Implemented daily process: player ranks.
  • + Theme updated to show a players rank difference going up or down.
  • + Enhanced PHP session support to recognize Web "robots" (ie: google, yahoo)
  • and disable the auto appending of session ID's in the HTML output. This will
  • help search engines to properly index your stats pages.
  • + Implemented daily process: clan rules
  • + Implemented daily process: players rules
  • + Implemented player bonuses. Ie: assign extra points to players (or teams
  • of players) based on different events like 'target_bombed'. Fully web
  • configurable. Note: this has nothing to do with AWARDS.
  • + Enhanced clantag support. different tags can be matched and combined into
  • a single clan entity automatically.
  • + Implemented awards. The awards system uses a plugin architecture to allow
  • for more complex awards. Currently basic player action and weapon awards
  • are present.
  • + Implemented player aliases.
  • + Implemented an easy to use online installation process.
  • + Implemented 'maxdays' feature! -- Old stats are removed automatically.
  • + Added 'maxdays_exclusive' option: If enabled, compiled stats are reduced
  • when old stats are removed. If disabled the compiled stats continue to
  • increase regardless of old stats being removed.
  • + Implemented automatic scheduling of 'daily' updates when stats.pl is
  • run. So using the -daily command line manually is optional.
  • + All dynamically created images (charts and graphs) are now fully
  • customizable via an external XML config file.
  • + Implemented automatic player bans from log events (incomplete).
  • + Implemented manual player bans. Wildcard support included. Ban players
  • by steamid, IP or name.
  • + Implemented fully functional DECAY system for decaying player skill
  • over long periods of inactivity.
  • + Implemented full Day of Defeat:Source support. Including detailed stats
  • based on team roles.
  • + Google Maps API support implemented for player world locations based on
  • their IP address. This is never 100% accurate, but it's good enough.
  • + New hitbox flash animation included with default theme. Fully 3D!
  • + HL2DM support added (classic HLDM should work the same)
  • + Implemented Feeder::stream to allow log streams from remote game servers.
  • NOTE: This feature is currently experimental and is not fully fleshed out.







  • 2 Total Files
  • 7 Total Categories
  • 1 Total Authors
  • 53 Total Downloads
  • PsychoStats Latest File
  • alex Latest Submitter

0 user(s) are online (in the past 15 minutes)

0 members, 0 guests, 0 anonymous users