Cure Curse Issue

[DaggerSplicer]

During my guild raids cure curse on name fights do not appear to be working correctly. During the Drels Ma'gor encounter where the curse jumps back and forth off the tank to a random toon every 28secs or so the bot just refuses to cure. I tried to use my hotbar key to cure instead, however, the cancel to cure curse button would kick in overriding the command to cure curse but the curse never triggers. So, is anyone else having this issue. The regular cures are just fine but cure curse just refuses to trigger. I have it set within the priority tab as a cure priority for 1 person with both raid and group triggers as well as checking to see if maybe others were just curing faster than my toon could, so this is not the case before anyone ask. Any advice would be appreciated.

 

[Kannkor]

During my guild raids cure curse on name fights do not appear to be working correctly. During the Drels Ma'gor encounter where the curse jumps back and forth off the tank to a random toon every 28secs or so the bot just refuses to cure. I tried to use my hotbar key to cure instead, however, the cancel to cure curse button would kick in overriding the command to cure curse but the curse never triggers. So, is anyone else having this issue. The regular cures are just fine but cure curse just refuses to trigger. I have it set within the priority tab as a cure priority for 1 person with both raid and group triggers as well as checking to see if maybe others were just curing faster than my toon could, so this is not the case before anyone ask. Any advice would be appreciated.

I suspect this is a fight that has 2 different cure curses. So in a bot situation, it calls out who should be cured and they cure it.

If you wish for the bot to cure all curses, turn raid options off and it will not have any special coding per mob basis.

 

[DaggerSplicer]

I suspect this is a fight that has 2 different cure curses. So in a bot situation, it calls out who should be cured and they cure it.

If you wish for the bot to cure all curses, turn raid options off and it will not have any special coding per mob basis.

You are coorect in your two cures assessment. One is a jump curse, meaning if not cure it wipes the person and triggers a ridewide detrimental that pretty much wipes the raid, while the other one is a player charm that should not be cured. I think the problem is that within the coding its just ignoring the cure calls all together. I am wondering if it's too much to ask for the curses to be identified within the programing as negative cure or positive cure.

 

[Kannkor]

You are coorect in your two cures assessment. One is a jump curse, meaning if not cure it wipes the person and triggers a ridewide detrimental that pretty much wipes the raid, while the other one is a player charm that should not be cured. I think the problem is that within the coding its just ignoring the cure calls all together. I am wondering if it's too much to ask for the curses to be identified within the programing as negative cure or positive cure.

That's not "the problem", that's "the design". When I coded the fight, I don't believe there was a way to tell the curses apart. So Ogrebot just disables cure curses unless someone specifically asks for one (which is coded into the fight for bots).

If you wish to tell me how you can identify someone with the negative or positive cure while it being on a different character, I'm all ears.

 

[DaggerSplicer]

That's not "the problem", that's "the design". When I coded the fight, I don't believe there was a way to tell the curses apart. So Ogrebot just disables cure curses unless someone specifically asks for one (which is coded into the fight for bots).

If you wish to tell me how you can identify someone with the negative or positive cure while it being on a different character, I'm all ears.

Ok! I will give this a shot. The name will cast an ability called: Dark Death, which lands at the same time as Dark Calling because this is the trigger curse that lands after Dark Death gets cured. There seems to be some confusion because both land at the same time. However, Dark Death will hit first once the curse is cured, then Dark calling will land afterwards on someone in the raid randomly some time later. So, having the bot seek out Dark Death prior to Dark Calling would be key. Now, comes identifying the negative and positive cure. I was thinking that both Dark Death and Dark Calling could be ID'd as positive since these two must be cured. However, the negative curse that can't be cured is also called Dark calling as this is the one that if not cured turns into a charm which your won't be able to cured. I may be totally off point here but I gave it my best critical thinking process.

 

[Kannkor]

Ok! I will give this a shot. The name will cast an ability called: Dark Death, which lands at the same time as Dark Calling because this is the trigger curse that lands after Dark Death gets cured. There seems to be some confusion because both land at the same time. However, Dark Death will hit first once the curse is cured, then Dark calling will land afterwards on someone in the raid randomly some time later. So, having the bot seek out Dark Death prior to Dark Calling would be key. Now, comes identifying the negative and positive cure. I was thinking that both Dark Death and Dark Calling could be ID'd as positive since these two must be cured. However, the negative curse that can't be cured is also called Dark calling as this is the one that if not cured turns into a charm which your won't be able to cured. I may be totally off point here but I gave it my best critical thinking process.

uhh.. Not quite what I meant.

Realistically, if there isn't an ACT trigger you can add to see which one is the good one, I'm not going to add in checking to see "which one lands first". If you're running bots, they will ask for a cure, and it will be cured. If you're only running 1 toon, can pause and cure that one curse manually.

The raid support is there to assist with bot-raiding more so than real-raiding.

And you can't see what curse someone has from a different person... Unless there is a trigger (I keep saying ACT trigger because that's what most people use, but it's really unrelated to ACT).

 

[DaggerSplicer]

uhh.. Not quite what I meant.

Realistically, if there isn't an ACT trigger you can add to see which one is the good one, I'm not going to add in checking to see "which one lands first". If you're running bots, they will ask for a cure, and it will be cured. If you're only running 1 toon, can pause and cure that one curse manually.

The raid support is there to assist with bot-raiding more so than real-raiding.

And you can't see what curse someone has from a different person... Unless there is a trigger (I keep saying ACT trigger because that's what most people use, but it's really unrelated to ACT).

I see. The guild was talking about this very thing. Kind of weird that there isn't a trigger. Oh well, if the trigger miraciously gets added then I will be sure to let you know. In the mean time; I will just turn off raid options until such time an Act trigger becomes available. Thanks for your time on this.