Monday, 11th June 2018, 07:32 by duvessa
this would save me negative time because i wouldn't expect it to target that spot by default, so i'd move the targeter based on where i would expect it to start, and then end up with an invalid target and have to go back
human visual reaction time is around 250ms, so for me (and I suspect a lot of other players) a targeter that consistently starts in a "bad" place is still faster than a targeter that starts somewhere I don't expect it to.
The change to the LRD targeter made the spell take roughly 10 times longer to use for me, and that's not an exaggeration; it used to use the default targeter so it'd start on a monster and I knew which monster it'd start on, so most of the time it was a matter of moving the cursor one step to the wall I want to break. That one keypress takes practically no time.
Then it got a "better" targeter that made it start on a wall near a monster, and I found that I couldn't consistently predict where that targeter would start, so I had to look at the screen every time to figure out where it started, then move it to the wall I actually wanted to break. This was easily more than 10 times slower, especially if there's lag.
The simple_targeting option was an improvement, but it's still much worse than the old default targeter: it makes the LRD targeter always start on your character. Now, this way I know where it starts, but I also usually have to move it 5+ tiles (LRD has LOS+1 range and you generally want to take advantage of that range). And typing zlb⏎ isn't much slower than zl⏎, but man, zljbjjj⏎ sure is. Still faster than having to read the screen an extra time though.