Jump to content

Team Kill Tracker (4.0.0) 23-Mar-2015


ImportBot

Recommended Posts

  • Replies 180
  • Created
  • Last Reply

Top Posters In This Topic

  • ImportBot

    181

Originally Posted by TMiland*:

 

Yeah... those changes might be the death of this plugin =/

 

But great that it was working for you; I'm gonna merge those changes in for a new release.

You can still punish and forgive players, so it is still working. :smile:
* Restored post. It could be that the author is no longer active.
Link to comment

Originally Posted by IAF-SDS*:

 

Holy shit, how did I miss that? Have you got a link to source for that, or is it in the latest patch notes? Goddamit.

DICE's patch notes are not detailed nor do they address these changes (which is usually the case), but I verified it myself on my servers. I knew what to look for because it is the same TK changes they had done a long time ago when they first introduced them together with the 300 secs IdleTime requirement.

 

You may test it yourself. Set your server to Hardcore by setting vars.teamKillCountForKick 5 and vars.teamKillKickForBan 3 (as well as vars.idleTimeout 300).

 

Grab a friend and TK him 5 times in the first map to confirm you get kicked with vars.teamKillCountForKick 5. TK him another 5 times in the same map to get kicked a second time. In the second map, TK him 5 times to get auto banned which will confirm the TK count does not reset when a new map is loaded (the ban shows up as TeamKillBan in ProCon). Note that you can't properly test this in Pre-Round because TeamKilling in Pre-Round does not trigger the server's kick, so make sure the round has started.

* Restored post. It could be that the author is no longer active.
Link to comment

Originally Posted by stajs*:

 

Thanks for that info. I did have a quick play last night and set the server to Hardcore with lock all presets ticked via the UI in Procon, ticked all the TK boxes to turn 'em off, closed Procon and re-opened and the TK boxes were unticked again. This is just from my (poor) memory of playing around last night, so take with a grain of salt.

* Restored post. It could be that the author is no longer active.
Link to comment

Originally Posted by TMiland*:

 

Just checked and it's there for me. Perhaps stop your layer, delete old DLL, copy new file and restart your layer?

 

2014-12-14 00_39_51-Procon Frostbite.png

I see it is there in the code, i have stopped the layer, deleted the dll and started it again, several times. :woot:
* Restored post. It could be that the author is no longer active.
Link to comment

Originally Posted by stajs*:

 

Very strange. I would like to help you figure out what is going on here, so please forgive any "stupid" questions while I check assumptions. On the "Details" tab of the plugin, is it showing the right version (3.5.0.0)? If you enable/disable it, does the plugin echo back the state in the output below?

* Restored post. It could be that the author is no longer active.
Link to comment

Originally Posted by TMiland*:

 

Very strange. I would like to help you figure out what is going on here, so please forgive any "stupid" questions while I check assumptions. On the "Details" tab of the plugin, is it showing the right version (3.5.0.0)? If you enable/disable it, does the plugin echo back the state in the output below?

Eeh, now it is present. No idea why, but it is. :biggrin:
* Restored post. It could be that the author is no longer active.
Link to comment

Originally Posted by Tomgun*:

 

could there be an option to have certain weapons unpublishable (in a whitelist), reason is I know claymores are a looked upon as stupid in hardcore but in my opinion if you just run around like a chicken and dont open your eyes then its your fault for running into an team mates claymore (go play softcore). The thing has a glowing icon and the amount of times I have layed a claymore to protect my back, someone just spawns on me and runs off right into it when it clear as day is countless. Then they punish you because they are blind!!!

* Restored post. It could be that the author is no longer active.
Link to comment

Originally Posted by TMiland*:

 

could there be an option to have certain weapons unpublishable (in a whitelist), reason is I know claymores are a looked upon as stupid in hardcore but in my opinion if you just run around like a chicken and dont open your eyes then its your fault for running into an team mates claymore (go play softcore). The thing has a glowing icon and the amount of times I have layed a claymore to protect my back, someone just spawns on me and runs off right into it when it clear as day is countless. Then they punish you because they are blind!!!

Agreed! :cool:
* Restored post. It could be that the author is no longer active.
Link to comment

Originally Posted by ColColonCleaner*:

 

could there be an option to have certain weapons unpublishable (in a whitelist), reason is I know claymores are a looked upon as stupid in hardcore but in my opinion if you just run around like a chicken and dont open your eyes then its your fault for running into an team mates claymore (go play softcore). The thing has a glowing icon and the amount of times I have layed a claymore to protect my back, someone just spawns on me and runs off right into it when it clear as day is countless. Then they punish you because they are blind!!!

Does that still count as a TK toward kick by the game though?
* Restored post. It could be that the author is no longer active.
Link to comment

