When hunting with my Phantom Ranger I target my mobs no problem.. but after i kill the mob I target the next mob and press the shortcut F(key) to attack the next mob. The problem happens right then.. somehow my target switchs back to the dead mob. I have talked to a few people that have the same exact problem. Why is this.. how can i fix it .. why should i have to fix it ... why hasnt it been fixed by now???? Its been going on forever.. while im at it... im tired of targeting mob to have myself try to walk right behind it... could expand the area just a hair or two would make this a tad ezier.. but thats not anywhere near as agrovating as the first part cause if you get the pointer dead on mob it works properly.
TY for reading my vent
I cant slow down the next mob is agroed because i just killed his friend right next to him or the second mob is slapping my healer in robes....and im really not targeting that fast. if the first mob hasnt disapeared it goes back to him. but ty for you reply. oh yeah one other thing if you can manage to press on the mob twice with pointer you atk him no problem.. just very tough to do sometimes when you healers threatened and mob is moving after them.
the targeting system has done that since the beginning and i dont think there is a way around it other than slowing down when you hit attack. very annoying thing you have to live with.
Suggestion:
Try using a bow on your PR. That'll not only avoid the melee kite problem you describe, but also let you make use of bow skills.
Also you can target the next mob while you're still killing another. That helps the target switch bug. I agree that it's the dumbest lamest bug (even WoW doesn't have that bug), but after 4+ years of lineage2, I just don't think they have the talent in all of f%^& Korea to fix it.
I have the same problem. I play a BD and during fast xp times, I get into a groove where I have mob almost dead, click next target and attack it just as the last one falls. Sometimes I get too fast and the target reverts back to the one that just died. The only way around this is to work on your timing to pause just enough to allow the second target to acquire. It only takes a split second but it is just a timing issue. Good hunting to you.
After CT1 i get "Cannot see target" message constantly with long range spels like mana burn on prophet or prominance on sorcerer.
When hunting with wollf u cant target close range mob ( mob actualy attacking me) but have to run away a litle to be able to do so.
Next target doesnt work for PP too if u hunt near raid boss group.
While this does work, the range on that macro is fairly poor thus useless for all those ranged attackers (*~*). The targetting system has always been bad, and i agree it has got worse since the update. The only way round it, that i found, was to target/highlight my next mob a few second before the current mob i am attacking, dies.
After CT1 i get "Cannot see target" message constantly with long range spels like mana burn on prophet or prominance on sorcerer.
I did notice this a couple of times with my SH whilst using Hurricane, not sure what the precise cause of this is but to me seems highly similar to the "The distance is too far and so the casting has been stopped." rubbish that seems to happen with a lot of skills.
These problems could be bugs but they could also be down to the game engine, which is definitely starting to show its age now.
While this does work, the range on that macro is fairly poor thus useless for all those ranged attackers (*~*). The targetting system has always been bad, and i agree it has got worse since the update. The only way round it, that i found, was to target/highlight my next mob a few second before the current mob i am attacking, dies.
After CT1 i get "Cannot see target" message constantly with long range spels like mana burn on prophet or prominance on sorcerer.
I did notice this a couple of times with my SH whilst using Hurricane, not sure what the precise cause of this is but to me seems highly similar to the "The distance is too far and so the casting has been stopped." rubbish that seems to happen with a lot of skills.
These problems could be bugs but they could also be down to the game engine, which is definitely starting to show its age now.
~ ~ ~ ~ ~
Eggy ^_^
they added "The distance is too far and so the casting has been stopped" back in like c1 I think and I really hate that and don't see why it was needed at all. really sucks when using macros. they need to just take it back out. really bad on my BH
/nexttarget
/attack
/delay 1
/spoil (right here if I'm not close enough spoil the marco stops and me and my pet just stands there)
/petattack
/attack
/attack
I even with delay 3 it does that some times and if I make it any longer just means more time I have wait before my pet helps kill it.
The range of "target next" command is stupidly increased. Now I press "target next" and very often instead of targeting the next monster I am fighting the target go to the other end of the room/spot and my toon leaves the good postion or even worse - draws anothe mob in the fight!