Rishodis P bot issue

[Agizor]

Sorry if this was covered elseware... Just faile to spot it I guess... Anyway, I have the latest build of this bot that is said to work with 1.11, and it is configured properly (atleast to my knowing) but when I go to start it, it will join a game and things fine, but after it sets the away message it types this:

.set gselect

And then an error comes up saying "Couldn't get a handle, please insure that Diablo II is running"

This sounds like a version problem with Diablo II and the bot or zpickit. Anyone know what would do this?

If it is zpicket (I couldn't find the latest version... I could only come accross the 1.10 compatible one) where can I get the very latest build?

Thanks

[Tool]

Well, seeings as the D2Loader of today for 1.11 won't work with plugins you kinda can't do shit about it. =\

[Argonsax]

The problem here is your pickit, not the bot, the loader, or your D2 installation. The " .set gselect" command is used by Pindle to determin the ground select in your zpickit.ini file. Its a simple fix, just make the global config in pindlebot.ini look something like this:
""""""""""""""""""""""""""""
[Global]
D2Path=
D2Exe=Diablo II.exe
D2Parameters=-skiptobnet -w -ns -lq -res800 -nonotify
D2WinTitle=Diablo II
GameName=
PauseButton={PAUSE}
AwayMessage=AFK...pindle.
MoveWindow=0
UsePickit=1
NoPickup=0
Runs=-1
MaxVariance=20
Stash=1
RunInterval=200
IntervalVariance=50
SleepTime=900
SleepVariance=600
SlotToUse=
"""""""""""""""""""""""""""
Without the "" of course, and your pindlebot.ini file may be different form this in any way, just pointing out that "NoPickup=" should be set to 0. This will tell it not to send the command thats crashing it. If this doesnt work for you, set "UsePickit=" to 0 until you can find a working version of zpickit. Be sure you're using the 1.11 loader from the downloads section here it works as a cd crack but it also loads plugins just fine.

[Agizor]

The problem here is your pickit, not the bot, the loader, or your D2 installation. The " .set gselect" command is used by Pindle to determin the ground select in your zpickit.ini file. Its a simple fix, just make the global config in pindlebot.ini look something like this:
""""""""""""""""""""""""""""
[Global]
D2Path=
D2Exe=Diablo II.exe
D2Parameters=-skiptobnet -w -ns -lq -res800 -nonotify
D2WinTitle=Diablo II
GameName=
PauseButton={PAUSE}
AwayMessage=AFK...pindle.
MoveWindow=0
UsePickit=1
NoPickup=0
Runs=-1
MaxVariance=20
Stash=1
RunInterval=200
IntervalVariance=50
SleepTime=900
SleepVariance=600
SlotToUse=
"""""""""""""""""""""""""""
Without the "" of course, and your pindlebot.ini file may be different form this in any way, just pointing out that "NoPickup=" should be set to 0. This will tell it not to send the command thats crashing it. If this doesnt work for you, set "UsePickit=" to 0 until you can find a working version of zpickit. Be sure you're using the 1.11 loader from the downloads section here it works as a cd crack but it also loads plugins just fine.

Thanks a million. Just wondering though. I was doing legit pindle runs and after a few I got kicked off b.net saying I was temorarily not allowed to access the realm. What gives? We aren't allowed to do legit runs now?

[Argonsax]

So all that worked out for you? And yea, bnet can be *****y like that, if you switch characters too much or send alot of illegal packets by say lagging out and teleing off the map...when you get that its normally just best to wait it out, there are ways around it but theyre kinda complicated..most of the time the ban lasts about 10 minutes to an hour, the max is i think 2 days, if you want I can explain how to get past it but like i said its complicated..

[Agizor]

So all that worked out for you? And yea, bnet can be *****y like that, if you switch characters too much or send alot of illegal packets by say lagging out and teleing off the map...when you get that its normally just best to wait it out, there are ways around it but theyre kinda complicated..most of the time the ban lasts about 10 minutes to an hour, the max is i think 2 days, if you want I can explain how to get past it but like i said its complicated..

Alright. Yeah though... I PM'd you about it. Would like to see. Dealing with proxies? I dunno, anyway, would like to see how its done.

Thanks

[WarriorOfD2X]

Thanks a million. Just wondering though. I was doing legit pindle runs and after a few I got kicked off b.net saying I was temorarily not allowed to access the realm. What gives? We aren't allowed to do legit runs now?

thats the new relm down msg it gives, so it no longer says relmdown, it says that.

[Agizor]

Still having problem now when I acutally tried it. Amazing.. Can anybody send me there zpickit.ini and bot config file (minus the acct name and pass of course) to see if im doing somthing wrong? Like my dir and all is default..

[Dark.Zero]

theres a new pickit for 1.11??? or am i missing something in that last post?

[Agizor]

I have no idea. The bot is said to work with 1.11, yet it clearly says in the ReadME to use zpickit... Yet the latest verson of that is 1.10. Makes no sense...

I figured out, if I just click "Ok" to restard the script when I get the "Can't find handle" error, it will start to run. She will run to the red tp after casting Chilling armor, and then I'll get the error a second time, and it just keeps doing so.

[Dark.Zero]

that means that it doesnt work....

[Agizor]

No $hit? How about telling WHAT exactly doesn't work. Says right here on the site under 1.11 for this bot. It DOES work because it moves and opens inv and everything correctly. It just gives that error every 7 seconds, whilst in the meantime, yes, it does work.

I wonder if it has anything to do with the loader im using. Which is now going "we got a big error here"

How to fix that??