[Update] XenoBot v3.0.5

This update fixes some critical bugs, improves behavior for many functions, and adds the Map.MoveItem() and Self.UseBed() functions to the Scripter.

Changelog:

Code:

---

v3.0.5
Added the "Use on Self" option to the Looter.
Added Map.MoveItem() to the Scripter.
        Parameters
                xfrom: source x coordinate of the item.
                yfrom: source y coordinate of the item.
                xto: destination x coordinate of the item.
                yto: destination y coordinate of the item.
                count: (Optional) If the item is stackable, the amount to move (defaults to all).
        Returns: 1 if success, 0 if failure.
        Notes: Can only move items on the same floor.
        Usage: Map.MoveItem(source.x, source.y, dest.x, dest.y, 100)
Added Self.UseBed() to the Scripter.
        Parameters
                x, y, z: the location of the bed.
                mode: the offline training mode to select. Acceptable inputs are:
                        TRAINING_SWORD
                        TRAINING_AXE
                        TRAINING_CLUB
                        TRAINING_DIST
                        TRAINING_MAGIC
        Returns: 1 if success, 0 if failure.
        Usage: Self.UseBed(x, y, z, TRAINING_SWORD)
Fixed a bug which cause the Replace/Skip Script loading dialog to appear blank and crash upon interation.
Fixed a bug which made people with non-ASCII characters in their "My Documents" path unable to use the bot. The bot will now default to C:noBot\ in these cases.
Removed "Ectoplasmic Sushi" from the list of edible items.
Modified the Replace/Skip Script loading dialog, it is now wider.
Modified the way XenoBot resets data. Instead of resetting upon log out, the following data points will only reset if you switch characters:
        Most Taken Damage
        Most Dealt Damage
        Last Target Name (Hold target will not obey here)
        Last Exivad Name
        Last Followed Name
        Killed Creature Counts
        Recent Loot
Improved Scripter Modules and TIMER_TICK events. These events will no longer pile up in queue, making wait() safe to use.
Improved Hold Target. It will now use intelligent behavior to prevent unintended white skulls.
        If the target did not have a skull when manually attacked, Hold Target will have no discretion.
        If the target did have a skull when manually attacked, Hold Target will stop attacking if the target enters an unjustifiable kill state.
Improved Targeting. It is a bit easier on CPU, especially when Hold Target is enabled.

---

For download and operation instructions, refer back to this thread:
http://forums.xenobot.net/showthread.php?19

Very nice! Gonna test it soon. Thanks DarkstaR.

Thanks. Downloading.

Tibian

good job mate

Awesome :D

GJ u are the best your bot are the best but still there is no person or possibility to do a safe script on souleaters (in pvp world ) in my best place :/

great job!

Awesome update I must say!

Thanks DARKY :]

Thanks!

Daah we want the screenshot() function!!!!!1111oneone

Oh wait, we already have that.

Thanks brah

The function MoveItem.
Does this mean we can make a better (faster) auto trasher now?
Or more as in, if a dp is trashed the bot will untrash it?
& Can we make a Dp trasher with it aswell?

Good job!

Nice update!

nice update, but... When u will make advanced alarms? :D

Nice, thank you.

Quote:

---

Originally Posted by kubax36

nice update, but... When u will make advanced alarms? :D

---

They already exist through using alert() in the scripter.

Quote:

---

Originally Posted by Spectrus

They already exist through using alert() in the scripter.

---

i mean something like TurnPlayerOnScreenAlarm(false/true) on label and White list in Player on screen alarm. Also it should be possible to turn off Screenshoot option becouse its funny when i find 10 LOWHEALTH screenshoots of my 12 druid on larvas :D

I just downloaded the update, and im getting this error message
e06: error in WinHttpReceiveResponse()!
I have no clue what's wrong, I would really appreciate some help :)

Quote:

---

Originally Posted by claesse

I just downloaded the update, and im getting this error message
e06: error in WinHttpReceiveResponse()!
I have no clue what's wrong, I would really appreciate some help :)

---

All of the network code is exactly the same as before. If you're getting this, something on your computer is not allowing the new version to connect.

thank's alot.

thank you sir!

Awesome!
That MoveItem will sure be useful and the data reset will help keep track of tasks easier after server save :) great job thanks!

Nice Job :)

Also, @The guy who asked about Souleater script (CBF going back to tag you) your answer is NO.

No-one here on forums can make a safe souleater script (Assuming you mean use AOE runes) i don't give a fuck how good they think they are.

The safest you can get is a floor checker and "x ray" checker so to speak, so that you can have the best chance at detecting if a player is above/below or just off screen.

This will avoid people levitating up or down onto ur runes, but when I wait, and dash onto screen with a 300+ Mage, ur bot is GOING to hit me at some point.
This, I guarantee you.

