Jump to content

Recommended Posts

Posted

PSYCHOSTATS INSTALLATION TUTORIAL FOR WINDOWS

 

Introduction

PsychoStats version 3.x is very easy and quick to install on any system. It includes an online installation wizard that you run through your browser. Follow these simple steps and you'll be up and running in no time. This documentation is for VERSION 3.x. All documentation for version 2.x is gone. Upgrade to v3 as support for v2 is depreciated. People are often very confused about how PsychoStats actually works. PsychoStats is software that relies on other technologies such as a WebServer like Apache and a database server like MySQL. You must be familar with these types of servers in order to use PsychoStats. And you must have access to a web and mysql server.

 

There are 2 parts to PsychoStats:

- Backend Perl Scripts

The backend takes care of the actual log parsing and updates. This is where the primary "stats.pl" perl script is run to fetch, parse and record log data from the game server(s) into the database.

Note: The system that runs these updates (Windows or Linux) is what defines which archive you should download a nd install.

- Frontend PHP Website

The frontend takes care of the interface that the user actually see's and interacts with. This is a set of PHP pages that interact with the same database as the backend so users can view the stats online.

 

Minimum Requirements

 

- PHP v4.3 (or 5.0+)

- MySQL v4.1.11 (or v5.0+)

- Perl v5.8 (Windows users: ActivePerl 5.8+)

Required Perl modules

- DBI

- DBD::mysql

Optional Perl modules

- Net::SFTP - This is only required if you need to download logs via an SFTP server. Note: This module has a lot of extra dependencies. Too many to list here.

 

These requirements are the bare minimum that ensure PsychoStats will work. 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.

 

Download Psychostats

Download the current release from the PsychoStats Downloads. Be sure to download the Windows archive.

 

Installation

Unzip the archive somewhere on your system. It does not matter where you do this. It's not required (nor desirable) to put this directory inside your web server directory root. Having the full unzipped archive in your web server's document tree means that users could potentially view your stats.cfg and get your database information.

 

Before you can run the Installation Wizard to finalize your installation you need to copy the frontend web files to your web server. This should be the only manual part of the installation you have to perform.

 

Most users running web servers on Windows tend to use the IIS web server from Microsoft. The document root for IIS is usually something like: c:\wwwroot. Thats the directory where you want to copy the PsychoStats web directory into.

# 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:\wwwroot).

# 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 of it.

 

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

 

For example, to start the installation use a URL like this: http://www.yourdomain.com/stats/install/index.php

Be sure to use a proper domain name in the URL to where your website is actually hosted.

 

Edit the stats.cfg with the proper database settings so PsychoStats can connect to your database.

 

All Done! Now you just need to run the stats.pl to update your stats. If you have shell access on your server then just run:

 

./stats.pl -v

 

