lag identifier

[MicroEDGE]

i'm looking for an addon that tells you whether or not (if you get it) lag is coming from your client or it's coming from the server.

can't find a download anywhere

help

[Ad Bot]

[FelipeO_O_]

There isn't such addon and probably wont exist.

You may identify it by yourself.

OPen the command line prompt and type in: ping -t 'google.com'

if the reported ping is over 300. It is comming from ya, otherwise from the server

[phflack]

if you lag on all servers, it's probably you
if you lag on just the one server, and other players are too, then it's probably the server

if it's due to your client, you would also be lagging on other games

OPen the command line prompt and type in: ping -t 'google.com'

just
ping www.google.com
is fine

[MicroEDGE]

ignoring felipe cause he's stupid

if you lag on all servers, it's probably you
if you lag on just the one server, and other players are too, then it's probably the server

if it's due to your client, you would also be lagging on other games
just
ping www.google.com
is fine

no


an addon DOES exist i just can't find it

[FelipeO_O_]

Good luck finding it maybe it does exist in your imagination.

[Kyuande]

There isn't such addon and probably wont exist.

You may identify it by yourself.

OPen the command line prompt and type in: ping -t 'google.com'

if the reported ping is over 300. It is comming from ya, otherwise from the server

Good luck finding it maybe it does exist in your imagination.

No you just don't know how to use a search button. Please have some consideration before saying stuff, seriously.

Lag Indicator (beta) - https://forum.blockland.us/index.php?topic=271967.0

[FelipeO_O_]

I won't have consideration with fool ignorant people like the author of this thread.

why don't you teach him instead how to use the search button before making a thread?

[TableSalt]

I won't have consideration with fool ignorant people like the author of this thread.

why don't you teach him instead how to use the search button before making a thread?

are you okay

[phflack]

are you okay

To be fair, the other two are being fairly rude

[Kyuande]

To be fair, the other two are being fairly rude

I am trying to avoid being rude here but felipe is constantly doing this in a lot of threads, posting without having much thought into it - sometimes being rude as well. Doesnt mean I should be either but I want to make a point here.

I won't have consideration with fool ignorant people like the author of this thread.

why don't you teach him instead how to use the search button before making a thread?

I was planning to add how to search properly so that isnt a big deal, its the fact that you are shunning him saying it doesnt exist even though it took me 5 seconds find it. You could of found it too so dont just blame OP.

[MicroEDGE]

No you just don't know how to use a search button. Please have some consideration before saying stuff, seriously.

Lag Indicator (beta) - https://forum.blockland.us/index.php?topic=271967.0

THANK YOU

[Not an alt]

this stuff classed server lag as client lag
not very useful at all

[Kyuande]

Note that it was in beta and never was finished

[Shift Kitty]

It's nowhere near a perfect solution.
All it's doing is checking the ping every second. If the ping doesn't change (which could be due to an enormous amount of factors) it classifies it as client lag. If the ping does change, it classifies it as server lag.
I imagine the thought behind this is that:
If your client is able to update the interface, then it's clearly not a freezing issue, it's a network issue.
If your client is able to get different ping results, then that means the connection is still active, but for whatever reason (server possibly busy), packets aren't being sent.
If your client always has the same ping result, then that may be an indication that there's an issue connecting to the server. Which means your client cannot connect to it.
But that's just a maybe. Maybe the ping was actually just the same because the connection was stable for that second. Maybe the server shut down, lost it's connection, etc. That's not necessarily the client's 'fault', but it is still the client being unable to connect.