Guild Wars 2

This is the one and only reason I stopped leveling my Engineer. I keep checking back after every new build to see if this is fixed, but it still isn’t.

Having weapon skill 1 on auto-cast makes sense with every kit (aside from grenade kit on the surface simply because it’s a targeted ability). And even if a kit didn’t work well with having an ability on auto cast, the player should be able to simply toggle it off and it will stay that way.

So, with all that said, why does it force me to re-enable auto-cast every time I switch to a kit? I really want to know if this is here to stay or I should continue to check each new build.

I was consistently avoiding switching out of my kit just because it got so tedious ctrl+right-clicking each and every time I swapped back to it.

No, not working as intended. Anet has said they are working on making a kit have an autoattack.

It is working as intended, insofar as it is the intended mechanic for bundles.

Trouble is, Arenanet want to have their cake and eat it too. They want kits to have such nice things like weapons have, yet they keep them as bundles.

Can’t have nice things and use bundles…

I don’t see why it’s such a big deal. You surely don’t want it to auto attack in PVP anyway. Even in PvE there are some monsters with retaliation, and reflects that’ll kill you if you have auto attack on.

But I guess having auto attack to trigger a skill as soon as you switch into a kit sounds handy.

On other classes, can you set a different auto attack for each weapon simultaneously, or is it just for the slot?
Because if it’s just auto attack on the slot; having no auto attack is no big deal at all; especially not to quit over.

Synsane.5189:

I don’t see why it’s such a big deal. You surely don’t want it to auto attack in PVP anyway. Even in PvE there are some monsters with retaliation, and reflects that’ll kill you if you have auto attack on.

But I guess having auto attack to trigger a skill as soon as you switch into a kit sounds handy.

On other classes, can you set a different auto attack for each weapon simultaneously, or is it just for the slot?
Because if it’s just auto attack on the slot; having no auto attack is no big deal at all; especially not to quit over.

Its only one of the issues with kits.

And it is entirely optional, no one forces you to use auto attack on the pistol/rifle, but Arenanet force you not to use auto attack on kits (or well, they make sure its absolute hell if you want the option)

Furthermore, its been addressed and acknowledged since BWE1, if you don’t know, that is months ago.

Still not fixed.

Its not just rage at that issue, its also many other issues and about how long its taking to fix something they have known about for months and promised to fix.

Creature.9476:

No, not working as intended. Anet has said they are working on making a kit have an autoattack.

Hopefully to actually remember the auto attack setting, and to not switch out kits when we hit water or revive.

Patience, they’re working on it. Engineer kit auto-attack is honestly probably low on their list of critical bugs to fix. As someone who regularly uses 3-4 kits, it will be nice to have auto-attack on kits but it’s going to make very little difference to my game play. It’s not that much effort to hit #1.

How much patience Gilgamesh?

They’ve known about it since BWE1, and said it would be fixed AT LEAST by launch. How much more patience does one need to have? Is the time for patience not over?

Lyuben.2613:

How much patience Gilgamesh?

They’ve known about it since BWE1, and said it would be fixed AT LEAST by launch. How much more patience does one need to have? Is the time for patience not over?

Citation please on fixed by launch. I played all 3 betas and paid attention to the beta forums and never read that.

Look, bugs look like this: you have high priority bugs, and you have low priority bugs. You can only fix so many bugs per build. You only have so many developers. My thoughts are this is a low priority bug. Priority is probably determined by how much an effect this has on the game. Does not having an auto-attack for kits break Engineer? Hardly. Many engineers are playing just fine. Thus, as my opinion, this is a low priority bug.

This bug may also be very complex and affect more than just Engineers, considering it could apply to bundles in general.

As much as it takes. There are over all issues that effect everyone that take priority over one professions needs.

Gilgamesh.2561:

Lyuben.2613:

How much patience Gilgamesh?

They’ve known about it since BWE1, and said it would be fixed AT LEAST by launch. How much more patience does one need to have? Is the time for patience not over?

Citation please on fixed by launch. I played all 3 betas and paid attention to the beta forums and never read that.

Look, bugs look like this: you have high priority bugs, and you have low priority bugs. You can only fix so many bugs per build. You only have so many developers. My thoughts are this is a low priority bug. Priority is probably determined by how much an effect this has on the game. Does not having an auto-attack for kits break Engineer? Hardly. Many engineers are playing just fine. Thus, as my opinion, this is a low priority bug.

This bug may also be very complex and affect more than just Engineers, considering it could apply to bundles in general.

Unfortunately there is no way to verify it since they deleted the beta forums, and I don’t want to get into an argument about the existence or non existence of a dev quote. I hope Coglin agrees with me on this one.

In the end, it has existed since the start, and it is a very important issue for engineers, as evidenced by it being the most commonly recurring thread, even after there are multiple threads, and it being the only thing that devs bothered to talk to us about in these forums.

Its a big deal, that’s been known about for a long time, and that is just terrible. It should have been fixed months ago.

Yeah, I may disagree with Lyuben on a lot of things, but he is right. They did say it would be fixed by launch.

At the time, I believe they thought they had a simple fix, and it turned out not to work, thus the delay. But that is just my assumption based on the way they stated it.