[Update] XenoBot Apophis v14.7.6.656 [10.50 & Apophis Global Release]

[Syntax]

Both lure modes are for all the lvl's, not just high lvl's. its just that X amount of monsters seems more efficient then point A to point B. anyways, its up to darkstar. but I just think since we're trying to put the bot to a new level, and luring is quite a big part of tibia, and there is load of lvl 200-250 (and also 300-400+) this shouldnt be left out just because its currently possible.

Wut. I didnt mean player levels, lol.

[Fleet]

Also noticed this "bug". When the monster stands diagonally 4sqm away the shooter wont shoot it with Exori San, even if it is said to shoot at 4sqm range.
It does shoot it when it's straight from the monster, but I think the shooter thinks it's farther away when the monsters steps another step diagonally.

Picture, when the monster is clearly still 4 sqm away, but the bot wont shoot it with any spell, just arrows (when the monster was 1 sqm north it did shoot spells):

Noticed XenoSuit updated today, but this is still happening.
Anyone else? Kinda annoying little bug as the monsters tend to stay in the diagonal corner.

@DarkstaR

[Koksik22]

How long are the clients running before this happens? How many clients must you run before it starts happening?

first time after 2hours of botting, second like 8hours, its depends how many mc i got opened, if i got 4-5 its can happen like only 1 time in 3-4days. but if i bot more mc risk grow up then i will gonna have debug.

[DarkstaR]

first time after 2hours of botting, second like 8hours, its depends how many mc i got opened, if i got 4-5 its can happen like only 1 time in 3-4days. but if i bot more mc risk grow up then i will gonna have debug.

That helps a lot, thanks. I'll keep digging into this.

[Aristeus]

I've also been experiencing debugs. So far it's only happened on my mage while using the same script (not sure if it has any relevance). It think it usually occurs about an hour after I start botting. Not sure if the amount of clients I have open matters since it just happened and i was only running one client.

[DarkstaR]

I've also been experiencing debugs. So far it's only happened on my mage while using the same script (not sure if it has any relevance). It think it usually occurs about an hour after I start botting. Not sure if the amount of clients I have open matters since it just happened and i was only running one client.

Are you sure they are debugs and not freezes? I don't have debug reports logged for you.

[Aristeus]

Are you sure they are debugs and not freezes? I don't have debug reports logged for you.

I'm not sure tbh, haven't been paying that much attention to the error message. All I know is that it recently started and has only happened a couple of times. What happens is that the client crashes which usually results in me dying, and when I restart tibia the 'error report' window pops up.

This also appears in the Xenobot log:

Tibia Debug detected...
{
}
Tibia Debug interception failed! 

I'll try and get a screen of the debug message if it happens again.

[DarkstaR]

Seems like XenoBot has no clue how to read the debug message for some reason. Interesting.

Normal or preview?

[Aristeus]

Seems like XenoBot has no clue how to read the debug message for some reason. Interesting.

Normal or preview?

Normal.

[Koksik22]

That helps a lot, thanks. I'll keep digging into this.

today only 1 debug after 8 hours and its write something else.