Blackguard Broken CL

[In passion, patience]

Description:

A Blackguard is a fully mundane build with access to a singular spell as a class-specific ability, Bull's Strength (+4 str). Normally, the CL of a fully mundane build is 30, and their DC vs dispels 42. I built a Blackguard/Fighter/Warlock and the warlock dip spanned only 3 levels. When I cast my Bull's from the BG ability, the game confused it for a warlock spell and my CL decreased from 30 to 3, making my DC vs dispel 15.

Steps to reproduce:

Make Bg/Ftr/Wa. Cast BG's Bulls. Get dispelled.

Expected result:

DC 42 vs dispel.

Actual result:

DC 15 vs dispel.

Screenshot(s):

Misc Notes:

N/A

Which Server(s)?

PGCC, likely also on Live.

Gaming Platform(s)?

PC

[Iceborn]

Interesting.
Can you test what happens when you try the same without warlock levels?

[In passion, patience]

On a fully mundane BG, the DC remains the same in spite of casting BG's STR.

[Iceborn]

I could not replicate this.
What pact did you take from warlock?
Also, what does the effective dispel resistance readout (rest menu, 5-2-10) say before and after warlock levels?

[In passion, patience]

I'll check in a few moments. Pact was Undying. The CL drop doesn't trigger if you don't cast Bull's or corrupt weapon; it seems to occur after that's done.

[In passion, patience]

Okay, I've done some more testing. I ran two simulations after server reset. Simulation #1 was warding without BG Bulls, and simulation #2 was with BG bulls.

[In passion, patience]

Simulation #1

As you can see, CL is 30 and DC is 42, dip is 3 warlock undying pact.

[In passion, patience]

Simulation #2, that was after casting BG's Bull.

As you can see, the CL drops to 3 and the DC to 15.

Tested this across multiple characters and different CD Keys (had friends make Bg/Wa) to make sure it's not just a corrupted character.

[Iceborn]

I managed to replicate this with corrupt weapon.
Using Bulls never dropped my CL.

Still looking into it.

[Iceborn]

Found the issue.
A fix is in the pipe.

Locking and archiving.
if this persists after you see the changelog go live, do not hesitate to open up a new thread.