[Update] XenoBot Binary v15.11.28.1193 [Protocol 10.90]

Quote:

---

Originally Posted by Joshwa534

JXScripts are long gone, same for the site, the host, everything.

---

Are you looking to do lizard city for xenobot? I can be a tester for it

my poor dollers spent lol xD

I'm opening my xeno and than ,,Attempting to reach xenobot server, please wait" and ,, failded, exiting "
whats wrong ?

Quote:

---

Originally Posted by padj

Are you looking to do lizard city for xenobot? I can be a tester for it

---

Once we have Zao completed as a dynamic town, yep.

Just finished Yalahar and have Fenrock Dragon Lords (all vocations) & Yalahar Grims (all vocations) being tested right now.
If you're looking to test scripts such as those (before public release), join our Slack.

Edit: nvm

100% of the time, is good every time!

Darkstar for President<3

The new changes to the targeting are causing me to take quite a bit more damage then before. Especially in spawns where I can have 3-4 targets on me at once.

The delay in the targeting is also allowing mobs that escape at low health to get away more easily.

It also seems to occasionally cause the bot to stop and loot if the character happens to walk by a corpse and pauses at the same time. (Not 100% sure of this, need to test a bit more.)

I honestly don't think the changes are very useful, even for low leveled paladins. The delay is simply too long, and it gets worse the faster the mobs you're fighting are (why it's not at all good for high level paladins).

I can see how this might be good for mages who use Aoe runes, because it can often take 2-3 attempts before a rune cast actually goes off. However, I don't think it's an ideal default setting. I'd suggest making this a specific target setting, for those who might want to use it.

These are just my observations from running a hunting script on a 240 paladin.

Will be botting my EK instead, tonight. Feels a bit too dangerous for the paladin and mage.

Can you add... in walkers advenced Waypoints...(deposit item in depot(1,2,3,4,5,6,7,8,... ?) cuz he think... depot1 is first bp dp, depot2 is second bp in dp:P and more...

Quote:

---

Originally Posted by Aristeus

The new changes to the targeting are causing me to take quite a bit more damage then before. Especially in spawns where I can have 3-4 targets on me at once.

The delay in the targeting is also allowing mobs that escape at low health to get away more easily.

It also seems to occasionally cause the bot to stop and loot if the character happens to walk by a corpse and pauses at the same time. (Not 100% sure of this, need to test a bit more.)

I honestly don't think the changes are very useful, even for low leveled paladins. The delay is simply too long, and it gets worse the faster the mobs you're fighting are (why it's not at all good for high level paladins).

I can see how this might be good for mages who use Aoe runes, because it can often take 2-3 attempts before a rune cast actually goes off. However, I don't think it's an ideal default setting. I'd suggest making this a specific target setting, for those who might want to use it.

These are just my observations from running a hunting script on a 240 paladin.

Will be botting my EK instead, tonight. Feels a bit too dangerous for the paladin and mage.

---

I'll make a few timing changes to hopefully reconcile this issue. If you're using long range weapons (like 6 or 7), you should consider switching to 3 SQM Dynamic lure. It is sooo much better anyways.