[Open Source] Lucky's Spacebot

[Cystacae]

I fixed the x64 link on the first page it is now working and you may proceed to download the x64 version again.

[Cystacae]

Did any you know you can actually see the changes made when coding the bot on our Twitter page by clicking the changeset link? That is, if you are interested in such things.

[TMichael]

Phago if you rename Impossible to Ascendancy and inside it from Impossible Sector to Ascendancy Barrier stuff it does work. They are an exact mirror... I did this and tested it... I can confirm it did work.

I actually did this a few builds ago with Ascendancy and the Hydrian/Polith missions, so they should include the initial revision to IS already.

Last night, though, I made a few more IS revisions. Must. Make. Better. Anyway, it ran 14-1 on my first round of tests, with a 100% success rate for the bonus, so I'll be updating the other three missions again shortly

[phagotron]

Hey guys,

Been playing around with the bot for a few days now. I have been bugging Cystacae a few times in PM's but I figured it was time to make a post hehe.

I was originally having issues with having to change my tolerance to get missions to start and it not being reliable with that, but I started making my own pictures and that fixes it every time now. So I've moved on to my next issue, which is the targetting system.

When I use the bot with my Jedi Knight, the bot is constantly shooting at it's own blaster fire, since they are also red. Those of you that say the bot is running perfectly, you don't have this problem? The bot is missing objectives on certain missions because it is constantly firing at blaster fire instead of the ships.

I also have a similar problem with my Imperial Agent, which loves shooting at it's own missiles, as well as the engines of republic war ships. Both of these are causing me to fail Taspan Ambush consistently.

Those of you that don't have these issues, can I ask what type of PC you have? Video card?

I built my main PC about 2 months ago.. overclocked ivy bridge @ 4.6 ghz, nvidia gtx 680 video card, 2x SSD in Raid 0, etc it's a beast. I'm wondering if the video card settings can determine the accurateness of the targetting system though... gamma, brightness, etc?

I've tried running the bot on 2 laptops as well, all decent specs with nvidia cards in them, with generally the same result.

I saw it mentioned somewhere about compiling your own files with autoit.. does that help with the targeting at all?

And one last question.. is there a diffence between the color and capitalizations of "Yes" next to all the missions? Grey/Blue/Purple, Full caps and not, etc.

Thanks

Taspan Ambush so far wasnt tuned to have a successful mission path, with very much luck and best equip it might work at one of 10 missions. Syvris should run lot better but will depend on ship too. Currently my personal reference is Jedi Consular and Sith Inquisitor. We are aware that there may be issues with other classes, worst case is BH. Speaking in terms of 5.x there is
no good soloution visible, since 5.x will only support one path per mission. So it always will work better with one class as with another. For 6.0 there will be more than one mission path per mission available, but it will be a lot of water running down the Hudson until a 6.0 public preview is available.

If you build a PC, Nvidia always should be second choice. ATI based cards (IMHO Radeon) usually work better. Maybe Nvidia will do few more FPS but over the time ATI just makes less trouble.
To have an SSD running as Raid 0 ... well I guess you wouldnt appreciate my comment on that. Since everything of the bot is based on color, custom settings here will have big influence, as well as custom settings that sound like presenting a better picture, like Smoothvision antiscopic filters of HD anti aliasing.

Compiling the bot yourself will not change targeting or image recognition in any way. I planned a custom target color setting, thats what the Mission tuning tab was thought for. But since plans changed and work on 6.0 will start once 5.35 is "done", the tab will disappear with my next SVN update.

The mission status "Yes" colors represent the current developement status of a mission. Grey: successful mission main objective is very unlikely, Green: Mission main sometimes reached, Blue: Mission main reached with good succes (50% or better), Purple: Mission main has a very good succes rate, one or more bonus missions also will complete with a good success rate.

[phagotron]

Phago if you rename Impossible to Ascendancy and inside it from Impossible Sector to Ascendancy Barrier stuff it does work. They are an exact mirror... I did this and tested it... I can confirm it did work.

Someone else (k just seen, thx TM!) already uploaded it into the SVN, so its already in there. I just changed the color from grey to purple.

[phagotron]

I actually did this a few builds ago with Ascendancy and the Hydrian/Polith missions, so they should include the initial revision to IS already.

Last night, though, I made a few more IS revisions. Must. Make. Better. Anyway, it ran 14-1 on my first round of tests, with a 100% success rate for the bonus, so I'll be updating the other three missions again shortly

I needed to do smaller adjustments to Polith to make it work with lvl40 equip (EMP is lvl45) to shoot sufficient mines. There might be slight revisions needed too for the last 90 sec, running it overnight got me a 44/40 wins/loses . (Sith Inq) As it looks there is an tor related issue with the bonus: often enough the second hunter drives are not counted even if they have been shot by enough missiles that usually have killed them.

[sejin]

Has anyone else had an issue with dailies with the bot? It seems to just keep running the first mission in the daily loop over and over. I'm currently using 5.34

[TMichael]

...Now he's 45 and doing Kalee. 35/1 just at this moment. I was lvling a Saboteur last week doing Pollith. W/L 180/13, bonus every time. Tried today for 15 rounds watching for bonus, misses every time(12 loss, too). SO messed up synchronisation (first rocks are proper evaded now, but rockets aren't hitting at the last ship)...

Hi Nhuts,

