EQ2Bot No Attack

[p0wers]

Since the patch it appears that none of my bots want to auto attack or cast any offensive spells, anyone else having this issue ?

 

[zipyzen]

Same here. Eq2bot doesn't want to bot anymore. I have noticed other things as well, like Craft crashing after it starts the reaction arts process.

 

[Kannkor]

I don't know how eq2bot is acquiring it's kill target data, but if it's using ConColors as one of the factors, they aren't working at the moment (I put a bug report in for Ama).

Again, I don't know if that is the issue causing it, but it's an issue for some things regarding kill targets.

 

[Marcus]

If its con colors, would clearing all the Ignores fix it? (Ignore tab under EQ2 bot options)
Tried it.. nope..

 

[badshark]

no i dont have any clicked and was still a no go

 

[Wescondley]

Is anyone looking into this yet? Everything seems to be loading up, and on the surface, everything looks good, but no one in the group does anything other than follow.

 

[eddie43302]

Yes my group only toons that are engaging and kill are my illy,inquis, other toons are not casting on the mob.. they will buff the group but will not cast anything.. defiler,wizard,troub will not cast at all.

 

[eddie43302]

Could it be this problem http://forums.station.sony.com/eq2/posts/list.m?topic_id=488509 the useability or w/e cause dont most bots use that to cast?

 

[schulerta]

Warden bot seems to not understand when the party is in combat. Has to be hit and then and only then will it do the "Keep Group HoT up" algorithm. That will also cajole it into Curing. It will not cast a single aggressive spell however no matter what.

 

[eddie43302]

Any fix coming ?

 

[Amadeus]

Is this still an issue? Or, did my ISXEQ2 patch today fix this?

If it is, then it might take a couple days until someone has time to test and edit eq2bot (since it's most likely an eq2bot.iss issue, not an ISXEQ2 issue.)

 

[Kannkor]

Is this still an issue? Or, did my ISXEQ2 patch today fix this?

If it is, then it might take a couple days until someone has time to test and edit eq2bot (since it's most likely an eq2bot.iss issue, not an ISXEQ2 issue.)

While not a lot of help, Ogrebot doesn't/never had this issue, so I suspect it's differences in how we acquire valid kill targets.

 

[v01d]

Target delay...

There appears to be a delay between targeting and target exists becoming true where there wasn't previously. This may be the root of the issue, but I neither use nor maintain eq2bot. I'm just sharing what I have seen in my own scripts...

Here is an example....

function fast_target()
{
	if !${Target(exists)}
	{
		if ${Actor[npc].Target.ID(exists)}
		{
			if ${Actor[npc].Target.ID} == ${Me.ID} || ${Actor[npc].Target.ID} == ${Me.ToActor.Pet.ID}
			{
				echo Fast Targeting (ID:${Actor[npc].ID} Hlth:${Actor[npc].Health}%)
				Actor[npc]:DoTarget
				wait 25 ${Target(exists)}
				echo Target Exists = ${Target(exists)}
			}
		}
	}
}

The line...


wait 25 ${Target(exists)}


Had to be added after GU58 because ${Target(exists)} was returning false.


I hope this is helpful...

v01d

 

[Pygar]

I've been working 16+ hour days at work and not had time to investigate.

Is this still an issue?

 

[wolfppo]

I think it is I cant confirm it atm though.

 

[Amadeus]

Everyone that typically works on eq2bot is working very long hours lately and will need a few days to have time to work on it.

So, if you're hooked on eq2bot you'll either have to just wait it out or else start learning lavishscript. Either way, I'm sure one of us will have it fixed before the end of the weekend.

No reason to post any more here in this thread unless you have additional data that might be useful.

 

[Pygar]

All I have to add is, hang out on IRC if your willing to assist me in debugging the issue remotely.

 

[Pygar]

Void,

My targets have always looked like this:
Actor[${TargetID}]oTarget
wait 10 ${Target.ID}==${TargetID}

Are you saying previously you had no wait? Or that you now need wait 25 values to be reliable?

This has always been a function of client lag and not really anything else, as it doesn't need to check with the server before changing your target.

All:

I posted a debug eq2bot today that will spam reasons why target checks return false. Someone might be able to play with it and report back on what is returning false falses ')

 

[eddie43302]

yea works fine for me in other instances so far.. where i was having issues it seems was the new zone first named could be fixed ill try the zone again later.. seems all toons was casting but wizard..

 

[v01d]

Pygar,

It's definitely more robust to have a wait and I probably should have had one all along but didn't. It worked pretty reliably for me in the past without the wait where as it doesn't today. The code that follows expects ${Target(exists)} to be TRUE if a DoTarget is performed, and is now malfunctioning without a wait. The key take away is that I'm seeing ${Target(exists)} taking longer to assert than it did in the past. I have no idea if it's applicable to eq2bot, but I figure it never hurts to share.

v01d

 

[eddie43302]

seems to be working fine now no problems.