Autoattack Failing

[Hammy]

Ok so the skill isn't exactly 'bugged' but imo, it shouldn't work the way it does currently. Autoattack can actually fail when your existing target has died and you've taken too long since your last action/macro and fail to hit the next target. This causes insane tediousness when attempting to solo on my tank alts as I have to keep changing targets and selecting to attack after a minute+ has passed on my first mob.

[toast]

This is really exactly as it was designed to work...

[DaveBot of Despair]

what toast said.. otherwise if u kill really slowly u can just camp a mass spawn spot and have autoattack never fail because the next mob spawns before the first one dies >_>

[Hammy]

The point of autoattack failing was to prevent camping on mob spawns.. NOT to prevent one from killing mobs he/she is already in combat with. It doesn't make any sense whatever to consider an active skill as doing a unique action and not failing to autoattack an additional mob, but if you don't have an active you can use you have to manually press cltr+a or an attack hotkey or you'll fail for being inactive even though you're in the same exact combat instance.

I can see how your issue is relevant, but it doesn't stop one for holding down a button or using a pet.

[DaveBot of Despair]

pet users get afk tested more often

holding down a button forces you to have rev window active at least, meaning u cant afk exp while watching a video or playing another game on your computer (unless your resolution is huge). Of course there are loopholes, but anything to discourage it is better than nothing.

[Hammy]

meaning u cant afk exp while watching a video or playing another game on your computer

Game issue merely requires two monitors, movie issue isn't actually afking, even if simply holding a button while watching said movie. Also, a good portion of media players have an 'always on top' option that keeps them over other windows. I resize the video players over a portion of my rev and can still hit macros or push arrow keys when I need to attack. If being incombat and acknowledging that you were there at 'some' point isn't enough, then I'd like to see the afk timer extended to around 5 minutes and THEN, have the chance to fail DURING combat rather than while shifting from one mob to another, because it's retarded how it's handled currently. If someone's going to sit and camp spawns, they're going to have an attack macro held down (Only Tankk gets afk checked on a non pet user, and even admins aren't against themselves afking on spawns on a pet user). If someone's actually attentive, that's a hell of a lot of tediousness to have us HAVE to manually accept/attack the additional targets hitting us after a minute or more has passed on single kills. It's not very player friendly to only punish one to two classes by having autoattack fail between the first and second mobs when it's so readily easy to avoid by pressing an active skill (if you have them) right at the end of the first mob or holding down a macro which I don't want to do, but do since there's no fear of punishment seeing as I'm actually HERE and can respond to tells sent to me (better luck through msn honestly if I'm afk to a movie/anime - the ding's annoying enough).

[DaveBot of Despair]

yes. those were the loopholes i was referring to.

extending the timer doesnt fix the problem.. especially if people start abusing it by speccing for super slow kills so they can afk, which i pointed out earlier.

In addition, if u extend it to 5 minutes, eventually some other crappy soloer is gonna complain because he cant kill one in 5 minutes.. and then we need to extend it again... and repeat over and over and over..

[Hammy]

Any non tank that's specced to chain spawns and continue endless combat can NOT afk on the spawn without dying. That'd be spending 3-5+ minutes in combat, on purpose.. PER MOB, nothing could effectively survive doing that to themselves. Even with min damage always being in play, even the best tank can not survive for a very long period without rest between mob(s).

Even if this was somehow abuseable, which I fail to see where you'll find a super fast spawn that someone could afk on without EVER ending combat, it would in effect be no worse, and actually more player minded/friendly, than people afking in groups/runs or idling at all.

The game was significantly easier for most of the melee classes when the autoattack timer was initially added anyways.

Also, my extended timer included autoattack failing during combat. Thus you'd seriously have to be inactive and not just in combat. 30 seconds isn't even long enough to run to piss =/.