get RID of the extra buttons to press when engaging please

[DoctorMog]

I USED to be able to walk up to a monster, and press 1 (light attack)

NOW I have to walk up, press "F" to pull out my weapon, "C" to lock on, then ENTER to start auto attacking.

I assumed they were trying to REDUCE the number of actions we had to take to do things.


Guess not...

Can we PLEASE just get an action at level 1 called "Auto attack on/off"

This whole "not sure if my character is attacking or not" thing is BS

[Ruri]

I see keyboard still sucks. Its not bad with gamepad. Btw I think you can still start a fight and set up auto attack by using an ability on a mob? Such as full thrust or something. Not sure if it worked but I think I did it that way.

[Reinheart]

I see keyboard still sucks. Its not bad with gamepad. Btw I think you can still start a fight and set up auto attack by using an ability on a mob? Such as full thrust or something. Not sure if it worked but I think I did it that way.

yep that works but with recast timers on the moves not best to start off with it + wouldn't work if fighting multiple mobs and stuff...

I got a weird one dunno if others got this too, when doing leve's and fighting mob groups and say there was a non-active/non-leve mob that just happened to be where the leve mobs were, you kill 1st leve mob and when trying to target the 2nd mob (or 3rd..etc) if you target the non-active/non-leve mob even without pressing the Enter Key to confirm sometimes it starts hitting the mob... but then again this doesn't happen on mobs you need to fight, you switch correct target but have to press Enter Key so it changes to the fight mode with that red light.

I swear I didn't push the enter key on the non-leve mob I was just pushing number 0 key to tab through the mobs... happened 2-3 times so far, so it's not happening every time but it's weird...

[Physic]

yep that works but with recast timers on the moves not best to start off with it + wouldn't work if fighting multiple mobs and stuff...

I got a weird one dunno if others got this too, when doing leve's and fighting mob groups and say there was a non-active/non-leve mob that just happened to be where the leve mobs were, you kill 1st leve mob and when trying to target the 2nd mob (or 3rd..etc) if you target the non-active/non-leve mob even without pressing the Enter Key to confirm sometimes it starts hitting the mob... but then again this doesn't happen on mobs you need to fight, you switch correct target but have to press Enter Key so it changes to the fight mode with that red light.

I swear I didn't push the enter key on the non-leve mob I was just pushing number 0 key to tab through the mobs... happened 2-3 times so far, so it's not happening every time but it's weird...

you dont need to confirm any more, if you have your bar active, and something is targeted and close enough to hit it, you will start attacking it.

an AA on off button would have been a better implemention imo.

[DoctorMog]

you dont need to confirm any more, if you have your bar active, and something is targeted and close enough to hit it, you will start attacking it.

an AA on off button would have been a better implemention imo.

For some reason, I walk up to a monster.
I hit F to pull out my weapon.
I hit C to lock on.

I still do not auto attack.

I must hit ENTER to initiate it.

[Physic]

For some reason, I walk up to a monster.
I hit F to pull out my weapon.
I hit C to lock on.

I still do not auto attack.

I must hit ENTER to initiate it.

i just get next to them, it will tell me im too far away if i lock on them from far, maybe it just takes a long time to start the first hit. i dunno. I do mostly use gamepad though, but it would still be better with an attack on/off button imo. and the first hit should be instant as long as you didnt just hit something else.

[Namynyor]

For some reason, I walk up to a monster.
I hit F to pull out my weapon.
I hit C to lock on.

I still do not auto attack.

I must hit ENTER to initiate it.

I have noticed many times that the action bar doesn't come up when I go into active mode. This means that if I am selecting a target to use Cure spell or anything else, I am not going to attack the enemy that's engaged with me. Auto-attack should override the action bar IF an enemy has enmity against you (i.e. is aggressive and has attacked you, or you have attacked it), and be passive until confirmed for an enemy that doesn't have enmity against you. This would solve the issues of non-aggressive mobs in middle of leve targets. Auto-target works that way with the auto-attack script in FFXI, so it's not something that can't be figured out. If an enemy starts to attack you, and you draw your weapon, you should automatically engage it, not have to draw weapon, bring up action bar, and then engage it. Also, I do not like how the action bar will shift target to myself when I'm casting buffs/cure as a mob dies, while there is still another mob engaged with me. I can't auto-attack when the target has shifted to self.

[Reinheart]

you dont need to confirm any more, if you have your bar active, and something is targeted and close enough to hit it, you will start attacking it.

an AA on off button would have been a better implemention imo.

Even if you're in active mode if you don't target and confirm (press enter key) it doesn't switch the target bar red with the sword icon on the right to start the AA, I noticed this when I was fighting different mobs I had to press enter key to make sure the target bar has that red color + sword icon in order to make it AA or I just stand there like an idiot.

Confirmation is fine I have no problem doing that but problem is I'm fighting 2+ mobs at same time in same mob group and once I finish the first one I start the tabbing through mobs so I can target the 2nd+ mob right away but if there is a non-active/non-leve right next to you and you tab through them before the actual mob you want to fight, it sometimes starts AA automatically without confirming (pressing the enter key) somehow when you kill the last mob the AA still stays in fight mode (with the sword icon) and doesn't go away right away so if you target mobs too quick after kill it still continues to AA on whatever mob you target first (if mob is right by you or in attack range) At least that's my guess.

[Rhomagus]

I haven't read the whole thread yet but here's the problem. DoctorMog is justified in his criticism here when he says;

For some reason, I walk up to a monster.
I hit F to pull out my weapon.
I hit C to lock on.

I still do not auto attack.

I must hit ENTER to initiate it.

Creators Hand's solution and what's being looked over I think is bolded:

you dont need to confirm any more, if you have your bar active, and something is targeted and close enough to hit it, you will start attacking it.

an AA on off button would have been a better implemention imo.

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.

Even if you're in active mode if you don't target and confirm (press enter key) it doesn't switch the target bar red with the sword icon on the right to start the AA, I noticed this when I was fighting different mobs I had to press enter key to make sure the target bar has that red color + sword icon in order to make it AA or I just stand there like an idiot.

[Gramul]

Not to sound insensitive to the plight, but you really should invest in a PC controller.