Mining Bot - Errors/Discussion

[Cooleko]

To those with the program, I have introduced some rather odd problems in the latest release. Some seem to occur in only Windows 7, and some are just bad coding on my part where I didn't consider all of the scenarios.

Can you post any problems here? I will make sure each one is addressed and send a new program out.

Posting here rather than email will ensure each tester can see that other people are having problems without me spamming each additional one to email. It will also allow me a centralized place to look for any problems I haven't already addressed.

Thanks!

[anarres]

the bot is working nicely (any version of v2 on w7 64bit) my problem now is about minerfiles if i can merge together nodes data without start from the beginning, because i have different back ups.All my old files are messed up so i'm doing iron lake (found 30 nodes atm & leves too) waiting if you can fix some zones that should already working good (halatali x ex) to tune up lately with other tools you send.
the use of aggro center/radius: i'm recording a new zone i start record route, arrive add node, then stop record. At this point i use the mining node as center of aggro and walk to the first available no mob zone and record radius ok?
if i have to record also route i need to go back to node now and start record or i can do at the same time when i do aggro center?
I still have no completely clear the function of smooth + add : i must use it frequently like at the end of a well done route, just at the end of a session to "record" what i have done or if i did precise nodes and routes i can avoid to use?
let me know thanx

[asdf1987]

Win 7 ult, 64bit.

problem i have is the bot will sometime rename a existing route as a different route name.
ie. route from node 1 to node 2 saved as 5-3...
which will confuse the bot in the route its suppose to run.
temp sol'n: run smooth+add

Also, noticed some routes runs through walls and cliff, not sure where these routes came from, but im assuming it was from smooth+add, since i cant possibly record those... I have deleted these routes and will keep an eye out if they pop up again (though i point it out and see if it was only a problem i have)

ps. add "wasd" for movement control

[anarres]

can't open any viewer (see error picture i send by mail)...i put all in same directory
also mining preparer doesn't make nothing if i try to open
i did almost all nodes (just1 repeated- i don't want to erase manually cuz i'm afraid to crash all like did in first bot) but i notice sometimes read wrong nodes also when record. I wish to correct but idk how.Please explain how to install and use correctly node viewer ,killer , preparer

thanx

[Cooleko]

We found that you never ran the Zdata program to properly format your routes. Hopefully you have no problems after following my recent instructions

[pcsmasher]

Hello. I have sent you a message and still haven't gotten a response from you yet. Hopefully you will hear me out from this post. I've been wanting to attend to your program, Cooleko.

[Cooleko]

atm, I am too busy to add people to the mining beta and/or begin the harvesting beta. When I am complete with the mining beta I will let those in the harvesting recruitment know which have been selected.

Working with the selected people for mining bot has already taken more time than I have available. Until they have finished their participation I cannot start the harvesting beta without over-taxing my sanity!

[anarres]

can' even open now as i told you by mail...i was thinking about closing areas i'm working on this weekend...so please le t me know

[ZENS!ERT]

error 23.path/file?

[Cooleko]

Did you post in the wrong thread fruhling?

[ZENS!ERT]

ups right....

[Luv2bLeeT]

I just want to let people know that they should probably run out to the diff spots they've done and double check they work. I had some issues when checking certain spots that I had completed that it would repeatedly ask me to record path to destination even though on route viewer everything checked out. Turns out part of my file had Nodes=# instead of Coords=# and just renaming nodes to coords didn't fix it. Had to re-run the "bad" routes to fix the file. Just a heads up. (Note: the files that were affected seem to be old ones as I had last modified them in early Oct.)