Version 2.7 for new patch. Implemented the proposal of Merkada above.
WQ bot for PWI
05/04/2011 21:25
msxgames#166
05/14/2011 01:22
spyd#167
can u pls explain me how to use it. i started it, but he cant find any char?!
05/14/2011 12:09
msxgames#168
Which server are you on? The download only works for Perfect World International.
05/14/2011 15:51
spyd#169
i amQuote:
Which server are you on? The download only works for Perfect World International.
05/14/2011 17:04
AEBus#170
run that with administrator rights or disable uac
05/17/2011 18:20
spyd#171
working great now :) ty for the hint
05/24/2011 12:56
spyd#172
is the bot able to cut the wq?
in general there r 30 npc to contact, but the bot skipped a few (imo). he got after 20, 22! and after 24 disappeared he got 27...
in general there r 30 npc to contact, but the bot skipped a few (imo). he got after 20, 22! and after 24 disappeared he got 27...
05/24/2011 18:52
msxgames#173
This is general WQ behaviour. NPC's are from 1 to 30 and each NPC gives you 1, 2 or 3 steps. This number is random and means that you don't have to go to every NPC, but just a random number 1, 2 or 3 each time.
05/25/2011 21:11
Merkada#174
unknown malfunction...
1.) when i start bot, sometimes force client to "Not Respond" state imediatly after i put some character to active state (right window) only when i have 2 or more clients running
2.) sometimes after bot doing whole WQ flying from NPC to NPC without quest (WQ done) and he still send my char again and again for another NPC without any reason
3.) when 2nd problems happend, after 5-7 NPC client lose some textures (zooming map, trees, grass, etc.... ) and if i dont stop that, client crash after few more NPCs
any clue :confused:
1.) when i start bot, sometimes force client to "Not Respond" state imediatly after i put some character to active state (right window) only when i have 2 or more clients running
2.) sometimes after bot doing whole WQ flying from NPC to NPC without quest (WQ done) and he still send my char again and again for another NPC without any reason
3.) when 2nd problems happend, after 5-7 NPC client lose some textures (zooming map, trees, grass, etc.... ) and if i dont stop that, client crash after few more NPCs
any clue :confused:
05/25/2011 23:37
msxgames#175
Hehe, I have exactly the same problems as you sometimes. So after WQ I fly back to archo and restart PWI.
05/31/2011 08:05
ggliukk#176
findWQbotOffsets.exe >> i Gues it's not Working,yes ? O_o .. doing the first way to update the WQing gives no results ... for the 2 it's creating a WQing file but it's emty ( .. Tell me pls .. is this a problem with the server i'm plaing on or it's a problem with (findWQbotOffsets.exe)? :)
[Only registered and activated users can see links. Click Here To Register...] Smt like This (
[Only registered and activated users can see links. Click Here To Register...] Smt like This (
05/31/2011 09:22
Interest07#177
Well, I haven't updated all this for a very long time, so it's prolly just out of date :)
05/31/2011 13:55
ggliukk#178
Sad :( .. will you update it in time .. or u just are allready on others projects ? :)
05/31/2011 16:02
Merkada#179
again error wit flying from NPC to NPC without any Q taking (WQ already done) but this time error comes when bot fly from Vibrant Cliffs to Hidden Orchid so when char was near Cave of the Vicious this error shows and crash whole client, maybe this can help with fix this problem
Windows 7 Ultimate, all time 2x PWI running, but WQ flying only with 1 character, i see bot mostly crash when i minimize PWI and bot window, but not this time
btw nice bot Interest07 and msxgames for keeping this alive :handsdown:
Windows 7 Ultimate, all time 2x PWI running, but WQ flying only with 1 character, i see bot mostly crash when i minimize PWI and bot window, but not this time
btw nice bot Interest07 and msxgames for keeping this alive :handsdown:
05/31/2011 18:00
msxgames#180
This error is a consquence of the client crashing. The bot cannot find the process, because the process it was connected to doesn't exist anymore. I agree that this error could be handled better, but it's not a bug in the bot. Just unhandled behaviour haha. After clicking <Ok> the bot continues working.