[Beta] UntzBot (Space Missions Bot, recorder+player)

[TheGlow]

This has just been getting erratic.
Skaross synced with 1200 delay. I come back in an hour, 5 wins and 1 loss, not too bad. but im watching and its ahead. OK, i add some delay to 1400, now its very behind. I take it back other way to 1000, not enough delay.. wtf, I try 1100, too early. 1200 too late.
in between is still either or. it seems its randomly loading it up out of sync regardless.
It seems we need the trigger to not be time but a location, first target, etc.
Is it looking only at the timer area for a trigger? if i make a bmp of some ships, will that work?

Just tried out of curiosity taking several screen shots of the moment 5:15 on Skaross and each one is different.. so there goes the idea of it being specific

[KcBlack]

Just in case it hasn't been said yet, having your frames showing in the corner can cause a problem. Learned this today earlier when I went to start the bot up mid day. Took me a while to realize it was open and that's why I was getting the "galaxy map not found" error.

[Tipsyy]

I think i've tried every suggestion on syncing so far.. I've tried changing the delay even in the 10's (1210,1220,1230-2000) X_X It's just haywire. Can't wait till the update. Meanwhile i'm increasing armstech!

[thephilz]

Just tried out of curiosity taking several screen shots of the moment 5:15 on Skaross and each one is different.. so there goes the idea of it being specific

as i think ive stated before, the timer is not fully reliable, and youve obviously found out what i meant
the mission load times depend on your comp specs, your internet lag, and also what i call 'mission evilness', which is the huge random delay spike for absolutely no reason that throws off the timer
however, the missions will always follow the same routine, so ships will always be in sync with each other, which is what 4.0 will sync to instead, not that stupid unreliable timer

I think i've tried every suggestion on syncing so far.. I've tried changing the delay even in the 10's (1210,1220,1230-2000) X_X It's just haywire. Can't wait till the update. Meanwhile i'm increasing armstech!

yeah syncing is just evil some times, and some missions are simply horrid to sync. 4.0 will try fixing that .. keyword, 'try'

Just in case it hasn't been said yet, having your frames showing in the corner can cause a problem. Learned this today earlier when I went to start the bot up mid day. Took me a while to realize it was open and that's why I was getting the "galaxy map not found" error.

note taken, will throw that into the readme file or similar later

I changed the imagesearch function to pixelsearch instead for a box of 2x2. Then I'd hone in on a particular area of the SWTOR window and get coords that would pick up a certain pixel color as a ship or something passed. The color would have to be in stark contrast to the backdrop but it has been working almost flawlessly for me as long as the tolerance is set properly. I don't even use a sleep delay anymore. I don't know if this would work universally for everyone or if it would be machine specific but its been working great for me.

Also I have revamped my disconnect protect and made a separate mini bot that logs you back into the game upon DC and starts up the missions again. I'd be willing to share it cause i know some of you guys have crappy internet like me and get DCed all the time, but I won't share it unless thephilz gives me permission. He has done such an awesome job building this bot!!

that is exactly what 4.0 is going to do, ive had the system in use for quite a while now but the crash error has taken priority (no point releasing a fix if something else is broken amirite)

Quick update, 2.0x_NoSettingsFile works perfectly for me. The NORMAL 2.0x file exhibits the same behaviors that were causing slow downs/freezing as the 3.0 versions. Mind you, this is just MY findings, this is obviously a very per-individual problem.

blah .. so it appears the settings file might be the cause, as i suspected

i will remove it temporarily from future releases until i can debug it fully
but really, opening and reading a file crashing the swtor client? really?
to be honest the bot already reads/writes from scripts/BotStatus.txt (which deathcheck uses) so i have no idea why it would stuff up with another file.

Also I have revamped my disconnect protect and made a separate mini bot that logs you back into the game upon DC and starts up the missions again. I'd be willing to share it cause i know some of you guys have crappy internet like me and get DCed all the time, but I won't share it unless thephilz gives me permission. He has done such an awesome job building this bot!!

