Print

Please login or register.
1 Hour 1 Day 1 Week 1 Month Forever
Login with username, password and session length

[Happylisk]

Let's say you want to blow up the recycler in the starting zone to get a storage unit.  You press f and fire.  Mr. Recycler doesn't die, but instead moves away. You press "f" again.  Your cursor will be placed on where he was, not where he is now, forcing you to move the cursor before firing again.  The default should be last targeted robot, not last targeted square. 

[Kyzrati]

What you describe here is already default behavior--'f' will always target the robot and not a square.

However, auto-targeting only happens in keyboard mode, so I'm assuming you're using the mouse? Mouse mode doesn't auto-target because it would complicate the behavior somewhat (different targeting behavior depending on direct clicking vs. pressing 'f'), and if the auto-target robot happens to be in an unexpected place because you weren't firing for a while, it can force you to pick up your mouse and move it to compensate for the distance.

Currently in mouse mode when you press 'f' it shouldn't even move the cursor at all (I don't see it doing that), just activate firing mode wherever the cursor is currently (which if you just fired at a robot, will be the last position at which you did so, hence what you're seeing).

That said, I believe the UI should probably be changed to distinguish an 'f' used to activate the firing mode, even while using the mouse, and allow it to target based on the preference set in the options (only when the "Auto Cursor" option is active).

[Happylisk]

Yeah I'm using the mouse which explains this.  I'll give a keyboard run a try and see how it feels. 

[Kyzrati]

Even players who don't start in keyboard mode seem to be tending to migrate towards hybrid and then even full keyboard play. It's simply more efficient. Either way, I'll most likely make the auto-targeting work for mouse in the case of 'f', as long as there isn't some unforeseen obstacle to doing that.

I also plan to add a new "part swap mode" for keyboard users, which will further streamline that UI functionality when you have a lot of swapping to do. (Unrelated to this issue, but just mentioning since you'll be testing keyboard mode and may feel that swapping requires holding too many keys--Shift+Ctrl.)

[Reiver]

I dunno, I can't see myself giving up the right-click-to-view or inventory juggling with the mouse any time soon, even if I'm using keyboard commands to [a]quire vs [g]et, etc.

Then again, that's mostly all I use the mouse for to start with, handy as it is.

[Kyzrati]

I was just investigating this for Alpha 3, and discovered the original cause of OP's issue: The code was already in place to correctly aim at the previous target in mouse mode, but it started ignoring that state after any point at which you use the mouse to actually fire. (In Alpha 2c it works normally only if you're also using 'f' to also fire.)

Fixed.