[Open Source] Lucky's Spacebot

[Jevnaker]

Older versions are no longer supported, but we might be able to help you out with your issue. Also, Phagotron might know if the older version is up somewhere.

If it simply exits the mission after a few seconds, this means that your system is not reading the starting timer image(s) to sync the bot. The first thing you should try is adjusting your Image Tolerance up by one or two at a time until the timer image is found.

We can help you more, though, if you post your system info from the bot's About tab.

it opens the leave mission box, but then does nothing just puts teh pointer in the uppermost left corner.

[goniukas]

Someone had mentioned that you can yield 70k credits/hour by running Kalee. how is that possible? Mission is roughly 5min30s if you add loading screens + crew skills it's more than 6min. The reward is 4k credits if you round it up it's 40k credits/hour. I am doing something wrong?

[TMichael]

Someone had mentioned that you can yield 70k credits/hour by running Kalee. how is that possible? Mission is roughly 5min30s if you add loading screens + crew skills it's more than 6min. The reward is 4k credits if you round it up it's 40k credits/hour. I am doing something wrong?

The 4k doesn't include the bonus, which is automatically added to your credit total during the mission.

[TMichael]

it opens the leave mission box, but then does nothing just puts teh pointer in the uppermost left corner.

We really need you to post your SysInfo if you would like more help. A pointer missing the "Leave" button is probably an issue with your desktop resolution, position, or aspect ratio.

[phagotron]

it opens the leave mission box, but then does nothing just puts teh pointer in the uppermost left corner.

We already discussed your issue. If there is no way for you to make your Notebook / Game client meet the recommendations, you have to cut out your own timer sync images.

Since our telepathic interface still is under construction, we need a bit more specific input if you want help on your notebook settings. Post sysinfo and a screenshot of your whole desktop, maybe we can say more with that.

[Croxphire]

During Ezran Outpost it just keeps shooting my own thrusters. I've tried making adjustments but nothing seems to help. Any suggestions.

Luckys Spacebot v5.35 x86 (R233)

System details: X64 CPU, WIN_7(X64) Service Pack 1
RAM total:7 GB,free:4 GB, used:46 %
Desktop dimensions: 1920x1080(32bpp, 60Hz)
Desktop theme: Custom

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=1
Timing override=4
Mission bonus=1
PSX OTT enabled=1
PSX DBG enabled=4
Last mission=Ezran Outpost
Win / Loss 0 / 0

[darkone23]

OK with the new build im haveing 90%+ success with drexel went 47/7 but when I wok up found myself looking at my web browser instead of the game. It had only been running for 2 hours before it logged me out for idleness, but now I cannot seem to get some missions to work at all the just exit after a few seconds in the mission ive tryed image tolerance but it does nothing. The missions are balosor, jaaval, Llanic and kovor theres one other but cant remember as i just wok up lol. I would think its the same problem since they are both the same mission just different tiers. I even tryed turning HD on really quickly for a few runs but that didnt work either.


Luckys Spacebot v5.35 x86 (R233)

System details: X64 CPU, WIN_7(X64) Service Pack 1
RAM total:7 GB,free:5 GB, used:27 %
Desktop dimensions: 1360x768(32bpp, 60Hz)
Desktop theme: Aero using NormalSize, NormalColor, 96dpi

SWTOR Client is not running, please start it and retrieve dbg info again.

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

Ok this is getting ridiculous. I still cannot get these 4 missions to work and I have tried every single IMG tolerance in the 80-125 range I even tried 79 and 126. Can someone please tell me what I'm doing wrong? do I have to restart both the launcher and game every time i switch tolerance? or just the bot? or just the game?

[TMichael]

During Ezran Outpost it just keeps shooting my own thrusters. I've tried making adjustments but nothing seems to help. Any suggestions.

Luckys Spacebot v5.35 x86 (R233)

System details: X64 CPU, WIN_7(X64) Service Pack 1
RAM total:7 GB,free:4 GB, used:46 %
Desktop dimensions: 1920x1080(32bpp, 60Hz)
Desktop theme: Custom

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=1
Timing override=4
Mission bonus=1
PSX OTT enabled=1
PSX DBG enabled=4
Last mission=Ezran Outpost
Win / Loss 0 / 0

That's usually a problem associated with the Mantis. Try checking "DS-Mantis mode" and let us know if that helps.

[phagotron]

Ok this is getting ridiculous. I still cannot get these 4 missions to work and I have tried every single IMG tolerance in the 80-125 range I even tried 79 and 126. Can someone please tell me what I'm doing wrong? do I have to restart both the launcher and game every time i switch tolerance? or just the bot? or just the game?

