[For Free] Luckys Spacebot

[Ludowitsch]

but guess its more because the swtor client jumps a second from time to time.

Been botting 8 hours a day for the last three weeks and never seen the game skip a second in the middle of a mission. I only have it skip during the first two seconds of a mission. What happens regularly though is that SWTOR changes the fonts very slightly. Different brightness, different character width, different spacing between characters. Hard for the human eye to notice because it's only a pixel and very subtle brightness shifts, but enough to throw off most bots. The really annoying part is that you can't just crank up shade variation, because when doing so the bot will sooner or later start confusing an 8 with a 9, 6, 5 or 3 or even 0.

Even more annoying is the fact that the French mission timer has again a different character spacing than the English mission timer. Haven't checked the German mission timer yet.

What we could really use is the memory address at which the mission time is found, and perhaps a word from the cracks on whether or not reading the game's memory will get you on SWTOR's anticheat's radar. Unfortunately I know jack shit about reversing.

[tulpanda]

For those of you, who saw bot do nothing on some missions here is a tip:
Enable mission log, resize and alpha it to default. Better untrack every quest, so it wont clog screen.

I realised after looking in pictures folder, that bot depends on timer showed in mission log.

[omron]

Attached is my current spacebot edition, providing some updates for making it easier to write / debug a complex mission script. Since I first started with some updated scripts, I needed to add some more global changes which hardly can be edited in in a few. So I guess a special edition will help more than some files, It is based on Lucky's Version 5.31 and it is work in progress.

I found that a bigger image for the mission timer init works better, meaning that now the edited missions will miss the startpoint in 1 or 2 of 10 mission. In this case, after a short delay the mission is aborted and restarts, Maybe imagesearch paramters can be optimized, but guess its more because the swtor client jumps a second from time to time.

For a mission setup you will need to set the mission time, for example 400 secs for Ezran starting at 6:40 and init the mission timer. Now you can wait_until("6:35") to do anything, like issue an attack function like Ezran1("6:20", False) which will fire until 6:20 mission time without using rockets. (Alternatively Ezran1(15000,False) can be used to fire for 15 secs )

A mission control label has been added, with dmsg debug msgs can be issued on the main tab.

The Ezran mission is a quite complex examle for a mission, since I was bored to see it firing into the air after having the main objective complete, I added a dectection if the main goal is reached and some if/then/elses to shoot some additional XP then. (works only for german client - change image ...)

The missions I edited are Jabiim, Sarapin, Ezran and Skaross. Using the available equip for the given level, these missions do succeed at 100% if the start timer doesnt fail. (green will be ok) Sarapin in most cases will succeed with bonus. Mugaar might work with some better equip, aiming here is not as it has to be. All other missions work - or do not work - as with 5.31.

Thanks for your efforts. I'm at 9 wins / 27 losses for Ezran with this version.

[phagotron]

Been botting 8 hours a day for the last three weeks and never seen the game skip a second in the middle of a mission. I only have it skip during the first two seconds of a mission. What happens regularly though is that SWTOR changes the fonts very slightly. Different brightness, different character width, different spacing between characters. Hard for the human eye to notice because it's only a pixel and very subtle brightness shifts, but enough to throw off most bots. The really annoying part is that you can't just crank up shade variation, because when doing so the bot will sooner or later start confusing an 8 with a 9, 6, 5 or 3 or even 0.

Even more annoying is the fact that the French mission timer has again a different character spacing than the English mission timer. Haven't checked the German mission timer yet.

These are handicaps indeed,might be useful to use an img which is some seconds from start then. Good to see that imgsearch works at least in most cases though and still can be improved. Will keep that in mind for the next mission...

[phagotron]

Thanks for your efforts. I'm at 9 wins / 27 losses for Ezran with this version.

That sounds weird ... can u provide info on level, ship equip and more important where it usually fails for u?

[omron]

That sounds weird ... can u provide info on level, ship equip and more important where it usually fails for u?

level 29 with everything I can equip at that level.

It seems to sometimes miss the cue that the mission has started.

I tried disabling the image search but I still die, just later in the mission from damage.

Every once in a while it fails mid-mission due to damage, but 90% of the time it is at mission launch.

oh - and I really like the debug info you added in to the bottom of the bot window. another nice little addition.

[spearfish]

