Could anyone be nice enough to tell me what xb can do? :D
Printable View
Could anyone be nice enough to tell me what xb can do? :D
I think the real question is what Xenobot cannot do...Quote:
Originally Posted by Asuna-Chan
xiaospike@ ---> Not showing gained profit, not have "auto follow". but without it xenobot IS AMAZING
^~^(^,.,-)^~^ VaMpIrE ^~^(-,.,^)^~^
Shut the fuck up.Quote:
Originally Posted by Joshwa534
Quote:
Originally Posted by xiaospike
Is it all script based? ._. your comment doesn't help D:
Mostly, yes.Quote:
Originally Posted by Asuna-Chan
@DarkstaR
So what ive noticed. When i was targetting a demon in edron demons, it keeps trying to walk over either 1 of these stones.
Yes im sure it does, kept having the message, Sorry not possible. Also, it kept standing in the waves of the demons insted of moving 1 step > wich was actually diagonal.
(got 3 sqm diagonal as targgeting). Except moving << to the stone or moving > there are no other possebillitys to mve to.
19:13 You see a stone. [ID 1778]
19:13 You see a stone. [ID 1772]
Pathfinder settings is set as walk on fire and walk over furniture so obviously it sees these stones as something thats walkable...
Quote:
Originally Posted by Tripkip
Does diagnostic information show them as walkable?
Im refilling, after that ill check it out and let you know!
Alright. Because I was botting in Edron demons and didn't see a problem.Quote:
Originally Posted by Tripkip
I've been botting the same spawn, with the earlier versions, 3.0.0 and 3.0.1 and i've never seen a problem there...Quote:
Originally Posted by DarkstaR
@Tripkip Is it in the South-West tower? If it is, and your standing still thats intended. No room to run in that small space
It shows as Blocking... yet it keeps trying to walk over, or maybe it trys to go trough the demon? either way it wont move away from waves of the demon, even when i move it manually it moves right back in front of the demonQuote:
Originally Posted by DarkstaR
Yeah, it was made like that on purpose. When we tried to have it run it would go down stairs or just sit there and 'try' to move in its place. This is why it was made 'hardcore' for that tower.Quote:
Originally Posted by Tripkip
yes it is in the soutwest tower, but I dont think its intented to try and bump into a demon/stone aslong as its killing it. no Human would do it, and therefore it seems detecable to me, just as walking into a stalker for about 10 minutes. So yes Im not a complete retard and I do understand it has no space to run, but does that mean it should bump into a creature for aslong as its killing it?Quote:
Originally Posted by Abuse
This part I don't know. Im just the tester :PQuote:
Originally Posted by Tripkip
Bumping into something thats unwalkable, isnt the fault of the script, unless the targetting ofcourse was standing diagonal.Quote:
Originally Posted by Abuse
its a flawl/bug in xenobot I geuss. If something is unwalkable, and therefore you cannot reach the desired "stance" this should be returned and it shouldnt try to walk trough.
@DarkstaR am I right? or am I talking complete nonsense here :P?
THEORY:Quote:
Originally Posted by Tripkip
This is because the character is still trying to find a way to continue staying diagonal from the target. It might just be a targeting issue but I don't think its something to worry about. I've seen a very similar scenario when you're at say Lizard Chosens and the special areas cause you to stay within a perimeter but next thing you know you're stuck in the corner of the cave with 3 Lizard Chosens bashing you. So basically the cave wall is against your back and the 3 Chosens have you trapped, there's nothing your character can do yet since the targeting is set to 3-4SQM diagonal, it still try to find a path to move away from those Chosens. Like I said though, I don't see this being an issue and its definitely not detectable.. rubber banding, or "banding" is in a lot of games. It can be caused from several things, take for example you go out manual hunting and you just start trying to talk face first into a dragon nonstop for 30 seconds. Doesn't mean you're botting, just means your son has his fingers on your arrow keys (happened to me plenty in the past). Its just Tibia's "bounce-back" or whatever you want to call it, the bot is only trying to find a way to stay diagonal, I think. Its been seen before in other bots in the past as well.
DarkstaR might clarify/confirm this and could probably write it out easier.
Alright that clears it up for me... tho I get you're explenation, I just doubt thats its undetecable... Might be able to get fixed tho?Quote:
Originally Posted by Joshwa534
I'll leave DarkstaR to answer thatQuote:
Originally Posted by Tripkip
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. @TripkipQuote:
Originally Posted by DarkstaR
Thank you,
Joshwa534
It will keep pathing until it finds a path.Quote:
Originally Posted by Joshwa534
Thank you =]Quote:
Originally Posted by DarkstaR
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"Quote:
Originally Posted by Joshwa534
@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?Quote:
Originally Posted by Tripkip
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!Quote:
Originally Posted by Joshwa534
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?
With the verison 3 of xenobot, will the new classes overwrite some of the old ones?
Excuse my unawareness.
Okay bro i have encountered a problem, probably due to operator error, but here she goes:
This works fine,
Code:--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.
Code:--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.
What am i doing wrong? Thanks for your reply.Code: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.
Also, how i do that code lua box? [CODE][/CODE=lua] shit like that is what i was trying, i dunno how lol.
It's cleary says what you are doing wrong: Error: attempt to compare function with number.Quote:
Originally Posted by KingDavey
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.Quote:
Originally Posted by sirmate
one of my friend still have problems with levers, i even sent for him install file what i used to install it on my comp
i need say this version work for me best :)