Team Kill Tracker (4.0.0) 23-Mar-2015

[ImportBot 10]

Originally Posted by stajs*:

 

Team Kill Tracker

 

Description

Track team kill statistics and allow self-management of team killers.

 

Features

• Allows victims to forgive or punish (slay) their killers.
• Optional kick for team killers after reaching a punish limit.
• Configurable commands and messages.
• Optionally allow killers to apologize to avoid punishment.
• Optionally protect admins or whitelisted players from being punished.
• Shame the worst team killers at the end of the round.
• Integration with AdKats.

Docs

 

Download

 

Install

 

Settings

[ImportBot 10]

Originally Posted by PapaCharlie9*:

 

This needs a bump.

 

A link to the documentation would be useful.

[ImportBot 10]

Originally Posted by dyn*:

 

Somehow we totally missed this!

 

Will be installing and testing tonight on a few live servers. Thank you stajs.

 

Edited so I don't double post.

 

Had a chance to give it a test and all seems to be working as intended! In our tests we did try to see what would happen if a protected individual TK'd and then met the kicking threshold. Even though a prompt was given that user would be kicked, the protected user was not kicked and a message posted saying they were protected from such actions was displayed.

 

First impressions also seem great with the 'worst team killers' feature!

 

Possible Suggestions / Feature Requests:

 

Have a different message available (or none at all) to send to the victim for the team kill message. Right now that same message is being sent to both the victim and the killer. Might be nice to have the option to have a different message, "PLAYER1 killed you. !p to punish !f to forgive" or "TeamKilled Player 2! Watch your fire!"

 

The ability to tell the killer what their current team kill count is. Ideally, we could include this count in the message that is sent to the killer about watching their fire.

 

The ability to issue an admin player yell for TeamKills. I can't tell you how many times I've personally missed that a TK took place because it was only in the chat window. If it were an admin yell (selectable how long to display) on the killer's screen not only would it notify the killer they just team killed, but perhaps it would give a little bit of an annoyance to the killer in an effort to stop their probably bad aim.

 

I think we tested this... would be great if we could send a message to the KILLER stating WHO punished them, not simply that they were punished.

 

Overall -- seems to be working as intended. Should make this experience much better. Thank you

[ImportBot 10]

Originally Posted by stajs*:

 

This needs a bump.

 

A link to the documentation would be useful.

Done =)

[ImportBot 10]

Originally Posted by stajs*:

 

@dyn, thanks for the feedback! I'll look at extracting the "wall of text" as you put it, in to GitHub issues to track each of those points. I'll come back and drop links here when I get to them. I really appreciate the suggestions!

 

EDIT

 

I've got most of these in GitHub now.

 

Even though a prompt was given that user would be kicked, the protected user was not kicked and a message posted saying they were protected from such actions was displayed.

I think you were just confirming this works as intended, so thanks! I haven't added an issue for this.

 

Have a different message available (or none at all) to send to the victim for the team kill message.

See https://github.com/stajs/Stajs.Proco...acker/issues/1

 

The ability to tell the killer what their current team kill count is.

