eq2bot targeting and running in dungeon crawl mode?

[milamber]

Noticed that in dungeon crawl mode when you are done with one encounter and have a mob within range it targets the mob then starts running straight forward and tries to cast at the same time until you're out of range. Then it will stop and get a new target and pull normally.

Is there anything I'm doing wrong here?
The Keyboard Configuration seems right..

This was noticed in antonica on a conjuror.

 

[draken12685]

I have been having the same thing happen to me... I cant seem to get dungeon or camp bots to run properly. I have tried the eq2pather combat with auto and without, i have made start and finish points, tried starting /run eq2 start finish, setting short distances... am I doing something wrong?

My scenario is as this...

run eq2pather combat auto

Box pops up asking for a name and i type Start

I run strait about 15 yards and then press F2 and name it Finish.

F3 to save.

I then run eq2bot start finish

I select dungeon crawl and set my automatic pull to my Abominable Anger spell with pull range 20.

The thing somtimes just goes haywire, sometimes runs at mobs and keeps runnign, sometimes casts while running... not sure where to go from here.

- Draken

 

[Pygar]

There has been a known issue regarding start and finish points too near each other.

I use dungeon crawl successfully in the croc caves in SS. WIth a start point near the cave opening, and a finish point in the very back. I can then set the bot to use dungeon crawl and it works just fine.

I occasionally get too many roamers that add an the wrong time for my 44 defiler to handle it, but thats rare.

I do have it set to wait for power before engaging the next target, and that works fine.


I've also tested this with conjurer, warden (on older eq2bot), and swash.

 

[Redstrike]

Was there ever any other feedback on this? My conj does the same thing except something to add. On the pull it will target closest in DC mode and start to cast my pull spell. After the spell hits it loses target, runs a few feet, re-targets, runs forward and tries to cast at the same time...then goes through combat routine as expected.

 

[Pygar]

I thought these issues had been fixed in a recent release of eq2bot.


I'm currently in the testing phase of the next relesae that uses a revamped pull function. I don't use dungeon crawl much, but I will test with it before releasing.