I'd just like to say, the constant bit of lag is disgustingly old and is making me not want to play. Thank you for your time.

Yes... I wonder what's causing it!

>_<

When are you experiencing the lag?

I've been having a lot of lag in group combat lately, when I haven't dealt with that in the past.

Been getting more than usual myself, just annoying one/two second lag in everything, bleh.

It's constant:

7813h, 4950m, 5808e, 10p, 29400en, 20400w elrx<>- {42.16}
wipe 10534
wipe 62782
envenom 10534 with mantakaya
envenom 62782 with mantakaya
maneuver perform pkd Morgfyre lleg
maneuver perform pkd Morgfyre lleg
Being careful not to poison yourself, you wipe off all the poisons from a hideous hammer of depraved steel.
7813h, 4950m, 5808e, 10p, 29400en, 20400w elrx<>- {57.523999999999}
Being careful not to poison yourself, you wipe off all the poisons from a hideous hammer of depraved steel.
7813h, 4950m, 5808e, 10p, 29400en, 20400w elrx<>- {57.683999999999}
You rub some mantakaya on a hideous hammer of depraved steel.
7813h, 4950m, 5808e, 10p, 29400en, 20400w elrx<>- {58.012000000001}
You rub some mantakaya on a hideous hammer of depraved steel.
7813h, 4950m, 5808e, 10p, 29400en, 20400w elrx<>- {58.026}
You execute the Pkd maneuver: CRUSH MORGFYRE LLEG.
I do not recognize anything called that here.
7813h, 4950m, 5808e, 10p, 29400en, 20400w elrx<>- {58.040999999999}
You execute the Pkd maneuver: CRUSH MORGFYRE LLEG.
You detect nothing here by that name.
7813h, 4950m, 5808e, 10p, 29400en, 20400w elrx<>- {58.056}

Takes going on a second to run through all the commands of a macro? No thanks.

I ran some tests when I heard people complaining about lag but it didn't appear to be on the server side (our side). We can do some more tests but any theories or more information you provide, the better!

It is your side. Denizens are retorting before influence eq recovery fairly regularly.

EDIT: Although it's possible that it's not lag so much as it is a failure of a timing script somewhere.

I get it every now and then in combat, when it counts or if I have a long line of commands like

Outr horehound
eat horehound
sip healing
focus body
kata perform Ilyarin chest gut gut2 heelsmash kill die death
kata terminate
sip quicksilver

EDIT: Made it more.. realistic

I don't know if it's the system running through things, but it happens quite a bit, sometimes even when I have my system off

ping yahoo.com -t

Pinging yahoo.com with 32 bytes of data:
Reply from 209.191.93.53: bytes=32 time=56ms TTL=56
Reply from 209.191.93.53: bytes=32 time=50ms TTL=56
Reply from 209.191.93.53: bytes=32 time=53ms TTL=56
Reply from 209.191.93.53: bytes=32 time=55ms TTL=56
Reply from 209.191.93.53: bytes=32 time=46ms TTL=56
Reply from 209.191.93.53: bytes=32 time=48ms TTL=56
Reply from 209.191.93.53: bytes=32 time=47ms TTL=56
Reply from 209.191.93.53: bytes=32 time=47ms TTL=56
Reply from 209.191.93.53: bytes=32 time=47ms TTL=56
Reply from 209.191.93.53: bytes=32 time=50ms TTL=56
Reply from 209.191.93.53: bytes=32 time=61ms TTL=56
Reply from 209.191.93.53: bytes=32 time=49ms TTL=56
Reply from 209.191.93.53: bytes=32 time=48ms TTL=56
Reply from 209.191.93.53: bytes=32 time=48ms TTL=56
Reply from 209.191.93.53: bytes=32 time=46ms TTL=56
Reply from 209.191.93.53: bytes=32 time=49ms TTL=56
Reply from 209.191.93.53: bytes=32 time=50ms TTL=56
Reply from 209.191.93.53: bytes=32 time=47ms TTL=56
Reply from 209.191.93.53: bytes=32 time=53ms TTL=56
Reply from 209.191.93.53: bytes=32 time=65ms TTL=56
Reply from 209.191.93.53: bytes=32 time=46ms TTL=56
Reply from 209.191.93.53: bytes=32 time=48ms TTL=56
Reply from 209.191.93.53: bytes=32 time=49ms TTL=56

Ping statistics for 209.191.93.53:
Packets: Sent = 23, Received = 23, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 46ms, Maximum = 65ms, Average = 50ms
Control-C
^C
ping lusternia.com -t

