its runs perfect, grabs every blue\yellow item, gems, ports back to town, BUT then it opens ESC menu, then closes it, then opens again, etcWhy can that happen? Thanks for your awesome work so far!
its runs perfect, grabs every blue\yellow item, gems, ports back to town, BUT then it opens ESC menu, then closes it, then opens again, etcWhy can that happen? Thanks for your awesome work so far!
$Pixel3 = PixelSearch(725,720,770,750,0xDC1D1D,; look for mythic potion (i dunno why u point to 725,720,770 750,the pot is not at the side?(1030,1000,1090,1050,0xCE1C1D)that i find on the bottom .or something i make wrong?
$Pixel3 = PixelSearch(1160,700,1180,730,0xE1B559,1) ; maybe I didn't click resume correctly? Lets look (this pixel is from which window)?
This has been answered numerous times. Look in the main post for the fix....
Those coordinates are not "at the side...". I'm pointing there because thats where the potion is.
Are you running 1920x1080 Windowed Fullscreen? Cause I kinda doubt it...
Last edited by jakesmurf; 06-10-2012 at 12:57 PM.
I am going to stop answering questions that have been asked time and time again and have an answer already within the thread. If you can't read back through a couple pages and see if your problem has already been solved for others, then I cannot be assed to spend my time helping you. Thanks.
Great script, almost working hehehehe... the problem im getting is that right after it resumes the game it already start to "move" but im still in the loading screen (shit internet ftw).. i tried to find the sleep function of that part and change it to 4500 but it didnt change anything so i think im editing the wrong line???
Func JoinGame()
While $ResumeVar < 18 ; as long as I haven't waited 9 seconds for the load to finish
Sleep(4500)
$Pixel3 = PixelSearch(725,720,770,750,0xDC1D1D,; look for mythic potion
If Not @error Then ; if I find the potion,
$ResumeVar = 1 ; reset the backup timer, then end the function. This will cause the entire stack to return back to the $going while, and restart the loop.
$Ready = true
Return
Else
$Pixel3 = PixelSearch(1160,700,1180,730,0xE1B559,1) ; maybe I didn't click resume correctly? Lets look
If Not @error Then ; looks like I'm at the main menu somehow. Lets resume
MouseClick("left", Round(230 * $x_ratio),Round(416 * $y_ratio)) ;button to resume game from main menu
Sleep(2000)
EndIf
$ResumeVar = $ResumeVar + 1
$Ready = False
EndIf
WEnd
If $ResumeVar > 17 Then
$Ready = True
Return
EndIf
EndFunc
Last edited by jakesmurf; 06-10-2012 at 03:10 PM.
Movement is not working with this script v 22a
update
it seems to work now. But had to use the other leave game function.
Update 2
Well the bot gets stuck surprisingly often at teh first 2 encounters and the next game doesn't find entrance to cellar.
Last edited by meta23; 06-10-2012 at 06:59 PM.
Don't know what to tell you. You didn't provide me with any information I can use to help you. All I can tell you is that something isn't working right on your end. If you didn't update the pixelsearch values yourself, then my assumption is that the script is working fine it just can't find something it's looking for on your display.
Lots of fails. Esc problem (fixed with new code), bot sits at main menu for 15 seconds before it clicks resume, picks up white trash items (fixed if i remove gem pickup codes), doesn't detect full inventory (the "inventory is full message doesn't show up for some reason), path to pickup gold is fail (runs into walls)
Last edited by woodyfly; 06-10-2012 at 08:49 PM.
That worked, thx... now the only thing that is still bothering me is that after he kill Sarkoth and pick up the gold he moves the cursor to the number "1" below the first hotkey button, then he moves toward the lamp at the right, back to number "1", and go up a little more. Its losing me ~15 precious seconds every run.
You should probably update the "rare" item color code. It's probably clicking your lamps because your colors are slightly different than mine, AKA your lamp color is the same color my rares are, and your rares are probably brighter yellow than my rares, on your PC. Fixing this will make it run smooth. Running on my PC, with personalized colors, the loot action is very, very quick - never clicks lamps etc. You can fix the hotkey bar clicking by setting $bottom to something like 650. Then FindItem() will ignore the bottom of your screen.
Then your PC needs color code updates. This script is one that I made for myself, and decided to share with others in case they wanted to use it - because properly configured its the fastest Sarkoth script I've tried, and with full features. My script with full looting running takes less time on both cellar open (with full looting) and cellar closed runs than notAres takes according to his posted times - and his are timed with NO looting. If you don't want to put forth 10 minutes of effort to update the script for your own application, then yes, it will not work properly for you and I suggest you run notAres script or one of the many others out right now. The code is solid and stable. If you don't configure it to run for you client though, it won't. This is autoit. It's not an injected bot that is reading an event log so that it works universally. This is also not a predominantly sleep() based script for timing like all the others are. For the other scripts, you have to edit sleep timers. For mine, you have to edit the colors. I don't see what all the fuss is about. Update it, or don't use it. Please don't come in my thread and trash on it because you're not willing to do either.
Last edited by jakesmurf; 06-10-2012 at 10:46 PM.
2.2b is now up. Not much has changed here except a couple under the hood optimizations. The biggest improvement is that I changed ALL pixelsearches to use a variable that is declared at the start of the script. The variables are well documented so it should be easier for yall to update the pixelsearches for the colors of your own system.
Locally, I have 0 issues with it. It perfectly detects join times, leave times, deaths, runs perfect, misses the door maybe 1 out of 100+ runs, never fails to kill, never misses gold, never misses loot, never fails to detect full inventory, never clicks lamps, never wastes more than a half a second or so after the loot phase. Historically, a few of those things would happen for me, but I've worked out all the bugs with redundancies and pixelsearches and emergency loops. If you had updated your values, I would predict performance similar to mine. My run times are about 45 seconds completing open cellar, with looting, and less than 20 seconds for a closed cellar with 99% successes, and 0 instances of leaving it unattended and returning to it doing nothing. I've also left it unattended for 12+ hours at a time, and returned to huge profits and the script still running flawlessly. To be honest, I'm am personally amazed that I even made a script as solid as this one. Any trouble you're seeing, based on my personal experiences with it and familiarity with how robust the scripting is, is because your colors aren't properly configured, you're using a poor pixel choice in your colors (its important to pick a "unique" looking pixel in any search), or you have something else incorrect such as resolutions or some such. In testing, I've even done stuff to try to screw with the script externally and to replicate some of the problems mentioned, and quite frankly, I can't manage that unless I screw with the colors some and break one of the pixelsearches - which causes the kinds of errors you're reporting..