Unable to hit player's with melee auto attacks or AOE abilities.

Unable to hit player's with melee auto attacks or AOE abilities:

We have tested and re-created a bug that makes player's functionally invulnerable to melee auto attacks and AOE abilities.

The invulnerability appears to drop off at times apparently if some status effects are applied to the character steps taken to re-create this are:
Cleric healed a player and they lost their invulnerability
Bard procced the 'Glee' status effect and they lost their invulnerability

To re-create the invulnerability we tested:

Scenario 1: Emberspring respawn

Player A and Player B can hit each other with melee auto attacks and AOE abilities.

Player A kills Player B - Player B respawns at emberspring runs back to fight again. Player A can no longer hit AOE abilities or melee auto attacks on Player B. Player B can hit melee auto attacks and AOE on Player A.

Scenario 2: Render distance

Player A and Player B can hit each other with melee auto attacks and AOE abilities.

Player B runs away out of render from Player A, Player B returns to the same location and is now invulnerable to melee auto attacks and AOE abilities from Player A. Player B can still hit Player A.

Scenario 3: Player who remains in the 'higher density' location is unable to hit the player who leaves and returns to the same location.

Player A and Player B can hit each other with melee auto attacks and AOE abilities.

Player B and all players besides player A left the render distance.
Upon return Player B was invulnerable to Player A melee auto attacks and AOE abilities.

Note: This all occurred in SW17 New Aela Vyra. We did send someone to SW9 who upon return was invulnerable too. (same as render distance).

Note: I can see some anecdotal reference to this bug in the forums specifically referencing 'Fighter' class, that is also how we first noticed but it extends beyond them as detailed above.

Note: I reviewed the known issues list and did not interpret any items to match this issue. REF: https://forums.ashesofcreation.com/discussion/61592/alpha-two-known-issues-list-read-me-first/p1

Thank you Devs good luck!

Find more posts tagged with

Comments

Firia

I should have added to clarify - Ranged auto attacks and targeted abilities are not impacted by this bug Player A and Player B can both be hit by these regardless of Scenario 1,2 or 3.

apfelkuchen74

Hi, I am the fighter guy with a similar bug. In my first case, where I, as a fighter, couldn’t deal damage to any other player, none of the scenarios occurred. I experienced the bug for more than 24 hours nonstop. In my second case, another fighter couldn’t attack me. This only happened with fighters, and even restarting their game and launcher didn’t fix it. However, your first scenario occurred with a bard class as the opponent. In this case, restarting the game and launcher did fix the issue. I will continue to test it further in the future.

Firia

Yes relogging fixed the issue but is not viable for any type of pvp. As you will never be in a situation besides organised fights where the opponent won't just gain huge advantage.

erx

Good post, I knew this was a problem for quite some time but wasn't aware of how to reproduce, hopefully the devs can fix this now that it's easily reproducible.

FG_Dave

Same issue with Melee in New Alea yesterday. We did some testing and multiple players reported this through ingame bug reporting.

It is only Melee that is broken, and skills which use Melee slot. Ranged attacks still work as normal

NA Citizens - Could not attack each other in melee, despite flagging or even being corrupted
Non node citizen - Could not attack but could be attacked. Moving in/out render distance and relogging changed nothing
Joeva Citizen - Neither side could attack each other with melee

Moved to Joeva zone of influence
Neither side could attack each other in melee
Both sides re-logged. Melee damage could now be performed between the 2 players who relogged only
Moved back to New Alea. Neither side could attack each other, including the 2 who relogged

Root cause still unidentified.

Child Item