Originally Posted by stajs*:

 

could there be an option to have certain weapons unpublishable (in a whitelist), reason is I know claymores are a looked upon as stupid in hardcore but in my opinion if you just run around like a chicken and dont open your eyes then its your fault for running into an team mates claymore (go play softcore). The thing has a glowing icon and the amount of times I have layed a claymore to protect my back, someone just spawns on me and runs off right into it when it clear as day is countless. Then they punish you because they are blind!!!

https://github.com/stajs/Stajs.Proco...cker/issues/33
* Restored post. It could be that the author is no longer active.
Link to comment

Originally Posted by ColColonCleaner*:

 

My first thought was, if it isn't punishable it shouldn't count. Open to suggestions though.

It's not up to us though, I was asking if the server counted it as a teamkill toward being kicked/banned, because it's not your fault if your team are idiots and run into your claymores.
* Restored post. It could be that the author is no longer active.
Link to comment

Originally Posted by stajs*:

 

Oh, you were talking about kicked by the game (the built-in team killing management) rather than my plugin? If you are worried about that, you can uncheck "No teamkill value limit" under "Server Settings > Team killing" in Procon and apply a really high value to effectively disable it.

 

I was thinking this plugin shouldn't count a TK if it isn't punishable.

* Restored post. It could be that the author is no longer active.
Link to comment

Originally Posted by ColColonCleaner*:

 

Oh, you were talking about kicked by the game (the built-in team killing management) rather than my plugin? If you are worried about that, you can uncheck "No teamkill value limit" under "Server Settings > Team killing" in Procon and apply a really high value to effectively disable it.

 

I was thinking this plugin shouldn't count a TK if it isn't punishable.

But nobody runs that because it makes the server custom still? Or did they fix that? I haven't exactly had my finger on the pulse of updates recently.
* Restored post. It could be that the author is no longer active.
Link to comment

Originally Posted by stajs*:

 

But nobody runs that because it makes the server custom still? Or did they fix that? I haven't exactly had my finger on the pulse of updates recently.

It doesn't seem to make it custom from my testing. In Procon, if you choose to "Lock preset related values", the first two team killing options become disabled, but this one remains enabled.
* Restored post. It could be that the author is no longer active.
Link to comment

Originally Posted by IAF-SDS*:

 

It doesn't seem to make it custom from my testing. In Procon, if you choose to "Lock preset related values", the first two team killing options become disabled, but this one remains enabled.

Unfortunately, that's not correct.

 

If you want to properly test it to remove any doubt, go to your server in battlelog and notice it shows Hardcore when you have vars.teamKillCountForKick 5 and vars.teamKillKickForBan 3.

 

Now, go into your ProCon Console tab and enter vars.teamKillCountForKick 10 (or any number other than 5) and press Send.

 

Refresh your server's page in battlelog and notice you're now Custom.

 

 

If you "Lock preset related values" you're basically telling the server to use vars.teamKillCountForKick 5 and vars.teamKillKickForBan 3 which are required to conform with the Hardcore preset.

 

If you uncheck the "No teamkill value limit" under "Server Settings > Team killing" in Procon and apply a really high value as you said, this has no impact because it is for the Team Kill value or "cool down" system and it works independent of the TeamKill count system (the value aka cool down system is broken and it is useless when the server kicks at 5TKs no matter what). In other words, the vars.teamKillValue variables (vars.teamKillValueForKick, vars.teamKillValueIncrease, and vars.teamKillValueDecreasePerSecond) are what you're changing with the settings to the right of No teamkill value limit.

 

Any value other than vars.teamKillCountForKick 5 makes you Custom, and any value other than vars.teamKillKickForBan 3 make you Custom as well.

 

 

In fact, to be sure nothing has changed since I last posted, I just confirmed everything I said above is still the case.

 

Notice also that the team kill count does not reset when a map changes and only resets when the server restarts. This means players get banned if they play too many hours in your server and accumulate the 15 TeamKills (or 3 TKs per map x 5 maps = TeamKillBan).

 

So DICE broke the forgive system, because no matter if you're forgiven and no matter what you set the broken TeamKill value system to, you're getting kicked on the 5th TK in a server designated as Hardcore (instead of Custom).

* Restored post. It could be that the author is no longer active.
Link to comment

Originally Posted by stajs*:

 

Unfortunately, that's not correct.

Well, it is correct but I guess your point is, it doesn't make a lick of difference :sad:

 

If you "Lock preset related values" you're basically telling the server to use vars.teamKillCountForKick 5 and vars.teamKillKickForBan 3 which are required to conform with the Hardcore preset.

 

