EQ2 Bot Issues

[demoante]

So, I've deleted the char xml's quite a few times. And I keep having the same re occuring issues these last couple weeks...

1. After a mob dies, I run off and attack nearest mob in range. Yes this has been an issue for as long as I've been a part of the community but I was able to set the %'s to over 100% and it quit doing this. also I know the input area's dont show letters if u type them on accident, this is why i delete the char.xml file... to start fresh, this now happens after every kill...

2. I know this has also been a long time issue, and it is about not auto attacking names... I've read elsewhere, that some names this bot is auto attacking and some it isnt... I dont presently know how the bot differentuates 1 named from another, but it must be doing so some how.

Any other ideas how to fix this?

 

[Pygar]

1. I need to know what class, what path type, what zones, what group makeup, etc that this is happening on. I'm suspect of classes actively set to do crowd control.

2. I've never been able to reproduce this error, and if I can't reproduce it, I can't fix it. I run my 3-6 man team thru damn near ever zone, instance, raid instance in the game, and I'll wager I've killed 95%+ of the nameds in norath, and I've never not had a bot assist me UNLESS I had ignore red checked and the mob conned red to the bot, or i had ignore epic and the mob was an epic, etc etc. Never has one not assisted when the target type was a valid target based upon the criteria on tab2.

Give me alot more detail on how to recreate both behaviors and I can investigate it, but broad statements about behavior with out exact details on how to reproduce, I can take no action on.

 

[demoante]

This is all ran off the Guardian script.

Also having issue 1 with assassin, but not when i first load the script the first time, after it saves and i shut the eq2bot, when I reload the bot, the issue starts again. I thoroughly checked the XML's and nothing in them has anything out of the ordinary, In the past Ive set the %'s to 800 and look in the xml and see 80w0, which would break that % and just auto attack all day long, however this isnt the issue.

1. After a mob dies, I run off and attack nearest mob in range. Yes this has been an issue for as long as I've been a part of the community but I was able to set the %'s to over 100% and it quit doing this. also I know the input area's dont show letters if u type them on accident, this is why i delete the char.xml file... to start fresh, this now happens after every kill...

1. Any group, setup I make within the last couple weeks has been doing this, be it a duo mentord down to an Assassin, or running through Rok Instances. I eventually had to lower my zone wide mob scan to under 10, to stop running and attacking any mob in site, I dont even attempt to loot (yes loot is on), it just runs off... All Zones do this. What I see exactly is when the mob dies, u can see that he scans a few times for the nearest mob, if i hit escape to drop the target hell pick it again takes about 3 escapes for him to exit out of combat, and return to normal. Sometimes I even have to move him around to stop him from running, cause once he does he runs into the agro mob and theres no avoiding combat. Also during all this when he does end combat, the guardian does not use his mend 50% of the time even though its up, like he was a few weeks ago.

**EDIT... Forgot to mention the above is happening if I leave the auto pull at 80/90% or at 800/900%(way that i had found to stop all auto pulling) He will auto pull until death.
**EDIT... Anothing thing that also happens is if the mob is in range but far enough out that he doesnt run to it, he sticks to it, if u hit escape he will keep re selecting the same mob(Though im sure this is really another issue all together.).

2. I know this has also been a long time issue, and it is about not auto attacking names... I've read elsewhere, that some names this bot is auto attacking and some it isnt... I dont presently know how the bot differentuates 1 named from another, but it must be doing so some how.

2. Group makeup... Guard, Monk, Bruiser, Templar, Coercer, Brigand... Some of the zones are, Unrest, City Writ Bold, Daring, etc... , Obelisk of Soul... Just to name a few. No problems in zones such as Crypt of Agony, and other RoK Instances. The main issue here is, when I turn on autoattack even by myself (cause the guard will not do so through script), the guard quickly exits out of auto attack mode. I keep trying to force him to stay in attack mode, and he quickly exits, over and over.

 

[Pygar]

Well congratulations, you have behaviors no one else is reporting.

I've botted all zones listed, never not engaged any named in any of those zones.

I suspect though your running the bot, but wanting to do manualy pulling? Just uncheck autopull, the bot was fixed to respond to any agro.

The guardian turns on autoattack on the first CA he uses, autoattack is canceled by the game on mob death. There is no code anywhere that turns off autoattack in the guard script or in eq2bot UNLESS you have engage in melee checked on tab2. This option is really just for melee priests, and should not be used on any melee class configuration.

I'm more apt to believe you have custom command and keyboard settings, and when the bot expects to hit backup its hitting autoattack or something of the ilk.

Overloading %'s or other inputs isn't supported, and whatever bizzare behaviors you get from doing so are your own journey, and I'm not going to attempt to support you on that.

 

[Zeek]

I recently updated my guardian script to what is current in SVN and am getting the autoattack issue happening on my guardian now also.

In addition its not just a auto attack issue.. he doesnt seem to do a whole lot as far as CA's go either.

The script works just fine with non NamedNPC types but when it gets to NamedNPC types it really starts to have issues.

I will try and delve into the Guardian script when I get time.

Note: this is not happening on any other of the 4 eq2bot scripts I am running.

Zeek

 

[Smyrk]

Going to add my 2 cents to the guardian issues as well.

I started a new one last night and am experiencing the Autoattack issues as well as a large number of targeting issues where the Guardian as MT will target (seemingly randomly) nearby Nodes or group members at the end of a combat sequence and remain in combat mode until I quit EQ2Bot and restart it. I've also been noticing the odd targeting and combat mode behavior on my 80 Zerk. This is after a full SVN refresh yesterday afternoon.

 

[Pygar]

Again....


There is nothing in guardian.iss that toggles autoattack, as there is nothing for it in any of the class files really.

There is nothing in guardian.iss that differentiates between NPC and NamedNPC.

And again....

No one has been able to give me a mob name and configuration profile to duplicate this behavior with.

 

[Zeek]

General D'Veres or what ever his name is in Jarsath Wastes is the only name I have tried running the bot on and it had the odd behavior.

Zeek

 

[demoante]

"Zygoth the Watcher" Obelisk of Soul...

Bone stock fresh installed eq2bot, with fresh ini. Guardian will not go into combat on this named.

Perhaps I should have started a list a long time ago, was helping a friend with his speak as a dragon quest, and ran across this one. Also, the Templar, and Assassin I also run, did not produce this behavior, and entered combat quickly, as they were written to do.

I completely apretiate your work here man, these small problems with this doesnt effect my actual game play, I just thought id point out odd behavior.

 

[Pygar]

Let me be clear that this behavior isn't class specific.

This is a function of being in the MT role. It could happen with any class.

I'll try to make my way over to OOLS when I have a chance to try this named. I was hoping for something easier to find and generally up more often to test with.

 

[pz]

i saw this behavior on the solo named inside d'morte's.. whatever, in nek. the instance where you knock over the headstones and a name spawns, there's .. 10 or 12 of them maybe? i forget. you were afk when i noticed, and i forgot to mention since. might be a good place to test as they're weak named, lots of time to try stuff while they beat on you.

normal behavior on the rest of the mobs in there, but would not engage on the named.