It's because when the bot has determined that it is safe, at that SPLIT second it takes to actually fire the rune, I've already moved 2 screen lengths.

Just me that gets completly overun since I updated bot?!

Errors on things that I havnet changed, that worked flawless before I patched.

02:44 XenoScript Error:
Script: GStomb.lua
Line #: 1750
Chunk: C:\Program Files ?x86??XenoBot?Data?XenoLuaLib.lua
Error: attempt to call field 'GetItemIDFromDualInput' (a nil value)
This is an error with user-input and should not be reported as a bug with XenoBot.

Quote:

---

Originally Posted by Bollo

Just me that gets completly overun since I updated bot?!

Errors on things that I havnet changed, that worked flawless before I patched.

02:44 XenoScript Error:
Script: GStomb.lua
Line #: 1750
Chunk: C:\Program Files ?x86??XenoBot?Data?XenoLuaLib.lua
Error: attempt to call field 'GetItemIDFromDualInput' (a nil value)
This is an error with user-input and should not be reported as a bug with XenoBot.

---

Some Lua in your script has something wrong with it, have had some problems like this before and fixed it by finding the broken function/Lua that was used.

Quote:

---

Originally Posted by Bollo

Just me that gets completly overun since I updated bot?!

Errors on things that I havnet changed, that worked flawless before I patched.

02:44 XenoScript Error:
Script: GStomb.lua
Line #: 1750
Chunk: C:\Program Files ?x86??XenoBot?Data?XenoLuaLib.lua
Error: attempt to call field 'GetItemIDFromDualInput' (a nil value)
This is an error with user-input and should not be reported as a bug with XenoBot.

---

It looks like you have something in your script which is setting the global "Item" class to a value other than the meta-table which is used in the library.

Quote:

---

Originally Posted by Mannow

Nice Job :)

Also, @The guy who asked about Souleater script (CBF going back to tag you) your answer is NO.

No-one here on forums can make a safe souleater script (Assuming you mean use AOE runes) i don't give a fuck how good they think they are.

The safest you can get is a floor checker and "x ray" checker so to speak, so that you can have the best chance at detecting if a player is above/below or just off screen.

This will avoid people levitating up or down onto ur runes, but when I wait, and dash onto screen with a 300+ Mage, ur bot is GOING to hit me at some point.
This, I guarantee you.

It's because when the bot has determined that it is safe, at that SPLIT second it takes to actually fire the rune, I've already moved 2 screen lengths.

---

Or sit near you till the soul eaters nuke you down.

Quote:

---

Originally Posted by Mannow

No-one here on forums can make a safe souleater script (Assuming you mean use AOE runes) i don't give a fuck how good they think they are.

---

I promise you I could.

Quote:

---

Originally Posted by DarkstaR

I promise you I could.

---

This looks like it could get interesting haha

Next up Self.Logout() and Self.UseItemOn(itemid, "eq name, eg shield")

Quote:

---

Originally Posted by DarkstaR

I promise you I could.

---

Well if anyone could it would be you or syntax/spectrus i guess,

Although, i just don't know how it could be done :P

When a level 350Mage is dashing onscreen, I'm sure that after a few attempt,s the bot will accidentally strike a player :D

Theres already scripts that take multi floor and x ray into account i think? Other than that I'm not sure what else could be done to not fire a rune, :(

Quote:

---

Originally Posted by Dorian

GJ u are the best your bot are the best but still there is no person or possibility to do a safe script on souleaters (in pvp world ) in my best place :/

---

bullshit :D

Quote:

---

Originally Posted by Mannow

Well if anyone could it would be you or syntax/spectrus i guess,

Although, i just don't know how it could be done :P

When a level 350Mage is dashing onscreen, I'm sure that after a few attempt,s the bot will accidentally strike a player :D

Theres already scripts that take multi floor and x ray into account i think? Other than that I'm not sure what else could be done to not fire a rune, :(

---

1. Do not shot GFB's within 45 seconds of seeing another player, switch to strike spells. This makes dashing back and fourth very hard to properly accomplish due to the fact that after a failure you have to go away for a minute before trying again.

2. Set up the GFBer to only GFB in enclosed locations, and make the script stand in the middle of those rooms and wait for the souleaters to gather. Make the spot where it stands a spot where someone dashing around has to cut south or north after running through the entrance to the cove.

3. Be awesome.

@DarkstaR there was a new update today if im not worng, do you gonna stream?

He usually does. Keep in mind he does have a day job and it's currently 7:30 or thereabouts where he lives. Other updates he's started streaming around 11 pm CET.

wheres he stream at ?

be patient a new update will come soon :)

I'm at work but I'm currently inspecting the new client. The reason they claimed to have update seems like a mask and I'm trying to figure out what they've added. There is ~14KB of new code in the client which I cannot account for. I did, however, notice that there aren't any new API imports, so its unlikely there's anything major going on.

we waiting for new update :)