I just wanted to pass along that Kalee was optimized a few days ago, so the won/loss ratio there sounds about right. Polith has completely new pathing (from the IS mission update work, which explains the improved avoidance), but only had a mission success rate of about 66% on the previous build because of those last ornery ships. I've come up with a new attack sequence for the final targets which comes at them from three directions, and so far this seems to be working much better.

The new code is in the latest unstable build, so feel free to download and let us know how it works for you. I'll post more updates as I go through more of the missions - probably Syvris next, since that was mentioned a few threads back.

[mcinsane]

I have a question for the coders:
I put a timer debugger in for myself and im noticing something weird which is why im having all my issues.

The bot starts on time, client and bot sequenced together, but as the bot progresses it will be 1 to 2 seconds off, which is why i keep running into the rocks...But at some point, the client and bot will be sequenced again.

My question is: Does the bot do sequence checks anytime after the beginning of the missions, or is it just that 1 time at the beginning?

[TMichael]

I needed to do smaller adjustments to Polith to make it work with lvl40 equip (EMP is lvl45) to shoot sufficient mines. There might be slight revisions needed too for the last 90 sec, running it overnight got me a 44/40 wins/loses . (Sith Inq) As it looks there is an tor related issue with the bonus: often enough the second hunter drives are not counted even if they have been shot by enough missiles that usually have killed them.

Thanks for testing those! The latest revisions (from today) include better bonus mission code, better survivability (I removed one mine field barrage and replaced it with a well timed pulse near the end), and a more efficient attack sequence for the final ships. I imagine that problems will still exist with level 40 equipment, but it's probably a good idea to run through it a few times first to see where any of the new problems might be.

[Rogean]

Thanks for the reply Phagotron. Let me give a little information about myself. I'm a network engineer by profession, and a programmer by hobby. I've always built my PC's with nvidia cards, and I generally prefer intel and nvidia over amd/ati. I believe that everyone has their preference regarding this, and no brand is clear cut definitively better than the other. I'm also aware of the lack of TRIM support with SSD in Raid, and their less than stellar track record for reliability :P.

Alas, this is not a discussion or debate over what makes the best PC I just wanted to give a brief background. My hope is that once I get the bot working consistently, that I can delve into messing around with the code and see about adding some new features that I've had in mind.

There's nothing different between the Consular and the Knight ships, correct? (I don't know if they have different blaster colors or something minor). My main character that I'm testing this bot on is a Jedi Knight, so it should fit the same success rate as a Consular. Is it normal for the bot to be firing at it's own blasters and missiles?

[TMichael]

I have a question for the coders:
I put a timer debugger in for myself and im noticing something weird which is why im having all my issues.

The bot starts on time, client and bot sequenced together, but as the bot progresses it will be 1 to 2 seconds off, which is why i keep running into the rocks...But at some point, the client and bot will be sequenced again.

My question is: Does the bot do sequence checks anytime after the beginning of the missions, or is it just that 1 time at the beginning?

Hi mcinsane,

The only true synchronization occurs at the beginning of each script when the timer image is read and the Autoit timer is initialized. After that, the timer itself is referenced throughout each mission script to help keep things synchronized.

If the bot gets out of sequence and then back into sequence on the same run, the problem could just be with the script itself. I'm in the process of running through the missions for testing and code clean-up now, but I've only been through five so far. On which mission(s) was this particular issue occurring?

[TMichael]

Thanks for the reply Phagotron. Let me give a little information about myself. I'm a network engineer by profession, and a programmer by hobby. I've always built my PC's with nvidia cards, and I generally prefer intel and nvidia over amd/ati. I believe that everyone has their preference regarding this, and no brand is clear cut definitively better than the other. I'm also aware of the lack of TRIM support with SSD in Raid, and their less than stellar track record for reliability :P.

Alas, this is not a discussion or debate over what makes the best PC I just wanted to give a brief background. My hope is that once I get the bot working consistently, that I can delve into messing around with the code and see about adding some new features that I've had in mind.

There's nothing different between the Consular and the Knight ships, correct? (I don't know if they have different blaster colors or something minor). My main character that I'm testing this bot on is a Jedi Knight, so it should fit the same success rate as a Consular. Is it normal for the bot to be firing at it's own blasters and missiles?

I'm an NVidia guy myself.

The bot firing at its own blasters (Empire side) is probably PixelSearch looking for a similar color and sending those coordinates to the attack code. Some of the code (Ascendancy/Polith) will sometimes look for the red crosshair after finding an initial target match, and this could be wreaking havok. Is this happening on any particular mission, or pretty much all of them?

[mcinsane]

I'm an NVidia guy myself.

The bot firing at its own blasters (Empire side) is probably PixelSearch looking for a similar color and sending those coordinates to the attack code. Some of the code (Ascendancy/Polith) will sometimes look for the red crosshair after finding an initial target match, and this could be wreaking havok. Is this happening on any particular mission, or pretty much all of them?

Drexel. It runs fine sometimes, but most of the time i have issues

[Rogean]

I'm an NVidia guy myself.

The bot firing at its own blasters (Empire side) is probably PixelSearch looking for a similar color and sending those coordinates to the attack code. Some of the code (Ascendancy/Polith) will sometimes look for the red crosshair after finding an initial target match, and this could be wreaking havok. Is this happening on any particular mission, or pretty much all of them?

It's happening on all missions for me.