Visik
Well-known member
When changes made to them aren't saved?
(Note: The actual Key Mapping labels are: "Select Next Combat Target" and "Select Previous Combat Target.")
Rangers with Improved Precise Shot and Casters with line-type spells both want to target the furthest enemy, in order to control better the direction the projectile or spell goes and maximize the number of intervening enemies they hit. Simply remapping <Tab> to "Previous Enemy" instead of "Next Enemy" is ideal for this purpose. In fact, "Next Enemy" is all but worthless, comparatively. Only time I can recall really needing that was as a ranged toon with PS but not yet IPS, to kill the closest mobs first.
If I go into Key Mapping, and clear both the entries for Next Target and Previous Target, then switch them (<Tab> for Previous Target; <Ctrl><Tab> for Next Target), it retains that mapping through logging out and back in, but it discards it on Exit. If these are meant to be unchangeable, I can see putting them in Key Mapping (as a lookup function for someone who doesn't know what keys have what effects), but they should be locked and unchangeable.. or a warning should be generated. If the intent isn't to make them unchangeable, it'd be nice if the changes would stick.
I've had a fair amount of frustration over this, recently.
(Note: The actual Key Mapping labels are: "Select Next Combat Target" and "Select Previous Combat Target.")
Rangers with Improved Precise Shot and Casters with line-type spells both want to target the furthest enemy, in order to control better the direction the projectile or spell goes and maximize the number of intervening enemies they hit. Simply remapping <Tab> to "Previous Enemy" instead of "Next Enemy" is ideal for this purpose. In fact, "Next Enemy" is all but worthless, comparatively. Only time I can recall really needing that was as a ranged toon with PS but not yet IPS, to kill the closest mobs first.
If I go into Key Mapping, and clear both the entries for Next Target and Previous Target, then switch them (<Tab> for Previous Target; <Ctrl><Tab> for Next Target), it retains that mapping through logging out and back in, but it discards it on Exit. If these are meant to be unchangeable, I can see putting them in Key Mapping (as a lookup function for someone who doesn't know what keys have what effects), but they should be locked and unchangeable.. or a warning should be generated. If the intent isn't to make them unchangeable, it'd be nice if the changes would stick.
I've had a fair amount of frustration over this, recently.
Last edited:
Upvote
0