[Open Source] Lucky's Spacebot

[phagotron]

@TMichael: I just updated the WaitForMissionTimerInit to the SVN. It may look a bit complicated but should be quite easy to handle. By default it now looks into 3 folders to locate the image. The image name may be just the name without the relative path and extension. Default folder still is "pictures\". (mi = 0)

Setting mi to 1 will lookup in each set folder to locate the image, If there is an image in more than one folder, it will be used.

There now is a global pset that can be set to a specific folder (currently pictures, Set-A, Set-B). Together with mi = 2 it will search the pset folder for imgname-a.png to imgname-c.png.

So if an a/b/c set of pcis for a mission is available, maybe best is to put it into Set-A, set pset to 1 and call timer sync with mi=2. Due to the global, this will only work for the mission where the pics are available, or the remaining space_ images have to be copied to Set-A then.

Hope the description helps, guess func has become a bit complicated in the end but I wanted to be able to globally switch to a specific pictureset if necessary.

[TMichael]

@TMichael: I just updated the WaitForMissionTimerInit to the SVN. It may look a bit complicated but should be quite easy to handle. By default it now looks into 3 folders to locate the image. The image name may be just the name without the relative path and extension. Default folder still is "pictures\". (mi = 0)

Setting mi to 1 will lookup in each set folder to locate the image, If there is an image in more than one folder, it will be used.

There now is a global pset that can be set to a specific folder (currently pictures, Set-A, Set-B). Together with mi = 2 it will search the pset folder for imgname-a.png to imgname-c.png.

So if an a/b/c set of pcis for a mission is available, maybe best is to put it into Set-A, set pset to 1 and call timer sync with mi=2. Due to the global, this will only work for the mission where the pics are available, or the remaining space_ images have to be copied to Set-A then.

Hope the description helps, guess func has become a bit complicated in the end but I wanted to be able to globally switch to a specific pictureset if necessary.

Sounds brilliant! I'm going to get a good night's rest, then tackle the image editing.

[arczi19]

Just a little update from me: the problem was Aero indeed. For some reason the service responsible for displaying Aero effects was disabled on my computer, so all I had to do was to enable Desktop Window Manager Session Manager service. Also, for some reason the bot was dying a lot when trying any 40+ missions on 5.35, so I got the older version, 5.32 and now most of those mission are running just fine, including Polith and Aetan

[phagotron]

Just a little update from me: the problem was Aero indeed. For some reason the service responsible for displaying Aero effects was disabled on my computer, so all I had to do was to enable Desktop Window Manager Session Manager service. Also, for some reason the bot was dying a lot when trying any 40+ missions on 5.35, so I got the older version, 5.32 and now most of those mission are running just fine, including Polith and Aetan

Thanks for the great report, might have happened to me too. Guess that should be mentioned in Q&A. If you still run a 5.35 preview "hotfix", these are outdated. Get the current one from the SVN (psx x86 unstable, R105 or higher) and give Polith a try, has been recoded by TMichel to be close to 100% with a selectable Bonus path. Sullust recoding is pending, currently it wont complete.

[Cystacae]

First they love it, then they joke about it, then they blame you for it until they find out how to use it. If at stage 4 you usually are married or at least engaged. Be prepared

I can only speak for myself. I would feel bad if I'd leave 5.35 as it is and dive into something new. I know that you badly want 6.0 to pace up but what would it help if we start over with 7.0 in same way one day leaving behind some half baked code behind. Maybe I'm a bit too much on rails to split my attention, maybe things go a bit too fast for me, so unless 5.35 isnt done I wont be much help for 6.0. Also maybe I feel a bit pushed atm. Maybe its the "just make this feature work, no matter how" thing where I only know too well what it leads to.

I wasn't intending on.... ok... we won't rewrite the bot. However, we do need to clean it up ALOT. It is a mess of confusion in there. Could we break the code up into pieces of related material? When I created stuff in 4.0 and 5.0 series I was all ways worried the upgrades I put in wold stop the bots functions. I am not trying to make you feel pushed, not my intention at all. I will work on a new interface.

[Cystacae]

That makes sense to me.



No worries, I feel the same way about 5.35. I'm right there with you until it's ready to go out into the big bad world on its own.

The code does need an overhaul and I still would like it to be split into sections relating to each other. Since you guys feel the same about 5.3 series and 6.0 we will just continue but on a longer delay in release. 5.3 line will continue as planned and will not be affected.

[phagotron]

I wasn't intending on.... ok... we won't rewrite the bot. However, we do need to clean it up ALOT. It is a mess of confusion in there. Could we break the code up into pieces of related material? When I created stuff in 4.0 and 5.0 series I was all ways worried the upgrades I put in wold stop the bots functions. I am not trying to make you feel pushed, not my intention at all. I will work on a new interface.

