[Open Source] Lucky's Spacebot

[TMichael]

Love the bot. It was working very very well. Last night I let it go and got three levels and a ton of gold. 93 missions passed, 2 failed. GREAT JOB.

My issue though is today, the bot has ZERO functionality except resizing my window. What is going on? What did I do? I created new folders from the rar file, fresh ones, that did not work, I downloaded the newest revision, that did nothing. I ran as admin in a bunch of different compatibility modes, nothing. When I click a button, nothing happens.
At the bottom of the bot shows Mission Control: stanby until client ready...

Any help???

Please post your SysInfo from the last bot tab. If I had to guess, this sounds like the time I had the bot window covering up the lower right corner of the game window, which obscures the image needed to verify the character is on the ship.

[TMichael]

Quick update:

I'm currently working through the Starter bugs posted here, as well as a few others I've discovered. The revision should be completed shortly. In the meantime, please post any additional Starter bugs found in this thread.

[Darkbounded]

Could it somehow shut down my computer even tho that it's running from a VM? O_o Cuz thats how I found my PC xD

Edit: It crashed again few minutes ago, same message like the last time and I also noticed that it keeps the cursor in the bottom right corner and keeps moving it there until I press F2 to stop it.

[TMichael]

Could it somehow shut down my computer even tho that it's running from a VM? O_o Cuz thats how I found my PC xD

Edit: It crashed again few minutes ago, same message like the last time and I also noticed that it keeps the cursor in the bottom right corner and keeps moving it there until I press F2 to stop it.

I hope not! I run all my instances via VMWare and I've never seen this happen. Is it possible your CPU got too hot?

Per the error, I might have that fixed in the upcoming revision. Posting momentarily...

[Darkbounded]

For sure my CPU wasn't THAT hot, I'm kinda Temperature Maniac got a total of 3 120mm vents just for the CPU :d, could be something else, anyway looking forward for the fixes this is more than the right timing for the starter to get implemented starting university in few days :d

[TMichael]

UPDATE 5.35 - R239


HIGHLIGHTS

• 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: The 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.


Changelog:

• A screenshot of inventory credits will be taken before every space mission, and before and after dailies, and then displayed on the main tab
• Added a second play button image to search for on the character select screen; it turns out the game uses both green and beige for the arrow, depending on server
• Tracked down a bug which was keeping the calculated variances from being applied to the actual run and off times.
• Added integer conversions to the new GUICtrlRead calls so that variances are read correctly
• Crashes during missions, or mission game closure via [F4], should once again cause a game client restart after the mission timer has run through
• CloseGame(), added a two second check for the Accept button before sending [Esc] to quit the game (fixes Crew Skills error)
• Accept() will now check for the accept button for up to 5 seconds before exiting
• Run Time no longer has a minimum value
• Run Time's maximum value has been increased to 1439 minutes (one day), however, running the bot for this long is not recommended!
• The bot should now detect crashes that occur both while in space and not in space, and then attempt a restart
• More testers needed! Please report any issues related to the Starter or new credit display in the main Lucky's forum thread, and please include as much detail as possible

Previous Changelog Highlights:

• Options, Run Time = number of minutes before the game quits, 0 = never quit
• Options, RT Variance = random run time variance in minutes, from -INPUT to +INPUT, 0 = no variance
• Options, Off Time = number of minutes before the game restarts, 0 = never restart
• Options, OT Variance = random off time variance in minutes, from -INPUT to +INPUT, 0 = no variance
• The client should now restart after crashing, which will in turn restart the session Run Time (if not 0)
• Added "Remaining: 0:00" field in middle of main tab to display remaining session Run Time
• The "Remaining" field will update after each mission, displaying "N/A" if Run Time is not used
• Minor cosmetic changes to Options and About tab
• Includes all mission updates from previous revisions

WORK IN PROGRESS

Version 5.35

• Mission and crew task improvements
• Bug exploding with exceptionally potent roadside bug bombs

Version 6.0

• Improved UI interface
• More mission and crew task improvements

IMPORTANT REPOST: INSTRUCTIONS FOR STARTER SET UP

1) Run Lucky's Spacebot, revision 237 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

Reminder: Leave the new Run Time and Off Time fields at zero if you wish to run the game indefinitely.
Team Lucky's and other developers: When submitting future updates, please make absolutely sure that your password is NOT included in Config.ini.


Please post any additional bugs found. Cheers!

[Darkbounded]

So if I try again with Alt+f4 it should work?

The new feature for the credits is reeeeeeeeally nice, but if its doing it before every mission, its taking like 4-5 seconds to do it, thats about 1 minute lost per hour, if you're running 24/7, thats 24 minutes lost per day (more or less) and thats ~30k credits lost per day. Don't get me wrong I really like it but, if it's not too much of a trouble you could add an additional field for that feature where we can write when it should make the screenshot, I mean every 2 missions, or every 5 missions, I guess it would be nice if it can be made customizable like most of the other stuff

