[quote="tallaron";p="66385"]
Howdy Watcher!
I found that by making the range at least 15 that the bot don't miss nearly as many nodes and it really didn't miss many anyways. Love the script and this bot harvests like a mad man and using a bot in feerott is awesome since alot of nodes are found that you would probably never see roaming yourself cause of the tree roots being so big there and the nodes hiding among them.
[/quote]
What were you using? 10? It wasn't missing nodes, they were out of range! I use a min of about 15 except for very VERY tight situations.
Thanks, it's nice to hear that you guys are enjoying the bot instead of just the problems with it for a change. 8^)
[quote="tallaron";p="66385"]
I might have found a problem with camping on tells but want to make sure before I give an official bug report. I had the playontells set to false and quitontells to true and got a tell and my bot just stopped and didn't camp.
[/quote]
Yup, you found a bug, one that lead me to fix another bug too, thanks. (See changelog below)
[quote="tallaron";p="66385"]
That new feature with playonfullbags will be nice too. I don't want to make more work for you, but another nice feature might be a custom autoreply feature where if you get a tell he replies but only once....this way you could say something like "Be right back need to relog" but obviously you never come back if you have it set to quitontells. If others think it would be useful and you like the idea then go for it, I'm real happy with what you and others have given us now
[/quote]
I have repeatedly asked for features that people want, beleive it or not you're the first to request one, see changelog.
[quote="mwsupra";p="66389"]
I've also had the same crash as mentioned above where it states "No Resources, moving on" and then the game drops down to about 2 frames per second. After a while it crashes with the same error. I haven't had this problem with any of your previous versions, nor any other scripts out there.
[/quote]
I just searched my code for the phrase "No resources" and came up blank, obviously I have altered that code so maybe I fixed it inadvertantly for next release. What is the frequency of this problem?
[quote="mwsupra";p="66389"]
Also, when I got stuck, it walked backward a bit, and then jumped forward. In the previous script versions, it would walk backward, turn to my right or my left, and then jump forward. While sitting there watching the bot work for a couple hours, there were a couple times I had to move my character to the right or the left because it got stuck. Was that taken out or did I set it up wrong? Is this happening to anyone else?
[/quote]
Nope, I've noticed the same thing, I did change the evade routines but they still need tweeking *sigh*. I have tried to remove the 'botlike' things the bot does and one of them was jumping over and over trying to get past an obsticle, it now jumps once, then turns to one side then to the other but with no jumps. Guess I need to work on the timing.
[quote="mwsupra";p="66389"]
I do love the new changes though and I'm sure soon enough you will find perfection
[/quote]
Hehehe, perfection never happens in coding, the best you can hope for is rare bug reports. 8^)
New ChangeLog for next version:
Code: Register to unlock hidden link
6-04-05 Watcher
Added check for no buffs for buff timer display.
Added tell sound to be done when inventory full.
Changed tell code to be able to play and quit on tells.
Updated docs to reflect above.
Changed 'pass through' range to 5, any MaxWander less than 6
is never searched for resources. (Personal reasons)
Quit on tells and Quit on timeout would only exit EQ if
CampOnEnd was true, fixed.
Added ReplyOnceWith which is a string that will be sent to the first
person that sends you a tell. Mostly for use with QuitonTells
although it need not be. It's one shot, once used will never
be used again.
duh...hehe
Who is online