There is a "Kick countdown" message, that has a placeholder for the number of punishes left (see https://github.com/stajs/Stajs.Proco...acker#messages). I am thinking about consolidating all the placeholders in to just one message each for the killer and victim (see https://github.com/stajs/Stajs.Proco...acker/issues/4)

 

The ability to issue an admin player yell for TeamKills.

See https://github.com/stajs/Stajs.Proco...acker/issues/2

 

would be great if we could send a message to the KILLER stating WHO punished them

See https://github.com/stajs/Stajs.Proco...acker/issues/3

[ImportBot 10]

Originally Posted by Gazovik83*:

 

@stajs thank you for the nice plugin!

 

I have a question and suggestion:

 

Whether it is possible to make so that after timkiller again went on the server and again reached the limit for TKs it has not kicked a banned

[ImportBot 10]

Originally Posted by raeed*:

 

any help with NO LEVOLUTION rules?

[ImportBot 10]

Originally Posted by stajs*:

 

Whether it is possible to make so that after timkiller again went on the server and again reached the limit for TKs it has not kicked a banned

Thanks for the suggestion! I'll have to think about how this could work, but I've added it my issues for tracking here: https://github.com/stajs/Stajs.Proco...acker/issues/5

[ImportBot 10]

Originally Posted by stajs*:

 

any help with NO LEVOLUTION rules?

Can I clarify what you are asking, as it seems this is not team killing related: are you asking for help with a plugin to prevent levolution? If so, I don't think you can detect a levolution event, at least judging by this thread: showthread....ght=levolution*

[ImportBot 10]

Originally Posted by MadSochi*:

 

Thanks for a Plugin !

Now i can turn off the auto kick team killers and allow this function to players themself !

 

NOUP. One thing must be realesed in your plugin.

I'm talking about YELL message.

Like in Mixed Spam bot - if i want to see message of plugin in chat - i just print text. If i want to see this message of plugin in YELL - i print this message with @ tag.

 

For example:

To see message in simple chat

{killer} TEAM KILLED {victim} ! Watch your fire dum-dum!

 

To see message in YELL

@{killer} TEAM KILLED {victim} ! Watch your fire dum-dum!

 

or YELL message to specific player like a message "Type !f in chat to forgive or !p to punish!".

maybe with another tag to YELL only for victim.

[ImportBot 10]

Originally Posted by stajs*:

 

One thing must be realesed in your plugin.

I'm talking about YELL message.

@MadSochi thanks for the suggestion, I've folded it into this issue:

 

https://github.com/stajs/Stajs.Proco...acker/issues/2

[ImportBot 10]

Originally Posted by stajs*:

 

v2.0.0 is released.

 

You can now:

 

- optionally yell messages (@MadSochi, @dyn).

- have a different message for killer and victim (@dyn).

 

Let me know if you get a chance to test this. Don't forget to view the docs for the changes.

[ImportBot 10]

Originally Posted by ColColonCleaner*:

 

Note: A general standard for procon plugin version numbers is 4 digits. Major.Minor.Patch.Patch

[ImportBot 10]

Originally Posted by stajs*:

 

Interesting. Most communities are moving toward semantic versioning, see http://semver.org/

[ImportBot 10]

Originally Posted by ColColonCleaner*:

 

Interesting. Most communities are moving toward semantic versioning, see http://semver.org/

It's something that's just been in place for a long time here, i originally ran with semantic versioning, but changed it to match the format of other plugins.

 

https://myrcon.net/index.php?/forum/9-plugins/

[ImportBot 10]

Originally Posted by stajs*:

 

I guess I'm probably breaking that somehow.... I had no idea that existed! I just made another release, so I guess I'll see what happens with this one.

 

v2.1.0

 

- Added a placeholder for the {victim} to the punished/forgiven messages (@dyn).

 

v2.2.0

 

- Added a command to list the worst team killers.

 

v2.3.0

 

- Added a setting for public shaming on round end.

- Added messages for when there is no one to shame, either publicly or privately.

[ImportBot 10]

Originally Posted by dyn*:

 

Just updated to newest version (2.3.0) and am seeing several issues:

 

• Deleting a message from the list does not actually remove it. Have tried removing the message while the plugin is disabled / enabled and same thing. Simply deleting a message actually results in the message auto populating again. The same thing with changing a message... not able to get a change to stick.
• Our setting... Kick after punish limit reached: no. This still results in a message [ (AdminSayPlayer player) Watch your fire! Punishes left before kick: 9999
• The link for instructions in the plugin Description does not open anything up. While IE is not my default browser, other plugins (tested with ADKATS) does open an IE Window upon clicking. Obviously nothing major... just noticed it.

Really coming along so far. Your work has made managing team killers much easier. Thank you.

[ImportBot 10]

Originally Posted by kcuestag*:

 

Testing the plugin, so far it looks really nice, thank you!

[ImportBot 10]

Originally Posted by kcuestag*:

 

An idea for a future update, make an option so that we can disable the messages in the Procon chat, right now it's a huge spam of AdminSayPlayer and AdminYellPlayer, can't really read what people say as it's mostly clogged up with this plugin's messages.

 

http://puu.sh/bVjdJ/1e4ab7a110.png

[ImportBot 10]

Originally Posted by ColColonCleaner*:

 

An idea for a future update, make an option so that we can disable the messages in the Procon chat, right now it's a huge spam of AdminSayPlayer and AdminYellPlayer, can't really read what people say as it's mostly clogged up with this plugin's messages.

 

http://puu.sh/bVjdJ/1e4ab7a110.png

Regardless of the spam, standard procon seems to be going with this format :

 

Source > Target > Message

 

Some plugins add more to this, making it

 

Plugin > Method > Target > Message

 

for private messages, and

 

Plugin > Method > Message

 

for global messages.

 

Would be nice to keep things uniform ;D

 

TeamKillTracker > Say > stajs > Message

TeamKillTracker > Yell > stajs > Message

TeamKillTracker > Say > Message

TeamKillTracker > Yell > Message

[ImportBot 10]

Originally Posted by MadSochi*:

 

Works great on mine BF3 server. You can add BF3 tag to this plugin.

[ImportBot 10]

Originally Posted by stajs*:

 

Wow, some great feedback guys.

 

@dyn Thanks for testing and reporting those issues. I'll check 'em out when I get some time.

 

@kcuestag Thanks for testing. That is a lot of team killing going on! I had assumed that people would want to see the messages in chat log, but agree that is a lot going on for you there. Perhaps it would be better off in the plugin console thingy?

 

@ColColonCleaner Great suggestion again =) Will do.

 

@MadSochi Thanks for letting me know! Will do.

[ImportBot 10]

Originally Posted by ColColonCleaner*:

 

Perhaps it would be better off in the plugin console

Chat is chat, console is for debug purposes.

 

EDIT: That tab is great to see messages sent to players, but it can get to be a bit much. Perhaps instead of removing display of the messages, you can make them more concise. That would benefit both the players, and the admins. You are sending so many messages with each teamkill you are essentially wiping their chat box out.

[ImportBot 10]

Originally Posted by ColColonCleaner*:

 

Feature request.

 

 

Boolean setting, disabled by default. "Use AdKats Punishment".

 

 

AdKats has a punish system, but it is not intended for teamkill management as the punish/forgive commands are admin use only. With this plugin, it adds commands players can use.

 

When this feature is enabled, it would not use the internal kill/kick/ban action (or send any messages to the teamkiller. teamkillee is fine.) when someone punishes a teamkiller. Instead it would execute the following section of code. (Modify the record message as needed to match the standard punishment reason in your plugin)

 

Code:

if (GetRegisteredCommands().Any(
        command => command.RegisteredClassname == "AdKats" &&
        command.RegisteredMethodName == "IssueCommand"))
{
    var requestHashtable = new Hashtable{
        {"caller_identity", "TeamKillTracker"},
        {"response_requested", false},
        {"command_type", "player_punish"},
        {"source_name", "TeamKillTracker"},
        {"target_name", "ColColonCleaner"},
        {"target_guid", "EA_698E70AF4E420A99824EA9A438FE3CB1"},
        {"record_message", "Teamkilling stajs"}
    };
    ExecuteCommand("procon.protected.plugins.call", "AdKats", "IssueCommand", "TeamKillTracker", JSON.JsonEncode(requestHashtable));
}
else{
    //AdKats is not enabled, run your normal punishment code
}

This would add logging of punishments against teamkillers, automatic increasing punishment severity, and add more functionality to both plugins. This keeps compatibility with both BF3 and BF4.

[ImportBot 10]

Originally Posted by dyn*:

 

I'm seeing several people type: !punish even though it clearly says to type !p. While I do personally like !p better than the full !punish, wondering if it would make sense to still allow !punish (in any CaSe) to be accepted.

It also looks like !P is not accepted (the capital P)

 

Has anyone figured out how to change the messages so the changes remain?

[ImportBot 10]

Originally Posted by stajs*:

 

Thanks again for the suggestions and bug reports. I think I've got everything raised as an issue now:

 

- @dyn Changes to settings not persisting

- @dyn There should be no "punishes left before kick" when the punish limit is off

- @dyn The description link doesn't open a browser

- @kcuestag Add setting to show messages in Procon chat

- @ColColonCleaner Follow standard format for Procon chat messages

- @ColColonCleaner Use AdKats Punishment

- @dyn Use case-insensitive matching for commands

- @dyn Allow multiple text matching for commands

[ImportBot 10]

Originally Posted by stajs*:

 

EDIT: That tab is great to see messages sent to players, but it can get to be a bit much. Perhaps instead of removing display of the messages, you can make them more concise. That would benefit both the players, and the admins. You are sending so many messages with each teamkill you are essentially wiping their chat box out.

In my defense, the number of messages (lines) is configurable so servers can spam as much or as little as they like (let's just ignore the fact that saving messages appears to have a bug ATM!). But yes, I agree, conciseness is usually best. And I don't think you are suggesting that the Procon chat tab should have a different shorter equivalent of the message sent to the player, but I'm just clarifying: what appears in the chat tab should exactly mirror what was sent in game IMHO.

 

Wiping out the chat box is pretty bad. I haven't come across that much TK'ing in my testing! I have raised an issue to make it optional to send messages to the chat box, so I'll see if that helps.

[ImportBot 10]

Originally Posted by stajs*:

 

Has anyone figured out how to change the messages so the changes remain?

I've written up how I save the settings here: https://github.com/stajs/Stajs.Proco...cker/issues/10

 

Would you mind having a look and seeing if that works for you? EDIT: I've closed the issue now, as ColColonCleaner has verified that it works as intended, but still interested to hear if you are having problems.

 

v2.3.1

 

- Added a debug setting to allow suicides to be counted as a team kill.

[ImportBot 10]

Originally Posted by kcuestag*:

 

Any ETA on having an option to remove the messages in Procon's chat window? Way too much text there.

 

Thanks!

[ImportBot 10]

Originally Posted by dyn*:

 

AHHH I feel like such a procon noob here! I totally knew that we had to click the three little dots to make an edit!

 

kcuestag: To remove chat spam follow the instructions above your post to add / remove as you see fit.

 

stajs thanks for the super easy (noob :x) instructions. Made it super easy.