Beneath all those clutter and desparation in the early morning ... what exactly is your problem now?

[TMichael]

Ok this is getting ridiculous. I still cannot get these 4 missions to work and I have tried every single IMG tolerance in the 80-125 range I even tried 79 and 126. Can someone please tell me what I'm doing wrong? do I have to restart both the launcher and game every time i switch tolerance? or just the bot? or just the game?

The settings will go into effect the moment you click another tab, so no worries about restarting. You can test this by checking or unchecking the bonus box, and then clicking the main tab - you'll see that the bonus text will change from gray to red or red to gray depending on which option you chose.

I was going to suggest submitting screenshots so that we could add them to the timer checks, but then I realized your desktop height was set at 768. Our windowed client requires a height of 804, and AutoIt will only acknowledge up to 12 extra pixels off screen. This means your window is being compacted when resized, resulting in incorrect "y" coordinates; it's looking in the wrong place for that timer image, and will likely misclick during missions as well.

For the bot to work as intended, you will need a monitor with a native height > 768, or you will need to use VMWare Workstation with Win 7 x86, since the virtual machine can display large resolutions, adding scroll bars as needed.

[Croxphire]

That's usually a problem associated with the Mantis. Try checking "DS-Mantis mode" and let us know if that helps.

I tried it. No change. I'm not a bounty hunter though, if that matters.

[TMichael]

I tried it. No change. I'm not a bounty hunter though, if that matters.

Hmm, now I'm at a loss. The last time I tested Ezran, it was working for my Sith. Is it shooting your own thrusters just some of the time or all of the time?

As a potential solution, this is one of the missions to which I've added a game tolerance adjustment. Try reducing this value by one point per attempt, which will reduce the range of colors searched. Please let us know if this helps.

[Croxphire]

Hmm, now I'm at a loss. The last time I tested Ezran, it was working for my Sith. Is it shooting your own thrusters just some of the time or all of the time?

As a potential solution, this is one of the missions to which I've added a game tolerance adjustment. Try reducing this value by one point per attempt, which will reduce the range of colors searched. Please let us know if this helps.

Id say about 90 percent of the time its firing on its own thrusters. The rest of the time it fires on friendly's as well as a few talon fighters. It does fire upon the station a little as it passes by but not much. When I first posted this, the game tolerance was at +3. I've adjust it one point at a time down to -5 with no change.

[NeoRinTinTin]

I think this probably has to do with your native desktop resolution. For some reason, AutoIt / Windows will only draw up to 12 extra pixels off screen if your window is too large. In this case, with your desktop set at 1366x768, the program isn't able to display the entire height of 804, which includes the windows title bar and frame, so your window is being compacted, affecting the y coordinate of your mouse clicks.

If 768 is your maximum native resolution, then the only solution I'm aware of, short of replacing the monitor, would be to run the client through VMWare. It allows for very large desktop resolutions, using scroll bars when needed. I had to do this for my wife's rig, and it's working perfectly now with the bot.

Instructions for successfully setting up VMWare Workstation with SWToR are posted on page 83 of this thread if you need them. Please let us know if this helps!

I found a simpler solution by using NVIDIA Control Panel and creating a custom resolution, 1366x804. Now all the ship skills activate.

Still getting wrecked in the later half of drexel sweep though. Using all grade 5 except the grade 4 missiles.

Luckys Spacebot v5.35 x86 (R233)

System details: X64 CPU, WIN_7(X64) Service Pack 1
RAM total:3 GB,free:0 GB, used:76 %
Desktop dimensions: 1366x804(32bpp, 60Hz)
Desktop theme: Custom

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=Drexel Sweep
Win / Loss 0 / 1

[darkone23]

The settings will go into effect the moment you click another tab, so no worries about restarting. You can test this by checking or unchecking the bonus box, and then clicking the main tab - you'll see that the bonus text will change from gray to red or red to gray depending on which option you chose.

I was going to suggest submitting screenshots so that we could add them to the timer checks, but then I realized your desktop height was set at 768. Our windowed client requires a height of 804, and AutoIt will only acknowledge up to 12 extra pixels off screen. This means your window is being compacted when resized, resulting in incorrect "y" coordinates; it's looking in the wrong place for that timer image, and will likely misclick during missions as well.

For the bot to work as intended, you will need a monitor with a native height > 768, or you will need to use VMWare Workstation with Win 7 x86, since the virtual machine can display large resolutions, adding scroll bars as needed.

but its only these 4 missions that do no work all of the others which i can do work fantastic but you are right about the misclicking i have to lower my window about.. say have an inch but then it works fine so I do not see why i would need a VM just to run 4 missions?