level 29 with everything I can equip at that level.

It seems to sometimes miss the cue that the mission has started.

I tried disabling the image search but I still die, just later in the mission from damage.

Every once in a while it fails mid-mission due to damage, but 90% of the time it is at mission launch.

oh - and I really like the debug info you added in to the bottom of the bot window. another nice little addition.

If your missing the image search try remaking the image on your machine in the same way as the one the mission uses the timer prob is due to the mission load time if you have not loaded in by the timer start then its shooting at the wrong points in the mission then the mission will fail.

[phagotron]

level 29 with everything I can equip at that level.

It seems to sometimes miss the cue that the mission has started.

I tried disabling the image search but I still die, just later in the mission from damage.

Every once in a while it fails mid-mission due to damage, but 90% of the time it is at mission launch.

oh - and I really like the debug info you added in to the bottom of the bot window. another nice little addition.

It should not fail mid-mission. If it does, there is a collision or you dont have mo power converter equipped. But more worse
is the 90% failed starts ... that suxx. It might be some videocard issue, as Ludo mentioned above - the mission starts at
6:40 what may lead to fails then.

To change mission start:

- get a screenie at 6:35 mission time
- cut out the 35, thight but not too tight. (something like old space_ezran1.png )
- save it as space_ezran1.png in pictures folder

edit erzan.au3:
Line 32 change
Until $result=1 Or $timer_diff > 15000 to Until $result=1 Or $timer_diff > 20000

Line 43 change
$mission_secs = 400 ;(6:40) to $mission_secs = 395 ;(6:35)

and last but not least Line 63

Ezran2(30000,False) ; save rockets - 6:00 to Ezran2("6:00",False) ; save rockets - 6:00

to adjust the mission timing.

Recompile.

Hope that helps for mission launch.

If missions still tend to fail due to low health - comment out the AdlibRegister at line 49.

[phagotron]

Been botting 8 hours a day for the last three weeks and never seen the game skip a second in the middle of a mission.

I just kept an eye on the mission timer ..looks as if it is shifted 2 pixel left and back right in a random schedule. Can anyone verify that?

[triranta]

hey
basicly i cant get it to work. its loaded iv followed all the steps to the correct interface ( 1024x768 or somthing like that, graphics on low) and then
it starts when im in front of the chair, it clicks the chair and waits a cupple of seconds ( at this stage my map hasnt loaded) then it continues to choose the mission without the map being there. so ofcorse it doesnt play. by the time the map has loaded the bot has already done the movments to select the correct level and start.

so thats one probs

so i start the bot on the screen that says about the fuel cost ( the last screen) and it clicks play and works but the guy dies at about 50 secs to the end ( this has happend 3 times)
any1 that can give me a hand let me know : )
post on the tread or add email ( [email protected] thanks)

[omron]

It should not fail mid-mission. If it does, there is a collision or you dont have mo power converter equipped. But more worse
is the 90% failed starts ... that suxx. It might be some videocard issue, as Ludo mentioned above - the mission starts at
6:40 what may lead to fails then.

To change mission start:

- get a screenie at 6:35 mission time
- cut out the 35, thight but not too tight. (something like old space_ezran1.png )
- save it as space_ezran1.png in pictures folder

edit erzan.au3:
Line 32 change
Until $result=1 Or $timer_diff > 15000 to Until $result=1 Or $timer_diff > 20000

Line 43 change
$mission_secs = 400 ;(6:40) to $mission_secs = 395 ;(6:35)

and last but not least Line 63

Ezran2(30000,False) ; save rockets - 6:00 to Ezran2("6:00",False) ; save rockets - 6:00

to adjust the mission timing.

Recompile.

Hope that helps for mission launch.

If missions still tend to fail due to low health - comment out the AdlibRegister at line 49.

Thanks so much!

Just changing the image got me to 90%+ completion, I'm making the additional changes now.

[Ludowitsch]

I just kept an eye on the mission timer ..looks as if it is shifted 2 pixel left and back right in a random schedule. Can anyone verify that?

Here's what I have observed (running the game at 1280x720 when botting):



When starting a mission, the timer font looks the way it does. Certain character width, certain spacing between characters. Let's call this "state 1".