Credits:Same (From Linux Tutorial)

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now


  • Posts

    • Since technical talk offends people, I believe I should return back to writting my Lineage 2 lore stories. Here's the next one:   Once upon a time, there was a boy and a small adorable wolf.    The boy really loved the wolf but as the wolf grow older and bigger, it became agressive and would bite the boy. One day the boy and the wolf decided to go to the city to buy potions. The road was long and hilly so the boy moved all his adena to the wolf bags to help his legs and reach the city easier.   When they reached the city, the boy tried to take the adena out of the wolf's bags. But the wolf would not ! He bit the boy and said "You will not get this adena back, this is my adena". The boy got angry. He decided to go to the pet master and ask for help.    "Pet master, pet master ! My wolf is big, bad and angry and it won't obey me. I want my adena back and it bites me. "   The pet master looked at the big angry wolf, then looked at the boy and said. "I have a solution for your problem young one. I have magic. Dark magic. I can turn your big bad elder wolf into a younger puppy for free, all you have to do is spell the magic chants. Nothing more, no wolf modifying wands, just your say".   The boy thought about it for a bit, and decided that he indeed wanted to turn things back. But when he was about to spell the magic words, guards arrived at the pet master.    The city guard captain said "Is this the big bad angry wolf that bites people and doesn't give back his adena ? We will kill this wolf !"    For a moment the boy hesitated but he said "This wolf is big bad and angry, but I love this wolf and I dont want it to die ! Please don't kill the big bad angry wolf." But the boy was not fast enough. The guards jumped the wolf and started slashing on him with their swords. The boy didn't know what to do, so in it its final moments right as the wolf was about to die, it spelled the magic words. "Pet master, make my wolf young and adorable again !"   But he was not fast enough. The wolf got slashed and killed by the guards just one moment before the boy could finish his last word.    But as the words came out of his mouth, with the wolf's dead body on the floor, a younger wolf manifested out of thin air. The magic was real. The guards got scared and run away. Now the boy was left with a dead old bad angry wolf and next to him an alive younger version.    The boys joy was even bigger when it opened the new wolfs bags and his adena was finally there. He took the adena and went back to buy potions in the city.   Twenty four hours later, the boy couldn't believe how his fortune would change ...   (No AI was used to write this story)
    • This is like 2017 MaxCheaters. i love it.
    • NEW SEASON GRAND OPENING FROM - 30 OCTOBER 2026, FRIDAY, 20:00 +2 GMT !
    • My bug report was a proper submission. I shouldn't have shown the exploit, I will accept that. Let's end it here. 
    • To Finish this, because it's need a explanation   1. “I come to your forum” — It's the L2JMobius forum, not mine. I'm a contributor, not the owner or the maintainer responsible for deciding which fixes get committed.   2. “Which is why I left” — That's not an accurate account of what happened. You may have left voluntarily once, but you were also banned from the Discord server three times after repeatedly returning and causing the same disruptions. Those are not the same thing.   3. “You personally reply and reject that it works” — I asked how a negative withdrawal could be performed and later requested a demonstration of the claimed exploit. At no point did I reject the patch or claim the vulnerability was impossible. Asking for evidence is not the same as rejecting someone's work.   4. “You leave it unpatched for days” — I don't make that decision. Whether and when a patch gets committed is entirely up to the project maintainer, not me.   5. “You challenge me to post a video” — Yes, I asked you to demonstrate the exploit. You interpreted that as a rejection of your work, which it wasn't. Requesting proof of a claimed exploit is a perfectly reasonable part of technical discussion.   6. “Asshole-ness is a mutually contracted disease” — You're responsible for your own behavior, just as I'm responsible for mine. Disagreeing with you or questioning your claims doesn't justify personal insults. If you believe I've treated you unfairly, address what I actually said rather than making my behavior an excuse for yours.   And one question remains unanswered: why did you publicly disclose the exploitationmethod before the fix was released, after previously saying you wanted to avoid harming the project?   The vulnerability was real, the fix was accepted, and the commit was published. I have no problem acknowledging any of that.   My disagreement has never been about whether the bug deserved to be fixed. It's about how you've handled the discussion and repeatedly misrepresented my role in it.     I have nothing against you personally. My issue is with the way you conduct yourself in these discussions.   And no, you're not obligated to prove anything to me. However, when you make a technical claim, the burden of proof is on you. You cannot reasonably expect others to accept your claims without sufficient evidence.   Questioning a claim is not the same as rejecting it, nor is it a personal attack.   This isn’t about fanaticism; it’s about pushing back against the completely senseless attacks constantly leveled at the project as a whole.   It’s always the same thing: they badmouth it, claiming the project is worthless—yet the very same people criticizing it are the first in line to download a leaked version.   Enough is enough. This discussion has dragged on far too long over something that ought to be straightforward; if you’re going to submit a bug report, you should at least do it properly.
  • Topics

×
×
  • Create New...

Important Information

This community uses essential cookies to function properly. Non-essential cookies and third-party services are used only with your consent. Read our Privacy Policy and We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue..