Jump to content

Latency Manager (1.0.1.16) January 2017


ImportBot

Recommended Posts

Originally Posted by Zaeed*:

 

What do you mean?

 

My debug monitor "issue" of "kicking over and over" is fixed.

The plugin does a version check when you enable it.

 

So when a new version is released, your plugin will begin to print messages to the chat console telling you that an update is available.

 

Since a lot of admins won't be checking the procon forums very often, and the packages system is no longer available, I'm looking into new ways of notifying admins that a plugin update is available.

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

Originally Posted by kcuestag*:

 

The plugin does a version check when you enable it.

 

So when a new version is released, your plugin will begin to print messages to the chat console telling you that an update is available.

 

Since a lot of admins won't be checking the procon forums very often, and the packages system is no longer available, I'm looking into new ways of notifying admins that a plugin update is available.

Honestly I think that's good enough, when I'm not playing and I'm just watching a movie I keep procon opened with the chat tab opened, and I can clearly see the purple "update" messages.
* Restored post. It could be that the author is no longer active.
Link to comment

Originally Posted by MorpheusX(AUT)*:

 

How about putting it into a taskbar notification rather than plugin.log? I get a lot of software update notifications through the taskbar, what's one more?

The Procon taskbar notificarion will not work in 90% of all cases since the popup will appear at the layer's server.
* Restored post. It could be that the author is no longer active.
Link to comment

Originally Posted by PapaCharlie9*:

 

The Procon taskbar notificarion will not work in 90% of all cases since the popup will appear at the layer's server.

I had assumed the notification was communicated by the layer to clients, but I guess not. Maybe that can be a wish list item for Procon?

 

It might not matter. I might go the nuclear route and just have my plugin disable itself if an update is available. So what I really want from Procon is a way to communicate what the latest production plugin version is. Meh, I'll take this to Developers.

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

Originally Posted by Mandizzy*:

 

yep. I have EB testing a new version now.. If all goes to plan, it'll be good to go tomorrow.. I think it's just getting confused about who's in the server.. No biggie

This issues is still present in latest version 1.0.1.1

 

Code:

[19:15:42 78] Latency Manager: High average ping kick PattonTheBack (201)
[19:16:03 81] Latency Manager: High average ping kick HiddenPuppy (226)
[19:16:03 81] Latency Manager: High average ping kick oryloun (270)
[19:16:03 81] Latency Manager: High average ping kick PattonTheBack (201)
[19:16:24 84] Latency Manager: High average ping kick HiddenPuppy (226)
[19:16:24 84] Latency Manager: High average ping kick oryloun (270)
[19:16:24 84] Latency Manager: High average ping kick PattonTheBack (201)
[19:16:43 92] Latency Manager: High average ping kick HiddenPuppy (226)
[19:16:43 92] Latency Manager: High average ping kick oryloun (270)
[19:16:43 92] Latency Manager: High average ping kick PattonTheBack (201)
[19:17:03 95] Latency Manager: High average ping kick HiddenPuppy (226)
[19:17:03 95] Latency Manager: High average ping kick oryloun (270)
[19:17:03 95] Latency Manager: High average ping kick PattonTheBack (201)
[19:17:14 95] Latency Manager: High average ping kick HiddenPuppy (226)
[19:17:14 95] Latency Manager: High average ping kick oryloun (270)
[19:17:14 95] Latency Manager: High average ping kick PattonTheBack (201)
[19:17:30 01] Latency Manager: High average ping kick HiddenPuppy (226)
[19:17:30 01] Latency Manager: High average ping kick oryloun (270)
[19:17:30 01] Latency Manager: High average ping kick PattonTheBack (201)
[19:17:41 01] Latency Manager: High average ping kick HiddenPuppy (226)
[19:17:41 01] Latency Manager: High average ping kick oryloun (270)
[19:17:41 01] Latency Manager: High average ping kick PattonTheBack (201)
[19:17:56 03] Latency Manager: High average ping kick HiddenPuppy (226)
[19:17:56 03] Latency Manager: High average ping kick oryloun (270)
[19:17:56 03] Latency Manager: High average ping kick PattonTheBack (201)
[19:18:04 07] Latency Manager: High average ping kick HiddenPuppy (226)
[19:18:04 07] Latency Manager: High average ping kick oryloun (270)
[19:18:04 07] Latency Manager: High average ping kick PattonTheBack (201)
[19:18:15 06] Latency Manager: High average ping kick HiddenPuppy (226)
[19:18:15 07] Latency Manager: High average ping kick oryloun (270)
[19:18:15 09] Latency Manager: High average ping kick PattonTheBack (201)
[19:18:34 06] Latency Manager: High average ping kick HiddenPuppy (226)
[19:18:34 06] Latency Manager: High average ping kick oryloun (270)
[19:18:34 06] Latency Manager: High average ping kick PattonTheBack (201)
[19:18:46 06] Latency Manager: High average ping kick HiddenPuppy (226)
[19:18:46 06] Latency Manager: High average ping kick oryloun (270)
[19:18:46 06] Latency Manager: High average ping kick PattonTheBack (201)
[19:18:57 06] Latency Manager: High average ping kick HiddenPuppy (226)
[19:18:57 06] Latency Manager: High average ping kick oryloun (270)
[19:18:57 06] Latency Manager: High average ping kick PattonTheBack (201)
[19:19:09 06] Latency Manager: High average ping kick HiddenPuppy (226)
[19:19:09 06] Latency Manager: High average ping kick oryloun (270)
[19:19:09 06] Latency Manager: High average ping kick PattonTheBack (201)
[19:19:27 06] Latency Manager: High average ping kick HiddenPuppy (226)
[19:19:27 06] Latency Manager: High average ping kick oryloun (270)
[19:19:27 06] Latency Manager: High average ping kick PattonTheBack (201)
[19:19:40 06] Latency Manager: High average ping kick HiddenPuppy (226)
[19:19:40 06] Latency Manager: High average ping kick oryloun (270)
[19:19:40 06] Latency Manager: High average ping kick PattonTheBack (201)
[19:19:58 06] Latency Manager: High average ping kick HiddenPuppy (226)
[19:19:58 06] Latency Manager: High average ping kick oryloun (270)
[19:19:58 06] Latency Manager: High average ping kick PattonTheBack (201)
[19:20:05 06] Latency Manager: High average ping kick HiddenPuppy (226)
[19:20:05 06] Latency Manager: High average ping kick oryloun (270)
[19:20:05 06] Latency Manager: High average ping kick PattonTheBack (201)
[19:20:17 06] Latency Manager: High average ping kick HiddenPuppy (226)
[19:20:17 06] Latency Manager: High average ping kick oryloun (270)
[19:20:17 06] Latency Manager: High average ping kick PattonTheBack (201)
[19:20:28 10] Latency Manager: High average ping kick HiddenPuppy (226)
[19:20:28 15] Latency Manager: High average ping kick oryloun (270)
[19:20:28 15] Latency Manager: High average ping kick PattonTheBack (201)
[19:20:42 07] Latency Manager: High average ping kick HiddenPuppy (226)
[19:20:42 07] Latency Manager: High average ping kick oryloun (270)
[19:20:42 07] Latency Manager: High average ping kick PattonTheBack (201)
[19:20:58 09] Latency Manager: High average ping kick HiddenPuppy (226)
[19:20:58 09] Latency Manager: High average ping kick oryloun (270)
[19:20:58 09] Latency Manager: High average ping kick PattonTheBack (201)
[19:21:10 12] Latency Manager: High average ping kick HiddenPuppy (226)
[19:21:10 12] Latency Manager: High average ping kick oryloun (270)
[19:21:10 12] Latency Manager: High average ping kick PattonTheBack (201)
[19:21:29 18] Latency Manager: High average ping kick HiddenPuppy (226)
[19:21:29 18] Latency Manager: High average ping kick oryloun (270)
[19:21:29 18] Latency Manager: High average ping kick PattonTheBack (201)
[19:21:41 18] Latency Manager: High average ping kick HiddenPuppy (226)
[19:21:41 18] Latency Manager: High average ping kick oryloun (270)
[19:21:41 18] Latency Manager: High average ping kick PattonTheBack (201)
[19:21:45 18] Latency Manager: High average ping kick HiddenPuppy (226)
[19:21:45 18] Latency Manager: High average ping kick oryloun (270)
[19:21:45 18] Latency Manager: High average ping kick PattonTheBack (201)
[19:22:00 18] Latency Manager: High average ping kick HiddenPuppy (226)
[19:22:00 18] Latency Manager: High average ping kick oryloun (270)
[19:22:00 18] Latency Manager: High average ping kick PattonTheBack (201)
[19:22:11 18] Latency Manager: High average ping kick HiddenPuppy (226)
[19:22:11 18] Latency Manager: High average ping kick oryloun (270)
[19:22:11 18] Latency Manager: High average ping kick PattonTheBack (201)
[19:22:29 26] Latency Manager: High average ping kick HiddenPuppy (226)
[19:22:29 26] Latency Manager: High average ping kick oryloun (270)
[19:22:29 26] Latency Manager: High average ping kick PattonTheBack (201)
[19:22:42 28] Latency Manager: High average ping kick HiddenPuppy (226)
[19:22:42 28] Latency Manager: High average ping kick oryloun (270)
[19:22:42 28] Latency Manager: High average ping kick PattonTheBack (201)
[19:22:57 31] Latency Manager: High average ping kick HiddenPuppy (226)
[19:22:57 31] Latency Manager: High average ping kick oryloun (270)
[19:22:57 31] Latency Manager: High average ping kick PattonTheBack (201)
[19:23:04 31] Latency Manager: High average ping kick HiddenPuppy (226)
[19:23:04 31] Latency Manager: High average ping kick oryloun (270)
[19:23:04 31] Latency Manager: High average ping kick PattonTheBack (201)
[19:23:20 32] Latency Manager: High average ping kick HiddenPuppy (226)
[19:23:20 34] Latency Manager: High average ping kick oryloun (270)
[19:23:20 35] Latency Manager: High average ping kick PattonTheBack (201)
[19:23:38 31] Latency Manager: High average ping kick HiddenPuppy (226)
[19:23:38 31] Latency Manager: High average ping kick oryloun (270)
[19:23:38 31] Latency Manager: High average ping kick PattonTheBack (201)
[19:23:42 31] Latency Manager: High average ping kick HiddenPuppy (226)
[19:23:42 31] Latency Manager: High average ping kick oryloun (270)
[19:23:42 31] Latency Manager: High average ping kick PattonTheBack (201)
[19:23:50 31] Latency Manager: High average ping kick HiddenPuppy (226)
[19:23:50 31] Latency Manager: High average ping kick oryloun (270)
[19:23:50 32] Latency Manager: High average ping kick PattonTheBack (201)
* Restored post. It could be that the author is no longer active.
Link to comment

