eq2harvest / eq2bot

[SuperNoob]

eq2harvest / eq2bot using the versions from May 4th on svn I ran into some problems running the two of them together. It seemed that if the toon was moving from a point to another point and drew aggro, the stuck state routines would fire instead of letting the eq2bot script handle combat. eq2bot tried, but the stuck routines from harvest kept trying to move around the "obstruction" caused by the mobs smacking me.

I am looking into it, but if someone has any ideas I would appreciate them.

-SN

 

[Pygar]

Interesting, I'll check it.

 

[untitled]

Hey Super,

I had the exact same problem and found that if I add:
Turbo 500 to EQ2harvest.iss or what ever is in EQbot.iss
in the main function it works for a while - still testing but it looks good so far. Will let everyone know the results here.

Excellent job on this Pygar - btw

 

[Cr4zyb4rd]

The problem was caused by moveto.iss not properly detecting aggro, which should be fixed in recent versions. (Sorry for the lack of follow-up)

If you're still having the issue, either moveto.iss needs more work or it's not "the same" problem. (No offense, but after years of troubleshooting I've found that most people claiming to have "the same" problem without an exact description are having a related problem or one with similar symptoms but different triggers)

At any rate, the turbo command wouldn't have worked as a fix for SN's problem (the moveto thing) and if it partly resolves your issue I strongly suspect it's just dumb-luck and hiding some sort of race condition that needs to be resolved. TBH eq2bot really shouldn't be setting it, let alone to such a ridiculously high value.

 

[Pygar]

I agree with Crazy, I just haven't had time to test Turbo 100 to see if it has any affect on the performance. Even that value seems hight to me.

 

[untitled]

You are both correct it didn't work. It did however prolong the aggro detection problem between nodes before it started acting strange. The problem I am having is it seems to want to get to within 0-1 distance of the current target, so it basically dances around miscasting spells. EQ2harvest says node found and then says, stuck ending script.


Will try the new moveto.iss (if its been changed yet) or come up with a homegrown fix.

On a side note to prevent getting yelled at from other players for harvesting their node and came up with a fix - after the harvest tool swap and before the actual harvest add;

if ${Actor[PC,range,15](exists)}
{
Harvest:SetBadNode[${NodeID}]
announce "polite harvesting mode - Activate"
return
}

It might set more then a few desirable nodes to bad but at least you wont get reported. It works great.