Target System Adjustments 1.17a -- Not Good

[darkstarpoet1]

I'm guessing you guys use keyboard? This change just made controller targeting NEAR perfect! I now use target mode A while in 'enemy target mode'. Since up and down is locked to party members its much better than using tmode B and selecting party members out of order or accidently changing targeting modes^^, along with the fact in Tmode A and using enemy I can now just hit my 'confirm' button and it targets the nearest npc/pc Rarely use macro anymore... Never accidently changed targeting modes cause you DON'T have to hold auto run to you know... auto run...

If you wanna auto run just tap it and do your other stuff xD The new controls are holding auto run button while pushing another button... why would u hold the auto run button and push other buttons if your intention was just to auto run and do other stuff? I don't get it... easy solution... DON'T HOLD AUTO RUN BUTTON if you don't wanna change targeting modes LoL Simple solution to a simple problem imo ... anyways *flame-on*, I'm guessing you won't agree xD

actually no i use a controller and having the same issue. it needs to go back to the way it was pre patch.

was out mining and didn't notice it changed on me so got attacked by a miteling on my 29 miner. i had to change to my thm just to find out that it changed itself to friendly only. the arrow buttons do not change back to all so had to put my weapon back up, grab my keyboard, type in targetmode b, then targermode a, and finally pull my weapon out and attack the mob. thank goodness it was a weak mob beating on me or i would been dead due to this stupidity. a bug report has been reported on this junk.

[Sonic_the_Hedgehog]

actually no i use a controller and having the same issue. it needs to go back to the way it was pre patch.

was out mining and didn't notice it changed on me so got attacked by a miteling on my 29 miner. i had to change to my thm just to find out that it changed itself to friendly only. the arrow buttons do not change back to all so had to put my weapon back up, grab my keyboard, type in targetmode b, then targermode a, and finally pull my weapon out and attack the mob. thank goodness it was a weak mob beating on me or i would been dead due to this stupidity. a bug report has been reported on this junk.

That's because the arrow buttons DON'T change which mode you're in. Hold down your auto-run button then press your emote button and it should be set back to ALL. Come on people read the patch notes.

[Misha]

That's because the arrow buttons DON'T change which mode you're in. Hold down your auto-run button then press your emote button and it should be set back to ALL. Come on people read the patch notes.

My thoughts exactly... and why people need to HOLD DOWN auto run button to auto run when it requires just a tap is beyond me... *facepalm* They damn well near perfect the controller targeting and people bytching like mad... Tmode B was untouched and all Tmode A added was ability to access other targeting types with the added ability to select pt members and close npcs while on enemy mode lmao...

I don't even know why I'm responding to this nonsense of a thread still, guess it just gives me a good laugh at how people can never read the patch notes properly and get messed up on the stupidest things xD

[darkstarpoet1]

My thoughts exactly... and why people need to HOLD DOWN auto run button to auto run when it requires just a tap is beyond me... *facepalm* They damn well near perfect the controller targeting and people bytching like mad... Tmode B was untouched and all Tmode A added was ability to access other targeting types with the added ability to select pt members and close npcs while on enemy mode lmao...

I don't even know why I'm responding to this nonsense of a thread still, guess it just gives me a good laugh at how people can never read the patch notes properly and get messed up on the stupidest things xD

who said anything about i was holding down autorun to lock it? i was mining then got attacked while mining. my autorun was not being used when it locked. what is so hard to understand it is glitchy and does it on its own? anything that locks your bar for no reason is a waste hence why a bug report was sent on it.