Dagger Bug - can't attack at certain proximity

[Serancha]

This is an odd one. The uncharged normal attack does not work at all within certain distance of mobs. Screenshots to show the range that is the issue.

EDIT: This is not just planar blades, but ALL rogue daggers! (goblin blades as the only exception)

What is interesting is that the archers in Tinderin wilds are coded to stay that specific distance from you, so they will continually back up so you can't hit them unless you use a skill attack. The charged normal will work at this position, but it does not hit anything, so is useless to try.

The bug makes it feel almost like you are stunned, standing there unable to hit anything. Really bizarre.

109556

109557

[Madnex]

If there was really a change, this was perhaps the most annoying feature previous daggers had. I kept being pulled close to the mob core when I had intended to just attempt to proc the myth daggs spamming arrows from a certain distance. But no, it would just autolock on something and completely skew the elimination order tactic I was trying to pull. Perhaps I've been a bow user for too long.

More specifically, on topic, try to switch out with magma daggs at the exact spot after the planar knives have failed. See if those bring you close or it was an overall adjustment.

[Serancha]

I just tested with All varieties of daggers I had handy, including:

Planar Knives
Magmatic Blades
Goblin Blades
Lifethief
Depraved
Dimensional
Incandescent

This bug applies to ALL daggers except the goblin blades! It does not pull you into hitting range, just freezes you motionless when you try to tap your attack (which dagger rogues do all the time between their skills)

[Madnex]

I think I'm understanding this better now. Not sure why the goblin daggers would have more range, probably an unintended detail.

Example 1: How many times have you pierced to a spot around Stahl in arena? Your ping seems fine and the arrows you shoot are going straight on him, right? But try using pierce or razor and you'll realize he's not exactly at the spot where you see him standing.

Example 2: Remember that glitch that let you walk outside the map borders in any map? It was not completely fixed because now, if you pierce while moving on a wall to something that *just* got blocked by a part of the wall which got in-between as your character moved away, here's what happens: as you walk away (appearing to be in safety distance from everything) you'll see yourself taking damage from enemies that would not normally be able to hit you from this far. What happens is that your position on the server is different from the one you're viewing at your end. Similarly to what happened when the out-of-walls glitch happened, your character will simply keep walking either back to the spot where the routes of your server coordinates and visible coordinates split or, if you keep moving, your server side "shadow" (invisible to you) will take the perfectly shortest route to join your character's image (that you are seeing). To be clear, these type of situations don't require high ping to occur.



This might also be related to the back-and-forth wiggling bug that we had a while ago on test server and although it's now fixed for the players, certain mobs like the purple melee vines still occasionally do that weird spastic movement which is slightly irritating because when they do it, they do it underground (you can't hit them if they don't surface). I'd imagine your daggs bug is the result of the described issue above.

It seems like an issue with certain moving enemies that don't consistently and properly update their positions on the client side (our side). Or there's an error margin at the mob's movement calculation with no confirmation backup or even no detection of the anomaly in the first place. This might be a little hard to understand if you don't get out in the field and test it.

[Serancha]

Example 1 happens with bow. It's something that started with the planar arena release, where you can not pierce close to stahl. Like he has a forcefield around him. Different bug entirely.

This dagger bug is brand new like within the last 2 weeks.

You can test this bug with barrels also. Windmoore harbour has a nice set right before the first bridge

[SacredKnight]

It should be understood that all content when released contains a variation of bugs :/ Unfortunate but we have to tolerate it.....

[Serancha]

This is not just new content. This is affecting all daggers of all levels, except one, which is a novelty item at best.

That is like having all mage staffs get bugged, or all warrior blade weapons. It means we can't effectively use 50% of our weapons.

[Madnex]

