View Issue Details

Jump to NotesJump to History
IDProjectCategoryView StatusDate SubmittedLast Update
0016901Return of ReckoningGeneralpublic2023-08-13 04:132023-12-09 15:17
ReporterReturnOfReckoning Assigned To 
PrioritynormalSeverityminorReproducibilityhave not tried
Status closedResolutionopen 
Summary0016901: Zealot Aethyric Shock is getting through Shroud of Magnus
DescriptionReporter: azpe

<!--
Issues should be unique. Check if someone else reported
the issue first, and please don't report duplicates.
Only ONE issue in a report. Don't forget screens or a video.
-->

**Expected behavior and actual behavior:**
When you pop Shroud of Magnus, you should disrupt 100%, but zealot Aethyric Shock (Stagger) worked even with Shroud of Magnus up.


**Steps to reproduce the problem:**
Use Shroud of Magnus. like Witch Hunter.
Zealot casts Aethyric Shock on you.


**Testing Screenshots/Videos/Evidences (always needed):**
<!-- Drag and drop an image file here to include it directly in the bug report,
     no need to upload it to another site -->
https://streamable.com/hxp877

<!--
Note that game critical and game breaking bugs may award a manticore/griffon (realm specific) at the leads discretion however, asking for one instantly disqualifies you from this reward.
-->
TagsAbility

Activities

ReturnOfReckoning

ReturnOfReckoning

2023-08-13 04:13

reporter   ~0031530

Commenter: colintgallagher

What is your base disrupt? SoM adds 100%, so if you're only at, say 2%, SoM will make it 102% and if the Zealot has -6% chance to be disrupted then you're sitting at 96%.
ReturnOfReckoning

ReturnOfReckoning

2023-08-13 04:13

reporter   ~0031531

Commenter: azpe

Base Disrupt: **7%**
https://i.imgur.com/bra1gnp.png

Base + SoM Distupt: **107%**
https://i.imgur.com/Wk4660G.png

Zealot was level 35, so maybe something is wrong with boost or maybe he is really lucky, i dont realy know.
MaxHayman

MaxHayman

2023-12-09 15:17

administrator   ~0041126

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:13 ReturnOfReckoning New Issue
2023-08-13 04:13 ReturnOfReckoning Tag Attached: Ability
2023-08-13 04:13 ReturnOfReckoning Note Added: 0031530
2023-08-13 04:13 ReturnOfReckoning Note Added: 0031531
2023-12-09 15:17 MaxHayman Note Added: 0041126
2023-12-09 15:17 MaxHayman Status new => closed