Any value other than vars.teamKillCountForKick 5 makes you Custom, and any value other than vars.teamKillKickForBan 3 make you Custom as well.

Yep, there was no argument there.

 

If you uncheck the "No teamkill value limit" under "Server Settings > Team killing" in Procon and apply a really high value as you said, this has no impact because it is for the Team Kill value or "cool down" system and it works independent of the TeamKill count system (the value aka cool down system is broken and it is useless when the server kicks at 5TKs no matter what). In other words, the vars.teamKillValue variables (vars.teamKillValueForKick, vars.teamKillValueIncrease, and vars.teamKillValueDecreasePerSecond) are what you're changing with the settings to the right of No teamkill value limit.

Ah, okay. I had (wrongly) believed the Procon UI: A player will be kicked for teamkilling a minimum of 4100.0 player(s) in one second or at a minimum rate of 4160.00 player(s) per minute. I did realise I was changing the "value" variables and I had assumed they would... do something. I had no idea it was so horribly broken.

 

Well, so much for that idea!

* Restored post. It could be that the author is no longer active.
Link to comment

Originally Posted by stajs*:

 

this has no impact because it is for the Team Kill value or "cool down" system and it works independent of the TeamKill count system.

I was probably a bit harsh, perhaps it isn't horribly broken. I didn't notice the independence of these systems. I found a post with a bit of history on them:

 

showthread....variables-work*

* Restored post. It could be that the author is no longer active.
Link to comment

Originally Posted by IAF-SDS*:

 

Well it is broken, in the sense that there is not an adequate amount of room for the TeamKill value system to work. For it to work, one would set their vars.teamKillCountForKick to a number much higher than their vars.teamKillValueForKick, but DICE is forcing us to kick at vars.teamKillCountForKick 5.

 

For example, if you wanted to kick a player at 5 TKs but give him a chance to get cool down credit, you could set vars.teamKillValueForKick 5 with vars.teamKillValueIncrease 1 and vars.teamKillValueDecreasePerSecond .0033 to have 1 TK subtracted about every 5 minutes. Then you could set vars.teamKillCountForKick 10 so that person would be kicked no matter what at the tenth TK, regardless of cool down credit from the value system. But again, neither the value system nor the forgive system can function when DICE is forcing us to use vars.teamKillCountForKick 5 for Hardcore designation.

* Restored post. It could be that the author is no longer active.
Link to comment

Originally Posted by Slayer*:

 

That's some dedication!

 

