Am I only one who finds autoattack so slow ?

[Synthesis]

battle ts better in general since patch, more ballanced and so on.
But auto attack is so slow, that is less playable than it was before patch ( I had more fun with 1key spamming, at least my chara did something).

I think battle could be a bit faster, so player actually feels he is playing. I think I am just standing sometimes and I find this very boring. I dont know how new players will, especially these on PS3, will welcome this. Some might but some might not as well. But you cant please all. At least I think "A bit" faster battle could be enjoyed by more ppl (not hyper fast, as it was before update was quite ok).

Please discuss if you have got similiar opinion on auto-attack spd rate.

Edit :
I am refering from my experiences as MRD or LNC. And from what 2 friends told me, they both quitted in first two days of game at ranks 12 and 24. Because of battle, they said. (they bought game and tried it after 1.18). I am used to game since collectors, so I am dealing with updates myself.

[Antanias]

I believe a previous letter from the producer went into detail as far as the battle system goes. We currently have the groundwork in place, and improvements being not too far from now.

[Falcus]

I just don't like auto attack at all, it's slow and it can be a pain in the ass at times.
I've had times where I've been buffing, then I'll start scrolling through mobs and I'll randomly auto attack one that's next to me even though it was only targeted for maybe 1/4 of a second. (Playing as ARC and it's usually something that I don't want to fight)

Personally I wish we could turn it off altogether if we want to.

[Dargoth_Draconia]

I just don't like auto attack at all, it's slow and it can be a pain in the ass at times.
I've had times where I've been buffing, then I'll start scrolling through mobs and I'll randomly auto attack one that's next to me even though it was only targeted for maybe 1/4 of a second. (Playing as ARC and it's usually something that I don't want to fight)

Personally I wish we could turn it off altogether if we want to.

Works perfect for me at all times and seems right considering I am using a 2H on MRD, LNC is quick once they get speed surge. They will be adjusting it over the next 2-3 big patches to make it even better so sit back and give it time.

[ChiefCurrahee]

I just don't like auto attack at all, it's slow and it can be a pain in the ass at times.
I've had times where I've been buffing, then I'll start scrolling through mobs and I'll randomly auto attack one that's next to me even though it was only targeted for maybe 1/4 of a second. (Playing as ARC and it's usually something that I don't want to fight)

Personally I wish we could turn it off altogether if we want to.

You don't engage mobs when selecting target.

You only engage mobs after selecting and confirming selection.

Either you are unaware that you have actively engaged a mob, or you are exaggerating.

[Physic]

You don't engage mobs when selecting target.

You only engage mobs after selecting and confirming selection.

Either you are unaware that you have actively engaged a mob, or you are exaggerating.

ok went in there and tested it because i remember these issues before. The problem is that "confirming" is the act of bringing up your battle menu, which would be fine, except the favt that you bring up your skill ui, not only for battle but also for buffs, cures, etc. so if you are switching between monsters while looking for your cure skill, or raging strike, or trying to chakra yourself after you die, you will hit whatever you have targeted, people who play with a lot of macros are probably less likely to have any issues since it doesnt bring up the action bar.

Its a bad design that merely looking at your skill bar list, or even bringing it up to scroll to a different ability, automatically puts you in AA mode. Especially when you look at the old system where having something targeted did nothing at all, you would often target things just to pull up your menu and do a buff fast, when nothing is close it starts on you, but when something else is close it locks on that.

Looking at it carefully, this looks to be one of the things where a lot of play was tweaked around a different mechanic, and doesnt gel as well because some rules changed.

They either need to make it so pulling up your action bar doesnt initiate AA on a selected target, or make it so that AA uses a different mechanism to officially trigger. They should probably put something into place that signals to the user that the guy is going to actively AA now. Its more clear when you have a button that says attack, or AA, but if your not doing that some sort of different stances when in AA mode or something could also work. Its still needs a lot of tweaking imo

as a side note this also means you are even more likely to AA a monster that you are trying to do something special too, if you are close enough, like sleep, paralyze, bind etc. because it requires you to go open your action bar, and have the monster targeted. You can probably get around this by using macros with subtarget commands, once/if thats enabled, but its still pretty counter intuitive and awkward design wise.

[Konachibi]

ok went in there and tested it because i remember these issues before. The problem is that "confirming" is the act of bringing up your battle menu, which would be fine, except the favt that you bring up your skill ui, not only for battle but also for buffs, cures, etc. so if you are switching between monsters while looking for your cure skill, or raging strike, or trying to chakra yourself after you die, you will hit whatever you have targeted, people who play with a lot of macros are probably less likely to have any issues since it doesnt bring up the action bar.

Its a bad design that merely looking at your skill bar list, or even bringing it up to scroll to a different ability, automatically puts you in AA mode. Especially when you look at the old system where having something targeted did nothing at all, you would often target things just to pull up your menu and do a buff fast, when nothing is close it starts on you, but when something else is close it locks on that.

Looking at it carefully, this looks to be one of the things where a lot of play was tweaked around a different mechanic, and doesnt gel as well because some rules changed.

They either need to make it so pulling up your action bar doesnt initiate AA on a selected target, or make it so that AA uses a different mechanism to officially trigger. They should probably put something into place that signals to the user that the guy is going to actively AA now. Its more clear when you have a button that says attack, or AA, but if your not doing that some sort of different stances when in AA mode or something could also work. Its still needs a lot of tweaking imo

as a side note this also means you are even more likely to AA a monster that you are trying to do something special too, if you are close enough, like sleep, paralyze, bind etc. because it requires you to go open your action bar, and have the monster targeted. You can probably get around this by using macros with subtarget commands, once/if thats enabled, but its still pretty counter intuitive and awkward design wise.

By action bar you mean the thing with your skills/spells that number 0 to 9 right?
You can set that to permanently be on in your options menu.

[Viridiana]

You don't engage mobs when selecting target.

You only engage mobs after selecting and confirming selection.

Either you are unaware that you have actively engaged a mob, or you are exaggerating.

Steps to reproduce:

1) Click enemy once. Note that nothing happens at all at this point.

2) Use any ability whatsoever.

3) Accidentally punch enemy in the face.

Feel free to go test it out yourself.

[AsterBarnivere]

Steps to reproduce:

1) Click enemy once. Note that nothing happens at all at this point.

2) Use any ability whatsoever.

3) Accidentally punch enemy in the face.

Feel free to go test it out yourself.

*Punches random person* D: I'm sorry AA made me do it!

[ChiefCurrahee]

Steps to reproduce:

1) Click enemy once. Note that nothing happens at all at this point.

2) Use any ability whatsoever.

3) Accidentally punch enemy in the face.

Feel free to go test it out yourself.

1)select
2)confirm
3)attack