the deathcheck originally had the anti-dc functions (it looks for the [play >] [okay] and etc buttons in server list) but i had a slight problem matching it with different clients so i removed it
ill ninja-reintroduce it probably next update

Id like to hear more details as I like to know how shit works behind the scenes.

ive been pretty open about the process, but here is a basic summary
- find world map
- click on chair
- figure out what mission you want, select it
- wait for timer (or in 4.0, an event)
- start recording/playback process
- play hits stop OR playback finishes
- find result
- back to the top

however the hard sections are the ones put in bold, and deathcheck is on during the playback to make sure it quits properly

-------

anyway with this in mind ill work on 3.3 and try to get it up tomorrow after i get home from going out

depending on how busy i am with my uni work 4.0 should be up by the weekend or during the weekend, but preferably the weekend (for me as well, i dont really like staying at home on weekend)

and i might as well just post this,



this is my results after sleeping for 10 hours, lol

however when i run an evil mission like skaross (which i now avoid) i end up with something like 60:30, which i guess is still okay, but yes different missions have hugely varied success rates.

[ortner]

Anyone want to share their Pakuuni recording?

[wimbobby]

Bot's working really well for me, but is there any way to get it working on XP? I've got a friend who'd really appreciate it.
Cheers.

[Rinthiax]

Bot's working really well for me, but is there any way to get it working on XP? I've got a friend who'd really appreciate it.
Cheers.

It works on XP just fine. I have no issues running it on XP SP3 Home on 3 of my current botting computers.

[qbert34]

I like your bot well enough, but like many here, the sync is a big issue. It takes me a long time to get it to sync correctly!

I record my own missions, and it will still get out of sync and end up failing. I'm simply trying to do the basic noob level mission, Saleucami Fleet. Sync is important because it needs to kill 5 out of 6 special ships. And an additional heavy armored ship. Failure to destroy these targets always results in my loss! So if I can't get the correct sync with my missiles, it's a very high failure rate.

[FanyFany]

Anyone having trouble recording missions for Imperial44Aeten? On this particular mission the bot is stuck on "looking for timer", and I can not record. I have changed the delay from 2000 all the way to 8000 to try and get it to work. I have even tried going back to previous versions of the bot (3.1d)

[niiklaaas]

Anyone having trouble recording missions for Imperial44Aeten? On this particular mission the bot is stuck on "looking for timer", and I can not record. I have changed the delay from 2000 all the way to 8000 to try and get it to work. I have even tried going back to previous versions of the bot (3.1d)

Then you're having the same problem as I have. I can't get past the point where the bot says "looking for timer", I can't get any in-mission images to match at all.

[FanyFany]

I can remember the name of the other missions, but the easier version of Aeten Defense, was giving me a lot of trouble with the timer as well. I am trying to record for the other lvl 44, but the EXP is not nearly as good as Aeten, and the failure right is much higher.

[TheGlow]

however when i run an evil mission like skaross (which i now avoid) i end up with something like 60:30, which i guess is still okay, but yes different missions have hugely varied success rates.

Great to hear that.
And actually, for a weird turn of events I woke up this morning and the bot was 84/0/0. On Skaross no less.
Only thing I did differently was make my own bmp of the timer, manually set the in game res to 800x600. I didnt even rerecord, still used the one I did previously.
Synch I had to set to 3150. But I would stop by occasionally to look at see it would be out of sync in the middle, but then be back on track near the end. So definitely something weird. Since those bombers move slow you get a lot of room for error. Even watching in the morning 2-3 in a pack would get away, but still enough to hit the 50 goal. The side mission to blow generators was hit or miss. and i blew a lot of missiles on em. Some it'd hit em all, others only 1 or 2.
Before work it was still at 89/0. I hope the wife doesn't stop it.
But again perfect example of one mission running better on one users than anothers.

Does the delay have any bearing on the recording process or just playback?

I think i've tried every suggestion on syncing so far.. I've tried changing the delay even in the 10's (1210,1220,1230-2000) X_X It's just haywire. Can't wait till the update. Meanwhile i'm increasing armstech!

