Free Allegiance Forums

Anguirel wrote:QUOTE (Anguirel @ Dec 21 2006, 03:36 AM) Perhaps create a new button to map which targets a null-object, preventing target acquisition.

Uuuuh, maybe I'm missing something here... but can't we just fix the 'Target Nothing' button to... y'know... do what it says? (And add an additional one for 'target nearest hostile' if you want.)


-- Cort

Cortex wrote:QUOTE (Cortex @ Dec 27 2006, 12:07 PM) Uuuuh, maybe I'm missing something here... but can't we just fix the 'Target Nothing' button to... y'know... do what it says? (And add an additional one for 'target nearest hostile' if you want.)
-- Cort

Many people use "Target Nothing" to automatically acquire the next hostile to be spotted by sensors, and want and expect it to work that way. We shouldn't remove current functionality and the existing binding needs to remain what it is so when it gets updated in code no one needs to alter their bindings unless they want the new type. So yes, you're missing something. /wink.gif" style="vertical-align:middle" emoid=";)" border="0" alt="wink.gif" />

So we add a new binding, and possibly alter the name of the old one to be "Target Nothing / Acquire Nearest Hostile" vs. "Target Nothing Always". If adding bindings is hard (I have no idea how bad it would be to add more in), then altering "Target Self" to function in a fashion similar to how one might expect "Target Nothing" to work seems a good solution.

There's already a target nearest hostile that I assume does what people expect Target Nothing to do.

Aoreias wrote:QUOTE (Aoreias @ Dec 28 2006, 07:48 AM) There's already a target nearest hostile that I assume does what people expect Target Nothing to do.

Not precisely... Target Nearest Hostile, when pressed repeatedly, will move through all hostile targets in the sector eventually. Target Nothing will do that, then nearly instantly switch to the nearest hostile if there is one in the sector every time. The implementation and resultant effect are different, which is why many people map Target Nothing rather than Target Nearest Hostile.

So expanding on what you said earlier, rename 'target nearest hostle' to 'target next nearest hostile', rename 'target nothing' to 'target nearest hostile', and either add a new targeting option that either does nothing, or change target self to target a null object and rename that to 'target nothing'