[Open Source] Lucky's Spacebot

[eibtech]

Yes and 20-22 missions is two hours not one hour.

I am doing 3 different tests now, one on my PC no VMs no nothing, one in the VM with R236 and the new win that removed the memory issue, and one on the other VM with Llanic(to see if it's only Drexe/Aeten) leveling another char, lets see if any of them will go through the 25 missions mark..

Test on PC 25+ missions, using more ram than the others (1,7gb)

VM1 Crashed at 20 missions again (with 1,3GB ram which normally is normal) giving the "dont send" error, if I remember correctly there was some option in windows to disable the "dont send" error messages and just close the program on its own, if its like this, then the bot should be able to relog it everytime it crashes on every 20 missions.... right?

VM2 Llanic still running 22 missions... - Update: Ran for 41 missions..... its limited to Kalee/Aeten...

About Vmware 9 I just can't get it to start "the right way" but it's running fine.. except the crashing ofc, going back to 8 and disabling error messages to see if this will help and if the bot will manage to restart it when it crashes , but like I said Llanic ran for 41 missions straight on the VM... I also tried running it from a different planet, because I saw somewhere that on some planets there are memory leaks, still no difference

I switched to R236 this morning since my friend was laughing at my crashes as he was just running R236 all the time, was still running when I got home tonight 153:0

Was something changed after R236? because every version afterwards has less of a lifespan

[Darkbounded]

Interesting then why its still crashing for me.. I will try with R236 again... eibtech is that in VM or simply on the PC?

And there is another problem that I have, when I said few posts back that it's starting with the correct dimensions for the game but incorrect dimensions for the picture itself (like the window showing just part of it) I was wrong, it's showing everytihng exactly like it needs to be but it's not showing me the UI, the UI is there but it's "invisible" and the bot can't see it... but I tried clicking here and there and I Managed to get in.... I'll make a screenshot later, a little resizing is fixing it..

Anyway I had ~100 straight Drexel Sweep... can't be more convinced now that it's only Kalee/Aeten

[TMichael]

I switched to R236 this morning since my friend was laughing at my crashes as he was just running R236 all the time, was still running when I got home tonight 153:0

Was something changed after R236? because every version afterwards has less of a lifespan

Nada. ничто. Nichts. Pagh! (Klingon for a little color)

Nothing in the Kalee mission script has been touched since well before R236, and changes or updates to the bot itself will have no impact on the individual missions. What happens between missions, though, is another story.

My best guess is that the default settings in config.ini are different between R236 to R248. Any number of changes there can have an impact on your W/L, so matching them up should lead to the same W/L ratio per mission run.

[Darkbounded]

Nada. ничто. Nichts. Pagh! (Klingon for a little color)

Nothing in the Kalee mission script has been touched since well before R236, and changes or updates to the bot itself will have no impact on the individual missions. What happens between missions, though, is another story.

My best guess is that the default settings in config.ini are different between R236 to R248. Any number of changes there can have an impact on your W/L, so matching them up should lead to the same W/L ratio per mission run.

Just that we arent talking about W/L ratio but about hour/crash ratio

[TMichael]

UPDATE 5.35 - R250


HIGHLIGHTS

• A Game Play Schedule has been added in a new tab. Players may now add up to 8 repeatable sessions within a 24 hours period.
• Revision 239: Credits are now displayed on the main tab - no more checking for credit totals between missions, or canceling missions early just for a quick peek
• Revision 237: SWToR Starter is now integrated into Lucky's, allowing for crash recovery and scheduled run times
• Major bug fixes

The new revision can be found HERE on the current x86 trunk.


GAME PLAY SCHEDULE

• A Game Play Schedule is now ready for use in its own tab
• Up to 8 sessions may be added to cover a repeating 24 hour period
• Sessions must be added in order, and canceling a session will shuffle any later sessions toward the top of the list
• Missions, and "Crew Skills Only", are chosen from a drop down menu
• If enabled, crew skills will function as normal during sessions
• When clicking [START] to activate your scheduled sessions:

- If the game client is closed, and the current time is between session times, the bot will display a timer and restart at the next scheduled session time
- If the game client is closed, and the current time is during session time, the game client will restart and begin running missions
- If the game client is running, and the current time is between session times, the game client will be closed until the next session begins, displaying a timer
- If the game client is running, and the current time is during session time, the session will begin

• Use of the Game Play Schedule will override Run Time and Off Time settings under Options
• Users now have three options with which to run missions and crew skills:

- Clicking a mission button from the Main tab will run a mission, or "Crew Skills Only", indefinitely
- Entering values into the Run Time and Off Time fields under Options, and then clicking a mission button from the Main tab, will repeatedly run missions and take breaks for the specified periods of time (+ or - a random variance)
- Starting the Game Play Schedule with sessions added will run a mission or "Crew Skills Only" at up to 8 designated times (+ or - a random variance) repeatedly over 24 hour periods

ADDITIONAL CHANGELOG

• Starting a Daily Mission or Game Play Schedule will now call SwitchToMainTab(), which switches to the main tab before performing any other functions
• The password field search image now includes the field outline and cursor to verify the field is ready for input
• Maximum possible wait times during start-up image searches have been increased significantly
• CloseGame(), CrashRecovery(), and StartGame() now search for the standard Windows error button, [OK], and the Windows program close button, [Close the Program]
• The search area for the Character Select play button has been increased to accommodate users with up to 11 characters
• Corrected numerous "Do After Dailies:" reconnect codes; the correct missions should now consistently run after doing dailies
• Cleaned up the Crew Skills tab and added all new pretty pictures
• The game client window should now move and resize properly after every start or crash recovery
• Moved the "HD mode" check to the MessageCatcher() function to help accommodate session related message checks while the client is closed
• Failed close game attempts will now lead to a WinClose() attempt followed by a WinKill() attempt, after which, if both fail, the bot will reset and wait for user input while drinking a tasty margarita
• Added green play button checks to loop2(), which should help some users successfully continue after a Loss followed by a drop to Character Select
• Corrected a Crew Skill bug which occurred when "Do not specify item type" was checked
• Reordered the bot tabs

WORK IN PROGRESS

Version 5.35

• Mission and crew task improvements
• Bug anninilation with an army of angry coder monkeys

Version 6.0

• Improved UI interface
• More mission and crew task improvements

IMPORTANT REPOST: INSTRUCTIONS FOR STARTER / SCHEDULE SETUP

1) Run Lucky's Spacebot, revision 250 or higher, and then immediately exit.
2) Navigate to your Lucky's folder and open Config.ini in your favorite text editor.
3) Scroll to the bottom of Config.ini until you see the following:

[Login Info]
Game Path=C:\Program Files (x86)\Electronic Arts\BioWare\Star Wars - The Old Republic\launcher.exe	
Pass=YourPass

4) Update Game Path with the full path to your game launcher.
5) Update Pass with your password.
6) Save the file.
7) Open Lucky's and enjoy your new functionality


ADDITIONAL NOTES

• Team Lucky's and other developers: When submitting future updates, please make absolutely sure that your password is NOT included in Config.ini.
• This revision was rather massive. There are bound to be bugs present that one programmer was simply unable to catch. Please post any major bugs that crop up so that we can address them as soon as possible.

Please enjoy.


***UPDATE ***

The following issues, only affecting scheduled sessions, are still present. I'll be working through these, and any others added to the list, as soon as I can:

• After two sessions, the bot will wait until the beginning of session 1 again, ignoring other sessions
• Starting the scheduler while the game client is closed, and the time is between sessions, is causing an unnecessary restart
• I found some anomalies in the session settings of the config.ini file - probably related to the first issue above

[TMichael]

Just that we arent talking about W/L ratio but about hour/crash ratio

Nada. ничто. Nichts. Pagh! (Klingon for a little color)

Nothing in the Kalee mission script has been touched since well before R236, and changes or updates to the bot itself will have no impact on the individual missions. What happens between missions, though, is another story.

My best guess is that the default settings in config.ini are different between R236 to R248. Any number of changes there can have an impact on your W/L, so matching them up should lead to the same W/L ratio per mission run.

Anyway I had ~100 straight Drexel Sweep... can't be more convinced now that it's only Kalee/Aeten

You were saying?

[Darkbounded]

I am saying that the problem is only with Kalee/Aeten not that it's the bot, anyway the new reloging features should help even if it keeps on crashing at every 20 missions, there is just one problem, like I mentioned few posts earlier, I don't know why but when I start the client in the VM it shows me everything just not the UI, which leads the bot to a confused state, and I am fixing this very easily, all it needs is just a little stretching right or down, even if its just by 1 pixel it will make it reload and show the UI, if you have any idea how to fix this shoot, if not is it too much of a problem to add this to the bot aswell? After it gets to the character screen just to stretch it a little and then get it back to the right size I know that you worked hard over the last few days and I'm asking only if its easy to do it, I don't know if anyone else has the same issue like me..

[TMichael]

@Dark:

The Move and Resize button under Options should automatically refresh your window. The bot will actually do that each time it starts, though, so I'm not sure why this wouldn't be working for you. I know your system is beastly, but the symptoms you describe really do sound like overtaxed hardware (memory, CPU, video, something....). :confused:

Per Revision 250:

It seems that multiple sessions are still buggy. The logic involved in setting these up is starting to hurt my brain.

I'll be addressing the following issues ASAP:

• After two sessions, the bot will wait until the beginning of session 1 again, ignoring other sessions
• Starting the scheduler while the game client is closed, and the time is between sessions, is causing an unnecessary restart
• I found some anomalies in the session settings of the config.ini file - probably related to the first issue above

On the bright side, most of the other changes, including the extra crash checks and extending play button search areas, seem to be working well! I'll get started on the current issues after I get some rest...

[Truestorybro]

I am saying that the problem is only with Kalee/Aeten not that it's the bot, anyway the new reloging features should help even if it keeps on crashing at every 20 missions, there is just one problem, like I mentioned few posts earlier, I don't know why but when I start the client in the VM it shows me everything just not the UI, which leads the bot to a confused state, and I am fixing this very easily, all it needs is just a little stretching right or down, even if its just by 1 pixel it will make it reload and show the UI, if you have any idea how to fix this shoot, if not is it too much of a problem to add this to the bot aswell? After it gets to the character screen just to stretch it a little and then get it back to the right size I know that you worked hard over the last few days and I'm asking only if its easy to do it, I don't know if anyone else has the same issue like me..

Using AMD? I have the same exact issue with my AMD computer in VMWare... which in turn makes my second computer dead weight as i can only use one client (none VMware) on it

[Buddelbaby]

Can you the Aeten Mission with All Bonus flight in?

[Darkbounded]

@Dark:

The Move and Resize button under Options should automatically refresh your window. The bot will actually do that each time it starts, though, so I'm not sure why this wouldn't be working for you. I know your system is beastly, but the symptoms you describe really do sound like overtaxed hardware (memory, CPU, video, something....). :confused:

Per Revision 250:

It seems that multiple sessions are still buggy. The logic involved in setting these up is starting to hurt my brain.

I'll be addressing the following issues ASAP:

• After two sessions, the bot will wait until the beginning of session 1 again, ignoring other sessions
• Starting the scheduler while the game client is closed, and the time is between sessions, is causing an unnecessary restart
• I found some anomalies in the session settings of the config.ini file - probably related to the first issue above

On the bright side, most of the other changes, including the extra crash checks and extending play button search areas, seem to be working well! I'll get started on the current issues after I get some rest...

You still don't understand :P if it crashes the bot will get it in the right position while the client is loading, but when it loads I will just be able to see the character and the ship behind him just no UI, no characters, no menu buttons no nothing, and AT THAT point if I stretch it a bit then they show up, resize button won't work (yes I tried) because it's already at the right spot with the right dimensions... so my point was, if you can make it do that after it gets at the character selection screen stretch it a bit and then return it to its original size... obviosly it's something they did that ****s up AMD and I guess it's only for the Bulldozers, Truestorybro FX-XXXX ?

[TMichael]

You still don't understand :P if it crashes the bot will get it in the right position while the client is loading, but when it loads I will just be able to see the character and the ship behind him just no UI, no characters, no menu buttons no nothing, and AT THAT point if I stretch it a bit then they show up, resize button won't work (yes I tried) because it's already at the right spot with the right dimensions... so my point was, if you can make it do that after it gets at the character selection screen stretch it a bit and then return it to its original size... obviosly it's something they did that ****s up AMD and I guess it's only for the Bulldozers, Truestorybro FX-XXXX ?

Resize only after character select loads.... I think that's doable. Anything to help our struggling AMD-VMWare-Spacebot users.

[Buddelbaby]

Have where a Missions Script for Aeten with all 2 Bonus Mission?

[TMichael]

Have where a Missions Script for Aeten with all 2 Bonus Mission?

Hi Bubbel,

Most of our missions focus on just one bonus because the pixel color search used to find targets is only so effective. Empire missions are particularly difficult because of those yellow exhaust targets.

TL;DR: You're not likely to find a two bonus Aeten mission in Lucky's unless or until we add recorder code as a secondary mission option.

[Darkbounded]

Thanks, anyway I am using Drexel Sweep for now as a replacer for Kalee, it's not that bad ain't loosing that much credits but it still gets ugly when it crashes (if)

Honestly if I knew what I know now, and if I had read enough when I had to (before buying the PC) I wouldn't chose AMD A lot of the choices would've been different but.... gotta burn once