Note that 1000 is a second. Changing it by 10 is going to be barely noticeable.
What I do is try to fire at something easy to spot early on, center of the moon, a small asteroid, top of an antenna, etc.
Then when playing back, see how bad my aim is. if your shooting it too early, not enough delay. raise it 200 or so. If your shooting where the target already passed, your too delayed, bring it back 200 or so. Eventually you'll find a sweet spot.

Then you're having the same problem as I have. I can't get past the point where the bot says "looking for timer", I can't get any in-mission images to match at all.

I tried taking pics of areas around the timer, and had that problem. I remember you tried making pics with the minutes in it. I just use bmps in similar layout as thephilz, with just the seconds around it and that 1 pixel or so border around them .

[niiklaaas]

Great to hear that.
And actually, for a weird turn of events I woke up this morning and the bot was 84/0/0. On Skaross no less.
Only thing I did differently was make my own bmp of the timer, manually set the in game res to 800x600. I didnt even rerecord, still used the one I did previously.
Synch I had to set to 3150. But I would stop by occasionally to look at see it would be out of sync in the middle, but then be back on track near the end. So definitely something weird. Since those bombers move slow you get a lot of room for error. Even watching in the morning 2-3 in a pack would get away, but still enough to hit the 50 goal. The side mission to blow generators was hit or miss. and i blew a lot of missiles on em. Some it'd hit em all, others only 1 or 2.
Before work it was still at 89/0. I hope the wife doesn't stop it.

Does the delay have any bearing on the recording process or just playback?


Note that 1000 is a second. Changing it by 10 is going to be barely noticeable.
What I do is try to fire at something easy to spot early on, center of the moon, a small asteroid, top of an antenna, etc.
Then when playing back, see how bad my aim is. if your shooting it too early, not enough delay. raise it 200 or so. If your shooting where the target already passed, your too delayed, bring it back 200 or so. Eventually you'll find a sweet spot.
But again perfect example of one mission running better on one users than anothers.


I tried taking pics of areas around the timer, and had that problem. I remember you tried making pics with the minutes in it. I just use bmps in similar layout as thephilz, with just the seconds around it and that 1 pixel or so border around them .

Trust me man, I've tried for atleast 10 hours making a valid picture. The pictures has been from like 50x20 to 2x2 big, so the image itself isn't the problem.

[thephilz]

Does the delay have any bearing on the recording process or just playback?

just the playback.

the recording delay is stuck at 2000 so you have two seconds to adjust anything, if you need to. for the record, when i bot, i keep it at 2000

to be honest, start delay SHOULDNT even mean anything - if it was set to 0, or 2000 on both, they >should< still sync correctly with each other no matter what, only if the timers sync together (which of course, as you all know, they often dont, which is why we have this problem)

however due to the fact that sometimes the original recording might start late or early, away from the 'real average' time, you can adjust the delay to match the average loading time to get a higher success rate (if that makes sense ..

Trust me man, I've tried for atleast 10 hours making a valid picture. The pictures has been from like 50x20 to 2x2 big, so the image itself isn't the problem.

unfortunately all the advice i can give is practically everything theglow has said

if the mission is starting, then that means your window positioning is correct, so the bot should be looking in the correct area for the timer

please note that the area it looks in is actually quite large (much larger than it should be) so the timer is practically impossible to miss if set up correctly

so by following the howto guide it should work for you

to be honest, im really not sure what to do if it does not, which seems to be the problem with you

and make sure you save as .bmp

Anyone having trouble recording missions for Imperial44Aeten? On this particular mission the bot is stuck on "looking for timer", and I can not record. I have changed the delay from 2000 all the way to 8000 to try and get it to work. I have even tried going back to previous versions of the bot (3.1d)

if everything works except for a certain mission, then youre going to have to replace the given image to be compatible with your computer. follow UntzBot on how to make an image and replace it with your own. my images work on most computers but of course everyones comp is different, so yeah

[aslz78]

Since Someone asked, Here's Pakuuni and as a bonus, Hydian.

Each are done with the best upgrades avaliable at the time, and work for me with very little error rate. (Practically zero at Pakuuni and 30-2 on Hydian)