[Open Source] Lucky's Spacebot

[Cystacae]

I downloaded the version 5.34 and gave it a try, the problem I have and not sure if there is a fix for it, is that I can't do crew skills. If I have it do crew skills, the mouse just repeats the same movements, it goes to the top right, goes to the middle, then goes back to the top right, then back to the middle, and just keeps on doing this over and over and over again. Is there a way to fix this on my end?

Thanks in advance.

The crew skills area hasn't been touched in a while but I am going to be changing it soon. It is an announced change I made in this forum I think just recently and if I didn't before, I did just now.

[Breathofthedying]

Nice IS port to AscBar.


Using my own images @6500ktemp


Lucky's Spacebot v5.35psx (preview R125)

System details: X64 CPU, WIN_7(X64)
RAM total:7 GB,free:2 GB, used:67 %
Desktop dimensions: 1920x1200(32bpp, 60Hz)

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

On Target Time=49
Missile Delay=333
Timer Skew =+50
IMG Tolerance=100
HD Status=1
Timing override=4
Mission bonus=4
PSX OTT enabled=1
PSX DBG enabled=4
Last mission=Ascendancy
Win / Loss 11 / 1
The one Loss was 1 missed objective.
Testing with other ships. (all Emp and Pub(knght& trooper til 43))
pictures.zip

[TMichael]

Fix for Drexel

Starts at line 125:

Drexel1("1:51",False)
shield_on()
evader_off()
sleep(200)
MouseMove(600,100)
sleep(1000)
shield_off()
evader_on()

The shield_on() and shield_off() switches to fast right here and the client sometimes wont receive the key command. Its a 50/50 chance that it will work correctly...I added a 4 second gap between shield_on and shield_off and fixed the issue. I dont know if anyone else experienced this issue or if i was just the lucky guy.

Hi mcinsane,

Thanks for the code input! There is actually some new functionality to address this in the latest Drexel build.

Two new functions, blaster() and shield(), have replaced shield_on() and shield_off() in six of the missions so far. Blaster(), used in attack functions, simply pixel searches to see if the blaster boost is on, sending a "1" if false, and doing nothing if true. Shield(), used in defensive functions or called by itself, does the same thing for for the shield button. Using these, bothersome time-out errors which cause the wrong booster to fire are no longer happening. They also allow us to do this:

ImpossibleX("5:57", True, 0, 0, 0, 0, 1, 568, 70, 408, 400)
ImpossibleX("5:52", True, 0, 0, 0, 0, 1, 542, 225, 362, 460)
ImpossibleX("5:41", True, 0, 0, 0, 0, 1, 602, 220, 362, 470)

or this:

shield_mover("6:34")
MouseMove(96, 646)
collision()
shield_evader("6:30")
Impossible("6:26", False, 1, 1, 0, 0, 0, 220, 50, 700, 520)
shield()

...

without ever worrying about improperly deactivating the blaster or shield.

