[RELEASE] Jawq (WQ bot for PWI)

make a refining hack :cool:

Quote:

Originally Posted by prodiac1 Anybody have an updated offsets set for this script?

The last I see is for 729 but I think the latest update is 748, no?

I've followed all the directions down to the letter, 32bit .bin file, etc etc etc, and it crashes every time. Win7 x64bit, tried 32 bit compiler and 64 bit compiler as well. "Jawk.exe has stopped working", and yes I ran it as Admin. I'm pretty sure the offsets are, well, off. Or something else is off.

Tried the offsets on the previous page, and after a reboot, at least it doesn't crash as before, but it gives error code 17. Still trying to get it to work.

Log file: Locking target Li Mengpai
[22.10.2013 09:49:57] >
Error occured, instance stopped

Update: Still troubleshooting. It seems it can navigate to where the NPC is through the air or on the ground, but mounting flying pet is giving it trouble, and if it can't get right up to the NPC it throws an error, which is what I've been getting, I guess.

Not sure what the error is, but it's having trouble mounting flying pet before continuing on the quest. I've edited the source code to manually focus the window and manually mount the pet before continuing, and while I don't like that solution, I'm not familiar enough with AutoHotKey to implement anything else.

Quote:

Originally Posted by zerosmoke I've followed all the directions down to the letter, 32bit .bin file, etc etc etc, and it crashes every time. Win7 x64bit, tried 32 bit compiler and 64 bit compiler as well. "Jawk.exe has stopped working", and yes I ran it as Admin.

Work fine for me with PWI and I have 64 bit win 7. You need to make the exe file first and change something at the settings from the exe software. I wrote what to change at one of the first messages from me here. Just take a look, I can not remember me what to change.

One moment, I take a look myself what I wrote.

OK, you need to compile it with 32 bit Unicode settings. Other do not work(ed for me).

Quote:

Originally Posted by martmor Work fine for me with PWI and I have 64 bit win 7. You need to make the exe file first and change something at the settings from the exe software. I wrote what to change at one of the first messages from me here. Just take a look, I can not remember me what to change. One moment, I take a look myself what I wrote. OK, you need to compile it with 32 bit Unicode settings. Other do not work(ed for me).

I'm past that actually. Way past that. Everything is working except we're having issues with the mounting flying pet in the script. Instead of mounting, the character starts running in place. Is yours currently working and what offsets are you using?

Here's the problem code, or where the problem is (for me)

if (action.type = "flyUp") {
myForm.controls["playerBlock" . player.instanceId].lblStatus.caption := "Status: Mounting flying

pet"
result := player.flyUp(action.position.z)

player.logWrite("Executing action flyUp, target altitude " . action.position.getClientHeight())
}

Ok, the only way I could get it to work, foolproof, every time, was to add a controlsend command to manually mount flying pet, right before NPC interaction. That seems to be one of the only entry points to control the mount before the character is locked for NPC interaction, and every attempt I've made to mount after the NPC interaction has failed due to the code structure.

I'm satisfied with the workaround, I guess I'll just stick to this until it's updated.

I'm using this Jawq and it works perfectly until the character needs to interact with the NPC. after flying and land, jawq show an error :
"Status : Error Occured, code: 17. Instance Stopped".

when I check in the logs, the last successfull action was :
> Executing action interact: Locking target Guard Autumnland
[23.10.2013 02:09:39] > Error occured, instance stopped:
[23.10.2013 02:09:39] > action code: 0
[23.10.2013 02:09:39] > error code: 17

And the NPC is not locked.

I'm using this offset :
CallSendPacket=0x006F55E0
CallIsQuestAvailable=0x007F2C00
BaseAddress=0x00C38B6C
BaseOffset=0x1C
PlayerStruct=0x34
PlayerId=0x494
PlayerLevel=0x4A0
PlayerName=0x688
PlayerTransportMode=0x69C
PlayerFlyMountId=0x5AC
PlayerPositionX=0x3C
PlayerPositionZ=0x40
PlayerPositionY=0x44
PlayerTargetId=0xC88
PlayerFreeze=0xCA6
PlayerQuestInventory=0xE54
PlayerAction=0x1290
PlayerQuestList=0x1298
ItemId=0x08
Lists=0x1c
NpcList=0x24
NpcSortedList=0x58
NpcId=0x1244

Quote:

Originally Posted by gdimazp I'm using this Jawq and it works perfectly until the character needs to interact with the NPC. after flying and land, jawq show an error : "Status : Error Occured, code: 17. Instance Stopped". when I check in the logs, the last successfull action was : > Executing action interact: Locking target Guard Autumnland [23.10.2013 02:09:39] > Error occured, instance stopped: [23.10.2013 02:09:39] > action code: 0 [23.10.2013 02:09:39] > error code: 17 And the NPC is not locked. I'm using this offset : CallSendPacket=0x006F55E0 CallIsQuestAvailable=0x007F2C00 BaseAddress=0x00C38B6C BaseOffset=0x1C PlayerStruct=0x34 PlayerId=0x494 PlayerLevel=0x4A0 PlayerName=0x688 PlayerTransportMode=0x69C PlayerFlyMountId=0x5AC PlayerPositionX=0x3C PlayerPositionZ=0x40 PlayerPositionY=0x44 PlayerTargetId=0xC88 PlayerFreeze=0xCA6 PlayerQuestInventory=0xE54 PlayerAction=0x1290 PlayerQuestList=0x1298 ItemId=0x08 Lists=0x1c NpcList=0x24 NpcSortedList=0x58 NpcId=0x1244

