v5 seems better than v8. the walk script in v8 tends to get lost and recovery is bad. v5 is the best for me so far.

Reinstall Sro. It should work then.

Look, I'm getting this error, when pressing Start Walkscript--->>>[Only registered and activated users can see links. Click Here To Register...]
It's says, that i need to cerate Script, but --->>[Only registered and activated users can see links. Click Here To Register...]
I'm using newest Agbot version, I think it's v1.6.5vX (2.2.10), don't know for real.

u named the scriptfile default555.lst or so u must call it only default.lst otherwise the bot wont accept it

Hell yeah! Thx alot. Problem again, walkingScript is very lame, I don't know, i don't think it's because of the lag, but bot, can't run probably... Any ideas? Is it only for me very buged Walkscript? Or what? I don't get it...

No, the walkscript thingy is not only for you very bugged. I dont know if its for everyone like that but the versions after 1.6.5v5 seems to work very buggy. Instead of walking into the train area he start to move back and forth a lot of time, i never reach the train area with the newer versions and use 1.6.5v5 again. Never change a running horse or what was it?

Anyway, i use nuconnector and not srproxy(with srproxy crash the game very often). If you have a lot of DC's then set the priority of nuconnector and agbot to the highest priority you can. Then youre able to do other things on your pc too without problems for your bot and he wont dc, or at least he dont dc very often. I can bot over 10hours without dc for sure and can play without problems COD4 while that as example.

Here is btw. the offical guide site to agBot:
[Only registered and activated users can see links. Click Here To Register...]

You can download there all the old versions.

I have followed all the guides and installed all of the libraryfiles, i have also tried srproxy but i still cant seem to get my player name and level to appear on the bot when i log into my character. I noticed that on my nuconnector its says "New Security Feature Failed. Do you have the NetBIOS protocol installed? If not, please enable it."
[Only registered and activated users can see links. Click Here To Register...]

The guides nuconnector says "New Security Feature Success."

[Only registered and activated users can see links. Click Here To Register...]

I dont know if this will fix the problem but i know nothing about netbios and was wondering if anybody knows how to enable this. Also if anybosy else has the same problem does your nuconnector say the same thing.

wow try to use an newer nuconnector then v5.5 :S

I ahve already downloaded 1.6.5v5, but there's still is problems with walkscript... And one more thing, I have to start walkscript after every teleport after botting at mobs, when no MP/HP or death, because he' don't do Start Walkscript, i don't know if there is such as command like start Walkscript.. So how can you bot 10h?

Wow.
Agbot becomes better & better.
This bot is as good as iSRO bot but he got lots of bugs :S
Thank god i got SM xD
But i will give this bot a try.
thnx for posting.

Start agBot click on the "Config" button and activate "Loop after teleport" then he will start the walkscript again after the teleport, what else. You should have an working walkscript first too, of course. :cool:

It's not that good right now. It was better before without the walk script, now its just extremely slow and bad when killing monsters and picking up gold.I hope a better version comes out soon because I can hardly bot with it at all.

im using agbot 1.6.5v5 and I have the problem with store items, bot goes to the storage, he deposits items, but I still see them in the inventory, they occupy the slots and I can't move them, they disappear after the next teleport, any solution how to fix it?

I LOVE YOU AXE! I remember you having the same problem as me and i just read your post about how the bot is slow so i read through some of your other post and saw u fixed the playername thing by changing ur non-unicode language to english. Thats what i did and it worked!

Have u tried going back to 1.6.5v5? Cuz I have the same problem u have and this was the solution for me.