Seal of Command is not workin with Judgement

Hello,
I have found that "Seal of Command" is not workin with Judgement. "Seal of Command" do not hit target when Judgement is used. I have made ticket, but it was Dismissed. Making topic here to have posibility to disscuss.
In ticket I got answer:
https://www.warmane.com/bugtracker/report/128471
___
In ticket I got response from @Bigpwn:
Blue provided an excerpt from a retail 3.3.5 log that shows the sequence of events when casting Judgement with Seal of command active. That sequence does not show any seal proc.
Therefore this report is invalid
___

What does it mean "retail 3.3.5"? We do not have ratail version for years.
Why "Seal of Command" should not work with Judgement?
In Judgement description sad "Refer to individual Seals for additional Judgement effect" so from my understanding it should work. Judgement is working with:
"Seal of Righteousness" additionaly hit target
"Seal of Wisdom" give mana
"Seal of Light" give hp
Why only with "Seal of Command" it should not work then?

Using a Judgement spell while Seal of Command is active deals Holy damage.

Judgement does not have additional hit as with "Seal of Righteousness". Judgement with "Seal of Command" also do not hit near targets

Quote:

---

Originally Posted by Ordojed2

Hello

---

Hello.

Quote:

---

Originally Posted by Ordojed2

What does it mean "retail 3.3.5"? We do not have ratail version for years.

---

Even if there is no 3.3.5 now, there is data from back then, if form of videos, logs...

Quote:

---

Originally Posted by Ordojed2

In Judgement description sad "Refer to individual Seals for additional Judgement effect" so from my understanding it should work.

---

You might have certain understanding based on tooltips, but as I've shown that understanding is wrong.
Tooltips are not good way to tell if something is right or wrong, as they themselves are at times misleading, incomplete or outright wrong.

Quote:

---

Originally Posted by Ordojed2

Why only with "Seal of Command" it should not work then?

---

That is a question for Blizzard from 16 years ago.

From development perspective, firstly business logic is prepared and development starts. If tooltip says something, it has to work.
I do not how it was working back then, but it had to work. From your logs, I can see it was working like it (not generating additional hit). From my point of view it was a bug which was not catch and fixed. Shouldn't we fix it now?
@BlueAo Do you know how it was working in WOTLK Classic?

As developer I feel weird now. Fill myself in QA skin coming to me with a bug :D

All you need is logs/video/proof from back when 3.3.5 official servers were live. And they will fix it.
What do you feel weird about, it didn't proc on live and it doesn't proc here - it's working properly as it did in 2008-2010 original as far as it's known so far.

Why don't you feel weird about Seal of Corruption, tooltip says it should start to deal additional damage once it's stacked to 5, but it doesn't work that way. There are probably dozen of spells like that.

My "filling weired" is out of topic ;) It regards my communication between Developer and QA.

Have not check "Seal of Corruption". If not working like described then also for potential fix.

they clearly stated that it's working the same way it worked in original, communication is at 100%.

Problem exists only on your end, work on potential fix for that.

Quote:

---

Originally Posted by angrylol

they clearly stated that it's working the same way it worked in original, communication is at 100%.

Problem exists only on your end, work on potential fix for that.

---

Stop being toxic. We are not here for that.
I see problem and want to get fix or clarification.

You already got it, but are refusing to accept it.

Quote:

---

Originally Posted by Obnoxious

You already got it, but are refusing to accept it.

---

I got answer and thanks BlueAo for that. I do not refusing to accect, but trying to give different perspective to consider.

Quote:

---

Originally Posted by Ordojed2

I got answer and thanks BlueAo for that. I do not refusing to accect, but trying to give different perspective to consider.

---

There's nothing to consider, though. It's working as intended the way it is right now. The tooltip being vague and leaving room for interpretation doesn't change that, we have video evidence of how it worked back in 3.3.5. Also, however it might be on Classic isn't relevant, we aren't trying to emulate Classic.