Recent content by rlane187

MQ2Melee turns off melee on cleric even if I turn it on manually. If I unload MQ2Melee, auto-attack does not turn off. MQ2Melee INI is below. Any help would be much appreciated. [MQ2Melee] bash=1 enrage=1 facing=1 infuriate=1 plugin=1 resume=75 stickmode=1 stickrange=75...

I enabled looting on my Rogue and it was throwing an error and breaking the script. The error was thrown by the following code on line 217 of modloot.inc: /if (${LMFollow}) { An error is being thrown because LMFollow is defined above it inside a nested /if statement starting on line 181. The...

This does not initialize properly on Emu. Get the following error on startup: No such 'int' member 'List' modbot.inc@3090 (AADump):/if (${Window[AAWindow].Child[List${b}].List[${a}].Length}) { modbot.inc@2852 (AAInit(IniSection)): /call AADump modbot.mac@61 (Main(INI)): /call AAInit...

Since the change to Attrib 148 in the spell info, MQ2Netbots buff stacking checks are broken. For example, the plugin thinks that the cleric Aegolism line does not stack with any Shielding line (shaman, int caster, etc.).

According to NetBots, the Conviction line of spells does not stack with Shielding line spells (Shaman, Int Caster, Cleric Armor Line, etc.). I tested the return values using /echo of the ${NetBots[name].Stacks[id]} method. Consequently, what buffs my toons have depend entirely on which toons...

I do not see that setting in either the Modbot INI or the Modbot wiki. There is not even a [General] section in the INI. Perhaps this for a different bot?

Have the bot interrupt heals if the target gets healed by something else before spell completion.

Finally got it working. It was because /next a was able to be called in more than one place. Changes were made to the /for loops to make them like this: /for a 1 to ${ADMobMax} /if (!${NearestSpawn[${a},pet].ID}) /goto :skip_a /for b 1 to ${ADMobMax} /if (!${ADMobList[${b}]}) /goto...

I have set up the bot to pull. My INI for the pull section looks like this: [AdvPull] APCheckTime=0 APRadius=40 APMobMax=3 APScript=pull_script APPath=pull_path APRetPath= APBefore= APAfter= APAnnounce=/gsay Incoming -[ %t ]- APRetries=1 While the bot is looking for targets, it crashes at...

Is there a range check for buffs? I play on a progression server and I am running version 4.32 of the bot. If I have someone outside of buff range, the toon just casts the buff over and over again. If there is not a range check for buffs, can we look into adding one?

It looks like any abilities that are /autoskill eligible cannot be activated. Across all my melee, nothing eligible for /autoskill will activate even when pressed manually. Other abilities work fine.

RESOLVED One of my toons had a custom announcement for ACAnnounce in the Melee section: ACAnnounce=/bc ATTACKING < %T > It was the word ATTACKING that was driving all of the bots to enter melee. I deleted that custom announcement and no longer have any issues. Sorry for the false alarm.

The following code from modbot.inc, line 345 is what is making them attack before ACAssistPCt=95: /if (${MsgText.Left[7].Find[attack]}) { /bc Setting - DoMelee TRUE & Attacking /varset ACState 100 /varset DoMelee TRUE /if (!${MsgText.Arg[2].Length}) /varset MsgText...

Still happening after update. UPDATE: Sometimes, it is working correctly and what I see in EQBC from the toons is: Meleeing: -[ MOB NAME ]- When they attack before the ACAssistPct=95, I see this in EQBC: Setting - Domelee TRUE & Attacking Meleeing: -[ MOB NAME ]-

My toons assist as soon as the mob is within leash range, even when the mob is at 100% health. Attached is an INI for my rogue. I have changed the tank and puller name, but I assure you that they are set correctly. Any ideas? [Settings] DoMelee=FALSE DoHeals=TRUE DoBuffs=FALSE DoDebuffs=FALSE...