[RELEASE] Jawq (WQ bot for PWI)

[Smurfin]

Originally Posted by edmundtyy

i tried using the new offsets from smurfy with the 3 lines from mrpaidi. when i click start to initiate the world quest, i got an error Code:256.

i used previous offsets from dixgen, and only i switch the 3 lines from mrpaidi, my client crash upon landing.

Which pw server are you playing on ? Pwi and Pw Indo probably now share the same offsets. I'm sure the offsets I posted in bold above are correct for PW Indo, I've tested and currently using them on my own tools.

Seems like the offsets from dixgen could work for PW Indo, they all matched to the list I posted in bold. Only difference is in hex/dec.

Thanks for mentioning it, just noticed his posting. I'll try it later.

-edit-

First, I used an older version 1.0.48.05 (the official website doesn't put the latest version of AHK , autohotkey dot com, or is that not the official website ?) and it doesn't seem to recognize some lines in the script. Then I downloaded the latest, version 1.15 , the client crashed.

Then I got one from and matched the version Shareen was using when developing this using 1.10.90.00. and got the same error as edmundtyy, critical error 256 but the client didn't crash. It recognized my characters' names so offsets should be fine, only the AHK version and how I should install it is the problem.

I'll try again with different installation between 32 bit 64 bit ansi unicode bla bla. This is annoying when a script doesn't work on newer version of the interpreter. It also happens with autoit >_< ' , so I keep the version of AutoIT installer I usually use.

[edmundtyy]

im currently playing in PW-MY. they just patched the server last week. prior to this, i have been using dixgen offsets which worked perfectly well.

i am still figuring what is the difference that made the error.

[Smurfin]

Now I've read carefully as Shareen instructed on how to compile, and critical error 256 was the best result I got without the client crashing, probably offsets related now, please let me know if you have any luck in getting it working, edmundtyy.

Btw, edmund, is PW-MY still around ? I heard it had closed down a long time ago, since mermaid/tideborn update if I remember correctly. Published by Cubizone at that time.

[edmundtyy]

thanks smurfy, i am still trying around with the offsets. so far no luck on getting it work. either it crashes or error 256. still figuring out.

to the other question, yes PW-MY is still alive. it was under cubizone earlier but they fail to get the license renewed thus a new company called Garena took over and they patch up tideborn at the same time. Seems that garena too failed to renew the license after 2years+ and now 4games under PWI took over. they have been holding this game for about 9months and recently they introduce Horizons patch which includes reborn.

[Shareen]

From lib/constants.ahk:

global ER_UNDEFINEDWQNPC := 256 ; Target npc for wq item id x is not defined

I haven't updated PW since 2-3 patches ago, but if I assume WQ NPCs didn't change, the error would indicate that script is receiving wrong/non-existent item id.

So, If I'm allowed another assumption , I'd say the offset for item id is off, most likely due to the item struct changes (I think I saw someone making a remark about that few posts back).

It's all guess work and speculation, but it explains 256 error, which btw, was put in place for the exact reason noted above

The easiest way to test this (with Jawq), is to enabled logging (Jawq.ini, main section, LogMode=1), run bot until it reports error 256, close bot, open log and look for line that reads:

Npc for item id *** not defined, exiting

where *** will be the item id received by the script and then check, if it matches real wq item in pwdatabase.

The lines that report this error, as well as log entries, are inside Jawq.ahk:

365	if (!IsObject(npcs[itemId])) {
366		player.onError.(0, ER_UNDEFINEDWQNPC, 1, player)
367		player.logWrite("Npc for item id " . itemId . " not defined, exiting")
368		return
369	}

[binz]

Originally Posted by Smurfin

I never do WQ, but right now after reincarnation, the exp is x4 and very tempting, need help filling the right offsets for this list, it's PW New Horizon 1.5.1 build 2309 btw.


This is so far the list that I can gather (in bold), I'll dig the rest later, now is just about the time for nation war so I haven't got more time to dig for more. I'll use decimals for the offsets that I think are the right ones. Some of the offsets are new for me that I never know how to search for them. If anyone has the complete set of offsets for that version please post it here.


[main]
GameProcessName=elementclient.exe
LogMode=0
LogPath=logs/
DelayOnError=5000
MaxErrorRetries=5
[gui]
AnimateRemove=1
[offsets]
CallSendPacket=7584640
CallIsQuestAvailable=0x007966B0
BaseAddress=13229996
BaseOffset=0x1C
PlayerStruct=48
PlayerId=1172
PlayerLevel=1040
PlayerName=1712
PlayerTransportMode=0x688
PlayerFlyMountId=1456
PlayerPositionX=0x3C
PlayerPositionZ=0x40
PlayerPositionY=0x44
PlayerTargetId=3388
PlayerFreeze=0xC3E
PlayerQuestInventory=0xDC8
PlayerAction=5032
PlayerQuestList=5040
ItemId=0x08
Lists=0x1C
NpcList=0x24
NpcSortedList=0x50
NpcId=0x124

Hi Smurf, long time no see
same error 256. I think the address and offset is not right yet.
I believe :
NpcList=0x20
NpcSortedList=0x50
and your level seems wrong
PlayerLevel=1236

CMIIW

EDIT 2 : I didn't look at previous thread lol... dixgen offset is working just fine in my JAWQ

[offsets]
CallSendPacket=0x0073BB80
CallIsQuestAvailable=0x007966B0
BaseAddress=0x00C9DFAC
BaseOffset=0x1C
PlayerStruct=0x30
PlayerId=0x494
PlayerLevel=0x4A0
PlayerName=0x6B0
PlayerTransportMode=0x6C4
PlayerFlyMountId=0x5B0
PlayerPositionX=0x3C
PlayerPositionZ=0x40
PlayerPositionY=0x44
PlayerTargetId=0xD3C
PlayerFreeze=0xD5A
PlayerQuestInventory=0xF50
PlayerAction=0x13A8
PlayerQuestList=0x13B0
ItemId=0x0C
Lists=0x1C
NpcList=0x20
NpcSortedList=0x58
NpcId=0x124

Thx

EDIT 3 : crap... it made my element client shut down... still working on it

EDIT 4 : now it's working just fine enjoy

[edmundtyy]

hi Shareen, i think they change the npc items slightly because previously before it was patched to Reborn, the npcs usually have yellow quest above their heads when there is an item to exchange. but right after the update, those quest turn blue above npcs which i suspect there was changes done which is why error 256 appears.

binz, many thanks. i will be testing it out. will feedback soon

edit: Binz, i tried the new offsets u provided but my client crash when id plan to mount on wings.

edit: Shareen i tried the method u mentioned about looking for the logs when the error pops up, i got this



------------------------------ Object created: TPlayer ------------------------------
[24.07.2014 14:17:47] > Position: x: 1329.818359, z: 219.617844, y: 935.015808
[24.07.2014 14:17:47] > Instance: 0
[24.07.2014 14:17:47] > Game process id: 5532
[24.07.2014 14:17:47] > Wq item index: -1
[24.07.2014 14:17:47] > Events binded

[24.07.2014 14:17:47] > Ready to start!

[24.07.2014 14:17:49] > Start button was clicked, instance started
[24.07.2014 14:17:49] > Critical error occured, instance stopped and unhooked
[24.07.2014 14:17:49] > action code: 0
[24.07.2014 14:17:49] > error code: 256
[24.07.2014 14:17:49] > Npc for item id -1 not defined, exiting
[24.07.2014 14:18:52] > Form is closing, removing player

[Smurfin]

Thanks everyone for helping out especially the creator Shareen, I'll try this again later when I can do WQ after I hit 70 on second reincarnation, shouldn't take too long..well..hopefully.

[binz]

Back from work this morning i WQ 4 instances. And now I only have 1 element client. This is the last log of each crashing element client :

====1====
[24.07.2014 15:43:46] > Current action index: 6
[24.07.2014 15:43:46] > No more actions for Ancestral Guardian Shawn

[24.07.2014 15:43:46] > New item id: 14064
[24.07.2014 15:4

====2====
[24.07.2014 15:38:27] > New item id: 14125
[24.07.2014 15:38:27] > Action index: 0
[24.07.2014 15:38:30] > Executing action flyUp, target altitude 25
[24.07.2014 15:38:36] > Current wq item id: 14125
[24.07.2014 15:38:36] > Current action index: 1
[24.07.2014 15:38:36] > Executing action fl

====3====
[24.07.2014 12:05:47] > Normal path is clear, flying to Merchant Fritz - Volume 35, target altitude 36
[24.07.2014 12:14:28] > Current wq item id: 37017
[24.07.2014 12:14:28] > Current action index: 2
[24.07.2014 12:14:28] > Executing action land:
[24.07.2014 12:14:28] >

Not perfect yet

[Smurfin]

@Binz: but did it work and your WQ got completed even the clients were crashed ?

After the client crashed, can we just re-run and continue from where it left off ? As long as it can get WQ done, I guess it's ok to use even if it crashes randomly, until we find where the error might be, still better than manually do WQ for many chars.

[binz]

Originally Posted by Smurfin

@Binz: but did it work and your WQ got completed even the clients were crashed ?

After the client crashed, can we just re-run and continue from where it left off ? As long as it can get WQ done, I guess it's ok to use even if it crashes randomly, until we find where the error might be, still better than manually do WQ for many chars.

From what i experienced today I think it is always crashed when it start and end @ Li Mengpai. Yes, it can finish WQ but for the next WQ round you have to restart the element client again, and with 10 windows it is definitely better than manual Need tutorial for making OOG bot it will make our life easier

[Smurfin]

I see, good to know, I'll try it 3 levels later.

oot:
I wish I knew how to make OOG stuffs too, but I guess it's still too advanced for making an OOG bot since there is still none released that I know of, probably need more ppl to gather and share their knowledge to make one.

The Russian forum zhyk.ru has the oog related informations though, ppl mostly use it to make an OOG catshop, but it's in different language than autoit, so I don't understand one bit about it, definitely not for newb >_<

[Shareen]

Originally Posted by binz

From what i experienced today I think it is always crashed when it start and end @ Li Mengpai. Yes, it can finish WQ but for the next WQ round you have to restart the element client again, and with 10 windows it is definitely better than manual Need tutorial for making OOG bot it will make our life easier

Li Mengpai is the WQ starter and what happens there (as opposed to other NPCs) is that a check is run if there is another WQ pending.
Function is in player.ahk:

166	isQuestAvailable(questId) {

It's called from Jawq.ahk:

395	if (player.isQuestAvailable(npcs[itemId].getQuestId(player.level)) > ER_NOERROR) {

My best bet is that offset for "CallIsQuestAvailable" in Jawq.ini is wrong, so whenever this address is called, client crashes.

Until you get the offset corrected, you can modify player.ahk to prevent crashes.
Open player.ahk, go to line 167 and comment it out.
After that line add "return 0"

Before modification:

166	isQuestAvailable(questId) {
167		return DllCall("PwInterface\IsQuestAvailable", UInt, questId, Char, this.instanceId)
168	}

After modification:

166	isQuestAvailable(questId) {
167		; return DllCall("PwInterface\IsQuestAvailable", UInt, questId, Char, this.instanceId)
168		return 0
169	}

This will prevent a call to wrong address and avoid crashing client.
Since return value of 0 signals a new WQ in waiting, bot will continue doing a new WQ (if available), or report error after failing to get new quest.

But it would no longer crash client.

[binz]

Originally Posted by Shareen

My best bet is that offset for "CallIsQuestAvailable" in Jawq.ini is wrong, so whenever this address is called, client crashes.

Until you get the offset corrected, you can modify player.ahk to prevent crashes.
Open player.ahk, go to line 167 and comment it out.
After that line add "return 0"

Before modification:

166	isQuestAvailable(questId) {
167		return DllCall("PwInterface\IsQuestAvailable", UInt, questId, Char, this.instanceId)
168	}

After modification:

166	isQuestAvailable(questId) {
167		; return DllCall("PwInterface\IsQuestAvailable", UInt, questId, Char, this.instanceId)
168		return 0
169	}

This will prevent a call to wrong address and avoid crashing client.
Since return value of 0 signals a new WQ in waiting, bot will continue doing a new WQ (if available), or report error after failing to get new quest.

But it would no longer crash client.

Thanks for your advice

So we need to modify the source code or finding the right address.
Never write a code in AHK, so I'm trying it now When i try to compile the source code, there is an error :

Error at line 1 in #include file "...\lib\iniFile.ahk"
Line Text: class TIniFile{
Error: This line does not contain a recognized action

is there any config file we need to setup?
Thx in advance

PS Smurfin : OOT the framework for OOG is either in delphi or C#. It's been years ago I used Delphi

[Smurfin]

binz, you and i use the same offsets, if I remember correctly you're playing pw indo too, right ? or do you play pwi ? can anyone from pwi post your offset list ?

If pwi and pw indo have the same offsets, I want to download pwi client and use it, pw indo client has horrible indo localization, everything is so messed up.

-edit-
I just tried it and it worked just like what binz said, always crash (can be prevented later using Shareen's instruction later) at taking the quest from Li MengPai/Antonio, I'll post again later when finished.

Is there any way to use auto teleport ? It's been a few years and noone hasn't have the info on auto teleporting, maybe by using packet or something, teleport point has ID too, like itemID.

-edit-

Got crashed when talking to the npc for getting reward, same as what binz was having. I'll try what Shareen suggested later, or if anyone has the correct isQuestAvailable call please post it here.

-edit-

No crash after changing the line which Shareen suggested. Thanks.