[Open Source] Lucky's Spacebot

[vatoloco]

anyone know where i can buy the best space ship stuff that vendor sells?

[JustBenHere]

Its over near the auction terminals and there are vendors in most planets space ports

[phagotron]

Hi all,

another hotfix for the 5.35psx preview is available. Please delete the old preview and get the new one:

Luckys_Spacebot 5.35psx - preview

(It can also be loaded from page 14 of this thread and as 5.35psx preview - unstable from thread starter)

Updates & Fixes:
- Mission Control standby (client interface detection) is now bound to HD-mode (720p will not test if client is ready)
- updated evading and shooting functions to prior default behavior with optional enhancements (thanks to TMichael)
- updated Mugaar mission (mission main now has a success rate)

Note: to save any values permanently, exit the bot with the cross. (x) or the windows close function. F4 will exit without save.
If the debug text in bottom of main tab says "Mission control: standby until client ready" and you are unable to start
any mission, drag the bot window to the right until is doesnt cover the swtor window any more. If the message then
changes to "Mission Control: enabled" everything is ok and missions should start as expected. (it looks for a part of
the radar here) If the radar is viewable and it still doesnt enable, check recommendations.and try calibration. To deactivate
this feature, disable HD-Mode in Options.

Recommended settings:
- Aero desktop (default Windows 7)
- Client in window mode, 1024x768, low detail, interface Default (from dropdown list)

[phagotron]

Thanks! I appreciate it... from now about two weeks till I see my grandparents as we talked about phago. I will try to get a new notebook before then that will allow me to play swtor to test code and get all the info I need as well as 6.0 code onto it. I dunno how much I will get done I anticipate we will see a 5.36, 5.37, and by the 5.38 I will have an alpha of 6.0. and maybe by 5.9 we will see beta 6.0 and then 6.0 will be the next release stable after 5.9 that is my basic road map. So hopefully I can stay on track. I am not starting college till the winter for finishing my computer science degree (focus game development). So, it should give me time once I get my vacations done. Going to see my grandparents in Texas, my best friends in South Carolina, and my brother in North Carolina. Going to be about a month worth of time out of town and then it is moving into my own place again. Yay! I gtfo of my mother's home... love her and thank her for letting me stay here after my divorce but she drives me crazy sometimes and her new husband is a moron.

Sounds like a nice vacation, closing a chapter and starting a new one ... good luck with that! Already am curious for the first glance to 6.0. From current state may plan for 5.35 is to have all imp missions up to Aetan ready, maybe except Taspan, 5.36 should come with IS and Ascendary, In 5.37 the crew skills should get some love. For the next versions I have no specific plans, but mission tuning and additional boni might come in focus. I dont think the BH issue can be solved easily by means of 5.x but who knows. So 5.38 and 5.39 might be just maintenance versions with minor enhancements. Another topic on table is the alternate image set(s) (darthangry and tekbill issue) which will be built in once a complete set is available so no idea which version it will be. Anyway, wont have much spare time in the next weeks, so progress will slow down a bit.

[vatoloco]

what mission would be the best to run for most credit/hour? with 100% succses ofc.

[Altmaster]

Just a small note, but as I've been working through the missions creating new timer init pictures, I ran across a bit of a speed bump with Javaal. I just wouldn't pick up the timer, even with the new screencaps. When I looked at the script, I noticed img tolerance was reduced by 8, and bumping it up to 108 in the bot to compensate fixed things; mission runs fine now. Is the tolerance reduction strictly necessary?

[phagotron]

Just a small note, but as I've been working through the missions creating new timer init pictures, I ran across a bit of a speed bump with Javaal. I just wouldn't pick up the timer, even with the new screencaps. When I looked at the script, I noticed img tolerance was reduced by 8, and bumping it up to 108 in the bot to compensate fixed things; mission runs fine now. Is the tolerance reduction strictly necessary?

Due to the bad color contrast there had been lots of false positive recognitions with this mission. Reducing tolerance by 8 here worked quite well for me, so far this wasnt issued. Could you try to lower tolerance step by step and report your lowest working value for Javaal?

[phagotron]

what mission would be the best to run for most credit/hour? with 100% succses ofc.

Sorry but there is no mission known running with 100% success. ofc. ;)

[TMichael]

================================Impossible Sector Mission Update=================================

After long hours of struggling with this space ballet of dodging and movements and attack functions, a working solution has been completed. It makes use of some new helper functions, posted below. The script has thus far had a 100% mission success rate on my Smuggler and Trooper (more testing needed).

Currently, the bot will complete the mission with no bonuses. I am in the process of adding the Disable Fighter Tenders bonus, but I wanted to get this out to the community as soon as possible. I'll post an updated script when it's finished.