Mate ... now dont jump from one edge to the other, keep cool, lean back, stay tuned. I dont want to let 6.0 go but atm its just a bit early to throw everything aside and jump into something new before the current version is in a presentable shape. I guess TM also curious about 6.0. But maybe it could work better to do the redesign / rewrite with a bit more of a plan than just breed out a new idea quarterly and drop in all forces until we realize a dead end.

My suggestion is to collect a feature list first to see whats on the plate. Then evolution - rinse and repeat. Once we are sure what features 6.0 will carry it might be the user interface, then we underlay whats needed for missions etc. Let there be time for the first step, everything else will come then. Keep in mind that collecting and evolving the features is a serious task and will take its time. No need to be hasty with that. Just put a txt file into the svn so we have a reliable source for this list and can add ideas and comments there.

Meanwhile we focus on 5.35, there still are issues with the missions along with some things to test. If you feel the need to brush up the interface - I dont mind that.
Anyway, it makes hardly sense to rewrite 5,35 part by part until something like 6.0 comes out. Just too much twisted code in it. But it still has its time.

[vapor311]

6.0 will not be a rewrite. But code does need an overhaul and I still would like it to be split into sections relating to each other. Since you guys feel the same about 5.3 series and 6.0 we will just continue as if I never said code rewrite.

Im out till this weekend, my machine crapped a brick last night via HD failure.

[Cystacae]

Mate ... now dont jump from one edge to the other, keep cool, lean back, stay tuned. I dont want to let 6.0 go but atm its just a bit early to throw everything aside and jump into something new before the current version is in a presentable shape. I guess TM also curious about 6.0. But maybe it could work better to do the redesign / rewrite with a bit more of a plan than just breed out a new idea quarterly and drop in all forces until we realize a dead end.

My suggestion is to collect a feature list first to see whats on the plate. Then evolution - rinse and repeat. Once we are sure what features 6.0 will carry it might be the user interface, then we underlay whats needed for missions etc. Let there be time for the first step, everything else will come then. Keep in mind that collecting and evolving the features is a serious task and will take its time. No need to be hasty with that. Just put a txt file into the svn so we have a reliable source for this list and can add ideas and comments there.

Meanwhile we focus on 5.35, there still are issues with the missions along with some things to test. If you feel the need to brush up the interface - I dont mind that.
Anyway, it makes hardly sense to rewrite 5,35 part by part until something like 6.0 comes out. Just too much twisted code in it. But it still has its time.

Ok then, I will chill out on 6.0 and not get riled up. I will experiment though and see if I can split the code safely into module for 5.35 as a test.

[Cystacae]

Im out till this weekend, my machine crapped a brick last night via HD failure.

Been there, done that, good luck.

[mcinsane]

A issue i noticed, more like a request lol.

CrewSkills
Diplomacy

Bot does: chooses light and dark side quests.
Would like: Choose only light side or dark side quests as to avoid gaining points for the other side(light/dark side)

[mcinsane]

A issue i noticed, more like a request lol.

edited: nvm, answered my own question

[corran11]

Well guys, i gotta say that this bot is as awesome as easy to use
but i still have serious problem, Drexal mission is not working as well as its supposed to so i tried using one of the unstable versions but all i got was leaving the mission few seconds after it started, i tried changing image detecting thingy and i could make it work at 115 but only for first mission, then when it tried to rerun it the same error appeared
tho i have to say that it worked flawlessly with psx unstable, i mean it didnt hit the rock and shot everything easily, i would love to run for hours but cant make it work more than once

what is weird, the stable version worked very well, never quit the mission, its just not effective, loses most of times

any idea how could i resolve it?
thanks

(ofc i have windowed 1024x768 with low settings and default interface)

[TMichael]

Well guys, i gotta say that this bot is as awesome as easy to use
but i still have serious problem, Drexal mission is not working as well as its supposed to so i tried using one of the unstable versions but all i got was leaving the mission few seconds after it started, i tried changing image detecting thingy and i could make it work at 115 but only for first mission, then when it tried to rerun it the same error appeared
tho i have to say that it worked flawlessly with psx unstable, i mean it didnt hit the rock and shot everything easily, i would love to run for hours but cant make it work more than once

what is weird, the stable version worked very well, never quit the mission, its just not effective, loses most of times

any idea how could i resolve it?
thanks

(ofc i have windowed 1024x768 with low settings and default interface)

The issue with mission starts is a top priority at the moment. We're in the process of implementing a wider range of image sets to check against so that a wider range of monitors will detect mission starts consistently. Phago or I will post once a full set for all missions is available in the Unstable build.

So, coming soon!

[swizzie]

So I am kind of lost here. Do any versions fully work? it seems I cannot find a version that I can let go over night, do missions and have companions collect stuff. It is either one or the other.