Temp Fix for solo mage's and eq2bot

[craftmaster32]

I worked up a temporary fix for eq2bot used with a solo mage class and the casting while moving problem. This change may cause problems for other class types. To apply the fix replace your CastSpell function in eq2bot.iss with the one below.



function CastSpell(string spell, int spellid, bool castwhilemoving)
{
press -release ${forward}
press -release ${backward}
wait 30 !${Me.IsMoving}

Me.Ability[${spell}]:Use

wait 100 !${Me.CastingSpell}
return SUCCESS
}

 

[Pygar]

I'm curious under what conditions you were having a problem?

The bot would not cast while moving, but would only move you to avoid additional aggro...

All other known issues of movement while casting had been addressed, so I would like to understand under what conditions there is currently an issue?

 

[craftmaster32]

Casting Issue

The only time I had a problem was when running my whizzy solo in DC mode, he would target something, start to cast, then move closer to the target. He would do this usually twice before standing still long enough to finish the pull spell and start a fight.

Someone else in IRC (Cade I think) told me it was an ongoing issue so I went in and dinked till I found a way to make it stop.

I know your activly working on new stuff for eq2bot and I am pretty sure I had the most recent SVN version when I did this.

Although I am still new to this bot so I may have had things setup wrong as well

 

[Pygar]

The last release by Kayre addressed this issue...

However I believe the bot will still interupt if the pull target paths outside the pull range.

While the changes to eq2 allow the spell to complete, there are justified reasons why we don't do so in the bot.

Basically if the mob leaves the pull range, in order to prevent adds, etc, the bot flushes the pull data rescans, finds the best target, and starts pull again. Often this is the same mob that pathed out, but in tightly populated areas, its another mob.

I am not directly addressing the issue your reporting in the next release, however I am significantly changing the logic it currently uses to select the pull target and how movement before and after the pull cast works. You might see some lessoning of the issue reported, but the behavior I described will continue to be possible.

 

[craftmaster32]

Makes sense to me, I am not sure if that was the problem I was having or not, I did update to your newest experimental version today and its running great.

Many thanks for the work your putting into this.

 

[Pygar]

I did some more testing with a solo caster in DC mode, and it could be better.


I'll update experimental in the next day or so with some tweaking for this. Works flawlessly on pulls in auto hunt, just need some refinements in DC.

Also seems to miss more loot in DC...