Target drop fail and continuously targets the monster

[rechellec]

Hello Guys,

I guess this bug, at ve_fild03. Some monsters can't attack. My bot attack magmaring, then the another magmaring cant attack because that monster is a bug. Other bot dont see it, its only me who saw it. Im using xkore 1 thats why i know.

So then, i try to reconnect and the bug monster is already gone.

I hope someone could help me on how to resolve this problem. I guess i just reconnect if i the bot cant attack the bug monster, but how?

[EternalHarvest]

Sounds like a known problem which occurs even in the original client.

Doesn't it drop the nonexisting target after a while due to ai_attack_giveup timeout?

[survivorsavior]

I believe this happened before, but there were no solutions to it because the original client also had this problem.
When a monster is pushed back and killed, the monster is sometimes recognized by the bot as an "undead but over damaged" monster, this causes the bot to continuously targeting the monster. Even if you drop the monster, the bot will still go back to the position where the "undead monster" is located, and stands there tempting to attack until the bot relogs, changes maps, or uses a fly wing.

Are there any other possible ways to solve this bug instead of using fly wings and relogs?
The server I play on requires a phone call to unlock the login sequence, and fly wings are custom items on that server.

[rechellec]

waiting for someone who can help hehe
We had the same problem.

[EternalHarvest]

Problem with "undead" monsters occurs even with the original client.

We can only fix target dropping and maybe remove monsters which are out of client sight.

[Pornograffitti]

so, is the target dropping fixed? cause mine still waits 12 sec before dropping the target and and doesn't change target to the closes aggressive. my conf's attack change target is already set to 1, and timeout.txt's drop target is 3 secs

[locke]

I solve this by not using overbrand on mob that can be knockback

[mooleh659]

You can also resolve this if you relog when you drop a monster using a macro.

[ptcarino]

simple macro that can solve your problem.

Code: Select all

automacro relog {
console /Can't reach or damage target/
timeout 10
call {
do relog
stop
}
}