The starter is still not working for me, I did it little different this time.. I moved the SWTOR to it's default location so that I didn't change the directory in the config but I didn't touch the Off Time this time, gonna set it to 1 again and try again... (thats with alt+f4 again) Trying with off time 1 now results in 5mins

[TMichael]

So if I try again with Alt+f4 it should work?

The new feature for the credits is reeeeeeeeally nice, but if its doing it before every mission, its taking like 4-5 seconds to do it, thats about 1 minute lost per hour, if you're running 24/7, thats 24 minutes lost per day (more or less) and thats ~30k credits lost per day. Don't get me wrong I really like it but, if it's not too much of a trouble you could add an additional field for that feature where we can write when it should make the screenshot, I mean every 2 missions, or every 5 missions, I guess it would be nice if it can be made customizable like most of the other stuff

The starter is still not working for me, I did it little different this time.. I moved the SWTOR to it's default location so that I didn't change the directory in the config but I didn't touch the Off Time this time, gonna set it to 1 again and try again... (thats with alt+f4 again)

It worked for me both times I tried. Give it a shot.

Per the starter, detail exactly what you did, and what the bot did, and post your SysInfo from the last tab. Info on the bot's debug line is relevant as well. Let's see if we can get to the bottom of this.

[Darkbounded]

Well the default location in the config file is C:\Program Files (x86)\Electronic Arts\BioWare\Star Wars - The Old Republic\launcher.exe , so instead of changing the path in the config file, I moved my SWTOR folder in program files and created all the other folders to match whats the default in the config because my SWTOR folder was on the desktop till now, I changed the Off Time to 1 and am waiting for it to "finish" Kalee Fortification, about 2-3 mins left will see if there will be any difference, about the SysInfo, kinda hard no browsers in the VM I'll rewrite it after few mins just to see what will happen now


So the message changed to "Standby until client ready", actually there is one thing that may be the problem, I am not starting the bot with Right Click->Run as admin, maybe this is preventing it from being able to automatically start .exes?

Doing another test, this time with "Run as admin", brb 6 mins

Still not working
here is sysinfo

R239

System Details: X64 CPU, Win_7(X86) SP1
RAM total: 2GB, free: 2GB, used 15%
Desktop Dimensions: 1152x864 (32bpp, 60Hz)
Desktop theme: Aero using NormalSize,Normal Color, 96dpi

SWTOR Client is nor tuning, please start it and retrieve dbg info again.

On Target Time = 50
Missile Delay=333
Timer skew=50
IMG Tolerance=90
HD status=1
timing override=4
mission bonus=1
PSXOTT enabled=1
PSX DBG enabled=4
Last mission=Kalee fortificaation
win/loss 0/0

[TMichael]

Based on the debug text, "Standby until client ready", it's getting stuck in the initial main loop while waiting to start. As long as a mission has been previously started, this loop should detect a client crash. I'm also wondering if the 2GB memory limit isn't behind your troubles. I use 3GB per VM to run SWToR because I found that 2GB simply wasn't enough.

Anyway, I've added an additional client check to each loop iteration which might help to solve your problem. The revision (R240) is now up and available. Let us know!

[Darkbounded]

I have 3GB memory, I don't know why but the bot is never detecting the real memory that I have, I have that same issues on all of the VMs and on my Laptop aswell, I have 4GB on the laptop the bot thinks that I have 3GB, Havent tried it on the PC itself. gonna try with 240 now, and yes I am starting a mission, after it loads the mission I wait around 5-10 seconds then I hit Alt+f4

And I just checked on the PC itself, I have 16GB Memory the bot says that I have 15GB, results in 5 mins

[TMichael]

Because you are essentially running a computer inside a computer, some memory has to be reserved for your main system as well. This is why you are only allowed to use the memory posted above.

I would recommend using the 4GB laptop for the VM/SWToR/Lucky's combo since you can get the full 3GB for your VM. I'd be interested to hear whether the same problem occurs there; the bot is currently running as smooth as silk on my three 3GB VMs.

EDIT

16GB should allow you to run three VMs with SWToR at 3GB each, provided you have a strong processor. Be sure each VM is given 2 processors and one core each. Let us know how it goes!

[Darkbounded]