As the timer counts down, you'll randomly see the character width change by one pixel. E.g. the number >5<. The bow at the bottom of >5< may be 5 pixels wide when it previously was 4 pixels wide, it may be 4 pixels wide when it previously was 5 pixels wide. This also changed back and forth a couple of times. "State 2".

When the timer reaches dual digits seconds with no leading minutes, spacing between the last second and the letter >s< changes. They go one pixel apart. Always happens. "State 3".

As before, the seconds continue counting down, so you'll likely run into characters changing their width again. "State 4".

The timer will eventually turn red. "State 5".

Even when red the character width changes back and forth irregularly. "State 6".

As the red timer reaches single digit seconds, the spacing between >s< and the seconds digit changes by one pixel. "State 7".

You may have guessed it, even during the last 9 seconds the character width changes back and forth. "State 8".



What I did with my bot was taking screenshots of the timer area for every second, cut out the parts I need and use it as a needle for my bot to look for in the haystack that is the timer area. I've also written my bot to take screenshots of the mission timer area on the screen when it couldn't read the second that was displayed, so I had another needle to prepare so my bot would correctly recognize this particular combination of annoyances in the future. My needle folder now holds over 100 such images. It's not just red and green mission timers or changes in character width or spacing, it's shifts in character brightness as well.

[vancejohnson]

Phogotron/Ludowitsch:

Awesome, and cool. I'm glad you guys figured this out. THIS is why the bot's been so wonky the past month, yeah?

Maybe search for several consecutive seconds' worth of images, and when you get a match start the bot at that point, subtracting from timer the difference between the normal start of 45sec (as an example, if that is what imagesearch is looking for that mission) and whatever it started at?

Or what about doing an imagesearch for a larger area of the screen, something which would identify the rocks (again, example) at a certain position, and THEN start the bot?

I'm probably offbase, and just my $.02...

[Cystacae]

It should not fail mid-mission. If it does, there is a collision or you dont have mo power converter equipped. But more worse
is the 90% failed starts ... that suxx. It might be some videocard issue, as Ludo mentioned above - the mission starts at
6:40 what may lead to fails then.

To change mission start:

- get a screenie at 6:35 mission time
- cut out the 35, thight but not too tight. (something like old space_ezran1.png )
- save it as space_ezran1.png in pictures folder

edit erzan.au3:
Line 32 change
Until $result=1 Or $timer_diff > 15000 to Until $result=1 Or $timer_diff > 20000

Line 43 change
$mission_secs = 400 ;(6:40) to $mission_secs = 395 ;(6:35)

and last but not least Line 63

Ezran2(30000,False) ; save rockets - 6:00 to Ezran2("6:00",False) ; save rockets - 6:00

to adjust the mission timing.

Recompile.

Hope that helps for mission launch.

If missions still tend to fail due to low health - comment out the AdlibRegister at line 49.

You should be able to use the WASD to set the position for certain time frames considering Pixel search/sleep will sleep it at the point the timer comes in and thus may hit rocks without assisting it.

[Ludowitsch]

Phogotron/Ludowitsch:

Awesome, and cool. I'm glad you guys figured this out. THIS is why the bot's been so wonky the past month, yeah?

I guess so. I'm not using either of the two

Maybe search for several consecutive seconds' worth of images, and when you get a match start the bot at that point, subtracting from timer the difference between the normal start of 45sec (as an example, if that is what imagesearch is looking for that mission) and whatever it started at?

Having a lucky strike decide when the bot starts playing may break the whole mission, or at least ruin the start. Look at the 6 fighters at the beginning of Nez Peron Sweep and its higher level bigger brother. Having the bot take these out would become a game of chance.

Or what about doing an imagesearch for a larger area of the screen, something which would identify the rocks (again, example) at a certain position, and THEN start the bot?

I'm afraid this isn't going to happen. ImageSearch in AutoIt works by taking a screenshot internally and scanning it for whatever we want it to look for. This takes time. Last I checked, it was around 40ms. At 60FPS, a new picture is displayed every ~16.667ms. At 30FPS, we get a new picture every 33.333ms. We'd need to slow the game down to like 20FPS to make make sure we can analyze every single picture being put out by the graphics card. If we skipped just one frame, it might just be the one that was showing the rocks in the right position for our ImageSearch to find it successfully. Remember, the scenery constantly moves and scaling and rotating the images we're looking for in ImageSearch isn't possible I'm afraid.