TBH the changes that DICE have made for team killing really hobbles this plugin (if you don't want to run your server Custom that is).

 

=(

BUGGA that sucks it really sounded quite good, wish Dice would let us run the servers how we want within their TOS, hell most of you lot out there actually pay for your servers and must find it frustrating even more than I at what they are doing. :/

 

Presently I run the ProconRulz teamkill script and thought your plugin might be a nice change to try from the below. :sad:

 

Code:

#########################################################
# Teamkill Punisher v1.2
# Original Author ty_ger07, tweak by bambam
# Enhancements by russel5
#########################################################

On Spawn;ServerFirst;Set %ini_punish% 0
On TeamKill;PlayerSay %p% you TEAMKILLED %v%. Watch your fire! This is your %c% victim.
On TeamKill;VictimSay %v%: !p or !f
# Team Kill Tracking Rulz
On TeamKill;Set %server_lastteamkill[%p%]% %v%
On TeamKill;Set %server_lastteamkiller[%v%]% %p%
# Team Kill Punish Rulz
On Say;Text !p,!punish;If %server_lastteamkiller[%p%]% == 0;PlayerSay %p%: could not find a recent team kill to punish.
On Say;Text !p,!punish;If %server_lastteamkiller[%p%]% != 0
	Incr %ini_punish_count[%server_lastteamkiller[%p%]%]%
	If %ini_punish_count[%p%]% == 3;TempBan 7200 %p% TempBan 2 hours;Set %ini_punish_count[%p%]% 0
	TargetPlayer %server_lastteamkiller[%p%]%;TargetAction PlayerSay %t% killed for team killing.;TargetAction Kill;TargetConfirm;Set %server_lastteamkiller[%p%]% 0
# Team Kill Forgive Rulz
On Say;Text !f,!forgive;If %server_lastteamkiller[%p%]% == 0;PlayerSay %p%: could not find a recent team kill to forgive.
On Say;Text !f,!forgive;If %server_lastteamkiller[%p%]% != 0;TargetPlayer %server_lastteamkiller[%p%]%;Set %server_lastteamkill[%server_lastteamkiller[%p%]%]% 0;TargetAction PlayerSay %t% was forgiven by %p%.;Set %server_lastteamkiller[%p%]% 0
#Leave
On Leave;Set %ini_punish_count[%p%]% 0
* Restored post. It could be that the author is no longer active.
Link to comment

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.

Guest
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.




  • Our picks

    • Game Server Hosting:

      We're happy to announce that EZRCON will branch out into the game server provider scene. This is a big step for us so please having patience if something doesn't go right in this area. Now, what makes us different compared to other providers? Well, we're going with the idea of having a scaleable server hosting and providing more control in how you set up your server. For example, in Minecraft, you have the ability to control how many CPU cores you wish your server to have access to, how much RAM you want to use, how much disk space you want to use. This type of control can't be offered in a single service package so you're able to configure a custom package the way you want it.

      You can see all the available games here. Currently, we have the following games available.

      Valheim (From $1.50 USD)


      Rust (From $3.20 USD)


      Minecraft (Basic) (From $4.00 USD)


      Call of Duty 4X (From $7.00 USD)


      OpenTTD (From $4.00 USD)


      Squad (From $9.00 USD)


      Insurgency: Sandstorm (From $6.40 USD)


      Changes to US-East:

      Starting in January 2022, we will be moving to a different provider that has better support, better infrastructure, and better connectivity. We've noticed that the connection/routes to this location are not ideal and it's been hard getting support to correct this. Our contract for our two servers ends in March/April respectively. If you currently have servers in this location you will be migrated over to the new provider. We'll have more details when the time comes closer to January. The new location for this change will be based out of Atlanta, GA. If you have any questions/concerns please open a ticket and we'll do our best to answer them.
      • 5 replies
    • Hello All,

      I wanted to give an update to how EZRCON is doing. As of today we have 56 active customers using the services offered. I'm glad its doing so well and it hasn't been 1 year yet. To those that have services with EZRCON, I hope the service is doing well and if not please let us know so that we can improve it where possible. We've done quite a few changes behind the scenes to improve the performance hopefully. 

      We'll be launching a new location for hosting procon layers in either Los Angeles, USA or Chicago, IL. Still being decided on where the placement should be but these two locations are not set in stone yet. We would like to get feedback on where we should have a new location for hosting the Procon Layers, which you can do by replying to this topic. A poll will be created where people can vote on which location they would like to see.

      We're also looking for some suggestions on what else you would like to see for hosting provider options. So please let us know your thoughts on this matter.
      • 4 replies
    • Added ability to disable the new API check for player country info


      Updated GeoIP database file


      Removed usage sending stats


      Added EZRCON ad banner



      If you are upgrading then you may need to add these two lines to your existing installation in the file procon.cfg. To enable these options just change False to True.

      procon.private.options.UseGeoIpFileOnly False
      procon.private.options.BlockRssFeedNews False



       
      • 2 replies
    • I wanted I let you know that I am starting to build out the foundation for the hosting services that I talked about here. The pricing model I was originally going for wasn't going to be suitable for how I want to build it. So instead I decided to offer each service as it's own product instead of a package deal. In the future, hopefully, I will be able to do this and offer discounts to those that choose it.

      Here is how the pricing is laid out for each service as well as information about each. This is as of 7/12/2020.

      Single MySQL database (up to 30 GB) is $10 USD per month.



      If you go over the 30 GB usage for the database then each additional gigabyte is charged at $0.10 USD each billing cycle. If you're under 30GB you don't need to worry about this.


      Databases are replicated across 3 zones (regions) for redundancy. One (1) on the east coast of the USA, One (1) in Frankfurt, and One (1) in Singapore. Depending on the demand, this would grow to more regions.


      Databases will also be backed up daily and retained for 7 days.




      Procon Layer will be $2 USD per month.


      Each layer will only allow one (1) game server connection. The reason behind this is for performance.


      Each layer will also come with all available plugins installed by default. This is to help facilitate faster deployments and get you up and running quickly.


      Each layer will automatically restart if Procon crashes. 


      Each layer will also automatically restart daily at midnight to make sure it stays in tip-top shape.


      Custom plugins can be installed by submitting a support ticket.




      Battlefield Admin Control Panel (BFACP) will be $5 USD per month


      As I am still working on building version 3 of the software, I will be installing the last version I did. Once I complete version 3 it will automatically be upgraded for you.





      All these services will be managed by me so you don't have to worry about the technical side of things to get up and going.

      If you would like to see how much it would cost for the services, I made a calculator that you can use. It can be found here https://ezrcon.com/calculator.html

       
      • 11 replies
    • I have pushed out a new minor release which updates the geodata pull (flags in the playerlisting). This should be way more accurate now. As always, please let me know if any problems show up.

       
      • 9 replies
×
×
  • Create New...

Important Information

Please review our Terms of Use and Privacy Policy. We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue.