well i found a lil bug nothing bad but it might get other ppl confused, if u have more than 2 clients opened up doing or not doing WQ in my case 1 was doing WQ and the other one wasnt, and when i closed the one that wasnt doing WQ all the names in the Fly WQ window dissapeared but since i left the one that was doing WQ open it was doing the WQ normally but the bot window wouldnt display the name on the right side of the window but it showed the quest # and stuff, it just didnt showed the name the of client that was open when i closed another client.
i didnt try if opening a new client would fix it but plz check that thingy up
I'm sorry, I no longer have the time to update my WQ bot, so it will remain buggy I'm afraid. It was originally intended to give people an idea how to make one, not to actually be used hehe. The source code is provided though, so people are free to change it around to their needs
I'm sorry, I no longer have the time to update my WQ bot, so it will remain buggy I'm afraid. It was originally intended to give people an idea how to make one, not to actually be used hehe. The source code is provided though, so people are free to change it around to their needs
Very impressive bot. Thank you for showing how this should be done, I learned a lot. I tested this on PWI and PW MY, PWI is working with one client WQ-ing. PW MY has similar issues as hibiki123 with more clients WQ-ing at the same time. I am not a programmer and not familiar with ahk, but I am going to check it. Thanks!
I sent it to a friend who has 2 pc's (vista + win7) but he cant get it to work.
He has UAC disabled, uses run as admin, using correct offsets(the ones i use), testing with simple char name, but char names do not appear did i miss a instruction?
I did some more tests and it seems that the NPC's on PW MY are not recognized. The bot flies to the NPC and does not select the NPC itself. PWI is working fine.
@DitDat Does he use a process name changer? To use multiclient one option is to edit jmp instructions in the executable, the other option is to change the name of the process so a second version of elementclient.exe does not detect the first executable running.
Edit: reason for not working is that four lines of code are missing in the automatic detection routine in the ini file. I guess the routine doesn't auto-recognize those offsets.
npcIdOffset
sortedNpcListOffset
baseListsOffset
npcListOffset
I use ntkids oracle bot for my main client what ever i'm doing
I had to do stuff to make it work since mermaid patch (oct 25th 2010) but that has nothing to do with with this wq bot
i used these offsets
I got the same warning from Kaspersy, it is a false positive. I have checked the source code myself for adding it to my own bot project, it's clean as a whistle.