The WWS Client
Starting the WWS Client
The Wow Web Stats Client is a small Java application that parses your combat log and uploads it to the WWS website.
In order to run the WWS Client, you must have a recent version of Java installed, you can get it at
http://java.com/. After installing Java, you can run the WWS Client by a simple
click on the "Client" icon on top of each page, or :
Start the WWS Client now !
You may get some security warnings about an unverified digital signature for the program, you'll have to click
the Run button to allow it to start.
If you run into problems with Java take a look at the Java Control Panel in your Windows Control Panel.
You can try typical fixes like clearing Java's Temporary Internet Files, or setting proxy parameters. The
WWS Client will also upload your combat logs to the WWS website, you must make sure that your
firewall allows this.
How to set-up shortcuts for the WWS Client ?
You can bookmark the following link http://wowwebstats.com/wwsc/wwsc24.jnlp
(right click on the link, then bookmark this link). You will then be able to launch the WWS Client simply by
clicking on the bookmark.
If you want shortcuts on your desktop or quicklaunch bar, run the following command "javaws -viewer"
(type Windows+R to bring Windows run dialog box), then right-click on the WWS Client line, and click
"install shortcuts".
Be carefull : you must never copy the wwsc24.jnlp file on your computer, because it would prevent
you to get future updates of the WWS Client.
How to update the WWS Client ?
You don't ! The Java platforms always check your version of the WWS Client at startup and downloads every new
available version automatically.
First launch of the WWS Client
First time you launch the WWS Client, you must go to the configuration pane, and fill in two
parameters : your WWS account name and password.
WWS needs a working directory to put temporary files and archive your log files after they've been uploaded
to the WWS Server. A default directory is chosen for you at startup, you can change it if you like.
The "Archive and delete logs after upload" checkbox lets WWS manages your log files from A to Z : every time
you successfully upload a set of logs on the server, these logs are compressed and archived in the working
directory, then the original log files are erased, so you're ready to run a new session of World of Warcraft.
The "debug console" may bring some magic to WWS :)
Uploading a combat log
This is going to be really simple : click "Add a combat log", choose a combat log on your hard drive, then click
"Host report", and that's it ! Your new report is available on your WWS account.
Your combat log is usually a file named WoWCombatLog.txt, but you can add other log files from your guildmates,
with other names. You can also add directly zipped combat logs. In case of multiple log files, WWS will "merge"
all files before submitting them to the server (see below).
If you've checked the box "Archive and delete logs after upload", WWS will handle your log files after the report
is generated. If not, you will need to handle these files manually.
You can add a comment to your raid, but don't worry if you forget to choose a comment, you can still change it after
your report has been uploaded.
I'm behind a proxy, how do I upload reports ?
Do everything as normal. After the client fails to contact the server, you will find a file named
"last-report.wwsl" in the working directory. Go to the WWS website, click on "My Reports", then "Upload a Report",
then select this file on your HDD and it will get uploaded through your browser.
Merging
The combat log records all events that you can see in game. But there are some combats
where you are very far away from your guildmates. In this case, you can merge the log files from
two or more persons to get the complete picture.
In order to merge log files, just add them all to the client before clicking "Host report". The client
will try to synchronize and merge all logs into a single log file that will be sent to the server.
This process works very well, and you get a report of the amount of data that was added by the additional
log file.
In some cases, the merger will bring some warnings about poor merging, and even sometime refuses to merge
two log files. This typically happens when the system clock of one of the machines that generated the log
files changed suddenly (eg because of an NTP process). In this case, you may try to deactivate the NTP process,
or identify the faulty machine and avoid using its log files in the future.
|