Example 1 happens with bow. It's something that started with the planar arena release, where you can not pierce close to stahl. Like he has a forcefield around him. Different bug entirely.
I'll have to test. Pretty sure it's an issue of similar nature. The "force-field" appears after he moves around once or twice and is sometimes removed when he changes place (so it's movement-placement related).

[Haligali]

This is not just new content. This is affecting all daggers of all levels, except one, which is a novelty item at best.

That is like having all mage staffs get bugged, or all warrior blade weapons. It means we can't effectively use 50% of our weapons.

All mage staff is crap and all warrior shield also, this is nothing new.

[Serancha]

All mage staff is crap and all warrior shield also, this is nothing new.

Hali, daggers were not like this 2 weeks ago. This IS new and it is wrong.

I play a mage too, and staffs don't have any bug anything like this. There is a huge difference between not liking something, or something having crappy stats, and there being a failure in basic functionality.

Daggers are a weapon that relies on auto-attack, if you can not use that function when within hitting range of the mobs, it makes them useless. Daggers have been my weapon of choice since season 1, and I can say without any doubt that this is a brand new issue - one that urgently requires fixing.

[twoxc]

So bottom line is PLEASE FIX IT lol.

[Serancha]

Mythic blades are the same as goblin. They hesitate like you're lagging, but will still let you attack. All other daggers disallow attacking when in the shown proximity to mobs, bosses, boxes, barrels etc.

Tested a shiny new set of common blades also. It runs all the way down the weapon chain.

Avaree said she started noticing it 2 days ago.

[Avaree]

Mythic blades are the same as goblin. They hesitate like you're lagging, but will still let you attack. All other daggers disallow attacking when in the shown proximity to mobs, bosses, boxes, barrels etc.

Tested a shiny new set of common blades also. It runs all the way down the weapon chain.

Avaree said she started noticing it 2 days ago.

It may have started sooner than two days ago, but that is when i noticed in tombs that at times the daggers didnt hit when i tapped. I chalked it up to lag, until i read this thread.
Blackbeard's nefarious hooks are same as the weaps Serancha listed in a few posts above, leaves the users stunned/frozen.

Tested this earlier on various elite maps, and regular maps.

This severely handicaps rogues ability to use auto attack.

* edit* the stun/frozen effect is broken when pets/party mate attacks enemies or crates & barrels

[Sorcerie]

Well if it makes you feel any better the mythic scythe staffs for mages only hit one target uncharged.

The most basic benefit of using a staff is to hit three targets, and we don't even have that on the mythic PvE weapn for sorcs.

GG.

[Serancha]

Well if it makes you feel any better the mythic scythe staffs for mages only hit one target uncharged.

The most basic benefit of using a staff is to hit three targets, and we don't even have that on the mythic PvE weapn for sorcs.

GG.

Again this is not about mages, nor is it a class comparison thread. Please make your own threads if you find a problem with a weapon for another class.

This is a dagger weapon BUG which makes daggers virtually unusable. It needs to be fixed.

[Samhayne]

Thanks for the head's up on this one. Will have our testing team give it a look.

[Jirikjurasek]

This is a dagger weapon BUG which makes daggers virtually unusable. It needs to be fixed.
Just for note to public: this bug affects all melee weapons, that means ALL warriors weapons (I cant test glaives which has longer range)

[Serancha]

Excellent find. I can't believe not a single warrior noticed this before. Possibly because they tend to get closer to the mobs and swords have a different range than daggers, making it less noticeable. Or else they just thought it was lag.

I did comfirm this on warrior with blades, sword/shield and maul-type weapons. Thank you!

[pepperx]

Thank you for posting this! I noticed last night while leveling a friend in low levels I could not hit enemy while spamming normal attacks. This need sto be fixed asap !! I prefer dagger to bow so don't want to switch!

[Candylicks]

Any word on this? It's annoying to tap auto w/ daggers only to stand there.

[Avaree]

i spoke with several tanks in guild this bug is affecting them. I also noticed that at times the elo bow would miss aim at obvious target and hit walls. Some sorcerers also reporting gun misses target too.

[Serancha]

Some word on the progress for this would be appreciated.

[Madnex]

I'm playing as warrior in the test server.. this is horrible. Unless you charge each and every hit, you'll find your character sitting and doing nothing in front of the boss even if you spam the attack button like there's no tomorrow!

[Serancha]

I'm playing as warrior in the test server.. this is horrible. Unless you charge each and every hit, you'll find your character sitting and doing nothing in front of the boss even if you spam the attack button like there's no tomorrow!

Finally, you get it! No more "just move up a step, lazy nab"? It's not that simple, is it.

[Madnex]

Finally, you get it! No more "just move up a step, lazy nab"? It's not that simple, is it.
It is but it's still annoying to have to move on it on every move the boss makes. Good thing axe and ss are there.

[Carapace]

Hey all,

I did find what I believe to be the issue on this, but it won't be in an update likely until next year.

Thanks!

[Serancha]

Ouch. Glad you found it though. Thanks for the update!

[notfaded1]

Hali, daggers were not like this 2 weeks ago. This IS new and it is wrong.

I play a mage too, and staffs don't have any bug anything like this. There is a huge difference between not liking something, or something having crappy stats, and there being a failure in basic functionality.

Daggers are a weapon that relies on auto-attack, if you can not use that function when within hitting range of the mobs, it makes them useless. Daggers have been my weapon of choice since season 1, and I can say without any doubt that this is a brand new issue - one that urgently requires fixing.

This is soooo true... if like Omni said this was maybe a bug all along then daggers have been bugged since day one... I like to think you were supposed to close on the mobs when using normal attack with daggers... this is the thing that felt so strange when you first started using daggers but we all adjusted to it if we wanted to be a dagger rogue and...... this is now NO LONGER THE CASE and it just happened recently. This changed a fundamental that was in the game from it's birth so it completely changes what we've been used to for basically EVER! So glad someone else (primarily Serancha and Candy) and now Carapace see it!!!

Candy is only recently a rogue and she immediately notice it o.O!

[Serancha]

Yes it's a new bug and affects all melee weapons. Cara said he found it, so I am hoping he will squash that bug flat. I use daggers for tombs (essence farming), meaning now I am only farming essences on mage 'cause it's just too slow and awkward on rogue using bow, and daggers are not useable.