[B]KickBanLogger logs all kicks and bans from the server to a log file, and optionally sends to a slack channel too. [/B][LIST][]Logs information about the person who banned/kicked a player[]Logs information about the banned/kicked player[]Sends information to slack regarding the kick/ban. Information is provided about the banned/kicked player.[]Setting to choose what you want to send to Slack, or whether you want to disable the Slack functionality all together.[/LIST][B]Default configuration file (oxide/config/KBLogger.json)[/B][CODE]{"Bans": {"Send bans to slack": true},"Kicks": {"Only send violation kicks to slack (true/false)": true,"Send kicks to slack": true},"Slack": {"Channel": "kblogger","Enabled (true/false)": false}}[/CODE]
[B]Send bans to slack[/B] - Optionally sends bans to the slack channel. If set to false they will only be in the log file.[B]Only send violation kicks to slack (true/false)[/B] - Kicks have to be enabled for this to work. This will exclude all other kicks unless the kick reasons were for high violations. If set to false, all kicks will be sent to slack.[B]Send kicks to slack[/B] - Optionally sends all kick messages to the slack channel. If set to false they will only be in the log file.[B]Channel[/B] - The channel name of the channel you want these notices to be sent to. You need to create a hook URL and put that in Slacks configuration file for this to work correctly.[B]Enabled (true/false)[/B] - This toggles the slack functionality completely. If set to false, all other slack methods will not be used and only the log files will be used. [B]This is disabled by default![/B]
[B]Problems[/B]If you have any issues with setting up this plugin, let me know in the plugin thread and I will do my best to help you. Please provide any errors you get in your post.
The original author may request that this plugin be removed and there is a risk that the plugin may be unavailable in the future.
Note that the current maintainer may not have permission to assign a license to the plugin if they are not the original author, so explicit permission would need to be obtained from the original author in order for the plugin to remain openly available and guarantee that it will be around for all to enjoy going forward.

