Dear devs,
As previously mentioned in the Discord chat I've noticed that autoattacks, for melee classes, either don't trigger or do so with serious delays in various specific situations.
This is a serious problem in game, since all melee classes depend on weaving for 20-40% of their total dps, depending on the class.
Below i've recorded some instances where autoattacks dont seem to work as intended.
@ Video 1: Autoattack pressed while moving in a straight line towards a still target results in "target too far away". Autoattacks also triggers in a delayed fashion once away from the target by 4m. For comparison, jumping into the 2m frontal radius of the target doesnt result in any delay.
EDIT: also just pressing autoattack without any movement key. shows no delay.
Watch 2024-10-30 16-14-50 | Streamable
@ Video 2: Trying to weave autoattacks while using a skill results in the skill happening but the autoattack failing. "Target too far away" message is shown before the skill.
Watch 2024-10-30 16-19-29 | Streamable
@ Video 3: Standing still after having approached the still target eventually results in autoattacks starting, with a delay of 2s circa. Jumping into the 2m frontal radius of the target doesnt result in any delay.
Watch 2024-10-30 16-20-10 | Streamable
@ Video 4: Demonstrates the bug of video1 in a dynamic environment, fighting a mob. Shows that autoattacks trigger only when the target is moving towards (frontal cone) the active player., and with enough delay that the character is behind the mob when the autoattack is registerd.
4hWOlsUEdhCj
@ Video 5: Demonstrates the bug in a simplified pvp environment. Confirms that autoattacks trigger only when the target moves towards the active player, being this way "intercepted". Randomly following the player, 5 registered autoattacks and about 4 more undetected for a total of 9, showed "target too far away" from a sample of 30 autoattacks attempts.
4hWOlsUEdhCj
EDIT: After some more exploring, i noticed also that if one approaches the target directly using the autoattack key *while not pushing any movement keys*, no error nor delay happens. This, while not solving the problem directly in dynamic situations (since the movement stops when the target is reached), opens up the possibility to "stitch" a convoluted solution: initially moving with "wasd", then lifting the keys when close to the target, pressing autoattack, then just as the target gets hit weaving the skill and starting to move again with wasd. Then repeat for every engagement.
This of course is a long shot from simply pressing a key and expecting it do what it should, and still results in some weaves "being lost" when the timing of the switching between wasd and autoattack is not perfect. That being said, I've seen some improvement in the rate of the weaves that actually go off while moving.
Best regards,
Sunnysidejoker/Cry
As previously mentioned in the Discord chat I've noticed that autoattacks, for melee classes, either don't trigger or do so with serious delays in various specific situations.
This is a serious problem in game, since all melee classes depend on weaving for 20-40% of their total dps, depending on the class.
Below i've recorded some instances where autoattacks dont seem to work as intended.
@ Video 1: Autoattack pressed while moving in a straight line towards a still target results in "target too far away". Autoattacks also triggers in a delayed fashion once away from the target by 4m. For comparison, jumping into the 2m frontal radius of the target doesnt result in any delay.
EDIT: also just pressing autoattack without any movement key. shows no delay.
Watch 2024-10-30 16-14-50 | Streamable
@ Video 2: Trying to weave autoattacks while using a skill results in the skill happening but the autoattack failing. "Target too far away" message is shown before the skill.
Watch 2024-10-30 16-19-29 | Streamable
@ Video 3: Standing still after having approached the still target eventually results in autoattacks starting, with a delay of 2s circa. Jumping into the 2m frontal radius of the target doesnt result in any delay.
Watch 2024-10-30 16-20-10 | Streamable
@ Video 4: Demonstrates the bug of video1 in a dynamic environment, fighting a mob. Shows that autoattacks trigger only when the target is moving towards (frontal cone) the active player., and with enough delay that the character is behind the mob when the autoattack is registerd.
4hWOlsUEdhCj
@ Video 5: Demonstrates the bug in a simplified pvp environment. Confirms that autoattacks trigger only when the target moves towards the active player, being this way "intercepted". Randomly following the player, 5 registered autoattacks and about 4 more undetected for a total of 9, showed "target too far away" from a sample of 30 autoattacks attempts.
4hWOlsUEdhCj
EDIT: After some more exploring, i noticed also that if one approaches the target directly using the autoattack key *while not pushing any movement keys*, no error nor delay happens. This, while not solving the problem directly in dynamic situations (since the movement stops when the target is reached), opens up the possibility to "stitch" a convoluted solution: initially moving with "wasd", then lifting the keys when close to the target, pressing autoattack, then just as the target gets hit weaving the skill and starting to move again with wasd. Then repeat for every engagement.
This of course is a long shot from simply pressing a key and expecting it do what it should, and still results in some weaves "being lost" when the timing of the switching between wasd and autoattack is not perfect. That being said, I've seen some improvement in the rate of the weaves that actually go off while moving.
Best regards,
Sunnysidejoker/Cry