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...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
Keeping for Nostalgia Reasons
Sold 150 ED / 100 RP to Quin
Bought 300ED from @Taco bell
Bought 350RP from @Taco bell
Sold 315ED to @Uranus
Sold 360 RP to @reaper15
Bought 250 MS from @Czoger
Bought 150 EK from @Mentoll
Bought 150 ED from @PunktG
Bought / Sold Many KK's to/from Various members
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 demon
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.
Keeping for Nostalgia Reasons
Sold 150 ED / 100 RP to Quin
Bought 300ED from @Taco bell
Bought 350RP from @Taco bell
Sold 315ED to @Uranus
Sold 360 RP to @reaper15
Bought 250 MS from @Czoger
Bought 150 EK from @Mentoll
Bought 150 ED from @PunktG
Bought / Sold Many KK's to/from Various members
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?
This part I don't know. Im just the tester :P
Keeping for Nostalgia Reasons
Sold 150 ED / 100 RP to Quin
Bought 300ED from @Taco bell
Bought 350RP from @Taco bell
Sold 315ED to @Uranus
Sold 360 RP to @reaper15
Bought 250 MS from @Czoger
Bought 150 EK from @Mentoll
Bought 150 ED from @PunktG
Bought / Sold Many KK's to/from Various members
Bumping into something thats unwalkable, isnt the fault of the script, unless the targetting ofcourse was standing diagonal.
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:
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?
I'll leave DarkstaR to answer that
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.
Posting Permissions
