Latency Manager (1.0.1.16) January 2017

Originally Posted by Zaeed*:

 

Basic information:

 

This plugin has two parts, a country based kicker, and a ping based kicker. The country kicker works as described here*.

 

The ping kicker has two methods of kicking, an instant kick, and an average kick. The average kick allows for you to define both the number of samples to use, and the minimum samples before acting on the average.

 

The plugin also has a trial version of a update notification system built in. If you decide to use it, you must first disable the sandbox mode. Messages will appear in the chat box, notifying you of an update to the plugin.

 

Ping wildcard for ping kick message is %ping%

Country wildcard for country kick message is %country%

 

 

Requirements:

Sandbox mode disabled for version control to work. If sandbox mode is enabled, the plugin will disable the version control.

 

Future Development:

- This is just in the drawing board phase, so input is more than welcomed. I envisage the plugin somehow handling the case when the server becomes laggy, and there are no more players to remove in an attempt to fix it. Perhaps something along the lines of triggering a server reboot when all players leave.

 

- Whitelist based on clan tag and reserved slots and country

 

- Disable kicking between two times

 

Installation:

- Extract CLatencyManager.cs into BF3 directory.

- Extract CLatencyManager.inc into Plugins folder

 

Current version:

1.0.1.16

 

Changelog:

1.0.1.16

- Fixed BF3 ping kicker

- Changed missing ping kicker with extra setting: start checking missing ping after x seconds:

 

Sometimes it takes a while for the players ping to appear, kicking them too soon (even during loading of the game.) With this setting you can control how long a player has to be in the server before the "missing ping check" starts. Players without ping will get several warning messages in ingame chat.

 

1.0.1.15

- Speeded up country kicker task

1.0.1.14

- Added option to disregard whitelist & player threshold for the country kicker.

 

1.0.1.13

- "No Ping" Kicker now checks the whitelist

 

1.0.1.11 -> 1.0.1.12

- Uncommented out kick function

1.0.1.10 -> 1.0.1.11

- Bug fixes

1.0.1.9 -> 1.0.1.10

- Fixed yell

- Switched to named kicks for BF4

1.0.1.7 -> 1.0.1.9

- Minor bug fix for issue with AdKats

1.0.1.6 -> 1.0.1.7

- Minor bug fix for poor BF4 leave logging

1.0.1.5 -> 1.0.1.6

- Minor bug fix for poor BF4 join logging

1.0.1.4 -> 1.0.1.5

- Added support for BF4

1.0.1.3 -> 1.0.1.4

- Added ability to kick players with no ping

1.0.1.2 -> 1.0.1.3

- Small bug fix

 

1.0.1.1 -> 1.0.1.2

- Small bug fix

 

1.0.1.0 -> 1.0.1.1

- Small bug fix

- Sorted Country List

 

1.0.0.1 -> 1.0.1.0

-Small performance gains

- Added Ingame messages

 

1.0.0.0 -> 1.0.0.1

Changed method of determining current player count

 

Download:

LatencyManager(1.0.1.16).zip

Attachment 4034

Attachment 3931

LatencyManager(1.0.1.13).zip

Download 1.0.1.12

 

Donations:

Donations for my work are more than welcome.

 

 

Thankyou to the following donators

ParaEXE

Yupster

IAF SDS

HexaCanon

kcuestag

xFaNtASyGiRLx

Blackis and clan =BF30=

GAZGAZ (www.big-team.ru)

jking54

_gp?

tonnic

EBassie

SnotGoblin

ixnorp

Originally Posted by kcuestag*:

 

Amazing, glad to be the first one to post here, thank you very much Zaeed!

 

Edit:

 

I love the "Minimum players before rule enforced", this allows me to set it to something like 35 so it doesn't kick people from America after midnight as those are the ones who normally keep my server alive at night!

 

This is great, will be testing the plugin tonight, thanks a lot, I will definitely donate for this.

Originally Posted by Zaeed*:

 

This is great, will be testing the plugin tonight, thanks a lot, I will definitely donate for this.

Cheers for that. Hopefully nothing goes wrong, but you never know.

Originally Posted by guapoloko*:

 

Thank Zaeed.

 

I will test them as soon as the update layer.

Originally Posted by kcuestag*:

 

Cheers for that. Hopefully nothing goes wrong, but you never know.

So far so good, I use the Average ping, as I think a simple ping spike is easy to occur for a few seconds with some connections, and so far it's worked good, we had a player with 320 ping on our server and it kicked him after less than 30 seconds, I kept it on default (20 pings to sample for average and 2 minimum pings before kicking, ping limit at 250).

 

If I keep it set at "20", how often does it ping players? Wondering if 20 by default is a good number.

 

Thank you!

Originally Posted by PapaCharlie9*:

 

Congrats! Good to see this available.

Originally Posted by Zaeed*:

 

