View Issue Details

IDProjectCategoryView StatusLast Update
0015727Legion CoreClasses - Monk - Монахpublic2023-11-14 08:10
ReporterzeakeyAssigned ToGhost 
PrioritynormalSeverityminorReproducibilityalways
Status closedResolutionfixed 
PlatformWindowsOS10OS Versionx64
Summary0015727: Chi Wave breaking CC #2
DescriptionFollow up the report down below:
http://tracker.legionbugs.com/view.php?id=15621

So I retested this recent fix and I see no change. CC still breaks on the jumps that monks isn't in control off.

uWoW demo:

Non direct red projectiles break CC
https://imgur.com/a/xQRxLTL

Retail Demo:

You can see on this video that chi wave jumps dont break CC. Unless directly used by monk on CCed target. With First projectile. The other 3 damage projectiles do not break CC.
https://www.youtube.com/watch?v=3sGvsSBX1zg

Activities

Shadowraze

2021-07-25 16:23

updater   ~0046996

Hello, I checked.
Works as you described.
I will redirect to the developer.

Ghost

2021-07-30 19:25

developer   ~0047153

you did not indicate in that report that the wave transition cycle itself should stop, I only understood that for the wave transition a goal is being sought in control and made sure that such a goal is not sought, but you do not take into account one point, in tests where you apply it to the main goal, you should have written that the transition cycle itself should stop at all.

Ghost

2021-07-31 18:22

developer   ~0047189

on the game worlds, my fix works perfectly, I couldn't reproduce it anywhere

zeakey

2021-07-31 22:58

reporter   ~0047196

Hi Ghost,

I've send you demo of how to reproduce the bug. It isn't very complex. You just need to challenge one person for a duel. You can PM me on Discord (PePe#0239) and I can live stream to you the actual bug and step by step while talking to you to show what is wrong.

The whole thing is that the spell is divided in to 3 parts.

1.) 1 First wave either hostile or friendly
2.) 3 or 4 Healing bounces
3. ) 3 or 4 Damage bounces

The very first wave is the one that can break CC. Any other hostile bounce that is automatically bouncing around should not break CC due to player not being in control of it. Only first one is the one player is in control of.

Ghost

2021-08-01 19:44

developer   ~0047228

in your video, there is a clear misunderstanding that the wave already flying into the selected target has the right to interrupt control, because it has chosen the target and is already flying, that is, having given the effect of losing control, it is necessary to understand that all the abilities already flying into the target will disrupt its action

a banal stupid example in the arena let's say you are for the warlock destruction and your partner is a mage, he casts a polymorph, but at this time you have already launched your chaos bolt
that is, the spell has already flown to the target and the owner cannot change the parameters of the spell further, it cannot control this as well as the process of flying a wave that has already chosen a target

there are no questions, write to the discord PM, we will test it, but then on a bunch of repetitions you will understand yourself that you are trying to achieve an unsolvable fix and you will see the meaning of my fix

here is my discord Бесперспективняк#6133

Issue History

Date Modified Username Field Change
2021-07-24 22:30 zeakey New Issue
2021-07-24 22:30 zeakey Status new => assigned
2021-07-24 22:30 zeakey Assigned To => Shadowraze
2021-07-25 16:23 Shadowraze Note Added: 0046996
2021-07-25 16:23 Shadowraze Assigned To Shadowraze => Ghost
2021-07-25 16:23 Shadowraze Status assigned => confirmed
2021-07-30 19:25 Ghost Note Added: 0047153
2021-07-30 19:25 Ghost Status confirmed => acknowledged
2021-07-31 18:22 Ghost Status acknowledged => resolved
2021-07-31 18:22 Ghost Resolution open => unable to reproduce
2021-07-31 18:22 Ghost Note Added: 0047189
2021-07-31 22:58 zeakey Status resolved => feedback
2021-07-31 22:58 zeakey Resolution unable to reproduce => reopened
2021-07-31 22:58 zeakey Note Added: 0047196
2021-08-01 19:44 Ghost Note Added: 0047228
2023-11-14 08:10 Alica228 Status feedback => closed
2023-11-14 08:10 Alica228 Resolution reopened => fixed