View Issue Details

IDProjectCategoryView StatusLast Update
0012349Return of ReckoningGeneralpublic2023-12-09 15:20
ReporterReturnOfReckoning Assigned To 
PrioritynormalSeverityminorReproducibilityhave not tried
Status closedResolutionopen 
Summary0012349: SW Brutal assault can't use from any position under Vengeance of Nagarythe
DescriptionReporter: Kweedko

Actual behavior:
SW Brutal assault can't use from any position under Vengeance of Nagarythe
Expected behavior
SW Brutal assault can use from any position under Vengeance of Nagarythe

Steps to reproduce the problem:
Use VoN try to hit mob in front with BA. - if you reed the skill descrition it says that you can use it from any position while you Vegenful. On live it worked that way.


Screenshots/Videos or archive.org evidences:

TagsAbility, Trivial, Visual

Activities

ReturnOfReckoning

ReturnOfReckoning

2023-08-13 03:41

reporter   ~0022101

Commenter: Torquemadra

It works fine, it doesnt light up. This should light up IF it indeed did light on live, it doesnt so I surmise it didn. Probably fixable in client but minor qol issue.
ReturnOfReckoning

ReturnOfReckoning

2023-08-13 03:41

reporter   ~0022102

Commenter: Kweedko

> It works fine, it doesnt light up. This should light up IF it indeed did light on live, it doesnt so I surmise it didn. Probably fixable in client but minor qol issue.

Yes it lighted on live. And this is not just light for client side this skill is unable to use but for server it's fine(so NB sequence not working properly cause of that). I bet the same thing with BAL on WH.
ReturnOfReckoning

ReturnOfReckoning

2023-08-13 03:41

reporter   ~0022103

Commenter: Gunlingers

The Problem lies not in it lighting up. On WH Bal and knockdown works as intendent. BaL and pistol wip are grayed out on action bar while not in right position, behind target, like if the wrong stance is applyed.

                                   !THE PROBLEM IS ONLY THERE IN PVE!

I haven't played my SW some time and wondered today, that something is wrong with Brutal Assault and Flanking Shoot. They are both permanently highlighed as ''useable''(coloured).
They should be both greyed out as long as the positional requirement is not given.

This occures only on Practice Targets, ''enemy'' NPC's that are orange aggro set.

And some Instance PVE Boss Mobs as for example:
Ard'da feat (GB middle last boss)
BS Karn the Vanquisher (middel path second last boss)
Cryps Necromancer Malsidius (right wing second boss)

On SW at these Bosses we can no longer visually see on the Castbar, if one these Skills are ready,
because they look like they are always ready. but if pressed, the just TRY to start the GDC and half of
the animation.

For NB for example (what is not important anyway) the problem lies in the fact, that NB by default
checks for a skill to be activ (useable) by checking if it is coloured. Since Brutal Assault and Flanking Shot are now permanently highlighted as useable, NB will always set that skill at the top of the activ
skills. It will go on with that, until that skill has been uses and triggered his CD. But as sayed, The NB part is not important, since it is just an Addon to help Players with small experience.
In such Bossfights it will brake the NB skillsrotation then and block almost all NB skills at all.

Bonus: The slayer has the same problem with Spine crusher. You never know if it is useable or not, because it is always coloured and if applyed to an NPC that is not facing away, the slayer will display
the attack animation without realy applying the skill/dmg.

All these positional Skills should be grayed out as long as the requirements of positioning or other
requirements are not given. For example the System perfectly prevents the WH by default of using
his grayed out Silence on a Caster that is immune to Silence by giving out an yellow error on screen, that the target can not be silenced and the Skill has to be double clicked to be used for the DMG anyway.
MaxHayman

MaxHayman

2023-12-09 15:20

administrator   ~0041309

This issue is being closed as it should be fixed in the new ability system. Please create a new issue if this is not the case.

Issue History

Date Modified Username Field Change
2023-08-13 03:41 ReturnOfReckoning New Issue
2023-08-13 03:41 ReturnOfReckoning Tag Attached: Ability
2023-08-13 03:41 ReturnOfReckoning Tag Attached: Trivial
2023-08-13 03:41 ReturnOfReckoning Tag Attached: Visual
2023-08-13 03:41 ReturnOfReckoning Note Added: 0022101
2023-08-13 03:41 ReturnOfReckoning Note Added: 0022102
2023-08-13 03:41 ReturnOfReckoning Note Added: 0022103
2023-12-09 15:20 MaxHayman Note Added: 0041309
2023-12-09 15:20 MaxHayman Status new => closed