traceroute to USWest.battle.net (63.241.83.13), 30 hops max, 40 byte packets
1 192.168.0.1 (192.168.0.1) 0.481 ms 0.584 ms 0.678 ms
2 * * *
3 GE-1-5-ur01.tacoma.wa.seattle.comcast.net (68.86.99.141) 22.740 ms * *
4 te-9-3-ur02.tacoma.wa.seattle.comcast.net (68.86.96.22) 22.919 ms * *
5 * * *
6 12.86.1.13 (12.86.1.13) 25.951 ms 12.822 ms 11.745 ms
7 12.127.6.185 (12.127.6.185) 42.056 ms 50.432 ms 50.595 ms
8 tbr2.sffca.ip.att.net (12.122.12.113) 50.802 ms 50.968 ms 51.413 ms
9 gar4.sffca.ip.att.net (12.123.13.178) 163.131 ms 163.310 ms 163.507 ms
10 idf22-gsr12-1-pos-6-0.rwc1.attens.net (12.122.255.222) 49.674 ms 49.890 ms 50.097 ms
11 mdf2-bi8k-2-eth-2-1.rwc1.attens.net (216.148.209.14) 58.967 ms 59.191 ms 59.354 ms
12 * * *
13 * * *
14 * * *
15 * * *
16 * * *
17 * * *
18 * * *
19 * * *
20 * * *
21 * * *
22 * * *
23 * * *
24 * * *
25 * * *
26 * * *
27 * * *
28 * * *
29 * * *
30 * * *

---

Q u o t e:
traceroute to USWest.battle.net (63.241.83.13), 30 hops max, 40 byte packets

---

So if I'm reading this right you've got about 120 ping in game?

Thank you for doing your trace bonkers.

---

Q u o t e:


run a traceroute for us please?

---

Are those even going to help when there is no other sign nor symptom of lag, the latency looks good, and the traces look good? I don't think this has anything at all to do with lag, other than lag exasperating or lessening the impact of certain effects, depending on situation/class.

---

Q u o t e:


Because the game we paid for and played all these years changed to near unplayable. If you've delt with this all along than you don't have anything to compare it to. Its like the saying goes... a man can not know sorrow until he has felt happyness.

Also, that isn't ironic.

---

I pay for the same game, and just because I haven't played on an American ping doesn't mean I don't know how it would be, it's like every other online game I have played. I shouldn't be standing right behind someone CLEARLY in melee range, but still, I cannot hamstring or shiv. Believe me, it's very ironic.

---

Q u o t e:


So if I'm reading this right you've got about 120 ping in game?

Thank you for doing your trace bonkers.

---

ruffly yeah, but it goes higher

yw

I should also add im using Ubuntu 7.10 gutsy

As for why it might help to run a trace route.

Its hard fact on what your ping roughly is, this isn't "feelings" or "experiences" rather it shows what kind of ranges people are in, ping wise, that are having issues.

The devs can take this to their focused testing setting and emulate the ping difference and work on the bug more easily, and fix it faster.

(your ping is roughly going to be double your biggest ping number on the trace, since the server has to reply along the same lines.)

Btw >.>

http://en.wikipedia.org/wiki/Irony

Not very ironic in the dictionary sense. Just funny at my expense really... what would be closer to irony is the fact that you'd mock someone for having the same problem that you do =D

I don't know why you guys have problems. It's working fine for me. I've been dominating in the BGs because of these new fixes and topping damage now as well.

---

Q u o t e:


http://en.wikipedia.org/wiki/Irony

Not very ironic in the dictionary sense. Just funny at my expense really... what would be closer to irony is the fact that you'd mock someone for having the same problem that you do =D

---

Eh, Yeah, I had it right. Look at it from my Point of View, me, and a lot of other oceanic players have been playing like this for 3 years now, we have qq'd and whinged about it to no avail. Now all of a sudden US players are getting, what sounds like to me, the EXACT same issues. ie: it's ironic. But, I don't really care to keep arguing with you over some pedantic wording in my text. Back to the issue.

Tracing route to USEAST.battle.net [63.240.202.120]

over a maximum of 30 hops:



1 7 ms 9 ms 8 ms 73.63.204.1

2 8 ms 9 ms 8 ms GE-2-2-ur01.S1marietta.ga.atlanta.comcast.net [68.86.110.85]

3 9 ms 8 ms 15 ms te-9-4-ur01.s5marietta.ga.atlanta.comcast.net [68.86.106.201]

4 9 ms 18 ms 8 ms te-9-3-ur01.b3marietta.ga.atlanta.comcast.net [68.86.106.197]

5 7 ms 8 ms 8 ms te-9-4-ur02.b0atlanta.ga.atlanta.comcast.net [68.86.106.125]

6 10 ms 8 ms 8 ms te-9-4-ur01.b0atlanta.ga.atlanta.comcast.net [68.86.106.13]

7 10 ms 9 ms 8 ms te-9-2-ar01.b0atlanta.ga.atlanta.comcast.net [68.86.106.9]

8 10 ms 9 ms 11 ms 12.116.116.13

9 30 ms 30 ms 29 ms tbr2.attga.ip.att.net [12.122.85.158]

10 30 ms 32 ms 44 ms cr1.attga.ip.att.net [12.122.17.89]

11 29 ms 28 ms 28 ms cr2.wswdc.ip.att.net [12.122.1.174]

12 29 ms 28 ms 29 ms tbr1.wswdc.ip.att.net [12.122.16.62]

13 28 ms 29 ms 30 ms gar5.wswdc.ip.att.net [12.123.8.25]