Pinging lusternia.com with 32 bytes of data:
Reply from 64.127.116.166: bytes=32 time=126ms TTL=47
Reply from 64.127.116.166: bytes=32 time=124ms TTL=47
Reply from 64.127.116.166: bytes=32 time=124ms TTL=47
Reply from 64.127.116.166: bytes=32 time=123ms TTL=47
Reply from 64.127.116.166: bytes=32 time=132ms TTL=47
Reply from 64.127.116.166: bytes=32 time=122ms TTL=47
Reply from 64.127.116.166: bytes=32 time=122ms TTL=47
Reply from 64.127.116.166: bytes=32 time=122ms TTL=47
Reply from 64.127.116.166: bytes=32 time=122ms TTL=47
Reply from 64.127.116.166: bytes=32 time=122ms TTL=47
Reply from 64.127.116.166: bytes=32 time=122ms TTL=47
Reply from 64.127.116.166: bytes=32 time=122ms TTL=47
Reply from 64.127.116.166: bytes=32 time=88ms TTL=47
Reply from 64.127.116.166: bytes=32 time=89ms TTL=47
Reply from 64.127.116.166: bytes=32 time=89ms TTL=47
Reply from 64.127.116.166: bytes=32 time=126ms TTL=47
Reply from 64.127.116.166: bytes=32 time=91ms TTL=47
Reply from 64.127.116.166: bytes=32 time=88ms TTL=47
Reply from 64.127.116.166: bytes=32 time=123ms TTL=47
Reply from 64.127.116.166: bytes=32 time=90ms TTL=47
Reply from 64.127.116.166: bytes=32 time=128ms TTL=47
Reply from 64.127.116.166: bytes=32 time=90ms TTL=47
Reply from 64.127.116.166: bytes=32 time=124ms TTL=47
Reply from 64.127.116.166: bytes=32 time=123ms TTL=47
Reply from 64.127.116.166: bytes=32 time=128ms TTL=47
Reply from 64.127.116.166: bytes=32 time=132ms TTL=47
Reply from 64.127.116.166: bytes=32 time=122ms TTL=47
Reply from 64.127.116.166: bytes=32 time=121ms TTL=47
Reply from 64.127.116.166: bytes=32 time=132ms TTL=47
Reply from 64.127.116.166: bytes=32 time=121ms TTL=47
Reply from 64.127.116.166: bytes=32 time=123ms TTL=47
Reply from 64.127.116.166: bytes=32 time=123ms TTL=47
Reply from 64.127.116.166: bytes=32 time=123ms TTL=47
Reply from 64.127.116.166: bytes=32 time=123ms TTL=47

Ping statistics for 64.127.116.166:
Packets: Sent = 34, Received = 34, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 88ms, Maximum = 132ms, Average = 117ms
Control-C
^C

Just noting the nice fluctuation in time between pings on the lusternia server as opposed to the yahoo server.

A 120 ping isn't bad (and I'm pinging at closer to 85ms myself). It really seems to be software or server load rather than a network issue.

I'm personally pinging 85 or so, which is normal for me. Are there any storms near where you live, Vath?

I'd assume there is a constant, swirling lightning cloud above MC Hammer's house.

MC Hammer's house? I thought the swirling lightning clouds that Xenthos lives under were above some big tower with a flaming red eye at the top...

While playing, I haven't really noticed any consistent lag, but rather periodic 3-5 second lag spikes (server side - everything stops, including denizen actions, etc). I dunno if this is maybe the servers making backups or something, but it's terribly annoying.

No storms and I play on a mildly high speed connection.

Connection speed is..
12.09 Mb/s down
2.53 Mb/s up

On the east coast, maybe that's why?


Pinging lusternia.com with 32 bytes of d
Reply from 64.127.116.166: bytes=32 time=122ms TTL=47
Reply from 64.127.116.166: bytes=32 time=100ms TTL=47
Reply from 64.127.116.166: bytes=32 time=100ms TTL=47
Reply from 64.127.116.166: bytes=32 time=109ms TTL=47
Reply from 64.127.116.166: bytes=32 time=116ms TTL=47
Reply from 64.127.116.166: bytes=32 time=146ms TTL=47
Reply from 64.127.116.166: bytes=32 time=110ms TTL=47
Reply from 64.127.116.166: bytes=32 time=101ms TTL=47
Reply from 64.127.116.166: bytes=32 time=107ms TTL=47
Reply from 64.127.116.166: bytes=32 time=100ms TTL=47
Reply from 64.127.116.166: bytes=32 time=118ms TTL=47
Reply from 64.127.116.166: bytes=32 time=106ms TTL=47

Ping statistics for 64.127.116.166:
Packets: Sent = 12, Received = 12, Lost = 0 (0% loss)
Approximate round trip times in milli-seconds:
Minimum = 100ms, Maximum = 146ms, Average = 111ms
Control-C
^C
C:\\Users\\Drarelle>ping yahoo.com -t

Pinging yahoo.com with 32 bytes of data:
Reply from 209.191.93.53: bytes=32 time=58ms TTL=53
Reply from 209.191.93.53: bytes=32 time=47ms TTL=53
Reply from 209.191.93.53: bytes=32 time=73ms TTL=53
Reply from 209.191.93.53: bytes=32 time=54ms TTL=53
Reply from 209.191.93.53: bytes=32 time=48ms TTL=53
Reply from 209.191.93.53: bytes=32 time=57ms TTL=53
Reply from 209.191.93.53: bytes=32 time=58ms TTL=53
Reply from 209.191.93.53: bytes=32 time=57ms TTL=53

Ping statistics for 209.191.93.53:
Packets: Sent = 8, Received = 8, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 47ms, Maximum = 73ms, Average = 56ms
Control-C

Vathael has been known as MC Hammer for a few days now. Get with the times.

@ruiku: Hell if I know, I just know it's old!