Wow, this thread hit conjecture and post-signing shithouse central in a day.
|
Yes, what you are doing is presenting to the game client a US based IP address. This is the sole reason you are seeing a lower in game ping on the game metre. The game client thinks your in the US. All you are doing is "tricking" the in game metre to present a lower number.*
|
I don't understand how you can even expect anyone to buy this. Why would a piece of software arbitrarily decide to display a number based on an IP? What?
That aside, as a druid, the changes in 2.3 have been amazing, especially client-side cancelforms and such. Haven't had the chance to PVP yet, but I'd assume it's going to be a lot easier without having a half second delay between certain sequences of events.
I think from a PVE standpoint, the combat log in this screenshot sums out how happy I am in my pants about the changes.
http://img132.imageshack.us/img132/1...7173320ft0.jpg
(Yes, I realize the combat log on client side is screwed in terms of event ordering, but the screenshot is still kinda cute :P)
((Yes, I also realize that even with a 50ms ping this wasn't possible pre-2.3 with a single keystroke. The difference here was it *was* an option with a tiny risk at 50ms, but a death sentence at 500))
Edit: a couple of people were asking me on IRC PM what the screenshot implied. It was an unshift-pot-healthstone-shift macro, our first real panic button aside from bearvasion trinkets. The events were so close together that it actually managed to make the combat log display the events in the wrong order.