Forum Settings
       
Reply To Thread

Technical IssueFollow

#1 Feb 08 2008 at 3:10 PM Rating: Decent
**
268 posts
I apologize in advance if this is an inappropriate place to put this type of thread but it seems to be a rogue only problem.

So I've recently made a Human Female rogue twink for the 19 bracket. Now im not sure if this issue pertains to human rogues only or rogues in general or if its just me but for some reason when I am chasing an enemy (well in weapon range mind u, literally on top of the enemy some time) I cannot land a hit and big red letters appear on my screen saying "Out of range". HOWEVER when running from a rogue or any melee at similar and sometimes greater distances I am STILL being hit by them.

I never had this problem while playing my warrior and duel wielding, it only seems to be my rogue. Ive searched all over official web site and other forums but cannot find a reason for this to occur unless its latency. I imagine it could be a problem with my computer and rendering the swings or maybe it is latency. Any advice or suggestions would be much appreciated.

PS: Again sorry for posting this here but I've searched all over the web (and the GMs in WoW are next to useless) and cant find an answer. Plus the people here usually know how to solve my problems.
#2 Feb 08 2008 at 3:16 PM Rating: Default
**
459 posts
Sounds like latency to me. I get the same problem sometimes, and i have to stun them to get some nice melee in. Keep a few CPs on your opponent for those KSs when that happens and you should be good.
#3 Feb 08 2008 at 3:21 PM Rating: Good
*
194 posts
Hikuu wrote:
So I've recently made a Human Female rogue twink for the 19 bracket.


Untoucheable wrote:
Keep a few CPs on your opponent for those KSs when that happens and you should be good.


Just pointing this out.

While latency is probably the issue, there's not much a 19 rogue can do about it except try to be up in their bootyholes the entire time.
#4 Feb 08 2008 at 8:42 PM Rating: Decent
**
459 posts
Oh, sorry, didnt notice that. I'm used to having a full array of abilities in my batman belt. Forgot KS came at lvl 30. Sorry bout that.
#5 Feb 08 2008 at 11:52 PM Rating: Decent
**
268 posts
Thank you everyone for your advice, Im just so frustrated that this is happening and to think its a latency issue :( Nothing more annoying in WoW than to be chasing an enemy and not hitting him while the other guy who is chasing him too is BEHIND you and still landing hits.
#6 Feb 09 2008 at 5:40 AM Rating: Decent
*
169 posts
Aaaaaand this is why rogues have a lot of problems in PvP. If this occurs to a warrior/druid, then just get a bit more distance and intercept/charge. On a rogue, you chase your target for the next 5 hours pointlessly until killed.
#7 Feb 09 2008 at 7:51 AM Rating: Decent
*
221 posts
Nocthil wrote:
Aaaaaand this is why rogues have a lot of problems in PvP. If this occurs to a warrior/druid, then just get a bit more distance and intercept/charge. On a rogue, you chase your target for the next 5 hours pointlessly until killed.


actually, ive tried the same thing, both on my rogue (which is "only" 47 atm) and my 70 druid.. it sucks, it really sucks.. even with my talented 15% speed increase (on my druid) I still got the stupid error message. I tried stopping for a second so I got a little farther behind, didnt work, I tried running a little closer, didnt work either, even on top of the target it still wouldnt work, so im quite sure its latency thats the problem..
although, NE druids had a melee-range bug not so long time ago
#8 Feb 09 2008 at 8:11 AM Rating: Decent
***
3,909 posts
I've noticed it too. It's just lag.
#9 Feb 09 2008 at 8:23 AM Rating: Decent
What might help is if you got the Minor Speed Increase enchant to some boots, unless you have that already.. or some swiftness potions, or even a Discombobulator Ray from engineers, it slows them down and turns them into a leper gnome, fun stuff :P
#10 Feb 14 2008 at 1:34 AM Rating: Decent
At that point it's better to just give up, restealth and go
look for someone else to kill. I suppose in theory you could
spec for dirty tricks, stop autoattack while still following
him and then when you drop combat, stealth+sap (which would
have larger range than your other skills). But I doubt
dirty tricks is a good way to spend those two talent points...
especially because I think even that sap would fail.

This problem makes me sooo mad... When enemy runs past me,
and my (talanted) sap fails because they're either out of range or
you are "facing the wrong way". ARGH.

I've actually began levelling a warlock because of this.
With them, even if you happen to be facing the wrong way, you can
still dot the enemy as long as they are in range, so
the margin of error is very large.
#11 Feb 14 2008 at 10:30 AM Rating: Decent
Another thing also....
My wife and I both play WoW and we have our computers set up beside each other, we try and pvp together so we have a slight advantage against others. There have been dozens of times that I will be getting the message out of range and will look over on her screen and see that I am actually much further behind the person I am chasing after than what my screen is showing. This kind of ties in with the loot bug where you kill a mob and the loot bag is grey when your standing on the corpse so you move around the spot where it turns active click on it and it tells you that your out of range!!! lol
BTW click on the corpse and then run off till the target drops from your screen then run back and it will be lootable! Basically there is an error in the graphic vectors between your client and the server as to the real location of said mob/enemy in relation to where you are at.
Reply To Thread

Colors Smileys Quote OriginalQuote Checked Help

 

Recent Visitors: 170 All times are in CST
Anonymous Guests (170)