Dispell priority?

Offended · Post by **Offended** » Sat Apr 17, 2021 1:44 am

Can we make Curse a larger priority over light when dispelling yourself please?

Thank you.

Offended · Post by **Offended** » Tue Apr 20, 2021 9:10 pm

Ok, reason being is let's say you can barely see in the dark.

You go down a trap, get cursed, now you can not see.

You cast light so you can see.

Stun to stun your enemy.

Then dispell to dispell the curse but you remove light.

Causing you to become cursed and stunned.

That's the problem with having light a priority over curse.

Post by **Lordlava** » Wed Apr 21, 2021 3:41 pm

Dispel always dispels Stun first.

Then it works differently if you are dispelling an enemy or a friend.
Self = Friend.

Dispelling a friend looks for the first spell of the following list that it can find in the spell[] data array and then tries to dispel it. Note that it is in the order stored in the spell array which normally corresponds to the order cast. It is not in the order listed below.
Light
Wimpy (Guardian Angel)
Stun
Curse
Warcry (Curse)
Warcry2 (Stun)
Weaken (C2)
Poison
Blind
Corrode

I am not sure from your example below what sequence spells were cast in or what slots had expired or were empty.
If you get cursed (spell[0]) and then you cast light (spell[1]) then dispel should dispel spell[0] before spell[1].

Marky · Post by **Marky** » Wed Apr 21, 2021 4:23 pm

You would normally want to dispel the bad things first: stun, curse, war-curse and such. Light shouldn't be considered a bad thing

I think before Light wasn't dispellable. So you would just dispel the curse, as people would want.
Now Light has been added to the dispel-a-friend.

So what happens now: you spell up, cast light, walk into a room, get cursed. Then you get dispelled. You are still cursed, and don't see your enemy anymore and can't parry. And...you're still cursed.
No bueno

Post by **LazyWarrior** » Thu Apr 22, 2021 7:19 am

Lordlava wrote: If you get cursed (spell[0]) and then you cast light (spell[1]) then dispel should dispel spell[0] before spell[1].

This is broken if this is how its supposed to work. I was cursed then light cast on me 2nd(with no other recent buffs/debuffs so spell order should be curse[0] light[1] and it dispelled light first when i tried to dispel myself.
Light appears to be the only spell that ignores cast order
Also you cant even dispel wimpy/GA, it says I'm unspelled, but that doesn't really matter.

Zraaq · Post by **Zraaq** » Fri Apr 23, 2021 8:33 pm

I'm wondering if the light block choice for others casting it on you is somehow having an effect...

Z

Offended · Post by **Offended** » Wed May 05, 2021 10:39 pm

This is still broken.

If light is before curse in your spell up, light is dispelled prior to curse.

Curse should take priority over any good spell regardless of it's order.

xclusive · Post by **xclusive** » Thu May 06, 2021 7:10 am

Light also dispells before blind. Tested on Mem Lane.

Post by **Drink** » Thu May 06, 2021 8:11 am

Lol
Yeah had this in ML

took of light after i got cursed.
was like.... gpots next plz no

risked it and it took off curse next

So think its just light is too high prio

Post by **Lordlava** » Thu May 06, 2021 2:52 pm

Dispel was not broken - just different to how you wanted it to work.

However, it should now move light to 2nd priority of dispel sequence.

Offended · Post by **Offended** » Tue May 18, 2021 12:54 am

Thank you for fixing it.