[Windows 7 x64] Walker Stops Bug

Bug Report

Operating System:

Windows 7 x64

Short Description:

Walker Stops Bug

Behaviors:

• Feature error
• Loss of or impaired functionality

Indepth Description:

This has been an issue that I've been experiencing for a few months now.

The Walker will just stop working, no matter what I do I cannot get it to do anything unless I close the client and open a new one. When this happens the targetter and looter still work properly.

A few weeks ago after a lengthy troubleshooting process I narrowed down the cause of this to be the wave attacks in the magic shooter. I turned all wave spells off and I stopped having issues with the walker.

Unfortunately though I am experiencing this walker bug again... My wave spells are still off so this shouldn't be the cause.

When it happens, tell me if Walker.Delay(0) fixes it.

How should I try to get it to execute this? Write it into a script and load the script? Also I got a bug last night, I don't know if it's related but it crashed my client and sent you a report. Should I post the bug report from the log file here?

Just have a lua script chillin with only that one line, execute it when the walker stops working, and see if it fixes it.

Well I don't know if it's even going to do it again, I've been going all day without any problems.

Yesterday 2 clients bugged (walker stopped) at different times throughout the day then one of the clients crashed later...

I'll make sure to test that script if it ever happens again and let you know if it works.

OK, the script bugged out again, walker stopped. The looter and targetter still functional.

I ran the script Walker.Delay(0) just as you said, in a lua file by itself. This did not work. I tried multiple times just to make sure it wasn't working (about 10 times).

How about killing all the scripts that are running while this happens, have you tried that?

That's the first thing I tried. It doesn't work.

I have a client client bugged out right now if you have anything else that you would like me to try.

Cavebot.Stop() Walker.Stop() Walker.Delay(100) Walker.Start()

Nothing. I will leave this client open for testing if you have anything else.

That happened to me before, i just stopped walker, killed all running scripts, and then reloaded the Settings file i was using, went into walker, found where I was in the wpts, and turned on walker. Not efficient, but it should work.

That's the first thing I tried doing when I started experiencing this bug, it doesn't work. Just tried it again, doesn't work.

Can special areas be causing this? The walker stops on the same waypoint about 90% of the time, it does happen in other points also. I have special areas all over the place, not just this one spot. It doesn't stop on a label, it stops on a node.

Quote:

---

Originally Posted by iudicium105

Can special areas be causing this? The walker stops on the same waypoint about 90% of the time, it does happen in other points also. I have special areas all over the place, not just this one spot. It doesn't stop on a label, it stops on a node.

---

If it doesn't get stuck then I doubt it's because of special areas but dont know, could be as well that some monsters block the path a screen away (if your nodes are too far from each other) but I think stuck alarm should be fired then as well.

Quote:

---

Originally Posted by Nakuu

If it doesn't get stuck then I doubt it's because of special areas but dont know, could be as well that some monsters block the path a screen away (if your nodes are too far from each other) but I think stuck alarm should be fired then as well.

---

It's not getting stuck like that. There's nothing blocking the path.

Are you walking with mapclick?

Yes it is using map clicks in spawn

That's what the problem is, then, probably. Tibia client's mapclick remembers the location of things like creatures and boxes, so if the path is blocked by them when you leave the screen, it will remain blocked as far as Tibia is concerned. You can test by map-clicking to the next waypoint yourself. A fix may be to toggle off mapclicks if you're stuck for > 20 seconds.

Good call, shadow

Quote:

---

Originally Posted by DarkstaR

That's what the problem is, then, probably. Tibia client's mapclick remembers the location of things like creatures and boxes, so if the path is blocked by them when you leave the screen, it will remain blocked as far as Tibia is concerned. You can test by map-clicking to the next waypoint yourself. A fix may be to toggle off mapclicks if you're stuck for > 20 seconds.

Good call, shadow

---

I learnt that from watching your pathfinding vlog. A lot of the information in that one has been really useful when laying waypoints.

I'm experiencing the same problem. At one node in particular in my script my walker stops working. I don't think its a map click issue because:

1) Manually map clicking works.
2) Manually walking to the node and then back to update creature locations stored in Tibia memory does not get the walker working.
3) Switching back to arrow key mode does not get the walker working again. In fact nothing does besides closing and restarting the client.
4) After getting stuck, it doesn't matter what node or label I'm on, the walker refuses to do anything. Not even label code or one-liners are executed.

Furthermore, Walker.Delay(0) and all the other lua commands to start and stop the walker and whatever don't do anything. It's probably not an infinite loop or delay in my script as my modules continue to work normally, and killing all my running scripts does not fix the problem.

Here is a video recorded after the issue occurs. I killed the scripts and changed the pathfinder before recording. This happened about 2 hours into a botting session.

https://www.youtube.com/watch?v=bhRLCd5z5_s

@DarkstaR

Show diagnostic info when its happening. That's what it's there for.

Quote:

---

Originally Posted by DarkstaR

Show diagnostic info when its happening. That's what it's there for.

---

Well, the error hasn't reoccurred in the past 25 hours of botting so I can't give you the diagnostic info in a video. Though before making the above video I did look at it. Unwalkable tiles appeared unwalkable and walkable tiles appeared walkable, so nothing unusual there. Not sure what else in the diagnostic info you would have been interested in.

Anyways, I'll probably just adjust the nodes until I stop running into the issue.

Quote:

---

Originally Posted by Ben

Well, the error hasn't reoccurred in the past 25 hours of botting so I can't give you the diagnostic info in a video. Though before making the above video I did look at it. Unwalkable tiles appeared unwalkable and walkable tiles appeared walkable, so nothing unusual there. Not sure what else in the diagnostic info you would have been interested in.

Anyways, I'll probably just adjust the nodes until I stop running into the issue.

---

The diagnostic issue might seem as simple to you as you just described, but I assure you I'm much better at parsing it in a meaningful way.

I've been having this issue with one of solidscripts paid scripts. They told me to post about it here in the bug report section as it seems to be related to the bot and not their script. It's been happening a lot to me recently (every 3 hour or so). It has only happened with this particular script though, I do own and use many others and never seemed to have the issue before this.

I will start the script, go AFK and check on it every now and then. Usually within 3 hours or so I will see the character just standing still doing nothing. Reloading the script doesn't fix anything and the only solution is to restart the tibia client. Is there anything you can do about this? Is there anything I can do to help you fix it? :P

Agreed about what @pajfest says above, it's still happenning to me EXACTLY same thing, not even with reloading script, or changing pathfinder works, it just stucks. The only thing that helps is restarting Tibia client, I've watched diagnostic thing and where it says "Following path:" it's false, somehow it doesn't go ahead, I forgot to take SS or something, I'll be aware for next time..
When this happens my character is stucked with many monsters, those are in way to hunt so I haven't added to atk them, but I have added in spells if walker is stuck do x thing, but when this bug happens, there is no Walker Stuck message, so it doens't atk any monster (I have also atk all creatures if stuck).

Does anyone give a shit about this? I don't think so.

http://prntscr.com/a12dzk

Oh, I think I have to be monthly subscriber in order to post bugs, yeah damn.

No doubt why I made this post: http://forums.xenobot.net/showthread...orst+community

same issue for me on some official and solidscript's scripts and nothing seems to be working to fix the issue except for restarting the whole client
but never encountered this using my own scripts

im having the same issue useing the ox mage demon script it just stops at all noad points for 5 sec-5 min the healer or targeter dont stop so not that big of a deal for that script bc it keeps the demon spawn up but still annoying and if anyone sees me stoping like that they know im boting and they will report me

Experiencing the same:
http://forums.xenobot.net/showthread...l=1#post490618
Here are posted screenshots. Sorry for making another thread, didn't notice this one, although my problem occurs in win10

http://i.imgur.com/2dcdfYF.png
happened again today on hydras on talahu

is this possible, that this happens when you get logged out of the xeno client? I just noticed that when I wanted to run next script now I was logged out of xeno and had to log in to inject

Died at Level 159 by a terror bird.

The solution is to stop the dynamic lure, I tried it and it worked well for me!