[Open Source] Lucky's Spacebot

[eibtech]

So far I haven't had any issues, I did notice the starter not work when I force closed the client. Does it actively check for the process like the original starter?

Only thing I've noticed is the mouse-over on the mission skew and OTT were backwards.

Thanks for the updates guys, been looking forward to it.

[Darkbounded]

I also noticed one more thing I don't know if it's relevant to the issue with the starter, and for some reason I can't make screenshots on the PC to show you exactly what I mean but I will try to describe it:

The client is opened right where it's supposed to be but the bot window if I move it around on various location (partly above the client window or not above the client window at all) it still gives me the message standby until client ready, there are some spots again partly above the client window that give me the Mission control: enabled message, or if there are some spots when the bot window is above the client window (the whole of it) and still gives enabled, or some spots again above the whole client window that still give me standby until client ready, spots when the bot window is not above the client window that give enabled, and same kind of spots that give standby until client ready, and so on, different various spots, I hope you understood what I mean.

Other kind of these "spots" that I just noticed for example where the bot window is above the game client and saying standby until client ready if I click on the client window (so that the bot window goes bellow it) then it says Mission Control Enabled, if I switch back to the bot window it gives standby again..

[TMichael]

This shouldn't affect the starter, but the Timer Skew is set very high. You might try lowering that to 50.

I think I might have found the problem. Maybe.

The main script keeps track of whether you've run your first space mission or not; this is so it won't automatically assume the client has crashed every time you start the bot without the game running. It looks like I only reset that particular variable when Run Time and Off Time are set. This means that if the bot was run with Run Time or Off Time set at default zero, it was not detecting client crashes.

Anyway, the fix should be available to download momentarily. I'll update this post when it's ready.

[Darkbounded]

Well my Run Time was indeed 0 but Off Time was set to 1.

[TMichael]

I also noticed one more thing I don't know if it's relevant to the issue with the starter, and for some reason I can't make screenshots on the PC to show you exactly what I mean but I will try to describe it:

The client is opened right where it's supposed to be but the bot window if I move it around on various location (partly above the client window or not above the client window at all) it still gives me the message standby until client ready, there are some spots again partly above the client window that give me the Mission control: enabled message, or if there are some spots when the bot window is above the client window (the whole of it) and still gives enabled, or some spots again above the whole client window that still give me standby until client ready, spots when the bot window is not above the client window that give enabled, and same kind of spots that give standby until client ready, and so on, different various spots, I hope you understood what I mean.

Other kind of these "spots" that I just noticed for example where the bot window is above the game client and saying standby until client ready if I click on the client window (so that the bot window goes bellow it) then it says Mission Control Enabled, if I switch back to the bot window it gives standby again..

There is a small symbol on the lower right of your game screen which cannot be covered up - this bot searches for this image to determine whether your game has loaded and you are on your ship. So yes, covering the screen is a no no.

Well my Run Time was indeed 0 but Off Time was set to 1.

I would guess that setting Run Time to a higher number will solve the problem. But a fix is on the way, so that shouldn't be necessary. Thank you for helping me to track this one down!

[eibtech]

So far I haven't had any issues, I did notice the starter not work when I force closed the client. Does it actively check for the process like the original starter?

Only thing I've noticed is the mouse-over on the mission skew and OTT were backwards.

The only thing I could suggest. Make a UI Options tab to add the credits feature on, that way if someone doesn't like it they can turn it off.

Would really like in the end to have a Power-Level checkbox and it automatically runs the known good scripts, checks the level and switches to the next appropriate script when a level has been obtained. Level 16-50 would be alot quicker this way and would appeal to those that let it run 24/7. Nothing like leaving your computer alone for 5 days to come back to a crap load of levels and credits.

Thanks for the updates guys, been looking forward to it.

[Darkbounded]

Lol a lot of good features can be added maybe we should start making a list? Haha

