Works for me till we are the ones dying... then what?!!
Printable View
Yeah but you can just use an ability forgoing the whole one other button you have to press. If you don't want to actually use an ability just click on something that is currently unavailable to be activated. Or just press two buttons instead of one. One button or two, you still have a choice because they didn't change anything in that regard you just have one less ability in your arsenal to actually press.
I think i'll consider using my PS3 controller. =/
I haven't read the whole thread yet but here's the problem. DoctorMog is justified in his criticism here when he says;
Creators Hand's solution and what's being looked over I think is bolded:Quote:
Originally Posted by DoctorMog
The problem DoctorMog is getting at is that the bar has to be active. I couldn't tell you how many times I've had my weapon out thinking, "Why aren't I attacking? Am I not close enough? What's going on?" Then I go to use a heal or something and I noticed that my bar wasn't active.
Yes, the system defaults to the bar always being active but you can turn that off in the configuration menu (which I've done because I like to have a clean UI). It would be nice if you could turn auto attack off and put melee's basic attack on a timer ala Archer bow delay, but I think just targeting an attackable mob and facing said mob should be enough to automatically bring up your bar and start auto attacking. If you're going to have auto attack; needing to confirm, even after all of those context sensitive requirements have been reached, is unnecessary.
Having auto attack off can have it's benefits without being game breaking. There have been some situations where I've wanted auto attack not to fire and others where I'm glad I don't have to worry about pressing a button for my basic attack.
While rare, and fault due to user error, sometimes on my Lancer I'll accidentally use a buff like Raging Strike when unintentionally. Now if I've activated Invigorate then I know eventually my TP will be high enough to put that Raging Strike to good use. Unfortunately, if I've accidentally pressed the button for Raging Strike, I have to unlock and turn away from the mob in order to wait for Invigorate to bring my TP up to a high enough level before I can reengage without "wasting" Raging Strike. This is especially more useful for tanks who want to concentrate on making those context sensitive weapon skills like Fracture, Jarring Strike, and Phalanx even more powerful by combining them with attack buffs.
Obviously turning auto attack off would only have benefits for more advanced users but it wouldn't break the game at all if you just made the basic attack function the same way as an Archer's bow delay would. Though, you would have to take into account what the Haste spell (currently unimplemented) would effect, ability timers or just attack speed.
EDIT: I guess there's more too it as well which only further supports DoctorMog's position and I've noticed this as well.
Quote:
Originally Posted by Reinhart
This is probably my only gripes about the update. I'd rather we just remove the cooldown on auto-attack, since it's y'know, auto-attack. Pressing 1 is much easier than F -> C -> Enter. That's my input on that, though.
About the whole Controller/KB+M subject; I find Keyboard and Mouse to be much more efficient with this game. The mouse is a better camera control than an analog stick, the number keys, more keybindings, etc. One of my friends tends to use macros to compensate for the lack of a keyboard. I'm not a huge fan of that personally, but opinions. I'd like for more support for both control methods. The keyboard is actually a viable controller in this game, unlike FFXI.