[Release] HZD Auto World Quest Bot for PW International: Neverfall (v1038)
Hi Guys!
Just sharing my own World Quest Bot for PW International - Neverfall (Version 2.0.7.2).
Unlike Jawq by Shareen, this is not made to support multiple Game Clients in a single run, but you can run it multiple times and attach to each Game Client.
"Auto World Quest check box" should be checked before clicking the "Start button".
Due to lag or slow connection, the bot just stops because it is not detecting any quest item in bank. Added key in timeouts.ini WQInvCheck and WQAccept (values are in milliseconds) for delay in lookup of quest items and Talking to NPC.
Zip file includes executable bot file, and the following updated configuration files: config.ini timeouts.ini, game.ini and worldquest.ini
Bug - restarts world quest instantly after it is done (trying to fix)
Commands:
Logout
SelectPlayer 'Player Name' (without the quotes)
SelectNPC 'NPC Name' (without the quotes)
UseItem 'Item Name' (without the quotes)
PickUp 'Item Name' (without the quotes)
Dig 'Item Name' (without the quotes)
UseSkill 'Skill Name', 'Skill Type' (without the quotes. Skill Type Options: "Active, Genie, Item")
To turn off Auto-Avoid, add these lines inside the "config.ini" file.
Please be noted that even if you turn-off auto-avoid and your bot detected one of my player-ids, it will still trigger auto-avoid.
It works great on Windows 7, i also had a second HZD_WQ opend on a 2nd char and it did also its WQ.
But on Windows 8.1 64X i get a error with that prog.
The error is in line 46475 of the WQ_64.exe, it says
Error: Subscript used with non-Arry variable and then the prog stops.
It works great on Windows 7, i also had a second HZD_WQ opend on a 2nd char and it did also its WQ.
But on Windows 8.1 64X i get a error with that prog.
The error is in line 46475 of the WQ_64.exe, it says
Error: Subscript used with non-Arry variable and then the prog stops.
Sorry, I don't have a computer with Windows 8.1 64-bit. I will try to look for one and check it.
The flying height between Sumor Camp Elder to blacksmith Yang (WH 15) is now 65 but must higher say 72. Why a char was killed on that route by the flying boss Jewelscalen.
So can you make a little height correction on that route?
The flying height between Sumor Camp Elder to blacksmith Yang (WH 15) is now 65 but must higher say 72. Why a char was killed on that route by the flying boss Jewelscalen.
So can you make a little height correction on that route?
Inside the worldquest.ini, each Quest Item ID has corresponding Quest ID, NPC Name and ID, Fly Flag, Fly Alt (altitude or height), Fly X and Fly Y (Dropping point), Talk X and Talk Y (TalkTo NPC Point to make sure that no dialog box will appear).
If you want to Adjust the Fly Height on your way to Blacksmith Yang which is the value of NPC_NAME_17, then adjust the value of FLY_ALT_17 from 65 to 72.
Please press thanks button if this is helpful. I would highly appreciate it.
If u have downloaded HZD WQ v1.0.2 for PWI then in the game.ini is a error.
U must open it and change Client=PWI.exe in Client=elementclient.exe and save it.
And then it works.
If u have downloaded HZD WQ v1.0.2 for PWI then in the game.ini is a error.
U must open it and change Client=PWI.exe in Client=elementclient.exe and save it.
And then it works.
Yeah I figured that out but then you have to connect to one of the clients using the process ID in the line, ie: "_Connect <Process ID>" and it doesn't do anything.
If u have downloaded HZD WQ v1.0.2 for PWI then in the game.ini is a error.
U must open it and change Client=PWI.exe in Client=elementclient.exe and save it.
And then it works.
Yep, this is easy. the hard part is getting it to keep running. It goes one hop at a time. Sometimes it doesn't leave fly mode and gets stuck, so you have to manually leave fly mode, drop to ground, restart bot. Get to next NPC, bot picks quest, then shows "World Quest Finished", and you have to click the check box to start it again.
I've tried both the 32-bit and 64-bit versions and they behave exactly the same.
Running it as administrator makes no difference, and neither does using the rendernofocus flag, or having the client in focus.
Currently, I cannot get it working any better than sitting here manually doing WQ myself.