BUG: (Fix) /alert list IDs

A forum for feature requests/discussions and user submitted patches that improve MQ2

Moderator: MacroQuest Developers

Valerian
a grimling bloodguard
a grimling bloodguard
Posts: 709
Joined: Sun Jul 28, 2002 3:29 am

BUG: (Fix) /alert list IDs

Post by Valerian » Sat Oct 11, 2003 6:46 pm

Code: Select all

[color=red]PALERT GetAlert(DWORD Id) {
    PALERTLIST pAlertList = gpAlertList;
    for (;pAlertList;pAlertList=pAlertList->pNext) {
        [/color]if (pAlertList->Id==Id) return (pAlertList->pAlert);[color=red]
    }
    return NULL;
}[/color]

Falco72
a hill giant
a hill giant
Posts: 215
Joined: Fri Sep 26, 2003 3:24 am

Post by Falco72 » Sun Oct 12, 2003 8:32 am

Beg your pardon Valerian, but after I make the change you posted and recompiled MQ from a new installation, I cant get any new result. As before, I can make an alert only using the name of the spawn (ie an orc pawn), but not using the "true" name of the spawn (ie an_orc_pawn00). What mistake am I making? Thank you.

P.S. I am stressing this point because I am using alert in a macro that pass the ids of the mobs around the char to my bot(s). In this case, if the mobs have the same name (ie an orc pawn) only the first id is passed to the bot. Else using the true name (ie an_orc_pawn00) ALL the mobs' id are passed also if they have the same name.

Valerian
a grimling bloodguard
a grimling bloodguard
Posts: 709
Joined: Sun Jul 28, 2002 3:29 am

Post by Valerian » Sun Oct 12, 2003 4:43 pm

I'm sorry, I wasn't clear in my post... the bug was that you could only have 1 alert list (the first one you made) and trying to add alerts to any other list would put them on the first one you made.

This doesn't deal with uncleaned names or ids

Falco72
a hill giant
a hill giant
Posts: 215
Joined: Fri Sep 26, 2003 3:24 am

Post by Falco72 » Sun Oct 12, 2003 5:05 pm

My fault. Thank you Valerian for the fast answer.

zedisdeadbaby
a ghoul
a ghoul
Posts: 83
Joined: Sun Nov 03, 2002 4:24 pm

Post by zedisdeadbaby » Sat Nov 08, 2003 3:48 am

this bug is back in the CVS source code

bump :!: