[Open Source] Lucky's Spacebot

[jstine]

it is still not finding the play buttons. if it were my aspect ratio, which im unsure of because the other 99% of the program works, how do i tell if so and rectify the situation?

should my desktop resolution be 1024x768 too? and im on a laptop if that makes any difference.


the really frustrating part is that the bot WILL find the play button on a failed mission restart, ive just retested this on kovor; it failed twice, so it logged out the char, and logged back in fine to retry. its just not finding the play button after a game restart when it quits out from the timer addition.

[TMichael]

it is still not finding the play buttons. if it were my aspect ratio, which im unsure of because the other 99% of the program works, how do i tell if so and rectify the situation?

should my desktop resolution be 1024x768 too? and im on a laptop if that makes any difference.

Your resolution should be greater than 1024x768 both horizontally and vertically. SWToR doesn't properly detect your actual desktop resolution, so you'll find many of the resolution choices will cause your client to stretch one way or the other. It might be best to simply experiment to see which resolutions make the 1024x768 window look correct.

That being said, I'm not convinced that's your issue. It was just a shot in the dark. Essentially, *if* your screen is perfectly positioned, sized, and has the proper aspect ratio, and *if* those images match up well enough with what shows up on your screen, and *if* you're using Aero, then it should simply work. I'm still at a loss as to why you're having this issue...

[mrmr]

[Bug Report]
The bot get stuck checking for "credits"

To reproduce this, open the game, open the bot. Focus game window and open "Crew Management" window (usually N).
At this point, with "credit check" option enabled, start the bot with any mission.

The Inventory will be open/closed continuosly (not finding what the bot is looking for...I presume).


