[Update] XenoBot v3.0.1

[Joshwa534]

The bot will never try to step on anything that it see's as blocking. If it cannot find a path, it chills in place. Make sure that part of the script isn't trying to use an item or rune which you don't have - that could be causing the same message.

So if you've set targeting to keep your character at least 3 squares away and you get trapped, the character will stop trying to get 3 squares away from the target? Just curious how it works in this situation, if that is the case then there most be another issue and we'll look into all possibilities. @Tripkip

Thank you,
Joshwa534

[DarkstaR]

So if you've set targeting to keep your character at least 3 squares away and you get trapped, the character will stop trying to get 3 squares away from the target? Just curious how it works in this situation, if that is the case then there most be another issue and we'll look into all possibilities. @Tripkip

Thank you,
Joshwa534

It will keep pathing until it finds a path.

[Joshwa534]

It will keep pathing until it finds a path.

Thank you =]

[Tripkip]

Thank you =]

Hmm it isnt using any runes, But I think I might know the "problem". In the targetting prioritys we got fire elementals (FE) set higher then the demon itself, because it can get u trapped between the demon,FE and special area. So to avoid standing in the waves, we let the fe's be killed first. If a fire elemental is summoned behind the demon, and therefore unreachable, it will try to target the FE? and thats whats causing, the sorry not possible? Cant think of anything else, altho it shouldnt try to attack a monster thats unreachable, unless it see's the demon as "walkable"

@DarkstaR

[Joshwa534]

Hmm it isnt using any runes, But I think I might know the "problem". In the targetting prioritys we got fire elementals (FE) set higher then the demon itself, because it can get u trapped between the demon,FE and special area. So to avoid standing in the waves, we let the fe's be killed first. If a fire elemental is summoned behind the demon, and therefore unreachable, it will try to target the FE? and thats whats causing, the sorry not possible? Cant think of anything else, altho it shouldnt try to attack a monster thats unreachable, unless it see's the demon as "walkable"

@DarkstaR

You're exactly right on everything you just said. We put fire elementals as a higher priority than demons because they will cause you to get trapped in a few areas that will have you facing a demon head on instead of running away from it. Although.. you're using this with a paladin or druid, is it not able to shoot the fire elemental from where its standing?

[Tripkip]

You're exactly right on everything you just said. We put fire elementals as a higher priority than demons because they will cause you to get trapped in a few areas that will have you facing a demon head on instead of running away from it. Although.. you're using this with a paladin or druid, is it not able to shoot the fire elemental from where its standing?

Yep I indeed hunt this with ED and soon RP! havent checked the rp yet. But I think the sorry not possible is caused by, the small amount of time it does try to attack fe, trys to reach it, and then finds out it cant, and goes back to the demon. So yes it might actually be able to shoot the fe but the bot blocks u from doing it because you cannot reach the monster. Anyways I might have a solution as I posted in your thread!

Make the whole area in that east tower special area, except the tile north of the stairs. This way demon + fe can hit you (if demon is standing in front of you), and it wont try to walk anywhere because its blocked by special area?

[Eotar]

With the verison 3 of xenobot, will the new classes overwrite some of the old ones?

Excuse my unawareness.

[KingDavey]

Okay bro i have encountered a problem, probably due to operator error, but here she goes:
This works fine,

--ALARM SETTINGS--
------------------------------------------------------------------------------------------------------------------------------------
--Manas
local mA = 50000							--How mana manas to sound the alarm.
local mT = "mana potion"				--What type of mana potion are you using.
--Healths
local oA = 10							--How mana "other" items to sound the alarm. (Can be anything, runes, potions, supplys.)
local oT = "ultimate health potion"		--What type of item is this. (Can be anything, runes, potions, supplys.)
--Capacity
local cA = 50							--How much cap to sound the alarm.
------------------------------------------------------------------------------------------------------------------------------------
--Do not touch below--

while true do
    if Self.ItemCount(mT) < mA or Self.ItemCount(oT) < oA or Self.Cap < cA then
        alert()
        wait(5000)
    end
    wait(300,500)
end

--Do not touch above--

--[[
Signed,
KingDavey
]]

But this, i am getting a nice little error.

--ALARM SETTINGS--
------------------------------------------------------------------------------------------------------------------------------------
--Manas
local mA = 50							--How mana manas to sound the alarm.
local mT = "mana potion"				--What type of mana potion are you using.
--Healths
local oA = 10							--How mana "other" items to sound the alarm. (Can be anything, runes, potions, supplys.)
local oT = "ultimate health potion"		--What type of item is this. (Can be anything, runes, potions, supplys.)
--Capacity
local cA = 50							--How much cap to sound the alarm.
------------------------------------------------------------------------------------------------------------------------------------
--Do not touch below--

while true do
    if Self.ItemCount(mT) < mA or Self.ItemCount(oT) < oA or Self.Cap < cA then
        alert()
        wait(5000)
    end
    wait(300,500)
end

--Do not touch above--

--[[
Signed,
KingDavey
]]

All i did was change the mana amount, this is the error.

20:18 XenoScript Error:
           Script: Alerts.lua
           Line #: 15
           Chunk: ...?Users?DVJasper?Documents?XenoBot?Scripts?Alerts.lua
           Error: attempt to compare function with number
This is an error with user-input and should not be reported as a bug with XenoBot.

What am i doing wrong? Thanks for your reply.
Also, how i do that code lua box? [CODE][/CODE=lua] shit like that is what i was trying, i dunno how lol.

[sirmate]

What am i doing wrong? Thanks for your reply.

It's cleary says what you are doing wrong: Error: attempt to compare function with number.
You don't call Self.Cap function and then match, instead you try to compare it (Self.Cap function) with number and that's why you are getting such error.

[KingDavey]

It's cleary says what you are doing wrong: Error: attempt to compare function with number.
You don't call Self.Cap function and then match, instead you try to compare it (Self.Cap function) with number and that's why you are getting such error.

Got it so i left out the parenthesis, thanks bro.