14 31 ms 39 ms 33 ms 12.122.255.46

15 30 ms 30 ms 30 ms mdf001c7613r0004-gig-10-1.wdc1.attens.net [63.240.193.18]

16 * * * Request timed out.

17 * * * Request timed out.


Eh; admittedly I'm not impressed with the ISP... but its not slow generally, and I don't see major things here - probably why it doesn't really harm any of my casters or lag anything. Just... GCDs that screw up.
It was between 120-130 ms latency measured in game today. I almost never see above 150, and sometimes drop down to ~90. Those numbers shouldn't be a problem.

---

Q u o t e:
Eh, Yeah, I had it right. Look at it from my Point of View, me, and a lot of other oceanic players have been playing like this for 3 years now, we have qq'd and whinged about it to no avail. Now all of a sudden US players are getting, what sounds like to me, the EXACT same issues. ie: it's ironic. But, I don't really care to keep arguing with you over some pedantic wording in my text. Back to the issue.

---

No, its really not the same issue. We never wanted you to have lag - but it was an understandable effect of location.
Being locked down from executing any abilities while still pathing fine, updating fine, not lagging, etc isn't at all the same. Stop != Slow

I understand not everyone has the problem - but there's even aussies in the thread saying this is much worse. It's a completely different sort of stuck. If you'd been stuck this way, I doubt any aussies would be playing anymore - it isn't slow or hope you get an ability off. It's can't. Period. Have fun dying.
It's not looking like we're behind someone and not being able to use our ability - it's trying to and that not only NOT working, but also preventing us from even trying anything else at all for a few seconds.

a pleasant fun time I experienced today was...as I cloak of shadowed on my rogue, it went off fine, after CoS was up, I got layered with lock dots, not one or two as can happen since it's not 100% resistance, but the entire spectrum of instant casts. My ping was a little high at the time due to downloading. But it seemed that between my using CoS, and server recognizing it's use, I got hit with everything, but since I technically used it before the casts, the cleansing effect had past already. And since he had used his dots before CoS was up, by the time I registered them, my cleanse was over, but the resist wasn't up when he initially cast em...so they all landed. I died miserably in the face. I was dissatisfied. But it's not really the end of the world. Over time they will correct bugs like this, and we will adapt to learn to use it.

Another fun time, I cheapshotted someone, and the stun didn't take effect till they were far enough away from me for me to deadly throw them, so the stun was over before I got to them. I caught up, and used Kidney Shot, we both moved a few more steps before I was pally stunned simultaneously as he was stunned by my Kidney shot. Numerous Rogue duels since have resulted in similar outcomes. it seems like there's a window of action around stuns now.

That is the issue I feel needs work.

But my over all sense of the issue when patch launched, I felt like everything was extremely laggy besides 40fp and a 10ms latency. Felt like everything was happening out of sync with my button presses. Was weird. In the end it won't take long to adapt, and attacking moving targets will depend a lot more on the anticipation of a targets movements.

---

Q u o t e:


No, its really not the same issue. We never wanted you to have lag - but it was an understandable effect of location.
Being locked down from executing any abilities while still pathing fine, updating fine, not lagging, etc isn't at all the same. Stop != Slow

I understand not everyone has the problem - but there's even aussies in the thread saying this is much worse. It's a completely different sort of stuck. If you'd been stuck this way, I doubt any aussies would be playing anymore - it isn't slow or hope you get an ability off. It's can't. Period. Have fun dying.
It's not looking like we're behind someone and not being able to use our ability - it's trying to and that not only NOT working, but also preventing us from even trying anything else at all for a few seconds.

---

I realize exactly what it is, I don't think you realize what aussie lag is. It's a combination of, a half a second before any ability goes off, and for melee it's also trying to guess where your opponent is, you have to play like they are a second ahead of where they are on your screen. It has always been like that, as a rogue or warrior it's often been the case that i've been standing right behind an enemy and no matter what I do my slow won't go off, so I have to either blow sprint to get inside the enemy, or back off and waste intercept. It has always been like this for us.

---

Q u o t e:


Feedback on changes posted in a constructive manner (like this) are a great way for us to see how it's affecting players. While it's understandable that people have feedback to share on this already, I'd like to ask that people give it a little time too and continue relaying their experiences to us so that we can assess any further changes that we need to consider making. We aren't planning on making any quick changes to things that have been implemented, but we are also watching carefully to see what effect it is having on the game and players overall.

I'd like to urge people that wish to give feedback to please refrain from typing /signed . It doesn't add your own voice to the feedback and only ends up in a thread that is less productive than it could be. Thanks!

---

All I can say for feeback is I dont like this new system on how your computer talks to the game server. It just makes me feel as if I have over 700 MS. Playing my rogue in pvp is frustrating to say the least. Tanking isnt as bad, but it is harder to react when im put into the position of having to chase after my mobs when I cant even land a taunt because "Its too far away"

I really dont like this new system you have.

Other then that, this patch would be pretty nice if it wasn't for this new system. And didnt you have alot of players on the test forums asking that this not come with the patch?

I didn't even realize this change had even occurred. My usual PvP was seemingly difficult, but I thought it was latency issues.

I lost to hunters and ice mages that I could easily defeat before the patch. I assumed losing to a hunter was due to the dead zone change, and against the mage, I had just assumed my latency was acting up.

Without a snare, and a cat form range bug, with this new GCD change, effective feral PvP against moving targets is impossible.

I'm very disappointed with the changes.

I say again, please give us back the old global cooldown system. This one is clunky and just plain bad.