Anyway, once the folder changing craziness is done (Cys?:confused, the latest revision should be up for you to peruse.

[Cystacae]

Hi mcinsane,

Thanks for the code input! There is actually some new functionality to address this in the latest Drexel build.

Two new functions, blaster() and shield(), have replaced shield_on() and shield_off() in six of the missions so far. Blaster(), used in attack functions, simply pixel searches to see if the blaster boost is on, sending a "1" if false, and doing nothing if true. Shield(), used in defensive functions or called by itself, does the same thing for for the shield button. Using these, bothersome time-out errors which cause the wrong booster to fire are no longer happening. They also allow us to do this:

ImpossibleX("5:57", True, 0, 0, 0, 0, 1, 568, 70, 408, 400)
ImpossibleX("5:52", True, 0, 0, 0, 0, 1, 542, 225, 362, 460)
ImpossibleX("5:41", True, 0, 0, 0, 0, 1, 602, 220, 362, 470)

or this:

shield_mover("6:34")
MouseMove(96, 646)
collision()
shield_evader("6:30")
Impossible("6:26", False, 1, 1, 0, 0, 0, 220, 50, 700, 520)
shield()

...

without ever worrying about improperly deactivating the blaster or shield.

Anyway, once the folder changing craziness is done (Cys?:confused, the latest revision should be up for you to peruse.

Working folder has been done and the links work. I had it all done since prolly like 2pm est. Also, inbound cleanup and update of UI. Soon after is Crew Skills... I am going to put in the new UI functions but I will disable them in the UI till I have it all set. I am not doing major changes to the UI though. If I do I will inform you guys.

[mcinsane]

Hi mcinsane,

Thanks for the code input! There is actually some new functionality to address this in the latest Drexel build.

Two new functions, blaster() and shield(), have replaced shield_on() and shield_off() in six of the missions so far. Blaster(), used in attack functions, simply pixel searches to see if the blaster boost is on, sending a "1" if false, and doing nothing if true. Shield(), used in defensive functions or called by itself, does the same thing for for the shield button. Using these, bothersome time-out errors which cause the wrong booster to fire are no longer happening. They also allow us to do this:

ImpossibleX("5:57", True, 0, 0, 0, 0, 1, 568, 70, 408, 400)
ImpossibleX("5:52", True, 0, 0, 0, 0, 1, 542, 225, 362, 460)
ImpossibleX("5:41", True, 0, 0, 0, 0, 1, 602, 220, 362, 470)

or this:

shield_mover("6:34")
MouseMove(96, 646)
collision()
shield_evader("6:30")
Impossible("6:26", False, 1, 1, 0, 0, 0, 220, 50, 700, 520)
shield()

...

without ever worrying about improperly deactivating the blaster or shield.

Anyway, once the folder changing craziness is done (Cys?:confused, the latest revision should be up for you to peruse.

awesome!!! cant wait to use it..

Now that im a higher level, i have moved on to Kalee....MUAHAHHAAH!!!

Kalee @3:38 the blasters turn off and it does not shot at the objectives...so the mouse moves between 10 objectives but does not shoot as they fly away Im trying to debug it now for you, but if you happen to have already fixed it, let me know.

[TMichael]

awesome!!! cant wait to use it..

Now that im a higher level, i have moved on to Kalee....MUAHAHHAAH!!!

Kalee @3:38 the blasters turn off and it does not shot at the objectives...so the mouse moves between 10 objectives but does not shoot as they fly away Im trying to debug it now for you, but if you happen to have already fixed it, let me know.

Kalee was one of the first I looked at, so this issue might be new. If the attack code is doing a secondary search for the red crosshair before firing, sometimes removing this can solve that issue.

Let us know how it goes! I'll have a look later on if you don't find it.

[TMichael]

Working folder has been done and the links work. I had it all done since prolly like 2pm est. Also, inbound cleanup and update of UI. Soon after is Crew Skills... I am going to put in the new UI functions but I will disable them in the UI till I have it all set. I am not doing major changes to the UI though. If I do I will inform you guys.

Awesome. I created a brand new folder on my end, so I'm up and running with the new structure. Looking forward to the UI and Crew Skills!

[TMichael]

awesome!!! cant wait to use it..

Now that im a higher level, i have moved on to Kalee....MUAHAHHAAH!!!

Kalee @3:38 the blasters turn off and it does not shot at the objectives...so the mouse moves between 10 objectives but does not shoot as they fly away Im trying to debug it now for you, but if you happen to have already fixed it, let me know.

I just edited the Kalee code to make use of the new blaster() and shield() functions - it appears to be working again at 3:38. The update is in the latest unstable x86 build. Let me know if any other issues crop up.

[Breathofthedying]

I was testing Aetan with all 3 Imp ships. It was roughly 50% or slightly less, when failing almost always being 49/50. I clicked override mission timing @49 timer on target and retesting. So far it is 100% more then 1/2 through repeat test. This is great because it's a nice credit farm.(I think clouds is the best)


I'm not sure if adjusting the time on target will get this mission a quick check off the to do list... Or if my test run results are similar to what' you guys have found...just passing my info.

Tell me to pipe down if you have it covered and I'm just posting what you know.
Rev125

[phagotron]

Luckys Spacebot now is licensed under GPLv3. Since all au3 files have been touched, BE SURE TO UPDATE YOUR LOCAL COPY BEFORE DOING ANYTHING ELSE.

See files DISCLAIMER and COPYING for more info. About tab has been updated along with that.

Please keep in mind that parts of the included documents may have different rights or licenses, mentioned or not. This refers mainly to included or referenced dlls, pictures etc, also to parts of the executable itself. We do not restrict or extend any of these rights as mentioned in COPYING.

[phagotron]

- intentionally left blank -

[sejin]

On R111, I haven't updated yet and I'm about to fall asleep, I have an issue where the game exits to the character screen after a few missions. Has this issue been addressed or is my case a unique and unknown one?

[phagotron]

On R111, I haven't updated yet and I'm about to fall asleep, I have an issue where the game exits to the character screen after a few missions. Has this issue been addressed or is my case a unique and unknown one?

This behavior currently happens most times a mission is lost. It should recover from char selection then by itself.

[Cystacae]

On R111, I haven't updated yet and I'm about to fall asleep, I have an issue where the game exits to the character screen after a few missions. Has this issue been addressed or is my case a unique and unknown one?

Generally speaking if you are to inform us of an issue in the unstable line make sure to download the new version and see if the issue is still present. The unstable code has been updated as much as 7 times a day.

[Breathofthedying]

[feature]. Color match wheel. I am no expert but I have worked with images and OCR a very long time. I have found time and again color matching cures a lot of issues. [/feature]

Once color is calibrated, in theory one image per chipset/video driver... (1 for nvidia line, 1 for Ati, intel ... Etc). Would cover all ground. IMO this is a lot of work for coders and will never be perfect. Since image start is everything ... The solution that works 100% for me is Using my own images. It takes about 5-7 min per mission to take a screen shot and set it up for use. Once you have your personal set you just need to add it to each Rev.

This is not the ideal method but I think any one could follow a simple guide for making their own images(I will jot down some notes on it to help form a guide). After all anyone who is not willing to work a ill bit to get a free bot working should donate to get access to a pool of image sets to pick and choose from or some crazy shit like cyst. Suggested.

The image problem will never be 100%. This is just a kiss(keep it simple...) idea to free up dev time.

Color color color

Again Ty all for the work hope my images have been helping and I will keep them coming til you yell at me to stop.