[Update] XenoBot v2.8.7

[kubax36]

yeah, its still falling down to holes ;/

[B0tt3r]

yeah, its still falling down to holes ;/

+2.......

[sirmate]

@DarkstaR
well, the version 2.8.5 work better than the new one.
cuz the lua bug so much than the old version mentioned.

i will give a an example:
if i use a script that destroy forniture (for avoid the trap) and if im going to refill, at the momment that i arrive to the dp mine client stop working (the .lua stop working)

Try using "TIMER_TICK" event instead "while" loop. You can find example in v2.5.1 thread.

[Mus]

how does the minimizing backpack and equipment work?

[Pepsi_901]

yup, still falling down/going up at ramps... Not as much as before this update, but it's still a lot and really annoying since I can't bot at nights cause of it

[DarkstaR]

@People still falling down shit:
The code is EXACTLY how it was before the problem occurred. You're either not installing the newer version (try clearing your cache) or something else is happening. But the code is EXACTLY how it was before, so there's no reason it's acting different.

[Pepsi_901]

The thing is that it's always been doing it, more or less. Atleast since I started using the bot (7-8(?) months ago)
Maybe it's cause of lagg or something else, but it still does it.

[jalleballe]

For me it happends when the bot is targetting a monster and then walks into stairs sometimes for some odd reason, and sometimes it dosent.

[kbzin]

@People still falling down shit:
The code is EXACTLY how it was before the problem occurred. You're either not installing the newer version (try clearing your cache) or something else is happening. But the code is EXACTLY how it was before, so there's no reason it's acting different.

I couldn't bot this night because of this problem. I didn't change anything in the script that i'm using and i tried to re-install it twice. Anyway when i arrive home today i'm going to uninstall it, clean cache, download and install it again. I'll post feedback here later.

Thanks.

[PunktG]

I'll check it out. May just add a Client.CloseDialog() function that you can use.

got this problem on only 1 world for sure some ppl do this
waiting for new fuction