The co-ords in the script are like this:
the code says to push "right" down, then sleeps for however long you want to have the "right" key down, then you send right up to stop.
for example
Send ("{right down}")
sleep (150)
Send ("{right up}")
Would be the equivalent to pushing d for 0.150 seconds. (1000=1sec)
so when making your own nav, just go into a BG and write down what you do, like turn right, run forward for 10 seconds or so, turn left. etc. run it and tweak it.
A lot of the commands are staight forward, like Send ("{NUMLOCK}") would be to run forward.
If you want to get fancy, use Auto-it's mouse co-ords tool to click on your action bars to buff up, making the illusion more real the you're there. For example my personal one clicks fel armor and mounts up on some of the BGs.
Hope that helps.
When do you think it will be done?
Updated one:
EDIT: Additions have been added to OP !
This one has:
Deserter mode
All navs (albeit, some are still buggy)
40 minute reset (incase of being kicked)
And remember folks full credit to =Z=, I just added a few tweaks.
Last edited by drek2; 10-09-2009 at 02:12 PM.
Yeah, I'm all for people adding on to this, that's why I made it open source, I don't want to take all the credit, I just created the initial framework, plus it helps people learn to code autoit which is useful for all kinds of awesome stuff.
Good job Drek, the additions you've made look pretty good.
I've cleaned up your code and changed a few minor things (I re-added in the input box for nav, some people may not want to navigate because it's too laggy or unpredictable on their system.... as a rule of thumb you should never remove anything that adds functionality even if you consider it useless, just comment it out on your own copy).
Also, what side did you do your nav routes on Drek, because the alliance and horde starting areas for most bgs are slightly different, have you tested them on both?
Anyways, I've reposted the newest version in the OP.
Last edited by =Z=; 10-09-2009 at 12:12 PM.
Open source is the shit!
hey drek2.... your newest auto-it with NAVs doesnt seem to find the join battle button for me? what am i doing wrong? Im using maximized-window 1280x1024 as usual (used it in =Z='s original release!)
=Z= your tweak of drek2's config doesnt seem to find battle button either![]()
Last edited by Xsty; 10-09-2009 at 12:26 PM.
The queue code was not even touched so it should have absolutely no effect on join battle at all, chances are you're standing in an area with too much red on the screen and its messing up the detection, I just tested the code myself and it found the join battle button no problem.
Last edited by =Z=; 10-09-2009 at 12:41 PM.
I'm not sure why it wouldnt be working, as I said, nothing in that respect was changed, try tweaking the coordinates here:
;Join function - detects enter battle button and joins BG
Func Join()
ToolTip("Waiting for BG to start", 0, 0) ; displays tooltip in top left corner
while 1=1
$coord = PixelSearch(517, 215, 628, 230, 0xE01308, 100) ;searches for color of join battleground button within 100 variations
make them all slightly larger and it may help.
Last edited by =Z=; 10-09-2009 at 01:31 PM.
Glad I helped =Z=, Also if you downloaded the code again make sure to re-input your co-ords for the join/leave/release if you haven't.
EDIT: And oh ya, navs are for horde.
Last edited by drek2; 10-09-2009 at 02:10 PM.
Awesome, I made sure to +Rep you and added in some credits for you in the source, check the first post for the updated code with your routes + some randomized timers to make things a little less detectable, looking good thus far.
I was planning on making the area where the enter battle button appears user defined (as in the user selects the upper left and bottom right corner of the "scan area" for the enter battle button) but that would probably be just as complicated and likely to screw up a lot of people as it's not very user friendly.
Since my the bot has absolutely no issue on my end finding the enter battle button I'm having a hard time troubleshooting what the problem may be, so if anyone experiencing the problem wants to take a shot at tweaking the coords or maybe increasing the variation number in the pixel search I posted above that may help, give us feedback and I'll be sure to add it in.
I think somewhere in the mix of things, the pixel coords were mixed up. Try changing them fromTo thisCode:while 1=1 $coord = PixelSearch(587, 206, 691, 215, 0xE01308, 100) ;searches for color of join battleground button within 100 variations If Not @error Then MouseMove ($coord[0], $coord[1]) ;move to area coordinates for join button ToolTip("Character has died, respawning", 0, 0) ; displays tooltip in top left corner sleep (2000) MouseClick ("left") ToolTip("Waiting for BG to load for 10 seconds...", 0, 0) ; displays tooltip in top left corner Sleep (10000)
Code:while 1=1 $coord = PixelSearch(517, 215, 628, 230, 0xE01308, 100) ;searches for color of join battleground button within 100 variations If Not @error Then MouseMove ($coord[0], $coord[1]) ;move to area coordinates for join button ToolTip("Character has died, respawning", 0, 0) ; displays tooltip in top left corner sleep (2000) MouseClick ("left") ToolTip("Waiting for BG to load for 10 seconds...", 0, 0) ; displays tooltip in top left corner Sleep (10000)