Originally Posted by eagle-rr*:

 

I've uploaded the files into my BF3 server's Procon Layer. Procon layer is running version 1.4.0.9 and the Latency Manager plugin (version 1.0.1.1) shows enabled. I have the following settings:

- Enable high ping kick? Yes

- Ping Kick Method: Average ping

- Pings to sample for average: 7

- Minimum pings before kicking: 10

- Ping limit: 300

- High ping kick message: High ping (%ping%)

- Debug Messages? Yes

- Ingame Messages? Yes

- Yell or Say ingame message: Say

- Min players before rule enforced: 6

 

However while having 10+ people on the BF3 server, we encountered 2 players with high pings (300 and 400 average). However, I did not see any debug messages in my Procon message window at the bottom of the plugin control panel; nor any messages in server chat console. Have I not setup something correctly?

 

I check my Procon Layer and it is not running in Sandbox mode.

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

Originally Posted by Phil_K*:

 

Hi.

 

You have to know that Procon does an update on ping only every 30 seconds.

This is for not to be too spammy and the ping are only updated in a 30 s interval

at the server side as well.

 

You set the number of ping for average to 7.. (3.5 Min to get them), and 10 to kick.

So I guess the plugin kicks the player about 5 min after his first ping...

 

Greets

Phil

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

Originally Posted by kcuestag*:

 

Hi.

 

You have to know that Procon does an update on ping only every 30 seconds.

This is for not to be too spammy and the ping are only updated in a 30 s interval

at the server side as well.

 

You set the number of ping for average to 7.. (3.5 Min to get them), and 10 to kick.

So I guess the plugin kicks the player about 5 min after his first ping...

 

Greets

Phil

So each "Ping to sample for average" takes 30 seconds? Wow, I had it set at 20 by default, that's 10 minutes!! I guess I'll drop it down to 5.
* Restored post. It could be that the author is no longer active.
Link to comment

Originally Posted by Zaeed*:

 

- Pings to sample for average: 7

- Minimum pings before kicking: 10

Thats your problem. You're telling the plugin to use 7 pings to determine the average, but take 10 before it does anything. It'll never get to 10.

 

I'll add some checking into the next version to combat this.

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

Originally Posted by eagle-rr*:

 

Okay......So I'll change to:

- Pings to sample for average: 5

- Minimum pings before kicking: 3

 

Oddly though...I thought that I would at least some kind of debug information within the window about this. Thanks for the input and I'll try the new parameter values.

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

Originally Posted by kcuestag*:

 

new version is out.. Hopefully it fixes the issue of kicking a player that isn't in the server.

Previous version worked fine to me, and this one does too, thanks Zaeed.
* Restored post. It could be that the author is no longer active.
Link to comment

Originally Posted by Zaeed*:

 

I hope I am not being stupid but since the update I cannot decrease minimum pings and pings to sample.......they will increase ok but will not decrease .....

ah you're right.. My bad..

 

Give me a minute

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

Originally Posted by Yupster*:

 

Hi Zaeed

 

Where does the ping kicker get it's ping data from?

 

I ask as our kicker is kicking players for ping when I have not seen their ping go over the threshold in procon.

 

The average and minimum pings are 7 and the threshold is 110 yet it seems to kick players in way less than 3.5 min.

* 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.