So far so good, I use the Average ping, as I think a simple ping spike is easy to occur for a few seconds with some connections, and so far it's worked good, we had a player with 320 ping on our server and it kicked him after less than 30 seconds, I kept it on default (20 pings to sample for average and 2 minimum pings before kicking, ping limit at 250).

 

If I keep it set at "20", how often does it ping players? Wondering if 20 by default is a good number.

 

Thank you!

It checks the pings 10 seconds after admin.listPlayers is fired. So every 30seconds.

 

The 20 samples means that at most, only 20 values are being used to determine the average ping.

45|34|54|34|23|54|56|76|45|42|34|33|42|23|34

 

The two samples is the minimum needed before it determines what the average is able to kick based on that.

 

So in the above case of 15 samples, the average ping is

(45+34+54+34+23+54+56+76+45+42+34+33+42+23+34)/15 = 42

 

The two minimum would be 45 and 34, so the player would be first able to be kicked after the second was taken, and their average at that time would have been (45+34)/2 = 40

 

When the number of samples reaches the maximum set, i.e. 20, the first sample gets removed, and the latest one added. So you're always looking at the 20 latest pings.

Originally Posted by Jaythegreat1*:

 

Nice, will install this tonight.

Originally Posted by kcuestag*:

 

It checks the pings 10 seconds after admin.listPlayers is fired. So every 30seconds.

 

The 20 samples means that at most, only 20 values are being used to determine the average ping.

45|34|54|34|23|54|56|76|45|42|34|33|42|23|34

 

The two samples is the minimum needed before it determines what the average is able to kick based on that.

 

So in the above case of 15 samples, the average ping is

(45+34+54+34+23+54+56+76+45+42+34+33+42+23+34)/15 = 42

 

The two minimum would be 45 and 34, so the player would be first able to be kicked after the second was taken, and their average at that time would have been (45+34)/2 = 40

 

When the number of samples reaches the maximum set, i.e. 20, the first sample gets removed, and the latest one added. So you're always looking at the 20 latest pings.

Thanks for explaining it, seems to be working quite well.

Originally Posted by EBassie*:

 

Nice Work Zaeed!

 

I see you are still hidden on my server

Originally Posted by Zaeed*:

 

Nice Work Zaeed!

 

I see you are still hidden on my server

lurking away

Originally Posted by EBassie*:

 

lurking away

Did you not read my "No Lurking" Policy?

Originally Posted by kunoichia*:

 

Thanks going to install now and test.

Originally Posted by Zaeed*:

 

I did, I decided I'm above the law

Originally Posted by EBassie*:

 

I did, I decided I'm above the law

Did you now

Originally Posted by guapoloko*:

 

Zaeed, a new update on the white list could have an option to use the list of reserved slot?

Originally Posted by Zaeed*:

 

Zaeed, a new update on the white list could have an option to use the list of reserved slot?

Yep, that makes sense. I'll do that.

Originally Posted by Jaythegreat1*:

 

Seems like it still kick players even though I have it set at 48.

 

These kicks occurred

 

[19:07:44 46] Latency Manager: High average ping kick MadDog21589 (406)

[19:07:44 46] Latency Manager: High average ping kick riinsey (293)

Originally Posted by Zaeed*:

 

Hmm, looking into that.

Originally Posted by guapoloko*:

 

For me the plugin is working perfectly, congratulations.

Originally Posted by Zaeed*:

 

I *think* there is a bug in the method I use to determine the current player count.. I've shifted where it gets that value, just testing it now. if no problems found by 5pm (currently 10:40am) i'll post an update.

Originally Posted by EBassie*:

 

I *think* there is a bug in the method I use to determine the current player count.. I've shifted where it gets that value, just testing it now. if no problems found by 5pm (currently 10:40am) i'll post an update.

Let's see if we are able to kick some innocent bystander again

Originally Posted by Jaythegreat1*:

 

Curious if it is counting the neutral team in the player count?

Originally Posted by EBassie*:

 

Curious if it is counting the neutral team in the player count?

Yes, I believe it does.

Originally Posted by TheDoctor*:

 

I will be trying this out!

Originally Posted by kcuestag*:

 

I *think* there is a bug in the method I use to determine the current player count.. I've shifted where it gets that value, just testing it now. if no problems found by 5pm (currently 10:40am) i'll post an update.

Yeah, it's definitely broken, my server is now running rush with 30-35 players at the moment, I set it to minimum of 40 players before it enforces de ping rule, but still kicks people with above 200 ping.

Originally Posted by Zaeed*:

 

alright, i'll post the update.

Originally Posted by kcuestag*:

 

alright, i'll post the update.

Thanks, it would be the perfect time as I could try it on my server now that it's ~3AM and it's got around 25-40 players.

Originally Posted by Zaeed*:

 

Done, redownload the plugin and see how it goes

Originally Posted by kcuestag*:

 

Done, redownload the plugin and see how it goes

Done, let's see how it goes, I'll report back!

 

I lowered the limit to 150 ping as I see no one with 200 or above right now so I set it to 150 to test it right now and let you know if it works.