View Issue Details

IDProjectCategoryView StatusLast Update
0035243Legion CoreClasses - Shaman - Шаманpublic2026-05-03 17:32
ReporterFrappa Assigned ToGhost  
PriorityhighSeveritymajorReproducibilityalways
Status resolvedResolutionfixed 
PlatformWindowsOS10OS Versionx64
Summary0035243: Chain Lightning doesn't jump/hit targets that are LoS
Descriptionhttps://www.wowhead.com/spell=188443/chain-lightning shaman ability doesnt hit targets that are line of sight. The ability is supposed to 'Enforce Facing on Primary Target Only' and spread to any subsequent target that is in range. ( after 1st hit LoS is checked from mob-to-mob, not player-to-mob).

Chain Lightning (ID 188443) Mechanic Error:
The spell is incorrectly checking for Caster Line of Sight on secondary jumps. Per Patch 1.11.0, (https://wowpedia.fandom.com/wiki/Patch_1.11.0) only Stealth/Invisibility checks should refer back to the caster. Secondary jumps should be determined by Line of Effect and Range from the previous target in the chain, not visibility from the caster.

Here is example video of how it currently works on uwow x100: https://youtu.be/Rz5nu1Hry84


__________________________________________
[Перегрузка цепной молнии] 45297
[Цепная молния] 188433
[Перегрузка потока лавы] 114738
[Поток лавы] 114074
имеет лос чек от шамана которого не должно быть, лос должен проверятся только от жертвы молнии до таргета отскока

Activities

Frappa

2026-04-23 04:10

reporter   ~0080813

Here, in this retail video https://www.youtube.com/watch?v=88iGMKDb5E0 at minute 12:26 , you can clearly see that enemy that is LoS is getting hit by subsequent jumps of Chain Lightning (288k initial hit and 242k mastery proc hit) also can see visually that chain lighting is jumping to LoS target

Frappa

2026-05-03 15:13

reporter   ~0080874

Problem is still there, nothing changed!

Whatinhell

2026-05-03 16:20

administrator   ~0080875

Look forward to the next game server update. In the meantime, you can check out the fixes on the test realm and make sure the issue is fixed.

Frappa

2026-05-03 17:19

reporter   ~0080876

My apologies, it's working perfectly on the test server. I simply thought fixes are implemented every morning after server reset.

Issue History

Date Modified Username Field Change
2026-04-23 03:57 Frappa New Issue
2026-04-23 03:57 Frappa Status new => assigned
2026-04-23 03:57 Frappa Assigned To => Whatinhell
2026-04-23 04:10 Frappa Note Added: 0080813
2026-04-23 12:46 Whatinhell Description Updated
2026-04-23 12:51 Whatinhell Status assigned => confirmed
2026-04-23 12:55 Whatinhell Assigned To Whatinhell => Ghost
2026-04-27 17:08 Whatinhell Description Updated
2026-05-01 21:17 Ghost Status confirmed => resolved
2026-05-01 21:17 Ghost Resolution open => fixed
2026-05-03 15:13 Frappa Status resolved => assigned
2026-05-03 15:13 Frappa Resolution fixed => open
2026-05-03 15:13 Frappa Note Added: 0080874
2026-05-03 16:20 Whatinhell Note Added: 0080875
2026-05-03 17:19 Frappa Note Added: 0080876
2026-05-03 17:32 Whatinhell Status assigned => resolved
2026-05-03 17:32 Whatinhell Resolution open => fixed