View Issue Details

IDProjectCategoryView StatusLast Update
0019321Return of ReckoningGeneralpublic2023-12-09 15:15
ReporterReturnOfReckoning Assigned To 
PrioritynormalSeverityminorReproducibilityhave not tried
Status closedResolutionopen 
Summary0019321: [WL] Coordinated Strike
DescriptionReporter: Symbelmyne

-->As toolip of Coordinated Strike (WL skill) states:
![Coordinated Strike](https://user-images.githubusercontent.com/16525371/125775529-8ada6b43-f2c9-4456-a09b-cbade3e4d2bc.png)
combat log should register 2 hits from player and 2 hits from WL while being within 35ft away from eachother.

Unless there was some change to how CS works it seems to be bugged and combat log only register one hit from a player and 2 hits from pet. Seems pet is not in 35ft range for a player POV, but player is within 35ft range from pet POV.
Of course tested while being in melee range both me and pet.
Edit: tested again and CS register only 1 hit from player and 2 from pet if CS is a 1st skill used in attack target.

![WAR-64 2021-07-15 12-36-04](https://user-images.githubusercontent.com/16525371/125775968-eab28bb0-57f3-4079-b0e0-cde7f4d786ca.png)


**Steps to reproduce the problem:**

Summon WL`s pet and attack construct with Coordinated Strike while being in melee range both pet and WL.

Reporting as new bug since WL "mega thread" is flooded with combat formulas and few bugs at once etc, but still miss simple bug - WL hit once, pet hit twice while using Coordinated Strike.

Also attaching .getstats regarding someone wants to calculate dmg done in screen above (which seems pretty low tbh)

![WAR-64 2021-07-15 12-55-01](https://user-images.githubusercontent.com/16525371/125777152-7c30dfd8-b841-47f3-bd66-cae716b6ba2d.png)
TagsAbility

Activities

ReturnOfReckoning

ReturnOfReckoning

2023-08-13 04:28

reporter   ~0035992

Commenter: lilimx

Hey,

uhm it's working on my end.
![grafik](https://user-images.githubusercontent.com/23266079/125787542-f43bc526-c545-4bde-b35e-9e5bd021423c.png)
Edit note: tested and worked on dev and live server


Could you post me your skill tree + tactics
ReturnOfReckoning

ReturnOfReckoning

2023-08-13 04:28

reporter   ~0035993

Commenter: Symbelmyne

Ok, I found the problem, CS register one hit from player when being 1st skill on attack. No other skills used before CS. If CS is a following skill , like FO>>CS - there are 2 hits registered. Try that. Of course from melee range attack.
ReturnOfReckoning

ReturnOfReckoning

2023-08-13 04:28

reporter   ~0035994

Commenter: Symbelmyne

Spec and tactics:
![New Bitmap Image](https://user-images.githubusercontent.com/16525371/125790724-d5cd56fe-9f17-4f6c-832d-2922a0950ff2.png)

Brute Force
Pack Synergy
Jagged Edge
Hack and Slash
ReturnOfReckoning

ReturnOfReckoning

2023-08-13 04:28

reporter   ~0035995

Commenter: lilimx

> Ok, I found the problem, CS register one hit from player when being 1st skill on attack. No other skills used before CS. If CS is a following skill , like FO>>CS - there are 2 hits registered. Try that. Of course from melee range attack.

Hey,
but that's what I did... I only used CS to test it
ReturnOfReckoning

ReturnOfReckoning

2023-08-13 04:28

reporter   ~0035996

Commenter: lilimx

Hey,

okay I did some more tests. It looks like that the lion "slacks" a bit in the beginning of the fight. So the game thinks the lion isn't next to you or so. It doesn't matter if you are already inside the mob or 3 ft away...sometimes it looks like the lion doesn't get the signal or so.
ReturnOfReckoning

ReturnOfReckoning

2023-08-13 04:28

reporter   ~0035997

Commenter: emailkook


https://user-images.githubusercontent.com/50253609/126148449-4e1cfae9-e597-4873-a7db-1176f2143703.MP4

that clip is an example of pathing problems WL pet plagued with. First attack on a player mounted or dismounted the pet starts/warps 40’ behind you. So this is related probably why some CS hits aren’t registered properly. Issue is ongoing for months with many pathing complaints.
MaxHayman

MaxHayman

2023-12-09 15:15

administrator   ~0040891

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 04:28 ReturnOfReckoning New Issue
2023-08-13 04:28 ReturnOfReckoning Tag Attached: Ability
2023-08-13 04:28 ReturnOfReckoning Note Added: 0035992
2023-08-13 04:28 ReturnOfReckoning Note Added: 0035993
2023-08-13 04:28 ReturnOfReckoning Note Added: 0035994
2023-08-13 04:28 ReturnOfReckoning Note Added: 0035995
2023-08-13 04:28 ReturnOfReckoning Note Added: 0035996
2023-08-13 04:28 ReturnOfReckoning Note Added: 0035997
2023-12-09 15:15 MaxHayman Note Added: 0040891
2023-12-09 15:15 MaxHayman Status new => closed