Looks like an extra 4 on that last number for the NpcId, that could be your problem. '124'

gdimazp, correct NpcId offsets, like zerosmoke said, that's your only problem.

zerosmoke, your problem is fly pet mount and dismount, both are the same actions.

If you have the tools to compile, I assume you installed AutHotKey.
If so, what happens if you run non compiled script?
What does the log say after failing to mount pet?

Reposted offsets by gdimazp (dixgen before that) are correct for the latest INT version, apart from NpcId as already mention by you, only gdimazp got that wrong.

Edit: I have mistakenly given credit for latest offset to Martmor. They were in fact posted by dixgen. I have corrected the mistake in my original post.

If I run non-compiled script I get the same errors mentioned in the first post, as expected. I don't remember what the log said after failing to fly. I posted it earlier in an earlier post on this thread, but I've spent too much time already trying to make it work, so I'll just stick with what I've got, it works 100% without fouling up on me.

wow thanks a lot guys. It worked. I didn't notice the "4" on the NPCID offset.

thank you, really appreciate it.

Quote:

Originally Posted by zerosmoke If I run non-compiled script I get the same errors mentioned in the first post, as expected. I don't remember what the log said after failing to fly. I posted it earlier in an earlier post on this thread, but I've spent too much time already trying to make it work, so I'll just stick with what I've got, it works 100% without fouling up on me.

There is one bug I noticed and that is that the result of flyUp operation is never tested for failure.
This would mean that the error code you are getting is from failure on operation that comes after, namely flyUp.

I'll fix this, so that pet mount/dismount is also tested for failure and it should give a more specific error code.
Obviously this change alone will not fix your problem, but it should hopefully give a better understanding of what the problem is, provided you are willing to try.

Quote:

Originally Posted by Shareen There is one bug I noticed and that is that the result of flyUp operation is never tested for failure. This would mean that the error code you are getting is from failure on operation that comes after, namely flyUp. I'll fix this, so that pet mount/dismount is also tested for failure and it should give a more specific error code. Obviously this change alone will not fix your problem, but it should hopefully give a better understanding of what the problem is, provided you are willing to try.

Well, here's the thing: With ControlSend I can send the manual 'mount flying pet' hotkey to the client with the client minimized. Basically, I have it set to dismount when the land command is sent, and I have the character remount just before NPC interaction, so that when interaction is over, the character rises into the air and continues on its way without having to remount. That way it eliminates any failure from trying to send the flyUp or flyOn commands to the client via the dll. If the script works for everyone else as it is, unmodified, that's great, don't worry about it. I'm one of those guys that says 'if it ain't broke, don't fix it'.

However, if you want me to help troubleshoot for Windows 7 x64, sure, I'll give it a shot. One of the most annoying things during testing was having to wait for every trip to every NPC to end so that the issue could be tested again, and I'm not used to that kind of waiting while testing my scripts, so it wore on me a bit. That's why I'm just glad my workaround does what it needs to do.

Quote:

Originally Posted by zerosmoke ... If the script works for everyone else as it is, unmodified, that's great, don't worry about it. I'm one of those guys that says 'if it ain't broke, don't fix it'.

It works for everyone else, but it is broke, at least the error handling part :)
Besides, it's a mystery and I like that.

Quote:

Originally Posted by zerosmoke ... However, if you want me to help troubleshoot for Windows 7 x64, sure, I'll give it a shot.

I do, but it has nothing to do with Win 7 x64, I'm using it as well without these problems, as I'm sure, many others.

Quote:

Originally Posted by zerosmoke ... One of the most annoying things during testing was having to wait for every trip to every NPC to end so that the issue could be tested again, and I'm not used to that kind of waiting while testing my scripts, so it wore on me a bit. That's why I'm just glad my workaround does what it needs to do.

This is really the least of the problem. Either a custom testing script can be written to test only specific action or a debug mode can be added to an existing bot framework to provide the same functionality.

Debug mode could in fact be useful for offset testing as well, might go with that.

Quote:

Originally Posted by zerosmoke Well, here's the thing: With ControlSend I can send the manual 'mount flying pet' hotkey to the client with the client minimized.

Sounds like an interesting idea. I was also tring this but without success. I was trying something like this:
ControlSend, ??? , {6}, %winTitel%

But i couldnt figure out, what to send as 2nd parameter "???".
Could you help me out with that please?

finally, now it work perfectly on PW indo update evolution

then pls write here the correct offsets for others. thanks