In order for that powerleveling thingy to work you need to have all the upgrades for ship that you will need through the process, altho that you can buy all the tiers, you can't buy Warfare Pod, Power Conversion and EMP at level 16 cuz you wont have the Commedations needed for it, which means that if you want it without any kind of checking on the bot probably the best it would do is like level 40... You need the Warfare pod for Drexel and EMP for Kalee, same goes for Empire I guess. But still I don't think its really neccesary because after level 20 it probably takes around or more than 24 hours to get to level 28, from then you have about a day per mission for leveling it's not that big issue changing them nor time taking and also if you want to be able to go "big" after the leveling is done you would still need the commedations to buy those gadgets, and to do that you need to do dailies, and to make the bot picking up the dailies and doing them, well I guess this will be harder than it sounds:P add to that that the console that gives the dailies is at a different place in every ship makes things even harder:P

[TMichael]

Thanks for the great suggestions guys. They all go into the big box. I'll add a check box under Options to enable or disable the credit display as my next project.

Revision 241 is now available for download. This corrects an error which prevented the client from restarting if Run Time was set to zero, so be sure to get the update.

@eibtech - Good catch on the mouse overs. I'll fix that in the next revision.

[Darkbounded]

Thanks will test it right now, but you may want to add also a field where we can write when we want the bot to check the credits (like every 5 missions or something) its a very nice feature but I just dont want it to do it before every mission, more like every 5-8 missions, because 24 minutes lost per day per bot can get bad if u r multibotting and only aiming to make credits (24 mins = 4x Kalee fortification = ~25k credits x3 = 75k credits lost per day with 3 bots going)

I'm gonna also try an older version with something written in the Run Time to confirm and to use until you add the features for the credits:P brb few mins with update

[Breathofthedying]

Nice update Tm.. Make my mission fiasco and troubleshooting look like a small hill of beans.

[Darkbounded]

Ok so I tried R238 and I set the Run Time to 999, it did work but I guess you haven't added the other Play button image on the character selection screen there and it wasn't able to find it, the new release also worked with Run Time set to 0, but then I forgot to edit the config and put my pass there, so waiting on it again I guess it will work...


R241 success inside the VM looking forward to the credits enable/disable :PP

[jstine]

R241, its getting stuck on 'checking credits from inventory...' when you try to start out doing dailys. also its still not finding the play buttons. my server is using the tan colored arrow. i made my own images and overwrote both gplay and gplay2 and it's still not finding the image. it says it fails to find the play button and tries to resume the missions whilst still on the char select screen

[TMichael]

R241, its getting stuck on 'checking credits from inventory...' when you try to start out doing dailys. also its still not finding the play buttons. my server is using the tan colored arrow. i made my own images and overwrote both gplay and gplay2 and it's still not finding the image. it says it fails to find the play button and tries to resume the missions whilst still on the char select screen

Make sure your screen is sized and positioned perfectly - if not, the images will be missed.

I noticed an exceptionally long wait time before dailies start. I thought it was broken myself before returning to the computer and seeing the dailies finally underway (so give it a minute). I'll track that one down for the next revision.

[jstine]

screen should be just fine as it will find the play button after a failed mission restart(earlier it did a kalee with 49/50 bombers for a fail, and it loaded back to the captains chair fine), its just not finding it when it does a restart after a quit. here's my info anyways.


Luckys Spacebot v5.35 x86 (R241)

System details: X64 CPU, WIN_7(X64)
RAM total:7 GB,free:3 GB, used:52 %
Desktop dimensions: 1600x900(32bpp, 60Hz)
Desktop theme: Aero using NormalSize, NormalColor, 96dpi

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=1
PSX OTT enabled=1
PSX DBG enabled=4
Last mission=
Win / Loss 0 / 0

[Darkbounded]

A little offpost but TMichael look at his info, the bot says 7GB for him aswell, again 1GB less I bet that he is with 8GB RAM