[Open Source] Lucky's Spacebot

[TMichael]

A small update with AMD users in mind...


UPDATE R251

• To accommodate users with display issues at the character select screen, the starter will now force a resize/move every 15 seconds during the play button image search window, and then force it once more after the play button is found (force = shrink the window by two pixels/move the window over by one pixel, then resize/move it correctly). This will also help with clients that simply restart at the wrong resolution. Note: This will NOT help with aspect ratio issues, which require a change in desktop resolution
• If the path to launcher.exe is incorrect, the starter will now post an appropriate error message and reset the bot

UPDATE R252

• Corrected a syntax error in StartGame()

NEXT UP

• Tracking down the bug which inadvertently changes the run times and session times after a successful crash recovery...

[meatsim]

i'm completing at a 2/3 win ratio or so, my problem to not get higher is that while EMP and EWP are used my power conversion module does not. that would give me a lot more survivability and firepower if it did.

any ideas?

[TMichael]

i'm completing at a 2/3 win ratio or so, my problem to not get higher is that while EMP and EWP are used my power conversion module does not. that would give me a lot more survivability and firepower if it did.

any ideas?

Hi Meat,

Off the bat, it sounds like a screen size/position/aspect ratio issue, but it's hard to say without knowing more. Which mission are you running? Also, please get your SysInfo from the About tab and post here.

[breadguy]

btw, just something i noticed that's new with 1.4, they changed something to the tor process so that every time it crashes, it's creating a windows pop-up or crash report

this didn't happen before 1.4, at least not with me

[mcinsane]

Botted for 6 hours and received a 1 week suspension.

BW is cracking down.

[breadguy]

LOL ^^

/10char

[breadguy]

for those of you that the latest lucky's works, do you always have ds-mantis mode on?

[breadguy]

am i seriously the only one where ALL missions work/start except for saleucami fleet action?

i've tried changing the timer images to 48 45 and 40 s, it's not picking it up, just exits right away

update: so i tried using 125 image tolerance and the mission worked, but after the mission ended, mouse just kept moving up and down endlessly inside the ship

update: okay, it seems like nez peron sweep is causing this up and down mouse issue, it's not starting at all or not finding the chair, weird

update: nm lol, shit is weird, i changed game tolerence to 5 and restared the bot, doing nez peron now.....and yeah, its freaking out after each mission

update: okay, i disabled crew missions and it was able to move on to the next mission without a hitch, i had 3 comapnions selected, tech parts, and always highest.....deactivated it and missions continue on without the mouse moving up and down

request: can you make it so that crew skills option only selected the top portion rank 6 missions (49-50), as opposed to "always highest"

[TMichael]

request: can you make it so that crew skills option only selected the top portion rank 6 missions (49-50), as opposed to "always highest"

"Always Highest" along with "Do not specify item type" should do just that.

for those of you that the latest lucky's works, do you always have ds-mantis mode on?

That's only for the one ship type.

Per your ship issues, missions have nothing to do with what happens in the ship before or after; always read the debug text on the bot to determine what the bot thinks is going on.

[breadguy]

"Always Highest" along with "Do not specify item type" should do just that.

This is true, but not for tech parts, for instance, it will do all slicing missions at level 50, or for medicinal supplies, it will do all missions.

It'd be great to where you can set it to always highest but only a specific item to look for.

Per your ship issues, missions have nothing to do with what happens in the ship before or after; always read the debug text on the bot to determine what the bot thinks is going on.

It says "looking for missions start image", almost like it's skipping the loading screen and any crafting/mission selection. The reason I say this is because it does this immediately after the mission ends, doesn't even bring up the inventory or companion window.

Everything works fine for you?

Try to check some dailies off, make sure crew skill is on (at least, 3 companions, look for tech parts). For me, after every mission successfully runs, it just stays at the ship with the mouse cursor moving up and down, like if it's looking for something, or something in the crew mission window.

[TMichael]

This is true, but not for tech parts, for instance, it will do all slicing missions at level 50, or for medicinal supplies, it will do all missions.

It'd be great to where you can set it to always highest but only a specific item to look for.



It says "looking for missions start image", almost like it's skipping the loading screen and any crafting/mission selection. The reason I say this is because it does this immediately after the mission ends, doesn't even bring up the inventory or companion window.

Everything works fine for you?

Try to check some dailies off, make sure crew skill is on (at least, 3 companions, look for tech parts). For me, after every mission successfully runs, it just stays at the ship with the mouse cursor moving up and down, like if it's looking for something, or something in the crew mission window.

Yeah, the crew missions have a number of bugs. I haven't really touched them myself except to apply fixes as requested. I'll take a look at them next after working the crash/run time bugs out - the fix shouldn't be too difficult from what I've seen of the code (fingers crossed).

[meatsim]

Hi Meat,

Off the bat, it sounds like a screen size/position/aspect ratio issue, but it's hard to say without knowing more. Which mission are you running? Also, please get your SysInfo from the About tab and post here.

i run zosha, impossible then kalee multiple times.my lil problem can hit any time, but not all the time... idk

Luckys Spacebot v5.35 x86 (R250)

System details: X64 CPU, WIN_7(X64) Service Pack 1
RAM total:7 GB,free:3 GB, used:52 %
Desktop dimensions: 2560x1440(32bpp, 59Hz)
Desktop theme: Aero using NormalSize, NormalColor, 120dpi

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

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

this fight that lost, same thing 1-2 for PCM not used but 3 and 4 are used fir EMP and EWP

[TMichael]

i run zosha, impossible then kalee multiple times.my lil problem can hit any time, but not all the time... idk

Luckys Spacebot v5.35 x86 (R250)

System details: X64 CPU, WIN_7(X64) Service Pack 1
RAM total:7 GB,free:3 GB, used:52 %
Desktop dimensions: 2560x1440(32bpp, 59Hz)
Desktop theme: Aero using NormalSize, NormalColor, 120dpi

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

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

this fight that lost, same thing 1-2 for PCM not used but 3 and 4 are used fir EMP and EWP

Hi Meat,

Differing resolutions can have a dramatic impact on basic bot functionality. Try the following:

• Your client should be running at 1024x766 (shown above as 1022x759). If this has been changing after you set it correctly, it could be happening because your game client is starting partially off screen. Make sure this stat reads correctly, and also make sure the aspect ratio looks correct (the characters should not appear too thick or thin). If every game client start seems to be too big, regardess of previous settings, try editing the (game) height and width and native (desktop) height and width in C:\Users\UserName\AppData\Local\SWTOR\swtor\settings\client_settings.ini. This usually does the trick for me when setting up a VM for the first time.
• Try running missions with psx debug mode unchecked. This option, if unchecked, will keep your ship from autofiring.

[breadguy]

Luckys Spacebot v5.35 x86 (R252)

System details: X86 CPU, WIN_7(X86) Service Pack 1
RAM total:2 GB,free:0 GB, used:78 %
Desktop dimensions: 1152x864(32bpp, 60Hz)
Desktop theme: High contrast 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=120
HD Status=0
Timing override=4
Mission bonus=1
PSX OTT enabled=1
PSX DBG enabled=4
Last mission=Jabiim Escort
Win / Loss 0 / 0

It can't even finish jablim escort in my inquisitor ship, it seems to just randomly target other things on the screen, so the escorted ship just ends up dying.

Running "low" graphics settings.

On a side note, where's a good place to begin with help/tutorials about programming with AutoIT?

[TMichael]

It can't even finish jablim escort in my inquisitor ship, it seems to just randomly target other things on the screen, so the escorted ship just ends up dying.

Running "low" graphics settings.

On a side note, where's a good place to begin with help/tutorials about programming with AutoIT?

Hi Bread,

• Per AutoIt, IMO the best way to learn is by combing through scripts and reading their documentation. If you're comfortable with programming languages, it should be a snap to pick up.
• Is your native desktop resolution 1920 x 1080? If so, I've found that a VMWare resolution of 1400x1050 works perfectly. If you're not using a VM, or you're sure the aspect ratio looks okay, then never mind this.
• For that ship, phagotron came up with one possible fix. Try checking "DS-Mantis" mode under Options and see if that helps.