[Open Source] Lucky's Spacebot

[Breathofthedying]

Any chance you are working on a work around for the current problems with the bonus in Aeten? It was working until the last major patch and has not been able to complete the bonus since then. Would be nice if the developers could work on this. 50% more credits is significant.

Aeten and many other Emp missions are nasty because of color. I had an experimental mission code set a few dozen pages back that was working in the high90s%. Clouds as well. Then after 1.4 certain days they are a mess.... And certain reboots made them 99% til power down. I never figured it out... It makes no sense... I figure I was crazy and took a break. Your welcome to them look back like 20-50 pages.

[Breathofthedying]

Aeten and many other Emp missions are nasty because of color. I had an experimental mission code set a few dozen pages back that was working in the high90s%. Clouds as well. Then after 1.4 certain days they are a mess.... And certain reboots made them 99% til power down. I never figured it out... It makes no sense... I figure I was crazy and took a break. Your welcome to them look back like 20-50 pages.

The long and short of my coding Is this: I attempted to add about 6 times the target attack calls to make the target boxes as tight as possible..... But.... Something tron warned me about was happening... The more I was telling it to target smaller boxes. The more boxes I needed to tell until it got to points the multiple events were colliding And no efficiency was gained. If you understand my bad English and warped script description.... Run with it.


The way I have been seeing the market is more people are selling credits then paying the game.

EA.

[TMichael]

Any chance you are working on a work around for the current problems with the bonus in Aeten? It was working until the last major patch and has not been able to complete the bonus since then. Would be nice if the developers could work on this. 50% more credits is significant.

If you would like to improve color recognition on your own computer, a custom solution might do the trick. Here's what's required.

1 ) Download and install the latest version of AutoIt.
2 ) Take a few mission screenshots which clearly show each target type (bombers, ships, turrets, etc).
3 ) Open your screenshot file, zoom in on the target, and find the best representative color you can using the color picker (eye dropper).
4a ) If in Photoshop: Clicking on the color in the color tab will bring up the color picker window, which will display the hexadecimal representation of the color.
4b ) If in Paint: Click on Edit Colors, and then choose Add to Custom Colors. This window will now show you the Red, Green, and Blue value of the color. Go to this website, enter those numbers into the appropriate fields, click on the RGB -> CMYK button, and the hexadecimal notation for the color will be displayed.
5 ) Open the Aeten.au3 mission file in the AutoIt editor, and scroll down to the the attack function. You will see a series of lines like this one for each target type:

$targ = PixelSearch($x1, $y1, $x2, $y2, 0xFFD629, $gtolerance)  ; yellow-orange

6 ) Replace the appropriate hex value(s) in the code, shown in red above, with your new hex value(s).
7 ) Save the file.
8 ) In the main Lucky's folder, right click on Luckys_Spacebot.au3 and choose Compile Script (x86).
9 ) Run your newly compiled space bot and see if there is any improvement in target recognition.

The long and short of my coding Is this: I attempted to add about 6 times the target attack calls to make the target boxes as tight as possible..... But.... Something tron warned me about was happening... The more I was telling it to target smaller boxes. The more boxes I needed to tell until it got to points the multiple events were colliding And no efficiency was gained. If you understand my bad English and warped script description.... Run with it.

Yes, in general, the more attack/search calls you add, the more slowly they perform.

[eibtech]

I just have to say that this build alone is just amazing. Well done!

I have it set to restart the game client after every 10 missions since crashing would vary between 13 & 23 wins. Doing so I hope will resolve the crashing. Testing overnight, will update when I wake up.

Well I got to enjoy it for a couple days atleast. Got dinged today while at work. Guess ill have to enjoy a week off

[eibtech]

FYI, I was running 57 minutes with a 10 minute variance on run time and a 1 minute with 3 minute variance on off time. Funny how they didn't ding me while max leveling my first toon, but the second toon I just started on this morning in space and I get raped.

[eibtech]

Just a suggestion TM,

Is there anyway for you to change the process name that is listed in task manager for the bot? Just in case they snapshot your processes, since it shows the full application name. If it's a thing of knowing what the application is for those that are less informed, maybe moving Changelog, Copying, Disclaimer, Public License to a 'docs' directory and setting common, imagesearch, and the lucky's script with a hidden attribute. That way it limits the possibilities of confusion. Now what to mask the process as, maybe something simple like svchost.exe that way no one looking at the processes would know the difference? I'm trying to think of different ways to cover tracks in the case that ToS decides to play their cards. I'm fighting with them over email which is kind of fun

[eibtech]

If you would like to improve color recognition on your own computer, a custom solution might do the trick. Here's what's required.

1 ) Download and install the latest version of AutoIt.
2 ) Take a few mission screenshots which clearly show each target type (bombers, ships, turrets, etc).
3 ) Open your screenshot file, zoom in on the target, and find the best representative color you can using the color picker (eye dropper).
4a ) If in Photoshop: Clicking on the color in the color tab will bring up the color picker window, which will display the hexadecimal representation of the color.
4b ) If in Paint: Click on Edit Colors, and then choose Add to Custom Colors. This window will now show you the Red, Green, and Blue value of the color. Go to this website, enter those numbers into the appropriate fields, click on the RGB -> CMYK button, and the hexadecimal notation for the color will be displayed.
5 ) Open the Aeten.au3 mission file in the AutoIt editor, and scroll down to the the attack function. You will see a series of lines like this one for each target type:

$targ = PixelSearch($x1, $y1, $x2, $y2, 0xFFD629, $gtolerance)  ; yellow-orange

6 ) Replace the appropriate hex value(s) in the code, shown in red above, with your new hex value(s).
7 ) Save the file.
8 ) In the main Lucky's folder, right click on Luckys_Spacebot.au3 and choose Compile Script (x86).
9 ) Run your newly compiled space bot and see if there is any improvement in target recognition.

Yes, in general, the more attack/search calls you add, the more slowly they perform.

What's the possibility of just having multiple screenshots of each item at different angles that you would ever kill in one specific mission and then having it scan the entire window for those items, does something like this just make it crash? Sometimes the PixelSearch picks up on planets/stars/blasters so I see this possibly being an issue regardless of the colors people specify. Maybe a double check to confirm..

PixelSearch() = True && ImageSearch() = True : if(ImageFound(turret/bomber)) fire missiles and blasters ELSE fire blasters

Of course my lil equation lacks guts, but the idea is the point

[deadlybot]

Anyone know why my swtor screen is flashing rapidly while using the 5.35 HD bot ? I am using Vmware. Any help would be appreciated.

[TMichael]

Just a suggestion TM,

Is there anyway for you to change the process name that is listed in task manager for the bot? Just in case they snapshot your processes, since it shows the full application name. If it's a thing of knowing what the application is for those that are less informed, maybe moving Changelog, Copying, Disclaimer, Public License to a 'docs' directory and setting common, imagesearch, and the lucky's script with a hidden attribute. That way it limits the possibilities of confusion. Now what to mask the process as, maybe something simple like svchost.exe that way no one looking at the processes would know the difference? I'm trying to think of different ways to cover tracks in the case that ToS decides to play their cards. I'm fighting with them over email which is kind of fun

I do this myself. You can rename the .exe before running it and everything will work just fine.

Unfortunately, I think their detection method involves observing your missions - and they know what Lucky's missions look like - so more than anything else, it's the timing of your runs I think.

What's the possibility of just having multiple screenshots of each item at different angles that you would ever kill in one specific mission and then having it scan the entire window for those items, does something like this just make it crash? Sometimes the PixelSearch picks up on planets/stars/blasters so I see this possibly being an issue regardless of the colors people specify. Maybe a double check to confirm..

PixelSearch() = True && ImageSearch() = True : if(ImageFound(turret/bomber)) fire missiles and blasters ELSE fire blasters

Of course my lil equation lacks guts, but the idea is the point

The problem with ImageSearch is twofold. First, because the ship is constantly moving in a 3D environment, the shape, size, and even color of the ships as they maneuver varies way too much. Secondly, ImageSearch is too slow to be of much help in targeting during missions.

This is one idea I've thought about, but it turned out to be unworkable.

Anyone know why my swtor screen is flashing rapidly while using the 5.35 HD bot ? I am using Vmware. Any help would be appreciated.

Are you using VMWare Workstation 8, with Windows 7 x86 as the VM operating system? If yes to both, then post your SysInfo here and we'll see if we can help.

[deadlybot]

I am running vmware 8 and winxp and have been using 5.32 up until the crashing started. With the new 5.35 HD version the rapid fluttering of the swtor window started and missions start but do not complete and then go to the character screen from being idle.

Luckys Spacebot v5.35 x86 (R257)

System details: X64 CPU, WIN_XP(X86) Service Pack 3
RAM total:2 GB,free:1 GB, used:51 %
Desktop dimensions: 1920x1080(32bpp, 60Hz)
Desktop theme: Custom

SWTOR Client is running with 1032x770
SWTOR Window:0,0 Win size:1040x804
Color scheme: Basic

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


Edit: Thank you for helping

[deadlybot]

Oh, I tried the calibrate function and also resize and restarted everything.

[deadlybot]

Are you using VMWare Workstation 8, with Windows 7 x86 as the VM operating system? If yes to both, then post your SysInfo here and we'll see if we can help.

System details: X64 CPU, WIN_XP(X86) Service Pack 3

With the newer versions of the bot am I supposed to be using windows 7 with vmware 8 now ? could this be my problem ?

[eibtech]

I do this myself. You can rename the .exe before running it and everything will work just fine.

Unfortunately, I think their detection method involves observing your missions - and they know what Lucky's missions look like - so more than anything else, it's the timing of your runs I think.

I was thinking about this as well, problem is I dont understand why they dinged me when running Sarapin today when leveling up my marauder vs. the non-stop botting for the past week on Aetan Defense, especially after getting the latest build and with the latest build I was using variances to offset the times so it would lessen the awareness. One thing I was thinking was making the bot just kill the client process tree instead of exiting the program either by closing the client window or exiting the game via ESC menu like normal to give off the 'crash to desktop' instead of a quit/restart/play cycle. Definitely going to change the executable to a less recognizable name.

[eibtech]

System details: X64 CPU, WIN_XP(X86) Service Pack 3

With the newer versions of the bot am I supposed to be using windows 7 with vmware 8 now ? could this be my problem ?

The bot needs to be run on the Aero Desktop feature enabled, which means that yes you need to have Windows 7 regardless of vmware or not. As for the version of VMware, I know there are a ton of posts on this forum especially in the past month that will help you out.

[deadlybot]

The bot needs to be run on the Aero Desktop feature enabled, which means that yes you need to have Windows 7 regardless of vmware or not. As for the version of VMware, I know there are a ton of posts on this forum especially in the past month that will help you out.

ahhh easy enough to fix then, thankyou.