And now, another tricky one.
Why with r236 I can start Sullust just fine (with tolerance 103) and with r244 there's no way to make it start (tolerance from 95 to 107)?
Same pictures (I don't think you changed them...)

[TMichael]

[Bug Report]
The bot get stuck checking for "credits"

To reproduce this, open the game, open the bot. Focus game window and open "Crew Management" window (usually N).
At this point, with "credit check" option enabled, start the bot with any mission.

The Inventory will be open/closed continuosly (not finding what the bot is looking for...I presume).


And now, another tricky one.
Why with r236 I can start Sullust just fine (with tolerance 103) and with r244 there's no way to make it start (tolerance from 95 to 107)?
Same pictures (I don't think you changed them...)

Thanks for the report! I'll add a check for the crew window in the next revision. Per Sullust, that one hasn't been touched in a long while - make sure none of your settings have changed from the norm.

Also on my work list for the next revision:

• After a client crash, having the starter resume the current Run Time, instead of resetting it, so that the Off Time can occur more or less on schedule
• Making Run Time functional with dailies and crew skills - currently, it only initiates after clicking a space mission button

[jstine]

Your resolution should be greater than 1024x768 both horizontally and vertically. SWToR doesn't properly detect your actual desktop resolution, so you'll find many of the resolution choices will cause your client to stretch one way or the other. It might be best to simply experiment to see which resolutions make the 1024x768 window look correct.

That being said, I'm not convinced that's your issue. It was just a shot in the dark. Essentially, *if* your screen is perfectly positioned, sized, and has the proper aspect ratio, and *if* those images match up well enough with what shows up on your screen, and *if* you're using Aero, then it should simply work. I'm still at a loss as to why you're having this issue...

There seems to be some odd things going on that I've come across:

For some reason the latest download comes with 2 versions for the bot, "Luckys Spacebot" and "Luckys_Spacebot", both R44 but 2 different revision times and file sizes.

For the area where clicking the play button works after it fails a mission and logs out, the code is thus (i think this is the right area):

; sometimes it drops back to Char selection ... (swtor1.3)
$r=_Imagesearcharea("pictures/play1.png",1,950,600,1030,740,$x,$y,$tolerance )
$r2=_Imagesearcharea("pictures/play2.png",1,950,600,1030,740,$x,$y,$tolerance )
$r3=_Imagesearcharea("pictures/play.png",1,800,600,1030,740,$x,$y,$tolerance )

It's using the image "play1", "play 2", and "play", whereas the char login area code, which is not working:

Find the in-game play button at charselect
Local $x_gplay, $y_gplay, $iterations
Local $maxgplaywait = 45 ; seconds to wait beyond the first 12

$iterations = $maxgplaywait * 2

EventDelay(12000)

WinActivate("Star Wars™: The Old Republic™","")

Do
$gplaybutton=_ImageSearchArea("pictures/gplay.png", 1, 940, 625, 1030, 670, $x_gplay,$y_gplay, $tolerance)
If $gplaybutton= 0 Then
$gplaybutton=_ImageSearchArea("pictures/gplay2.png", 1, 940, 625, 1030, 670, $x_gplay,$y_gplay, $tolerance)
EndIf

This is trying to use the images "gplay" and "gplay2".

Also, I noticed that the capitalization between the two aren't matched up either. Code block 1 has "Imagesearcharea", whereas block 2 is using "ImageSearchArea". Could this be a problem?

What about the numbers that come after the image file name? They don't match up either, could this be why it can't find the gplay buttons?

[jstine]

i went ahead and changed out the code from block 1 into block 2 and now so far it seems to be working...

changed "ImageSearchArea" to "Imagesearcharea"
changed the file image from "gplay.png" to "play1.png"
changed "1, 940, 625, 1030, 670, $x_gplay,$y_gplay, $tolerance)" to "1,950,600,1030,740, $x_gplay,$y_gplay, $tolerance)"

[TMichael]

...

For the area where clicking the play button works after it fails a mission and logs out, the code is thus (i think this is the right area):

; sometimes it drops back to Char selection ... (swtor1.3)
$r=_Imagesearcharea("pictures/play1.png",1,950,600,1030,740,$x,$y,$tolerance )
$r2=_Imagesearcharea("pictures/play2.png",1,950,600,1030,740,$x,$y,$tolerance )
$r3=_Imagesearcharea("pictures/play.png",1,800,600,1030,740,$x,$y,$tolerance )

...

Also, I noticed that the capitalization between the two aren't matched up either. Code block 1 has "Imagesearcharea", whereas block 2 is using "ImageSearchArea". Could this be a problem?

What about the numbers that come after the image file name? They don't match up either, could this be why it can't find the gplay buttons?

I'm glad you got to the bottom of it!

The code you used was the original play code - the two snippets do essentially the same thing (which means I'll make one of them go away), except of course that the original has a larger search area (which is why the numbers are a bit different) as well as a third search image.

This probably means you do have an aspect ratio issue, but regardless, since it fixes the issue for you, I'll implement the same change in the next revision.

The capitalization is just a bit of sloppy coding left over from previous versions, but it has no effect on code execution in AutoIt, so no worries there.

Lastly, per the file names, use Luckys_Spacebot.au3 for any custom editing since that has the latest code revisions.

[jstine]

i let it run for a few hours, it did 19 wins 2 losses but then i came back to an error box at line 16946, not sure if thats anywhat significant. the client was closed out so not sure what the nature of the crash was, but it didnt restart the game.

[TMichael]

i let it run for a few hours, it did 19 wins 2 losses but then i came back to an error box at line 16946, not sure if thats anywhat significant. the client was closed out so not sure what the nature of the crash was, but it didnt restart the game.

Do you remember what the error message said?

[vaelis]

is there any way to lengthen the amount of time the bot looks for the play button upon restarting? Im VM seems to take forever to load the client when logging in, and the bot gets stuck in a loop of closing and reopening the launcher


Luckys Spacebot v5.35 x86 (R244)

System details: X64 CPU, WIN_7(X86) Service Pack 1
RAM total:2 GB,free:0 GB, used:66 %
Desktop dimensions: 1626x986(32bpp, 60Hz)
Desktop theme: Aero using NormalSize, NormalColor, 96dpi

SWTOR Client is running with 1024x766
SWTOR Window:0,0 Win size:1040x804
Color scheme: Aero

On Target Time=50
Missile Delay=333
Timer Skew =50
IMG Tolerance=106
HD Status=0
Timing override=4
Mission bonus=4
PSX OTT enabled=1
PSX DBG enabled=4
Last mission=Aeten Defense
Win / Loss 107 / 0

[TMichael]

I was just about to commit the next revision, so you have very good timing. I will just double all the StartGame() button search times; for those concerned, this will not stop the script from progressing immediately once the button is found.

[TMichael]

UPDATE R245

HIGHLIGHTS

• Game client crashes will no longer cause the session Run Time to restart - no more missing out on your session Off Time

Changelog:

• Modified the inventory credit search to include a second search area in the event that another window, such as Crew Skills, is open (request)
• Inventory credit search will now time out after three attempts so the script can continue in the event of an error
• Run Time is no longer being reset after game client crashes, which means Off Time will no longer have its starting time rudely interrupted; barring internet disconnects, the game should now always close and restart as expected
• Added two additional character select play button images and expanded the play button search area slightly (request)
• Increased search time for the launcher play button (120 seconds) and character select play button (90 seconds); the script will still progress immediately as each image is found (request)
• Replaced more Sleep calls with the new EventDelay() function; the bot may now be closed while space missions are loading
• Fixed a display bug in off time -> return time -> minutes which only occurred when the hour field read "12"

This latest revision is now available for download. Enjoy.


COMING SOON

• 24 Hour Run Time Schedule - have even more control over when your bot runs and closes

[Darkbounded]

An issue that I had yesterday: Since I am runing them inside VMs things are little more laggy, and now I have a different ISP and it may also be causing some delays... so the issue is that after it opens the launcher it takes veeeeeeeeery long time until the Play button "lightens up" and I'm guessing that the restarter is "timing out" on waiting for that button and it gets in launcher restarting loop so maybe you should increase that "waiting time" there or think out some other way to fix this issue)

[noob766]

An issue that I had yesterday: Since I am runing them inside VMs things are little more laggy, and now I have a different ISP and it may also be causing some delays... so the issue is that after it opens the launcher it takes veeeeeeeeery long time until the Play button "lightens up" and I'm guessing that the restarter is "timing out" on waiting for that button and it gets in launcher restarting loop so maybe you should increase that "waiting time" there or think out some other way to fix this issue)

do a sleep loop on the login screen splash, and on the dark play button and it will fix the issue. Had the same problem with my starter

[buildsflyingcars]

One request I have is to be able to input the 5 security questions/answers into the start up script.