[FZFalzar]

Title: Brutus Insurgency2 Logger/LogFixer

Changelog:

1.0.0 - Initial Release
1.0.1 - Fixed a bug that caused the weapon name to not be replaced in a kill event log (NOTE: For Psychostats users, please remove ps_heatmaps.smx from your plugins or it will cause a conflict!)
1.0.3 - Added missing M14 EBR entry from the weapon list as well as removed duplicate M249 entry. This should fix the problem whereby M14 kills are registered as M16A4's (Thanks GiZZoR)
1.0.4 - Fixed logging for suicide messages, should display the weapon used for suicide accurately. There might be an issue where another weapon is shown when the player walks over his own molotov fire after firing another gun. Happens rarely though, so I won't pay too much attention to it.
1.0.5 - Fixed a stupid typo on one of the weapons (M87 (wrong) -> M84 (correct)). Added team-checking for both Capture/Destroy Events. Added potential new weapons (Garand, K98).
1.1.0 - Moved from static weapon list to a configurable list by an external file (see install instructions) (Thanks jballou for the idea!). This allows the logging of new/custom weapons from custom theatres and stuff without having to constantly recompile. Fixed CP Destroy event not being fired. Added sanity check for ingame clients, fixed CP Capture/Destroy event errors. Include files updated.

Description: This is a modified version of the original SuperLogs by psychonic that intercepts and re-writes HL log messages for Insurgency2 . It also logs down weapon statistics in a format compatible with Psychostats/HLStatsX web interfaces. There are no cvars/commands for this plugin, it is largely silent.

Features:
Fixing improper weapon naming in the game log
Logging for headshots/hitbox regions per weapon
Logging for Control Point capture/destroy events (NOTE: Currently logs all human players online when this happens)

Installation:
Place the plugin (brutus_ins_logger.smx) in your game/addons/sourcemod/plugins folder and make sure logging is enabled for your game server. Place the configuration file (brutus_ins_logger_weapons.cfg) in game/cfg/sourcemod folder.

Credits:
psychonic - For SuperLogs
FZFalzar
MR.David

Notes:
The attached Include Files in the ZIP are required to compile this Plugin. The forum compiler will not suffice.
The events for CP Capture/Destroy are registered as "ins_cp_captured" and "ins_cp_destroyed" respectively. You should set your log capture regexes to pick those up should you require registering number of times of successful capping.

For any support/queries, please add me in Steam and send me a message as I rarely read the forums.

[FZFalzar]

-> v1.0.1 Bugfix Released, refer to changelog in main post

[GiZZoR]

Hi there,
Thanks for working on this!

I've noticed 2 issues so far:
1) You have 2 weapon entries for weapon_m249
2) Kills with a M14 EBR show as weapon_m16a4

Thanks,
GiZ

[FZFalzar]

Noted, changes have been implemented in the latest version -> v1.0.3

[GiZZoR]

Just had a bot suicide with M67 grenade, but log came up with:
"Rosin<99><BOT><#Team_Security>" committed suicide with "player"

EDIT: Same happened with the F1 nade.

Nades are logging correctly for normal kills tho:
L 07/17/2014 - 14:21:41: "Nikolas<33><BOT><#Team_Security>" killed "Bruce<37><BOT><#Team_Insurgent>" with "grenade_m67" at (-3054.871094, 4648.378418, -775.821655)
L 07/17/2014 - 15:052: "Jeremy<79><BOT><#Team_Insurgent>" killed "Paul<76><BOT><#Team_Security>" with "grenade_f1" at (1052.742920, -2329.473389, 83.305519)

[FZFalzar]

-> 1.0.4
Fixes suicide messages, more info in changelog

[GiZZoR]

Looks like an issue with the object capturing. All human players on the server appear to be triggering the "ins_cp_captured" event.

L 07/17/2014 - 21:02:29: "GiZ<197><STEAM_1:1:11391458><#Team_Insurgent>" triggered "ins_cp_captured"
L 07/17/2014 - 21:02:29: "HAVOK_ZA<186><STEAM_1:0:44029383><#Team_Security>" triggered "ins_cp_captured"
L 07/17/2014 - 21:02:29: "Uberutang<230><STEAM_1:1:43124473><#Team_Insurgent>" triggered "ins_cp_captured"
L 07/17/2014 - 21:02:29: "[wrdn]Godfather<226><STEAM_1:0:89566231><#Team_Insurgent>" triggered "ins_cp_captured"
L 07/17/2014 - 21:02:29: "Sm00th3mi1<243><STEAM_1:1:10881483><#Team_Security>" triggered "ins_cp_captured"
L 07/17/2014 - 21:02:29: "Logan<244><STEAM_1:1:51675928><#Team_Security>" triggered "ins_cp_captured"
L 07/17/2014 - 21:02:29: "=slack=<252><STEAM_1:0:17662983><#Team_Security>" triggered "ins_cp_captured"

L 07/17/2014 - 21:05:00: "GiZ<197><STEAM_1:1:11391458><#Team_Insurgent>" triggered "ins_cp_captured"
L 07/17/2014 - 21:05:00: "HAVOK_ZA<186><STEAM_1:0:44029383><#Team_Security>" triggered "ins_cp_captured"
L 07/17/2014 - 21:05:00: "Uberutang<230><STEAM_1:1:43124473><#Team_Insurgent>" triggered "ins_cp_captured"
L 07/17/2014 - 21:05:00: "[wrdn]Godfather<226><STEAM_1:0:89566231><#Team_Insurgent>" triggered "ins_cp_captured"
L 07/17/2014 - 21:05:00: "Sm00th3mi1<243><STEAM_1:1:10881483><#Team_Security>" triggered "ins_cp_captured"
L 07/17/2014 - 21:05:00: "Logan<244><STEAM_1:1:51675928><#Team_Security>" triggered "ins_cp_captured"
L 07/17/2014 - 21:05:00: "=slack=<252><STEAM_1:0:17662983><#Team_Security>" triggered "ins_cp_captured"

[FZFalzar]

Yup, it was a design decision as all players should be rewarded as they have helped (in one or another) way to cap the objective. I could make a cvar to disable that.

[GiZZoR]

That I understand, however, if you read carefully... it's ALL human players on BOTH sides.
So, there is no way to tell who captured/destroyed the objective.

[FZFalzar]

-> 1.0.5 Please refer to the changelog in the main post!