[Rothgar]

Compile Crashes should be fixed:

http://bugs.alliedmods.net/index.php...25#comment2726

[louie666]

Indeed the compiler seems to be working nicely now, no crash with build 1781

[Tobi17]

Hello

the new version v1.9 was released with the following changes:

HLstatsX Ingame Plugin:
- Team colors are checked on every call
- The function to color players only uses one global array now
Fixed: Handle the comma on splitted messages properly
Fixed: Check now if the client is ingame for all HLstatsX commands

Bye
Tobi

[Tobi17]

Hello

Originally Posted by SaintK The problem here is that when you type /rank, its not being displayed to other players. Anyway to adjust that?

To display all HLstatsX commands just turn off the option "hlx_block_commands" within your server.cfg.


Bye
Tobi

[dann]

I seem to be having issues with this plugin, after about 12-24 hours it seems that when you type rank top10 etc in the server it no longer displays(statsme does though). You actually have to restart the server for it to work again.

[urus]

Tobi17 it`s possible to make multilingual support for ingame hlxmenu!?

[Tobi17]

Hello

Originally Posted by dann I seem to be having issues with this plugin, after about 12-24 hours it seems that when you type rank top10 etc in the server it no longer displays(statsme does though). You actually have to restart the server for it to work again.

What happens if your reload the plugin with "sm plugins reload hlstatsx"? Also ensure you are running the latest version v1.9. Normally this should not happen.

Bye
Tobi

[Tobi17]

Hello

Originally Posted by urus Tobi17 it`s possible to make multilingual support for ingame hlxmenu!?

Yes, this is possible and will be inlcuded in one of the next releases. Until it is included just change the values in the sources and recompile the plugin with the webcompiler.

Bye
Tobi

[Tekniqal]

Tobi17:

I am getting some errors with SM 1815

L 12/20/2007 - 18:08:59: SourceMod error session started
L 12/20/2007 - 18:08:59: Info (map "de_dust2") (file "errors_20071220.log")
L 12/20/2007 - 18:08:59: [SM] Native "GetClientTeam" reported: Client 5 is not in game
L 12/20/2007 - 18:08:59: [SM] Displaying call stack trace for plugin "weapon_logging.smx":
L 12/20/2007 - 18:08:59: [SM]   [0]  Line 275, D:\Remote Filez\css-nuclear fallout\addons\sourcemod\scripting\weapon_logging.sp::dump_player_stats()
L 12/20/2007 - 18:08:59: [SM]   [1]  Line 478, D:\Remote Filez\css-nuclear fallout\addons\sourcemod\scripting\weapon_logging.sp::Event_CSSRoundEnd()
L 12/20/2007 - 18:15:21: Error log file session closed.

Lots of that

[LocutusH]

Tobi: Just a few thoughts, i hope you are not misunderstanding it. Just to make the install process something easyer to understand.

I have just completed to set up a server with sm+hlstatsx plugin 1.9, and a webserver with perl+mysql runnign hlstatsx 1.20RC2.


No it wasnt easy, but mostly because i was inexperienced with setting up a mysql server. But apart from that, there were major difficulties, because some undocumented things:

1. The walktrough is good, altough it has many typos, and missing things. Mainly, the most confusing is, that HLstatsX is often written as hlstat, hlstats, hlstatsx, hlstatx or even hlstart etc. Therefore we must watch every single option, to write everywhere the same name A unification would be very helpful.

2. It is nowhere written, that i must give "run" rights to the perl's files. Ok, it may be obvious, but not after hours of setting up everything else... It is evident, that i had to set the _run file to run rights, but i had to set the other pl-s too. Otherwise, the perl daemon stated that it has started successfully, but really it did not. Not until i gave all files a run permission.

3. It would be helpful, to clarify more, that we must dump the "web" folders files to the hlstatsx folder. There is only a mv command, but i didnt understand why it is there.

4. It sould be written somewhere, that if the servers, perl, and web are running on the same server, the ip address is not working, we must type localhost instead. Why this making a differenc i dont know, but it does.

5. It is also nowhere written, that we must edit the run_ perl file, because there is a path line to the perl directory, wich must be configured ;)

But after all, success