It is runing smooth as silk for me aswell and again "standby until client ready", the VM is using more than 2GB I can assure you, I noticed this problem a while ago and I did a deeeeeeeeeeeeeeeep digging about it, it has 3GB it is detecting it, it shows it in System Properties and in Task Manager, there is no point in giving it more than 3GB because x32 win can't use it, I was observing the Task Manager and I saw it at 2,2GB Memory, I also used a Mem Test to see if it can really use all these 3GB, I got it up to 2,9GB so it is not this. The SWTOR client itself is using a maximum of 1,4GB Memory (at least I haven't seen it use more than that) the win uses about 500MB, so even 2GB should be enough. The SWTOR is no longer shared(there is a full copy of the game in every VM) like it was before, I bought a new HDD just for the VMs and now I have them spread around some on the SSD some on the HDD (it's 7200RPM SATA3, 130MB/s read/write). PLUS at the moment I am runing only one VM , I will try if the starter will work on the laptop now without VM.

Another feature that you can add is, since we already have the starter integrated you can add a "Start" button, so that the bot can load the game on its own and add a dropdown menu next to the button, similiar to the one in the Dailies tab.


Same thing with the laptop, standby until client ready...

Currently the VM that's runing on that PC has 4 Cores x 4GHz, (I have FX-8150 clocked at 4GHz atm) and 3GB RAM, the CPU load never goes above (inside the VM) 50-55%, the RAM never goes above 2,2GB, and yes I was runing 3 VMs awhile ago while the host CPU was at about 80-85% load. It can run with 2 Cores but it often can go at 100% and I doubt that this is good, thats why I am giving it more, just because I gave it 4 Cores that doesn't mean that all 4 cores are specially reserved for it, you can have all 3 VMs with 4 cores each, so that if needed they can use more resources if there are 3 VMs with 4 Cores each loading at about 50%, that is about 75-80% load on the host CPU(if its 8core cpu).

[TMichael]

Another feature that you can add is, since we already have the starter integrated you can add a "Start" button, so that the bot can load the game on its own and add a dropdown menu next to the button, similiar to the one in the Dailies tab.

The bot will already restart whichever mission you were running before the crash occurred. You probably won't be seeing significant UI changes until version 6.0 is released.

Per your bot issue, I'm at a loss at this point. It might help to see your SysInfo from when the game is running. It restarts as expected for me and others - I would love to figure out what's causing your restart to fail.

[Darkbounded]

That's from the laptop


Luckys Spacebot v5.35 x86 (R240)

System details: X64 CPU, WIN_7(X64) Service Pack 1
RAM total:3 GB,free:1 GB, used:72 %
Desktop dimensions: 1600x900(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 =+400
IMG Tolerance=90
HD Status=1
Timing override=4
Mission bonus=1
PSX OTT enabled=1
PSX DBG enabled=4
Last mission=
Win / Loss 0 / 0

[Crewskills]
On/Off=4
[Crewmembers]
1=4
2=4
3=4
4=4
5=4
6=4
[Allskills]
Allskills=4
[Position]
Left=1
Middle=4
Right=4
[Skill]
Skill=Possible Item Types
[Barrel_Rolls]
On/Off=1
[Timer]
1=333
2=50                     
3=+400
4=90
5=0
6=0
7=0
8=1
9=0
[Level]
Level=Always Highest
[Aloop]
Aloop=1
Sloop=4
Aloop2=4
[LateMission]
Sullust=1
Drexel=1
[Dailya]
Dailya=Nothing 
[Dailyemp]
1=4
2=4
3=4
4=4
5=4
6=4
7=4
8=4
9=4
10=4
11=4
12=4
13=4
14=4
[Dailyrep]
1=4
2=4
3=4
4=4
5=4
6=4
7=4
8=4
9=4
10=4
11=4
12=4
13=4
14=4
[Imagesearch]
On/Off=1
[TimerOverwrite]
on/off=4
[PSX_DEBUG]
on/off=4
[HD]
on/off=1
[Screen]
Width=1040
Height=804
X-Offset=0
Y-Offset=0
[Basic]
Hibernate=4
Reserved1=4
Reserved2=4
DSMantis=4
[Login Info]
Game Path=C:\Program Files (x86)\Electronic Arts\BioWare\Star Wars - The Old Republic\launcher.exe	
Pass=xxxxx

And my game path - C:\Program Files (x86)\Electronic Arts\BioWare\Star Wars - The Old Republic

Would it give out some error if the game path is wrong?


Sys info after 1 mission (intentionally caused it to fail)

Luckys Spacebot v5.35 x86 (R240)

System details: X64 CPU, WIN_7(X64) Service Pack 1
RAM total:3 GB,free:0 GB, used:79 %
Desktop dimensions: 1600x900(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 =+400
IMG Tolerance=90
HD Status=1
Timing override=4
Mission bonus=1
PSX OTT enabled=1
PSX DBG enabled=4
Last mission=Kalee Fortification
Win / Loss 0 / 1


I will try on the PC now just to ensure that it's not a Memory or CPU problem (got lots of both)