[RELEASE] Generic Log Parser
-
Introduction
This is a rather simple plug-in that takes events from the game log and translates them into punishments. This is most likely only relevant to people writing their own GSC.
We at AWOG are using this to punish EMP-ing of perks. Whenever a perk is EMP’d the following log line is written
ScriptPerkEMP;<attacker guid>;<attacker slot>
The plug-in uses the following config to translate this into warnings in IW4ma. Which causes the well known behavior on our servers.
{ "EventName": "ScriptPerkEMP", "targetsPlayer": true, "Punishment": "warn", "Message": "Do NOT EMP the Perks!" }
Features:
- Can be used to react to any in-game event
- Customize-able actions
- Customize able messages
Changelog:
- c1cbcee
- Ignore Bots in events to prevent issues.
Download:
You are NOT allowed to mirror or hot link this file.
-
@Xerxes Excuse me, what other punishments can I use. I try to use “ban” and IW4MAdmin does not start, it gives me an error.
On the other hand, if I use “kick”, the application starts normally.
I need to use “ban” in this case. -
The currently public version has those modes.
flag, //Flag warn, //Only warn kick, //Only kick warnKick, //Warn then Kick
The new version will have 2 more. If you want to I can add ban as well.
-
@Xerxes
Hi, I’m new to IW4MAdmin and server management.
I want to enable auto bans for cheating.
From what I understand, IW4MAdmin only monitors but doesn’t ban cheaters automatically.
Do I need to use your plugin to enable auto banning? If yes, could you please guide me on how to set it up? -
This post is deleted! -
@nimaydp said in [RELEASE] Generic Log Parser:
IW4MAdmin only monitors but doesn’t ban cheaters automatically.
Hi, this isn’t true, IW4m Admin does ban cheaters if it detects them via its statistics plugin. You can use this plugin to build additional detections in GSC and then instruct IW4m Admin to add additional bans, one example is by detecting if the classes of players are manipulated.