[paegus]

/*
 * Pure kick log
 *
 * Description:
 *  Logs client disconnection due to file inconsistencies.
 *
 * Changelog:
 *  v1.0.0
 *   Initial release.
 */

relatively simple really. could add database support i suppose but cbb right now.

Ideally for periodic review so if you only protect certain vulnerable files you can see what clients are altering them.

[Sammy-ROCK!]

Why don't you store the BuildPath directory calling it on OnPluginStart instead of calling it whenever someone gets kicked due the pure kick? So it won't be called twice.

[paegus]

well so far it's called fairly infrequently. only once or twice a day so i wasn't that fussed. I'll move up to PluginStart though thanks.

[DontWannaName]

Sorry to bring up an old topic but what about logging who has stuff that is being blocked. Kicking is disabled.

[paegus]

i wish but no joy as yet i'm afraid.

[f64]

Not knocking your idea, but all I have to do is search in the default logs directory for files
containing the phrase Pure server and I can find all the instances.

The server will only write a log under the following conditions:

sv_pure 1
sv_pure_kick_clients 1
sv_pure_trace 1

And will only show you the first file it finds, not all of them. If you have:

sv_pure_kick_clients 0

Only the client will recieve a console message, not the server log.

[paegus]

disconnections (in this case case caused by sv_pure_kick_clients 1) are indeed logged normally. i just couldn't be arsed to search masses and masses of log files for 1 or 2 instances of inconsistency when it is far simpler to have the plugin check why they were disconnected and if it's a pure reason then log it to a separate file for ease of access etc...

Originally Posted by f64 And will only show you the first file it finds, not all of them.

not sure what you mean by that... what will only show me the first file it finds? a directed search will show me any files i want it to.


originally i'd wanted to just see what inconsistencies where occurring and possibly react later but as mentioned sv_pure_kick_clients 0 does not leave any logged evidence so there's no way to log that information... which is unfortunate.

if you don't see the point in the plugin then you don't have to use it. but if you want to access a list of violations quickly, without having to faff about searching through your numerous logs then by all means, log them separately.

[f64]

Your plugin should be faster than downloading the logs, so not a bad idea really.
I dl'ed 15,000 logs the other day out of curiosity, which took awhile.
The search for phrases in those files was much, much faster.

Over 3 months time, I found about 20 files that had pure server disconnects. Most were sound files,
some were our custom models, and one was an extra file, which isn't a cheating attempt at all.

If a client has multiple files that don't match the server's crc files, then the server
will only report the first file it comes to that differs instead of listing all of them. Hope that helps.

[paegus]

ahh right. yeah it reacts to the 1st one only which was why i wanted to be able to see ALL the files that broke consistency. unfortunately those violations are only printed to the server's console but not logged in any way that SM can detect, or that anyone has told me how to intercept.

perhaps a Metamod pluging?

[IceCucumber]

Any way to get the entire message logged, instead of

L 07/17/2013 - 01:26:50: STEAM_0:1:12345678 (Name) (IP:27005) - Pure server: client has loaded extra file [GAME]\materials\m...

or

L 07/18/2013 - 13:59:00: STEAM_0:1:12345678 (Name) (IP:27005) - Pure server: file [GAME]\materials\building\facade02.vmt doe...

?

Especially with long file paths, it's impossible to see which file was in question.