[Update] XenoBot v2.7.0 [9.63]

[diofeher]

Tibia updated in the middle of a huge update on my end. The update was still a week premature which is why we're seeing these problems. I can't help it when Tibia chokes an update out of me when the bot isn't ready for one.

That's why you should be using version control with branches

[DarkstaR]

That's why you should be using version control with branches

I am using Mercurial but didn't think to branch off as I wasn't expecting an update any time soon, haha. Also, I did have to add/change quite a few constants and modify a lot of the same files, so it would have been merge HELL.

[sirmate]

Some items seems to be considered as walkable since this update (ex. some borders on this roof).

[DarkstaR]

Some items seems to be considered as walkable since this update (ex. some borders on this roof).

Perfect. I'll look into it, thanks.

[Kingdom]

@DarkstaR

If a scarab dies and a larva dies on same spot, then the bot just stands there forever because it can't reach the loot, and i fully understand thats what you updated, but would be cool with a option "Ignore loot if not reachable"?

[DarkstaR]

@DarkstaR

If a scarab dies and a larva dies on same spot, then the bot just stands there forever because it can't reach the loot, and i fully understand thats what you updated, but would be cool with a option "Ignore loot if not reachable"?

I actually did not change anything having to do with this. In the past did it do this? Nothing I changed should effect this.

[sirmate]

Found ID's for them: 995-999 and 1004-1005.

EDIT:
After adding those ID's into blocking section in Items.xml file I ran into such situation (those borders seems to be walkable only when some walkable item is below it):

[Koksik22]

then xeno be update or need new scripts? becose i dont understund that.

[Mega]

working beautifully, no problems what so ever with waypoints.

[Koksik22]

working suck on my perfect script for 300k. perfect becose after uptade working great