[Update] XenoBot Apophis 14.5.22 [10.38 - 10.41, Preview Client 10.41]

Quote:

---

Originally Posted by DarkstaR

Thank you so much for this report, I actually fixed a critical bug (that has existed for a long time!) because of it. About 50% of my spells had the wrong ID's, so cooldowns were being improperly recognized. The fix will be released soon.

@All
Along with the fix mentioned above, we're getting many optimizations, some additions to the shooter, and lure waypoints very soon :)

---

This release is really needed.... and I love to help! :)

Im not to bothered by it but browse field doesnt seem to work very well. Iv seen it use browse field what appears to be randomly and not use browse field when creatures die on the same space. One time I saw it use browse field on a corpse I wasnt the owner of, it sat at the corpse and waited until the 10 seconds was up before moving on.

Quote:

---

Originally Posted by soul4soul

Im not to bothered by it but browse field doesnt seem to work very well. Iv seen it use browse field what appears to be randomly and not use browse field when creatures die on the same space. One time I saw it use browse field on a corpse I wasnt the owner of, it sat at the corpse and waited until the 10 seconds was up before moving on.

---

yea that is weird, unless you did damage to it? then it might try it

Quote:

---

Originally Posted by Kamoblindside77

yea that is weird, unless you did damage to it? then it might try it

---

Yup i did do damage to it so I know the bot will try to loot it. What is support to happen is the bot tries to loot the corpse realize it cant and continue on. When it used browse field it tried to loot the corpse and didnt move on until it was able to open the corpse.

If you read the thread, you would see that browse field issues are well known. I fixed them on Monday, but I'm still doing testing on a lot of things. They'll come in the next update.

@DarkstaR

Another Debug today. Same as first time, on a label right after a one-liner.

It's an issue with your script, though I'm not sure what. You're either eating up memory or passing some invalid parameters. Can you share the code?

Quote:

---

Originally Posted by DarkstaR

It's an issue with your script, though I'm not sure what. You're either eating up memory or passing some invalid parameters. Can you share the code?

---

Check my old thread

Same script.

It's not the same bug. This seems to be a bug with the script associated with the label.

Is it possible to make so it reconnect after death?