AOE Toggle Needs to GO

[Ilean]

yeah, we know it's change for the sake of change. it is not change to make the game better.

Dumb assumption with nothing to back it up. I am willing to bet my lunch money that they are removing it either because there is a fundamental change in the new battle system on our ability to make almost any spell AoE, or if not that, simply because most of us hated the silly toggle that remembered last state and made us AoE offensive spells and single target cures.

Gogogogo shift+action bar spell = AoE!

[RabidSquirrel]

Gogogogo shift+action bar spell = AoE!

I'd be cool with that. Or use ctrl+action or alt+action. Keeping ctrl and alt to macros is duuuuumb. Or make a cancel spell key and double tap an action to AoE. Tap once more to revert back to single target cast.

[zzapp]

So is SE really removing the toggle? It's a done deal? Where was that stated?

Also, could someone educate me about toggling AoE with the Z key. My Z key does nothing?

Personally, I like the toggle. Beats having to deal with 2x the spells.

[darkstarpoet1]

So is SE really removing the toggle? It's a done deal? Where was that stated?

Also, could someone educate me about toggling AoE with the Z key. My Z key does nothing?

Personally, I like the toggle. Beats having to deal with 2x the spells.

yeah one of the mods confirmed it that they spoke with the developers and they said it was being taken away.

but yeah when casting a spell instead of clicking on the button to change aoe on/off the z key on your keyboard is the default key to toggle it and on a controller it is whatever key you have set to open your macro menu.

i understand they are taking it away, but i would love to hear what they plan to replace it with. at this point i am happy with it as it is, but maybe with some information on the change i could look forward to it.

[Ayerc]

Gogogogo shift+action bar spell = AoE!

Just an FYI, this is already used in game, as a way to stack Spells (and any WS for that matter) for Battle Regimens.

And how can a remembered state cause you to misfire an AoE spell...if it's on, it's on, if it's off, it's off... That's not the toggle's fault, that'd lie on the player who forgot what the spell they cast not a few seconds before was set on. And no, lag's not the problem there, that's entirely user-side.

In any event, if the change is being made to coincide with some other major change to the battle system, they need to tell us that along with the decision to remove the toggle. I don't think anyone can blame us for putting this move in the context of what we know about the game in it's current state, since we have nothing else to go on.

And I wouldn't say most players hate the toggle. If anything, they may hate the extra confirm, which others have pointed out is simply a sub-target confirmation, which would need to be there regardless. You can't select a target to cure if you're locked on the monster, and using the clunky targeting system as is to select a member to cure is way to slow and cumbersome for efficient casting.

[Ilean]

Just an FYI, this is already used in game, as a way to stack Spells (and any WS for that matter) for Battle Regimens.

ok ctrl + spell!

And how can a remembered state cause you to misfire an AoE spell...if it's on, it's on, if it's off, it's off... That's not the toggle's fault, that'd lie on the player who forgot what the spell they cast not a few seconds before was set on. And no, lag's not the problem there, that's entirely user-side.

Well not all of us are perfect in mind and body, so a toggle that remembers it's last state is bad news once things heat up.

[Ayerc]

ok ctrl + spell!

I get what you're saying though, an alternate way to toggle AoE is not a bad idea. A key combination may not be the best method, however, since the controller doesn't have any unused buttons to match that type of function.

I'd also find a toggle to set before selecting the spell to cast possibly cumbersome as well. Going for a cure, but forgot to set AoE, you'd have to back out to the toggle, then reselect the spell, subtarget, etc. I honestly think keeping it at the subtarget confirmation step is the easiest way to handle an AoE toggle.

Now, if they want to allow us to set two different AoE, support and offensive, or set the initial AoE state in the ability bar menu, that'd be great.

Well not all of us are perfect in mind and body, so a toggle that remembers it's last state is bad news once things heat up.

Look, I'm not perfect either. I mis-fire an AoE just as much as the next player, but I just deal with the consequences. I definitely don't blame the system though, since 99% of the time, I cast what I intended to.

I think you'll find the same thing will happen with a toggle that doesn't save the last state. It might reduce collateral damage, but a ill-timed single target cure when AoE is needed can be just as, if not more, detrimental. KO party members are more of a liability than an extra mob to tank/sleep.