As always, BIG thanks to the creators of these magnificent scripts. I'm happy if I can lighten their workload, even a little.

================================================================================ ==================================

Impossible Sector - Updated - Pastebin
This mission script belongs in the Missions folder.

Update 7/22/12 5:55pm PDT: Two small timing adjustments were made to avoid a rare collision issue, and the attack type used from 1:06 to 1:01 was changed to direct fire.

Blaster and Shield Functions - New - Pastebin
These two functions go in misc.au3 as optional replacements for shield_on() and shield_off(). The original shield functions have a potential timing issue; if one is called too soon after a previous call (within 1 to 1.5 seconds), the call fails, leaving the scripter wondering why a button is off when it should be on.

Each new function, when called, will search the appropriate part of the hotbar for black colored pixels (0x061019, booster off). If found, a button press is sent. If not found, it does nothing. It's simple, yet effective, helping achieve 100% booster up time in the IS mission.

To implement, add booster() to the beginning of every attack function and shield() to the beginning of every defensive function. After doing this, all instances of shield_on and shield_off should be removed from the script.

Mover Function - Updated - Pastebin
This function goes in misc.au3. It moves the mouse to one of four positions around the screen when called.

Update: The random movement in the original Mover function has been replaced with sequential movement. In practice, sequential movement has shown itself to be more effective at avoiding blaster fire.

Shield Evader - Updated - Pastebin
This function goes in misc.au3. It activates the shield while rotating through the Evader movements once every 300 milliseconds. It will check for end function every 50 milliseconds.

Update: It now accepts either a delay (in milliseconds) or an end time string, such as "4:12", for the first parameter. The new shield() function was also added.

Shield Evader Mover - Updated - Pastebin
This function goes in misc.au3. It utilizes functionality from the Shield Evader function, and adds movement, via the Mover function, every 800 milliseconds. It is called with a delay or time parameter and a second optional parameter, to specify how many 50 ms time units to wait between movements. The second parameter default is 18.

Update: It now accepts either a delay (in milliseconds) or an end time string, such as "4:12", for the first parameter. The new shield() function was also added.

Shield Mover - New - Pastebin
This function goes in misc.au3. It uses the Mover function while shielded, without Evader. It accepts an integer delay in milliseconds, or an end time string, like "4:12".

In practice, I found this to be more efficient at avoiding hits than the other defensive functions, and it was instrumental in helping to complete the IS script.

Drag Right Function - Updated - Pastebin
This function goes in misc.au3. It accepts x, y coordinates passed in from Mmove, and then right clicks and drags down over those coordinates, initiating an auto-target which fires when the right mouse button is released.

Update: It now optionally accepts a timing delay for parameter three (as last updated by phagotron) and a pixel drag length for parameter four. The fourth parameter default is 50. The starting y coordinate has been updated to y = y - (drag length / 2).

[ibeathepussyup]

Hey guys, everything is working. Including the impossible mission thanks to the new script above.

THE ONLY PROBLEM I HAVE:

Please someone answer...When I attempt to do multiple dailies in a row, the bot simply repeats the first daily I checked off over, and over again. How do I get the bot to move on to the next daily?

THANKS.

[TMichael]

I made a few quick adjustments to the IS script. The new version is linked in the original post above.

[Schadwe]

Looks like there's a virus in these latest downloads. Norton AV is detecting with WS.Reputation.1. Can anyone verify?

[TMichael]

Looks like there's a virus in these latest downloads. Norton AV is detecting with WS.Reputation.1. Can anyone verify?

Which files are you talking about? I downloaded the latest Lucky's, and it unzipped into normal ae3 files. And my post above is just a copy pasta on Pastebin.

???

[Schadwe]

Which files are you talking about? I downloaded the latest Lucky's, and it unzipped into normal ae3 files. And my post above is just a copy pasta on Pastebin.

???

It's the exe file that's being detected as carrying the virus. I unpacked it and Norton caught the virus immediately (I have Norton check all zipped/rar'd files as they are unpacked). I went back to previous Spacebot versions to see if it was always there and it looks like it was injected with version 5.32.

[TMichael]

It's the exe file that's being detected as carrying the virus. I unpacked it and Norton caught the virus immediately (I have Norton check all zipped/rar'd files as they are unpacked). I went back to previous Spacebot versions to see if it was always there and it looks like it was injected with version 5.32.

The .exe is compiled from the accompanying script. It's likely a false positive, but if you have any doubt, just compile the script yourself (right click, compile) and delete the .exe that comes with the download. To do this, you'll need AutoIt.